Related
Hi guys. I published a step by step guide for all the newbies (I had a tough time the first time. Slightly different combination but it works! Also flashed the custom recovery image!
http://ilikemygooglephone.com/2010/...-and-root-google-nexus-one-mac-windows-linux/
This tutorial on rooting and flashing the RA recovery rom is THE BOMB!
Followed all the steps and now I too have gone to the dark side, and eaten some cookies....
Nice work.
Great! Love it!
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Does it have to be 2.0.0? or can it be any of the RA recoveries above 2.0.0?
bahathir said:
This how I REroot Android in my N1.
Needs:
1) RA recovery image v2.0
2) fastboot
3) adb
1) Set to bootloader
Code:
adb reboot-bootloader
2) Boot RA-recovery 2.0
Code:
fastboot boot /path/to/recovery-RA-nexus-v2.0.0.img
Yes, it only boot the recovery image in memory.
2a) If you have RA already, then just boot the recovery
3) RA: Mount -> mount /system
4) Change permission /system/bin/su to 4755
Code:
adb shell 'chmod 4755 /system/bin/su'
5) Reboot, and enjoy your rooted Android.
Tested, on FRG83D, FRG83G and GRI40 stocks
Good luck.
Thank you.
Click to expand...
Click to collapse
A question for you, if it's possible to simply just change the permission of the su file on the phone, why do most auto root zip's come with an su file of their own?
Could they not just run the script above?
this whole procedure thing ... do stock users like myself lose anything? Like, does it wipe data or does it simply root and nothing at all changes?
You can never tell with these procedures... half wipe the phone...
I haven't tested it, but from the steps listed above (by bahathir) you won't lose any data.
All he's doing is getting you to boot into fastboot mode (power on the phone while pressing the trackball), and then loading the custom recover into temporary memory.
Then, the system folder is mounted and the required permissions are applied to the su file. Once that's done, you reboot your phone and nothing else changes.
The question that I had above though, is that I've not seen this method used before. Most one-click root methond replace the su file (requiring you to flash a zip file from custom recovery).
ahh too bad it doesn't work. maybe a 2.3.3 thing, but I just tried unlocking my bootloader and it says I'm missing AdbWinApi.dll from my PC ... but it's clearly there.
I have the most up-to-date Android SDK packages. I've used them before to root my nexus without a hitch...
SU should be present on the system, and the method above takes it for granted. Thus it's for RErooting. Rooting methods bring the SU - they don't care if there's one on the system, assuming that there isn't.
On the other hand, I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader. If it's the case - this is the most overlooked and bulletproof rooting method for Nexus. But I doubt it's the case.
Here's a n00b question. I have an unlocked boot loader and had previously rooted my phone using superoneclick. I wiped all the data before moving to stock gingerbread since I was on CM7 nightlies before. So there is no "su" in my phone. I get the obvious error:
c:\android-sdk-windows\platform-tools>adb shell 'chmod 4755 /system/bin/su'
/sbin/sh: chmod 4755 /system/bin/su: not found
when I try to run the steps listed here. Any ideas how to get the 'su' on my phone?
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Jack_R1 said:
I guess you're executing "rerooting guide". Well, you can stop now, since there is no SU.
Flash it on your phone. That would be the obvious solution. Running unlocked bootloader and custom recovery, not really hard to do.
When you're doing things you don't fully understand, sometimes you go in extremely awkward ways to accomplish simple tasks. Having unlocked bootloader, why are you bothering with those guides? Reboot to fastboot, flash custom recovery, flash SU package in recovery, reboot. That would be all. Hard? not really.
Click to expand...
Click to collapse
Thanks Jack! Can you point me to an su package that I can safely flash with gingerbread?
Sent from my Nexus One using XDA App
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
aliezad said:
I found the package nexus-addon-0.1-signed.zip while searching for 'su' packages to root an unlocked nexus one on this guide http://forum.xda-developers.com/showthread.php?t=636795 . Will it be safe to flash this on a stock gingerbread?
Click to expand...
Click to collapse
I don't think that zip would work.
I rooted by applying the su.zip provide by dsixda here: http://forum.xda-developers.com/showthread.php?t=968396 (attachment, bottom of first post)
You would need to flash this from custom recovery (I used Amon RA 2+).
Thanks Brownbay! Worked like a charm!
Jack_R1 said:
...I'm completely unsure that "fastboot boot recovery.img" will work on custom image and locked bootloader.
Click to expand...
Click to collapse
Unfortunately this won't work on a locked bootloader (at least, not on mine!), so if you've used 'super one click' to root your N1 without unlocking it (like me), this method won't work for you.
I already have had my bootloader unlocked. I'm wondering if this rooting method alone will wipe my phone?
No, it won't wipe your phone.
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
leech2082 said:
Well I need help. Last week when verizon was having probelms with service my friend thought that it was his phone. He got to messing with **** and now he cant load any roms. Im hoping someone can help. When he boots into recovery mood he no longer has the option to flash zip from sd. Also Nand backup is now missing so he can not backup to a restore point. the only options he has is flash update reboot wipe cache and factory reset. I have heard of people losing root but with that would you even be able to boot by pressing power and the volume up key... he wont leave me alone about fixing his problem so any info someone could shed on the situation I would really appreciate... Thanks
Click to expand...
Click to collapse
Just redo Amons recovery. That should fix it.
Follow these steps: (Also found in Sticky section)
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
Once you do this...power down... then volume up + end = recovery..
The behavior of the recovery boot that you are describing is an HTC recovery; it is not Amon_RA. Amon_RA didn't change, it got replaced.
That strongly suggests that "your friend" re-flashed an HTC ROM onto the phone, probably using a HBOOT method (using a "PB00IMG.ZIP" file).
droidkevlar said:
Just redo Amons recovery. That should fix it.
Click to expand...
Click to collapse
droidkevlar assumes here that what got flashed was the HTC Root PB00IMG.ZIP file.
For the sake of "your friend who won't leave you alone", I hope droidkevlar is correct; otherwise your friend has joined the leak club.
Good luck,
bftb0
vash8806 said:
* adb shell mount -o rw,remount /dev/block/mtdblock3 /system
* adb push recovery.img /sdcard
* adb push flash_image /system/bin
* adb shell chmod 755 /system/bin/flash_image
* adb shell flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
or you could do it from the PC with a single command. Put the phone into FASTBOOT mode (power on phone holding down both Send+End/Power), and then
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
The md5sum of Amon_RA v1.6.2 for the Eris is e3932991f097993602af3c7a4b61a4f8
You can check to see if fastboot is communicating with the phone by using the command "fastboot devices". (Note that if running fastboot from Linux, fastboot needs to be run as root to access the USB device).
bftb0
Okay, so I'm coming from a Vibrant and trying to get Mobile AP going on a friend's Epic. Should be no problem, right?
First: His phone was completely 100% Stock (DI18)
Guess not. So I manually rooted using the following:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/root.sh
adb shell chmod 755 /data/local/root.sh
adb shell /data/local/root.sh
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb shell rm /system/etc/install-recovery.sh
adb push joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push jk-su /system/bin/jk-su
adb push Superuser.apk /system/app/Superuser.apk
adb push playlogo-orig /system/bin/playlogo-orig
adb push playlogo /system/bin/playlogo
adb push busybox /system/bin/busybox
adb push resolv.conf /system/bin/resolv.conf
adb push remount /system/bin/remount
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo
adb shell chmod 755 /system/bin/busybox
adb shell chmod 755 /system/bin/remount
adb shell chmod 755 /system/bin/playlogo-orig
adb shell /system/bin/busybox --install -s /system/xbin
adb reboot
Which is the same as the one click root except I killed the DI18 recovery.sh thing.
Now everything looks pretty good, but I didn't test root (guessing this is my big ****up) and so I went on to install ROM Manager and then flash ClockworkRecovery for the Epic from ROM Manager and it seems to succeed. Asks for Superuser, I hit okay when the Superuser box pops up, and yay, I'm in the home stretch, right?
NOPE.
So I reboot to recovery and it goes like it's loading Clockwork, but then it says that it failed signature check. Uh oh. Well, whatever, reboot and try again later. Or not - now it won't do anything except reboot into recovery and it says "manual mode" at the bottom. It lets me scroll up and down, but not select anything - yes, I tried every single button on the phone.
On to Odin, then! So I download the tar (DG27) and pit (512 first, then 513, later), but it hangs at param.lfs every time, and now it gives the good old phone--!--pc bit. Can get back to download though.
Suggestions, please, anyone?
dorsai3d said:
Okay, so I'm coming from a Vibrant and trying to get Mobile AP going on a friend's Epic. Should be no problem, right?
First: His phone was completely 100% Stock (DI18)
Guess not. So I manually rooted using the following:
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
adb shell chmod 755 /data/local/tmp/rageagainstthecage-arm5.bin
adb push root.sh /data/local/root.sh
adb shell chmod 755 /data/local/root.sh
adb shell /data/local/root.sh
adb shell mount -t rfs -o remount,rw /dev/block/stl9 /system
adb shell rm /system/etc/install-recovery.sh
adb push joeykrim-root.sh /system/bin/joeykrim-root.sh
adb push jk-su /system/bin/jk-su
adb push Superuser.apk /system/app/Superuser.apk
adb push playlogo-orig /system/bin/playlogo-orig
adb push playlogo /system/bin/playlogo
adb push busybox /system/bin/busybox
adb push resolv.conf /system/bin/resolv.conf
adb push remount /system/bin/remount
adb shell chmod 755 /system/bin/joeykrim-root.sh
adb shell chmod 755 /system/bin/playlogo
adb shell chmod 755 /system/bin/busybox
adb shell chmod 755 /system/bin/remount
adb shell chmod 755 /system/bin/playlogo-orig
adb shell /system/bin/busybox --install -s /system/xbin
adb reboot
Which is the same as the one click root except I killed the DI18 recovery.sh thing.
Now everything looks pretty good, but I didn't test root (guessing this is my big ****up) and so I went on to install ROM Manager and then flash ClockworkRecovery for the Epic from ROM Manager and it seems to succeed. Asks for Superuser, I hit okay when the Superuser box pops up, and yay, I'm in the home stretch, right?
NOPE.
So I reboot to recovery and it goes like it's loading Clockwork, but then it says that it failed signature check. Uh oh. Well, whatever, reboot and try again later. Or not - now it won't do anything except reboot into recovery and it says "manual mode" at the bottom. It lets me scroll up and down, but not select anything - yes, I tried every single button on the phone.
On to Odin, then! So I download the tar (DG27) and pit (512 first, then 513, later), but it hangs at param.lfs every time, and now it gives the good old phone--!--pc bit. Can get back to download though.
Suggestions, please, anyone?
Click to expand...
Click to collapse
Did you try flashing the PIT by itself? If not, try it. Sometimes that will get you back up and running.
Also, the DI18 tar is available now.
http://rapidshare.com/files/423321746/SPH-D700-DI18-8Gb-REL.tar.md5
Yep, tried pit by itself, and I just downloaded DI18 .pit, still nothing. He gave up and is on his way to get a replacement.
But I saw (somewhere...so many threads in such a short time period....) that I think someone executed something to do with rageagainstthecage while doing the manual root - that wasn't in the one click root I downloaded from the sticky in the development section. Could that have anything to do with it? I wouldn't think so, but I'm really quite curious how this could fail so hardcore - this is the first andriod device I've not been able to recover from (modded to hell and back a G1, Magic, Droid, and a Vibrant...)
EDIT: wait, pit...no, didn't do the pit by itself - I'm a dumbass, I tried tar by itself. Guess that's what I get for being in a rush
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
infamousjax said:
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
Click to expand...
Click to collapse
The PIT file is nice to have around in case you bork your phone from a bad flash or if you're flashing a kernel or radio independently from a ROM. But if you're just flashing a stock system tar, then you are correct in saying it's not needed.
Hmm...I always opened Odin, had the phone in download, then plugged it in. It recognized it fine, and that's how I flashed my Vibrant. Oh well, that's not the real oddity here. I'm more concerned about why it was stuck in stock recovery mode and you couldn't select anything (but could scroll?!). Why would this happen, and why did clockwork recovery fail the signature check on first install? I still want to get this working, but I don't think he's going to put his (now functional replacement) up for tinkering after that scare, but I'll be getting one relatively shortly.
I got stuck in the same place - used the one-click root method and had Superuser and Titanium and Rom Manger said they had root. So I flashed the clockwork recovery mod and that seemed to work fine, but when I went to backup my current ROM, I got stuck exactly in the same place with the stock recovery "manual mode" where I could scroll but not select anything.
I did however run Odin and flashed it back and worked perfect the first time I tried, so not sure why it isn't working in your case.
Coming from the EVO I didn't know there was an issue but I read that you can't use Clockwork Mod on the stock kernel? I don't know but since this is my wife's phone and I've bricked it once I'll just play with my EVO for now
Okay, so it's reproducible. That's a start. I'm assuming you downloaded Clockworkmod through ROM Manager as well?
When you reflashed, what OS/bit operating system was it? I did it from Windows 7/64-bit. Wondering if maybe the drivers have something to do with it... (oh samsung, you write such awful software but your hardware is oh-so-tasty....)
yes - I downloaded clockwork mod from Rom Manager and it had a choice for the Epic so I thought all was good.
I usually use my Macbook Pro which works fine with my Evo but wouldn't work with the Epic when I rooted so I used my Windows 7/64 bit machine for both the root and then the Odin recovery. I installed the 64bit drivers found somewhere here initially so those are what were installed when I ran Odin. I did use the DI07 tar for some reason (it was this past weekend and I'm not sure DI18 was posted here yet or I just grabbed the wrong one), so maybe try that one if you haven't yet.
Okay, so long story short, don't use ROM Manager for the Epic. Should've done it manually like I usually do instead of taking the lazy way out. Oh well, live and learn, no permanent damage done and I hope this will prove helpful to others.
dorsai3d said:
Okay, so long story short, don't use ROM Manager for the Epic. Should've done it manually like I usually do instead of taking the lazy way out. Oh well, live and learn, no permanent damage done and I hope this will prove helpful to others.
Click to expand...
Click to collapse
ROM Manager works fine if you have a compatible kernel installed first. Most of the newer custom kernels have the compatibility built in.
Right, but the compatibility isn't there in the stock kernel, hence the issue. I don't remember if there's any kind of PSA about this in the dev/root/clockwork threads, perhaps there should be. If there is, forgive me, for it's late and my attention is divided...
irwinm said:
I got stuck in the same place - used the one-click root method and had Superuser and Titanium and Rom Manger said they had root. So I flashed the clockwork recovery mod and that seemed to work fine, but when I went to backup my current ROM, I got stuck exactly in the same place with the stock recovery "manual mode" where I could scroll but not select anything.
I did however run Odin and flashed it back and worked perfect the first time I tried, so not sure why it isn't working in your case.
Coming from the EVO I didn't know there was an issue but I read that you can't use Clockwork Mod on the stock kernel? I don't know but since this is my wife's phone and I've bricked it once I'll just play with my EVO for now
Click to expand...
Click to collapse
dorsai3d said:
Okay, so it's reproducible. That's a start. I'm assuming you downloaded Clockworkmod through ROM Manager as well?
When you reflashed, what OS/bit operating system was it? I did it from Windows 7/64-bit. Wondering if maybe the drivers have something to do with it... (oh samsung, you write such awful software but your hardware is oh-so-tasty....)
Click to expand...
Click to collapse
mattallica76 said:
The PIT file is nice to have around in case you bork your phone from a bad flash or if you're flashing a kernel or radio independently from a ROM. But if you're just flashing a stock system tar, then you are correct in saying it's not needed.
Click to expand...
Click to collapse
I went through the same thing. Stuck in Clockwork recovery. Here is the way I got out. First I flashed the mixup kernel from clockwork. Then I backed up my ROM. THEN I simply restored the ROM and presto...back in the OS. Once I had everything up and smooth THEN...I finally added the MobileAP update zip via the file fixed by Firon.
Not stuck at clockwork, though. Stuck in the stock recovery. Something it just seems you have to odin out of because you can't flash anything.
infamousjax said:
first off, you dont need the PIT at all.
secondly, the reason it was hanging was because you didnt hook the phone up right.
for the best results, you need to do it like this, IN THIS ORDER:
have odin open on your desktop screen
plug in phone
before the phone starts charging, BOOT INTO DOWNLOAD MODE
Odin will instantly pick up the phones connection, and you can start from there. I'm not sure why THIS setup works when doing it in another order is technically the same thing... but hey, you can thank Samsung for that.
happy flashing!
Click to expand...
Click to collapse
DuDe, what a save! The steps you described are what got me out of a hole I had been in since 2pm. I can't believe that's what fixed it. Thanks!
YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.
Symptoms-
Not booting (Hanging at LG screen)
Able to access CWM recovery
Unable to Mount USB
Unable to access Download Mode
#####1#####
Uninstall all previous LG Drivers installed (Add/Remove Programs)
#####2#####
Install PDAnet to get the drivers required installed.
#####3#####
Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.
(ADB Devices should give the result of: ###DEVICEID### Recovery)
#####4#####
Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
(The file will need to be renamed to aboot.img)
#####5#####
Download: http://www.androidfilehost.com/?fid=23252070760973106
#####6#####
Extract the files we need:
g2_security
loki_patch
loki_flash
recovery.img
#####7#####
Get into a command prompt and run the following:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!
#####8#####
Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)
#####9#####--At this point the following thread finished reverting the phone to stock.
http://forum.xda-developers.com/showthread.php?t=2448960
My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.
If you found this help, please donate and buy me a beer!
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C
Hi, your last step, a Verizon link for restoring back to stock.. I have international D802.. can I use some other rom(omni rom) instead of your last step...
Guys, this exactly worked for me.. i used D802... however, i used all verizon files only to flash and finally went to download mode and flashed stock ROM... awesome help guys.. i was about to change the PCB by spending half of mobile cost..... i am definitely getting you a case next week...
still nothing
Still stuck in fast boot mode cannot do anything in cwm
---------- Post added at 09:39 PM ---------- Previous post was at 09:35 PM ----------
Still stuck in fast boot mode cannot do anything in cwm. Please can someone help me ??????
:good:
Me too on D802 and it worked. followed exactly as instructed.
thanks bro!
Thanks so much for the guide, one problem for me.... Im on a mac... I have pdanet, and android sdk set up but i cant get the commands to work. any idea on what to use for the commands?
P.S It does find the phone just fine with ./adb devices
dtuma1980 said:
I will preface this with stating that this is not my phone. A friend had rooted his LG G2 and installed CWM. After he accepted the OTA, the phone was essentially rendered useless. After this process, the phone will be reverted back to 100% STOCK. It took a while to compile all of this information, and I give all credit to respective owners, but this process I pieced together from multiple threads and was able to make this work.
Symptoms-
Not booting (Hanging at LG screen)
Able to access CWM recovery
Unable to Mount USB
Unable to access Download Mode
#####1#####
Uninstall all previous LG Drivers installed (Add/Remove Programs)
#####2#####
Install PDAnet to get the drivers required installed.
#####3#####
Once PDAnet is installed, ADB should recognize the device when it is in 'Recovery' mode.
(ADB Devices should give the result of: ###DEVICEID### Recovery)
#####4#####
Download aboot.img from: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
(The file will need to be renamed to aboot.img)
#####5#####
Download: http://www.androidfilehost.com/?fid=23252070760973106
#####6#####
Extract the files we need:
g2_security
loki_patch
loki_flash
recovery.img
#####7#####
Get into a command prompt and run the following:
adb push g2_security /sdcard/
adb root
adb push loki_patch /data/local/tmp
adb push loki_flash /data/local/tmp
adb push recovery.img /data/local/tmp
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img"
adb shell "chmod 644 /data/local/tmp/aboot.img"
adb shell "chmod 755 /data/local/tmp/loki_patch"
adb shell "chmod 755 /data/local/tmp/loki_flash"
adb shell "/data/local/tmp/loki_patch recovery /data/local/tmp/aboot.img /data/local/tmp/recovery.img /data/local/tmp/recovery.lok"
adb shell "/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok"
adb shell "rm /sdcard/g2_security"
adb shell "dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img"
adb shell "dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota"
adb shell sync
adb reboot recovery
Once the above is done, the phone should boot into TWRP. I shut the phone off at this point and held "Volume Up" + "Power" and Download mode now worked!
#####8#####
Uninstalled PDAnet and then followed the instructions on the following page (including installing the drivers)
#####9#####--At this point the following thread finished reverting the phone to stock.
http://forum.xda-developers.com/showthread.php?t=2448960
My only suggestion is that you RUN THE MD5 HASH to ensure the large file downloads correctly. After this was done, the phone was successfully reverted back to stock.
If you found this help, please donate and buy me a beer!
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZBZ8G6ZPUEN4C
Click to expand...
Click to collapse
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Joppykid said:
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Click to expand...
Click to collapse
Are you connected via PDAnet?
dtuma1980 said:
Are you connected via PDAnet?
Click to expand...
Click to collapse
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Oh boy i got the same issue before. I just go to a local technician to have it fixed.
Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Same issue here. In the command prompt, anything I do returns the unauthorized device error.
EDIT- I'm going to try and sideload a custom ROM, and then flash the stock ROM after setting USB debugging to see if that helps at all. I'll let you know
Joppykid said:
I can't because I cannot turn on USB Debugging, I am stuck in the Recovery. Details of my situation are in this thread I posted. http://forum.xda-developers.com/showthread.php?t=2726985
Click to expand...
Click to collapse
Please refer to the initial post. This will only work if you can access the recovery. If you cannot access recovery, this method isn't going to work. Sorry!
dtuma1980 said:
Please refer to the initial post. This will only work if you can access the recovery. If you cannot access recovery, this method isn't going to work. Sorry!
Click to expand...
Click to collapse
Did you not see what I wrote? Recovery was the only thing I could access. This method didn't work because the RSA Token wasn't authenticated on my computer any longer. My phone was bricked. I now have a new one. Lesson learned. Make sure you have USB debugging on with an RSA token on your computer at all times.
Did you end up wiping the internal SD with the process? I am in a similar situation except I don't have a friend like you to help me out haha.
Joppykid said:
My ADB keeps saying that my phone is unauthorized ;( I can only access .zip. Anyone else have this issue? Have tried multiple drivers, Sideload is the only thing that works.
Click to expand...
Click to collapse
I factory wiped/reset my phone is CWM which got my phone to be recognized as in recovery.
I can't get past the adb shell commands to work. it keeps saying 'dd: can't open '/data/local/tmp/aboot.img' : Not a directory
I tried with the double quotations and without to see if the command would work thinking I was messing up the syntax.
perfect just saved my a$$. ota took for the 24a update. found this and i am back where i was.awesomes