Hey,
I had AOSP installed on my ascend p6, everything working no problems at all.
Suddenly when I was a week on vacation when my battery died it wouldn't get passed the rom loading screen.
I have TWRP 2.7 and have wiped everything and everything over and over but nothing is working. I am now trying to install The lastest aosp sincde OMNI and CM11 didn't work.
Any help how to fix this? it keeps happening at every rom I install.
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
UPDATE: Okay somehow after rebooting it around 20 times with fastboot, recovery and other combinations it is now booting I think. Praise the lords. It is now optimizing the apps
I have no idea what I did but I will post an update when it is done optimising
UPDATE UPDATE: Okay the weirdest thing just happened and I don't get this at all... I have wiped my whole phone like 5 times. with itsto and exsto. but somehow I now boots with all my apps, settings and launcher intact and inplace... I even installed multiple roms trying to make it work. WHAT IS THIS MAGIC?!
I know I shouldnt do this but I am going to re-install twrp 2.6.*.* and then pushing it to 2.7. Wish me luck! (following the excact instructions to make it work haha)
UPDATE UPDATE UPDATE: Okay, After seeing the wi-fi not turning on I tried rebooting my phone now it is stuck at the huawei ascend screen.
TomTheTiger said:
Little update:
I just tried reverting from twrp 2.7 to stock boot and recovery and I think I just bricked my device Can;t get passed the huawei ascend screen.
I wanted to reinstall the 118cn from stock recovery. is there anyway to fix this? Thank you!
Click to expand...
Click to collapse
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
warea said:
Jelly Bean China stock roms can brick device (lots of users on xda got their device bricked). If you wanted to unlock, best to use KK China.
Click to expand...
Click to collapse
Will try! I thought I was passed this haha. When It starts i'll try to figure out a way to install it probs trough adb fastboot. since I can't get to the recovery screen with buttons
Update: Okay I managed to boot recovery up trough adb, It automatically started installing the update.app package.
I am now hoping for the best, one good thing... My phone was luckily already in unlock state
UPdate: Succesfully flashed my phone the stock with unlocked bootloader!
UPDate: And now on omni rom Everything is working fine!
i can't go into download or recovery mode anymore and no os is installed.
What happend:
i had base 4.4.2 (lg v50020a) i rooted it and flashed twrp recovery. I flashed cyanogen mod + gapps. Everything seemed to work. Then i noticed that i have this known brightness dim issue. I searched for a solution and found out that i have to use 4.2.2 as base and then flash cm. So i looked for a .zip to flash 4.2.2 and found this: http://forum.xda-developers.com/showthread.php?t=2719411
i made a fullwipe and flashed it.. it was trying to flash for almost 4-5 hours and after that i knew there was something wrong and i cancelled it by pressing the on/off switch for a reboot.
Yeah pretty dumb but i didn't find another way there was no cancel button..
so yeah i have no idea what to do now there is also no nandroid backup...
When i connect the tablet to the pc i can still hear the "connect" sfx and that's it.
And when i turn it on it's stuck to the LG logo but that's pretty obvious because there is no OS.
tried to go into download mode by pressing both volume buttons + plug in usb = doesn't work
and i don't know how to go in recovery mode by just pressing the hardwarekeys i went there with advanced reboot in cm.
Does someone have an idea?
Look over here:
http://www.youtube.com/watch?v=uo3YfszOPsQ
Good luck.
If you get the lg logo on boot you should be able to use the key command like the previous post to get to recovery. Flashing the 4.2.2 base image you linked to is a lengthy process. However it sounds like you may have had a bad download or something. The 4.2.2 firmware should be used if you are going to use most aosp based ROMs. If you are flashing a stock based ROM most of those require the 4.4.2 firmware. You were on the right track to solve the brightness issue if you were using an aosp based ROM.
Sent from my LG-V500 using Tapatalk
hi friends.. basically i am unable to install any new rom on my Redmi 1s, I searched almost everything but couldn't find the solution.. so i am posting it here... i will try to describe my problem below..
Back a few months i was using CM 12.1-20150603-UNOFFICIAL-armani.. then a OTA update came i installed it joyfully.. but my joys didn't last longer as a noticed that after booting my Wifi always shows "Turning WiFi On" but never got really opened. So i flashed back to old version... Then i installed Xtreme Music Mod and and the Earpeice Speaker went off... So i thought of flashing again, This time I flashed Flex OS.. was sucessful and then days later i installed xposed and got struck in bootloop due to an improper mod... due to my noobness i staraight away tried to flash flex OS again and then the install was successful but after the initial boot phone worked for like 30 seconds then freezes and reboot.. this happened again and again untill i flashed the CM 12.1-20150603-UNOFFICIAL-armani again... in middle of all this i tried using Multirom but was unsucessful....
And NOW MY PHONE WON"T ACCEPT ANY ROM OTHER THAN CM 12.1-20150603-UNOFFICIAL-armani
I tried changing recovery, gone through the Fastboot flashing and doing things a fresh
but every time i install a rom My phone either freezes on "ANDROID IS UPGRADING" or it boots completely and then freezes and reboot...
I hope someone has a solution for this.. coz m dying to use MM ..
Thanks
niimtz said:
hi friends.. basically i am unable to install any new rom on my Redmi 1s, I searched almost everything but couldn't find the solution.. so i am posting it here... i will try to describe my problem below..
Back a few months i was using CM 12.1-20150603-UNOFFICIAL-armani.. then a OTA update came i installed it joyfully.. but my joys didn't last longer as a noticed that after booting my Wifi always shows "Turning WiFi On" but never got really opened. So i flashed back to old version... Then i installed Xtreme Music Mod and and the Earpeice Speaker went off... So i thought of flashing again, This time I flashed Flex OS.. was sucessful and then days later i installed xposed and got struck in bootloop due to an improper mod... due to my noobness i staraight away tried to flash flex OS again and then the install was successful but after the initial boot phone worked for like 30 seconds then freezes and reboot.. this happened again and again untill i flashed the CM 12.1-20150603-UNOFFICIAL-armani again... in middle of all this i tried using Multirom but was unsucessful....
And NOW MY PHONE WON"T ACCEPT ANY ROM OTHER THAN CM 12.1-20150603-UNOFFICIAL-armani
I tried changing recovery, gone through the Fastboot flashing and doing things a fresh
but every time i install a rom My phone either freezes on "ANDROID IS UPGRADING" or it boots completely and then freezes and reboot...
I hope someone has a solution for this.. coz m dying to use MM ..
Thanks
Click to expand...
Click to collapse
*go to cm12.1 thread
*download and flash firmware.zip from post #3 and flash it
*wipe all in twrp(leave internal,external,usb otg)incase you want to wipe internal too,don't forget to make a backup before on pc.
*flash R31+5.1.1 gapps(i will prefer open gapps)
*wipe cache and dalvik
*reboot
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?