Hi all,
I've rooted my new (Telstra/AU) N7105T using Odin & ChainFire's autoroot ala http://forum.xda-developers.com/showthread.php?t=1933542. I've installed ROM Manager (+premium) & tried to flash CWM (6.0.2.8), but have struck a problem. The root went fine (and works), but when I try to reboot into CWM-recovery, I get the Samsung splash screeen, then the screen does this weird scroll/wipe thing - and it gets stuck at that point. I have to power-on+vol-up to break out of the boot cycle to boot normally.
There's a possibility that I flashed it twice (screen went to sleep, I didn't see a confirmation on the first time, so tried it again). Unsure if that makes a difference though.
Is the problem that CWM isn't supported on this phone yet, or have I screwed something up?
Cheers,
Brettt
brettt said:
Hi all,
I've rooted my new (Telstra/AU) N7105T using Odin & ChainFire's autoroot ala http://forum.xda-developers.com/showthread.php?t=1933542. I've installed ROM Manager (+premium) & tried to flash CWM (6.0.2.8), but have struck a problem. The root went fine (and works), but when I try to reboot into CWM-recovery, I get the Samsung splash screeen, then the screen does this weird scroll/wipe thing - and it gets stuck at that point. I have to power-on+vol-up to break out of the boot cycle to boot normally.
There's a possibility that I flashed it twice (screen went to sleep, I didn't see a confirmation on the first time, so tried it again). Unsure if that makes a difference though.
Is the problem that CWM isn't supported on this phone yet, or have I screwed something up?
Cheers,
Brettt
Click to expand...
Click to collapse
Hey Brett,
I also have the N7105T. I tried to flash CWM to the phone earlier today too, and I had the same problem with the flashing screen. The only way I could fix it was to boot the phone into DOWNLOAD mode and use ODIN to flash TWRP recovery.. at least now I have a working recovery again.. I wish it was CWM, but at least TWRP works.
You've probably solved it by now considering you posted 2 months ago, so if you have, let me know how you got around the problem
Pete.
I injected root via a very famous KDZ update method proposed on XDA. Then I flashed Xposed Framework via Flashify. My device got struck in bootloop after using the device for 2 months in root. I always had some startup problem after installing Xposed via Flashify {beta}. Sometimes, it would not start but then after hour or so it would. The installation of Xposed framework itself took 10 minutes{It didn't rebooted for 10 minutes}. It was the first time I had this boot problem. I used Xposed for almost 2 months it was working amazing except those boot up issues. It was again and again re-starting on LG G4 logo. I installed stock rom via LG G4 recovery method and miraculously the device started but it again powered of after few seconds and then again same bootloop thing started. I flashed stock rom because I thought it was a bootloop but that didn't fixed the device either. Now everything in the device is factory reset. I can't really remember I ever unlocked its bootloader.
Bootloop can be fixed by re-installing firmware. But it didn't worked. So, I think it wasn't a bootloop. There was some hardware issues. I send it to LG shop they couldn't fix it either. They have send the device to company saying "Its a hardware issue". Did Flashify broke the hardware? Or its some other genuine hardware issue. Flashify ain't did any S*H*I*T*. I am asking this because I will again Flash Xposed via Flashify after I get a new device. I can't simply live without Xposed and its amazing Modules especially ads away for apps and youtube.
I followed this rooting guide. Hopefully this has no bootloader unlocking mechanism.
LG H818N International
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.
Hi there, I have the above device with unlocked bootloader. It was rooted but I had a problem where the tablet kept rebooting but only after it loaded Android. No amount of following guides fixed it and Recovery and Fastboot were throwing g up problems whenever I tried to flash anything.
Eventually, I managed somehow to switch it on to Chinese update cycle I think and update the ROM with the latest official Chinese EMUI through multiple reboot loops (it downloaded about 10% of the update each time before crashing and getting the next chunk of download next time).
So I'm currently on the latest Chinese ROM running android 5.1.1 and it started working again. However the ROM came without gapps included so I flashed TWRP and installed gapps and I'm back to the reboot cycle. It lasted a long time before restarting again though so I'm guessing it's to do with gapps trying to update.
So I'm back to square one again. Any ideas? Is there any kind of log I can provide to help diagnose? I still have TWRP and have access to that without the bootloop starting again..
How did you rooted it?
Hi, so i got someone to root my phone to enable a safetynet pass on an app with Magisk
Suddenly now as soon as the screen turns off via sleep or lock it myself, I will boot into TWRP recovery.
This is becoming a huge problem for me now so im trying to find a solution asap.
Do i unroot my phone and just reset it all to norm? If so how do i go about doing this step-by-step as im not too entirely familiar with root which is why i got someone else to do it.
Re-flash the stock recovery. Even I was facing this kind of issue after rooting. I wasn't able to get my Mix 2 booted after installing TWRP for rooting. However, I got it solved by re-flashing stock recovery.
I was long time ago, but I think it should work for your as well. In you want to root your Mix 2, instead of flashing TWRP, boot it right away, flash magisk to get root access & reboot, you should not get any such bootloop issue whatsoever.