I had TWRP 2.8.7.0 working fine, but tried upgrading to 3.0 -
That had a weird issue where twrp would show the splash screen, the screen would intermittently turn off and on, and keep showing the splash screen, but never entered recovery.
Decided to revert to 2.8.7.0 using flashify... Now when I try to create a nandroid backup in 2.8.7.0, it starts working and then shows the twrp splash screen, and as in 3.0 the screen intermittently turns on and off.
Anyone experienced something like this before? Kind of unsure how to proceed.
Update: now it does the screen intermittently flashing on and off, stuck on twrp flash screen just trying to enter twrp.
Also tried removing SD-Card with no luck
Update2: The behavior is pretty much identical to what's seen in this video https://www.youtube.com/watch?v=Kr46ugrpL6U , except it only happens in recovery (I can enter the os normally if i dont attempt to go into recovery)
This has been common problem with twrp from the looks of it. Right now when I boot to twrp 2.7.x.x I get stuck at the twrp splash. However my problem I can't find any info on your there looks to be two terminal commands you can run to fix it..... Seeing this post I wanted to ask about mine at the same time couldn't hurt do to its starting to look related to the recovery boot loop. But like I said I'm just stuck at it not looping.... very odd.
---------- Post added at 03:14 PM ---------- Previous post was at 03:02 PM ----------
OK mine was sad and simple.... I formatted my SD card back to portable storage and poof it now boots to recovery don't know if it could be related but it's worth a shot!
cmjester6421 said:
This has been common problem with twrp from the looks of it. Right now when I boot to twrp 2.7.x.x I get stuck at the twrp splash. However my problem I can't find any info on your there looks to be two terminal commands you can run to fix it..... Seeing this post I wanted to ask about mine at the same time couldn't hurt do to its starting to look related to the recovery boot loop. But like I said I'm just stuck at it not looping.... very odd.
---------- Post added at 03:14 PM ---------- Previous post was at 03:02 PM ----------
OK mine was sad and simple.... I formatted my SD card back to portable storage and poof it now boots to recovery don't know if it could be related but it's worth a shot!
Click to expand...
Click to collapse
Unfortunately I don't think it's the same, because I still have issues even with the SD card removed. Also, I'm on lollipop if that helps.
I remember that happened once to me in a Samsung device. But eve worst, my device was unable to boot into OS. What I did was put download mode and flashed any version that was easy to root. Then, root, flash recovery TWRP, and then used a nandroid backup. You can apply same procedure on this LG G3 and you'll be back on the game.
Enviado desde mi LG-D851 mediante Tapatalk
Related
Let me start off by saying I'm pretty noob with all this stuff and I just need some instructs on what to do.
When I first got my Kfire I installed firefirefire on it so i could install some roms, later on I tried installing CWM and that's when I started having problems. After trying to install CWM my kindle fire just boots up and shows the FFF logo then reboots When I plug the kind into my computer windows doesn't pick it up and I can't do anything actual device since it reboots every 2sec so I'm unsure how to fix it.
smitty5569 said:
Let me start off by saying I'm pretty noob with all this stuff and I just need some instructs on what to do.
When I first got my Kfire I installed firefirefire on it so i could install some roms, later on I tried installing CWM and that's when I started having problems. After trying to install CWM my kindle fire just boots up and shows the FFF logo then reboots When I plug the kind into my computer windows doesn't pick it up and I can't do anything actual device since it reboots every 2sec so I'm unsure how to fix it.
Click to expand...
Click to collapse
CWM doesn't work on KF, it's a known problem. Don't panic though, do you have the latest FFF 1.4a from hashcode? It has an option to recover from bootloop issues. You need to use TWRP to flash ROMs, which you can get using the kindle fire utility found on XDA.
cwmr does work on the kindle fire.
BUT there is a problem with a certain version of chip's ware levelers and a certain version of cwmr. (it only effects 1 type of chip). this only effects the chip partitions when a wipe or restore are performed.
Did you ever get into cwmr (and perform a restore or wipe?) if not then your in the clear from the superbug. & what version of cwmr did you try to install?
if it reboots after only 2 seconds, I would say the battery has depleted. (make sure to charge (with stock charger 1.8A) for at least 3/4 hours.
then i would use kfu to reinstall drivers etc and reinstall fff1.4a & twrp 2.1 then reflash a new rom.
follow this thread (if it charges).
read read & then read again (your driver issue should lie in there).
when you have adb & fastboot working we can have a look at what chip you have and if you have any damage.
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
sorry forgot link http://forum.xda-developers.com/showthread.php?t=1552547
there you go
I am currently having trouble with my phone, it works fine as long as i do not turn my phone off. If I turn my phone off it seems to go into a hard brick, and I cannot get back into my phone unless I use a homemade jig to get into download mode and there for getting back to my phone rebooting. I noticed this problem right after I downloaded the teamwin app to update my recovery, but I accidentally choose the "I9300" recovery instead of my phone "I747". That initially put my phone into the first hard brick that I encountered, then with the help with www youtube com/watch?v=y5_yoJilLe0, I was able to get my phone and flash the correct recovery as well as a new rom. So my question is, how can I fix this problem of not turning off my phone and making it go into a hard brick? Any help will be much appreciated, and I am sorry if this is in the wrong place, this is my first post.
I do have a nandroid backup that I have tried and it still has this problem
Further testing I have figured out that I have to have my SD card that has the software to unbrick(using the method in the youtube video) in my phone for it to turn on. With my SD card out it acts just like a hard brick.
Sounds like a bootloader problem...
You probably flashed over sbl1. Its not included in firmware updates so the odin flash will not help.
Thats just a guess though. It depends on what partition the i9300 stores its recovery. It may be a different one from sbl1.
---------- Post added at 04:36 AM ---------- Previous post was at 04:28 AM ----------
Ok, I just checked and you wrote over the rpm partition (mmcblk0p6). This is included in the firmware package so flashing with odin should have fixed it. Did you not flash the firmware? You said you followed a video, but you should use the instructions we have in this forum.
It also helps to know what build your current firmware is.
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
MrDelicious said:
Am unlocked, S-off, rooted, otherwise stock 4.4.3. Was trying to update to the latest 4.4.4 so replaced TWRP with stock recovery. First attempt failed, red triangle. I figured this was due to Viper4android and the buildprop tweaks that required so I uninstalled the driver and replaced the buildprop with stock version. At this point, I had turned fastboot on and USB debugging off.
After this the phone will not reboot to OS. I can get the HTC screen to flash for a few seconds by pressing Power+VolUp, which then goes black and nothing happens. I can also sometimes get to bootloader, but cannot get my PC to recognize the phone in ADB so not much luck there.
I assume something went wrong with Viper4Android uninstallation or I screwed up the buildprop replacement. Am out of ideas, should I do a factory reset in the bootloader? I do have a TWRP backup, but I can't replace the recovery or anything else through ADB for that matter.
Edit: I did notice in bootloader that OS gets no version info, so something obviously gone wrong there. I just have no idea what to do without ADB. I guess I'm screwed.
Thanks for any help!
Click to expand...
Click to collapse
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
Click to expand...
Click to collapse
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
str8str said:
Go to captain throbacks site for our m8 he has twrp fishable zips that you flash in your bootlloader. After that you can do a restore or reflash whatever. It might not show the proper os in bootlloader but don't worry bout it you can fix after. You'll be able to see what one your on after you get up and running again. Hopefully that should work. Just make sure you follow the directions correctly on his site. Just Google captain throwback.
---------- Post added at 02:02 AM ---------- Previous post was at 01:57 AM ----------
Also best way to update your firmware is thru a bootlloader flushable zip as well you don't have to worry about restoring stock recovery and doesn't matter what rom your on etc. There are threads on how to do it very easy.
Click to expand...
Click to collapse
Thanks! I shall look into this.
Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
cthulhu_tentacles said:
Hi all, my nexus is a very poorly little thing at the moment. Bootloops on the google screen on start and can't get to recovery from the bootloader. I have tried flashing with a stock rom but it is still bootlooping. I'm assuming the next step is to try flashing the bootloader, something I'm very scared of doing without being absolutely sure that I'm not about to turn my critically ill nexus into a completely dead nexus. Could anyone give me the exact commands I need to use to do this?
Click to expand...
Click to collapse
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
DroidIt! said:
I think all you need to do is reflash the recovery. Your bootloader may be fine. Did you accidentally erase your recovery partition? What were you doing when you first saw the problem?
Click to expand...
Click to collapse
I didn't do anything unusual. Went to sleep. Woke up in the morning and it was frozen. Gave it a long press on the power key and has been stuck ever since. Just tried the one-click restore here http://forum.xda-developers.com/showthread.php?t=2381582 and it is still bootlooping after that.
OK, I'd download a recovery to your computer and fast boot flash it that way. I've not used that tool, but I did the same once. I accidentally erased my recovery partition. So I just redownloaded the latest twrp .IMG and did fast boot flash recovery and all was fine. That's what I'd suggest for a start.
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
Ah I see, that tool wipes your entire device. So I'd go here https://developers.google.com/android/nexus/images and download the latest factory image. While in your boot loader, connect to your computer and run the .bat file from the download. That all return you to stock. Be patient it takes some time, but that should solve your issue.
Thanks, giving it a shot now
Yep, download, unzip, connect to computer while in bootloader, and double click the .bat file. It will go through a series of flashings. It's restoring everything to factory. Just leave it plugged in until it starts to boot up. ?
i had installed custom recovery and i was going to install the lollipop pac-rom (http://forum.xda-developers.com/showthread.php?t=2348415) after using cmd to boot the boot.img from the rom, the guide i had been reading (http://forum.xda-developers.com/showpost.php?p=38933080&postcount=1) had said to reboot and i did so. After the reboot my phone had gone through htc logo then a black screen, the guide had also said "wait some minuets" so thats what i had assumed it was doing. after leaving it alone for about 10 minuets i had thought there had been an error. i tried booting the boot.img from another rom to see if it would even start, it now gets to the verizon symbol stays on that for a while then restarts. if there is any way for me to access my storage to put another rom on the phone or a way to revert it back to stock (preferably keeping the custom recovery) that would be appreciated very much.
fancy feast said:
i had installed custom recovery and i was going to install the lollipop pac-rom (http://forum.xda-developers.com/showthread.php?t=2348415) after using cmd to boot the boot.img from the rom, the guide i had been reading (http://forum.xda-developers.com/showpost.php?p=38933080&postcount=1) had said to reboot and i did so. After the reboot my phone had gone through htc logo then a black screen, the guide had also said "wait some minuets" so thats what i had assumed it was doing. after leaving it alone for about 10 minuets i had thought there had been an error. i tried booting the boot.img from another rom to see if it would even start, it now gets to the verizon symbol stays on that for a while then restarts. if there is any way for me to access my storage to put another rom on the phone or a way to revert it back to stock (preferably keeping the custom recovery) that would be appreciated very much.
Click to expand...
Click to collapse
edit; There is a separate Verizon HTC One (M7) forum
roms may not be cross compatible.
see
Frequently Asked Questions
This thread will be moved to Verizon HTC One (M7) Q&A, Help & Troubleshooting
---------- Post added at 03:00 PM ---------- Previous post was at 02:52 PM ----------
see edit.
Our mount points are different. Please install one of the roms in this section to get your phone up and running again. You can also run an ruu if you wish to go back to stock hassle free. Second spoiler of Q8 has a link to the ruu with instructions.
Sent from my HTC6500LVW using XDA Free mobile app