Am I un- Rooted? - Hero, G2 Touch General

I am selling my phone soon, so I downloaded RUU, did that, then installed the OTA update (4 mb file)
It was all successfull and the phone works.. Does that mean the Phone is back to stock condition (with origional recovery rom etc?)
i ask because when I hold power and home I get the exclamation mark in a triangle... Thanks,
Anthony

Yes.
And probably unrootable to boot

The instant root apk works with the new FOTA update, so no worries.
I have rerooted my phone with instant root, recovery flasher to get amon-RA's image. And flashed the pre-rooted stock rom from modaco's site.
dont worry

Related

Someone please help

I was rooted, flashed back to stock, had froyo working perfectly. I wanted my recovery image and someone told me to install superbot ere27, now i have no signal and everytime i turn my phone on it says "process system is not repsonding" then it soft resets. When i plug a cable up my computer doesn't recognize it so i can't go to fastboot or adb. I can only install zip files. the stock zip files from paul's website and the froyo zip do not install, i also tried to install "signed-passion-ERE27-from-ERD79.a487b405" no go, any ideas?
I'd say try getting the stock recovery image & uninstall the driver you have on the computer; download usb-driver.zip (easy google for android driver), see if you can get the ERD79 .nbh and flash it back to factory; after that upgrade to ERE27 & then back to froyo.
I'd avoid a custom bootloader for the moment; did you reroot it after you installed froyo with cyanogen's rooter?
JareduPS said:
I'd say try getting the stock recovery image & uninstall the driver you have on the computer; download usb-driver.zip (easy google for android driver), see if you can get the ERD79 .nbh and flash it back to factory; after that upgrade to ERE27 & then back to froyo.
I'd avoid a custom bootloader for the moment; did you reroot it after you installed froyo with cyanogen's rooter?
Click to expand...
Click to collapse
I was going to install cyanogens rooter but it said i needed a recovery image on my device first.
When i get the stock recovery image, how should i install it?

[q]gb root

I updated to the gingerbread-sense2.1 and lost my root. I was wondering if there is any way to root or go back to an older image version.
I dont think there's a way for you to reroot until a dev or somebody posts up a new root method for this update.
Right. Thanks.
I'm in the same situation.
Upgraded to 2.3.3 OTA and lost root.
Running the Android 2.2 RUU exe to downgrade fails with 140 bootloader version error.
Running the new Android 2.3.3 RUU exe installs just fine on top of itself.
I don't have clockwork installed and w/out root don't see a way to do so.
The restore zip from SD card method (http://forum.xda-developers.com/showthread.php?t=971550) also does not work - never get the "push vol up to update" option.
Any other suggestions?
P.S. When I get to bootloader and select recovery, screen shows this triangle with exclamation point icon. (pic attached). I would have thought "recovery" option should give me some more options, not just die like this...
I believe they locked the bootloader with the new OTA update. You will have to wait til someone comes up with a new reroot method.
P.S.
The devs already made a flashable rooted stock GB zip. The same day.
Evo SHIFT

OTA Update install keeps failing [i9023]

Hi
I have a rooted nexus S. When i first rooted it i had this issue
http://forum.xda-developers.com/showthread.php?t=1135929 and solved it using post #3.
Now when i get OTA updates the phone reboots and then the android icon with a package appears. the install begins but fails to and android with an exclamation mark icon.
I dont have logs because when i reboot the update isnt offered anymore for a really long time. does any one have any idea what could be wrong?
thanks in advance
The verify check has to complete and u need to flash it manually in custom recovery
I got this when I rebooted my NxS several times while the OTA was ready to be installed. It somehow got lost and couldn't be retrieved anymore.
As I couldn't find a solution I just reflashed the official 2.3.4 full rom and then got a) a working stock recovery and b) a working OTA again.
Official stock roms are signed and can be flashed via the stock recovery and don't need unlocked bootloader.
Thanks, i think i will wait for ICS and then reflash. I'm too lazy to do it all now and then again in a few months time.
Can you have permanent root with stock everything?
boozelclark said:
Thanks, i think i will wait for ICS and then reflash. I'm too lazy to do it all now and then again in a few months time.
Can you have permanent root with stock everything?
Click to expand...
Click to collapse
Depends on how you define "everything". You'll need at least an open bootloader to flash the superuser zip via a custom recovery(, can relock the bootloader afterwards).

Problems installing OTA updates

OK, for starters:
Tablet's current stats:
ROM: CWM-Rooted_Acer_A500_7.006.01_COM_GEN2
Recovery: Stock US 1.141.07_COM_GEN1
Root status: Rooted
Problem at hand: Cannot install OTA updates. I used Acer Recovery Installer to originally install CWM so I could flash ROMs (duh). So I used Acer Recovery Installer to have it install the stock recovery image so I could actually install the OTA updates. I know this likely means I would lose root, and that is OK.
When I installed the stock recovery back, I tried to let it install the update. It would reboot, show the package opening (little box that was open and a progress bar showed up). The bar got about 25% completed, then it changed into a triangle with a "!" inside it, and the little Android dude below it. After a few minutes, it would reboot by itself. Once booted up, I would get a message that simply said "Update Failed".
I brought this up in another thread, and someone suggested I unroot as well. I immediately tried to do that, but IconiaRoot gives me the following:
Removing superuser.apk
Removing /system/xbin/su
Sleeping in 5 seconds...
Something went wrong.. you are still root?!?!
I can confirm I am still rooted by going into terminal emulator and running su and I get a # sign. So I am at a loss now on what else to try. With the stock recovery, if I tell Acer Recovery Installer to reboot into recovery, when it reboots, all I get is the triangle with a "!" in it. I noticed the ROM has GEN2 and my stock recovery has GEN1, and the OTA update ends with GEN2, is that an issue?
EDIT: I also know now there are other rooted ROMs with these OTAs applied. I'd like to unroot and go back to stock, so please do not recommend this.
Ok did you make a backup via CWM ?
In the other thread the recovery i restored was the backup i made of my one via Acer recovery,
If i was you i would reinstall CWM and make sure that recovery is working then wait for someone to come in and tell you the correct stock recovery for your one is.
oh i get u now, u got the gen2rom installed and u want back to your own stock gen1 to get the OTA, correct?
u need a cwm backup of 3.2 gen1 stock, when u restore it, u should receive an OTA notification for the 3.2.1 GEN1 OTA. Before you download it, u need to be rooted, use the backdoor/OTA method of timmyDeans. It will create a backdoor so after you have installed the OTA you can get in to run the installtools command again to root and install cwm again. AND you will still recieve OTA's.
Iconia Root - only works on 3.1, it will not work for 3.2, so it will throw an error.
But i'm sure root wont prevent the install as the OTA overwrites system files and resets the permissions, it also checks all system apps are there, so if you;ve deleted any bloatware or changed build.props the update will fail.
I have spent the last week trying to get back to stock so i can OTA. I have read hundreds of posts and tried all the methods that had been posted. The easiest and quickest and most successful way of achieving this was the backdoor method. Yes you need adb installed but you dont actually use it, it is all done for you. there is a very good walkthrough here http://www.chdcomputers.gr/en/mnu-kb-en/mnu-kb-android-en/mnu-kb-android-devices-en/mnu-kb-android-a500-en/254-art-kb000005-en
Then install the backdoor v3 (link in sig) -have a look and see if that will get u to where u wanna be!
Decideed it was easieeer to just install one of the prerooted roms from the dev forum. Running 7.014.14.com gen 1 now. Thanks guys.

[Q] Help with 4.4.4 OTA

I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
sfobrien said:
If you want to stay stock here you go. Look at the last page or so and it also has a link to the newest TWRP which you need to get going again.
http://forum.xda-developers.com/showthread.php?t=2529492
Click to expand...
Click to collapse
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Lenster45 said:
No, I don't want to stay stock. I want to be able to install TWRP so I can flash SuperSu.zip and get root back. When I do a fast boot install of the TWRP Image, it completes with no errors but when I reboot into recovery, I get the dead Android with the exclamation point not TWRP
Click to expand...
Click to collapse
Since you took the OTA your bootloader may be locked. After you get it unlocked I gave you where to get the recovery you need, the one you have is not KitKat friendly.
Lenster45 said:
I was running 4.4.3 Rooted with TWRP recovery. Bootloader was unlocked.
I accepted the 4.4.4 OTA update and when it was done I found I lost root.
Tried to go into recovery to install Supersu.zip but had also lost TWRP.
Just got the dead android with the ! mark.
My Boot loader is still unlocked. I ran fastboot. Verified that I got a device id with Fastboot devices.
Then used Fastboot to install openrecovery-twrp-2.6.3.1-manta.img
Completed with no errors. Rebooted the device and then shut it down.
Rebooted into Fastboot, selected recovery and I still get the dead Android with the ! mark.
What did I do wrong?
Len
Click to expand...
Click to collapse
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
charesa39;53763629
EDIT: Oh said:
Strange, had a friend who took the OTA awhile back and it locked the bootloader. It was a JB version maybe they changed it with KitKat ? ( he could have locked it prior to my getting it going who knows) Thanks for the info, have never used an OTA since I got my N10 when it first came out.
Click to expand...
Click to collapse
charesa39 said:
Well, you didn't do anything wrong per se. When you flash the OTA (which I assume you did in TWRP), you lose root and your custom recovery since it replaces it with stock. You did the right thing by fastboot flashing your custom recovery back. However, the only thing you did "wrong" was rebooting into the Android OS instead of booting into the newly flashed recovery first. After you flash the custom recovery, select the recovery option in the bootloader, and it will boot into your custom recovery. If you don't boot directly into your custom recovery, and instead boot into the OS, the recovery will revert back to stock, which is why you saw the dead Android with the ! mark (that is the stock recovery). Just fastboot flash TWRP again, and boot straight into it. Then, just flash the SuperSU zip and reboot system. You should be good to go.
EDIT: Oh, and having an unlocked bootloader has no effect on receiving an OTA or your ability to flash it. If your bootloader was unlocked before flashing an OTA, it will remain unlocked. The only way it would become locked again is if you locked it yourself. You can even completely flash the stock image, and the bootloader will remain unlocked.
Click to expand...
Click to collapse
That did it. Thanks
Hi,
Could you add a [SOLVED] tag to the title, as it is now solved ?
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505

Categories

Resources