Hi!
I am currently running CM12-20150314-NIGHTLY. I am still using this old version because every time i flash a new rom the phone won't boot. It will ALWAYS get stuck on the splash screen. It will still be possible to access recovery mode, but it won't help wiping, reflashing the new version or reflashing the old version. To solve the problem i have to re run the guide for "root, ulocking bootloader and flashing recovery" to get the phone to boot again.
Do someone have an idea why the phone won't boot after upgrading to a newer rom? I have performed the process three times with different versions of the rom so i know it will happen if i flash a new rom again.
//diddi
Bump
Couple of questions. What roms are you trying to flash and where are you getting them? How long do you let it sit at the splash screen before giving up? When you say wipe, do you mean a complete data wipe? Or just a cache wipe? My thought is that it could be any of the following:
1. You just need to let it sit longer. The first boot after a new flash can take a really long time.
2. The rom may not be complete, or it could have been a bad download.
3. You aren't wiping everything and there is something conflicting.
If it's not any of those, let us know. But we need more details.
Thanks for your response!
This time i have not tried to flash a new rom, since it have not worked the past three times. Last time i think i came from CM12 20150210 to about 20150215. But that did not work, neither the previous flash between to ROMS.
1. I have let the phone load for at least 20 minutes one time, shouldn't that be enough?
2. No, really don't think that's the case, since i can't even get the phone to bot with the rom that i was previously using.
3. i have tried to wipe cache and a complete wipe, no difference
/diddi
It seems like you know what you are doing. For good measure, I would try instead of installing a nightly, just do a nandroid backup, and try a completely different rom designed for the the OPO. If that won't flash, then it may be something wrong with the recovery or bootloader.
Thank you! Will try that tomorrow when i got some spare time! I'll come back with the results!
//diddi
Related
I've been using CM7 Nightlies ever since build 3 without any problems on my D1. All of the sudden, I am unable to boot into clockwork recovery. So now I can't backup, update, or recover. Any thoughts?
I'm considering a full wipe if I can't get this resolved. Thanks in advance for all of the help
i am currently having the same issue with my Moto Droid.
Running CM7rc2 wont boot into CWR.
I've tried updates of CRW (currently version 2.5.0.1) but it wont flash high versions...
Updated Rom manager, that wont boot into it.
CM7 reboot menu wont boot into it.
X+power wont boot and volume down one wont work either...
Also tried the alternative recovery flash and rom manager cant flash it.
I feel your pain, it was very frustrating. After a few days of not being able to backup, recover, or update, I decided it was time to wipe the droid and start with a clean slate. It took me a couple hours to get everything back up but I didn't know what else to do. Hopefully someone out there has a better solution so you don't have to do the same thing.
airballwall said:
I feel your pain, it was very frustrating. After a few days of not being able to backup, recover, or update, I decided it was time to wipe the droid and start with a clean slate. It took me a couple hours to get everything back up but I didn't know what else to do. Hopefully someone out there has a better solution so you don't have to do the same thing.
Click to expand...
Click to collapse
I've been struggling with this for weeks, finely found out it is a simple fix, turn off debug. settings, applications, development, UNCHECK debug.
It works.
I found a fix as well. I simply flashed an alternate recovery, at the very bottom of the rom manager app, and then reflashed clockwork. I really should have thought of this first, oh well.
Sent from my Droid using XDA App
I have been rooted for a couple of months now, and I was tired of dealing with the auto-update keep taking control of my phone.
So tonight I decided to instadd das BAMF rom and the MR2 radio... long story short, I could never get the radio to install so through hboot, i selected recovery to recover the stock ROM, I wiped the data and cache prior to recovering, then rebooted.
Now it is stuck at the htc boot screen.
I need help pretty soon guys, if anyone reads this soon, i have to be at work in 5 hours!
Thanks
tothehouse34 said:
I have been rooted for a couple of months now, and I was tired of dealing with the auto-update keep taking control of my phone.
So tonight I decided to instadd das BAMF rom and the MR2 radio... long story short, I could never get the radio to install so through hboot, i selected recovery to recover the stock ROM, I wiped the data and cache prior to recovering, then rebooted.
Now it is stuck at the htc boot screen.
I need help pretty soon guys, if anyone reads this soon, i have to be at work in 5 hours!
Thanks
Click to expand...
Click to collapse
If you flashed the radio last, it might had wiped the phone, meaning you need ot flash a ROM afterwards, or the phone is bricked, from something you did. I don't know much about the TB, but you should ask in its dedicated sub-forum instead, you'll get much better results there.
thanks, I wish I could but I have less that 10 posts... i dont understand it, i can access h-boot and i can do anything in there like everything is fine, but the phone will not reboot or restart
tothehouse34 said:
thanks, I wish I could but I have less that 10 posts... i dont understand it, i can access h-boot and i can do anything in there like everything is fine, but the phone will not reboot or restart
Click to expand...
Click to collapse
Then it's not bricked, most call it soft "brick" since it doesn't boot. You should wipe in clockwork, and then flash another ROM.
I have tried to recover my stock rom 4 times, but i just found a stock debloated version of the stock rom, so im going to try and flash it.
I have tried to do this a couple of times since the new version of BMM came out. I followed all of the instructions to make it work. Then I flashed PACman and I got stuck on the loading (seemed like a bootloop) screen for like half an hour. And no matter what ROM that I use this seems to be happening. I would like to use either the PACman or AOKP that alerted has up. Any suggestions?
at2smithjason said:
I have tried to do this a couple of times since the new version of BMM came out. I followed all of the instructions to make it work. Then I flashed PACman and I got stuck on the loading (seemed like a bootloop) screen for like half an hour. And no matter what ROM that I use this seems to be happening. I would like to use either the PACman or AOKP that alerted has up. Any suggestions?
Click to expand...
Click to collapse
Did you flash the gapps too?
If it were me, I'd FXZ back to stock ICS then root, install BMM, boot into BMM, factory reset, flash ROM, flash gapps then reboot. Works for me every time.
Brought to you by time and relative dimensions in space.
I always make sure that I get the proper gapps.apk file for the version of the rom that I am installing. I think that the only thing that you are doing different than me is the factory reset. Thanks. I will give this a try and i will keep my fingers crossed.
at2smithjason said:
I always make sure that I get the proper gapps.apk file for the version of the rom that I am installing. I think that the only thing that you are doing different than me is the factory reset. Thanks. I will give this a try and i will keep my fingers crossed.
Click to expand...
Click to collapse
You no do factory reset before flashing ROM? That's the cause for bootloop.
And if you have BMM set up and different ROMs on various systems, then doing a factory reset on any system wipes other systems too. You just have to delete the partitions for that system in order to delete it.
And btw Gapps come in flashable zip and not apk
Remember, if you're trying to flash any of the Kexec based ROMs (like anything posted by deveshmanish) and you keep getting stuck at the boot screen, then you may be one of the unlucky "Kexec - rejects" like myself.
If so, then none of those ROMs will work for you. You need to try one of the non-kexec versions. There are several by different devs.
Sent from my personal phone thingy.
I just rooted last night and everything was good... This morning all I did was freeze some of the stock Verizon apps, and the system crashed. Now when it reboots, it's stuck at the Verizon screen. I can access Bootloader/Recovery, and have tried "fastboot erase cache" but that hasn't fixed it. If I let it sit, I can hear notifications and stuff in the background (I also have MightyText installed, and can send/receive texts via that), so Android is running in the background - it's just "stuck" on this Verizon screen. I'd really rather not have to do a factory reset, since I just spent last night getting everything set back up from the root process.
Any suggestions? Please help!
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Drunkula said:
Uncertain. Just a shot in the dark but which recovery do you have? Have you tried doing a "fix permissions" within it?
Click to expand...
Click to collapse
TWRP. Just did that now, no changes.
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
andybones said:
You may have froze something you shouldn't have. At this point, I'd personally do a full wipe and reflash the ROM. If not on a ROM and on the stock RUU ROM. I would:
1) consider flashing a stock based ROM:
This ROM is 100% stock based off RUU -
http://forum.xda-developers.com/ver...-4-17-605-9-stock-resources-firmware-t3196906
2) run RUU again, and freeze one app at a time to narrow down what may have caused this.
3) you can try a wipe of just cache/dalvik cache
Click to expand...
Click to collapse
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
dajoip said:
Thanks, yeah I just wiped and flashed a ROM. I needed my phone running in the next two hours, and didn't have the time to investigate. Hopefully it doesn't happen again.
Click to expand...
Click to collapse
Next time when you're cleaning out Verizon bloat, don't take out anything that you're not sure of.
Leave in there: VZWAPN and vzwdummylibs if you dump any Verizon apps.
Besides being able to start the phone, it's got to be able to send and receive calls. I have learned this thru bad decisions and their results.....
I have a well and heavily used Galaxy S5 (GM-900P) and about 2 months ago it started accting up pretty hard. Becoming very very slow so I decided to update to the latest sprint firmware and install a new(er) rom ([ROM][QD1][6.0.1]14Dec2017] Stock-ish Plus Tidbits and Magisk) and all was good for about 5 days and the phone started having apps crash/force close like crazy and most the time just reinstalling them would fix it but a bunch of google play services would crash and would have to uninstall the updates then it would work again for a day or so, sometimes it would randomly restart and get stuck at the boot screen and the phone would get crazy hot and the only way out of it was to boot into the recovery and then reflash the stock firmware in odin again then reinstall the rom. Then I had my phone all of a sudden act like there was no sim card in it and originally though it was a sim card issue but turns out it wasnt, I had to boot into the recovery and do a full wipe of everything reflash the stock firmware yet again and then reinstall the rom again. That happened twice in a matter of a week. At my wits end I decided to give LineageOS v16 a try so I boot into recovery, do a full wipe, boot into download mode, flash the latest stock firmware in odin, then boot right to recovery, flash LineageOS 16.0 then latest Magisk and all was great, for about a week, then Google services start crashing again and random apps crash over and over and even times the phone would slow down and reboot, get stuck at the boot screen and then eventually just reboot back into recovery by itself after failing to boot. But with LineageOS at least just reflashing the rom in the recovery will let it boot right back up sometimes and work as it should for another few days, other times too much stuff will just keep crashing so I do a full wipe and reflash LineageOS and all will be great for another few days to a week and it starts all over again. Its like stuff just randomly gets corrupted on the device and the only way out of it is to reflash the whole thing and start over and enjoy it until it does it again. Sometimes it will go days, sometimes a day later its all screwy again.
Also, TWRP always fails when I try to do a back up and it seems to always fail when in the data or data/private-app part of the system and its never at the same point.
I guess my question here is, could the onboard flash (the motherboard/logic board) be taking a crap on me? I really really dont want to give up on this phone just yet as it has everything I want in a phone and frankly, I just really really like it. I can get a new (used) motherboard for like $20 but even that kind of worries me cause I dont want to possibly be in this same position 3 months later again. I have a Galaxy S8+ (unlocked AT&T phone) that I refuse to use yet just cause I can not root it or unlock the bootloader.
Any help or ideas would be much appreciated and sorry for the long winded post.
could be wrong, on this one, But.....
If it was mew, I would go to stock . run that for a day, maybe 3... if all it well, then flash over what ever Rom you would like.
"KNOWING IT Work" is the key. Oh, another thing, that may help too . seen this on one of the LineageOS 15.1 or 16 is when you wipe ... System and Data, can be Reformatted, they have had some major success by also formatting it, (YES EXT4) but this will help to ensure nothing left over....
May even help with others Android 8.0, 8.1, 9.0....
Well, I have a new motherboard on the way so we'll see how that goes but I did manage to get the stock firmware on there and booted then I reflashed TWRP and then Magisk and going to just run it that way for a bit and see what happens.
I initially went in to TWRP, wiped data,system, etc... then flashed the stock firmware in Odin, then rebooted, got stuck at the Samsung boot logo so pulled the battery, booted to stock recovery, did a factory reset (Wiped everything, internal sd card included), then got it to boot, set the phone up, then rebooted to download mode, flashed TWRP, then rebooted again, set the phone up a bit more then decided to flash Magisk so I have root, and so far its working. 100% stock with magisk. Fingers crossed.
I still think there is an issue with the internal flash memory though as I can not get a TWRP backup to actually complete without failing. It always fails when backing up stuff in the data partition/section and never at the same point like its having read errors or something. I'll grab a TWRP log and post it up in a bit.
Well, that didnt last long. Within an hour, apps started crashing. I will make this thing work! LoL