I am having an issue with cwm. when I go into rom manager i was able to succesfully flash it to my phone. Now when i reboot into recovery I get the android guy with a red exclamation point. sometimes I can get in but I cant reboot my phone from the menu and have to do a battery pull. I am able to flash .zip's and update the bootanimation for example if i get in. When I reboot from rom manager I get some error message that is stopped working before it reboots and again sometimes it works sometimes it doesnt.
should I push the recovery through the sdk again?
Yes, you should. I read that sometimes CWM won't stick if applied through ROM Manager.
There is a file on the nexus s and i believe the Gnex as well that will rewrite the stock recovery after a reboot. unless you change this file you have to flash the recovery every time you want to go into it. use a file manager and search for install-recovery i believe its install-recovery.sh and rename it to install-recovery.sh.bak ( or wtv ) may solve it.
I just did a quick search in root explorer and found a file called "install-recovery.sh"
it should be in the root folder/etc/install-recovery.sh
and i just tried going into CWM and got the same thing as the OP. I am going to rename the "Install-recovery.sh" file like Goat_For_sale suggested, then reinstall CWM and see what happens after a few reboots.
Standby.
*final* edit
So here is what I did.
1.renamed "install-recovery.sh" to "install-recovery.sh.bak" (located in the "etc" folder of the root) I used root explorer. Make sure you mount as writeable or else you cant change the file name.
2. rebooted phone as normal. went into Rom Manager and reinstalled CWM.
3. turned phone off, and booted into recovery and boom! CWM came up nicely.
Glad I found this thread, or I would have been annoyed when I go to flash a rom tonight and couldnt figure out why I wasnt able to get into CWM.
Good luck OP.
I hope you were able to resolve this issue. I was having the exact same issue and i followed the instructions in this thread and it corrected it and i havent had a problem since.
http://forum.xda-developers.com/showthread.php?t=1392336
Now cwm seems to be working but when I hit to boot into recovery from rom manger it says that something has stopped working unexpectally but it seems to boot into recovery just fine.
If you follow the steps on the link that i posted, and make sure that you follow the step of deleting the file with Root Manager once you have moutned as RW then that should get you working. If you are still having issues with I would be happy to walk you through the process tonight over google talk once i get off of work.
Thanks Angelino I will try that today. I just havent deleted that file yet. Now since im rooted and already flashed cwm, i should just go into root manager delete the file and then do the fastboot and flash the recovery again?
TSanborn79 said:
Thanks Angelino I will try that today. I just havent deleted that file yet. Now since im rooted and already flashed cwm, i should just go into root manager delete the file and then do the fastboot and flash the recovery again?
Click to expand...
Click to collapse
dude try my method, it was super easy, and doesnt require deleting anything, just renaming that file.
threepio said:
dude try my method, it was super easy, and doesnt require deleting anything, just renaming that file.
Click to expand...
Click to collapse
I did try your method but it only partially works. I still get an error when trying to boot from rom manager.
It actually says superuser has stop working. Finally was able to read it.
I am having issues with my gnex and recovery. I am rooted and can run clockwork when I boot from the app. However when I run root explorer i can find any of the recovery files to delete or rename. They arent showing up in system or etc but when i restart my phone stock recovery is still there... ideas?
TSanborn79 said:
I did try your method but it only partially works. I still get an error when trying to boot from rom manager.
Click to expand...
Click to collapse
wierd. I havent had a problem yet. Hope u get it figured out.
Related
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
djtoonjr said:
i rooted my sisters white Evo yesterday.i followed up on Hboot 2.02 S-Off Like a Boss! guide, and it worked and everything. it flashed Stock 2.2 Rooted and i followed up on updating PRL/Profile and what not, but i was still in the process of picking a rom for her. i tried to enable wifi, wasnt working, 4G, wasnt working either. i was like wtf? then i got an update for 3.30 somehow and it was like 6mbs. my dumbass installed it, got wifi and eveyrthing to work, but! i lost my recovery and hboot aint pikcking up any PC36IMG file either.
Click to expand...
Click to collapse
Have you tried using Rom Manager to install a recovery?
xNotta said:
Have you tried using Rom Manager to install a recovery?
Click to expand...
Click to collapse
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
djtoonjr said:
i run rom Manager and get the following screen.
First Screen:
you must root your phone for ROM Manager to function Superuser was not found at "/system/bin/su" or system/xbin/su". Use google search on your computer to find instructions to root your phone.
superuser from the market is installed...
Then i go and click Flash Alternate Recovery(RA Recovery v1.8.0) and it force closes.
Then i try to flash clockwork and it takes a long time too and i get a message An error occured while attempting to run privileged commands.
Click to expand...
Click to collapse
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Click to expand...
Click to collapse
i cant get to recovery lol
i go to the bootloader, scans for a PC36IMG file but it donesnt find it, even tho the file is there! lol. maybe i shold format my sdcard. hmm.
but i scroll down to recovery, and it senss me to the default recovery, not clockwork or amen ra. the stock htc recovery. lol.
xNotta said:
You seem to not have SuperUser installed as a system app.
Go here: http://forum.xda-developers.com/showthread.php?t=682828
Download the correct version and flash it in recovery.
It should fix superuser.
Scratch that, I just noticed you don't have a recovery to flash from. :-/
Is your HBoot S-Off?
Click to expand...
Click to collapse
lmfao. yeah i have S-off.
drmacinyasha said:
If the phone downloaded the OTA update for 3.30, as your first post suggests, then it became unrooted and you'll have to root it again.
Click to expand...
Click to collapse
ive been trying dat but when it comes to the part to flash the first PC36IMG, it doesnt find it, i formatted my sdcard and trying it again.
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
xNotta said:
I am really failing at reading tonight, lol.
Can you boot into the bootloader and use ADB?
Could try ADB Push-ing the files extracted from the Superuser's flashable .zip to their respective locations.
Not sure how that would work out though, never tried it.
Get files "su" from su-2.3.6.1-ef-signed.zip\system\bin
and "Superuser.apk" from su-2.3.6.1-ef-signed.zip\system\app
put both files in the folder with ADB.
open adb command prompt and
Code:
ADB push Superuser.apk /system/app (Press Enter)
ADB push su /system/bin (Press Enter)
Then reboot back into the rom.
You might need to use a file explorer to navigate to /system/app and click Superuser.apk to install it.
(Uninstall old SuperUser from the market before installing.)
Worth a try if no one else has any fixes.
Click to expand...
Click to collapse
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
djtoonjr said:
OMG! ORGASM! lolwell i didnt try ur method YET, but i formatted sdcard, and it picked up the PC36IMG file. so im re-rooting it against, hopefully trying to re-root it wont fk things up u know. will post bak on progress. thanks alot tho man. i know the last couple of times, couldnt get anyone to help me out lol
Click to expand...
Click to collapse
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
t3project said:
if you are s-off all you have to do is flash a rooted pc36img in bootloader and then flash a recovery. no need for the entire process again.
Click to expand...
Click to collapse
lmfao. damn. now u tell me haha.
well i went ahead and re-rooted and got it woking now but thxs for the help.
if PC36IMG isnt getting picked up by boot loader, just format SDCARD and run it again lol
im seeing an android with an exclamation point! when i go into recovery. this wasnt happeneing yesterday. what happened?
qman66 said:
im seeing an android with an exclamation point! when i go into recovery. this wasnt happeneing yesterday. what happened?
Click to expand...
Click to collapse
What did you use to install it? When I first tried to flash it with ROM Manager CWM would dissapear every reboot or 2. I then downloaded the CWM recovery image and flashed it with fastboot and it has been perfect since. (theres literally no use for ROM Manager and it causes alot of problems for people in general)
sluflyer06 said:
What did you use to install it? When I first tried to flash it with ROM Manager CWM would dissapear every reboot or 2. I then downloaded the CWM recovery image and flashed it with fastboot and it has been perfect since. (theres literally no use for ROM Manager and it causes alot of problems for people in general)
Click to expand...
Click to collapse
first i flashed it with adb then i heard it was good to use rom manager to re flash it.
Did you delete /system/recovery-from-boot.p? Each time you reboot the system, Android overwrites the recovery if this file exists. Reflash clockworkmod and delete the file using adb shell or root explorer..
madj42 said:
Did you delete /system/recovery-from-boot.p? Each time you reboot the system, Android overwrites the recovery if this file exists. Reflash clockworkmod and delete the file using adb shell or root explorer..
Click to expand...
Click to collapse
perfect thanks. its working
Good Morning XDA!!!
I went through the Odin Rooting process last night and everything went as planned. I downloaded CWM Manager through Google Play and when I go to open it up it is telling me that the Super User file is not there. I have put Super USer on my phone but again it tells me I need to root my phone. I will admit I am a bit confused, I can boot into CWM mode but since I am not flashing a new rom at the moment I don't know what I did wrong. I did go into the CWM manager to "Flash ClockworkMod Rocovery" but it downloads then tells me there was na error with command lines..........Is there anyone who can help me out.....I really don't get where I went wrong, cause everything says I rooted the phone.....Thanks for any help......
>'.'<
How did you root? Do you have superuser or supersu installed?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
nicky9door said:
How did you root? Do you have superuser or supersu installed?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes I did but it also was telling me that it wasn't rooted.....however the only thing that I had was the Superuser App. Is there something i need on the SD card? Or to psychically flash to the phone.....thanks for getting back to me with this....
Go into Settings>Apps>Superuser and clear cache and data. Go into the market and go to SuperUser and see if there is an update. This should update the binaries. Then try a Root App to see if you get the SU toast.
2nd option is to boot into recovery and go to wipe /Cache then advanced and wipe /Dalvik-Cache. While in Advanced, hit Fix Permissions and let it run. Reboot and try a Root App.
Btw, you never said how you rooted. Your title says Odin, so I am assuming mrRobinson's method.
Woodrube said:
Go into Settings>Apps>Superuser and clear cache and data. Go into the market and go to SuperUser and see if there is an update. This should update the binaries. Then try a Root App to see if you get the SU toast.
2nd option is to boot into recovery and go to wipe /Cache then advanced and wipe /Dalvik-Cache. While in Advanced, hit Fix Permissions and let it run. Reboot and try a Root App.
Btw, you never said how you rooted. Your title says Odin, so I am assuming mrRobinson's method.
Click to expand...
Click to collapse
Sorry about that......I used the method from this site....http://www.androidauthority.com/galaxy-s3-sgh-t999-t-mobile-easy-root-99302/
It did everything that was explained was supposed to happen.....its just I get the feeling I missed something somewhere.....I hope this helps....I haven't rooted anything in years.....lol
Ok, so you downloaded ROM manger from the market and tried to run the recovery script and it is saying that you don't have Root correct?
I agree, I think that you did miss a step somewhere. I suspect it was in between the CWR and SuperUser zips.
Are you familiar with Odin? I assume so since your first post said you Odin'd, but just double checking. I suggest you either start over from the link you posted or try mrRobinson's method. It is real easy and gives you stock ROM, rooted and has the option to install a custom recovery (like CWR or TWRP) also.
Here are Odin versions of both CWR and TWRP. Do this after you've done mrRobinson's method. Once it is done with first reboot (don't forget this take the longest time to boot bc it is rebuilding the /Dalvik), reboot back into download mode and flash either CWR or TWRP that way and you should be good to go after that.
Woodrube said:
Ok, so you downloaded ROM manger from the market and tried to run the recovery script and it is saying that you don't have Root correct?
I agree, I think that you did miss a step somewhere. I suspect it was in between the CWR and SuperUser zips.
Are you familiar with Odin? I assume so since your first post said you Odin'd, but just double checking. I suggest you either start over from the link you posted or try mrRobinson's method. It is real easy and gives you stock ROM, rooted and has the option to install a custom recovery (like CWR or TWRP) also.
Here are Odin versions of both CWR and TWRP. Do this after you've done mrRobinson's method. Once it is done with first reboot (don't forget this take the longest time to boot bc it is rebuilding the /Dalvik), reboot back into download mode and flash either CWR or TWRP that way and you should be good to go after that.
Click to expand...
Click to collapse
The last phone I rooted was a Mytouch 4G. I am not familiar with Odin. I just went to the site that I posted in my last reply and followed the directions exactly. I only downloaded the IMG file for ClockworkMod that it supplied. It never told me to install or download a SuperUser zip file. I can boot the phone into CWM after shutting down, but when I open the CWM Manager that I downloaded from Google Play it tells me the following:
" You must root your phone for ROM Manger to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google search on your computer to find instructions to root your phone."
I am a uber novice. That's strike one....two....I'm a girl.....lol I just don't want to mess up my phone....it was really expensive......lol Thanks again for all the help you are giving me......it is greatly appreciated......
Ok then. I think you missed something then.
Let's do this. You want to download the latest version of Odin (It is here aboout half way down). Install it on your PC.
Then go to mrRobinson's thread and download this This is based off of the stock image TMO T999UVALH2
Perm Mirrorownload - MD5 Sum: 4abdcf029f248e66caa83c9c8477bdff root66_TMO_T999UVALH2.7z
and follow the directions. Unzip it and put the Root66 file on you PC where you know it is. Put your phone in Download Mode (see instructions in the link above on how to do this) and open Odin.
Click PDA in Odin and point it to Root66 file from above and make sure that nothing else is ticked above or below PDA. Click start. It should take about 5mins but less than 10 and you'll reboot and have a Pass.
Once that is done and your phone is rebooted, you can either install CWM or TWRP in odin or from the market. CWR= ROM Manager app; TWRP=Goo.IM app. Those will install your custom recovery.
Above all read the OPs f the threads I linked. They have valuable info in them.
Also, just because you are a girl has nothing to do with it. I know a few girls and women that are power users and will run circles around most in this forum. Don't sell yourself short.
I gotta get to work, but I'll check in on ya later on. Good luck.
Flash root 666 with Odin then u will have root
Sent from my SGH-T999 using xda app-developers app
Signature.
jinx0117,
Were you able to get it to work ?
Woodrube said:
Ok then. I think you missed something then.
Let's do this. You want to download the latest version of Odin (It is here aboout half way down). Install it on your PC.
Then go to mrRobinson's thread and download this This is based off of the stock image TMO T999UVALH2
Perm Mirrorownload - MD5 Sum: 4abdcf029f248e66caa83c9c8477bdff root66_TMO_T999UVALH2.7z
and follow the directions. Unzip it and put the Root66 file on you PC where you know it is. Put your phone in Download Mode (see instructions in the link above on how to do this) and open Odin.
Click PDA in Odin and point it to Root66 file from above and make sure that nothing else is ticked above or below PDA. Click start. It should take about 5mins but less than 10 and you'll reboot and have a Pass.
Once that is done and your phone is rebooted, you can either install CWM or TWRP in odin or from the market. CWR= ROM Manager app; TWRP=Goo.IM app. Those will install your custom recovery.
Above all read the OPs f the threads I linked. They have valuable info in them.
Also, just because you are a girl has nothing to do with it. I know a few girls and women that are power users and will run circles around most in this forum. Don't sell yourself short.
I gotta get to work, but I'll check in on ya later on. Good luck.
Click to expand...
Click to collapse
Ok, I have gone and downloaded the 3.7 version of Odin and installed it.....I am now waiting as the root666 TMO file is downloading.....and I will try to pick it up from there.......I will keep you posted.... : )
Ok. Good luck. Don't forget to Unzip it before putting in the PDA. Read mrRobinson's OP.
I won't be on until later in the day but there are some very talented people on here that will be able to help.
Woodrube said:
Ok then. I think you missed something then.
Let's do this. You want to download the latest version of Odin (It is here aboout half way down). Install it on your PC.
Then go to mrRobinson's thread and download this This is based off of the stock image TMO T999UVALH2
Perm Mirrorownload - MD5 Sum: 4abdcf029f248e66caa83c9c8477bdff root66_TMO_T999UVALH2.7z
and follow the directions. Unzip it and put the Root66 file on you PC where you know it is. Put your phone in Download Mode (see instructions in the link above on how to do this) and open Odin.
Click PDA in Odin and point it to Root66 file from above and make sure that nothing else is ticked above or below PDA. Click start. It should take about 5mins but less than 10 and you'll reboot and have a Pass.
Once that is done and your phone is rebooted, you can either install CWM or TWRP in odin or from the market. CWR= ROM Manager app; TWRP=Goo.IM app. Those will install your custom recovery.
Above all read the OPs f the threads I linked. They have valuable info in them.
Also, just because you are a girl has nothing to do with it. I know a few girls and women that are power users and will run circles around most in this forum. Don't sell yourself short.
I gotta get to work, but I'll check in on ya later on. Good luck.
Click to expand...
Click to collapse
Ok...I have tried to download the file twice.....it takes about an hour and then when it is done it tells me the file is not there or damaged.....Oh heavens......now what?
jinx0117 said:
Ok...I have tried to download the file twice.....it takes about an hour and then when it is done it tells me the file is not there or damaged.....Oh heavens......now what?
Click to expand...
Click to collapse
Hold on BRB
Ok according to your original post you have recovery. so go here http://forum.xda-developers.com/showthread.php?t=1726088 and download the superuser.zip file and place it on your internal sd card.
Reboot into recovery and flash the superuser.zip and reboot and you will be rooted.
saldebot said:
Hold on BRB
Ok according to your original post you have recovery. so go here http://forum.xda-developers.com/showthread.php?t=1726088 and download the superuser.zip file and place it on your internal sd card.
Reboot into recovery and flash the superuser.zip and reboot and you will be rooted.
Click to expand...
Click to collapse
Ok....I just did what you asked...got the zip and placed it on the internal storage.....booted into CWM and found the file, it installed ok.....here goes nothing....lol
saldebot said:
Hold on BRB
Ok according to your original post you have recovery. so go here http://forum.xda-developers.com/showthread.php?t=1726088 and download the superuser.zip file and place it on your internal sd card.
Reboot into recovery and flash the superuser.zip and reboot and you will be rooted.
Click to expand...
Click to collapse
:victory::victory::victory::victory: It worked!!!!! Thank you so much......every one of you guys who helped me.....Thank you Thank you Thank You!!!!!!!!!!!!!!!!!!!!!!
jinx0117 said:
:victory::victory::victory::victory: It worked!!!!! Thank you so much......every one of you guys who helped me.....Thank you Thank you Thank You!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
You go girl, do your thing...lol i'm happy it worked. Now happy flashing :thumbup:
Good job man. Looks like we may have converted another crack-flasher.
Jinx, first thing you need to do is boot into CWR and make a Nandroid. Save a copy of it to your PC for safe keeping. This will help you recover from any "mishaps".
Why it didn't work
When the phone reboots, it destroys the flags on the root software that was added via Odin.
To get around that problem,
do the odin process again, but uncheck the auto reboot before you start.
Then when the process is finished, take out the battery on the phone.
reinstall the battery after a few seconds, and then....
BE SURE YOU DON'T MISS THIS STEP,
GO INTO cwm PROCESS TO FLASH THE FILE YOU LOADED WITH ODIN.
if you miss the 3 button CWM load it messes up the file and you again have to reload it with odin, so that part is where you might be having the phone not actually root.
Go to this website and watch HOW TO DO IT till you can do it in your mind without any missteps...
Then, It WILL WORK!
Here is the link:
http://galaxys3root.com/galaxy-s3-root/how-to-root-u-s-and-canada-galaxy-s3-sgh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Good Luck!
Here is the official ClockworkMod Recovery 6.0.4.7 non-touch images and touch images for the Nexus 10 enjoy :cyclops:!
Credit goes to Koush for releasing the official ClockworkMod Recovery images
These are safe to flash via fastboot.
Non-Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-manta.img
Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-manta.img
These can be flashed via fastboot using the following commands:
Code:
fastboot flash recovery /path/to/.img
fastboot reboot
Once again enjoy :victory:!
Note: To get the recovery to stick on reboot when Clockworkmod Recovery asks you if you want rename flash-recovery.sh or similar say "Yes", this will allow you to keep Clockworkmod Recovery installed permanently (Unless you flash a different recovery image) when you reboot your phone.
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Dees_Troy said:
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Click to expand...
Click to collapse
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
Ok that is really bizare, both CWMR and TWRP are not working right and encountering similar issues regarding random reboots and mount issues. Whats odd is other people are experiencing random reboots during regular use even when not in recovery. I'm starting to believe that something Google might have to put out at fix for software wise may be needed.
So I take it no more "booting" the temporary ones posted before for the Nexus 4/Nexus 10? We can go ahead and "flash" these ones right?
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
i cant even get the sideload to work to get SU installed. Its driving me crazy. I keep trying it over and over again with the same result. As soon as i go over to recovery it unmounts from the computer then the sideload command fails due to computer losing connection with it. "Device not found"
Tried both CWM versions now .5 and .6
Not my first time around the block with rooting :-/
Used heimdall suite to flash my GS2.. any way to get it to push the .zip file for SU over to the phone? Push the recovery img then push the .zip maybe?
So I never even ended up trying to sideload anything, I just flashed the official recovery, then went immediately to recovery from fastboot, and once there I just flashed the SU zip and now I have root. Of course, CWMR doesn't work (i.e. if I use Quick Boot to boot to recovery it just takes me to the stock recovery, and if I try to go to recovery from fastboot manually, I just get the dead android w/red triangle).
Jayrod1980 said:
Finally got it... helped to just get the supersu on the root of the device. I used the fastboot commands to get to cwm touch and then I quickly installed it through the interface. I couldn't sideload. The device won't recognize adb when I'm in fastboot mode at all. I don't know what I was doing wrong in that instance, but using cwm briefly let me install supersu. Thanks for your help! Surprising this is so buggy considering it's a nexus... and it's not the nexus that's excluded from AOSP. Go figure!
Click to expand...
Click to collapse
I had to do it this way in order to get root. Finally.. been working on this for like 5ish hours now.. what a pain. Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon. Good luck to everyone that goes this route.. it takes a lot of trial and error
snunez said:
Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon.
Click to expand...
Click to collapse
I'm sure there will be, probably by the end of the weekend, if not sooner
I took apart CWM touch 6.0.1.6 and fixed reboot after 20 sec
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
So,
Am I right in thinking...
cd to the adb tools folder where the sdk is saved.
I need to unlock the boot loader via fastboot oem.
Then copy your file to the same directory on my Mac
Then type in the command line you suggested with the correct filename?
After that I will be rooted
Swype'd at pace from my Galaxy S2
Here's my working tree
The-Kevster said:
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
Click to expand...
Click to collapse
I used this tool to unpack and re-pack the image: https://github.com/huaixzk/unpackbootimg.git
Attached is my current working tree as a tar.gz
Edit: the tool in that git repo is missing a step to gunzip | cpio the ramdisk... I made a shell script to do that for me when unpacking and repacking
Edit2: I added the wrapper scripts I made for posterity
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Underworld79 said:
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Click to expand...
Click to collapse
I could probably do it to TWRP as well (later today, it's sleep time for me)... however, I don't know where the latest nexus 10 recovery image is from them (considering it's not in this forum).
so can I permanently flash this now instead of fastboot?
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Well I just flashed your version of the recovery, and after doing "fastboot-mac reboot" and rebooting, I tried rebooting to recovery via adb, and unfortunately it brought me back to the dead android red triangle screen. In fact, I can't even get to CWMR at all. Anyone else??
And to be clear, I have successfully rooted, so at this point I'm just trying to get a functioning version of CWMR on the tablet, if possible.
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Randomwalker said:
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Click to expand...
Click to collapse
Yeah I know that, but I'm not trying to enter stock recovery, I'm trying to enter the custom recovery (which is the supposed "stable" one by damien) which I've installed. And it only let me access CWMR immediately after flashing it. However anytime afterwards I simply cannot access it again:
1) tried "adb reboot recovery" and it brings me to the dead android w/red triangle
2) tried getting to recovery via the Quick Boot app, and the same thing happens
3) tried getting to recovery via the normal holding buttons down to get to bootloader, then going to recovery manually from there, and a no-go as well.
In the end, all that happens is I have to toggle the buttons once I get to the dead android screen, and the menu for the stock recovery appears, which allows me to reboot. But as for CWMR, it is nowhere to be found. WTF.
Did you reboot after installing CWM? If so, did you remove install.sh, that will restore the stock recovery?
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2