Hello guys,
I used the ics leaked rom for the Acer Iconia. And not i am stuck with it on my tablet.
I rooted it following a tutorial, and tried using clockworkmod but it always says "recovery verified failed" when i try to boot into recover using Volume+power.
I tried following a tutorial that i cant post the link to because of security here on the thread.
I get far enough to enter the CPUID but when i enter my Serial it is only 11 characters long when the EUU tool is asking for 16. I tried converting it to SBK but it still didnt work, just said wrong CPUID entered.
If anyone can please help me get ICS off my tablet and back to 3.2 or 3.1 i would greatly appreciate it!
coder_for_life22 said:
Hello guys,
I used the ics leaked rom for the Acer Iconia. And not i am stuck with it on my tablet.
I rooted it following a tutorial, and tried using clockworkmod but it always says "recovery verified failed" when i try to boot into recover using Volume+power.
I tried following a tutorial that i cant post the link to because of security here on the thread.
I get far enough to enter the CPUID but when i enter my Serial it is only 11 characters long when the EUU tool is asking for 16. I tried converting it to SBK but it still didnt work, just said wrong CPUID entered.
If anyone can please help me get ICS off my tablet and back to 3.2 or 3.1 i would greatly appreciate it!
Click to expand...
Click to collapse
Your UID number is not your serial number. If you had CWM installed, and a recovery backup made BEFORE you installed the leaked ICS, you should be able to find your original UID number on your Ext SD card in the Clockwork folder. Should be a file called UID.txt or similar.
At least I "assume" you made a recovery backup at one time or another.
If you don't have one, then you'll have to hopefully use ADB and push a new CWM recovery image to your tab. You can find more info on this procedure from the original developer (tegraowners)
Moscow Desire said:
Your UID number is not your serial number. If you had CWM installed, and a recovery backup made BEFORE you installed the leaked ICS, you should be able to find your original UID number on your Ext SD card in the Clockwork folder. Should be a file called UID.txt or similar.
At least I "assume" you made a recovery backup at one time or another.
If you don't have one, then you'll have to hopefully use ADB and push a new CWM recovery image to your tab. You can find more info on this procedure from the original developer (tegraowners)
Click to expand...
Click to collapse
Thanks i did make a backup but the backup i made does not contain this file for some reason it only contains 4 files that arent text files. Also how coult i push a new recovery image to my tab? at this point i will do ANYTHING to revert back to 3.2 or 3.1.
coder_for_life22 said:
Thanks i did make a backup but the backup i made does not contain this file for some reason it only contains 4 files that arent text files. Also how coult i push a new recovery image to my tab? at this point i will do ANYTHING to revert back to 3.2 or 3.1.
Click to expand...
Click to collapse
One more thing to try. Install Acer Recovery and try to install a new CWM recovery image that way.
or
With ADB;
use adb (PC):
1. adb push recovery.img /sdcard
2. adb push itsmagic /data/local
You can get the recovery image at the original Dev's website I mentioned earlier.
Or, you can use RA Recovery, which is really good!
http://forum.xda-developers.com/showthread.php?t=1459821
Sorry for the newbie question but where do i place the rocovery file and its magic file? I keep getting the "no such file or directory"
I am new to this.
coder_for_life22 said:
Sorry for the newbie question but where do i place the rocovery file and its magic file? I keep getting the "no such file or directory"
I am new to this.
Click to expand...
Click to collapse
Did you try getting Acer Recovery Installer from the Market? And try installing a fresh CWM Recovery image? That would be the first thing to do I would think.
But if it doesn't work, then you will have to do:
You have to use ADB to "push" a recovery image.
Usually this has 2 things. Android SDK, the downloading the ADB drivers. If successfully installed, and your tab shows up in PC Device manager as ADB Device, then is simple to open an ADB shell and push the image and "it's magic" (just make sure USB Debugging is enabled on your tab)
There are plenty of guides on installing SDK and ADB.Anybody who messes with custom Roms, Rooting, and expecially installing leaked beta roms, needs to familiarize themselves with ADB.
Maybe i didnt make my question clear. I have tried the Acer Recovery but when it tries to but into the recovery i get "recover verified failed". I am familiar with ADB i have it up and running. I already had the android-sdk installed from development i do.
But i was asking when pushing the "recovery where to i place the recovery?
When i use adb push recover-ra-3.16-gmn.img /sdcard i get
"cannot stat: no such file or directory"
I was asking where do i place the files at to successfully push them using adb?
coder_for_life22 said:
Maybe i didnt make my question clear. I have tried the Acer Recovery but when it tries to but into the recovery i get "recover verified failed". I am familiar with ADB i have it up and running. I already had the android-sdk installed from development i do.
But i was asking when pushing the "recovery where to i place the recovery?
When i use adb push recover-ra-3.16-gmn.img /sdcard i get
"cannot stat: no such file or directory"
I was asking where do i place the files at to successfully push them using adb?
Click to expand...
Click to collapse
Ah, misunderstood things. As far as I know, you can r try putting it in /System
From Terminal on tablet;
from terminal (TABLET): (thors CWM)
su
chmod 755 /data/local/itsmagic
mount -o rw,remount /system
rm /system/etc/install-recovery.sh
mount -o ro,remount /system
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p1
./data/local/itsmagic
Thanks! So once i push the itsmagic and RA recover to my tab what do i do next?
coder_for_life22 said:
Thanks! So once i push the itsmagic and RA recover to my tab what do i do next?
Click to expand...
Click to collapse
According to Drellisdee, these are his instructions'
Install itsmagic:
1. Copy itsmagic somewhere to /data or /cache, and set chmod 755 to it.
adb push recovery-ra-iconia-3.13-gnm.img /sdcard
adb shell
su
dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
(I never used this method, I used the flash zip version.)
---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------
Other notes from the It's Magic Thread.
Flash a custom recovery:
1. dd the new recovery to mmcblk0p1:
e.g.
Code:
dd if=/mnt/external_sd/cwm.bin of=/dev/block/mmcblk0p1
2. Call itsmagic
3. Reboot. Bootloader will do the rest
4. Boot into recovery and see if it works
5. Every time you change mmcblk0p1 or mmcblk0p2, itsmagic must be called again.
Pretty much the same as Drellisdee had.
When i try to "adb push recovery-ra-iconia-3.13-gnm.img /sdcard"
I get "File cannot be pushed: Is A Directory"
Any ideas?
coder_for_life22 said:
When i try to "adb push recovery-ra-iconia-3.13-gnm.img /sdcard"
I get "File cannot be pushed: Is A Directory"
Any ideas?
Click to expand...
Click to collapse
Not a clue.
Try posting on Drellisdee's thread for the recovery. He's usually pretty good about answering. Or send him a PM. He should be able to fix you right up
Interesting, you are not the only one to mess up the recovery with the ICS leak. Saw a couple others lately, and they were both running CWM. You might want to look in Taboonay, Lightspeed, and Flexreaper thread. I think that's where I might have seen them. At least I think.
---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------
Never mind the previous post. I found the thread.
http://forum.xda-developers.com/showthread.php?t=1552010
The guy used Acer Recovery to install the RA Recovery. CWM wouldn't install.
So try Acer Recovery, and use RA
hi guys i have been soo fustrated trying to roll my iconia back from the ics leak!
I tried to use some of the methods on a thread i posted earlier but no luck =(
I always get the error "recovery verified failed" when i try to boot into recovery mode.
Does ANYONE know anything that can fix this issue and help me rollback my tablet?
Thanks guys
coder_for_life22 said:
Hello guys,
I used the ics leaked rom for the Acer Iconia. And not i am stuck with it on my tablet.
I rooted it following a tutorial, and tried using clockworkmod but it always says "recovery verified failed" when i try to boot into recover using Volume+power.
I tried following a tutorial that i cant post the link to because of security here on the thread.
I get far enough to enter the CPUID but when i enter my Serial it is only 11 characters long when the EUU tool is asking for 16. I tried converting it to SBK but it still didnt work, just said wrong CPUID entered.
If anyone can please help me get ICS off my tablet and back to 3.2 or 3.1 i would greatly appreciate it!
Click to expand...
Click to collapse
How are you getting this serial # your using? Every method I have seen out there to roll back needs this cpuid#
Sent from my A500 using xda premium
rdnkchevy said:
How are you getting this serial # your using? Every method I have seen out there to roll back needs this cpuid#
Sent from my A500 using xda premium
Click to expand...
Click to collapse
I would suppose the "serial#" is the tabs serial number.
I know with RA recovery, the backup contains a UID.txt file. Not sure what would be in Clockwork. I don't have any to check, so not sure if clockwork keeps the UID number.
Related
Hey, I am trying to successfully get a new ROM, and in all the forums and such I have read tell me that with the Desire Z/G2 I need to flash the newest ClockWorkMod recovery. So i have downloaded a couple different recovery .img files.
Now when i use Emulator, i put in;
su
flash_image recovery /sdcard/recoveryname.img
and it says
flash_image: not found
I dont understand why ROM Manager doesnt give the newest recovery file as an option.
Can anyone help me in this situation?
Thanks
mobilemidget said:
Hey, I am trying to successfully get a new ROM, and in all the forums and such I have read tell me that with the Desire Z/G2 I need to flash the newest ClockWorkMod recovery. So i have downloaded a couple different recovery .img files.
Now when i use Emulator, i put in;
su
flash_image recovery /sdcard/recoveryname.img
and it says
flash_image: not found
I dont understand why ROM Manager doesnt give the newest recovery file as an option.
Can anyone help me in this situation?
Thanks
Click to expand...
Click to collapse
Did u delete the name on the recoveryname.img upon flashing??
Sent from my HTC Vision using XDA App
Download Root Explorer and navigate to /system/bin
Make sure /system is mounted in r/w then take this attached file, unzip it, and place it inside of /system/bin
Go back into terminal and try that command again.
ok so I installed root manager, and put the flash_image.zip in the system/bit, and tried it again with the terminal emulator, but i still have no results, it says after the pause when you plress enter after the flash_image prompt, your supposed to reboot the phone and it should start with the new recovery, but when i open ROM manager it staill shows V 2.5.... If i did somthing wrong i cant figure it out., Please help.
Thanks
http://www.youtube.com/watch?v=w4QViSam2og&feature=youtube_gdata_player
Follow these instructions. You can't go wrong. Make sure you back out of the app and go back in. It sets the cursor to the correct posistion. All you have to do is put the .img in the root of your sd. Hope this helps, it did for me.
Sent from my HTC Vision using XDA App
wait, so why aren't you just flashing the recovery through ROM manager? Are you trying to install CWR 3.0+?
yes I am trying to flash cwm 3.0, and it is not an option with ROM manager. I will try the Youtube instructions. Thanks
Ok so I tried the instructions with the Youtube video, and when i do the cmd promt in Terminal i get this;
Cant open device: "/dev/block/mmcblk0"
error in reading mbr!
failed with error: -1
I have the recovery.img file (not zip) on the sd card, I used root mamnager to put it in the bin file within system. but the instructions on the video say to use astro and it doesnt give an option to go as deep as root manager.
Thanks
Yes unzip it but make sure its in the root of your sd. That means not folders at all. That's the command that he is making in the video. I don't think you can flash cwm 3.0 in rom manager, only revert back to earlier recoveries, for froyo roms.
Sent from my HTC Vision using XDA App
Make sure the file is named what your commanding it to be. Make sure its recovery.img no caps.
Sent from my HTC Vision using XDA App
OK so I am trying this too. I am putting the recovery image directly to the root of my sd and I can see that it's there. But in TE, I put in the commands and it tells me
flash_image: not found
It's there!!!! I can see it when I have my phone connected. What am I doing wrong?
Edit: I am running stock rooted. Does this have something to do with it?
Rooted running a stock rom? Honestly I can't tell you all I know is I'm running custom rom. If I had to guess I would say it doesn't. All I can say is I had issues until I watched the video, sorry I can't help more. Only thing I would say to do is wipe everything you did and try redoing it.
Sent from my HTC Vision using XDA App
I can say you should only have one .img in your sd to not confuse it. I'm pretty sure you can use command prompt on your pc if you have access to one.
Sent from my HTC Vision using XDA App
Ok, I think I am getting somewhere, I was searching my sdcard on my computer, and I realised that the root of my sdcard is not called "sdcard" so in the command i was doing it wrong, It is called "HTC DESIRE" so i did it in Emulator and it worked i rebooted my phone in recovery and I am now rocking the new ClockworkMod Recovery 3.0.0.5...
Thanks all for the help, Hope what i discovered helps someone else.
Wait, Wait, Wait... I just screwed it up again... I went into ROM Manager after I successfully flashed 3.0.0.5. and it was not showing that in ROM Manager, so I tapped on flash latest recovery, and damnit... it replaced all my hard work with the 2.5 recovery... I have tried to repeat the flash process a few times with 3.0, and i have not been successful... Help... I dont know what to do now!!!
Instead of flashing the recovery in rom manager, after you've inputted the
su
# flash_image recovery sdcard/recovery.img
you can just type in after it
# reboot recovery
and it will reboot you into CWM 3.0. Be sure to perform a nandroid backup under 2.2 first and when you want to go back to a froyo rom, you'll have to flash the 2.5 recovery image again.
Yes, you will not see it in rom manager. Just reboot into the recovery and if you see orange and cwm 3.0 your good. Just repeat the steps.
Sent from my HTC Vision using XDA App
mobilemidget said:
Hey, I am trying to successfully get a new ROM, and in all the forums and such I have read tell me that with the Desire Z/G2 I need to flash the newest ClockWorkMod recovery. So i have downloaded a couple different recovery .img files.
Now when i use Emulator, i put in;
su
flash_image recovery /sdcard/recoveryname.img
and it says
flash_image: not found
I dont understand why ROM Manager doesnt give the newest recovery file as an option.
Can anyone help me in this situation?
Thanks
Click to expand...
Click to collapse
"flash_image: not found" means that you do not have the 'flash_image' binary installed. Follow the guide here to get 'flash_image' installed on your device (the 'flash_image' binary is attached).
As for why ROM Manager not giving the newest recovery as an option, ROM Manger isn't fully compatible with the latest recovery as it just came out. The latest recovery (I'm assuming you're referring to v3.x) is only for Gingerbread based ROM's, if you're trying to install a Froyo based ROM then you should be using recovery version 2.x.
OriginalGabriel said:
"flash_image: not found" means that you do not have the 'flash_image' binary installed. Follow the guide here to get 'flash_image' installed on your device (the 'flash_image' binary is attached).
Click to expand...
Click to collapse
I will try this tonight, thank you. I haven't run into this in any of the tutorials I've read though. I appreciate it.
Hey everyone I found a site that shows me how to flash CWM 3.0 through ROM Manager,
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
However, it is not working for me, if anyone has been successful in doing it this way please let me know cause evrything i try this i still am left with CWM 2.5. I really want to try the new Cyanagen nightly ROM, but i need to have 3.0... I had it once when i was doing it through terminal, however stupid me went back into rom manager and ruined what i did, and could not redo it... i am getting frustrated.
Please Help me.
Thanks
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
Hello Mates,
Here I am posting the Way, Methods and Files to get rid of the problem arised with the latest recovery 5.0.2.0 in Idea Blades. I have found the way to solve it out through this thread thanks to Tetora.
The error will somehow as pasted below when You boot into recovery:
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
Due to this error one can not do anything in recovery like backup, restore,wiping,flashing roms , etc. and which is very annoying. This happens because the CWM reject or failed to identify the root access of the device.
Even I have a headache on my birthday due to the problem. I have followed that thread (post above) posted by tetora and sorten out the problem.
Now I can flash, backup, restore and can do anything with the recovery
There are two methods to get the recovery Working:
1 . Through ADB
Attached is the file to flash via adb.. Please follow the steps given below (thanks to matt4321) :
The 'flash_image' is within the attached zip file! Use the file within the zip file, NOT the zip file itself
The 'recovery.img' is your chosen recovery file, get this off ClockworkMods website or if you have a copy use that. Then when flashing the recovery image where ever it says 'recovery.img' replace that with the name of the recovery file. following me?
Here's the instructions:
(make sure you're in the command prompt and have changed directory to where the adb file is)
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
and then boot into recovery now everything should work perfectly.
A big thanks to tetora for finding the recovery image file and matt4321 for his commands
2. Through Recovery Manager:
Install the application Recovery Manager v0.37b.apk
Extract the image file from recovery zip and place in the SD card.
Open the application "Recovery Manager"
Go in recovery Tab to flash the recovery img. Once you select to "Flash Recovery" it will search the img file automatically.
After flashing recovery you are done.
Thanks to ramubhat for providing procedure and testing the same.
You can use this link for the second method.
Disclaimer- I will not responsible for any damage so use it at your risk
Don't worry there is no other options left apart from it and its 99% safe.
Can confirm this works, I've done it loads of times!
PS: thanks for the thanks
Will add this in the sticky guide.
Sent from my LT26i using xda premium
karthiknr said:
Will add this in the sticky guide.
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
My pleasure...
But the thing is that no body came to use and find this useful till the time.
hi, i will try.
Can i flash this recovery img using recovery manager apk
ramubhat said:
hi, i will try.
Can i flash this recovery img using recovery manager apk
Click to expand...
Click to collapse
I didnt try with that...but I will strongly recommend the steps given in the OP because I have self tested the same on my device...
hi, r u still online?
Do u have fast boot drivers for idea blade?
Do i need fastboot to flash recovery?
ramubhat said:
hi, r u still online?
Do u have fast boot drivers for idea blade?
Do i need fastboot to flash recovery?
Click to expand...
Click to collapse
In some cases fastboot won't work.. try to use ADB its very easy to push the files with the steps given in OP by matt4321
Hi Shiv
Thank You,
The recovery img worked.I flashed it using 'recovery manager.apk'
Don't need adb to flash, works fine with recovery manager. Thank you again.
I will be in touch
ramubhat said:
Hi Shiv
Thank You,
The recovery img worked.I flashed it using 'recovery manager.apk'
Don't need adb to flash, works fine with recovery manager. Thank you again.
I will be in touch
Click to expand...
Click to collapse
Great to know that Apk recovery work..Could you please upload the APK file.. So that I can update this process in OP.
hi Shiv
I have created a zip 'Idea Zte blade pack' pls use it in u r post
https://www.dropbox.com/s/k9sbpa73oostqrk/Idea Zte blade pack.rar
ramubhat said:
hi Shiv
I have created a zip 'Idea Zte blade pack' pls use it in u r post
https://www.dropbox.com/s/k9sbpa73oostqrk/Idea Zte blade pack.rar
Click to expand...
Click to collapse
OP updated with the new method.
Sir please help
zte blade s. Android 2.3.5. French
I install z4root, when choose permanent root, written down aquiring then i dont know nothing happen.
I install recoverymanager when i launch it, Force close.
Then I :crying:
i have already down, all sdk file,
I dont know how to adb, and fastboot, i have all the files.
DOnt know what to do sir. please help step by step. :crying:
beautyangel said:
zte blade s. Android 2.3.5. French
I install z4root, when choose permanent root, written down aquiring then i dont know nothing happen.
I install recoverymanager when i launch it, Force close.
Then I :crying:
i have already down, all sdk file,
I dont know how to adb, and fastboot, i have all the files.
DOnt know what to do sir. please help step by step. :crying:
Click to expand...
Click to collapse
which z4root u used? normal z4root wont work on blade ,,.....use z4root from this link....
and tell me what happened
https://www.dropbox.com/s/k9sbpa73oostqrk/Idea Zte blade pack.rar
ramubhat sir
I use the one on your dropbox, z4root_idea blade_perm_root_v2
im doing permanent root running exploit in order to obtain root access, aquiring root shell, then i dont even know if im rooted or not.
after install recovery manager 0.37, when launch it got FC processus com.podtwo.recoverymanager
beautyangel said:
ramubhat sir
I use the one on your dropbox, z4root_idea blade_perm_root_v2
im doing permanent root running exploit in order to obtain root access, aquiring root shell, then i dont even know if im rooted or not.
after install recovery manager 0.37, when launch it got FC processus com.podtwo.recoverymanager
Click to expand...
Click to collapse
If you have used Z4root v2 (modded one) than it will aquire root in your cell. However if you are not sure then you can download the application "root check basic" from playstore to check whether you are rooted or not.
hmmmm does the issue mentioned in first post occur after sometime as I have the mentioned recovery flashed already on my Blade and so far never had an issue!!
Now what would be good is a touch version of the recovery being available for the Blade!
lohtse said:
hmmmm does the issue mentioned in first post occur after sometime as I have the mentioned recovery flashed already on my Blade and so far never had an issue!!
Now what would be good is a touch version of the recovery being available for the Blade!
Click to expand...
Click to collapse
Does your blade is a chinese variant? However this problem is not arising with every chinese blades. Ya touch recovery will be the best to see..But dont know it will work perfectly on chinese blades
Shiv Prajapati said:
Does your blade is a chinese variant? However this problem is not arising with every chinese blades. Ya touch recovery will be the best to see..But dont know it will work perfectly on chinese blades
Click to expand...
Click to collapse
Nope it's a UK ZTE Blade(san francisco)
I came across this thread somedays ago to help one of my friend.
should u guys need to build a touch recovery, u can build it yourself from here.
http://builder.clockworkmod.com/
just put the stock or any other custom recovery image and build a touch recovery.
Although its written that the touch recovery works only on ICS kernel but I used it even on Froyo and GB kernel.
warning: do it at ur own risk
cheers
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice
if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab
I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?
It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.
prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop
Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.
JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app
mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack
I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]
JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack
simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...
Hello,
I plan to install a custom rom, and for that I followed all the tutorials on the web without success.
Using Acer recovery install, whatever the chosen recovery I get the error "recovery verified failed", and flashing the stock 4.03 recovery I have bugdroid lying.
Using AfterOta, it freezes at step 3/5 and Blackthund3r, it stuck stage two..
I have a bootloader and ICS 4.0.3 OTA maj.
If someone has an idea, I'd be grateful
Thanks !
babysugar said:
Hello,
I plan to install a custom rom, and for that I followed all the tutorials on the web without success.
Using Acer recovery install, whatever the chosen recovery I get the error "recovery verified failed", and flashing the stock 4.03 recovery I have bugdroid lying.
Using AfterOta, it freezes at step 3/5 and Blackthund3r, it stuck stage two..
I have a bootloader and ICS 4.0.3 OTA maj.
If someone has an idea, I'd be grateful
Thanks !
Click to expand...
Click to collapse
Rooted?
Yes? use AcerRI to install any recovery.
Download thor200240/digetx CWM 1.7.3.zip here
Copy zip to SD card
Reboot to recover.
Install from zip file > Choose file from SD Card
Select the zip and install.
Reboot to recover if u see CWM 1.7.3 ur set.
Full Backup
Save your cpuid (In your CWM folder on your sd card inside the backup files u just made. Should be a text file named uid.txt or cpuid.txt.)
Copy any compatible rom onto your SD card
Wipe data, cache and dalvik
Flash your rom the same way u installed the .zip file.
Thank you for your response.
Yes, I'm rooted and I already tried Acer Recovery Install without success...
I get "recovery verified failed" (in red)...
tried all the recoveries in ARI?
use adb to install the zip then.
shadowmikeshadow said:
tried all the recoveries in ARI?
use adb to install the zip then.
Click to expand...
Click to collapse
I tried all the recovery... And I don't know how to use adb :s can you quickly explain ?
use the platformer tool link below to use adb so u dont need sdk.
Follow instructions on platformer tool download page to set up your adb
open command prompt and navigate to your platformer
cmd commands:
view available directories: dir
change directory: cd (cd desktop (forward directory example) / cd .. (up directory example))
Use this guide to install with adb
cwm: here
platformer: here
Ok, I'll try later because I can't now and I tell you !
Thanks !!
make sure your rooted too, that could be causing the issue with ari..
download root checker from play store its free
shadowmikeshadow said:
make sure your rooted too, that could be causing the issue with ari..
download root checker from play store its free
Click to expand...
Click to collapse
I already checked, I'm rooted
Having the same issue.
I will also look into adb tool because I'm in the same boat. I did pretty much the same thing and am also stuck with the same error message and can't access the Recovery mode.
shadowmikeshadow said:
make sure your rooted too, that could be causing the issue with ari..
download root checker from play store its free
Click to expand...
Click to collapse
I don't understand.
I put the recovery on sdcard with adb, and next ? How should I install it ?
Follow this guide here
but use the recovery from the zip in earlier post.