So i recently unlocked and rooted my GNex (LTE version) and upgraded to 4.0.4... It worked fine until sometime later apps that required root access couldnt acquire it. I couldn't flash cwm in rom manager and i couldn't boot into cwm. When I powered the device on and went into recovery manually (volume buttons and power button) it just went to the stock recovery/bootloader.
I think i need to reroot my device again? I'm not sure. Any help would be appreciated!
Sounds like you just need to reflash CWM. I'm not sure what version you were on before, if it was touch based or not. But either reflash CWM file you did before, or if you use ROM Manager just flash CWM at the top option in the app and reboot into recovery. Hopefully that will work for you.
You probably lost root when you applied the 4.0.4 update. You need to install a custom recovery via fastboot and install the new superuser. Some su.zip's do not work, so you need to find a newer one. adrynalyne posted a working one. I'm sure you can find it by searching his user name and looking at the results as posts.
A 'rootkit' may also work for you. It does the same thing, just makes it so users don't really know what's happening .
Related
Ever since I updated to the last OTA I have lost clockworks recovery image. Thus now I am unable to install the latest froyo rom.
I have tried to install the latest clockworks recovery image and Amon_Ra recovery through Rom Manager. Each time it states it is installed but everytime I try to boot up to the recovery image it gives me the following error:
E: Can't open /cache/recovery/command
and it just gives me the Android System Recover <2e>
Any help would be appreciated....
It sounds like you are not rooted.
If you accepted the OTA from Sprint using your system update on your phone, you are no longer rooted and will not have a custom recovery/root permissions. You will be unable to flash any custom recovery/ROMS/delete any sprint apps/Other Root only things until someone comes up with a way to root 2.2.
Have a drink in hopes that a dev will come up with a way to Root 2.2 soon!
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
coolguycarlos said:
I didnt update over the phone
What happened is I installed a rooted verson of 1.47.651.1 but in doing that it got rid of the recovery image... it definetly a rooter version because i can run apps that require root.. such as wife tether titanium back etc...
any other suggestions...
Click to expand...
Click to collapse
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Here is the update.zip...Just extract Recovery.zip....Do this OR/AND what the Senior Member above said and you should be good
timothydonohue said:
there's an update.zip around here somewhere that will allow you to boot into an early form of clockwork recovery.
so, assuming that you goofed something, but still have nand unlocked....
find that update.zip. put it and a .zip for a real recovery onto your sdcard. boot into hboot, let it run the update.zip, that will take you to koush's early clockwork recovery. use that recovery to flash a solid recovery.
done.
alternative method would be to use fastboot to erase the recovery partition, then put a new recovery in.
Click to expand...
Click to collapse
I actually tried the update.zip one already and it doesnt install... it will stated that the signature cant be verified and it will about the installation... havent tried the fastboot approach... I guess I will need to find out how to do that now
so from the looks of it I am screwed... I have hboot .79 if that matters and from the looks of it the rooted rom i installed screwed up my nand unlock.. which is why i think i can install any recovery images... i tried alot of the nand unlock tutorials and most of them I eventually get to a point were i need to write to /data and i cant because permissions are denied... great... oh well i'll keep on trying... any suggestions are appreciated...
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
I'm having a very similar problem also. My Hboot is 0.79.000 too & after trying clockworkmod recovery, a few RUU update attempts, and attempting to change ROMs completely (not in that order) I'm at a loss, no success anywhere. I can't even get in to recovery anymore. It just reverts back to Bootloader menu where my options are Reboot, Reboot Bootloader, or Power down (& I think there is one other option that i tried and sent me back to the aforementioned screen). However, I can still load my pre-existing ROM...
Does anyone have any ideas if there is anything I can do?
TIA
topdawgn8 said:
If you still have super user, try this...same thing happend to me.
http://forum.xda-developers.com/showthread.php?t=744621&page=4
Click to expand...
Click to collapse
I have a question bout this... I seen this before but the sdk that I downloaded for Windows 7 does not have the Su command... any ideas on how I can get it for Windows 7?
Sent from my PC36100 using XDA App
Nevermind I got the Su command to work
Sent from my PC36100 using XDA App
you can erase recovery from rom manager and try to reflash. i would recommend reinstalling rom manager just to make sure it installed correctly. it installed bad on me once and corrupted my recovery trying to update it, reinstalled and installed an old recovery then the newest one and it worked.
Thanks for the suggestions all. I followed the instructions from link you posted using terminal emulator. No such luck, still reading HBOOT 0.79.0000 and running same ROM.
I also tried reinstalling (several times) clockworkmod recovery images and it effects nothing.
Should I try to completely unroot my phone again? If the images i just flashed didn't do it what will?
Im totally at a loss here. ARG!
hit there jtwonbly.......are you also running the stock rooted 1.47.651.1?
Build number 1.47.651.1 CL195459 release-keys
yea same here......and what is it that your trying to do...go back to stock ROM?
I'd like to go to any other ROM. Its as if I'm no longer rooted anymore.
I think I may try to start all over again using NeckFaces old tutorial on unlocking NAND w/o adb. I'm just not sure if that will fix the HBOOT file because I can't get in to Recovery.
OK Guys thanks for all your help but I have been able to get it fixed now!!!
I pretty much had to redo all of Toast Root tutorial and NAND unlock to get it working. Both Part 1 and Part 2 even though I was already running a rooted rom.
The original problem I had is I kept getting told to just try the nand unlock in part 2 but the phone wasnt having it. It wouldnt like the engineering build of the pc36img.zip
So I started from Part 1. Downloaded the rooted rom pc36img.zip and what do you know it finally let me install it. By the time I was done with both parts 1 and 2 I was able to flash a recovery image, get back to hboot .76 and I am now another proud owner of an Evo running a rooted Froyo!!!!
I rooted my EVO 4G yesterday. Everything was going fine until I uninstalled some of Sprint's factory software. This caused my system to behave very weird so I decided to flash it back to the OTA software.
I followed the instructions on android central, but unfortunately the PC36IMG.zip file they tell you to download and install is Android 2.1. I'm now stuck on 2.1, and the OTA update doesn't work. I am new to this and accept that this is my fault, but I was wondering if anyone had instructions on how to update to 2.2?
I tried downloading and installing HTC OTA Froyo 2.2, *FINAL*, build 3.36.651.6 (Rooted) Odexed from this site, but the bootloader screen won't let me install this file. Any help would be greatly appreciated. THANKS!
What root method did you use?
Also, you can't flash ROMs from bootloader, you need to be in recovery -- when you get to the bootloader screen, go to recovery, press power. Also, make sure that you have a recovery installed (ClockworkMod or Amon_Ra).
From recovery, you should be able to flash to any 2.2 ROM you want (assuming that you have full root/nand unlocked/s-off/whatever else people want to call it).
Also, be prepared to be flamed for posting this in the development section (as opposed to the Q&A).
Yeah, should have done it in Q&A. Sorry for that. Again, noob
I initially used Unrevoked. I had ClockworkMod installed before reverting back to 2.1. It's gone now. Should I just use Unrevoked again to reinstall it?
chadz70 said:
Yeah, should have done it in Q&A. Sorry for that. Again, noob
I initially used Unrevoked. I had ClockworkMod installed before reverting back to 2.1. It's gone now. Should I just use Unrevoked again to reinstall it?
Click to expand...
Click to collapse
Go to the market, and download ROM manager. If you already have root, you will be able to flash either Clockwork or (if you scroll down to the bottom of the options when you open the ROM manager app, you will see the option to flash an alternate recovery) Amon recovery via ROM manager. Once the recovery is flashed, you can boot directly into recovery using the ROM manager app. Place the rom file on the root of the SD card, and when you boot into recovery, find "install zip from card" and flash it. Make sure you wipe everything twice before you flash a new rom.
Before you do anything, make a nandroid back-up. If anything goes wrong with the rom, you can always download ROM manager again and revert back to how your phone is now. (providing that whatever went wrong didn't break your root)
Hey guys,
I a long time IOS user and just moved over to the Android family. I just purchased my S3 from ATT yesterday. Came home, did the OTA update and went to root it.
I just found out that the new OTA prevents you from installing CWM and rooting the traditional ways. So my question is, what is my option to get my phone rooted? I wanna remain on the stock ROM but, just clean it out a little from all the bloatware, use google wallet and be able to tweak some things around.
Any help would be greatly appreciated. Thanks
I THINK the ota can be rooted through the toolkit...pretty sure I read that before. Maybe someone can confirm that.
Sent from my SGH-I747 using xda premium
I'm pretty sure the toolkit can do it. Option 4 (I think ... the last option at least) will walk you through using Odin to flash a custom recovery and then flashing a zip file in recovery to root your device.
You may find that when you reboot your custom recovery will be replaced with stock recovery. The OTA includes a script that's run on boot to reset recovery to stock. If that happens to you, then make sure that when you use Odin to flash the custom recovery you don't let Odin reboot your phone. When the flash is done, pull the battery or press and hold power and Vol Up until the phone turns off, then press Vol Up, Power, and Home to get into recovery. Then flash the zip to root your device.
Once you reboot your phone, you can remove /system/recovery-from-boot.p and /etc/install-recovery.sh. You may need to install a custom recovery one more time, but it should stick.
no idea what's going on. i flashed via Odin to get root, and that worked. but i can't get into recovery via power/vol+ and home. also tried vol+ and power but no joy. download works fine.
i installed rom manager to have a peek and that says i "need to have clockworkmod recovery" before i can do anything. the weird thing is in spite of all this, rom manager *can* reboot me into recovery. i just used it to backup my rom just in case.
for now, it seems the only way i can get into CWM is via rom manager? this can't be right since my htc desire and galaxy s2 could do it from a cold boot. had to in case we screwed something up and couldn't boot an OS.
the root guide i used was via here. not2root.com
tommo123 said:
no idea what's going on. i flashed via Odin to get root, and that worked. but i can't get into recovery via power/vol+ and home. also tried vol+ and power but no joy. download works fine.
i installed rom manager to have a peek and that says i "need to have clockworkmod recovery" before i can do anything. the weird thing is in spite of all this, rom manager *can* reboot me into recovery. i just used it to backup my rom just in case.
for now, it seems the only way i can get into CWM is via rom manager? this can't be right since my htc desire and galaxy s2 could do it from a cold boot. had to in case we screwed something up and couldn't boot an OS.
the root guide i used was via here. not2root.com
Click to expand...
Click to collapse
Here is CWM 6.0.1.5 mate https://hotfile.com/dl/176065007/332cffb/cwm6-recovery-n7100-121014.tar.html, flash with Odin/Mobile Odin. Also read this for root http://forum.xda-developers.com/showthread.php?t=1901196.
cheers
flashed and got into recovery but not at 1st. i always held down the 3 buttons when trying to enter recovery and this time i noticed a flash of "the recovery screen" before it rebooted and went into android.
apparently you just press the buttons and let go with the note 2? not sure if i just realised it now or if this fixed it but either way i got in so tomorrow can flash a new rom.
cheers
Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.
OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank
I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.
Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13
FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank
FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega