Hello !
I'm trying to unbrick the i9195 of a friend.
Basically it was on official stock ROM, and from one day to the next it didn't go past the bootloader, stucking into a bootloop.
When trying to enter recovery, it bootloops and still gets stuck in bootloader.
I can only flash files with ODIN. I tried to flash another Stock ROM, and I tried to flash TWRP recovery. For both tries, I can't boot, whether it's system or recovery.
I don't even know what Android version was installed before it crashed, I guess it doesn't matter. Bootloader displays "V2" so it might be 4.4.2
I've some experience in flashing, Qualcomm HS-USB QDLoader 9008 etc. but this time I think that's beyond me.
Maybe I forgot some steps, so I'm looking for some help or any information... It seems like a faulty hardware for me
Thank you in advance and have a nice day !
Cheers
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.
I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?
Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...
This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.
got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.
I tried LGUP but it could not recognize the device while this was looping.....a bad experience......
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.
Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.
iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.
croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.
I will release a fix for that soon. Check the twrp thread for updates on this.
Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks
Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.
Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:
Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.
Hey guys,
I would have liked to get the OREO update, because it said every time is up-to-date, and I wasn't patient. because all of these already get it, and the battery life was terrible with, and I have just 30 days to cancel the phone if I'm unsatisfied with it, so it was urgent for me to update and try it.
But I didn't know enough from the newest devices, so that I need unlocked bootloader to flash STOCK ROM or ROOT or for flash RECOVERY
Mine is XT1789-06, I tried to flash first this ROM:
https://androidfilehost.com/?fid=962187416754456314
It didn't tell this is TMO. :/
This changed my baseband to TMO and my boot image to T-mobile, after I didn't have signal and the fingerprint sensor didn't work.
I wanted fix it with RETAIL ROM flashing.
I tried to flash this: https://androidfilehost.com/?w=files&flid=241773
After that my phone didn't boot, says your device is corrupt.
Cause this I tried to flash back the previous version so this: NASH_RETAIL_7.1.1_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from here https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
But no result. The baseband stucked on TMO, the phone is not start up. Fall back to fast boot mode.
After and mean while these things I tried many things.
The Motorola Device Manager isn't working at all.
The Software Upgrade Assistant what the phone want when show boot up failed message isn't working just say processing device information and isn't going further. I don't understand why the phone ask it, because that is for verizon phones.
The RSD lite says the model name is Fastboot nash S and isn't start to flash anything, when I press the start it says the phone failed to switch to fastboot mode, but it's in that.
I tried already flash more different ROMs, but didn't work one of them .
Recovery is unable, the phone isn't rooted, the bootloader is locked, however sometimes it showed ""Your device software cannot be checked for corruption. Please lock the bootloader", but I checked in the powershell and in fastboot mode I looked what phone says, so it's locked.
I was thinking maybe if I unlock it will solve the problem, but I can't turn it on, so the developer options are unavailable and I don't know maybe it won't help, if I can do it somehow.
Now if I want turn on the phone it's going to fastboot mode right away or say your device is corrupt... and after.
I can't try flash it through Qualcomm 9008 because the PC recognise the device for fastboot device.
In the device manager the computer shows Motorola ADB interface.
I try to unbrick for 3 days, please help me.
Thanks a lot in advance.
Same here, if you find anything out DM me
I already contacted with the phone, I will bring back to Repait it.
I couldn't find out nothing, I tried everything what was possible.
i think i found a solution i just dont know how it works exactly, something to do with a batch file and a full flash of the phone
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 im going to try this and let you know
Hi Team, I was using a custom rom aex based on pie for a while now. Suddenly my phone rebooted and stuck on screen:
Start up Failed:
Your device didn't start up successfully. Use the software repair assistant on computer to repair your device. Connect your device to your computer to get the software repair assistant.
I can't reboot into twrp, not able to flash stock rom using adb fastboot (fasboot commands working fine, but after restart coming to same screen).
Used rsd lite on win10 but, my device not getting detected. Tried LMSA - fails at 68% on flashing. Not able to do anything for the past 2 days.
Please help. Really appreciated.
Do you have your unlocked bootloader?
As long as you have your bootloader unlocked, it is possible to unbrick the phone.
If you don't, then your phone is irreversibly toasted.
Hello,
I'm facing a bit of a weird situation with my K20 Pro. I just went to update it after a long time ( unlocked bootloader, TWRP and custom rom Revolution X). At the moment of installing, it was usually going to TWRP and rebooting and all good, this time, no. Just black screen. And since then, it's stuck in bootloop, and whenever i try to access recovery mode it just crashes. I tried to reinstall twrp trough fastboot but the same is hapenning.
I tried to flash the OEM OS too trough miflash but after 0s is says '' success '' but as you could guess it : nothing.
I already had others soft bricks on other phones but nothing like this, if anyone has a guess ?
Update : Could access TWRP for the first time after trying again to flash the official rom
+ now says that no OS is installed (