• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Solved] device wont complete boot!!!

davidmargolin said:
nope nothing... no mods this time around...
also had this bootloop prob before (on many roms and not just mobz) but didn't really care much... just started from scratch those times...
Click to expand...
That's weird. What firmware do you have installed?

BTW, the RUU recommendation isn't to run the stock ROM, but a number of users on the Evo 3D have had problems like this and couldn't get past them until they flashed the RUU to re-sync everything. Since you are S-OFF you don't need to relock the bootloader and the RUU flashes in about 10 minutes, then you just need to flash a custom bootloader and recovery and you're back in business.

Might be worth a try.

ramjet73
 
ramjet73 said:
That's weird. What firmware do you have installed?

BTW, the RUU recommendation isn't to run the stock ROM, but a number of users on the Evo 3D have had problems like this and couldn't get past them until they flashed the RUU to re-sync everything. Since you are S-OFF you don't need to relock the bootloader and the RUU flashes in about 10 minutes, then you just need to flash a custom bootloader and recovery and you're back in business.

Might be worth a try.

ramjet73
Click to expand...

dont need to relock bootloader??? will it put me back to s-on???
 
Just to be clear, you restored your data partition to a fresh ROM flash and then deleted the nandroid you restored from? Or did you just have an advanced backup of the data partition? I'm probably missing something again, but was trying to figure out why you couldn't restore the whole nandroid that contains the data you need.

ramjet73
 
ramjet73 said:
Just to be clear, you restored your data partition to a fresh ROM flash and then deleted the nandroid you restored from? Or did you just have an advanced backup of the data partition? I'm probably missing something again, but was trying to figure out why you couldn't restore the whole nandroid that contains the data you need.

ramjet73
Click to expand...

i have a full backup and an advanced backup of data

restoring the advanced backup of data on a fresh install causes bootloops

restoring the full backup also causes boot loops

getting only a fresh install boots fine
 
davidmargolin said:
dont need to relock bootloader??? will it put me back to s-on???
Click to expand...
No. That's an urban myth. ;)

The only things it does that need to be reversed are the stock recovery and bootloader. And your firmware will be at the base VM level so you might want to install the OTA while you are stock or flash the firmware from prinny's update thread after the RUU.

ramjet73
 
Have you tried reflashing anthrax (clearing caches, of course)? I think the data partition gets corrupted sometimes with anthrax and reflashing might work.

Did making a data back up and reflashing the ROM then doing an advanced restore, data only, not work?
 
thebryceee said:
Have you tried reflashing anthrax (clearing caches, of course)? I think the data partition gets corrupted sometimes with anthrax and reflashing might work.

Did making a data back up and reflashing the ROM then doing an advanced restore, data only, not work?
Click to expand...

tried reflashing anthrax and nada
advanced backup of data and then restore of it on a fresh flash also produces.... you guessed it... nada
 
davidmargolin said:
tried reflashing anthrax and nada
advanced backup of data and then restore of it on a fresh flash also produces.... you guessed it... nada
Click to expand...
That's really strange. There are definitely things that can happen in the data partition to keep a ROM from booting, but they usually don't manifest themselves after a ROM has been running for a while. It's almost like you have some app that's causing issues.

Hey, I just thought of another possibility. Have you heard of "safe" mode? It's a way to boot the phone without the apps that normally autostart. I don't remember exactly how to turn it on and off but can look it up if you want to give it a try.

Edit: Here you go. Check post #3 as that has a simple method for getting in and out of safe mode.

ramjet73
 
ramjet73 said:
That's really strange. There are definitely things that can happen in the data partition to keep a ROM from booting, but they usually don't manifest themselves after a ROM has been running for a while. It's almost like you have some app that's causing issues.

Hey, I just thought of another possibility. Have you heard of "safe" mode? It's a way to boot the phone without the apps that normally autostart. I don't remember exactly how to turn it on and off but can look it up if you want to give it a try.

ramjet73
Click to expand...

ill try anything at this point...
 
can't seem to get it in safe mode... boot animation just keeps going and never gets to lock screen
will keep trying though... reminds me of puting my ipod in dfu mode
 
davidmargolin said:
can't seem to get it in safe mode... boot animation just keeps going and never gets to lock screen
will keep trying though... reminds me of puting my ipod in dfu mode
Click to expand...
Hmmm....

I have two Evo 3D's and got it to work on both of them. One has mazda's AOKP installed and the other has MeanROM ICS 2.6 which is similar to Harmonia.

I pressed the volume down button from the time the splash screen appeared until the lock screen came up with "Safe mode" in the lower left corner.

ramjet73
 
davidmargolin said:
nope nothing... is there an adb command for safe mode
Click to expand...
I don't think so. You've already tried changing bootloaders and the fresh install of the ROM. I don't know of any backup that runs outside Android, so if you can't boot after restoring the entire nandroid or just the data partition after a fresh ROM install, I don't know what's left to try but the RUU+OTA then a nandroid restore. If the problem is inside your data partition I don't see how that will fix it, but it won't hurt anything either.

Do you have recent Titanium Backup of all apps+data and settings? Restoring that is not always perfect but it's better than nothing.

ramjet73
 
I just remembered that I have a flashable version of the VM stock kernel (attached) so you could try flashing that from recovery just in case your booting problem is Anthrax related.

ramjet73
 
this happened to me recently too

I got a version of mobster rom about 3-4 months ago and have been running it ever since. so for 3-4 months I did not change roms. i just stayed on the same one.

on saturday, my phone died, usually not a problem, i swap in a new one and keep going.

but it wouldnt boot. did the same thing yours did.

i could get into bootloader and from there into recovery.

the ONLY fix was to wipe everything and re install the rom from the .zip i have on the sd card.

then 2 days later it happened AGAIN.

while in recovery wiping dalvik and cache and fixing permissions, i kept getting the error that some block was missing. only reinstalling the rom once more solved it.


i can only assume that the nandflash inside the phone is failing and randomly wiping bits of important data (boot/rom data)


i did a 5x full wipe of the phone and formatted the sd card and installed the latest mobster and my phones been ok since, but "since" means the last few days.

i would not be surprised if the phones are manufactured with super cheap flash memory that doesnt hold data properly after a few months. this is the same issue i have with cheap no-name brand flash drives.
 
thanks for all the responses... fell asleep cause i was really tired... will look into everything and report back tonight....
 
OverByter said:
Unfortunately he's using 4EXT and the app only supports cwm and twrp nandroids.
Click to expand...
I use the latest version of 4EXT (v1.0.0.5 RC9) and tested that app and it read the nandroid backup fine, although it takes a while to parse through the applications. Max (madmaxx82 on XDA) made the 4EXT backup format compatible with CWM and even uses the same directory location.

ramjet73
 
You must log in or register to reply here.
Back
Top Bottom