Unrevoked - Internal Error: am reported error starting service
I was able to root using the new unrevoked version yesterday. But today I had to erase everything and start over with the phone for unrelated reasons. Now when I try to do the unrevoked again I get the message: Internal Error: am reported error starting service
I've installed the hboot drivers for windows, selected charge only when connected, and checked usb debugging. And sync is not installed on my computer.
Last edited by fryc86; January 2nd, 2011 at 02:33 AM.
Fixed: Nevermind, I checked and I still had s-off. I checked in terminal and apparently I'm still rooted. I thought when I did the recovery image that I would lose it. Guess not. I don't know for certain if this is what caused the error message, but I can't imagine it being anything else. Anyways, disregard
Last edited by fryc86; January 2nd, 2011 at 03:40 AM.
When you root with unrevoked, you need to do two things to unroot:
1) Flash the s-on tool
2) Flash the appropriate PC36IMG.zip for your hboot version.
If you skipped the first step, you would not have unrooted. In fact, the PC36IMG probably wouldn't have even done a whole lot. Did you still have a custom recovery?
hmm I don't know. I didn't do the s-on tool. I just put the pc36img back on my sdcard and flashed it from clockworkmod recovery. It enabled me to boot the phone up which I had been unable to before then. I have a few nandroid backups on my sdcard, but they have never worked for me. Every time I try to recover my phone with a backup I make it says its working then when it goes to restart it stays in the evo white splash screen forever and never gets any farther. This has happened multiple times. So whenever that happens I need to flash the pc36img and I still have everything on my sdcard, but the phone looks essentially back to stock and I have to set everything up again. I wasn't aware that the unrevoked root would still be applied.
What version of Clockwork do you have? From a terminal, type cat /proc/mtd and let me know what you see for erase size?
As far as unrevoked in concerned, it sets s-off lower than hboot, which means if you flash a pc36img, it will not fully unroot your phone unless you flashed the s-on tool, first.
What version of Clockwork do you have? From a terminal, type cat /proc/mtd and let me know what you see for erase size?
erasesize is the same for all of them: 00020000
Quote:
Originally Posted by akazabam
As far as unrevoked in concerned, it sets s-off lower than hboot, which means if you flash a pc36img, it will not fully unroot your phone unless you flashed the s-on tool, first.
thanks. I'll keep that in mind should I ever need to take it in to Sprint for repair.
ugh... I was going into recovery to check which version I have (clockwork mod - at least that's what I've always had before). And this was the first time trying to access it since doing the pc36img this last time, and now all I get is the black screen with phone and red exclamation point inside triangle. So I guess I don't know yet...
Last edited by fryc86; January 2nd, 2011 at 05:42 PM.
That's why you need to be careful with flashing PC36IMG files. They can wipe things out, like, say, recovery . So, what state are you in now? I'm losing track of threads here. Your phone is bootable, you have s-off, and your root is rooted, but you don't have recovery? Use ROM manager to flash recovery. You can either flash Clockwork 2.5.0.1 (available once again) or the just updated RA recovery (now 2.1.1). Do not flash Clockwork 3.0.x.x. it's pretty much broken right now.
That's why you need to be careful with flashing PC36IMG files. They can wipe things out, like, say, recovery . So, what state are you in now? I'm losing track of threads here. Your phone is bootable, you have s-off, and your root is rooted, but you don't have recovery? Use ROM manager to flash recovery. You can either flash Clockwork 2.5.0.1 (available once again) or the just updated RA recovery (now 2.1.1). Do not flash Clockwork 3.0.x.x. it's pretty much broken right now.
yeah I see that now lol. Yes my phone is bootable I have s-off and root access. I am pretty sure I have root access since all my root applications have worked and I have s-off. But now in Rom Manager while trying to "Flash Alternate Recovery Ra Recovery v2.1.1 I just get "An error occurred while attempting to run privileged commands!"
edit to say I get that error message when trying to flash any of the recoveries in Rom manager
Nothing is ever simply for me lol
Last edited by fryc86; January 2nd, 2011 at 06:03 PM.
yes su was the first thing I checked in terminal to see and it did change to #. Which Superuser app, the first one listed just named Superuser? I downloaded it and it says No apps in list.
ok, now its working and I flash the RA v2.1.1 and it worked and I'm now in Android System Recovery thanks for that. Now I need to get back to the original question about why my backups boot into white evo screen but never get any further...
Just did a back up on it. Is there anything else I should do before doing Nand restore? What's up with that back up google proprietary system files option? haven't seen that one before.
That's a weird error. /sdcard/nandroid/ is where your RA nandroid backups are stored. Boot up into android and make sure everything works. Open any file browser of your choice, then browse to /sdcard/nandroid/. You should find a directory with a unique number to your phone. In that directory should be another directory named after the date/time GMT of the backup you just created. Open that and verify there are .img files in there. If so, your backup was successful.
okay. It rebooted fine and I opened Root Explorer and there are a few files, I'm not sure how many there should be or if I'm missing any, or if there should be the files with 0 bytes in them.
android_secure.tar
03 Jan 11 00:33:00 ---rwxr-x 0 bytes
Hehe, I guess I should have thought to ask that question. Yeah, you need way more than 5mb of free space. Nandroid backups run in the ~500 MB range. clean up some space (give yourself at least 1 GB, then try again.
The Following User Says Thank You to akazabam For This Useful Post:
okay will do That was probably basic error on my part, but I really don't know enough about all this to be sure (and was already annoyed by not having enough room on my 8gb card so don't like removing any music if I don't have to).
This certainly explains any previous nandroid issues you may have had. Keep in mind that you can always copy nandroid backups to your computer so you don't clutter up your sdcard. You should always keep at least one backup on the sdcard, though. You don't want to get stuck without one. It's not unrecoverable, it's just a pita.
okay trying again. another question I don't know why I didn't ask before, but there is an option for nand backup or a nand + ext backup. Should I do one or the other, or both? thanks
If you've ever partitioned your sd card, typically for use with a2sd for moving all your apps to the sd card to avoid mounting issues, then you would choose the option to backup + ext. If you have never created a partition on your sd card or simply have no idea what I'm talking about, then don't bother with that option. If you try it without that partition, it will simply fail. You'll get a message when you restore that it didn't find an ext partition and it will skip it. That is normal for backups created without one.
ok thanks. Just thought I'd ask to be sure before going ahead. This time no errors or messages of any kind, just Performing backup: lots of dots and "Backup complete!"
And for the first time ever I got past the white splash screen during the reboot after a nand restore. And it looks as though everything is the same.
Thanks for all the help. I apologize for taking up your time for what was simply a sdcard space issue. Now I can start looking into the roms and kernels that are compatible with my phone now that I know I don't have to start over every time one doesn't work.
ok thanks. Just thought I'd ask to be sure before going ahead. This time no errors or messages of any kind, just Performing backup: lots of dots and "Backup complete!"
And for the first time ever I got past the white splash screen during the reboot after a nand restore. And it looks as though everything is the same.
Thanks for all the help. I apologize for taking up your time for what was simply a sdcard space issue. Now I can start looking into the roms and kernels that are compatible with my phone now that I know I don't have to start over every time one doesn't work.
That's great to hear. You don't need to apologize for anything. It's a learning experience for me just as much as it is for you. See, now I know what will happen if you try to make a nandroid backup without enough space. I'm always happy to help people out. I'm glad you got things working. Trust me, you'll pick up on things quickly.
I was able to root using the new unrevoked version yesterday. But today I had to erase everything and start over with the phone for unrelated reasons. Now when I try to do the unrevoked again I get the message: Internal Error: am reported error starting service
I've installed the hboot drivers for windows, selected charge only when connected, and checked usb debugging. And sync is not installed on my computer.
Anyone getting the Internal Error: at the end of the root process. Try this.
When Sprint announced their first ever 4G handset at CTIA in March 2010, they dropped a bombshell on the mobile world. The HTC Evo 4G is a device that introduces a lot of firsts when compared to other North American handsets. This is the first Andr... Read More
Unrevoked - Internal Error: am reported error starting service
