Hello everyone!
I restored a backup of my 2.3.6 rom, unrooted, locked the bootloader and got the ota sent to phone. I have warranty work coming up and I wanted to be 100% stock. When I power on phone with vol up / power and select recovery I am taken to droid on his back with a red exclamation mark in his chest.
Im guessing this happened when i did the update and noticed superuser was still there and it was a sys apk. So i rooted and used a root explorer to remove the apk and then unrooted. So my rom backup of 2.3.6 will always bring back the superuser. I looked around and have not seen much on this.
Any ideas or steps to take to fix and get 100% back to stock? I have a few ideas but i thought i would ask around first.
Thanks!
Try pressing the power button when you see the Droid figure with the red thing. Try combinations of buttons.
Sent from my Nexus S using XDA
Yes when I use volume up and power it then brings me to the stock recovery. I wonder if I root and restore my 2.3.6 would rid the recovery error. But then I need to unroot and when I do the superuser app remains. I just need a 100% stock. PS. I root / unroot using fast boot.
Sent from my Nexus S using XDA
I think the error is normal.
Sent from my Nexus S using XDA
I did have clocktouch recovery flashed when I unrooted. Its like the custom recovery wants to load. Doesn't seem right. Hmm is there a root slash unroot method that completely removes su. I guess my option is to flash back to 2.3.6 or if there is a flash able stock 2.3.6 and try update again.
Sent from my Nexus S using XDA
Related
I've rooted my desire using r6-desire-root-alt and flashed cyanogenmod6; then after 2 days the phone encountered a problem and returned back to htc rom!!
The superuser widget is not longer available! So I do not know if my phone is still rooted or not! can the phone be rooted without a superuser widget?? The clockworkmod recovery still available!
How the phone returned back to HTC rom on his own?? Can the phone un-root itself automatically?
Thanks
I have not heard of a Desire doing this. You said it had a problem and then it was gone. Maybe you restored the wrong image from Nandroid? Anyway, if your recovery boot is still available restore a back up of your rooted phone. You did take a backup after you got it how you liked it, right?
Unc.
try rooting it again, i unrooted my phone but when i root it again it says "still rooted" but no SU app
Did you try reinstalling SuperUser or SuperSu?
Use this app to check your root:
https://play.google.com/store/apps/details?id=eu.thedarken.rootvalidator
I lost root access after trying out a new rom. I first notice the problem when I tried backing up apps using Titanium Backup. It kept saying root access denied. I tried restarting the phone. That didn't work. I uninstalled and reinstalled Titanium backup; that didn't work. I soon found out that all my apps that required root access didn't work either. How I fix the problem; I re-downloaded the rom zip I was using. Place it at the root of sd card. Power off my phone. Push power and volume key. Selected recovery and I was in Clockworkmod. So I did a wipe. And I reinstalled the rom zip I was using. After doing that; I regained root access without having to go thru the whole root process again on my Inspire 4G. I don't know if it will work for other phones. Give it try and posts your comments.
Or you could of went into Rom manager, went to download tm, extras and downloaded and re installed superuser
Sent from my Inspire 4G using XDA Premium App
Thanks for letting me know. But; with out root access. Canyou still reinstall superuser from Rom Manager?
Yes sir. I remember I flashed a cyanogenmod nightly and there was a bug where it didnt have root. So I went into Rom manager and it installed without asking
Sent from my Inspire 4G using XDA Premium App
trell959 said:
Yes sir. I remember I flashed a cyanogenmod nightly and there was a bug where it didnt have root. So I went into Rom manager and it installed without asking
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
+ 1. I remember that nightly build you're talking about. Installing superuser through ROM Manager did indeed fix the problem.
i had that exact same problem probably should have read this forum before i restored to the original back-up of the inspire which for me was 2.2 -.-
still stuck. Help!
i have no root access and my clockwork wont root into recovery, not even when i try the sound button power up. any ideas on what to do next?
zr0lou said:
i have no root access and my clockwork wont root into recovery, not even when i try the sound button power up. any ideas on what to do next?
Click to expand...
Click to collapse
Turn off fastboot on your phone. Then power down or restart your phone and hold down "Volume Down" and "Power" till you see the bootloader. From there you can enter "Recovery".
As far as root access did you install superuser if not on your phone or included in your ROM for some reason? Have you even rooted your phone and installed a rooted ROM?
I posted this same issue a couple days ago.
Here is the fix.
clear data for superuser app.
menu-settings-applications-manage applications- find superuser
Clear data.
it worked for me.
I had this with revolution one time. Reflashing the rom will also do the trick.
Sent from my Inspire 4G using xda premium
I do not want to restore if possible. I did OTA update to my wife's stock rooted phone last night and now the home key does not work. Back key is only way to home screen. It vibrates when pressed but no action. She is already pissed about her tethering being disabled again. Any suggestions appreciated. I really don't want to have to tell her I have to restore. She didn't want the update in the first place.
Sounds to me like a fxz flash is the best option.
Flash back to 2.3.5 and root.
Flash one of our handy ROM'S that are currently available.
Get your teathering via sqlite.
Then your set!
Sent from my MB865 using xda premium
Thanks. I already had her talked into it. Think I figured out possible problem. I remember she uninstalled ONE of the original at&t apps. Update said completed but I think may have corrupted something. She had a lot of FC today, definitely major issue. Back to stock we go!
Hmm. I don't think it should have ever updated over the air with some of the att bloatware missing.
Atleast it didn't for me.
Well, it sounds like your on your way!
Sent from my MB865 using xda premium
If you haven't flashed yet, you can boot into Recovery from the Atrix 2 Bootstrap and make a Nandroid backup, then after you flash to stock and update to 2.3.6 and root you can "Advanced Restore" the "data" part of the backup to keep your apps and settings.
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Can you check your file system and see if your CWM folder has a backup? It should be Sdcard/CWM or extsdcard/CWM. If not, do you mind flashing another rom or that same rom?
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
2 questions: Which factory image did you use to restore (link to thread)? Did you change the default backup location in CWM (ie, did you backup to the external sd or the internal - internal is default)?
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Didn't unlock bootloader?
I don't know for sure. I unzipped SU plus bootloader file exactly as specified in forums/video. Had no problems until I tried installing that ROM through ROM manager. And forgive me for trying that. I hadn't rooted in over a year. But main problem now is just that I want to recover how my phone was ie settings and set up if possible.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How big are those 2 folders?
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That sounds about the right size for a backup. When you go into CWM and do the restore (or restore from external - which ever has that folder, you didn't say) it doesn't show a backup?
What version of CWM are you running?
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe after all that flashing and Odin-ing your recovery install got wanked, somehow.
Let's try this: it will re-install the latest CWM, clean and then let's see if it'll recognize your backups.
http://www.clockworkmod.com/rommanager/
download the touch image for the d2vzw (or just click here)
put that in the root of your internal sd card.
Open up terminal emulator on your phone and type the following:
Code:
su
dd if=/sdcard/recovery-clockwork-touch-6.0.2.3-d2vzw.img of=/dev/block/mmcblk0p18
reboot recovery
(partition 18 is your recovery partition)
That'll push the known good CWM to your recovery partition and boot you into it. It won't mess with any sort of data anywhere else on the phone.
Alright, thanks. I'll give this a try after I get back home from work.
Sent from my SCH-I535 using xda app-developers app
recovery
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
COuld you possibly link the file you used to get back to stock? i resently tried to root my device and it won't start.
No problem. Once again, I'm at work. I'll post it when I get home though.
Sent from my SCH-I535 using xda app-developers app
Hey guys,
Hoping someone here might be able to help me get rid of the bane of my existence right now. I've been reading all over and using various methods other people seem to have had success with but nothing is working for me.
I have a Samsung Galaxy Victory 4G from Virgin Mobile. I'm also responsible for 2 others that are having the same issue.
A while back I had rooted all our devices and put TWRP on them but have total stock rom.
A few weeks ago we all started getting this system update prompt that lets you install now or later. If we tried to install it with TWRP it just boots into TWRP. So I put the stock recovery back on and took the prompt and let it reboot. It begins installing but halfway through I get a red yield sign and it stops and reboots the phone. If we go this route the prompt usually doesn't show up again for days.
So I went and tried custom recovery and custom rom next. Didn't get the update on the custom rom until the next morning when I woke up. Went and got a perfect custom recovery/rom package for the phone and went total stock. Same issue as before where it gets halfway through and fails.
I've tried navigating to the root/cache folder as another thread suggested and renaming the update stored there but the update has never shown up in that directory.
Basically now, periodically this prompt continues to pop up, sometimes very frequently on the foreground of whatever you're doing on the phone and constantly reminds/annoys the hell out of us.
I'd take a screenshot but it hasn't reappeared in 2 days since I last took the update and it failed.
Appreciate any help from anyone!
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
bweN diorD said:
Your phone needs to be stock for the update to work. No custom recovery, no root, no ROM. Flash back the official stock firmware and the update should work.
Sent from my LG-VS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I had not thought to try going stock with no root. That is the only thing I haven't tried. Will report back. Thank you