I have flashed skrilax v8 unlocked BL with v8pubA50 recovery
I flashed it using blackthund3r ATX flashtool
My question is
1. Why I can't enter boot recovery, it's just show green robot with exclamation at its body
2. How I can flash cwm recovery since it's extension is .Img
(fyi). I use UNroot A501 with stock HC 3.2.1
Thanks
Sent from my A501 using xda app-developers app
Help help :'(
gigacats said:
Help help :'(
Click to expand...
Click to collapse
IF you are sure you have the v8 bootloader installed, you should be able to install a recovery.
You must have an ICS rom installed, or on the Ext SD card, have an ICS rom ready to flash.
If you currently have a stock ICS rom installed, then you need to be rooted, and delete the "boot recovery" file (or similar name). Or else when you boot your tab, the custom recovery gets overwritten.
You can look at Civato's Bootloader and Recovery guide for the exact name of the file.
Note that v8 bootloader and ICS recoveries, DO NOT work well with HC based roms. You must have an ICS Rom.
MD
I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app
gigacats said:
I'm on HC 3.2.1 stock ROM and unroot
Here i give some picture
View attachment 1218773
View attachment 1218774
When i choose boot recovery, that robot will go out and my tab restart after a minute.
Please guide me how to open recovery.img
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
1) the robot is the 'stock recovery.img'
2) you must be rooted before you can flash 'anything'
3) The only way to do this (on HC) is by installing a custom pre-rooted rom
4) If you want ICS your tab should update itself, you will need acer enhancement app from the market. then Settings>About Tablet>System Update
5) you can install a stock or custom ICS rom BUT you must have root to update to the patched bootloader which some of the custom roms require.
6) you cannot "open" recovery.img.
Ok, so please stop posting the same issue in other threads, or you will never get your problem solved.
Now. You say you have Skirlax_cz's V8 bootloader installed. Correct? If so, you should be able to boot into the menu system of it (vol+ and PWR). If you get the bootloader menu, good.
Now, you will need the Android SDK (google it and download and install it). After installation, go to c:\windows\program files (x86)\android\android-sdk\platform-tools. Open a command window here. (it may be installed in program files)
Boot your tablet like I described above, and at the bootloader menu, select "fastboot". The tablet should say fastboot mode.
Now, copy your recovery.img (or whatever you named it) into the platform tools folder on your PC. It has to be in the same folder as fastboot.exe
Now, make sure you have the rom you want to install on your EXT SD Card.
Next, plug in your tab to the USB (I always make sure in device manager that the tab is recognized as a fastboot device)
In the command window you opened earlier, type in the following;
fastboot flash recovery recovery.img
Remember, if your recovery image is named "public-recovery.img" for example, that is what you should type in the command above.
Once the recovery is successfully flashed, then turn tab off.
Unplug from USB
Hold PWR and Vol- untill you see the message "booting recovery kernel", then release both. You should boot into the custom recovery now. Then you can do your wipes and stuff as per the rom install instructions.
Of course, this is ONLY if you have the V8 bootloader running.
Also, I posted a better rom. Evil Alex Unleashed, so you should install this. It has problems fixed.
MD
OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts
gigacats said:
OK MD, thanks for your guide.. now I have installed your ROM successfully, it's running very smooth. Thanks very much and sorry for double posts
Click to expand...
Click to collapse
Wow! It worked!!!!!!!!!!!!
Damn, better than I thought.
Gotta love Skirlax_CZ and putting flashboot in the bootloader v8. Throw a thanks at him when you get the chance please. And if you used EZTerry's public recovery, please throw a thanks at him also. And anybody else who helps you. That's how it works here.
I hope you installed Evil Alex. She's much better than Alex V. Alex V is a good girl, but she need the wakelock app from the market. Evil Alex hopefully does not. After all, these are Acer leaks. AKA "beta". So we really don't know what to expect. And things "will" change in the next month, and new builds "will" be released.
Am glad you got it running.
And Dibbs, throw a thanks to him also His instructions were after all, correct (he didn't know your V8 was working).
Any issues, please put them in my rom thread.
MD
Related
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
sfetaz said:
I have never done this, but I am sure you can use software on your PC to do a nandroid restore to full stock honeycomb. Then once you are stock use one of the root methods to reattain root and then upgrade to a ICS Rom. Research the development forum.
Click to expand...
Click to collapse
I hope there is program like that
Backwardsblade said:
Can you nvflash?
Sent from my Transformer TF101 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think so.
I try but don't find the device
frederuco said:
If you want to flash to completely stock, unrooted, just go to the ASUS Support site, download the firmware you want (ICS or HC 8.6.5.21). Unzip the file 1 time (it will still be a .zip) and put it on a microSD.
Go to CWM, install zip from card, choose the update.
It will overwrite CWM and go back to stock recovery, unrooted stock ICS or HC.
I saw GoodIntentions has a post around here somewhere with that info in it.
EDIT: Found it - [UNROOT]The easiest unrooting method
Click to expand...
Click to collapse
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
1090t said:
I hope there is program like that
I don't think so.
I try but don't find the device
I try that many time
I get " installation aborted " (status 7)
I use: US_epad-user-9.2.1.11 & US_epad-user-8.6.5.21
Click to expand...
Click to collapse
unzip first. inside another zip file.
goodintentions said:
unzip first. inside another zip file.
Click to expand...
Click to collapse
Yah, i do that
.........................
why is the only rom i can install and work is the: Android Revolution HD ?!
1090t said:
why is the only rom i can install and work is the: Android Revolution HD ?!
Click to expand...
Click to collapse
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
1090t said:
hello,
My device: tf101
running: Android Revolution HD-EeePad v3.0.0 (root)
I have these following issue in my tf101 :
1) after my install the custom rom the device auto boot in to Clockworkmod Recovery not in to the rom ( so i always press power button and - button and select the android logo to boot)
2) when i left device is auto shut down.
4) I can't update the Clockworkmod Recovery 3.1.0.1 (R3-240511-1908) to the new one.
I like to flash to last stock update and root device.
sorry of all these mess,
Click to expand...
Click to collapse
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
goodintentions said:
You have a very odd problem. I've never seen this problem before. They should all work.
The only other suggestion I can give is try installing the stock recovery, use it to flash in the stock honeycomb build, and upgrade to ICS from there.
Just follow the following instruction.
(1) Download the stock recovery and the honeycomb build from asus website.
stock recovery
(2) Flash stock recovery in with your CWM.
(3) Unzip the honeycomb firmware from asus ONCE and change the name of the zip you find inside to "EP101_SDUPDATE.zip"
(4) Restart the TF system. The firmware should install automatically with the stock recovery.
If it doesn't, tell me and we'll try something else.
Click to expand...
Click to collapse
it doesn't work i just wait there
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is that right why to boot in to rom (from cold-boot) ?
horndroid said:
The problem is most likely with your CWM Recovery version 3.1.0.1
Replace it with this recovery http://forum.xda-developers.com/showthread.php?t=1446019 and try flashing the stock Asus ICS rom again.
Click to expand...
Click to collapse
I try many time with these the Recovery still same
even with the old version ..nothing
1090t said:
it doesn't work i just wait there
is that right why to boot in to rom (from cold-boot) ?
I try many time with these the Recovery still same
even with the old version ..nothing
Click to expand...
Click to collapse
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
feisty_noodle said:
I will venture a guess that you are on CWM 5.5.0.4 installed using RomManager.
If so, you are experiencing a well established problem with a fairly easy solution.
Look at this thread and ask for help, if needed:
http://forum.xda-developers.com/showthread.php?t=1530337
By the way, installing a stock recovery is almost always a bad option. Don't do that.
Good luck.
Click to expand...
Click to collapse
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
The op's problem is very similar to this one http://forum.xda-developers.com/showthread.php?t=1549062 which has been resolved.
goodintentions said:
This is not his problem. He clearly states he's on another CWM.
He's got some other weird problem... either that or he doesn't know how to do these things correctly. We're giving him advice assuming he knows how to do certain things correctly.
Click to expand...
Click to collapse
You are right, I may have misinterpreted the OP.
Still, I think the solution is the same.
When the device boots into recovery and can be cold-booted into ROM, the most likely culprit is the 'boot-recovery' flag which is set in the /misc partition. When the system sees that upon boot, it goes straight into recovery.
It should be the recovery's job to blank out that flag at some point, but CWM 5.5.0.4 (and, perhaps this recovery the OP is using) does not do this.
So, the solution is to reset it with the 'echo ...' command (or blanking out the first few bytes of /dev/block/mmcblk0p3) in shell.
My suggestion is very conservative.
I'll gave try and let u know
when i connect to the computer nothing shows up
even the Asus sync don't found it
I'll gave try on Linux
any help
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Vipe.teo said:
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Click to expand...
Click to collapse
You need to unlock your bootloader and flash a recovery
blackthund3r said:
You need to unlock your bootloader and flash a recovery
Click to expand...
Click to collapse
Thanks for your reply, can you recommend threads to teach me how to go about doing it?
I believe Mlopik page did mention if I follow correctly, I would have already unlocked my bootloader, am I right?
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Moscow Desire said:
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Click to expand...
Click to collapse
Hi, thanks for coming to my aid, sorry for PM-ing U asking for help.... but I'm a super noob for this....:silly:
1) I have a boot screen by Skrilax_cz, but how do I fastboot a CWM recovery via a command prompt window?
2) A few min ago, I tried to use AfterOTA it got stuck at [3/4 flashing recovery] for a long time..... (Force restart)
3) I saw a solution <Click Here> then after downloading the recovery.img and running the code... It say done but after i restart nothing happen.
4) I continue using AfterOTA, again it got stuck at [3/4 flashing recovery] for a long time.....(Force restart)
I out of option....
erm... Help ???
Use fastboot to do a complete wipe.
Run ICSROOT. Zip to get rid of the boot.p file.
Reflash the v8 and cwm using apxflash tool
Boot straight to cwm and flash yr rom.
Do not use any type of rom manager apps to flash roms
Sent from my GT-I9300 using Tapatalk 2
FIXED !!!
Yeah !!! Got It to work !!!
Big THANKS to all who have help and spend time answering my noob questions...
THANK !!!!
First of all I want to tell everybody I work as a WebDeveloper and designer. Last year I had rooted and changed my rom on HTC HD2 (to know i am not a newbie to this area) not a big deal. Me and my brother decided we can root our ACER ICONIA A500 because we.. just wanted it, but I guess we mess it up hard. Here is what we have done:
1.Find a SD card - Format it to FAT32 - Upload the GingerBreak.apk - USB Debugging (ON) - Original thread - http://forum.xda-developers.com/showthread.php?t=1055354 - DIDNT WORKED
2.Format the SD card for second time on FAT32 and run the files on PC from this thread http://forum.xda-developers.com/showthread.php?t=1546593 (ofcourse following all steps one-by-one) - and guess what -> IT DIDND WORKED
So we tought rooting for this device wont work, we have to try something else and I uploaded "update.zip" (this ZIP was from http://forum.xda-developers.com/showthread.php?t=1633907 ) into my formatted SD card and run the tablet with Power btn and Vol- it started to load it everythig seemed OK till it restarted by itself and showed me this VIDEO
So where I am now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
on the second pic it says "boot verified failed..."
The version before I bricked it was with Android 4.0.3
Kernel version: 2.6.39.4+
Image version: Acer _AV041_A500_RV03RC01_WW_GEN1
Build number: Acer_AV041_A500_1.031.00_WW_GEN1
P/N: FM.S14A0.00U
What can I do now?
EDIT: I've got it running back by putting stock "Acer_AV041_A500_1.031.00_WW_GEN1" into SD card naming it update.zip and booting by Pwr btn and vol-
But Now... How to root it?
If u never root or unlock bootloader so maybe your a500 still on hc bootloader n u just doing upgrade it into ics rom woth hc bootloader with unsigned version update. Zip,maybe u can find how to push the honeycomb rom update. Zip into root of sdcard using adb and doing flash again pwr+vol -
Sent from my HTC Desire VC
oregorn said:
But Now... How to root it?
Click to expand...
Click to collapse
Go to the dev section.
a. NVFlash Unlocked Bootloader
b. Install CWM recovery
c. Flash a rooted ROM
Moscow Desire said:
Go to the dev section.
a. NVFlash Unlocked Bootloader
b. Install CWM recovery
c. Flash a rooted ROM
Click to expand...
Click to collapse
This is like step 1 then step 2 or just three different methods I can get my tablet rooted?
Could you please help me with some links? Thank you
oregorn said:
Thats the options like step 1 step 2 or just methods i can get root?
Could you please help me with some links? Thank you
Click to expand...
Click to collapse
The ONLY way to get root with full system RW, is to go to this thread;
http://forum.xda-developers.com/showthread.php?t=1622425
There are several ways to do this (unlocked bootloader and CWM) You HAVE to do the bootloader, and you HAVE to install a CWM. And you HAVE to install a pre-rooted rom. The thread offers different methods to do this via an application run from PC.
Root, is just allowing access to view the hidden system files. Most root apps, demand to do writes to the /system. Example, is SU. It does remounts so it can install SU binaries. Just having the Superuser app doesn't mean anything without /system RW. And the only way you get that, is by running an insecure kernel. And the only way you get an insecure kernel on ICS/JB, is via CWM. And of course the only way all this works, is via unlocked bootloader.
That's why we have the package in that link.
You "might" get by with doing the bootloader and CWM. Afterwards, Flash one of the kernels in the dev section (just look), then install SU and Busy Box from the market. This might probably keep your current rom intact. Or, just install a custom rom.
Ok. I think I unlocked my bootloader successfully. But I find it difficult to actually Install CWM recovery! I know that i have to have root before installing CWM recovery actually, am I right?
These are videos from what happens when I launch the tablet on normally and with vol + & -
tinypic.com/player.php?v=33u4lzo&s=5 - Normally
tinypic.com/player.php?v=2cy41fq&s=5 - Vol-
tinypic.com/player.php?v=2s82zdj&s=5 - Vol+
Question: What is full system RW ?
I even dont know how to flash a kernel.
It may be hard, but I will keep trying till its done.
oregorn said:
Ok. I think I unlocked my bootloader successfully. But I find it difficult to actually Install CWM recovery! I know that i have to have root before installing CWM recovery actually, am I right?
These are videos from what happens when I launch the tablet on normally and with vol + & -
tinypic.com/player.php?v=33u4lzo&s=5 - Normally
tinypic.com/player.php?v=2cy41fq&s=5 - Vol-
tinypic.com/player.php?v=2s82zdj&s=5 - Vol+
Question: What is full system RW ?
I even dont know how to flash a kernel.
It may be hard, but I will keep trying till its done.
Click to expand...
Click to collapse
Can't see anything from yr links for some reason BUT to clarify.
No you are not right!
If you want root to install a recovery, it doesn't work like that with the acer, you must unlock the bootloader.
The unlocked bootloader AND custom recovery are 1 package - if the flash is successful you will already have cwm.
The link Moscow provided you with gives you everything you need.
Which ever method you choose (manual nvflash or auto tools) you must follow each step to the letter!!!
Run the bootloader package again.
Choose yr recovery.
Flash.
Boot DIRECTLY to recovery.
Wipe data/media and cache
Flash yr rom
Reboot.
Done.
If you really only want r/w access use blackthund3r's ICSRoot tool...in the link Moscow posted.
Also if you are on stock rom be sure to read that post regsrding boot.p file.
All of this information is in that post, please take some time to read thru it so u know exactly what is involved. ...if u need further help there are guides in my sig as well.
dibb
Sent from my GT-I9300 using Tapatalk 4 Beta
dibb_nz said:
Run the bootloader package again.
Choose yr recovery.
Flash.
Boot DIRECTLY to recovery.
Wipe data/media and cache
Flash yr rom
Reboot.
Done.
Click to expand...
Click to collapse
This is the word i was missing all time.
What i have done?
Installed TWRP, Wiped off SYSTEM,Factory, Dalvik Cache, Cache and finally installed stock rom with full root.
CTR V2.4 Full Touch Recovery for Our Device
INFO
It is basically CWM V6 Recovery with full touch support and touch buttons menu. It has all functionality of CWM Recovery, with added extra, Aroma File Manager support.
Instructions
Important to know: if the menu is bigger than
screen surface, to be able to scroll page down you
have to swipe right , and for scroll page up to swipe
left. Also swipe left for Go Back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Install:
1. Download and install mobile uncle tools from Playstore
2. Copy Recovery.img to root of your sdcard
3. open mobileuncle tools and select recovery update
4. select your recovery.img and select yes to flash recovery
NOTE :: if you see too many recovery images after choosing recovery update
then disconnect from wifi or mobile data then tryDownload v2.0 - http://d-h.st/2Vc
Download v2.2 - https://drive.google.com/file/d/0B0hTietms2e6cFZuUTJSVXcyTnM/edit?usp=sharing
Download v2.4 - https://www.dropbox.com/s/mwn4p3i2p28qgzz/CTR_V2.4_Q700.zip
amazing recovery
Thanks for making this recovery,
I was waiting for recovery like this,
Nice UI,
Easy to use,
Rainbow mode is also good
Every thing is fine..
Thanks dude
i am having a little bit trouble......heres wat happened.......wen i did the whole process...it went in to recovery mode and everything worked well...wen i reboot my device.. and try to go to recovery mode by pressing power&volume it goes to normal stock recovery... even i open mobile uncle tools and select reboot in to recovery it again goes to stock recovery...and again i did 4steps again selecting recovery.img..then it went to touch recovery but system reboot and shutdown..etc wen i click on them,a screen appears asking "no--or---yes(reboot to stock recovery)""this cannot be undone"..something like that...so i removed battery and restarted again....
Will this cwm works with xolo Q700s too?? Help plz need custom rom n cwm
Sent from my Q700S using xda app-developers app
I copied the recovery.img to root of sd and disabled wifi/data, still mobile uncle tool doesn't show any recovery. It throws an error "finish search, num0".. Any help.
Edit 1: Got the solution. the file downloaded is something.apk and it should be renamed as recovery.img.
Edit 2: After I renamed the file and ran through mobile uncle tool, it would boot into recovery but give "No command" error.
Figured out that the right way to do is download the file in computer, unzip it, transfer it to mobile sd card, and then run through mobile unkle tool.
Everything fine except when install from sd card if many files in sd card it doesn't scroll down so i need to keep files to be flashed in folder named a...
If possible please fix or give any solution
Sent from my XOLO Q700i using xda premium
moinakbera said:
Everything fine except when install from sd card if many files in sd card it doesn't scroll down so i need to keep files to be flashed in folder named a...
If possible please fix or give any solution
Sent from my XOLO Q700i using xda premium
Click to expand...
Click to collapse
You Can Scroll down by Swiping your finger in Right Direction of display. It Works fine for me.
Its awsome bro ... :thumbup:
Sent from my Q700i using Tapatalk
SDShukla said:
Its awsome bro ... :thumbup:
Sent from my Q700i using Tapatalk
Click to expand...
Click to collapse
Thanks bro
Still with stock recovery
Hello. I have a ZTE Blade L2, it came with stock KitKat 4.4.2. I managed to root it, and installed busybox and mobileuncle. I did the procedure you stated but when I try to go to the Custom recovery, it enters in the stock recovery.
Any idea why?
DeviRSilva said:
Hello. I have a ZTE Blade L2, it came with stock KitKat 4.4.2. I managed to root it, and installed busybox and mobileuncle. I did the procedure you stated but when I try to go to the Custom recovery, it enters in the stock recovery.
Any idea why?
Click to expand...
Click to collapse
First, you should see that this section or thread isn't for your device. and it probably won't work on any other devices than Q700/Q700i.
Abhinav,
I'm having an issue with v2.4.
When I try to reboot or power off from recovery, it just goes back to recovery without doing anything. the only way to reboot is pull battery out.
On selecting reboot phone or any option from power menu, it gives a message which is as follows. I couldn't see this properly as the message appears just for a fraction of second.
May flash recovery on boot
This cannot be undone.
With two options which are as follows:
No.
Disable flash recovery on boot.
After this it goes back to CTR main menu. Any help here.
Install CM14 for OnePlus X (The Unofficial)
** How to Install TWRP for the 3.1.0 version you installed Oxygen.
B1: Starting Fastboot mode by turning off the power on. Then hold down + to the source.
Step 2: Install the driver and connect to the computer (HD drivers installed on the network to find it)
B3: Run cmd (run -> cmd) command fastboot boot attachments and enter this download Mod edit link removed
B4: boot into TWRP Self.
** The Stock 2.2.2 ROM you are using the network attempt to open up the OEM and then down Flashfy unbootloader install TWRP on CM ROMs directly or similar 13 and then into TWRP always offline.
** Note: Back up your data before doing us avoid errors arising restore offline.
** Download ROM CM 14: Mod edit link removed
** Link Download Grapps:Mod edit link removed
** Conducted into TWRP and wipe data, cache partitioning, Dalvik Cache. Flash ROM + Grapps and restart.
This is an experiment with me what errors arise not responsible. For those you love to dabble and discourage those you do not know and do not understand anything. People are already getting a bit bored Android does not dabble to dabble like new. : D
Path: Mod edit link removed
Vietnamses : Mod edit link removed
downloading, will report back soon.
Cam on
Thanks much
Post some screenshots.
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Well, this is interesting.. The step-by-step guide is a bit confusing though. I will download and try the 'ol good method of flashing ROM, gapps and supersu. Hope it works!
namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app
be_are said:
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
here you go: https://drive.google.com/file/d/0B_Km0FbYnea1aDdIaTEydElhUkk/view?usp=sharing
twrp has not made it to 3 ox you have to use a downgrade to get a fresh start using unbrick method, (keep flashable backup via flashify) get twrp installed with the new (old) boot loader, flash cm14+ext. and you are done.
if you had cm13 or the likes, please confirm if you CAN upgrade to 14 before ox people start trying to install without knowing if it even has android 6 (last update i saw on the branch was from june 7 so idk)
teamwin does not have twrp for the ox 3 on oneplus x yet (on their releases anyway) so you have to follow some other process to downgrade to a twrp'able os (and a backup) before trying yo install this
if i see any info from people who have been able to update (and if it has android 7) i'll try to make a video on the process (in white, Texan english)
Please remove this page.
namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.
ksigit said:
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.
Click to expand...
Click to collapse
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
namquang93 said:
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
Click to expand...
Click to collapse
Looks like a successful install to me. Could you provide twrp logs?
With whose permission did you post this build here ? Don't you think there was a reason that even after a complete build of CM14 it was still not posted to the forums ?
I am asking you, as politely as possible, to remove the links and this fake procedure, when N is ready, it will be shared, you might find phony builds or legit but non working ones on the interweebz, that doesn't mean it gives you the right to share it just because you think its cool, because its not.
Take it down.
EDIT: Sure, if you build yourself and want to share it then you're more than welcome.
And then they will cry if things are broken !! Take it down folk !
Sent from my ONE E1003 using XDA-Developers mobile app
This Build was just a test build, what made u think that i will not post it here on xda if the rom booted? We, the team are working to make it work but yeah dont post the builds from afh here, will update u all for sure when its done. I think it was my mistake to not to make that build private. -_-
It flashes successfully but doesn't boot, goes back into recovery. Still, great work.
congrats for succesfull starter build
hats off !!!!! to you guys ([/B]developers off this rom) :good:
Flashed with/without gapps. Doesn't boot - goes back 2 recovery
foster095 said:
Flashed with/without gapps. Doesn't boot - goes back 2 recovery
Click to expand...
Click to collapse
Kindly refer to the developer's post, POST #16