This is a guide on how to fix a bootloop on your T-Mobile G2 if you don't have a suitable backup (i.e. md5sum mismatch won't let you flash, you forgot to make one, etc.) This procedure also works if you want to unroot your device for warranty purposes or if you flashed something that can't be undone by flashing another ROM (rare, but it can happen)
WARNING: You WILL lose your root. The possibility of bricking your phone by entering a typo in the commands are somewhat high. If you don't wanna take risks, then find another tutorial.
THIS TUTORIAL DOES NOT WORK WITH THE HTC DESIRE Z
Prerequisites:
-ADB installed and fully functional.
-My misc.img file. You can grab it from this link: http://www.mediafire.com/?80r8dkkqzcwszdb
-The stock ROM (PC10IMG.zip) Grab it from this link if you don't have it: http://www.megaupload.com/?d=20Y1ELB0
-Clockworkmod Recovery
Let's begin, shall we?
1. Boot into Clockworkmod Recovery (Volume+Down, then scroll down to recovery and press the power button)
2. Place the misc.img and PC10IMG.zip files in the same folder where ADB is located, and enter the following commands:
Code:
adb push misc.img /sdcard/misc.img
adb push PC10IMG.zip /sdcard/PC10IMG.zip
(alternatively, you can go to Mounts and Storage, mount USB storage, then transfer the files that way)
3. Now, we're gonna use the dd command to edit the misc partition. Enter the following EXACTLY as it's written over here:
Code:
adb shell
su
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
You should get a message saying 512 records out or something.
You might ask "Why can't we use misc_version instead of the dd command?" Well the answer is that misc_version doesn't really work in recovery mode as far as I've tested. You can try misc_version, and if it works, congratulations!
4. Reboot into HBoot mode (Power off, then power+volume down)
5. Wait for the update to flash, and viola! You're now out of that pesky bootloop. You're unrooted, but then again you can start over.
I rooted my phone and installed FreeGee to install the TWRP bootloader. Followed all the instructions, but now every time I power on the phont it goes to recovery mode and I can't get out. Even if I reboot it always goes to recovery. It says this: Android system recovery <3e>
I tried restore using LGNPST but it still only boots into this screen. I can't get back into Android. Help please
davelee1054 said:
I rooted my phone and installed FreeGee to install the TWRP bootloader. Followed all the instructions, but now every time I power on the phont it goes to recovery mode and I can't get out. Even if I reboot it always goes to recovery. It says this: Android system recovery <3e>
I tried restore using LGNPST but it still only boots into this screen. I can't get back into Android. Help please
Click to expand...
Click to collapse
I had this same issue last night. I ended up using LGNPST on the entire 800MB firmware .bin for 4.1.2 in order to get back to it. I lost all my apps and whatnot, but I thought it was worth it to have my phone be a phone again.
The issue is the reboot to recovery flag is set in your misc.
Run these commands from an adb shell to clear it:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/data/media/misc-bad-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
bump can someone help me out with this i cant even select anything
I'm trying to backup my phone before making any substantial changes to it. I've done the de la Vega root and made the AT&T APN changes and that's about it. I wanted to use the ADB fastboot commands to load CWM temporarily to do a backup. So I've installed the sdk and downloaded the CWM 6.0.4.5 to the platform tools folder. I found an article on androidcentral which explains how to do this on a GN (which looks a lot like an S3) which instructs on how to use the fastboot boot xxxxxx.img command. I'm stuck before that trying to download the CWM to the phone.
Not sure what I'm doing wrong. the instructions suggest booting into the bootloader by using the ADB reboot bootloader command. That puts it in a "downloading... Do not turn off target" screen which is captioned Odin Mode and on the bottom of the text it says Write Protection Enabled. Did I miss a step with Sudo?
the next step is described as running fastboot devices to see if the computer sees it. This gets no response but the prior reboot command would still work. Finally it ignore the fastboot boot command as it did the fastboot devices command.
Can anyone tell me where I've dropped the ball and what to do?
bump
You can't use fastboot with Note 3. It's not supported. But you can run adb backup I guess. Also you can image partitions with dd but not familiar with it. Just search the forum...
YOURE LOOKING UP DIRECTIONS FOR THE WRONG PHONE!!! STOP NOW! Never...ever use directions meant for another phone unless it's been confirmed by others that it works; or unless you like being a pioneer.
What exactly are you trying to backup? Your EFS, FSG, modemst1 and modemst2 should be the only backups you need. Everything else is "rebuildable" yourself. If you killed the bootloader msmercy42 started a N900T hard brick unbrick thread. If you have a soft brick you can always Odin the stock firmware.
CAREFUL when playing around in adb. One wrong number means a hard brick. Meaning if you meant to type mmcblk0p3 in a "dd if" command and instead typed mmcblk0p2 you might end up with a device upon reboot shows a completely black screen (hard brick).
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
Help! Please
I have rooted my phone thru odin mode, downloaded a rom to install and it wont let me it says on my screen downloading do not turn off target, what can i do? nothings happening to the phone its been stuck on this screen for an hour.
As far as I know, you install a ROM through a custom recovery, not through Odin.
Sent from my SPH-L900. Please hit the thanks button if I helped you out!
When I plug it in into my pc, nothing comes up. I tried going into download mode to download the drivers but it fails everytime. Help please.
Also, here's a little backstory. I accidentally tried installing the new software a month ago when my phone was rooted which caused the phone to be stuck in recovery mode. I fixed this problem by doing this:
"before trying anything else just type in these commands
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
got help from the IRC xda-devs for the second step to complete the fix."
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
However, now my phone doesn't have recovery mode, but it saids that I'm still rooted. I just want to go back to stock firmware. Please help thank you
Lgg3root.com
Shows a video on how to unroot and go stock stock. Then start fresh
BAD ASS G3
We I accept the update to lollipop my phone restart and now is dead...
My phone was a twrp recovery but can't access now... No download mode works...
No screen turn on...
Only my Pc recognize on hardware QHSUSB_BULK
LG TOOLS not reconigce....
Please and help to resurrection my phone...
celtichazard said:
We I accept the update to lollipop my phone restart and now is dead...
My phone was a twrp recovery but can't access now... No download mode works...
No screen turn on...
Only my Pc recognize on hardware QHSUSB_BULK
LG TOOLS not reconigce....
Please and help to resurrection my phone...
Click to expand...
Click to collapse
You can never take an OTA update with a custom recovery. See this thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 it may help.
acefsw said:
You can never take an OTA update with a custom recovery. See this thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667 it may help.
Click to expand...
Click to collapse
My phones don't enter in to download mode screen is turned of all the time
celtichazard said:
My phones don't enter in to download mode screen is turned of all the time
Click to expand...
Click to collapse
its bricked, you have to do some research on what you can do......if anything
never take an OTA if you are not 100% stock
decaturbob said:
its bricked, you have to do some research on what you can do......if anything
never take an OTA if you are not 100% stock
Click to expand...
Click to collapse
all ready do a research all day and no luck to fix
So when the phone is off and you hold the volume up button and plug in the usb it won't go into download mode?
vel0city said:
So when the phone is off and you hold the volume up button and plug in the usb it won't go into download mode?
Click to expand...
Click to collapse
Yeah, I'd at least try a battery pull, have all the drivers/downloads etc. ready for TOT. make sure the usb is plugged in to computer side on a usb 2.0 port, then attempt volume up/plug usb into phone.
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
TheCoutures said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
His screen doesn't turn on, so no TWRP access. He needs download mode or likely a jtag if he can't get that. Battery pull might help or be absolutely useless, especially since his computer is just recognizing the qualcomm chip
Here's some research links celtichazard https://www.google.com/search?q=QHS...458045j0j0&sourceid=chrome&es_sm=122&ie=UTF-8 don't give shady strangers money to unbrick
---------- Post added at 12:35 AM ---------- Previous post was at 12:20 AM ----------
Read this http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
TheCoutures said:
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
Sorry but the phone dot turn the screen thanks
celtichazard said:
Sorry but the phone dot turn the screen thanks
Click to expand...
Click to collapse
Read the links posted above, especially the 2nd one. Also, https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ is for a one + one phone, not ours, but explains some of what it takes to restore the files for the chipset
acefsw said:
Read the links posted above, especially the 2nd one. Also, https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/ is for a one + one phone, not ours, but explains some of what it takes to restore the files for the chipset
Click to expand...
Click to collapse
Thanks dude but the only problem is I cant find the right driver to make it work
this is my device manager detect whe I plug the phone
Thanks TC the fix worked. Thought I had OTA disabeled