-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Phone stucko on "4G" white screen
- Thread starter cyaiphone
- Start date
-
- Tags
- htc evo 4g
cyaiphone
Android Enthusiast
OK i was able to get to hboot. i went into recovery and hit reboot and it seemed like it was going to work and then it got stuck on the 4g screen again.
OK i was able to get to hboot. i went into recovery and hit reboot and it seemed like it was going to work and then it got stuck on the 4g screen again.
With the battery you just put in or the one that died earlier? You got into recovery or just as far as hboot? If you got to recovery, try clearing cache/dalvik, then reboot.
cyaiphone
Android Enthusiast
I actually was able to go into recovery menu and hit "reboot". let me try cleaning cache/dalvik and rebooting. BRB
cyaiphone
Android Enthusiast
Didn't work got the stupid 4G screen again. I have a nandroid back up, How do i use it?
What exactly happened before? When the battery gets low enough, the phone is supposed to just shut down. Did it not shutdown gracefully?
Anyway, are you using clockwork or RA recovery?
Clockwork - once in recovery, select "nandroid", then "restore". You'll get a menu with all your backups. Select the most recent one.
RA - select backup/restore, then restore. Pick the most recent backup.
Not sure which battery you're using now, but make sure you have >30% or there's a good chance you'll get errors. Keep in mind that doing a nandroid restore will erase anything you've done since you made the backup (installed apps, text messages, etc.).
cyaiphone
Android Enthusiast
well I got the low battery warning. Next thing I know (few moments later) phone was dead and wouldn't turn back on. Got home and tried changing the battery and all i get is the white screen. The battery I have it in now is fully charged. I will try nandroid restore, see if it works.
cyaiphone
Android Enthusiast
Looks like restoring is complete. I'm about to reboot system now but just wanted to note this. I'm not sure if it means anything or not. i got a message on the bottom that says this
Erasing boot before restore
restoring boot image
restoring system
resotring data
restoring .android secure
restoring cache
sd-ext.img not found. skipping restore of /sd-ext.
restore complete
Erasing boot before restore
restoring boot image
restoring system
resotring data
restoring .android secure
restoring cache
sd-ext.img not found. skipping restore of /sd-ext.
restore complete
cyaiphone
Android Enthusiast
so once i get my apps back and settings how i want them should I go ahead and make a new nand back up?
OK it seems like i got my phone back
I had a pop up telling me of a system update available. Of course i declined it. did this maybe have something to do with it?
Hmm, it would definitely cause problems if it had actually downloaded and installed the update, but you would have different symptoms. For one thing, it probably would have just gotten hung up at reboot due to a custom recovery. If you somehow did manage to install it, you would probably just lose root. Since you already know the issue started with the dead battery, I doubt it got that far. You did a very smart thing by declining the update. If you go to settings->system updates->htc software update, you can uncheck the "scheduled check" option. I highly recommend you do so. You definitely don't want to accept any OTAs while rooted.
Yeah, you may as well. I usually keep up to two nandroid backups on my sd card. The first may be out of date, but it's one I know works (have restored from before), and the second is a more up to date one with my current settings. So, go ahead and make a new one, but keep the old one since you know it works. That's my advise. I'm sure a lot of other people do different things. At a minimum, always keep one around. It did you well to do so tonight
.
cyaiphone
Android Enthusiast
thank you so much for your help again! You should be given mod privileges!! You are always helping people non stop on these boards. Thanks!Yeah, you may as well. I usually keep up to two nandroid backups on my sd card. The first may be out of date, but it's one I know works (have restored from before), and the second is a more up to date one with my current settings. So, go ahead and make a new one, but keep the old one since you know it works. That's my advise. I'm sure a lot of other people do different things. At a minimum, always keep one around. It did you well to do so tonight
cyaiphone
Android Enthusiast
one last thing to flash the kernal i was running i just go to recovery and flash from zip right? it should still be there?
also how do i delete a nandroid back up?
also what is "wipe data/factory reset" does that unroot me?
Is it possible to do restore back to a state that is unrooted?
I have a nandroid back up from 12-23 when i did the root but im not sure if that was before the root process or after.
1) Go to recovery, wipe cache and dalvik cache, flash the kernel. As long as you left it on your sd card, it'll still be there. Nandroid restore doesn't do anything to your sd card (with the exception of an ext partition if you made one).
2) You can use any file explorer to browse to /sdcard/clockwork (for clockwork) or /sdcard/nandroid/(unique number)/ to find all your backups in directories named by the date and time GMT that the backup was created. Each of those directories contains img files of each partition to make a whole backup. You can delete any of those whole directories to delete a nandroid backup. You can also copy them to your computer if you like (but keep at least one on the sd card).
3) Wiping data will delete everything in /data wiping out all apps and settings. It will take whatever ROM (whether it be custom or stock) back to stock (default apps and settings; for custom roms, it takes them back to the way they were when you flashed them). It will not touch anything below the android file system (recovery, hboot, etc.). That being said, it does not unroot your phone. You will still have s-off and a custom recovery. In fact, you need to wipe data when switching roms and applying some mods. Always follow directions for specific roms/mods when deciding whether to wipe data or not.
4) There are two kind of root - soft root and full root. Soft root means that you have su privileges in your ROM (run root apps and such). Full root means you have s-off and can permanently write to /system. Since you can't make nandroid backups until you have root, it wouldn't make any sense to have a backup of an unrooted rom. You have s-off anyway, and no nandroid restore will ever change that. If you'd like to unroot, follow the directions here:
http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies-extras.html
That being said, any nandroid backups you have must be from after you rooted. You couldn't have possibly created it without being rooted. Even if for some odd reason you manage to apparently lose root in a rom, you have s-off. Just flash something else.
2) You can use any file explorer to browse to /sdcard/clockwork (for clockwork) or /sdcard/nandroid/(unique number)/ to find all your backups in directories named by the date and time GMT that the backup was created. Each of those directories contains img files of each partition to make a whole backup. You can delete any of those whole directories to delete a nandroid backup. You can also copy them to your computer if you like (but keep at least one on the sd card).
3) Wiping data will delete everything in /data wiping out all apps and settings. It will take whatever ROM (whether it be custom or stock) back to stock (default apps and settings; for custom roms, it takes them back to the way they were when you flashed them). It will not touch anything below the android file system (recovery, hboot, etc.). That being said, it does not unroot your phone. You will still have s-off and a custom recovery. In fact, you need to wipe data when switching roms and applying some mods. Always follow directions for specific roms/mods when deciding whether to wipe data or not.
4) There are two kind of root - soft root and full root. Soft root means that you have su privileges in your ROM (run root apps and such). Full root means you have s-off and can permanently write to /system. Since you can't make nandroid backups until you have root, it wouldn't make any sense to have a backup of an unrooted rom. You have s-off anyway, and no nandroid restore will ever change that. If you'd like to unroot, follow the directions here:
http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies-extras.html
That being said, any nandroid backups you have must be from after you rooted. You couldn't have possibly created it without being rooted. Even if for some odd reason you manage to apparently lose root in a rom, you have s-off. Just flash something else.
cyaiphone
Android Enthusiast
sorry for so much questions bro! I just did a restore back to the first nandroid back up that i had. My phone looks stock now. How do i know if i "lose root in a rom" ???
Chances are you made a nandroid backup right after you rooted, which would probably look stock. You can always check for root by doing this:
open a terminal emulator
type "su" without the quotes
If the prompt changes to #, you have root. If it gives you an error and/or the prompt stays as a $, then you don't have root.
Oh, and don't worry about asking questions. If you can't find the answer, it's better to ask than to accidentally do something wrong
.
cyaiphone
Android Enthusiast
Chances are you made a nandroid backup right after you rooted, which would probably look stock. You can always check for root by doing this:
open a terminal emulator
type "su" without the quotes
If the prompt changes to #, you have root. If it gives you an error and/or the prompt stays as a $, then you don't have root.
Oh, and don't worry about asking questions. If you can't find the answer, it's better to ask than to accidentally do something wrong
....ummmmmmmmm what is a terminal emulator
....ummmmmmmmm what is a terminal emulator
The more advanced way of interacting with a unix/linux based system
. Just install this:Android Terminal Emulator - Android app on AppBrain
It's just the command line. By typing "su", you are giving yourself superuser permissions. As is the standard, when you have root from a command line, you get the # prompt. It's a very quick way of determining if you have root or not. Once you've done that, close it right away if you don't know what you're doing
.You can google all kinds of guides on how to use the command line in linux if you're not familiar.
TheRealAshland
Member
ok same thing is happening to me. I had my phone plugged into my laptop like I always do charging,and i heard it vibrate and cut off and then again then i hopped up to look at it and it was stuck on that white screen, i did a batt pull and unplugged it. now i trying plugging it up again it makes a sound like its plugged in to the computer but no light comes on, i tried the wall and same thing,...NOTHING. I have not done anything to my phone in a long while , like a month or so, so what in the hell is going on .. going to cry shortly