I had to get a replacement because the vibration conked out on my fascinate (not due to a DI01/DJ05 mixup). It's just dying a not so peaceful death. Anywho, I've got the stock nandroid flashed and I'm back on stock kernel, but I want to remove the superuser apk so that I don't have any traces of root when I send it back. All of the threads in the sticky take you back to stock WITH root. I have a Mac without boot camp, but I'm going to use a friends computer this evening to work on this, so I've got one shot to make sure I do this right and git 'er done.
I'm familiar with adb, so I tried using some instructions on Android Forums Fascinate ADB or SU Terminal Unroot Method, but no dice. When I hit the line saying "rm /sdcard/Superuser.apk" it errors out because superuser is in the system not the sdcard. Any help that you can give would be greatly appreciated, as i've got to send the replacement back tomorrow.
Their is a DI01 image over in the Development thread that will get you to stock without root. Flash it with Odin, and you will be all set.
Thanks,
Chris
Amberlina said:
I had to get a replacement because the vibration conked out on my fascinate (not due to a DI01/DJ05 mixup). It's just dying a not so peaceful death. Anywho, I've got the stock nandroid flashed and I'm back on stock kernel, but I want to remove the superuser apk so that I don't have any traces of root when I send it back. All of the threads in the sticky take you back to stock WITH root. I have a Mac without boot camp, but I'm going to use a friends computer this evening to work on this, so I've got one shot to make sure I do this right and git 'er done.
I'm familiar with adb, so I tried using some instructions on Android Forums Fascinate ADB or SU Terminal Unroot Method, but no dice. When I hit the line saying "rm /sdcard/Superuser.apk" it errors out because superuser is in the system not the sdcard. Any help that you can give would be greatly appreciated, as i've got to send the replacement back tomorrow.
Click to expand...
Click to collapse
Awesome, just found the thread. They really need to sticky that with the rest! Hopefully I should be golden by tonight.
Related
Some how I lost root access to my phone. I was having memory issues with the phone and after uninstalling everything it was suggested I install a memory manager. I did and it didn't work so I uninstalled it and I think my root access went with it.
At any rate I was instructed to open a command line on my phone and type SU and see what happens. I installed ConnectBot so I could get the command line access and typed SU and it came back access denied. So I guess that proves I lost my root access. But my question now is what guide do I use to get it back? The original guide I used said it was for v1.5. The other guides listed are for people that have done the OTA and have the Sprint 2.1 running on their phones. Well I'm in between and I have Damages 2.09.1 rom.
So what is my next move to get the root back? In reality do I need root at this point? What would happen if I just reflashed DC's rom again?
Help or comments will be appreciated.......
Lisa
You didn't lose root, you lost Superuser, search the DC2.8 thread about SU...
I did and either didn't find the right threads or didn't find the solution but I didn't get it fixed. All I found was that debugging needed to be checked and it is. Still no SU access. Give me. More help if you can......
Thanks...
Lisa
I did and either didn't find the right threads or didn't find the solution but I didn't get it fixed. All I found was that debugging needed to be checked and it is. Still no SU access. Give me. More help if you can......
Thanks...
Lisa
Download superuser from the site below and flash it though recovery. That should fix it. Make sure to get the proper zip for your version of Android.
http://handheld.softpedia.com/get/System-Utilities/Enhancements/Superuser-106560.shtml
Open your app drawer...Do you see anything that says Superuser Permissions?
What memory issues were you having? If it was storage problems, perhaps try Apps2SD -- usually takes care of any internal storage issues when you get it working. This thread here is for A2SD: http://forum.xda-developers.com/showthread.php?t=715116
Reflashing the DC ROM really wouldn't hurt anything either, you'd just have to re-setup your accounts, preferences, etc. and redownload all your market apps.
Lots of good information in these two responses. I have some questions. First what Rom do I have? Cupcake, eclair, donut? Just know its DC's last Rom.
Next could you explain how to "flash from recovery". Is that done through Nandroid?
Next I do have SU in my app drawer. It will open and has a green button besides my to programs that use SU. But SU doesn't seem to be working.
Finally flashing the Rom again is something I want to avoid as I really don't want to start from scratch.....
Thanks for your help.........
Lisa
mslisaj said:
Lots of good information in these two responses. I have some questions. First what Rom do I have? Cupcake, eclair, donut? Just know its DC's last Rom.
Click to expand...
Click to collapse
These refer to versions of Android. You have 2.1 which is aka "eclair". 1.5 was aka "cupcake", 1.6 was "donut". Almost all ROMs here are 2.1 eclair, with the exception of the cyanogenmod which is android 2.2 aka "froyo".
mslisaj said:
Next could you explain how to "flash from recovery". Is that done through Nandroid?
Click to expand...
Click to collapse
No, it is done in recovery. To boot into recovery, hold Home then press Power on your phone. One of your recovery menu options will be "Flash zip from sd card". After you put any .zip files on the base/root of your SD card, this is how you will flash (or install) them. "Nandroid" only refers to the process of backing up and restoring your data, which is a separate option in the recovery console (Backup/Restore)
Did you try reinstalling the Superuser.apk? It may just need to be reinstalled.
Mr. chromiumleaf.....
Thanks so much for the information here. I have "flashed" from recovery but didn't realize that was what it was technically called. I have in my own terms refered to "Recovery Mode" as Nandroid. But now I will associate both as one. Thanks for clarifying what version Rom I'm running. I didn't want to guess so I asked. I think I will uninstall the Superuser that I have now and then reflash the new version that I will down load. I will report back. This would be so cool if this settled my problem............
So appreciate it and I will let you know..........
Lisa
I am following through as I alway do to thank you all for your help and tell you how I resolved the problem. I received some great advice from everyone and the last tip, which is usually my luck was the best.
The bottom line someone questioned why I thought I lost root. I explained what was going on and the best and final suggestion was to down load the latest Superuser.apk and flash through "recovery". Yes I had to ask exactly what that meant but I followed the directions and did it. Problem solved. I had SU working on my phone for Root Explorer and Titanium Backup. Then I downloaded Cachecleaner and it worked this time perfectly and it found 25MB of junk on my phone and cleared it out. So now I'm running 40MB of internal memory with all my programs working rather snappy now. In my estimation I screwed up the SU with the memory manager that was recommended somewhere along the line. When it didn't do anything for me I uninstalled it and I think my SU went with it. But the phone is fixed and I want to thank you all for your time in responding to my problem and requests. Sometimes multiple............
Thanks again.....
Lisa
Good to hear you got everything fixed. Glad to have helped out.
Yeah...and that's why there are people in this world more patient than I.
Sent from my HERO200 using XDA App
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted
Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S
I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?
Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...
Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.
I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke
Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"
pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?
When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it
I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....
i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)
I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)
So, this G2 is my first real phone, and I was really excited about rooting it and putting CM6 on it so I've been reading and trying to learn as much as I could so I wouldn't end up screwing things up. However, I'm stuck in a peculiar situation.
First, I'd like to point out I don't have a computer I'm able to download any programs to (android dev tools like adb). I can use my brothers computer to download files onto my phone, I just aren't able to install programs to his computer. So, any advice would be appreciated if it took that into consideration.
Anyway, I'd been keeping up with the VISIONary updates since about r8, and when it got around to r13 I tried to do the perm-root. It didn't work, and so I tried to read and troubleshoot the situation. I saw a couple people talking about temp-rooting, doing clockwork recovery, and then rebooting and it working out alright, so I tried that. What I did was I temp-rooted with VISIONary, did the clockwork recovery and then tried to reboot and perm-root the phone. Unfortunately, what's happened is that I can't get even get temp-root anymore.
So, I guess what I'm asking is simply this, is it possible to fix my g2 and get it rooted using only the phone itself?
I have tried booting into recovery with clockworkmod and also stock recovery many times. I have disabled fastboot and each time I have tried I get the picture of the phone and the triangle.Once again I have fastboot turned off. I have searched the threads and tried what ever I found and nothing has worked. I am wanting to do a nanroid backup and I am getting more and more discouraged each time I try and it fails. I guess maybe its time to send it back as I have 4 more days left on buyers remorse. Thought I would try to solicit some help before making the decision to send it back. I have a Nexus One and a Vibrant and have never had this problem with either one of them. I have tried it with the Visionary temp root applied and with it off and does not make a difference. I have not applied the perma root yet. Any and all help is and will be greatly appreciated
I had a similar issue. I would do the full permroot, then flash clockwork recovery through fastboot.
Thanks so much for the swift reply. I am not sure if I am going to keep this phone so I am not wanting to permaroot at this time. Is there not a way to flash recovery without doing permaroot? i read where Paul Obrien states in his thread for permaroot that one should do nanroid backup before doing permaroot. This leaves me very confused. How in the world do you do that???lol It looks like the decison to send it back or keep it is being made for me. I have never called CS and asked for help to flash recovery as I feel that they would not respond favorably and want to know why I want to flash recovery, but that could be wrong also. Help!!!!!!!!!!!
Edit:Just got off the phone with tech support and they state that recovery cannot be accessed as a safety feature. Not sure I believe them as he did not know what fast boot was or what a nanroid backup is. He said the little phone and the triangle with the exclamation is the bootloader screen and no other screen can be accessed after selecting recovery. Any and all help and info is GREATLY appreciated.!!!
Help PLEASE
tenbeau said:
Help PLEASE
Click to expand...
Click to collapse
I'm not sure how far you'll be able to get, but I've been in your position before, so anything I can suggest to help-
http://forum.xda-developers.com/showthread.php?t=834225
If you follow it EXACTLY it should work out- you might have to try a few times- I did, he also includes the script to return it to S=on. The terminal emulator worked best for me
Once you get permroot you can get clockwork on there.
I don't understand what you're trying to do. Are you trying to boot into CWM recovery or the stock recovery? The way I understand it is that once you flash CWM, it overwrites the stock recovery. And furthermore, if you're trying to make a nandroid, you will need to boot into CWM. If you need the stock recovery back, someone posted a link to reflash it back onto the phone.
Follow the above instructions on how to turn s-on. Itz actually easy. Jes download the files, type in 2 commands in terminal emulator, you are now perm rooted with s-off. That easy. If you want to unroot, go to visionary and click on unroot, simple and works like a charm
Sent from my HTC Glacier using XDA App
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
drk.hd said:
The touchscreen on my Fire stopped working today. I already talked to Amazon and am getting a replacement, but I want to revert back to stock before sending it in. I've seen ways to do this with TWRP, but I don't have a touchscreen to use TWRP, or any recovery for that matter, with.
Is there any way to do this?
I do have full ADB and Fastboot access, with FireFireFire working, but do not have a currently working rom installed (I was on CM9, and it won't go past the boot screen).
Click to expand...
Click to collapse
There is a way to do this with adb... I just do not know the proper commands. Sorry
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
sengwall said:
Does installing a custom rom void the warranty? Seems like it would be BS for Amazon not to honor it when it's apparently a hardware related issue.
Click to expand...
Click to collapse
No, I don't think it does, but I'd rather not take the chance.
drk.hd said:
No, I don't think it does, but I'd rather not take the chance.
Click to expand...
Click to collapse
YES! It absolutely does. The second the device was rooted it broke warranty.
Sent from my myTouch_4G_Slide using XDA App
The same thing actually happened to me earlier today. I was just browsing some sites on the ICS rom when it just stopped responding. I couldn't get it to recognize any touches even after a bunch of reboots, so I just figured it to be some bug that hadn't been squashed yet. When I dropped down to recovery and saw the same issue, I knew I had a real problem.
Hoping against hope, I tried both CWMR and TWRP on it and got no results. Like you, I figured it would have to go back to Amazon, so I started searching for a way to get it back to stock... nothing obvious jumped out at me because everything is written with access to recovery in mind... which doesn't help.
So, I started reading about adb and going through the built-in help. As I was familiarizing myself with some basic adb commands and options, I left TWRP open in front of me. I don't know how long I had it that way when I mindlessly tapped on the screen and thought I saw it flicker. Yes! I had pressed the Wipe button and it had taken me to that section. It's been working fine ever since.
I'm not claiming I did anything and I don't have a how-to on how to fix it, but it couldn't hurt to just leave the thing running in recovery for a while and see if the touchscreen comes back to life for you too.
Still, I'd love to see someone with more adb knowledge provide a simple tutorial on how to get it back to stock without access to recovery. I'm sure it would be helpful to someone in the future... maybe even me if the same problem comes up again.
Best of luck to you.
Just ignore my comment
Sent from my Amazon Kindle Fire using Tapatalk
If your on the rooted stock rom you could always wait until Amazon pushing the next OTA
You will have to make a fastboot image and flash that with fastboot. But before you create the image, you will have to create all the appropriate symlinks. Then you run...
Code:
make_ext4fs -l 512m -a system -s /path/to/fastboot_system.img /path/to/system_folder
That will create the fastboot image. Then when FFF gives you fastboot access, you run...
Code:
fastboot flash system fastboot_system.img
You will also need a fastboot image for recovery and the bootloader.
Isn't there any easy way like with my desire, simple ruu.
Or hasn't anyone created these images to flash. I also need to get back to stock everything and send it to amazon, my wifi gets error after some period of time and some times when screen goes off, try'd 3 roms and stock.
There is a way to tell the device to install /sdcard/update.zip via shell commands. I forget what they are tho. Something about the extendedcommands. If I have time tomorrow I'll look it up.
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
b63 said:
here it is:
http://www.theandroidsoul.com/kindle-fire-stock-rom-installation-guide/
Click to expand...
Click to collapse
Thanks for the link. I'm back on this thread because I think my Kindle Fire touchscreen is now dead for good. However, those instructions do not work as-is because you need to press a button on the screen to tell the Kindle Fire to allow the host to mount it as a USB Mass Storage device. Although those instructions don't get you all the way there, I was able to use the core idea to get my Kindle Fire back to stock. So, many thanks for pointing me in the right direction.
On top of the touchscreen not working, I ended up partially bricking the device trying to find a way to flash it back to stock, so I had also posted in the Unbricking thread. I posted my solution there....
http://forum.xda-developers.com/showpost.php?p=23226260&postcount=701
Odds are, if you have a device that is booting correctly, you will be able to ignore steps 3 and 4 and get it booting back to stock. I do have a couple of other suggestions... Leave your USB cable hooked up to the Kindle Fire as it boots into stock for the first time. This is the only time that it will automatically mount the /sdcard to your computer and you will have a chance to reclaim (and delete) all the files stored there. You can also do something like 'adb pull /sdcard C:\sdcard' before you flash. Also, depending on what ROM and apps you were using before starting the process, you might want to delete your user data and reset the device to factory defaults. You can do this with 'fastboot erase userdata' and the next time you start the device, you'll get a warning that it's about to reset. Hit the power button and you should have a clean, fresh from the factory Kindle fire... albeit with a broken touchscreen. Good luck!
After several failed attempts to follow this guide (no offense to posters; I appreciate your contributions), I found this to be the simplest method.
http://stackoverflow.com/questions/10817721/wipe-data-factory-reset-through-adb
Download stock update, then it's basic procedure in adb:
adb push C:/update.zip /sdcard/update.zip
adb shell
recovery --wipe_data
After reboot, go back into to adb shell and do "recovery--update_package=/sdcard/update.zip"
Factory reset, etc. and you're good to go.