Database Users

Freeze on system wipe

I was doing a system wipe to install my first ROM on my G2. I installed TWRP 2.6.3.2. I started doing a system, data, and dalvik wipe and it froze on the system wipe. I let it sit for quite some time and it was still frozen. Gave it a reboot and now I'm stuck on the LG logo. I can't get it to boot into the stock rom, and I can't get it to boot back into TWRP. This is on a D801 T-Mobile model. Can I get some help please? Thanks.
Crisis averted. I thought I wasn't able to get into download mode, gave it a couple tries, and I'm in... Now I just hope that I can salvage it from here.
I am curious, though... Why would it just freeze on a wipe? I hope this doesn't happen again when I try it tomorrow.
Went back to full stock. Rooted again. Installed TWRP again. Tried doing a cache wipe. Same issue... Any idea about potential causes?

i have almost the same problem with my friend!
i 'm stuck on lg logo. i can get in download mode but i can't finish the process to flash the stock rom...it stops when the programm tries to install the rom to the phone. what did you do to flsh the rom?

l33t p1mp said:
I was doing a system wipe to install my first ROM on my G2. I installed TWRP 2.6.3.2. I started doing a system, data, and dalvik wipe and it froze on the system wipe. I let it sit for quite some time and it was still frozen. Gave it a reboot and now I'm stuck on the LG logo. I can't get it to boot into the stock rom, and I can't get it to boot back into TWRP. This is on a D801 T-Mobile model. Can I get some help please? Thanks.
Crisis averted. I thought I wasn't able to get into download mode, gave it a couple tries, and I'm in... Now I just hope that I can salvage it from here.
I am curious, though... Why would it just freeze on a wipe? I hope this doesn't happen again when I try it tomorrow.
Went back to full stock. Rooted again. Installed TWRP again. Tried doing a cache wipe. Same issue... Any idea about potential causes?
Click to expand...
Click to collapse
Its well documented. Go into settings and choose "rm -fr" or whatever it says. Or flash 2.6.3.3.

By using search you would've gotten an answer so much faster....
Sent from my ZTE Blade using XDA Premium 4 mobile app

Help! Updated while rooted, stuck in TWRP

So I am fairly new to rooting and didn't know that it's not a great idea to do an OTA update while you're rooted. So I did just that and when prompted to restart the phone, it did and loaded directly in to TWRP. I tried to just reboot from there and it kept going back to TWRP. So I tried to recovery from a backup, same thing, right back to TWRP. Also, I can't get into download mode. What do I do?

floydmcscroops said:
So I am fairly new to rooting and didn't know that it's not a great idea to do an OTA update while you're rooted. So I did just that and when prompted to restart the phone, it did and loaded directly in to TWRP. I tried to just reboot from there and it kept going back to TWRP. So I tried to recovery from a backup, same thing, right back to TWRP. Also, I can't get into download mode. What do I do?
Click to expand...
Click to collapse
This should help. http://forum.xda-developers.com/showthread.php?t=2451696

You need to first download the kdz and lg flash utility with drivers.
Install drivers
The factory reset deleting system, cache, internal sd.
Then shutdown your g2.
Start to downloaded mode connecting your g2
Flash kdz & voila... Done
I too bricked my phone before. My flashing stuck at 49%. Recovered using above method, all is well now
This works 1000%. I bet on it. Just remember to wipe the phone completely before flashing. You will return to stock with unrooted status in download mode. U will have your warranty back too
Sent from my LG-D802 using XDA Premium 4 mobile app

TWRP recover unresponsive after OTA update

I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.

I had same issue with TWRP in the past and never found a solution, to run into the ROM directly and escape the loop thing try
Power Button and volume -
Then continue and it will boot up normally.
I had to change to Clockwork-mod recovery after this.

einsiol said:
I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.
Click to expand...
Click to collapse
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505

einsiol said:
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505
Click to expand...
Click to collapse
i meaned the one i posted in s4 twrp page :-O NOT i9305 (wich is s3lte not s4)
Sent from my Xperia T using XDA Free mobile app

Zenfone2 works but no recovery

OK I had an issue awhile back where my phone really took a crap. Not sure what happened, it is not rooted. But it would not boot, would just go to a dead android. No recovery, nothing. So 2 days of playing around with different programs, I finally got it to boot normally and all seemed well. Now I got a message for a new update and it reboots and does nothing. If I check for updates it downloads it again and does the same thing.
So I tried to boot to recovery and I don't have a recovery now. I get to the fastboot screen(I think that's what it's called) and select recovery. Just reboots. I connected to my laptop and issued the adb reboot recovery, same thing, just reboots. Adb reboot bootloader works however.
So if I have no recovery, how do I re install the recovery? I'm to the point where I might just buy a new one, as fast charging doesn't even seem to work anymore but I'd rather not, I really like this phone.
Thanks for any help you can give.

I believe if you download the proper firmware for your phone, you should be able to extract the recovery image and flash it through ADB. ( fastboot flash recovery recovery.img). As long as you have Asus drivers and ADB installed, you should be able to. I'm sure this is how I reflashed my recovery after I accidentally wiped it.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

Thanks Quicksilver, I'll give that a try. I was a lot more up on all this stuff a few years ago when I used to root every device I got. I've been happy with the stock Zenfone 2 so I haven't messed around with this stuff for a long time!

You're welcome Bluze. I hope this for you.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

That didn't work. It seemed to flash recovery.img ok, but still no recovery mode.

Wow, I don't know what exactly worked but I have a recovery now. I finally just bit the bullet and unlocked the bootloader, then used a tool that supposedly roots and installs Clockworkmod. Well, it didn't work. Sort of. I was able to get to cwm recovery one time before I rebooted but it was all back to "normal" (no recovery and not rooted). Rom Manager would hang when I tried to reboot to recovery. So I downloaded SuperSU and installed it manually. Ta Da! Root! Tried to reboot to recover and dead android. Pressed power and volume up and for the first time, it rebooted to stock recovery! Still no CWM, and I'm not sure it will work on Zenfone 2 but hey, I got my recovery back! Now I won't be able to do OTA upgrades but at least I can do them manually!
Quicksilver, your suggestion should have worked. It didn't, but thanks for the help!

I need your help guys. (bricked nexus 6p)

Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]

I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.

Yea just flash stock image I had this happen to me before and flashing stock image fixed it.

Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk

im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.

i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.

Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.

this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:

pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??

im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.

I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk

im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.

Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!