I was trying to downgrade from RC30 to RC7. Pressed Camera+Power button, after gray screen popped, it checks something and then an error popped..."Not allow"
What happened here?
*should be in q&a thread*
you may not be flashing the right dreaming.nbh or you may need to make a gold card first - don't have a link handy but google "cyanogen g1 root wiki" here you will have all the info you need as well as links to the proper downloads
Sent from my HTC Vision using xda premium
Actually, I really don't know where to begin. I cannot get into phone w/out register with google. But then, no wifi. Cannot run adb because everytime I plug in phone to pc, it reads the sd card. Already put all necessary files for rooting. Install everything but still end up with nothing.
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
SEP 2 2008
SERIAL 10
I tried all the bypass methods but nothing... no reboot, nothing.... Going around in circles as there are many guides on how to root this phone. Also applied the method where you code in the commands to activate developement w/out going into the phone.... that too cannot get thru. So far, I've tried 3 different ways to root. None of them worked.
Thanks....
well if you downloaded adb through the xda package and you followed the link in there to bypass and you still can't, I suggest finding someone with a tmobile sim card to bypass, then remove their card after you get wifi on and continue the steps
Sent from my HTC Vision using xda premium
I have T-Mobile simcard. Problem is there's no tmobile here on the islands. Now how do I activate wifi so I can register? At the moment, still cannot get pass the google registration because of no wifi.
the steps listed in the cyanogen g1 root wiki will do it, if you read through the wiki you will see a link explaining it very well
if you still have problems report back exactly what you have done, and you'll get more help
Sent from my HTC Vision using xda premium
Ok, I tried this link but got stuck at the following:
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now you have root!
Cannot accept "telnetd"....
so you are in the android os now? if so do you have telnet app downloaded onto phone?
Sent from my HTC Vision using xda premium
Not in android os. Tried adb devices and no devices shown. I tried this link but cannot enter "setprop persist.service.adb.enable 1". It doesn't change to adb development mode. Tried a thousand times. Could it be because this phone is network locked? But then I am using TMobile Sim which goes directly to the main screen.
Any other possible ways to activate the wifi?
I am very sorry guys. I just put up this computer and forgot to install android drivers but I plug in the phone. After numerous attempts, I decided to try other computers. Wallah, it reads phone as adb. All is fine now. Phone working perfectly.
Once again I am very sorry for all this.
Jabbacks said:
I am very sorry guys. I just put up this computer and forgot to install android drivers but I plug in the phone. After numerous attempts, I decided to try other computers. Wallah, it reads phone as adb. All is fine now. Phone working perfectly.
Once again I am very sorry for all this.
Click to expand...
Click to collapse
I was just about to mention the adb android drivers, as I recently had to perform the same steps (using a different xda guide tho, telnetd is weird). Congratulations.
Everything working?
Related
I've found a way to register the G1 in the initial registration screen that comes up the first time you boot the phone (or after you wipe the phone). It will allow you to register if you don't have a sim card at all, or if you have a sim card but no data plan.
First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry. If you don't know for sure what version you have, but you know you haven't installed a modified RC30 build, then the easiest way to check is to reboot the phone, and once it starts up and is showing the "click the android to begin" screen, or the "no sim card" screen, then type the following on the phone keyboard
<enter>reboot<enter>
If it reboots, then you have RC29 or ealier. Otherwise you have RC30.
Second, you must have adb installed on your computer, and have the USB drivers installed, or at least ready to install when it asks for the driver when you connect the G1. See this page for details on how to get adb working: http://code.google.com/android/intro/develop-and-debug.html#developingondevicehardware
Third, you must have a wifi network that you can connect to.
There are too many possibilities to write specific step-by-step instructions for every case. So I will give an overview of the process instead. If someone else wants to write some specific instructions, that would be welcome
-----------
When you start up the phone without a sim card, it goes into a locked screen that says "no sim card found", and you can't even get into the registration app. So the first step is to get around that screen. You have to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
And then reboot the phone. When it starts up again it will go into the registration screen instead of the locked "no sim card" screen.
This assumes that you have the sqlite3 binary on your phone. This binary is provided in RC30 v1.2. Alternatively, you could manually copy the binary to your phone with adb push, or put it on the sdcard and copy it to your phone. I can post a copy of just the sqlite3 binary if needed.
-----------
The second step is to enable and configure wifi, so that the registration process can connect to the google servers. In an adb shell session, type the following command:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
This doesn't have to have root access to work. It works fine with the "shell" user that adb on non-modded phones runs as.
That command will bring up the settings page on your phone. From there, you can enable wifi and connect to your wifi network, and then proceed with registration as per normal
------------
A few tips and tricks:
- If you have an official RC29 or lower phone, type the following command on the phone keyboard to enable adb:
<enter>setprop persist.service.adb.enable 1<enter>
- If you need to get root access on an official RC29 or lower phone, while it's at the registration screen, or the "no sim card" screen, enable adb (see first tip), and then type the following command on the phone keyboard:
<enter>telnetd<enter>
Now, copy a busybox binary to /data/local/busybox with adb push, and then connect to your phone with adb shell, and give the busybox binary execute permissions (i.e. chmod 755 /data/local/busybox)
busybox has a telnet applet, so you can do:
busybox telnet 127.0.0.1
to get a telnet session with root access.
- If you don't want to register the phone at all, you can set the app.setupwizard.disable property to 0 to prevent registration. Once you have an adb shell session open, type the following:
setprop app.setupwizard.disable 1
and then reboot. once it loads back up, it should bypass the registration screen all-together.
But beware, the phone seems a bit glitchy if you don't have it registered. For example, the home button doesn't seem to work. And you can't access the market or any of the google apps of course.
(Note: the following was the previous way to skip registration. I'll keep it here for informational purposes, but its easier to use the app.setupwizard.disable method instead of this)
- If you don't want to register the phone at all, you can edit /data/system/packages.xml and disable the registration screen. Add the following to the end of the <package> section for com.android.setupwizard, and then reboot:
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
so the full <package> would look something like below after the modification:
<package name="com.android.setupwizard" codePath="/system/app/SetupWizard.apk" system="true" ts="1217592000000" userId="10010">
<sigs count="1">
<cert index="0" />
</sigs>
<disabled-components>
<item name="com.android.setupwizard.SetupWizardActivity" />
</disabled-components>
</package>
He worked on this for a very long time with me and walked me through all the steps when testing this out. Great person.
Really nice...
I'll try to do it.
I have to study though...
I'll be in touch.
Thanks
thanks JF you are good in this thing.
My case i have sim card without data plan, when turn on phone show me screen for register email account with google.
c:\adb shell
show me # simbol
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
and in the phone show me the menu for connect to my wireless
conected, registered, go ahead.
thanks
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Ok, my device was recognised and "installed" but no driver was requested.
I have read I need to do some settings from within the g1, but I can't, since it's not activated! (http://forum.xda-developers.com/showthread.php?t=443797&highlight=info)
When I issue the "adb devices" command, I get no recognised devices...
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
cmavr8 said:
satru, in what screen are you typing "c:\adb shell"?
1. Before you click "the android"
2. while reading the agreement
3. When you can select "create" or "sign in" to a google account
4. Or later ? (where?)
Thanks
EDIT:
Ok, I hate to do that but:
I am completely stupid. I've been reading around xda-dev for hours and still can't find how to check what software I'm running. (prior or post RC30...)
In boot loader it says:
"DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.28
Sep 2 2008
Serial0"
Do I have RC30?
I couldn't get it out of bootloader mode, so I pulled the battery out.
Click to expand...
Click to collapse
A quick way to check if you have RC30 is to reboot the phone, and then once it starts up and it shows the "click the android to begin" screen, type
<enter>reboot<enter> on the phone keyboard.
If it reboots, you have RC29 or lower. Otherwise you have RC30.
If you do have RC29 or lower, then you can use the first tip I posted to enable adb. Once adb is enabled it should ask you to install the drivers when you plug it in.
satru said:
conected, registered, go ahead.
thanks
Click to expand...
Click to collapse
Great! Glad it worked for you
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
cmavr8 said:
Hi again, thanks for your reply.
I rebooted without sim card, no "click here to begin" appeared, just the "no sim card" notice.
I entered reboot and it rebooted! So this is good.
Now, with the phone connected, I type in terminal:
"[email protected]:/media/Docs/Android/tools$ ./adb shell
error: device not found
[email protected]:/media/Docs/Android/tools$ ./adb devices
List of devices attached
[email protected]:/media/Docs/Android/tools$ "
This is not normal, is it?
What should I do now?
(I also have a t-mobile sim card, not activated. It just came with the phone. I can go through the activation proccess (gmail account etc) but it can't complete as it's disabled)
Click to expand...
Click to collapse
Did you try my first tip to enable adb?
johnny13oi said:
To cmavr, try entering the restore mode and see if the computer will detect it then. Is it automatically mounting the SD card onto the computer? If it is then you probably have RC19 which is good. Try removing the SD card and plugging the phone into the computer.
Click to expand...
Click to collapse
Thanks for your reply.
SD mounting works fine.
In recovery mode nothing is better... (tried recovery without sd only)
Is there anything else I should try?
JesusFreke said:
Did you try my first tip to enable adb?
Click to expand...
Click to collapse
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
cmavr8 said:
What do you mean enable?
I should enable it on the g1 but it's locked, no menus available.
I thought the first step was to enter the "adb shell" command in the PC, then pass this through the pc to the G1:
"sqlite3 /data/data/com.android.providers.settings/settings.db INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
Am I missing something?
Click to expand...
Click to collapse
A couple of things:
- Look further down the post, there's a "tips and tricks" section. The first tip is how to enable adb.
- second, I don't think you need to go through the first step (the sqlite3 command). The first step is to get past the "no sim card" screen. You said you have a sim card, just no data plan, right? So you don't need to get past the "no sim card" screen . You can skip to the second step (once you get adb working, of course)
DID IT!
Thanks so much!!
I now have to wait for the unlock code so that I can also use my sim card...
Thanks both of you!
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Great! Glad you got it working
cmavr8 said:
EDIT:
T-mobile sent me the unlock code although I was not a customer for even one day!
That's great...
Click to expand...
Click to collapse
how?
thanks
xaxis said:
how?
thanks
Click to expand...
Click to collapse
Probably by getting lucky and getting a nice CSR
JesusFreke said:
Probably by getting lucky and getting a nice CSR
Click to expand...
Click to collapse
man thank god you are here,
do i need the SDK installed to get the adb?
thank you
Yes, adb is included in the sdk
Ok, i'm a newbie, just got a new G1, switching from a wizard. I have the tmobile prepaid plan so I cannot register when I start up the phone. I have seen the sticky - http://forum.xda-developers.com/showthread.php?t=452316. The post says if you have the official rc30 then the process doesn't work. I started up the phone, on the keyboard hit enter, typed reboot and hit enter again but nothing happens so I'm assuming I have rc30.
Does that mean there is nothing I can do? Can I roll back to rc29 via the sd card - http://android-dls.com/wiki/index.php?title=Root_For_RC30? I'm at work so I can't really do much now but I want to know what, if anything, i can do to get the phone registered. Any help is much appreciated, thx.
Download the SDK
Unzip the SDK
download the windows Drivers
unzip the windows drivers
plug in phone.. install drivers using windows drivers
open comand prompt and navigate to sdk tools dir
adb shell
paste in shell "
am start -a android.intent.action.MAIN -n com.android.settings/.Settings"
establish wifi connection
proceed to register your device...
????
profit
edit: now with links!
u r profit
but in all seriousness, thanks for this. i'm going to do this to my G1 as soon as i get home!
Thanks for the response, my problem is when i plug in the phone it doesn't prompt me to install drivers. It does give me an e drive thats listed as removeable storage but i can't access it or format it.
When i hook up the phone to my pc, i get an e drive, removable disk but when i try to access it i get "please insert a disk into drive e". It doesn't matter if i have the sd card in the phone or not. I never get prompted for drivers. If i try to <enter>setprop persist.service.adb.enable 1<enter> i get put into the emergency phone dialer.
Thanks for the help. I followed the directions here to downgrade to rc29, then i did <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter> from JesusFreke's sticky, then i was able to connect the phone and get prompted to install the drivers now, then I followed kash04's steps and was able to connect with no problem, took all of about 3 minutes, thanks for the help to everybody on these forums, you guys are great.
Ok so I downgraded from rc30 to rc29, downloaded the necessary recovery.img, and jfv.1.42_rc33. I got root using telnet after typing enter "telnetd" enter. I also downloaded busybox from my phones browser.But now why do I get " cannot access files from directory/no such directory" message when I enter in "dd if=/sdcard/download/busybox.asc of=/system/bin/busybox"?
I'm suppose to enter this into telnet correct? Or is it through my computers command line?
Am I suppose to have the usb mounted or unplugged when I type this in?
Can someone please walk me thru the android wiki for rooting and keeping root from: android-dls.com/wiki/index.php?title=keeping_root
ps: if i.m. is easier let me know. please help!
you don't need to install busybox if you don't want to(it comes installed for later use in the jf builds you are going to install later). You can just download a terminal program and run the commands that contain the flash_image for the recovery.img. Then once that is done you will have moved the recovery.img to the /system folder and then you have the jf file renamed to update.zip on your fat32 formatted sd card. Once you do that you will then reboot holding home and power. A screen should come up prompting you to hit alt+s to update your system. WAIT for it to finish before you press home and back key to exit.
I think that's it... I suggest rereading the wiki a few times to get familiar but also reading the sticky posts that have this same info as they have the same steps and make it just as easy as the wiki.
Easier Tutorial
There is a real easy tutorial over at our site AllShadow.com that explains everything step by step. No need to run the telnet anything. Just go here: http://www.allshadow.com/forum/viewtopic.php?f=9&t=5052 Those are the steps I followed to get root and Ive done it several times with no problem
I am sad to say the time has come to retire this post....Now before you get all panicky and ****, just sit your **** down, take your adderall and relax, damn antsy ass people. Anywho, with people our there like xHausx and others that have automated all of this there really isnt a need for me to keep this updated. I will keep the post here for archival purposes but, I will not be updating it, any further. I may pop into the thread here and there but probably not. I would like to thank all those that helped and supported me during this threads run. With out you we would still be stuck.
In the mean time if your looking to root your phone, check out xHausx's thread
here: http://forum.xda-developers.com/showthread.php?t=838448
And no I still dont recommend Clockwork or Unrevoked.
Till next time...Super Tramp - Goodbye Stranger
Archive of the guide as of 2/14/11
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
======================================================
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
Click to expand...
Click to collapse
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
Click to expand...
Click to collapse
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
Click to expand...
Click to collapse
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
Click to expand...
Click to collapse
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
Click to expand...
Click to collapse
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
Click to expand...
Click to collapse
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
Click to expand...
Click to collapse
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
Click to expand...
Click to collapse
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
================================================
UNROOT GUIDE
NOTE: This will erase all data on the phone. (Will not erase data on the SDCard)
1) If your on Hboot 2.10 Download the PC36IMG.zip Here. If your on Hboot 2.02 Download the PC36IMG.zip here then Unrevoked s-on here rename the pc36img file to pc36img.zip copy that and the unrevoked s-on tool to the root of your sd
2) Power your off. Power the Phone back on into the boot loader by holding power and vol-down until your presented with a white screen.
3) It will scan for the pc36img.zip. Select no to flash. Select recovery from the menu. Once in recovery choose flash zip from the menu, and select unrevoked forever s-on.
4) When its done flashing select reboot from the menu.
5) From here either run the official ruu or boot back into the boot loader (see step 2). When it scans and ask you to flash the pc36img.zip select yes then yes to reboot.
Click to expand...
Click to collapse
FAQ
FAQ:
Your here cause something went wrong right? Ok thats fine. This list isnt extensive but its here to provide quick answers to some weird or common questions. New questions and problems are added to the bottom.
Q: Will this downgrade my hboot
A: No. I used to have an hboot downgrade but it was bricking peoples phones. However is you want to risk bricking your device, visit this thread here. I I advise against this. This bricked alot of phones which is why I pulled it.
Q: How do I install the Hboot Drivers
A: Check this here
Q: I get "error: more than one device and emulator"
A: kill the adb.exe tasks in task manager or reboot your computer
Q: Step #9 my phone does read the PC36IMg.zip
A: If you renamed the zip file make sure it doesn't say PC36IMG.zip in the name remember that xp and up on windows doesn't show the file ext by default so if you see PC36IMG.zip chances are its named PC36IMG.zip.zip
Q: Why cant I use Clockwork Recovery
A: At the moment its not coded for the new partitions. Just read the first few pages of this thread or check this here
Q: What Hardware does this work for
A: All currently known hardware 0001-0004
Q: What Hboot's does this work for
A: It was built for 2.02 and 2.10 however it will work for all version its just there are easier ways for those
Q: I think I messed up can I just start over.
A: Yes. Its recommended if you want to start over run the official ruu.
Q: This is very complicated
A: It is...thats why there is instructions
Q: Will this erase my data
A: Yes but not from the SDCARD
Q: Can I deleted the files off my SDCARD when done
A: Yes, except for RSA_OEM.KEY and WIMAX.IMG
Q: I get permission denied or device offline when trying to step 10
A: Check here or here or here this might work for you
Q: I used clockwork it seems to work fine.
A: It might but considering the partition information is not correct. You may have just over wrote your wimax keys and broke 4G. Have fun with that like this poor guy here
Q: This uses unrevoked in one of its steps? Explain?
A: There have been some concerns that this uses unrevoked-forever in one of its steps. As far as we know that Unrevoked 3 (not to be conufused with unrevoked-forever) is causing some radio issues with hardware in general and new hardware. Unrevoked-forever does not appear to bork the radio like unrevoked 3 does. This is apparent by the many success stories. However Unrevoked3 could very well possibly destroy your radio/wimax/brick if used.
Q: I get device not found
A: Install the drivers for your phone, (Unrevoked, ADB)
Q: Camera doesnt work after doing this
A: Flash a new rom thats current. Like SteelRom, Fresh, Stock Rooted. The issue here is the Hardware is different. NO CUSTOM KERNELS
A2: Reports say they changed the camera provider/hardware. And the drivers are different! Using a rom based off the latest release and kernel should fix it As Discussed here and here and here
Q: When I go to recovery. I get a red triangle.
A: See Step 10
Q: This doesnt work!
A: Yes it does if you follow the directions, Unless some other bull**** decided to popup!
Q: CM6.x doesnt work
A: See Question 7....Nothing I can do about that if the kernel doesnt support your camera/device.
Q: My phone boot loops now...You broke my ****!
A: I didnt break your ****. You broke your own ****! Its not broken so chill out (well it might be but probably not). What rom did you flash? Did you flash a custom kernel? Did your rom come with a custom kernel? I bet your using a custom kernel. Try a rom like Steel Rom, Sprint Lovers
Q: How do I back up my RSA Keys
A: Check here for the latest up to date information. Or run this command from the shell
cat /dev/mtd/mtd0 > /sdcard/wimax.img
Click to expand...
Click to collapse
Q: My 4g Doesnt work
A: Was it broken prior to the s-off, what steps did you take. Are you running AOSP ROM or Another kernel?, Did you try a different rom? What version is your phone? Do you have SwitchPro Widget installed? (uninstall it), Did you try to run unrevoked3 prior to this? After flashing the radios and stock kernel based rom did you do a data and prl update? Does the mac behind your battery match whats in about phone (4g has to be on to see mac) Also try the tree.xml fix posted
adb shell
ls /data/misc/wimax/
look for a file with your macaddress ending in .tree.xml. you want to move that to another location so it gets regenerated. (the following command basically renames it.)
mv /data/misc/wimax/(Your-mac-address).tree.xml /data/misc/wimax/(Your-mac-address).tree.xml.old
4. Start 4G may not connect
5. Do a prl/profile update
6. Power off the phone and power it back on. Try it
7. PRL/Profile. Try it
Click to expand...
Click to collapse
Q: 4G is still broke.
A: Check your RSA keys
adb shell
cat /dev/mtd/mtd0 | grep RSA
returned output show appear as this:
# cat /dev/mtd/mtd0 | busybox grep RSA
cat mtd0 | busybox grep RSA
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA-REQUEST
RSA-REPLY
RSA-REJECT
RSA-ACK
RSA-1024
RSA
ReRSA
RSA requests
RSA replies
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
#
It should look just like the above
the important lines are BEGIN RSA PRIVATE KEY and END RSA PRIVATE KEY.
If you have those two lines, your keys are still likely to be intact.
If those two lines are missing, your keys are likely missing.
/dev/mtd/mtd0 is where the wimax image is stored.
Click to expand...
Click to collapse
Q: OK I think My Keys are tossed. We made a backup right? So how do I restore it?
A: This post or post should do it for you
Q: My Phone says its not rooted.
A: If you have s-off your rooted. Simple as that. Try a different rom if you want. The second pc36img.zip file you flashed is Sprint Lovers and is a very nice rooted rom.
Q: When I try to get into Fastboot by pressing VOLUME UP and booting the phone, my phone instead buzzes three times and acts dead. What happened?
A: The S-OFF update also enables Qualcomm Diagnostics mode on your phone, which is entered by doing what you just did. You can exit this mode (and boot normally) by removing the battery and USB cable.
Q: Can you tell me what this does?
A: Read the guide? Basically your downgrading the phone, so you can flash unrevoked because htc "comically fixed" the phone. Then your re upgrading the phone back to shipping radios, system, pri, nv, kernel...all the while with keeping s-off
Q: How did you get to be so cool
A: If you have it, you don’t need it. If you need it, you don’t have it. If you have it, you need more of it. If you have more of it, you don’t need less of it. You need it to get it. And you certainly need it to get more of it. But if you already don’t have any of it to begin with, you can’t get any of it to get started. Which means you really have no idea how to get it in the first place, do you? You can share it, sure. You can even stockpile it if you like. But you can’t fake it. Wanting it, needing it, wishing for it. The point is, if you’ve never had any of it, ever, people just seem to know.
Q: Do you really own a vette?
A: Yes, and a backpack with jets!
Q: Whats with you and the dots ...
A: ...
Q: Your Kind of an Cocky Asshole
A: Yea...I Get that. Oh well. I cant fix stupid or ignorant.
What is the point of getting the new HBoot?
sorry, wrong question
abiezer said:
What is the point of getting the new HBoot?
Click to expand...
Click to collapse
there is no point in getting a new hboot....this tool is for those that have phones with the new hboot....that unrevoked wont work on.
this is not the new hboot
Oh I see so this is basically for people who couldn't root to be able to root. Got it. Thanks.
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
shepkc said:
Dumb question, sorry trying to keep up with this while at work. Once I do this, then I still need to run Unrevoked, correct?
Click to expand...
Click to collapse
its included in the script it tells you how to do it.
update failed, said main version is older...
its working for some but not others...i dont know why the main version is older thing...
i think we have ironed out the mainversion deal...
looking into it now.
Should be fixed now...so try it I guess.
v2
Looks like your V2 is working, I didn't run into the main version failure. Flashing as I type, I hope slyder got this to work.
Confirmed, V2 works
alright brotha your v2 of the batch file works like a charm. S-OFF confirmed on HBOOT 2.02. Thanks to everyone involved in making this happen.
Outstanding
Sent from my PC36100 using XDA App
On a brand new fresh 2.2 out of the box running HBOOT 2.02 I got "Main version is older". Are there any prerequisites i have to run to get this to work? I just reinstalled 2.2 and ran the script and got main version is older.
did you download version 2
do you have gtalk
I did download v2, and I do have gtalk.
b0r0b said:
I did download v2, and I do have gtalk.
Click to expand...
Click to collapse
you got PM....i want to know exactly whats happening.
Main version is older
I have also tried with V2 and get the "Main version is older".
Baseband
2.15.00.09.01
Software
3.30.651.2
PRL
60671
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.