Database Users

[Q] Semi-Bricked installing Clockworkmod (Not 100% noobish, I swear!)

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!

[Q] Fascinate Troubles

I recently did a factory restore on my Fasciate and obviously I lost my roots and etc etc. I tried to root it again using the "How to root" from android central, link that was provided in how to remove bloatware, install clockworks, and root(Can't post links yet) , but no luck. I even looked around and noticed there was another rar file with updated files to pass the "error: device not found" and I followed the instruction to that and I'm still receiving the errors.
What I am doing is :
1) Installed Samsung Drivers
2) Plugged usb + phone waited until it was installed/detected
3) Started the root
4) While the root rebooted my phone I unplugged my usb because people said it was working that way. I was still getting the "Device not found" error so I used the unplug method.
5) Plugged back in after unlocking the device
6) The root proceeded with the "Start Time" message
7) Couple minutes later it says "Successfully exploited yada yada yada" and the "Device not found" error listing 6 times and says it'll reboot my phone which it did not.
8) Looked at my phone and it was frozen with another error that said that various programs crashed, I could not go to the home and had to pull the battery.
9) That's it. Tested if it was rooted or not with Titanium and it does ask for users rights. It successfully granted it but I made sure and tried to freeze an item but it didn't work. So I am assuming the root didn't work.
So if you can help me out with my situation, much appreciated. Thanks in advance
Edit: The error that froze my phone was "com.google.process.gapps has an error" and with an option Force Close

I'm no expert, but how did you go about the factory restoration? You may have to use ODIN and flash a new image onto your phone, the factory restore image in your phone may have been corrupted when you rooted/modded?
Look up the ODIN threads, but follow the directions carefully!
(And ODIN will get you to DL09 right away.)

toby1064 said:
I'm no expert, but how did you go about the factory restoration? You may have to use ODIN and flash a new image onto your phone, the factory restore image in your phone may have been corrupted when you rooted/modded?
Look up the ODIN threads, but follow the directions carefully!
(And ODIN will get you to DL09 right away.)
Click to expand...
Click to collapse
Thanks but I figured it out, after I was shown the message I rebooted my phone then plugged it back in and ran some CMD commands which rooted my phone. But does using ODIN to get to DL09 really make a difference? What is the major thing that DL09 provides that the DL01 does not. I was stuck will calling Verizon then being transferred over to Samsung for approximetly 2 hours just due to the IP_PREVIOUS_UPDATE_FAILED error from Verizons DL09 update. While in the call they said that DL09 didn't make that much of a difference compared to DL01.

Sorry for the double post. Edits not working on for me on school computer.
If anybody ran into the same problem here are the commands
Open up your CMD start>run>cmd or just search cmd then type the location of your unzipped files for example "cd C:\FascinateRoot_v02" then type the following commands and reboot your phone.
adb shell sh /data/local/tmp/com.sh
adb shell rm /data/local/tmp/su
adb shell rm /data/local/tmp/Superuser.apk
adb shell rm /data/local/tmp/busybox
adb shell rm /data/local/tmp/rage.bin
adb shell rm /data/local/tmp/com.sh

HTC Desire HD won't boot after flash

Hello!
I have a big problem.
I might have bricked the device however the things what i can do are the following:
- Boot into recovery (clockworkmod)
- start a usb data connection with a computer (clockworkmod)
- input of the ADB commands through terminal running in the computer
What i did?
Flashed the memory with a Cyanogenmod 6.3 according to official guideline:
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
and took note and used most procedures from there actually:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Didn't do the engineering hboot.
Everything was working. I got cyanogenmod working.
Then after a while i tried to restore a backup which i had from original HTC configuration which was actually just before i did the cyanogenmod flash with clockworkmod.
So the backup was from the time i already unlocked the phone from locks and had root access.
So again the restore function worked and everything was back to normal.
How i managed to half brick the device?
Yesterday i wanted to put cyanogenmod back to my phone and then the s hit happened.
I admit that i didn't check whether the locks were off i just thought that these should have been off because backup soft was from time i had phone unlocked.
Anyway to cut the long story short - after flashing the memory with cyanogenmod with the help of rom manager the phone didn't boot anymore.
I tried all the options from clockworkmod flash and format and upgrade straight from sd card a new cyanogenmod but nothing worked. Again the white HTC screen and connection through a usb cable.
So probably i have the s-off and who knows what else.
I dont have a root access anymore as well because i already tried it through the terminal. It doesn't recognize the su command.
Question is, how can i put the cyanogenmod back on by only using clockworkmod recovery and working ADB connection through usb link?
Probably have to just get the locks off but the original instructions say i have to have terminal emulator running in phone but i only have clockworkmod recovery soft running at best.
S hit, again very long story, but hope someone can help me!
Cheers!

I had a similar problem yesterday, after flashing ClockwordkMod Recovery to version 3.0.0.5 (it said it had an update) and trying to reinstall CyanoGenmod 6.3 my phone would no longer boot, it got stuck in the white HTC Logo screen.
I'm not really an expert on this stuff, but I managed to "recover" my device by downgrading it again to 1.32.405.6 using this thread: http://forum.xda-developers.com/showthread.php?t=905003. First I had tried to recover a previously backed-up ROM, but that did not work.
I had to put the stock 1.32 PD98IMG.zip file on my SD card using ClockwordMod Recovery (since I could no longer boot), I'm not exactly sure which steps I took to do so, I have tried a lot of things yesterday before I got everything working again.
After this my phone could boot again and I was ready to play around again. I reinstalled CyanogenMod again using an older version of ClockwordMod Recovery. I'm not sure if this is related in any way, but my phone works smooth again..
Once again; I'm really not on expert on how all this stuffs works, I just hope that I can help you on the way with some ideas on how to fix your device.
So probably i have the s-off and who knows what else.
Click to expand...
Click to collapse
I figured out wether my device was S-OFF and/or Eng S-OFF by entering "adb reboot bootloader" from cmd. At the top of the page for me it states:
ACE PVT ENG S-OFF
I believe it stated only SHIP S-OFF when I had the problems you describe.

Thanks man for quick reply!
I definitely try the downgrading solution and i remember i too did the update for clockworkmod rom manager before the flash.
I'll report back tomorrow.
Cheers!

couldn't boot up any roms earlier after upgrading clockworkmod recovery to v3... downgraded to 2.5.1.3 and worked fine

Hi Guys, I have exactly the same problem. It would be really great if you provide me the step by step process to downgrade clockworkmod recovery.
Cheers,
Pav

I'd like to say to you guys that the downgrading solution worked
Didn't have to use any programs inside phone except clocworkmod recovery which was the only thing i had running.
Thank you user jvdminne!
The downgrading solution was in official cyanogenmod guidelines as well but forgot it anyway.
------------
Pavanka!
The downgrading solution from the link is pretty step by step actually.
But anyway, with my half-broken phone the lines didnt do the trick:
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
I had to copy psneuter and misc_version to /tmp folder not into /data/local/tmp.
But anyhow, i already had # root access through computer. Probably from last half flashed system.
So only thing i basically had to do was to cd in windows cmd into folder where i had psneuter and misc_version and after that:
Code:
adb push misc_version /tmp
adb shell chmod 777 /tmp/misc_version
adb shell
in the shell (adb shell):
Code:
cd /tmp
./misc_version -s 1.31.405.6
And after that follow the instructions from previous link.
To get the ADB functions working just follow the guide here or from previous link where it had adb program included, but not sure whether it was working cause i had it from Android SDK package already set.
Hope you got some sense out of it.
Cheers!

Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...

maxa1577 said:
Hey
I had similar problems to those mentioned in the beginning with the cyanogen mod...
I installed cyanogen and the it got to the screen with the blue swirlyness and then just kept restarting. I decided to restore a backup and just got stuck on the white htc screen.
I decided to follow this post and now am stuck with this...
I just tried a couple of different things to no avail...
Click to expand...
Click to collapse
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required

ghostofcain said:
If you had ROOT , S-OFF etc you shouldn't need to go through all this rigmarole, if you can access recovery carry out a full wipe /system /cache /dalvik-cache and reflash your chosen ROM, should be all that's required
Click to expand...
Click to collapse
phew cheers for that. First time flashing and I thought I killed me poor desire.

LG G2 (Verizon) - Recovery (CWM), no download, bootloop stuck **FIXED**

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

[Q&A] [ROOT][LOLLIPOP] Root Mi2 with Lollipop 5.0 !!

Q&A for [ROOT][LOLLIPOP] Root Mi2 with Lollipop 5.0 !!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][LOLLIPOP] Root Mi2 with Lollipop 5.0 !!. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

problems with wi-fi after root lollipop mi2
I have a problem.
After flashing "bottinsecure.img" in the fastboot mode, the Wi-Fi doesn't work anymore!
Suggestions?

ferrets said:
I have a problem.
After flashing "bottinsecure.img" in the fastboot mode, the Wi-Fi doesn't work anymore!
Suggestions?
Click to expand...
Click to collapse
Um... I'm not sure whether it is the problem of flashing bottinsecure.img... It's because I flashed it before and succeeded without problems...
I think you should complete the whole guide first, to make sure that rooting is complete.
BTW, how is the WIFI not working? Can you turn it on/off or can you scan for available WiFi networks?
P.S. You can ask here for answers too. Just if you know Chinese or I can help you to ask.

problems with wi-fi after root lollipop mi2
henry0504 said:
Um... I'm not sure whether it is the problem of flashing bottinsecure.img... It's because I flashed it before and succeeded without problems...
I think you should complete the whole guide first, to make sure that rooting is complete.
BTW, how is the WIFI not working? Can you turn it on/off or can you scan for available WiFi networks?
.
Click to expand...
Click to collapse
Sorry, I don't know chinese.
The first two times I follow all the guide, to the end. Root works perfectly, but Wi-Fi doesn't turn on.
The third time I noticed that Wi-Fi stops working as soon as I flash the bootinsecure.img.
Now I'm trying to reflash ROM and follow the second part of the part without flashing bootinsecure.img

Ok I can confirm that the problem is in the file bootinsecure.img.
After rooting and confirming the wi-fi doesn't work, I reflash the originale boot.img of my ROM from fastboot with the same procedure.
The Wi-Fi work again and the root disappared..

With 4-11-28 wifi disapear if install this busybox, hard choise, root or wifi

I cannot even root my device, even though I followed every step carefully. six times.
every time, I did a factory reset and tried the order of the translated post and the order of the original Chinese post. (they paste the BETASuperSu in the beginning)
nothing works. I use the 4.11.28 by Ivan and can't open Google search app. other than that, it works fine
can anyone help me? thx in advance

kokoparkletal said:
With 4-11-28 wifi disapear if install this busybox, hard choise, root or wifi
Click to expand...
Click to collapse
helped you ask in chinese here http://geek.miui.com/content-14-964-1.html

henry0504 said:
helped you ask in chinese here
Click to expand...
Click to collapse
Thanks, but the same result, or root or wifi, with 4-11-28 and Mi2S

kokoparkletal said:
Thanks, but the same result, or root or wifi, with 4-11-28 and Mi2S
Click to expand...
Click to collapse
According to this http://www.miui.com/forum.php?mod=viewthread&tid=2119701&page=60, a new version of Lollipop for Mi 2 has been released. It said with the latest version, bugs will be cleared. Check it out!

henry0504 said:
According to this, a new version of Lollipop for Mi 2 has been released. It said with the latest version, bugs will be cleared. Check it out!
Click to expand...
Click to collapse
Working perfectly now, Thanks!:victory:

"No space left on device" ?
At the step
cp /data/local/busybox /system/xbin
I get
cp: /system/xbin/busybox: No space left on device
I tried executing this script to enlarge my partition maybe, but this script didn't work either (http://forum.xda-developers.com/mi-...ript-fix-partition-table-android-4-4-t2878553).
What can I do?

Root Xiaomi Mi 2
Hi,
I was trying to root my new Mi 2 - and this is the first time for me, so having no knowledge i tried to do it following the guide...
downloaded some of the apps to use after it had been rooted to update it to lollipop from kitkat.
first thing i did was follow this guide here:
Root Mi2 with Lollipop 5.0 !!
In Xiaomi 2, you need to carry out special procedures to root with the Android Lollilpop (5.0) version.
***This root kit is not made by me. I just translated it.***
1. Download the Root Mi2 Lollipop.zip (9.17 MB) in the attachments of this thread.
2. Unzip it in a location you like.
3. Open the "Command Prompt.bat" in the folder.
4. Enter fastboot mode in your Mi2 by shutting down and then long-press VOLUME - AND POWER BUTTON.
5. Connect it to your PC with USB CABLE.
6. In "Command_Prompt.bat" in Root Mi2 Lollipop, enter followings:
Code:
fastboot flash boot bootinsecure.img
fastboot reboot
7. It will then reboot. After boot, Open "Command Prompt.bat" and enter followings:
Code:
adb kill-server
adb root
adb remount
adb push busybox /data/local/busybox
adb shell
su
cd /data/local
chmod 755 busybox
./busybox
mount -o remount,rw /system
mkdir /system/xbin
cp /data/local/busybox /system/xbin
cp /data/local/busybox /system/bin
cd /system/xbin
busybox --install .
sync
reboot
8. This will install the busybox and reboot. After it boots, copy the "BETA-SuperSU-v2.19.zip" into the root directory(/sdcard0). Rename it "update.zip"
9. Shut the phone down. Long-press VOLUME+ AND POWER to open recovery. In recovery, choose the "update.zip" to flash.
10. Reboot and you are done!!
You now has root access on L on your Mi2!!
[EDIT] Thanks to zipalign, pointing out the second edition of the tool kit.
As the attachment is over sized, please use the external link below, thanks
I got as far as finishing number 6 where I went to reboot it from the command prompt and it went to reboot but doesnt at all...
now all i can get from a working phone is starting it up like normal and it only gets to the first screen where it just shows the letter m. So I cant actually do anything and it no longer works. I cant go to reset it either - that doesnt work.
The only thing I can access is Fastboot mode...
any help? or have i ruined the phone already??
thanks!

Use MiFlash to recover your phone.
Than you probably have to reuse MiFlash to install CWM.

SuperSU works well for a long time.

Fortinho said:
Use MiFlash to recover your phone.
Than you probably have to reuse MiFlash to install CWM.
Click to expand...
Click to collapse
hey, so ive tried to use MiFlash to recover, installed all the drivers and set it up with Mi Flash, plugged it in in fastboot mode and my computer picked it up, clicked on flash and after about 3 seconds it gave me an error in the status saying "Unspecidied error(0xffffffff: )"
any help?
thanks!

raab93 said:
hey, so ive tried to use MiFlash to recover, installed all the drivers and set it up with Mi Flash, plugged it in in fastboot mode and my computer picked it up, clicked on flash and after about 3 seconds it gave me an error in the status saying "Unspecidied error(0xffffffff: )"
any help?
thanks!
Click to expand...
Click to collapse
Have you selected a MIUI fastboot package to flash?

Fortinho said:
Have you selected a MIUI fastboot package to flash?
Click to expand...
Click to collapse
yea, i downloaded it all and then in MiFlash from my computer selected the right one and checked it all out in the advanced settings...
had a look round online as to what else could be wrong, so got rid of all spaces in the files, changed the directory to C:\ and such...
not sure what else?

MI2 not booting
Thank You for the post,
I tried to root my MI2 device, it got failed at below step
adb root
error: device not found
PLEASE HELP