Database Users

Flashing new recovery isnt working.

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

[GUIDE] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).

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)

Root Obtained **EASY!**: T-Mobile G2 2.3.4 official OTA manual update

For those of you wondering why the S-OFF feature was worth your extra time to update, this is a prime example of why S-OFF kicks royal behind.
So here is the situation I was having. Friday morning, T-Mo showed me some love and sent me the Gingerbread update. I didn't have my morning coffee so I wasn't thinking strait and authorized the update. I forgot that it would probably interfere with good ol' ClockworkMod Recovery. Sure enough, it did. So, after the OTA failed due to the recovery, I haven't been able to get T-Mo to show me some OTA love again.
However, I had previously invoked the S-OFF feature when it was discovered how to.
After following the guide at http://forum.xda-developers.com/showthread.php?t=1202060 I found myself with a G2 using stock recovery and bone stock Gingerbread (S-OFF still invoked).
After some thought, I decided to do the following:
Flash ClockworkMod via the bootloader screen, and flash SU via the ClockworkMod screen.
Note: You can only do this if you have S-OFF! And since my guide writing skills are not so pristine, I'm assuming you have some sort of working adb/bootloader/recovery knowledge.
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.

Thanks!
It sounds like you started where I am: Clockwork Mod, S-OFF and stock Froyo 2.2.
Q. How did you follow the steps in the thread to get onto Gingerbread? Did you remove ClockworkMod? If yes, how did you revert to stock recovery? This is the step that I'm caught on, and can't find a thread regarding. Thanks!
Edit to add:
Did you unroot the phone using these steps?
If so, were you at all scared about the warning regarding PC10IMG.zip?

I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk

rdmerck said:
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Okay, so just to verify, you flashed CWM recovery while running the GB update? When you adb shell you open a # prompt? I've been gfree s-off'd since I got my phone so even with the leak or otherwise I've been able to just reflash the stock 1.19/1.22OTA and reroot it but I didn't think to try flashing cwm while it's stock gb'd....so tempted.

I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
So I sit down to write up a quick guide this morning and what do I find? Nicely done. Couple of points I wanted to add to why this works -
This method fixes the things that the OTA breaks for root: New stock hboot and stock recovery are flashed and on the rom side it wipes /system/xbin which breaks the su symlink.
Flashing the PC10IMG above fixes the recovery.
Flashing the superuser package reinstalls Superuser.apk, the su binary and fixes the symlink to xbin.
But, still not hboot-eng so your fastboot options are limited.
When I did this I had replaced the DZ engineering hboot.img in rmk's package with the G2 engineering hboot.img and edited android.txt for the new G2 build. This allows you to take care of both in once flash.
Hope this is useful to someone and thank you for saving me from writing a guide!
8/27/2011 Edit:
Realized ro.secure=0 so I repacked the stock boot.img from the 2.3.4 PC10IMG.zip with the below changes to default.prop. This allows use of the "adb remount" so files can be pushed to system folders without needing to go into terminal and mounting rw.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Modified installation instructions for full root:
Flash the PC10IMG.zip with the G2 engineering bootloader in this post
Flash the superuser update.zip in the OP
Extract the attached boot.img to the platform-tools directory
Remove the PC10IMG from your sdcard and reboot into bootloader
Select fastboot
Enter the following command in terminal or cmd:
Code:
fastboot flash boot boot.img
fastboot reboot
Kind Regards,
Kevin

zkid2010 said:
Okay, so just to verify, you flashed CWM recovery while running the GB update?
Click to expand...
Click to collapse
Yes. Just flash the PC10IMG and you have clockwork recovery again. However, you absolutely need SuperCID set while in froyo or this does not work.
Kind Regards,
Kevin

Confirm Here that it works...
Root and S-OFF
Gingerbread OTA 2.3.4
Thanks Guys for your help!

Flawless!
This worked flawlessly!!
I admire you so much for figuring this out!!
Thank you so much!

HELP!
sort of noobie here..
so i just updated my g2 to 2.3.4 following http://forum.xda-developers.com/showthread.php?t=1202060
and now i want to perm root my phone and overclock it but im having troubles.
1. how do i get clockworkmod installed? i know you can install this from rom manager but it requires root. right?
cause you said.. "Just flash the PC10IMG and you have clockwork recovery again"..
i tried flashing the PC10IMG.zip but got an error and says aborted.
any help please?
thanks in advance

If you are already on 2.3.4 and had not previously rooted then this thread will be of no use to you since your G2 does not have SuperCID (again, read the wiki.)
You will need to downgrade back to froyo (other threads on this and links in the wiki.) Once rooted, then install one of the rooted stock roms in this forum or follow this guide to reinstall the recovery and superuser (hboot optional.)
Hope that gets you going in the right direction.
Kind Regards,
Kevin
Sent from my T-Mobile G2 using Tapatalk

G2 Problems??
Hi, how can i get S-OFF on my g2 since it seems i can not generate a beta key from the revolutionary website cause g2 it's not in the drop down list, don't know what to pick and i want to be able to have my g2 rooted with android 2.3.. can somebody help me please?
Thanks.

Revolutionary is not available for the Desire Z/G2. Have you flashed the leaked 2.3.3 and trying to root? PM please.

Hey I notice most of the people in this thread are Americans - would this method work for the DZ or is it just for the G2?
Sorry if this is a noobish question.

Not a noob question, this one is new for me too. Fundementals are the same, process would be the same. I don't know if there is any issue using a PC10IMG with the info for a G2 (contained in the file called android-info) so may need rebuild one modified with DZ information.
Proceed with caution and do not do anything you are not 100% sure about.
Sent from my T-Mobile G2 using Tapatalk

I'll hold off on confirming the update in that case! I'm still on stock firmware, didn't apply the update from March either. When I've read enough to be confident on how to perma-root the current firmware I might risk following the method in this thread. Then I'll post back to let you know if it works on the DZ.

My DZ came with 1.34 firmware, I rooted it on this firmware. I accidentally upgraded it and am now on the OTA gingerbread ROM. Is this method suitable in this situation or do I require to flash a rooted stock ROM for this method to work.

Accidentally manually applied the OTA? Should work, you have a G2 now!
Sent from my HTC ThunderBolt using Tapatalk

Is there any newbie guide for how to do this? From getting Clockwork on there to getting this rooted 2.3.4 on. I have a rooted 2.2 with S-OFF right now, stock. Just don't really know what to do from this point on.

How to is in the OTA thread (which needs a helping of Iron Fist.) Come back here when ready to re-root.
Sent from my T-Mobile G2 using Tapatalk

rdmerck said:
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
**** Im at the step above finally lol this is my first root and I had to downgrade, man Ive been doing this for hours and hours. My brain is fried LMAO **** I currently have my G2 with S-OFF and a stock Gingerbread 2.3.4. I have the PC10IMG.zip and su.zip in the root or directly in my sdcard. In no folders im trying to say... I reboot into the bootloader. The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
Well when I do it it doesnt ask me to "flash the recovery" it says "Parsing....(SD ZIP)
(1) RECOVERY
Do you want to start the update?
<VOL UP> YES
<VOL DOWN> NO
I accept the update by pressing vol. up. It comes back and says Update comeplete... - OK
Press Power to Reboot
I reboot and get into clockworkmod it says click "install zip from sdcard" I click it and a little hat appears but it doesnt do anything from there. I let it set a couple of min but still nothing... I have to pull battery out to get it to reboot. help pls....
Sean...

Some things you should know about rooting and flashing ClockworkMod recovery

I had some problems with rooting and flashing ClockworkMod, and when I solved it, sunitknandi asked me if I could post info which some people may find it useful, so here it is.
sunitknandi said:
Things to know while rooting stock ROM:
1. HTC Tattoo is HTC's first NAND locked device preventing users to write to system and recovery under normal conditions.
2. This NAND lock can be defeated by inserting tattoo_hack.ko module. This module was created on taking the help of info from a leaked QualComm datasheet.
3. The module needs to be inserted prior to writing to system or flashing recovery.
4. The manual rooting method and Maveric/NTenisOT 1-click method flashes a custom boot.img after rooting so that the NAND remains unlocked everytime the device is used. On the other hand, Universal Androot unlocks the NAND temporarily while rooting and unrooting. If Androot is used, the device gets permanently rooted, but the NAND locks itself after a reboot, until Androot is used again or tattoo_hack is inserted.
5. Custom 1.6, 2.1, 2.2 roms have tattoo_hack added to their modules list to keep NAND unlocked while device is running. On 2.3, however, the unlock code is compiled into the kernel, so the module is not needed.
6. We deal with this module because no one has developed S-OFF for the Tattoo.
7. Most users forget about this module once their Tattoo is rooted. New users oversee this module and run into problems. The CyanogenMod wiki is misleading in 'How to root Tattoo' because of this.
Click to expand...
Click to collapse
Next post solved my problem. I had 1.6 stock ROM with original recovery, and I just could’t install ClockworkMod recovery via ROM Manager. For rooting I used Universal Androot application (Download link in attachment below).
sunitknandi said:
Go to universal androot. Hit root again. Let it complete.
Then use Root Explorer and mount /system as rw. Or u ca also use Terminal Emulator. Just type these.
su
mount -o remount rw /system
Close terminal.
Go to ROM Manager. Tap Flash ClockWorkMod recovery. First it will take time. Let it successfully flash. Tap again. Let it flash. Tap again. Let it flash.
I am telling you to tap this many times. Because CWM 5.0.2.0 doesnt flash easily. I got so many failed flashes even on CM7. It only gets flashed after a couple of time.
Otherwise, hit menu button on ROM Manager, slect settings and check mark 'Erase recovery before flashing'. Go back and flash recovery twice.
Finally reboot manually. No need to use ROMManager's reboot option. I read that it works rather badly on Android 1.x. Boot with HOME+POWER.
Lemme know.
Btw, the safest method to flash recovery is NTenis's tool. Used it many times without problems because it flashes the boot to disable the write-protection.
Click to expand...
Click to collapse
Thanks again, sunitknandi.

Thanks bro.
Universal Androot users, always remember to re-root and mount ur /system as rw before flashing recovery from ROM Manager if u r using stock ROM. Thats what u need to do in short.
Hope this helps many people, as I know there are guys around who do not like to use a PC to root their Tattoo.

[Q] how to root Nexus 10 (upgraded to Kit Kat 4.4)

Newbie here.
Pls guide me..
Many tks!
Sent from my SM-N9005 using xda app-developers app

Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord

Issues with rooting (4.4), stuck after flashing recovery
I just got my Nexus 10, and unlocked the boot loader, then flashed the custom recovery. All was fine, and I could boot into recovery, however recovery can not mount any filesystems. So I rebooted, now the Nexus does not boot, but hangs on the intro animation, normally meaning in my experience that the kernel is looped and is no longer finding (or else) booting the OS. I've tried booting 3 times.
So then, the steps I took,
enable USB debugging
were copy over the zip file for supersu
reboot to (fastboot mode), verify device
unlock boot loader "fastboot oem unlock"
flash the recovery "recovery-clockwork-touch-6.0.4.3-manta"
reboot into recovery
Failed to mount filesystems
for instance "E: Can't mount /cache/recovery/command or E:Can't mount /sdcard .... (you get the idea).
rebooting again a leaving it does nothing.
I also tried side loading a new image in my case "ThunderKat_manta-KRT16S-20131201" and after installing the "UniversalAdbDriverSetup", I was able to do so, I also was also able to side load the google apps "GoogleAppsPack-4.4-20131128", in both cases I get a success message after the install, however there after when I attempt to reboot I'm still stuck looking at the boot animation.
Now I'm really confused as if if the OS was destroyed when I unlocked the device, then side load of the zip contains a new kernel and OS image so it should be working, but it is not. In fact, recovery while still working throws the same can not mount exceptions after the flash as it did before (I rebooted) as I was previously getting and a factory reset, fails to mount /data, but does flash /cache and sd-ext without issues, so again I'm lost as to what to do.
Best guess I have is that partitions such as /data are just missing, I have no idea the state of teh device in such a case, but recovery and side loading using adb are working, how do I recover a working ANDROID OS from here?
Thanks,
ERIC

stuck in loading screen
Hi,
i just got my Nexus 10 yesterday. I tried to root it, but it is stuck in the loading screen. What can i do now? Can i like undo it to get it back to work?
I have the same issue egandt described.
Edit: I just got it back with this tutorial to android 4.2.2 and now i am updating it back up
nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/

I unlocked nexus10,
Flashed cwm,
Installed su, but whn i turned it on, su not found, rootchecker shows no root access..
I also encounter bootloop initially,
Need to wide data / factory reset then its normally booted..
Sent from my SM-N9005 using xda app-developers app

Agreed the factory reset was required to fix the issues I encountered, then installing super-su worked.

I still cannot root the Nexus10..
Any one can help?
Thanks in advance!

XxLordxX said:
Hi!
You can easily boot a custom recovery and then install the SuperSU.zip from there .
1 - Download the SuperSU zip from here: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip.
2 - Copy it to your Nexus 10 root folder (the one where it's located Download, DCIM, Android, etc)
3 - Download the .img file from here: http://www.teamw.in/project/twrp2/128, then rename it to recovery.img
4 - Copy it to your fastboot/adb folder (if you doesn't have one search for how to get it)
5 - Plug your Nexus 10 in your PC
6 - Turn USB Debugging on (Settings --> About Tablet --> Press many times Build Number --> Developer Options --> On --> USB Debugging)
7 - Open a cmd in your PC and go to your adb/fastboot folder, then type:
Code:
adb reboot bootloader
(When the screen turns on you type) fastboot boot recovery.img
Wait for it to turn on and then click install, select the SuperSU.zip and then confirm. Then it's done . If you can't get this way working you can try one of the many tools in the Development thread. I'm sure one will work with you .
~Lord
Click to expand...
Click to collapse
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!

xing369 said:
Many thanks for the detailed explanation, bro!
Still got following questions:
So do I need to enable "USB Debugging" 1st before unlocking Bootloader?
Although I successfully installed SuperSU, but still lack of SU power, those apps required SU access are not working at all.
the kitkat poisons me... sigh...
Thanks again!
Click to expand...
Click to collapse
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .

shimp208 said:
If you are going to follow the commands he listed in step 7 then yes you need to enable "USB Debugging" before you go ahead and unlock the Bootloader. Installing SuperSU alone will not give you root access, you need to flash the SuperSU .zip file in recovery as the end of step 7 mentions to properly gain root access. If your still confused about anything or have any questions let me know I'll be happy to help you .
Click to expand...
Click to collapse
Thanks for your kind offering of hands!
Last night I tried again to re-flashed latest TWRP as well as latest SuperSU.
I ran 2x Root Checker,
1 said rooted,
1 said no root access, no BusyBox available.
I tried some apps like GMD Gesture, no working or no root access.
So,
Should I redo everything: enable USB Debugging then unlock bootloader then flash CWM then install SuperSU?
I initially gone thru above steps w/o enabling USB Debug..
Many thanks!
Sent from my SM-N9005 using xda app-developers app

Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS

xing369 said:
Now Nexus10 stuck at boot animation.
Did several data wipe / factory reset, not working...
SOS
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.

fritzhy said:
https://developers.google.com/android/nexus/images
Download the appropriate factory image, extract it, boot to bootloader and flash everything using fastboot commands/execute the .bat file IF you're running Windows on your computer.
Click to expand...
Click to collapse
Very much appreciated for reviving my nexus!
However, after flashing latest TWRP, and installed SuperSU 1.80,
It seems my nexus still unrooted.
Any ideas?
Thanks!
Sent from my SM-N9005 using xda app-developers app

Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk

fritzhy said:
Do you have SuperSU in your app drawer? If so, open it and see if you have to update the SU binaries. If not, try flashing the SuperSU zip again.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app

xing369 said:
Thanks for replying!
Yes, got SuperSU app in drawer..
But a silly question: How to update SU binaries?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
If it's needed the app will say so when you open it.

fritzhy said:
If it's needed the app will say so when you open it.
Click to expand...
Click to collapse
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app

xing369 said:
Sigh..
Seems still 'unrooted'.
Any other ways to get it done?
Thanks!
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Not that I can think of, nope...