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

Root Unrevoked - Internal Error: am reported error starting service

F

fryc86

Newbie
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.
 
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 :)
 
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.
 
akazabam said:
What version of Clockwork do you have? From a terminal, type cat /proc/mtd and let me know what you see for erase size?
Click to expand...
erasesize is the same for all of them: 00020000

akazabam said:
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.
Click to expand...

thanks. I'll keep that in mind should I ever need to take it in to Sprint for repair.
 
akazabam said:
Ok, and which recovery/version are you using?
Click to expand...

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...
 
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.
 
akazabam said:
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.
Click to expand...


:) 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
 
And you've verified in the terminal that you have root? Is this what you did?:

Open terminal
Type "su" without quotes, then enter
Prompt changed from $ to #

If so, you do have root. Do you have the Superuser app? If not, well, you need that. Open it and see if ROM manager is on the whitelist.
 
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.
 
Did you get any errors during the backup? If not, then you can restore if you like.

As for that other option, I'm not sure yet. I'll have to go look into that one.
 
It didn't specifically say error. But it did say "E: Couldn't open directory /sdcard/nandroid" This is what the recovery screen shows specifically:

Build : RA-supersonic-v2.1.1
E:Couldn't open directory /sdcard/nandroid/
Create Nandroid backup?
Pres Power to confirm.
any other key to abort.

Performing backup : ..........................
.....................................................
............................

Backup complete!
 
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

boot.img
03 Jan 11 00:32:00 ---rwxr-x 3.00MB

cache.img
03 Jan 11 00:33:00 ---rwxr-x 0 Bytes

data.img
03 Jan 11 00:33:00 ---rwxr-x 0 Bytes

nandroid.md5
03 Jan 11 00:33:00 ---rwxr-x 0 Bytes

system.img
03 Jan 11 00:33:00 ---rwxr-x 195.94MB

wimax.img
03 Jan 11 00:32:00 ---rwxr-x 384.00K
 
Well, those are the correct files, but definitely the wrong file sizes. Can you try to create another backup? Make sure your battery is above 30% btw.
 
okay... yeah battery's at about 85%... and now I'm actually getting an error...

"Performing backup :

Error : Run 'nandroid-mobile.sh' via adb!"

I've never been able to figure how how to run adb...
 
Weird, those are usually errors you get when the battery is low. Can you try reflashing recovery from ROM manager? Maybe it didn't flash right.
 
I'll try. I also searched for that error message and found this thread: Run nandroid-mobile.sh via adb! error. how to fix it? - xda-developers

One suggestion was to manually back up sd card and then reformat it then put the files back. after that do nandroid backup.

Another said that plugging it to the charger works (mine has been plugged in the whole time)

Another had a theory that it had to do with not enough space on the sdcard to expand. I only have about 5mb left on the card...
 
You must log in or register to reply here.
Back
Top Bottom