I've been trying to install a lollipop rom for weeks now and nothing has worked. I cannot S-off and thought all hope was lost. UNTIL! CM put out their CM12 nightly and I was super excited to try it out, only to have it APPEAR to soft brick. I waited for a good 4 minutes the first time and just flashed a back up... But today! I was so mad I just left my phone on my desk and walked away. When I came back my phones screen was black, thinking it was odd i tried to power my phone on only to have it show me CM 12! I guess my question is, why the hell didn't it show my the boot logo!?
UPDATE: Just rebooted to install the new Gapps and it still doesn't show a boot logo :s. Anyone got a fix?
UPDATE 2: It still takes an eon to boot, after flashing the Gapps it took 10 minutes to reboot.
Related
So here's the deal..
So I'm no newb when it comes to flashing roms. my Dinc is my 3rd phone with a custo.m ROM. Well what happened is. I flashed to cm9 kangs from cm7 v13. Well after about a week I was sick of the instability and having to install apps twice just got annoying.. soo... I decided to go back to cm7 but I didn't have it on my sd anymore so I pulled it from my comp and flashed through ROMmanager. Well upon booting it got stuck in a bootloop (which is the first time I've encountered this.) So I took out the battery, and I held down both volume and the power button and the phone vibrated 5 times and the LED went from flashing red to green and the screen stayed black. Now I can't boot into recovery.. nothing. Almost thinking its bricked... is there any way to save this phone?
Thanks for any help u can gived.
XCmaster said:
So here's the deal..
So I'm no newb when it comes to flashing roms. my Dinc is my 3rd phone with a custo.m ROM. Well what happened is. I flashed to cm9 kangs from cm7 v13. Well after about a week I was sick of the instability and having to install apps twice just got annoying.. soo... I decided to go back to cm7 but I didn't have it on my sd anymore so I pulled it from my comp and flashed through ROMmanager. Well upon booting it got stuck in a bootloop (which is the first time I've encountered this.) So I took out the battery, and I held down both volume and the power button and the phone vibrated 5 times and the LED went from flashing red to green and the screen stayed black. Now I can't boot into recovery.. nothing. Almost thinking its bricked... is there any way to save this phone?
Thanks for any help u can gived.
Click to expand...
Click to collapse
If you can access hboot its not bricked. You need to do the five vibes fix herehttp://pvillecomp.com/?page_id=33, if you can get to hboot to use fastboot. If you cant access hboot you are out of luck.
well an update. what i did was pulled the battery and held down the power button for 10 seconds, then put in the battery and plugged the charger in. and it forced it back into the bootloop. i was then able to access hboot and try and reinstall. well both cm7 and cm9 both started the bootloop. so i went through and factory reset the phone and formatted the sd. and also wiped the dalvik and cache. also formatted system/data/cache, and reinstalled cm7 and it started force closing EVERYTHING. so i completely wiped the phone and reinstalled cm9 and everythijg worked fine, so i went back to cm7 and now everything is working as before. didnt have to enter code in the terminal emulator blahblah.. just an easy fix for me dont think itll work for most but did here so its worth a try i guess.
Tried everything I could find, so decided it was finally time to come here. I was happily running CM11 for more than a year and saw that CM12 was available. Used the CM app on my phone, did the whole Windows part, the update started, then failed. Now my phones boots and gets to the first screen after, and for hours the arrow spins round and round.
Tried Vol+/Home and Power, the screen flashes something real quick and it reboots. When I try the same with Vol-, I get a screen that says it's downloading, but nothing ever happens. I'd be happy getting the stock Samsung ATT ROM, CM11, anything so the phone would work. I even tried seeing if I cold flash various other ROMS with Odin to no avail. Must have brain damage (exhaustion) because Odin isn't seeing the file it wants in any of the ROMs I've downloaded.
Thanks in advance.
Before flashing anything else, flash back to cm11 and confirm the bootloader currently installed on the phone.
I have a NOTE 4 that was just sent to me as a replacement from Sprint. It came with Lollipop loaded. I rooted using Chainfire autoroot. When I loaded the phone it told me that I didn't have root.
I think used the battery pull method to try and get TWRP to load. So I ran CF-Auto (I know I used the correct one). This time I unchecked auto reset or restart. I pulled the battery and went into TWRP manually
Once there I flashed the BOBv2 and Noterized Rom as well.
Each time I reboot with either of them it just HANGS and the yellow Sprint spark screen. I have tried to wipe cache, I did the factory reset with TWRP. I reflashed them...still NOTHING. Just hangs at that screen regardless of what ROM it is. Please help.
Are you giving it time to load? Maybe like fifteen minutes.
Yeah, got to give it at least 15 minutes to boot up after that. Hell I've gone up to 25 minutes.
It takes a super long time not like pre lolipop days. It make me hate flasing as much . Everyone phone takes super long to boot . It will just be patient. I wasted my time thinking it wouldn't boot to. Then i listened to everyone and they was right takes a long time. Let us know how things go
ART, known as Android Run Time can be a pain when loading your applications and optimizing the device. But once it's all loaded, your device will fly.
Thank u guys. I was just being impatient
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
joskur98 said:
My Nexus 7 2013 tab is stuck on boot animation and not switching on thereafter. I installed a custom rom after flasing TWRP RECOVERY 3.0.2 via P.C and thereafter using the TWRP.
The installation process is successful each time but wont go further than the boot screen. I waited for almost an hour . Evem the Gapps zip is not installing and giving error on log saying that file not mapped. Any way out of this mess? Does it have anything to do with my process? ...I advance wipe the system , data and cache before flashing and the file.
Click to expand...
Click to collapse
Which rom? Do you use the right gapps? Flash the rom without gapps and look if it's booting
Don't know if you ever figured this out, but last night, mine froze while the kids were playing a game. I couldn't do anything at all. I had to hold the power button down for a while and it finally shut down. I charged it overnight, and all I could get it to do was display the Google screen. I searched and searched for a solution, and the only crazy thing that actually worked was to give it a good whack! I don't know why, but as soon as I smacked it (not on the glass!!), it booted right up as normal. Very odd.
Click to expand...
Click to collapse
Holy ****, this worked! Had the same problem last night for the first time (I used it until the battery drained and this morning I got the loop). Smacked it on the back and now it's fully on!
Shame I got desperate and did a factory reset first