My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Related
First of i'd like to thank the community! I've ran in to numerous issues and have been graciously saved several times.
I'll start of by providing some context in to the issue.
original configuration:
Unlocked - T-Mobile US SIM
AT&T LG E980 factory tot 4.1.2 - flashed using LG Flashing Tool
Root - E980 Universal Root
Unlocked Bootloader - Freegee [Android Marketplace]
Installed Recovery TWRP v2.6 - Freegee [Android Marketplace]
Removed bloatware - AT&T Applications
So from this point the phone was working as expected. I spent hours configuring to my liking and decided to call it a night. Before I called it quits I decided to make a backup using TWRP. Backup took a really long time but it said successful. I left handset plugged in to charger overnight, roughly 6 hours of continuous charging. When I woke up I noticed the phone was in recovery mode. Touchscreen was also unresponsive. I held the power button to allow it to reboot and it rebooted me back to recovery. At this point I knew something was wrong. I attempted to re-install backup files made from previous night, this failed. The phone booted back to recovery. I then installing some zip files I had pre-loaded on to the external SD card, this was CM10.1 and gapps files for E980. I tried this out a few days ago and it was working fine. I decided lets try installing this and see what happens. Install was successful and rebooted. The phone boots back in to recovery. At this point I'm really frustrated. I checked the memory card by running through the TWRP menu. I noticed the file sizes were unchanged but the files were not displayed on both in/ext memory. I decided to finally restore again by using LG Flashing Tool. This by the way has saved my a$$ numerous times. So the one thing I would note, at the 85% when the phone reboots I noticed there was an error, an error I've never seen before. It was a picture of sync icon (large) and android man on top of it and text that said "error 0x123456" I didn't note the exact string. I let it go and monitored the flashing tool, somewhere around 93-95% it rebooted again in to the normal boot sequence. Viola my phone is back to where I started.
So here's some of the questions I had:
How did I end up in the TWRP Recovery boot loop?
Why could I not see the files to install once in TWRP?
Why did TWRP continuously boot back in to recovery mode after successful install of restore?
Why did TWRP continuously boot back in to recovery mode after successful install of CM10.1/gapps zip?
Has anyone seen the LG Flashing Tool error I described above and does anyone have an explanation as to what happened?
Here's my theory on what happened...
My phone was on 4.1.2 as mentioned. I noticed a few times that there was a notification stating the phone had a OTA software update available. The first time I tried to update (already rooted and unlocked) the phone failed to update. The error cited that my phone was believed to be rooted. I paid no attention to this and decided to continue using. Later in the day I noticed the notification again, I opted to try again. The phone updated, or at least tried to. It kept booting in to TWRP Recovery. Nothing I could do could restore it, except flashing using the LG Tool. After experiencing this I knew to leave the OTA alone. I don't know if this is possible but somehow I think the OTA was pushed and forced through while I was sleeping allowing the phone to charge. This is the only time I've seen that behavior. Is that even possible???
Where am I now...?
Phone is restored, I opted to upgrade using the OTA before I start tinkering again. Maybe I won't mess with it at all and leave it alone at this point.
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.
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
BillJake said:
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
Click to expand...
Click to collapse
What is your IFWI version number in bootloader ?
IFWI Version: 0094.0183
BillJake said:
IFWI Version: 0094.0183
Click to expand...
Click to collapse
Flash raw 4.21.40.184 M with AFT in bootloader
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Thank you so much. Fixed my phone.
BillJake said:
Thank you so much. Fixed my phone.
Click to expand...
Click to collapse
Marvelous , drop a thank you to realyoti in the link , hit his thanks button too.:good::highfive:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
threehappypenguins said:
I unlocked an H812 (2017 version... serial starts with 702) several months ago and successfully flashed a stock Nougat ROM. Everything was working great until now. This past week, it randomly started shutting down. Yesterday, it got to the point where I could no longer boot into the OS. I think I got to the unlock screen once, and then it shut off. Now it simply boot loops. There is no SD card in the phone. I couldn't figure out how to get into Safe Mode from TWRP, so I did a factory reset. Still boot loop. I then did a factory reset + wiped the internal drive, and then reinstalled Stock N ROM. Still boot looped. Tried reinstalling the ROM again. Still in a boot loop. I know LG G4 has hardware issues. However, I can boot into TWRP just fine, the temperature doesn't look crazy at all, and it can stay in TWRP indefinitely without shutting down.
Something I noticed after wiping the internal drive is that when I'm finished installing N stock, it says it's successful, but when I checked the File Manager to look in the internal SD card, it still shows it as blank (with the exception of a TWRP folder). Is this normal? Isn't the operating system supposed to be installed on this? Why is it telling me that it's finished installing, and yet nothing is there. For fun, I tried booting up, and I'm still in a boot loop. But I assume it's because I have no OS? Or does the internal sd populate with files upon bootup?
I also used used fastboot and flashed the 4 core image (H811 because GPT compatibility said H811). And I also flashed the 4 core TWRP. I tried installing the stock N again, and file manager still shows no files or folders on internal sd except for TWRP folder. Phone still stuck in boot loop (no OS)?
Please, someone help!
I spoke with LG in case it is a motherboard issue, and they said they only replace the 2015 and 2016 model motherboards for free.
Click to expand...
Click to collapse
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
sdembiske said:
Refer to FAQ # 5a in the UsU unlock thread.
Did you do a clean flash of the rom? If not, wipe cache, dalvik cache, system and most important, format data, before installing the rom again.
I note you did not mention flashing the appropriate gapps for the rom version you're trying to boot up. Maybe an idea if you didn't.
If all else fails, go to IRC (Support / IRC Channel paragraph in the UsU unlock thread OP) and get help directly from steadfasterX.
Click to expand...
Click to collapse
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
threehappypenguins said:
Yes, I did a clean flash. wiped cache, dalvik cache, system, and also formatted data (yes, formatted, not just wipe). I did not flash gapps because I flashed a stock Nougat ROM (the same one that has been working for months).
I'm really hoping to know whether it's normal for file manager to be blank and not show the Android, data, folders and all that. I want to know if those folders populate upon a successful bootup, or if they're supposed to be there right after the ROM says it's successfully flashed. That way I can tell if there is an issue with the ROM not installing (which if that is the case, of course I can't boot up).
I have been posting on the UsU thread, but steadfasterX said to flash 4 core boot rom and 4 core TWRP. I did that, but still no boot up. And I *think* there is no boot up because I have no operating system? Again, what is supposed to be in file manager after a ROM flash? I asked steadfasterX but have not gotten an answer.
Click to expand...
Click to collapse
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
sdembiske said:
I know when I've clean flashed a rom in TWRP, I show no files in Internal in the USB connection screen. If you didn't get an error indicating no OS installed, I wouldn't worry about that for now.
Again, refer to FAQ #5a. Did you immediately flash the baseband file after the rom flash? Did you re-install the N modem? etc, etc. You may have to re-install the bootloader stack etc. Go through all the steps.
And again, go to IRC if all else fails.
Note: Please learn to use the Thanks button (bottom right of post), when members answer your questions or provide useful information when trying to help. It's an XDA courtesy - please learn to use it.
Click to expand...
Click to collapse
Here's what I've done now at this point. I tried creating and flashing a 2 core boot image via fastboot, and then flashing the 2 core TWRP. Still bootloop.
I flashed the v29a N modem and UsU kernel for my device (H812), then went to TWRP and flashed stock N ROM again. Still bootloop.
I flashed N stock modem again, then baseband package for my model. Still bootloop.
I'm about to extract my MM modem and flash that.
Beyond that, I don't know what to do. I had zero issues with the UsU method originally and everything went fine and has been fine for the last couple of months since I did it.
Well, roadblock again. I attempted to extract modem from the kdz with SALT in FWUL, and after a while, I get a popup window that says: "This KDZ has an ARB of: arb-detect-error" and then it says "Select partition(s) to EXTRACT:"
Except there are no partitions to select. And my only options are "Deselect All" "Extract" and "Abort." If I try "Extract," I get the error, "No partition selected or abortioned by user."
I did make sure I had the latest version of SALT.
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Code:
fastboot flash modem modem_32768.img
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
threehappypenguins said:
Gave up on salt to extract the kdz and turned to Windows. I didn't know what else to do. I was able to extract the .dz, and then extract the modem_32768.bin file. Transferred it to FWUL, renamed it modem_32768.img, and then typed
Rebooted, and still have boot loop.
I'm going to investigate this bootloader stack thing (I don't even know what that is). But again, I really don't understand why this all worked fine for a couple of months.
Click to expand...
Click to collapse
Read about the ilapo it can't be fixed by software it may just help to enlenghten life.
Sent from my OnePlus 6T using XDA Labs