I was running Ginervolt 2.0 on ZV7. I chose to install the Stock ZV8 rom using LGNPST. It eventually installed ok. Afterward it successfully installed the ZV9 Rom from the Big Red Mothership. I used @dexter35803 's VZ8/9 Root utility to root the rom and it worked. SU is installed and is allowing root access to cachemate and RomManager. However, I am not able to install Clockwork Mod.
I used Easy V8 to install CWM. it reported access denied.
I tried to install CWM using the one click method and it reported access denied errors.
My attempt to confirm CWM recovery was to use
Code:
ADB Reboot Recovery
from the command prompt to force it to boot into recovery.
That resulted in the LG Boot logo, followed by a black screen.
I used the PWR + VOL Down button to gain access to CWM, it proceded to wipe the user data like the stock recovery,
Lastly I used RomManager to install Clockwork. It succeeded in gaining root access via SU, and proceed to reboot. Now it's Stuck @ the LG Boot logo.
After waiting 5 minutes I pulled the battery. Now if I use PWR + vol down, it will wipe the user data, but again hang at the LG boot Logo.
What should I do?
thesavo said:
I was running Ginervolt 2.0 on ZV7. I chose to install the Stock ZV8 rom using LGNPST. It eventually installed ok. Afterward it successfully installed the ZV9 Rom from the Big Red Mothership. I used @dexter35803 's VZ8/9 Root utility to root the rom and it worked. SU is installed and is allowing root access to cachemate and RomManager. However, I am not able to install Clockwork Mod.
I used Easy V8 to install CWM. it reported access denied.
I tried to install CWM using the one click method and it reported access denied errors.
My attempt to confirm CWM recovery was to use
Code:
ADB Reboot Recovery
from the command prompt to force it to boot into recovery.
That resulted in the LG Boot logo, followed by a black screen.
I used the PWR + VOL Down button to gain access to CWM, it proceded to wipe the user data like the stock recovery,
Lastly I used RomManager to install Clockwork. It succeeded in gaining root access via SU, and proceed to reboot. Now it's Stuck @ the LG Boot logo.
After waiting 5 minutes I pulled the battery. Now if I use PWR + vol down, it will wipe the user data, but again hang at the LG boot Logo.
What should I do?
Click to expand...
Click to collapse
use root explorer and go into system/etc/ and delete the file called install-recovery.sh
The reason why you aren't getting clockwork recovery to work is because the install-recovery.sh is a shell script designed to over write any recovery back to stock recovery on each boot. So when you run the cwr tools and the phone reboots the script immediately erases what you just did. So deleting this file before you run the tool will allow the tool to install a perminant cwr
then run V8 all in one root plus cwr here https://www.dropbox.com/s/l1090uvf1iw3jux/V8%20All%20In%20One%20-%20Root%20and%20CWM.zip
and choose install root and cwr options and viola
+1 on removing the script.
But before all that your going to need to flash the v8.tot in emergency download mode, use the test mode fix, update, use the v8 aio, and hope you have a nice day. if cwm doesn't stick then try removing the script described above and rerunning the aio smile and have a brewski for your time and trouble.
Sent from my VS910 4G using XDA
all of which can be found in the general forum.
Sent from my VS910 4G using XDA
das7982 said:
use root explorer and go into system/etc/ and delete the file called install-recovery.sh
The reason why you aren't getting clockwork recovery to work is because the install-recovery.sh is a shell script designed to over write any recovery back to stock recovery on each boot. So when you run the cwr tools and the phone reboots the script immediately erases what you just did. So deleting this file before you run the tool will allow the tool to install a perminant cwr
then run V8 all in one root plus cwr here https://www.dropbox.com/s/l1090uvf1iw3jux/V8%20All%20In%20One%20-%20Root%20and%20CWM.zip
and choose install root and cwr options and viola
Click to expand...
Click to collapse
You should really read his second to last little paragraph. He used Rom Manager to install CWM when it's not supported for the phone. So now he'd have to install ZV8 through LGNPST to have a working phone again. Also, This should really be in General instead of Development.
Where should I start?
With the Phone @ the LG Boot Logo screen, the LGNPST windows application will not recognize the phone nor will ADB.
Update, found something
1. pull battery
2. pull USB
3. hold [PWR] + [vol Up]
4. Plug in USB
5. Wait for display to flash and read "Downloads in progress. Do not Disconnect cable. "
But this only lets me update the phonebook, not flash a rom or use ADB. what now?
When you select the phonebook file to flash, use the instructions on selecting the v8.tot. It'll flash everything, not just the phonebook.
Sent from my VS910 4G using XDA
Correct me if I'm wrong, but isn't cwm not available for v9? So going higher than v8 is useless until the way to install cwm is figured out, besides I don't remember seeing any posting that there said that there is a custom ROM for v9 yet.
Sent from my VS910 4G using XDA
I.M.famous XMAN said:
When you select the phonebook file to flash, use the instructions on selecting the v8.tot. It'll flash everything, not just the phonebook.
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
I tried this and it failed with
Code:
invalid binary file
error.
able to flash rom
I found an old machine in the basement today with Windows XP installed Nativity on the machine. I was using an XP VM for this. I was able to use LGNPST to successfully flash the TOT files while the phone working. I was not able to flash after bricking it.
Now with a native XP machine, I am able to flash the rom.
Sorry all for the noob-ism. Its been a long weekend here.
Also, is there no CWM for ZV9? How would I find out? I thought there would be a Sticky for that.
- Also, no I am in this
Test Mode
Click to expand...
Click to collapse
. Time to research that one.
There is cwm for V9. The V8 aio works just fine.
test mode fix
I found the thread on
Code:
[URL="http://forum.xda-developers.com/showthread.php?p=26737282#post26737282"]Test Mode Fix[/URL]
But it just crashes in XP native. Any thoughts? I have installed DotNet 3.5 Framework, but that doesn't seem to work.
Well, I found the zv4 TOT rom that I could download from. (most of them now only let the owner re-download.)
I flashed it with LGNPST. So with this FroYo rom, it no longer reported to be in Test Mode, when plugging in a USB cable. However, it also would not update through
Code:
Settings Menu --> About Phone --> Software Update --> Check New.
I used LGNPST again to flash the ZV7 rom over ZV4. However the phone again reports being it test mode @ startup and when plugging in to a PC.
I hope the VZW store can fix this, i am all out of ideas.
I would try the test mode fix on another computer first. Test mode is an obvious sign you did something you weren't supposed to do
You may have to run it a couple of times for it to fix test mode. You'll know when it works, after reboot you will see USB icons in the notification bar.
Sent from my VS910 4G using XDA
I have a fresh new XP box ready to go but the drivers link on the first post is busted.
thanks all
New phone arrived on Friday. Does anyone else have anything they want me to try before then?
Thanks all for your help and support during this ordeal.
Related
Ok so I have successfully rooted my phone after updating to Gingerbread. However, I had a few issues and had to read through a bunch of different posts to get there. So I'm bored and decided to consolidate everything into one.
If anyone has any other issues or fixes post them here and I will update the OP.
Credit goes to mtmichaelson and all those who helped get this working
http://androidinvasion.us/forum/index.php/topic,77.0.html
Here it is:
1. ROOT PROCESS
A. Get back to Stock:
-download the stock Zv4 ROM zip from here and put it on your external SD card- http://forum.xda-developers.com/showthread.php?t=1326893
-Back up all your apps in titanium (important: USER apps only, no data or system apps)
NOTE: It has been reported that restoring apps and data in titanium may cause some issues coming from Froyo to Gingerbread. I backed up my user apps only for easy re-install and NO data or system apps. It worked without a problem.
-MAKE SURE YOU HAVE 4G ENABLED
-boot into recovery (CWM)
-backup?
-factory reset
-select "install ZIP from SD card" in CWM, and install the stock ZIP from the link
-re-bootyour phone (you will have to re-activate it as well)
-install revo toolkit from here if it was wiped with the system reset - http://forum.xda-developers.com/showthread.php?t=1144951
-press "install recovery" and then !!!Revo Stock!!! to go back to stock recovery and wait for it to complete
B. Update to Zv6 then Zv7 (Gingerbread)
-manually search for the update and install it (this will install the v6 update)
-once that installs, manually search again to install the gingerbread update
NOTE: Some people still can't get gingerbread. Verizon has not finished rolling the update out to everyone yet.
Now here is where it gets a little dicey...
C. Rooting Your Gingerbread Phone
-pick up the rooting package from mtmichaelson here - http://forum.xda-developers.com/showthread.php?t=1326509
-follow the instructions he has on that page to obtain root
-Two issues arose for me from this point on.
2. ISSUES
A. Drivers Issue
-The first issue was that some people, including myself, couldn't download the esteem drivers.
-Some people were able to get the drivers from this page to work - http://androidnerds.net/2011/10/08/lg-esteem-oneclickroot-now-ready/.
-I was not able to get my computer to recognize my phone using the above drivers either. I would run the root command from the downloaded package and it would get stuck at "running daemon something something".
-What I did was manually uninstall the LG drivers from my computer and deleted everything "LG related"
-Then I got the drivers from the LG website at this link - http://www.lgforum.com/resources
-Scroll down to the Verizon section and download the "LG_VZW_UNITED..." drivers.
-Your phone should be recognized using the drivers from one of these links.
B. Superuser/Root access Issue - NOTE: this should be fixed now with mtmichaelson's newest root method found here - http://forum.xda-developers.com/showthread.php?t=1326509
-The second issue that came up was that the previous superuser app I had installed stayed on my phone after the updates, even though I lost root.
-The root command from the LG Esteem page would think I had root, but I actually didn't get root access.
-Apparently this issue came up on the Esteem previously and someone wrote a fix for it here - http://androidforums.com/esteem-all...-w-superuser-3-0-6-binary-3-0-3-download.html. It will uninstall the old superuser and install the new version.
3. INSTALL CWM RECOVERY
-mtmichaelson's new rooting package should automatically install CWM recovery on your phone now.
Old method:
-To get CWM back on your phone it's the same process as before the update. Get the Revo Toolkit from thecubed here and follow the instructions - http://forum.xda-developers.com/showthread.php?t=1144951
-There is sometimes an issue where the recovery does not install correctly and gives a fatal error. If this happened, make sure you have version 1.17.1 of busybox installed at system/bin. This worked for me and I got it installed correctly.
...And you should have root after trying a combination of the above. Hope this helped.
-If you have READ through this and still have any issues you can get more personalized help on the IRC channel here.
-Again I did not help with any of this, I'm just consolidating info. If you want to thank someone, thank mtmichaelson and everyone else who helped figure all this out.
-I will keep updating this as new issues arise.
Thank you for compiling this information, it is a useful reference for people to have. I know that the drivers issue took me quite a while to work out even though it is pretty simple. Hopefully this helps others to get rooted with much less trouble.
Quick question using that stock ROM will it completely unroot me?
Also a bit confused with me running revolt does that mess up me just flashing that and it has the stock boot image.
I've Revolted have you?? Sent via tapatalk plugin.
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
Hey guys, I have a new package for root for those having problems. I need testers though. If you can come on irc in about 20 minutes. It has the drivers in it also.
Sent from my VS910 4G using xda premium
xjli said:
i'm having issues with CWM... i flashed back to my stock+root backup and every time the OTA update tries to install it boots to clockwork. ran the exitrecovery.zip in clockwork and it still boots to clockwork. i cleared the cache/dalvik again, the OTA is downloading gonna try it again...
Click to expand...
Click to collapse
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Haro912 said:
You need to use Revo toolkit to get cwm off and the stock recovery back on. from there it will run fine. Then you just have to reroot using MT's modified rooting .bat file
Click to expand...
Click to collapse
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
xjli said:
How? I'm pretty good at this stuff but i feel like a moron bc i can't figure this out.
Click to expand...
Click to collapse
Got it. I guess the first release of revo toolkit didn't have the flash stock recovery option. Can't wait to finally have gb on this thing..
Still reboots to cwm... it won't flash stock recovery. Any ideas?
xjli said:
Still reboots to cwm... it won't flash stock recovery. Any ideas?
Click to expand...
Click to collapse
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
mtmichaelson said:
Go into revotoolkit, Click install clockwork recovery, it should pop up to choose !!revo_stock!! or 4.0.0.2. Choose the revo stock. After it runs, click to check which recovery is installed and make sure it says revo stock, then reboot.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
OP updated for the new packages from mtmichaelson
xjli said:
It doesn't..still says 4.0.0.2... how long should it take to 'install?'
Click to expand...
Click to collapse
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
jrf28 said:
It depends on you connection speed. If it's 3g a while. I recommend doing it on 4g or wireless. You also need busybox installed in the right location. Install the version 1.17.1 in system/bin. The newer versions of busybox may work now but they previously did not.
Click to expand...
Click to collapse
Righto. Only slow 3g in my silo of an office :-/ ill let it go for a while.
Just reinstalled busybox... got it!
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
borborpa said:
The only issue I'm having is getting CMW to stick. I install it, reboot into recovery, and it's there. Reboot, open RevoToolKit, check version, and it says none installed. Hmmm. Trying to install again and see...
Click to expand...
Click to collapse
It looks like it's a common problem. I haven't installed the ROM yet but mt's new gingervolt rom is supposed to make CWM stick - http://forum.xda-developers.com/showthread.php?t=1326542
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
i_t_n said:
Ok so I'm a complete and utter noob when it comes to CWM etc. Never had an android device before this one, never flashed a ROM.
I've got a pretty good grasp of whats going to be happening here, but I'm a little skiddish.
I'm on stock GB with root, at the point where i'm supposed to install CWM with the RevoToolkit. In the RevoToolkit instructions, thecubed says "If no version is listed, STOP and post here.". Well, no version is listed, presumable because i'm on a GB stock recovery. Do I stop here, or do I proceed with installing clockwork recovery?
Specifically, RevoToolkit reports "Version Not Found".
Advice?
Click to expand...
Click to collapse
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Haro912 said:
I had the same thing I got all pissed and thought I was screwed then someone mentioned the GB thing. You'll be fine if you flash cwm. Just flash cwm, boot into it, make a backup in cwm, flash gingervolt, and reboot. everything will work fine
Click to expand...
Click to collapse
Awesome, thank you for the quick reply. Another stupid question that i'm sure is answered somewhere on here, but what exactly will I lose when flashing a ROM, and what will I be able to restore back with a backup?
OK, so I'm using ICS beta 4 for the Streak, and on ROM manager it says I have CWM 3.0.2. But when I try to boot into it, I either get stock recovery or fast boot. When I click on Software upgrade via update.pkg on SD card, on the stock recovery my screen turns blank and I have to hard reset.
Can someone help me get Clockwork Recovery please? Thanks!
PS. I used NVflash to flash ICS, don't know if that helps, but Im trying to provide sufficient information.
ICS B4 comes rooted with SuperUser7 and CWM 4.0.1.4 installed. Don't think that your supposed to use a ROM manager with it. Not sure how you have another CWM version unless you installed it yourself.
Reflash again and don't use the ROM manager app.
OK, well if it came with it, why can I not boot to it. I downloaded ROM manager but never used it. Never installed and other version of CWM, and if I did install another version, wouldn't I be able to see it? I can not boot to CWM.
Thanks for your suggestion, but reflashing is last option. Does anyone else think they know what's going on?
DO NOT USE ROM MANAGER!
First off, CWR isn't working very well right now, I have a new recovery image I've created that adds some functionality to recovery but its still a work in progress.
To get into recovery mode:
1) Power off device
2) Press Power and Volume+, hold
3) You will come into the Dell recovery menu
4) Use Volume (-) to get to "Install Package" and press Power to select
5) You are now in CWR
When I tried that it lagged a second and then booted normally. I'll post a video in a bit.
Oxymorphiend said:
When I tried that it lagged a second and then booted normally. I'll post a video in a bit.
Click to expand...
Click to collapse
Did you use ROM MANAGER and flash a recovery? If you did, recovery is hosed and you will have to fastboot flash the recovery from the B4 directory.
I did use rom manager. And where would I find it in the directory?
Oxymorphiend said:
I did use rom manager. And where would I find it in the directory?
Click to expand...
Click to collapse
Look in your ICS B4 download, you'll see "recovery.img" file.
Thank you both. I finally signed up when I had my first problem, and you guys hooked me up with speedy replies. Much appreciated.
First I would like to thank PlayfulGod and mtmichaelson for the development that makes this work. The other credits as mentioned in the bat file are djrbliss, DRockstar, koush, Raidzero, thecubed, and firon.
This All in One will root, unroot, install and uninstall CWM without any pre setup on your V8 & V9 Revo. Super easy!
I modified the LG-Esteem-Revo_AIO.zip to work on my Revo and thought others would find it useful. I modified the bat file and moved a few things around. I tested all of the options on my V8 Revo. When using this your phone will reboot several times during the process. Please note that your phone needs to have USB Debugging enabled and the phone needs to be in Internet Connection mode.
I am NOT a phone expert!!! So please remember that if you have any trouble!
Please give all credit to the developers as shown above.
The original file was no good. Sorry!
*** NEW FILE LINK ***
http://www.filefactory.com/file/7f2w7g1h3i99/n/Root-CWM_zip
Filefactory is adding the ' before and after the file name. I have NO idea of why. Just rename the file without the ' and it works as expected!
I added another copy of the file here:
https://www.box.com/s/8867602e2ff53649c37b
CWM would NOT work on my wife's rooted Revo after using this tool. I had to use the LGNPST tool and replace the V8 software. Worked perfectly afterward! Rooted and CWM V8!!!
Mark Once Again said:
First I would like to thank PlayfulGod and mtmichaelson for the development that makes this work. The other credits as mentioned in the bat file are djrbliss, DRockstar, koush, Raidzero, thecubed, and firon.
This All in One will root, unroot, install and uninstall CWM without any pre setup on your V8 Revo. Super easy!
I modified the LG-Esteem-Revo_AIO.zip to work on my Revo and thought others would find it useful. I modified the bat file and moved a few things around. I tested all of the options on my V8 Revo. When using this your phone will reboot several times during the process. Please note that your phone needs to have USB Debugging enabled and the phone needs to be in Internet Connection mode.
I am NOT a phone expert!!! So please remember that if you have any trouble!
Please give all credit to the developers as shown above.
http://www.filefactory.com/file/4g1l2reuoyxz/n/V8_All_In_One_-_Root_and_CWM.zip
Click to expand...
Click to collapse
Has anyone tried this yet? I'm trying to get my ZV8 to root, but I don't know how.
SmokinHawtVegasChic said:
Has anyone tried this yet? I'm trying to get my ZV8 to root, but I don't know how.
Click to expand...
Click to collapse
This is how apparently
Sent from my VS910 4G using xda premium
Make sure you backup your current setup before trying any new root method. Ive been saved countless times by this and some people are just to lazy to let the phone backup for ten minutes, because they get over excited by being able to root a new version.
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
File replaced
The original file was bad. Sorry!
New link posted above and here:
http://www.filefactory.com/file/7f2w7g1h3i99/n/Root-CWM_zip
Filefactory is adding the ' before and after the file name. I have NO idea of why. Just rename the file without the ' and it works as expected!
Additional info - Needs stock V8 to work!
CWM would NOT work on my wife's rooted Revo after using this installation tool. I had to use the LGNPST tool and replace the V8 software. Worked perfectly afterward! Rooted and CWM V8!!!
Mark Once Again said:
CWM would NOT work on my wife's rooted Revo after using this installation tool. I had to use the LGNPST tool and replace the V8 software. Worked perfectly afterward! Rooted and CWM V8!!!
Click to expand...
Click to collapse
Wait how do i do that? :/
you mean use lgpnst?
see here: http://forum.xda-developers.com/showthread.php?t=1337386
my download failed...
it will only let me download the file once and my download failed can u plz post a new link? or a torrent??
---------- Post added at 03:06 AM ---------- Previous post was at 02:09 AM ----------
just tried it, went straight to zv8 and rooted with esteem aio, works perfect thanks so much
I uploaded another copy here:
https://www.box.com/s/8867602e2ff53649c37b
Hope it works better.
My vz9 OTA keeps failing, even after running Stock Recovery in this AIO...others having the same issue?
---------- Post added at 02:16 PM ---------- Previous post was at 02:04 PM ----------
also, when I choose the "Unroot and Stock Recovery" option it says:
"The system cannot find the batch label specified - UNROOTSTOCK"
ok I downloaded from the newer box.com link and that solved the cannot find the UNROOTSTOCK issue. But I still cannot successfully push stock recovery. It says
# is not recognized as an internal or external command
I tried it on my Revo. I got the same message. When the phone booted back up it had the stock recovery and root was gone. I don't know why the message shows up but the result was correct. Hope it helps. Hopefully someone with more knowledge can improve this. I put CWM and root back on without a hitch with option 2.
I successfully reverted back to stock recovery using this thread's AIO - I chose option 4 for stock recovery. I didn't chose 'unroot and stock recovery'. After that the OTA successfully pushed VZ9 to my device without error and I re-rooted using the Esteem root method here:
http://forum.xda-developers.com/showthread.php?t=1621625
After that, I used this thread's AIO Option 2: root and recovery to get CWM back. root just failed because I was already rooted using the Esteem method but CWM re-installed.
Only hiccup is after I re-rooted, my phone booted and hung at the black screen after about 3 seconds of the intro splash. I hard reset and restored all of my data (cwm - advanced restore - data only) using a CWM backup I did just before beginning. Maybe if I wiped dalvik and cache before starting it might have prevented that bump in the road?
All good now: VZ9 rooted with CWM and my phone and data just as it was before the OTA.
jeff_roey said:
I successfully reverted back to stock recovery using this thread's AIO - I chose option 4 for stock recovery. I didn't chose 'unroot and stock recovery'. After that the OTA successfully pushed VZ9 to my device without error and I re-rooted using the Esteem root method here:
http://forum.xda-developers.com/showthread.php?t=1621625
After that, I used this thread's AIO Option 2: root and recovery to get CWM back. root just failed because I was already rooted using the Esteem method but CWM re-installed.
Only hiccup is after I re-rooted, my phone booted and hung at the black screen after about 3 seconds of the intro splash. I hard reset and restored all of my data (cwm - advanced restore - data only) using a CWM backup I did just before beginning. Maybe if I wiped dalvik and cache before starting it might have prevented that bump in the road?
All good now: VZ9 rooted with CWM and my phone and data just as it was before the OTA.
Click to expand...
Click to collapse
When you did option for to install Stock Recovery did you get the "# is not a recognized internal or external command" as part of the activity string?
dbeauch said:
When you did option for to install Stock Recovery did you get the "# is not a recognized internal or external command" as part of the activity string?
Click to expand...
Click to collapse
I honestly don't recall. My phone did reboot 3 times and the final command line message informed me that stock recovery was installed. Aside form that, I didn't pay much attention to the string messages.
jeff_roey said:
I successfully reverted back to stock recovery using this thread's AIO - I chose option 4 for stock recovery. I didn't chose 'unroot and stock recovery'. After that the OTA successfully pushed VZ9 to my device without error and I re-rooted using the Esteem root method here:
http://forum.xda-developers.com/showthread.php?t=1621625
After that, I used this thread's AIO Option 2: root and recovery to get CWM back. root just failed because I was already rooted using the Esteem method but CWM re-installed.
Only hiccup is after I re-rooted, my phone booted and hung at the black screen after about 3 seconds of the intro splash. I hard reset and restored all of my data (cwm - advanced restore - data only) using a CWM backup I did just before beginning. Maybe if I wiped dalvik and cache before starting it might have prevented that bump in the road?
All good now: VZ9 rooted with CWM and my phone and data just as it was before the OTA.
Click to expand...
Click to collapse
Does this work with Broken Out? Or were yo running stock when you used this?
My Revo is Broken out and works fine.
My wife's Revo is stock and works fine.
I have a heavily modified version of BO and after trying both option 4 and 5 the update failed.
sleepycarl5150 said:
I have a heavily modified version of BO and after trying both option 4 and 5 the update failed.
Click to expand...
Click to collapse
Yeah same for me man. I had to use LGNPST to go back to V7, then did OTA updates to V8 then V9. So I am on V9 now unrooted, and stock, waiting for MT or someone else to do a V9 ROM...hopefully I don't have to wait long...BING SUCKS!
Hello,
I yesterday got new at&t Atrix hd with android 4.0.4. I updated to newest 4.1.2 (I think). I rooted it with Motochopper. I tried to install CWM with Myth Tool. Didn't work.
Finally I installed CWM with this method.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
Click to expand...
Click to collapse
Then I installed [ROM] CM 10.2 (Android 4.3) for AtrixHD from zip in CWM. Everything was working great till turned Atrix off.
Then it stuck on "bootloader unlocked" screen. Most of the time I was not able to enter CWM but one time somehow I managed to enter CWM, if I use restart option in CWM after restart android loaded successfully. Tried restart again but I was not able to enter recovery and got stuck again. After messing around with volume/power key somehow android loaded again successfully (without enter recovery).
Now it's working but I'm scared to restart or do anything.
What do you think? What should I do? Is it ROM problem, system or what?
Currently there are no install-recovery.sh (or install-recovery.sh.bak) file. Maybe this could be problem?
I would appreciate any help.
Thanks!
mm166 said:
Hello,
I yesterday got new at&t Atrix hd with android 4.0.4. I updated to newest 4.1.2 (I think). I rooted it with Motochopper. I tried to install CWM with Myth Tool. Didn't work.
Finally I installed CWM with this method.
Then I installed [ROM] CM 10.2 (Android 4.3) for AtrixHD from zip in CWM. Everything was working great till turned Atrix off.
Then it stuck on "bootloader unlocked" screen. Most of the time I was not able to enter CWM but one time somehow I managed to enter CWM, if I use restart option in CWM after restart android loaded successfully. Tried restart again but I was not able to enter recovery and got stuck again. After messing around with volume/power key somehow android loaded again successfully (without enter recovery).
Now it's working but I'm scared to restart or do anything.
What do you think? What should I do? Is it ROM problem, system or what?
Currently there are no install-recovery.sh (or install-recovery.sh.bak) file. Maybe this could be problem?
I would appreciate any help.
Thanks!
Click to expand...
Click to collapse
Are you sure the install-recovery.sh file is not installed? Just to make sure, I would install Root Explore to use that to check to make sure.
I don't have root access but I think I should be able to see that file, right?
Do you have root access? You need to install a file manager like Root Explorer so you can easily change the file permissions and rename the file by adding .bak to the end of the file name.
Weird, I don't see it either. I see it in mine though.
No, I don't have root access. I hope it's ROMs issue. CM10.2 doesn't come with root access. There are weird things going on with my phone. I really hope that other ROM will fix that. Thanks for reply.
mm166 said:
No, I don't have root access. I hope it's ROMs issue. CM10.2 doesn't come with root access. There are weird things going on with my phone. I really hope that other ROM will fix that. Thanks for reply.
Click to expand...
Click to collapse
Maybe you could install Root Explorer. Maybe that will allow you to see the file.
I also have problems getting straight into recovery sometimes but if I hold vol up+vol down+power I can select recovery from there. as far root on cm 10.2 flash superuser.zip
Can you tell me what key combinations you use for what purpose? I doubt you make a mistake there...
Sent from my MB886 using xda app-developers app
Just bumping this one
I am pretty desperete now
RSD'ed to Mexican retail
Rebooted fine but I get N/A in every device property value in RSD
When I flash CM 10.2 (wiping cache/dalvik/factory reset/format system and wiping caches/factory reset after) It boots fine the first time and gets stuck in Moto log/Unlocked bootloader when I reboot
I know I missing something but WTF am I missing?
narta said:
Just bumping this one
I am pretty desperete now
RSD'ed to Mexican retail
Rebooted fine but I get N/A in every device property value in RSD
When I flash CM 10.2 (wiping cache/dalvik/factory reset/format system and wiping caches/factory reset after) It boots fine the first time and gets stuck in Moto log/Unlocked bootloader when I reboot
I know I missing something but WTF am I missing?
Click to expand...
Click to collapse
have you tried PAC 4.3 to see if it gives same issue.
frog1982 said:
have you tried PAC 4.3 to see if it gives same issue.
Click to expand...
Click to collapse
it does
I'm having the same problem. Running CM10.2.
Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
elektronchika said:
Hello everyone. There are such topics after each official update for this device and many more.
I tried towelroot (with the secret code also) and Framaroot. No one succeeded. I couldn't root 4.3 with CF-Auto-root, so i didn't try this one. Anyone can help? Thanks!
Regards!
Click to expand...
Click to collapse
install costum recovery via odin and flash supersu in costum recovery, thats it
9134
klemen241 said:
install costum recovery via odin and flash supersu in costum recovery, thats it
Click to expand...
Click to collapse
This is CF-auto-root, which as I said didn't work with 4.3
elektronchika said:
This is CF-auto-root, which as I said didn't work with 4.3
Click to expand...
Click to collapse
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
klemen241 said:
i did that after updating to 4.4.4. N version and it worked. Idk what can you do more
Click to expand...
Click to collapse
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
If you let the phone reboot after flashing custom recovery, it will overwrite the custom one with stock one - tried that earlier today
---
sorry, misunderstand, if you update supersu just open knox and close after it shows you options to lock screen - then the supersu handles knox blocking properly
---
edit2: I tried with supersu by chainfire, didn't test with other party superuser.apk
adamuadamu said:
this works, but you have to untick "reset" in Odin and after flashing the recovery disconnect it, pull the battery, put it back and start the recovery manually, then flash supersu .zip and the other one that prevents the original recovery to be written back
Click to expand...
Click to collapse
This also doesn't work...
Try also Koush's Superuser.
Sent from my GT-I9305 using XDA Free mobile app
elektronchika said:
This also doesn't work...
Click to expand...
Click to collapse
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Thank you adamuadamu !!!
It works!
Regards Sonic76
adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
sham79 said:
you mentioned recovery disabler from CF root, can you point me where exactly do I find that file? Cheers!
Click to expand...
Click to collapse
first attachment in the OP
direct link: http://forum.xda-developers.com/attachment.php?attachmentid=1680841&d=1359295479
Thanks for the explanation adamuadamu,
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Thanks in advance for the reply and explanation.
Cheers,
Da Fig
Do you have to flash the custom recovery first and then SuperU? Is it possible to just flash SuperU and then using Triangle Away in order to root 4.4.4?
I want root but want to stay as stock as possible.
Da Fig said:
However, just to be sure, apart from the recovery disabler file, the other CF-Root file that I need to flash is the "update supersu2.02.zip"? I've read a lot of posts explaining the same procedure but no link to the actual files that need to be flashed, and sometimes the reference is to generic names like CF-root and when you search for it there is a lot of different files, etc.. I'm a newbie, so sometimes I don't know if any version of Philz will work or if it's better to use just plain CWM, if CF-auto-root is the way to go or just the old CF-Root (last version for i9305 says is for 4.1.1).
Click to expand...
Click to collapse
I remember using some older SuperSu (1.9xx) as the files were already on my SD Card
In case you need proper and updated files and you're a bit afraid of confusing them - google for skipsoft toolkit, choose your device, wait for the program to download appropriate files and then in order to get the files you need, you'd have to (all from my memory, in case you'd need more detailed info, let me know and I can check within couple of hours, as I'm not in front of my private PC now)
1. go to root options and use option to push supersu and recovery disabler to your card
2. let the program reboot your phone into download mode
3. contrary to the advice onscreen, use odin, but untick "Auto Reboot", flash your recovery (the program will show you the path to newest recoveries it downloaded upon first run)
4. wait for the recovery being flashed, disconnect the phone, pull the battery. DON'T CLOSE ODIN yet, you may need it if you fail to boot into recovery directly!
5. start the phone using 3-key combo into recovery. if you fail, you'll need to go back to step 2.
6. flash both files copied in step 1.
7. reboot into system
personally I stick with PhilZ touch, as it always checks for root when leaving recovery and offers to repair it
8. go to play store and download or update supersu by chainfire (whatever applies to you)
9. run SuperSU, agree to disable KNOX
Thanks for the reply adamuadamu, I'll try this and see. Apparently most supersu or the correspondent CF-auto-root will do the trick. I'll try your method first, otherwise I'll start playing with different files.
Cheers.
KennyMRos said:
Hi, so if I understood well, the only thing I have to do to get rooted my S3 with 4.4.4 is to flash the CF-autoroot via Odin, isn't it? Then how can I install a new Superuser.apk if it brings me a force close trying to open the one already installed caused because of Knox?
Has anyone tried that method already? Does it actually work?
Click to expand...
Click to collapse
SuperSU version 2.01 has the forced close problem on 4.4.4.
Download the SuperSU version 2.02 in following thread and install it. It will ask to disable KNOX. select YES.
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
:good:
isn't there a way to instal just SU with towelroot installing an old samsung kernel without tripping knox like in this thread?
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
adamuadamu said:
well, just to be sure, you may not allow the phone to enter normal boot mode after flashing custom recovery
so step-by-step how I did it:
(you have to put both zips from cf-root to your sd card before you proceed any further)
1. phone in download mode, odin->untick "reboot"
2. choose your recovery file->start
3. as soon as you see "reset" in Odin window, you may ignore the message on the phone "do not turn off" and pull the battery
4. re-insert the battery, boot with vol-up+home+power combo (if you don't enter recovery, but the phone boots normally - restart from scratch, as your custom recovery just got overwritten)
5. flash your supersu and recovery disabler (both files from cf-root)
6. you may reboot to system now, set up know, update (or download) supersu from play store, allow to disable knox
that's it, I used philZ touch recovery
--------
info from another forum: it's said you can root with kingoroot
so after you root you can use semi-automated recovery install using skipsoft united - after you root, you send the script to prevent recovery overwriting via adb, you got to download mode, flash your recovery and you're done
Click to expand...
Click to collapse
I installed Philz Touch Recovery and fix it all.