Related
1. Will Galaxy Nexus rooting wipe my phone's data?
2. Which method is recommended? I've found Toolkit 5.7, and that one:
http://forum.xda-developers.com/showthread.php?t=1454314
Maybe they all do exactly the same?
Unlocking wipes phone, rooting comes after..Copy anything from sd card you want to save to pc. Use mskip's toolkit and read all instructions and you will be fine. Google saves all your apps in market and contacts will sync when you sign into google.
Hope this helps.
Use my guide.
Stickied above...and linked in my sig.
But yes, it will wipe your data.
You could, however, use the backup method detailed in my guide.
DON'T use these damn toolkits...
If you someday soft brick your phone (and if you tinker...you will, I promise) you're going to want to know how to utilize the resources you needed to root it manually...and if you used a toolkit, you'll be far worse off as you won't even know if adb/fastboot are set up properly...and will cause a huge barrier of troubleshooting your problems.
I personally promise...
Do it the manual way...and you'll end up with a rooted phone in an hour.
It's not hard.
I also root my nexus without using those tool kits (seems don't have any when I got my nexus)
you may follow Jubakuba's guide, it's safe and not that hard, I root my nexus within 30mins (not following Jubakuba's guide, but almost the same)
Jubakuba said:
DON'T use these damn toolkits...
If you someday soft brick your phone (and if you tinker...you will, I promise) you're going to want to know how to utilize the resources you needed to root it manually...and if you used a toolkit, you'll be far worse off as you won't even know if adb/fastboot are set up properly...and will cause a huge barrier of troubleshooting your problems.
I personally promise...
Do it the manual way...and you'll end up with a rooted phone in an hour.
It's not hard.
Click to expand...
Click to collapse
X3. I used the toolkit for the drivers when I couldn't get mine properly installed. Otherwise, everything else was done in the command prompt with ADB and Fastboot. Very simple and you'll learn what these toolkits are doing behind the scenes so you can better troubleshoot later.
I also rooted my Nexus one without tool kits, it's very easy!
bullka said:
1. Will Galaxy Nexus rooting wipe my phone's data?
2. Which method is recommended? I've found Toolkit 5.7, and that one:
http://forum.xda-developers.com/showthread.php?t=1454314
Maybe they all do exactly the same?
Click to expand...
Click to collapse
If your bootloader is locked, and you are running 4.0.1 or 4.0.2, you can root using this method.
If you want, you can then install ROM Manager from the market and do a backup. Then copy that backup off your device, and proceed to unlock your bootloader (which will wipe) if you want, but then you can restore your backup, and you will have all your data and an unlocked bootloader.
Hi,
I have my bootloader unlocked at the moment after the upgrade to 4.0.4 using this guide: http://forum.xda-developers.com/showthread.php?t=1391881
So I understand that rooting won't erase my phone. Right?
To root I need (I'm skipping blablabla and leaving just the important):
1) fastboot reboot-bootloader
2) fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
3) select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the Superuser-3.0.7-efghi-signed.zip
4) find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option
I'm rooted permanently without loosing my data (as I already have bootloader unlocked), right?
bullka said:
Hi,
I have my bootloader unlocked at the moment after the upgrade to 4.0.4 using this guide: http://forum.xda-developers.com/showthread.php?t=1391881
So I understand that rooting won't erase my phone. Right?
To root I need (I'm skipping blablabla and leaving just the important):
1) fastboot reboot-bootloader
2) fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
3) select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the Superuser-3.0.7-efghi-signed.zip
4) find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option
I'm rooted permanently without loosing my data (as I already have bootloader unlocked), right?
Click to expand...
Click to collapse
Correct.
Just remember that un-locking/locking DOES reset your SD.
But as you said, you're already unlocked. So you're good!
Edit:
PLEASE let me know if that superuser.zip works for you, btw.
I had to update the OP recently to fix 4.0.4 users not being able to root...but wanted the same file to also root us CDMA users and GSM users who aren't on 4.0.4.
If that zip doesn't work...you simply won't have root access. Nothing bad will happen.
Let me know if that happens though (I can't test a 4.0.4 gsm phone, obviously) and I'll get you a .zip that I KNOW works for 4.0.4 users.
Quick question: does the SuperUser app developer has his homepage? Who's the author of that?
Now I understand that there're tons of superuser.apk modifications in the internet. Right?
bullka said:
Quick question: does the SuperUser app developer has his homepage? Who's the author of that?
Now I understand that there're tons of superuser.apk modifications in the internet. Right?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
There are binaries required in 4.0.4 that aren't officially updated, it seems.
Hence my new .zip that is compiled from official SU, but with new binaries.
Jubakuba said:
Correct.
Just remember that un-locking/locking DOES reset your SD.
But as you said, you're already unlocked. So you're good!
Edit:
PLEASE let me know if that superuser.zip works for you, btw.
I had to update the OP recently to fix 4.0.4 users not being able to root...but wanted the same file to also root us CDMA users and GSM users who aren't on 4.0.4.
If that zip doesn't work...you simply won't have root access. Nothing bad will happen.
Let me know if that happens though (I can't test a 4.0.4 gsm phone, obviously) and I'll get you a .zip that I KNOW works for 4.0.4 users.
Click to expand...
Click to collapse
Hi,
Thanks.
Just followed you guide and I have now superuser installed and working. Thanks.
Your guide has some errors. Link is to Maguro and your guide says to flash Toro. Fix the links.
When I flashed Clockwork Recovery with ROM Manager, superuser app asked to confirm the SU request by ROM Manager.
So I assume rooting works well.
bullka said:
Hi,
Thanks.
Just followed you guide and I have now superuser installed and working. Thanks.
Your guide has some errors. Link is to Maguro and your guide says to flash Toro. Fix the links.
When I flashed Clockwork Recovery with ROM Manager, superuser app asked to confirm the SU request by ROM Manager.
So I assume rooting works well.
Click to expand...
Click to collapse
I should probably implement that better.
Guide originally came from a CDMA only forum.
And a GSM only forum.
Merged the posts here...
But it does mention changing the code.
I'll fix it up so it's more obvious now.
And yes, if it asked for SU...
It's fine.
Great news. I hadn't had anyone test yet.
Thanks for being a guinea pig .
i just bought an ssg2 which was apparently unlocked. trying to root it through odin but it doesnt do anything. as soon as i click start all it does is nothing. it is running stock gingerbread.
any input dudes?
Phone recognized by the PC? Correct drivers installed on the PC? Have you followed the steps properly?
You need to flash a custom recovery first, something like Clockwork Recovery or TWRP (I think that's right?), and flash a root binary through that, in your case it would be a file called 'su-3.0.5' (that's for gingerbread).
There are tons of guides here on how to install a custom boot recovery and how to root, find one that you understand and follow it.
First of all,
What is Unbricking ?
Second Question:
If I flash my SU640 to GingerBread 2.3.5 , Root it using whatever method. confirm root using
"adb shell"
"su"
Install CWM using "dd" or "cat" to mmcblk0p13
Copy any custom ROM to my sdcard,
boot into CWM
Can I flash these customs ROMs successfully ?
If not , why not...
If yes , then why does the guide tell me to flash AT&T version of Gingerbread to install CWM.
P.S i have not been able to boot into AT&T GB using ANY guide so far.
I have been able to use CWM and root access on Korean GB though.
salimbaba said:
First of all,
What is Unbricking ?
Second Question:
If I flash my SU640 to GingerBread 2.3.5 , Root it using whatever method. confirm root using
"adb shell"
"su"
Install CWM using "dd" or "cat" to mmcblk0p13
Copy any custom ROM to my sdcard,
boot into CWM
Can I flash these customs ROMs successfully ?
If not , why not...
If yes , then why does the guide tell me to flash AT&T version of Gingerbread to install CWM.
P.S i have not been able to boot into AT&T GB using ANY guide so far.
I have been able to use CWM and root access on Korean GB though.
Click to expand...
Click to collapse
i'm fairly new here but i'm pretty sure about the following:
if you booting into cwm you dont need to unbrick. unbrick is for if you've bricked your phone through a fail flash or corrupted d/l or w/e.
if your reading a unbricking guide thats why its telling you to flash to at&t because if your phone is upgraded to Ice Cream Sandwich then it got bricked by secure bootloader that gets installed.
you should be able to flash a custom rom as long as you follow the proper procedure, find the procedure for installing the rom you are using and follow it.
note: ALWAYS BACKUP YOUR ORIGINAL ROM IN CWM before flashing a custom rom. reasons for this are you could have problems with the rom and have to revert, among other things, also you may not like the new mod and want to go back for preference etc.
for my p930 i run cyanogenmod 10, it's jelly bean and it seems to be stable, after all it is marked as stable by the developer, here is a link for d/l and install instructions if you want to try it.
http://get.cm/?device=p930 this is where you can download CyanogenMod one of the most popular, there are others though if you are curious google them. I recommend a stable version for your first flash.
http://forum.xda-developers.com/showthread.php?t=1980505 <-- install guide, click on the show content button under the kind of rom you are installing... READ THE WARNINGS ON THIS PAGE.
*edit* dont forget to backup your contacts/apps that you want to be sure you have for your custom Rom as well. titanium backup is the generally recommended app for backing up apps and their data, there are tonnes of apps that do contact backups.
i was going through threads and i noticed that u have the SU version of the phone, make sure you get a rom that is compatible with SU640
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://d-h.st/QGe
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Reboot directly into recovery, and allow TWRP to disable the re-flashing.
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
----IMPORTANT NOTE:----
IF you are on the latest OTA and have NOT unlocked, it is impossible at this time to unlock. It may be possible in the future if someone finds another exploit, but not likely. Basically, if you updated without researching (that's why you shouldn't do that) or got a new one after the OTA, you're SOL for right npw
sloosecannon said:
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/twrp2.4-recovery-scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Run adb shell from the same info and run the following commands (you can copy-paste and press enter):
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro /system
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
Click to expand...
Click to collapse
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Awesome!!!! Hopefully this will spark up some dev activity. I know this is huge I just hope its not too little too late.
BoredKender said:
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
Click to expand...
Click to collapse
Nope, don't need to uninstall safestrap, and yep, you do need SU.
sujaanj said:
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Click to expand...
Click to collapse
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
sloosecannon said:
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
Click to expand...
Click to collapse
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
trouble installing recovery
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
dnoren said:
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
Click to expand...
Click to collapse
You need to be in fast boot mode for it to flash recovery.
Turn off your device, hold Power + Vol Up + Vol down then select fast boot and plug your phone into your computer.
Sent from my XT907 using xda premium
new roms
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
CaptainElwood said:
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
Click to expand...
Click to collapse
Yes, as long as you mount your /system first. Found that out the hard way too...
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Nope
ifrankie10 said:
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No, everything is the same except I get a warning every boot that my phones bootloader is unlocked
Has anyone flashed a dev edition rom yet? If so what one, I wanted to try but the cm10 thread has broken links. Can I get that somewhere else?
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Sent from my XT907 using xda app-developers app
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
and can we rsd back to stock if we can't get into the recovery but into fastboot
Sent from my XT907 using xda app-developers app
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
mindflayyer said:
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If I recall correctly, 4.1.1 is fine, just use the JB root method. 4.1.2 is an issue, but that has not been pushed yet (on Verizon that is).
Floundering with recovery
I've tried both methods cwm and twrp it says writing recovery, okay, and finished but when i try to go into recovery I just get the Green robot
Any ideas on what I'm doing wrong?
Thanks
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Hmm..
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Click to expand...
Click to collapse
If they are able to discover that the phones system files have been tampered with in anyway, including unlocking, rooting, installing custom recoveries, roms, modems etc.. most likely they will not fix your phone. Quoted off the Motorola website "Unlocking your DEVELOPER EDITION's bootloader voids all warranties" (Naturally this goes for retail edition even more so). I have however hear of people getting unlocked phones repaired under warranty, just make sure that you RSD back to stock, unrooted before you send it.
pjf626 said:
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Gonna need a tad more detail.. Are you sure that you're rooted? If not, that would cause both of your problems. You also need to uninstall safestrap through the safestap app, and then remove the app.
sujaanj said:
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
Click to expand...
Click to collapse
Yes unlocking is blowing a fuse but that's beside the point, there is a separate piece of software that looks at that fuse and decides whether to allow the system to boot an unsigned system or not. If the OTA changes this piece of software to use another fuse instead (there might be many of them) then your device will be locked again and we will be back at square one, no fuse need to actually be reset for this to happen.
NOTE! This guide is extremely old and likely isnt up to date. I cannot maintain it any more. If anyone is willing to take it over and fix any issues, let me know!
TOOK THE OTA AND GOT STUCK IN RECOVERY LOOP? DERP, DONT TAKE OTAS, DUH. ANYWAYS, IF YOU CANT GET INTO DOWNLOAD MODE AFTER OTA, DO THIS
GUIDE:
Thanks to Bliss who worked the exploit into Loki, Dees_Troy built TWRP for us, djkinetic, Huskehn, and myself tested.
So good news folks! TWRP is now working on LG G2 thanks to an updated loki patch from bliss. Note that Loki patch is not necessarily an unlocked bootloader, but for the end user there is basically no difference. We can flash kernels (when they exist) roms (when they exist) recoveries etc etc. A full bootloader unlock could come someday, but this is all you will need until then.
First off, if you have issues with ADB not connecting, try THESE DRIVERS
The install is super simple, and you have two or 3 options.
Download the img for your device:
AT&T IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Verizon IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
TMobile IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
Korean Telecom IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
d802 IMG DOWNLOAD THE NEWEST VERSION ONLY!!! as of writing that is 2.6.3.3
For other models, click HERE and scroll down to find the files beginning with d2, and see if any of the folders sound like your model.
NOTE FOR THESE DOWNLOADS! READ ME! UPDATE! Ok, so if you look in the download page for your device and you are getting a zip file, this is a flashable zip, but it cannot be treated the same as an IMG file in this guide. You need to flash an older one that is a .img file, and then use that to flash the newer zip.
YOU MUST ALREADY BE ROOTED! follow This guide to do so if you arent. BE AWARE THAT THIS ROOTING METHOD ONLY WORKS BEFORE TAKING THE OTA. IF YOU ARE UPDATED AND UNABLE TO ROOT, FOR NOW THE ONLY WAY IS TO FLASH BACK TO STOCK AND ROOT BEFORE THE OTA, THEN TAKE THE OTA, THEN INSTALL TWRP
NOTE THAT ALL GUIDES BELOW ARE REFERENCING THE VZW img file. Be sure to replace it with whatever version you downloaded!
ABSOLUTELY DO NOT FLASH ANYTHING NOT MADE FOR YOU PHONE SPECIFICALLY!
OPTION 1 RECOMMENDED The way I tested it in #lg-g2 Possibly safer as loki runs some safety checks first. Download loki from github here Click download zip on the right. and go into the bin folder of the zip. push loki flash and the img like so:
Code:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
-------------------------------------------------------------------------------------
OPTION 2 via dd. Push just the recovery img like this:
Code:
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
[B][COLOR="DarkOrange"](IF YOU DONT SEE A # prompt, type su to get it.)[/COLOR][/B]
cd /data/local/tmp
dd if=/data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
adb reboot recovery
--------------------------------------------
OPTION 3 easy, untested (as of time of writing) install it from goomanager on the phone! This aparantly does work bu you have to manually browse to the file or something... anyone who's tried care to clarify?
I tried and cant figure out where you find the recovery. I recommend Option 1 or 2
----------------------------------------------
Troubleshooting:
If you get "Failed to open aboot for reading." when following method 1, Be sure you have the # prompt, not $. If you rooted properly you should alutomatically have # in shell, but if not just type su to get it. then run the flashing command.
If you had confusion based on the pushing steps because the two img names listed in the command were different, my bad. the filenames changed while I was writing from test version to final, I missed replacing the first name in the commands. Look at the post again as it is fixed now.
If adb reboot doesnt work, make sure that "exit" command fully exited you out of the adb shell prompt. you should be at standard command prompt for that. type exit again if you arent, or heck just open a new command prompt
-------------------------------------------------------------------------
Be happy with what you have, so soon. Be sure to thank all the devs and donate to them![/SIZE][/U]
Got stuck trying to send the recovery to my ATT G2, replacing verizon files, renamed all the files including recovery file to RECOVERY and got it running. TWRP up and running. WOOOHOOO, let the roms begin lol
What? You mean no one cares whether or not I get this device only what @scrosler gets?
I kid, I kid.
Nice work on getting TWRP on the device. Now it is time for something truly awesome to happen, now that this first step has been taken.
Thread Cleaned
can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?
Walter21026 said:
can someone confirm sucessful TWRP installation via GooManager? This is the only way i feel comfortable installing it at the moment can someone confirm this method is working?
Click to expand...
Click to collapse
I'd like to know this as well, please
This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?
If this works as the loki for the S4 did, then we will have access to flash everything. Kernel, modem, and ROM. There are no boundaries.
Sent from my LG-D800 using Tapatalk 4
JustusIV said:
This doesn't mean anything about the bootloader does it? You still have to run the stock kernal?
Click to expand...
Click to collapse
Currently this is a work around. Bootloader is still locked up tight
Goo says no recovery found for this device.
Sent from my LG-D800 using XDA Premium 4 mobile app
Basically the bootloader no longer matters except for the purity of beating them at their own game. I am sure there are other benefits, but crackflashers will have our fix
Sent from my LG-D800 using Tapatalk 4
i tried thru goomanager i went in to the install open script and it says no recoveries are available
HUGH Thanks to everyone that made this possible! :victory: You guys are the reason I stick with android and never worry about buying the latest devices.
Patience paid off. :highfive:
Now Bring on the ROMS!!!!!:laugh:
Doesn't work for me. I get a "cannot stat 'g2vzw.img': No such file or directory"
Do I need to root before this
Nvm I'm dumb
Sent from my VS980 4G using XDA Premium 4 mobile app
Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....
Han Solo 1 said:
Since there is no file named simply "g2vzw.img" from the OP download links, it's not letting me do the step:
adb push g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.0-g2vzw.img
and tells me that no such file or directory exists, which is true.
Confused....
Click to expand...
Click to collapse
i was about to try, then saw this when reading through it. i don't get it.
So in theory an OTA will patch this just like the S4 so be careful with updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.
jayochs said:
i was about to try, then saw this when reading through it. i don't get it.
Click to expand...
Click to collapse
Hopefully the OP will chime in here soon.
JustusIV said:
So in theory an OTA will patch this just like the S4 so be careful updates.
Wish i had mine in my hands but i dont have my upgrade till the 29th.
Click to expand...
Click to collapse
Stop by the store or CS they will push it up for you no problem. They did for me just ask nicely
Sent from my LG-D800 using XDA Premium 4 mobile app
Han Solo 1 said:
Hopefully the OP will chime in here soon.
Click to expand...
Click to collapse
i'm also frekaing out because this is the first i heard about this chinese root method possibly having spyware..that's the method i used, and despite the fact i deleted their superuser app immediately, i'm wondering if i should go back to stock and do all that bs just to root again with the new method..