Alright, need some help here... decided to try a custom ROM for the first time since 5.1 came out. Flashed the newest Blisspop 5.1.1 build (4/30), got everything set up, apps restored, was running great. Using ElementalX kernel. I rebooted and I got the "android is upgrading" screen (did not say which apps were being optimized) and it finished, unlocked, and the phone shut off. Same thing about five times. Decided that I didn't want to mess with it tonight, so I just wiped and restored the Nandroid that I had made before flashing the ROM; the phone just will not turn on. After my sixth attempt nothing at all happens. Just endless bouncy balls. Master resets galore, reflashing kernels, everything. Not really looking forward to loosing all my data and settings for literally nothing. I've gone through the same backup/restore process countless times before and I've never run into this issue. I was thinking it could be an issue cause by going to 5.1.1 and then back down to just 5.1, but that doesn't really make sense to me. Anyone have any tips?
crazyjimbo said:
Alright, need some help here... decided to try a custom ROM for the first time since 5.1 came out. Flashed the newest Blisspop 5.1.1 build (4/30), got everything set up, apps restored, was running great. Using ElementalX kernel. I rebooted and I got the "android is upgrading" screen (did not say which apps were being optimized) and it finished, unlocked, and the phone shut off. Same thing about five times. Decided that I didn't want to mess with it tonight, so I just wiped and restored the Nandroid that I had made before flashing the ROM; the phone just will not turn on. After my sixth attempt nothing at all happens. Just endless bouncy balls. Master resets galore, reflashing kernels, everything. Not really looking forward to loosing all my data and settings for literally nothing. I've gone through the same backup/restore process countless times before and I've never run into this issue. I was thinking it could be an issue cause by going to 5.1.1 and then back down to just 5.1, but that doesn't really make sense to me. Anyone have any tips?
Click to expand...
Click to collapse
So it appears you're stuck in soft brick. I'm sorry but you may have to sacrifice your data in order to recover. It would be my suggestion, to boot to bootloader and issue: fastboot format cache and fastboot format userdata.
Related
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Dr. Falken said:
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Click to expand...
Click to collapse
a bit noobish myself, but I think I can answer a bit regardless, anyone feel free to correct me...
1: if everything is working, great! if you dont feel comfortable, and dont mind resetting everything up, go ahead, do it again, cant hurt. whenever reflashing/new flashing, Dont Forget to make a nandroid and wipe! (and you can rename the backups in USB disk mode so you know which ones are what, otherwise go by the embedded date in the autogen'd title. in the nandroid folder on your SD card btw)
2: as far as I know, leave it?
3: HUGE fan of Darchs work, cant go wrong... keep in mind it does not have VisVoicemail in it, fix flash needed.
4: reboot into recovery, make a nadroid backup, WIPE!, flash the new one according to cookers intructions! done! (if ya dont like it, buggy, nandroid restore back to your last good one you did like!)
well I reinstalled the rom and wiped first...and everything is running way smoother than last time. I don't know what in the world happened or what was going on but I'll take it as it is
Hi Folks,
so here's my problem, the other day I got the standard "not enough space"-warning and I thought crap there must be a solution to this by now, so I checked and found that script that cleans up the cache etc.
So today suddenly apps(mostly gapps) started crashing one after another, without them even being open, just as it would do when space in /datadata got very low. The phone was basically unoperable, so I restarted it and it was stuck at the boot screen(blue flashing screen, not before). I tried everything to get rid of this, clearing different caches, new nightly, new skript version....nothing.
So I did a nandroid backup, reset the whole thing and started it, everything went fine. Another restart into recovery flash nand-backup....back to old habits :/
Still not wanting to give up I reset it again and reflashed only /system.....all worked, reset it again and only flashed /data.....stuck again. So it must have something to do with the /data-partition, since I would really love to have my data and apps back it would be great if someone could help me out here.
Device-Info: newest CM9-nigthly, kernel that CM9 uses, of course I9000
For more Info please ask!
Weeman90
I do realize I am beating a dead horse but I'm having trouble finding the specific answer that I'm looking for. When I first flashed M Dev preview the day it was releaser I did not get the boot error. I rooted got the error, then it wouldn't boot until I flashed a custom kernel. We all know that this is what needs to be done.
However, I've flashed stock lollipop and gone back to M several times, stock recovery, correct boot loader and wiped all data and cache several times however I am still getting the boot error. Now all you have to do is wait the 5 seconds or however long it is and the device boots fine, but I've also noticed that ever since this began happening back when I first rooted, my LTE signal indicator goes away. I still have data and I can still use the device to get online and such. I wouldn't really are except there's one thing, when the LTE indicator goes away I can't make calls either. I am not set to LTE only or anything, I have the correct radios flashed and it doesn't matter what I do.
I can flash factory images manually or in NRT and I still get the boot error, and I still get the signal issue.
Don't worry so much about the LTE issue because I feel like it is caused by whatever is wrong and causing me not to be able to go back to complete stock.
I just need some advice on how go back to TOTAL stock, (UNrooted, stock recover, stock kernel, stock everything) so I will no longer get the boot error.
Thanks in advance to anyone who is willing to help.
jonzey231 said:
I do realize I am beating a dead horse but I'm having trouble finding the specific answer that I'm looking for. When I first flashed M Dev preview the day it was releaser I did not get the boot error. I rooted got the error, then it wouldn't boot until I flashed a custom kernel. We all know that this is what needs to be done.
However, I've flashed stock lollipop and gone back to M several times, stock recovery, correct boot loader and wiped all data and cache several times however I am still getting the boot error. Now all you have to do is wait the 5 seconds or however long it is and the device boots fine, but I've also noticed that ever since this began happening back when I first rooted, my LTE signal indicator goes away. I still have data and I can still use the device to get online and such. I wouldn't really are except there's one thing, when the LTE indicator goes away I can't make calls either. I am not set to LTE only or anything, I have the correct radios flashed and it doesn't matter what I do.
I can flash factory images manually or in NRT and I still get the boot error, and I still get the signal issue.
Don't worry so much about the LTE issue because I feel like it is caused by whatever is wrong and causing me not to be able to go back to complete stock.
I just need some advice on how go back to TOTAL stock, (UNrooted, stock recover, stock kernel, stock everything) so I will no longer get the boot error.
Thanks in advance to anyone who is willing to help.
Click to expand...
Click to collapse
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2954008
Follow method #2.
Evolution_Tech said:
Here's the thread:
http://forum.xda-developers.com/showthread.php?t=2954008
Follow method #2.
Click to expand...
Click to collapse
You, my friend, deserve a 4th of July beer. ?
So recently my phone was behaving unstable, took a look at XDA, Flashed a new rom, like any other person here.
SO then i figure out that i cannot log into any third party apps, (facebook, instagram) and figure it may just be a bug with the app itself.
Upon further invetigation, i figure out that this happens on, ANY ROM! Even STOCK rom. i ran a restore back to it's original Stock room, flashed, fixed persmissions, wiped calvik,cache, i tried everything!
Everything is closing, nothing works, phone is slow, laggy, hot and everything is ****ED.
Please help a fellow out, i used roms on all my samsungs, nexus 5, now 6. I'm an experience user. Never had this problem before.
saitek1911 said:
So recently my phone was behaving unstable, took a look at XDA, Flashed a new rom, like any other person here.
SO then i figure out that i cannot log into any third party apps, (facebook, instagram) and figure it may just be a bug with the app itself.
Upon further invetigation, i figure out that this happens on, ANY ROM! Even STOCK rom. i ran a restore back to it's original Stock room, flashed, fixed persmissions, wiped calvik,cache, i tried everything!
Everything is closing, nothing works, phone is slow, laggy, hot and everything is ****ED.
Please help a fellow out, i used roms on all my samsungs, nexus 5, now 6. I'm an experience user. Never had this problem before.
Click to expand...
Click to collapse
Did you try flashing the latest stock rom including userdata,img manualy in fastboot, start with fastboot erase system then flash system, userdata, boot, recovery, cache and that should fix iyour problems.
did you wipe your data before flashing a rom? if not, you should have. if you wiped your data before flashing a rom, thus would not happen.
simms22 said:
did you wipe your data before flashing a rom? if not, you should have. if you wiped your data before flashing a rom, thus would not happen.
Click to expand...
Click to collapse
Ofcourse i do.
When coming from a other rom, then always clean flash.
When updates from the same rom, you can dirty flash.
saitek1911 said:
Ofcourse i do.
When coming from a other rom, then always clean flash.
When updates from the same rom, you can dirty flash.
Click to expand...
Click to collapse
when updating the same rom, you can USUALLY dirty flash, but not always. so, did you clean flash this time?
Do a factory reset, anyway.
hello,
ive been searching around for about an hour and i havent found a thing.
Let me describe my phone:
Safestrap
rooted
android 4.4.2
Scenario:
got a nasty ad virus yesterday, so i restarted my phone today and went into safestrap. Then i installed my previous back up from about a month ago. (not sure if i needed to delete anything left of the device) I restored data and system and it worked fine. I was in android for about 5 minutes then it restarted. so i assumed it was normal then it did it continuously.
First off im not sure what a bootloop is but i assume it doesnt post to the android system and continuously loops the boot logos.
Whats happening to me is that my phone will boot for a few seconds, sometimes minutes, and i can get on android for a few. Then the phone restarts. Ive been looking around for a few hours now and i cant find a fix or a way to restore my phone to the restore i made on 4/22/17.
ANY help would be greatly appreciated and please correct me if i did something i wasnt supposed to.
If you need more info i will gladly post more
-LL
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Sicuro said:
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Click to expand...
Click to collapse
I got it fixed i had to flash a new stock rom and root it again. up and running from a softbrick. Its also running Android 4.4.2