'Recovery Flasher' + 'Backup for Root' Problems. - G1 Q&A, Help & Troubleshooting

I have started a new thread from - http://forum.xda-developers.com/showthread.php?t=549622 - as this is a new problem and thought I would separate it out.
I'm having a problem with 'Backup for Root' after using 'Recovery Flasher'. I am now getting very confused about this process of rooting.
OK, so the story goes:
I thought that I could use 'Recovery Flasher' and be rooted there and then. Once I had done that I could use the 'Backup for Root' program, backup all my stuff, then I could boot into the recovery menu, flash, restore, whatever. But, it seems I was wrong?
After applying the Recovery Flasher' I can't seem to use the 'Backup for Root' program. Well, it runs and says complete, but there isn't anything on the SDCARD. Even if I reboot after using 'Recovery Flasher' it doesn't work.
In addition I downloaded 'Terminal Emulator', after applying the 'Recovery Flasher' program, from the market and ran 'su' on it and it said 'Permission Denied'.
Can anyone shed more light onto this? Maybe help me understand more? Am I getting things wrong anywhere?
The fruit of all this effort is that I want to install an Ion Rev.2 ROM, but I want to backup my apps and stuff first.
I would like to say thanks to DirectMatrix for helping out so far. His advice is to give up with the Rooting program and move onto more conventional (and longer) methods. I am this to agreeing and forgetting the rooting app.

you will not be able to use backup for root users until you flash a modded rom. you have to flash a modded rom for su to work check my sig for a guide to using 1 click root easily if you still want to do it that way.

Original question(s) seem to be solved.
Closing thread

Related

help installing apk using terminal

ok i just updated to CM 5. and well none of my apps are there, now im trying
this following :
sh /sdcard/installapk.sh /sdcard/theapp.apk
and no luck i think i can b doing it wrong.
cant DL the app cause i dont have the market app ether
Download DroidExplorer and you can do a bulk install of all your apps straight to the sdcard. Works everytime!!!
Link is in my sig
yea but i have no market on the phone and i dont have adb set up on my pc is it possible trew terminal to install astro so i can go on from there?
If your market is not there then you failed to flash the gapps.
You need to flash those AFTER CM5 or BEFORE. I've heard it works different for some people. First time I flashed it, it was before. Now it's after. Before and after won't hurt.
i figured that but the link on CM page for gapps is not working for me
I'm not really sure what having the market working has to do with anything. Clearly you didn't even take the time to click the link in my sig and go to the DroidExplorer thread.
it seems like that is for computers 64bit and up i have 32
brios86 said:
it seems like that is for computers 64bit and up i have 32
Click to expand...
Click to collapse
Are you talking about DroidExplorer? I have it installed on my 10 year old Dell and it is definitely a 32 bit machine. I'm assuming you are talking about something else.
You can use busybox if you have the latest CM ROM installed which you do. Busybox is included in the ROM so you can run busybox commands from terminal.
Put the apps you want to install on the root of your sdcard just to make them easy to find. Once in terminal, su so you have a # symbol
Then
Code:
busybox install /sdcard/yourapp.apk /sd-ext/app
great now i am F*** i tried installing the debug phone ota file that was required for CM 4.x and now i have no recovery it comes out the phone with exclamation mark
trying the droid explorer now
no luck droidexplorer seems to view the device but nothing else
brios86 said:
no luck droidexplorer seems to view the device but nothing else
Click to expand...
Click to collapse
Well that makes sense considering Droid Explorer requires root...According to your post on the first page, you are seeing an exclamation point when booting into recovery which means you lost root access by flashing whatever it is you flashed. Time to start all over again.
There is an updated rooting post for the Dream over at theunlockr.com
ok now my thing is i cant have the phone on cause it will keep getting FC and after a few it reboots
im trying to set up ADB on my pc now will that help me fix this? the phone boots up and the it reboots on its owne
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
DirectMatrix said:
It seems pretty clear that you don't really know what you are doing when it comes to modding your G1, and it is also pretty clear that you aren't willing to listen to directions.
I told you that you could batch install applications through Droid Explorer and you blatantly ignored my directions then said that it wouldn't work because you have a 32 bit computer.
I then gave you directions on how to use busybox to install the application that you wanted and never got a response regarding whether you even tried it or not.
You responded further into the thread saying that now you are getting an exclamation point when booting into recovery which MEANS THAT YOU DON"T HAVE ROOT ANYMORE!!!!!!!!!!!!!!!!!!
Installing adb and getting it working isn't going to do anything for you as far as installing applications because you lost root access which means you don't have the correct permissions to do anything anymore.
I gave you the link to an updated post on rooting so either do that or update this thread with where you stand exactly. Can you get into recovery? Is it an exclamation point? Can you launch the terminal app? When you type "su" do you get a # or an $? Does it say permission denied? ETC ETC ETC
Click to expand...
Click to collapse
My whole point with the no market is if he would have flashed the gapps or found another way to get them he could have installed a file manager then installed the app off his sdcard.
This was a 1 - 2 minute procedure that he has not made an hour/s procedure.
I agree with droidexplorer, I use it quite constantly. However, if he would have correctly installed CM5 this issue would have never arisen.
As for OP, I strongly advise that you unroot and stick to stock. If you cannot successfully do this, there is a high chance you are going to brick and it's just not worth it.
this is not the first time i try this i have a understanding of what i am doing, for some reason i decided to try another sdcard and it magically booted fine, now the gapps link doesn't work for me, so i am trying to install astro threw terminal emulator (astro is on the root of the sdcard) so i can just install the rest of my apps
thank you busybox worked thank you so much
funny after all the stuff i tried i decided to try a diff sdcard and it booted fine and then changed back to the old sdcard and it works fine

[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Easy & Safe!)

Turkeys' ULTIMATE Guide to Rooting v42.1.2
Note: It does not work on 2.2.1 Wildfire's (i.e. - Any bought after Feb - March 2011)
Like this guide? Hit the thanks button at the bottom left of this post
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me, you can do so below.
GBP
EUR
USD
So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...
So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...
Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF
Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!
A2SD
Note: It has come to my attention that doing this with ROM Manager doesn't work most of the time. If you have problems please partition your card another way. (I recommend GParted - There is a Live CD if you don't have Linux)
First, we need to partition your SD card with ROM Manager. This will wipe all the data on your SD card so please backup before continuing.
1) Open ROM Manager (Download it from the Market if you don't have it - Although you will need the Market Mod to show all apps) and press Menu > Manually Override Recovery **Not sure exactly what it says, pls could someone help me out here** Then scroll down to Partition SD Card. Choose the ext size you want for your apps to be installed on, then tap 0 for swap size, then tap OK to reboot into recovery and start partitioning!
Note: While it's partitioning it will show a picture of an Android. You can press (Power?) to see what it's actually doing and if there's any errors.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.
Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Buzz. Now, you need to recall what version of Android you were on before you rooted. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.
Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse
Reserved for good measure.
I'm sure this will help many people. Should be sticky'd
HCDR.Jacob said:
I'm sure this will help many people. Should be sticky'd
Click to expand...
Click to collapse
Good Idea!!!
For the rru you need to click on the windows mobile section and select buzz NOT bravo
Added A2SD guides, misc fix & unroot guide. Bump to v42.1.2
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
PanGalactic said:
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
Click to expand...
Click to collapse
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
42turkeys said:
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
Click to expand...
Click to collapse
And buzz is under windows mobile for some reason
The guide really great....but the shipped rom website don't have RUU for Buzz
coltrain said:
The guide really great....but the shipped rom website don't have RUU for Buzz
Click to expand...
Click to collapse
Look under windows mobile - who put it there? Those files do work.
This thread still not stickied?
Piece of art already. Should be stickied for sure.
I thought a bit about 'reporting' the thread to make a mod notice it but it said specifically what report was to be used for , so i didn't do it , i guess we'll have to bump it up so it gets stickied. Great post !!

[Q] About to root phone with 2.32.651.2

Hello,
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version, or should I downgrade. If I need to downgrade, can anyone tell me which software version I need to downgrade to in order to root, and a thread linking to a guide to downgrade?
forum.xda-developers.com/showthread.php?t=847993
this should do it
I think you can root this version, search around... if it possible you will find a post regarding it.
If you plan to downgrade, I would recommend .5 and then root using regaw's method - you should find all the details on the CDMA hero wiki page.
xlectik67 said:
I unfortunately just updated to 2.32.651.2 before deciding to root my phone. Is it still possible to root with this updated version [?]
Click to expand...
Click to collapse
HERE is the link to the post i wrote (in the thread which guided me) to get root in this stock-rom... so, yes, it can be done...
as far as dowgrading, im not sure i would recommend it - but as mentioned earlier, the wiki has a guide which i believe is based on a ...31...5 version you could use...
gl, h.
Root Sprint 2.32.651.2 OTA Permanently (in 10 steps)
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
ccrosno said:
Hi All
I have been able to root the Sprint 2.32.651.2 OTA permanently with the old boot-patched method. It is a little tricky and requires some knowledge of the Android SDK and Android Commander (There are several documents on how to install and use these 2 tools. Please search them out and learn.)
None of the other rooting methods seem to hold root after booting on this update. I have done this twice and it retains root permanently.
You must follow these steps to the letter.
First gather the tools needed for this root method
Android SDK (up and running)
Android Commander (androidcommander.com - makes moving and deleting so much easier)
SuperOneClick http://forum.xda-developers.com/showthread.php?t=803682 (this will give you temporary rootand install superuser, It is only temporary. After you do a boot the phone will loose root)
RomManager (download from Market after you have temp root)
Boot-Patched.zip (place this at the root of your SD Card. Flash through recovery. This is what will give you permanent root. File attached)
I take no credit for the tools that are needed. They are freely distributed. If I could remember who they belonged to I would give them props. Props to all the devs for making my Hero more enjoyable!!!
Process:
1: Install Android SDK. Make sure it is up and running and you have knowledge of the tools
2: Install Android Commander. Make sure it is up and running and you have knowledge of the tools
(Plug your phone into your computer with a USB cable)
3: Download and install SuperOneClick on your Windows based computer.
4: Run SuperOneClick.exe from the programs folder and click the ROOT button. (this will give you temorary root and install superuser onto your phone)
(At this point DO Not Reboot!! You will loose root and have to re-run step 4)
5: Download and install RomManger from the Market
6: Open the RomManager App and install the Clockwork Recovery (now you have a custom recovery on the phone. This will allow you to run Boot-Patched.Zip while temporarily rooted.
7: Through Android Commander copy Boot-Patched.zip to the root of your SD Card
8: Once Boot-Patched.zip is copied, boot into recovery either from Android Commander or RomManger
9: From recovery, flash boot-patched.zip like any other ROM. (this will permanently root this Sprint Update)
10: From recovery, boot the phone. re-run Android Commander and look at the bottom left corner of the program window. If it says "root OK" then it worked. If it says "root NO" then start over at step 4.
To test if you have permanent root, through Android Commander, remove a stock app that you do not want on your phone. If it works, you have permanent root. You will not be able to remove apps with temporary root.
I have an understanding of all of these tools. For you noobs out there, just keep learning. Trial and Error that is how its done. Keep asking questions (in the right forums please) someone will answer.
Enjoy
PS: Once rooted your WiFi will be non-functional. The only Kernel I have been able to get to work with this update and fix WiFi is the ZenKernel from 08122010. Serch it out, download and flash. (If you dont, you will be stuck with a phone with no WiFi and a top speed of 585mhz through SetCpu)
Click to expand...
Click to collapse
Sorry I forgot to mention that there were a couple times that the phone locked up durring the reboot to recovery stage. I do not know why. I beleive that it was due to forgetting to install the recover before rebooting. If this happens, pull the battery, replace the battery and start over.
Thanks
tailsthecat3 said:
forum.xda-developers.com/showthread.php?t=847993
this should do it
Click to expand...
Click to collapse
my WiFi worked fine after rooting the ota update by following the linked method. ^
Go ahead and root using the method mentioned above, if anything goes wrong... you can always RUU and reroot.
BTW, I have downgraded using .5 RUU and rooted my phone, so based on my experience I can say, it works well. I had initially rooted my .7 and was running CM 6.0 stable, had some issues, got my recovery screwed up, so had to go all the way... ;-).
tailsthecat3 said:
my WiFi worked fine after rooting the ota update by following the linked method. ^
Click to expand...
Click to collapse
Ya I tried that one. Couldn't get it to take. Mine is sort of the non-syntax method.

[Q] OneClick Root Works, But Superuser App Missing?

Hi, I posted a similar question about this under the OneRoot thread, but I don't see a lot of activity there anymore, so I was hoping to get more responses in a separate thread. I've scoured this forum and everywhere else on the Net and I haven't seen anyone experience this same issue. Hopefully someone will understand the problem and have some idea how to rectify it.
So, I have an AT&T Samgsung Captivate with the stock 2.1 Android "Eclair" build on it. I do believe there was an AT&T issued OTA update for it not long ago that put the build number up to UCJH7. I followed the instructions for TGA_Gunnman's One Click Root/UnRoot method documented here. Everything seems to work fine, in terms of booting into the recovery mode and selecting the update file. After the phone reboots, however, I do not see the Superuser Permissions app with ninja icon in my Applications area. If I browse the directory tree in my internal SD card in /system/apps, I do see a SuperUser.apk file. However, clicking on that shows me the message "Install blocked: For security, your phone is set to block installation of applications not sourced in Android Market." So it appears that rooting procedure worked, all the necessary parts were installed, but I don't have permission to execute su. I see that the xbin folder has been created, and it does contain busybox, su and something called ipctool. Also, a link does exist in /system/bin between su and /syste/xbin/su. If I use the Terminal Emulator and type "su", the prompt sits there for 10 seconds and says "permission denied".
Any ideas on what could be preventing me from gaining superuser access here?
Thanks for your help,
Mike
Download and install "SuperUser" from the Android market
OK, so here is another strange thing about this. This doesn't seem like it'd be related to my original su permission problem, but you never know. I decided to try to un-root using the one click method. Now, during the un-root script, I see the adb daemon start, but it fails on the push command writing unroot.zip to update.zip in the /sdcard folder; it says that permission is denied!. Of course, after booting into recovery, applying the update file fails, as it wasn't found in /sdcard. I'm not sure how this could have happened, as the root script was able to push the root.zip to sdcard just fine initially. Now, after I open a shell against my phone using adb, I check the permissions for the sdcard folder, and this yields rwxrwxr-x. I'm not sure, but I believe there should be another w flag set for other on sdcard. How the heck could that have been cleared?
It does look like I can copy the update.zip to sdcard manually through Windows Explorer and just manually boot into recovery using volume up + down + power, so I'm not completely dead in the water. Yet, I'd like to fix the permissions for sdcard, or else I can no longer use the one-click method.
id10terror said:
Download and install "SuperUser" from the Android market
Click to expand...
Click to collapse
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
mskelton said:
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Click to expand...
Click to collapse
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
End points are HIGHLY important, and if you read your post carefully, you have not yet demonstrated that superuser access is broken, only the icon from which you inferred it is broken. Let me know then we can go from there
Sent from my SAMSUNG-SGH-I897 using XDA App
fatttire said:
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks, that was one of the first things I tried last night, but that did not work.
fatttire said:
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, you're right, now that I see that error message, I guess it is trying to install it. That's odd, because I thought that the oneclick method would have already installed this app during the recovery boot load?
Regarding ROM manager, funny you should ask, that was the entire genesis of why I'm trying to root, so I can backup my phone and install the custom ROMs. After I installed ROM manager and tried to run it was where I initially noticed I must not have root access. When I try to flash clockwork recovery, the app hangs for (oddly enough) around 10 seconds. I never see any prompt for granting root access to clockwork recovery, nor does it boot into the recovery mode.
Okay I have another idea.
If your goal is to simply make a backup to flash a ROM, try this:
1. Download Cog 2.3b6. Other ROMs may have the file I'm looking for but I know it is here. Also you may be able to search and find this file directly but I'm too lazy to find the link for you lol
2. Open the zip file on your computer and extract /sdcard/update.zip
3. Adb push update.zip /sdcard/update.zip
4. Reboot recovery, reinstall packages, you are in clockwork recovery and can back up your ROM.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to try that, except that it appears there is some type of permission snafu on /sdcard. I believe the permissions on that folder *should* be 777, but it is 775 (other has no write access) for some odd reason, and I have no clue how that happened. Hence, when adb tries to push the update.zip to the internal SD folder, it gets permission denied. As I mentioned, not sure if this is related to not being able to execute su, but it is strange nonetheless.
Guys, please disregard what I mentioned earlier about adb and not being able to push the root/unroot.zip to /sdcard. I'm a moron, and I had left the internal SD card mounted to Windows after connecting the phone via USB. Clearly for adb to push/pull off of /sdcard, the internal SD card must *not* be mounted by Windows. My mistake, sorry for the confusion.
The original theme of the thread is still unanswered though, which is how the one-click root could have worked and not installed the SuperUser app onto my phone.
I will try the recommendation earlier in the thread, to download and install the SuperUser app from Android Market to see if that fixes things.
OK, so I downloaded and installed the SuperUser app from the Market, and for whatever reason, this seems to have addressed the issue. I am now prompted to allow applications root privileges. I'm not sure why this was necessary or how it fixed things, perhaps because it overwrote the version of su that was on my phone with a newer one. In any case, it's working.

[Q] [UPDATED]some question about signal, contacts and app on sd

Hi to all...
I have a big problem
I have a N1 with froyo 2.2.1
radio rom 05.12.00.08
build frg83D
And I cant' recieve OTA because it said that my version is upgraded....
But this is not the main problem...
I've root the mobile with SuperOneClickRoot and everythings goes fine, I have the icon in the launcher and I have the phone rooted...
I've tried to flash the recovery of amon Ra with the terminal app, and it said that flash_image not found...
So I've tried the ROM Manager and I've installed clockwork...when the yellow status bar finisch it gave me and error that some command cannot be executed with high privileges (or without high privileges I didn't remember the error was in italian language)...
What I have to do? I'm stuck with this phone...maybe rooted but it seems that anythings works on it
Please...
Thanks in advance
EDIT:
Please read THIS for the updated questions
Thanks
RealPsygnosis said:
I've tried to flash the recovery of amon Ra with the terminal app, and it said that flash_image not found...
Click to expand...
Click to collapse
Interesting.. It's not found? Did you also where did you put the file and what was the command you did? Also.. what instructions did you follow? I'm assuming you typed in "su" as well right?
Try either fixing permissions via ROM Manager, or installing busybox through the Titanium problems menu...
Maybe it's because I've root the phone without installing the SDK but only the driver for nexus?
when I root I see that all adroid driver for windows was installed except the one of nexus...
Can I install SDK and then root again?
Of course it won't allow you to use flash_image - you don't have the executable on your phone.
Please read the proper manual in Wiki under "Installing Recovery image" (link in my signature), and follow the manual step by step.
Just because you have superuser in the app draw does not mean you're rooted.
Sent from my Nexus One using XDA App
New question
I've found out that the problem was that ROM Manager doesn't have the root privileges -.-
So I've installed amonra and cyanogen...
everything is good but I have a really BIG problem
The phone sometimes goes to "only emergency call" also if there are strong signal, maybe it's the Radio? can I re-install it? or can be the sim-card?
Sometime it happen when the phone is for long time stand-by some time random...it's pretty annoying
I've installed Cyanogen mod, the phone is already rooted?
how can I import windows contact to android?
There is a way to config the app I want that can notify me?
Can I install app directly on SD instead of trasfert it after they are installed on the phone memory?
Thanks in advace
1. It's not a radio.
2. Yes.
3. Google can answer that with 1000 guides.
4. Only in the app itself. There is no external control over notifications.
5. There's an option for that in CM. I don't suggest using it or transferring apps to SD that weren't meant to go to SD - since the next question you'll come with would most probably be "Why are my apps/widgets disappearing".
ahahah LOL
thanks, but I didn't understand well the point 5 about the app to sd (why some peole talk about App2SD???)
And if it is not the radio what is it???
There are several options for moving apps to SD. In CM7 they use the default option, existing since Froyo days. This default option has several limitations that you need to know before using it - I wrote them.
The other way is partitioning the SD card, adding another partition to it, and running a special set of system scripts that moves all the apps by default to that partition.
Please read FAQ, question 13, and the thread that it links to.
If it's not radio - it can be your SIM, it can be your signal, it can be your phone, or anything else. The radio is just a SW build, and it works.

Categories

Resources