Database Develop

Unable to get root access...

Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves

yvesg said:
Hi,
I have a T-Mobile G1.
It was in Android 1.5 when I received it.
I rooted it woth the "one click" method (flashrec 1.1.2) using recovery-RA-dream-v1.2.2.img.
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The one click method doesn't work anymore. I get "Could not run command".
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Anyone has an idea ?
Thanks,
Yves
Click to expand...
Click to collapse
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !

yvesg said:
It worked fine, and I was able to test some ROMS.
But the last one I installed, Android 1.6 User debug from HTC, doesn't allow to get root access again.
The Fastboot method doens't work anymore too.
I'm stuck with the 1.6 "Android dev phone 1".
Click to expand...
Click to collapse
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.

lucky 69 said:
if i remember right the 1 click root only works with 1.5 and wont work with 1.6 . if you made a nandroid back up before you flash the 1.6 i think you can restore from there to get root .read threw the thread on 1.6 i think there was some mention of this !
Click to expand...
Click to collapse
I ashamed, but I didn't do the backup :-( .....

yvesg said:
I ashamed, but I didn't do the backup :-( .....
Click to expand...
Click to collapse
Try what Harry wrote.

harry_m said:
I think you have still root. Do you have adb installed?
Try this one:
Code:
adb root
adb shell
Now you should get the root-prompt ("#").
The reason why you can't flash any other rom anymore is because the recovery-img operates with wrong keys (that's what I think).
What you could do now is to reflash the recovery by using the flash_image command (you have to copy the flash-image-binary on your phone first - extract it from any other rom - it's located in /system/bin).
So, copy the flash_image binary to your phone:
Code:
adb remount
adb push flash_image /system/bin/.
adb shell chmod 0755 /system/bin/flash_image
Now copy the recovery-image you want on your phone:
Code:
adb push recovery.img /sdcard/.
Flash the recovery:
Code:
adb root
adb shell flash_image recovery /sdcard/recovery.img
Now ... boot into recovery-mode ([power]+[home]) and reflash your phone with whatever you like. Since fastboot doesn't work for you I guess you have never replaced the original SPL.
And ... what I've heard ... the ADP1.6-firmware will check the recovery on boot and will reflash it every time!
You could also check this site.
Click to expand...
Click to collapse
Hi,
Thanks a lot.
I'm now able to get root access and I'm about to flash the G1.
I thaught I replaced the SPL, but I'm not sure .... I've tried so much things since I have this phone (since last sunday) .....
Again, thank you for your help.
Yves

ooops,
"Installation aborted", during the apply of update.zip.
Now the phone is bricked.
I'm going to format my sdcard and retry the flash ....
Same error :
(No such file or directory)
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
Installation aborted.

redownload the rom

Spon4ik said:
redownload the rom
Click to expand...
Click to collapse
Meanwhile, I try with another rom and it seems to work ....
Thanks again for your help.

In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way

If you ask me ... the above mentioned error
Code:
E:Failure at line 80:
set_perm_recursive 0 2000 0755 06755 SYSTEM:xbin
has nothing to do with a wrong-signed rom!

SPL
yvesg said:
In fact, I can only flash with HTC SIGNED roms .....
I tried several others and each crash the same way
Click to expand...
Click to collapse
would this have to do with the SPL? similar to not being able to flash a EUR ROM on a USA phone .. you have to flash the HardSPL etc in order to switch ROMs

Or you could just gain root access manually the way those of us who had RC30 did...

You are may be right about the HardSPL.
When I try to flash it, (with Camera + Power), I get "not allow".

Help with flashing [Recovery] CDMA Sprint [07-Mar-2010] RA-heroc-v1.6.2

After getting into adb shell and following the commands it says:
"Cannot find recover partition"
What do I need to do?
thanks

Danokan said:
After getting into adb shell and following the commands it says:
"Cannot find recover partition"
What do I need to do?
thanks
Click to expand...
Click to collapse
boot your phone into recovery first, then type in the adb commands

Show me the command you typed.
Danokan said:
After getting into adb shell and following the commands it says:
"Cannot find recover partition"
What do I need to do?
thanks
Click to expand...
Click to collapse

Danokan said:
What do I need to do?
Click to expand...
Click to collapse
Download the fresh kitchen and use it...
I originally rooted with the command line but corrupted my recovery image upgrading to RA1.6.2 via adb.
The fresh kitchen was the only way out of 4 i tried that was able write a new recovery image.

I am using Fresh 2.0d
Booted into RA
Hit the MS/DOS usb command
then did the commands straight from the amon_RA recovery single post thread, i.e.:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img

make sure you dont have any spelling errors...
flash_image recovery /sdcard/whatever_your_image_name_is.img

sladehawke said:
Download the fresh kitchen and use it...
I originally rooted with the command line but corrupted my recovery image upgrading to RA1.6.2 via adb.
The fresh kitchen was the only way out of 4 i tried that was able write a new recovery image.
Click to expand...
Click to collapse
I thought kitchen (even newest version) wouldn't work with Fresh 2.0d because it is based on 2.1 sprint.

Bump for some help.

Danokan said:
Bump for some help.
Click to expand...
Click to collapse
Try and download the pre-kitchen here
It still works for non-sprint phones.

I have a Sprint Hero thus the reason for posting on this particular forum.

How to flash stock recovery.

Hi guys,
I have to send me N1 to htc for fix some problem.
I have RA recovery with lock bootloader, and I want to flash the original, but "fastboot" way doesen't work (signature fail ).
How can i flash it in other way?
Ty
(sry for my eng )

Just flash the stock rom with the recovery image like frf92 original.

evilkorn said:
Just flash the stock rom with the recovery image like frf92 original.
Click to expand...
Click to collapse
How? Through recovery? Because "fastboot" hates me, and won't work.

I'd suggest using a passimg for frf85b and then maybe updating to 91 (or just leave it at 85), you can always re-root when you get it back.
________________________
N1 w/ XDA App

got it, thk to cyanogen wiki
Plug the phone into the computer
Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
Code:
adb devices
​A device name and 'recovery' should be returned
Code:
adb push recovery.img /sdcard/recovery.img
​recovery.img is located on android-sdk/tools dir
Code:
adb shell flash_image recovery /sdcard/recovery.img
​This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
Reboot

nrdmtt said:
got it, thk to cyanogen wiki
Click to expand...
Click to collapse
Thanks for searching!
I hope this encourages other users new to ADB, flashing ROMs, etc. to continue to search after asking for help.
Way to go nrdmtt!!

[Q] Stuck at Fastboot usb screen

I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?

If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?

How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.

I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.

ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s

1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.

unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.

casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.

ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.

casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.

ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.

I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.

ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks

Did you fix this yet?

Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!

Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!

[Recovery] ClockworkMod 5.0.2.0 Official

I just noticed it now, grab it here:
S-OFF
recovery-clockwork-5.0.2.0-buzz.img
S-ON / fake-flash
recovery-clockwork-5.0.2.0-buzz.zip
Haven't tested it, try it at your own risk but should be safe
S-OFF: flash with fastboot with
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
S-ON: simply rename to update.zip and put it on your SD card

Eh!!! Confused!!!!! cwm 5.0.2.0 been around for ages????
"sent from me2u"

I just didn't see it posted lol, did a search and didn't see the official 5.0.2.0, only older and customized versions

Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!

Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium

So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )

Qarl said:
Can anyone help me install it?
I've installed v4.0.1.4, but I can't install it
I want install from Ubuntu please...
Regards!!
Click to expand...
Click to collapse
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
nogoodusername said:
Cwm can be flashed when s-on?
I don't have wildfire... my friend has...
If it works ill flash it from his s on hboot...
Edit: his hboot is 1.01.0002
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
With S-ON, you can only use the fake flash by renaming the .zip to update.zip and "flash" it from the stock recovery to launch CWM...
nejc121 said:
So...what's new in this version?
(Also, is there a way to change the color of text in the recoveries, I want the orange color back )
Click to expand...
Click to collapse
No idea

Kwen said:
Assuming you have S-OFF, install the Android SDK and just boot into the bootloader, then select fastboot and use the command in the first post...
Click to expand...
Click to collapse
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English

See http://developer.android.com/guide/developing/device.html
"If you're developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux:"

Qarl said:
Yes, I've S-OFF.
Turn ON my device on Fastboot, it's connected to computer obviously!
If I run:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
The console says that "fastboot" isn't a valid command.
If I am in Android SDK directory and run:
Code:
./adb devices
The console don't found any device.
Where is the problem?? Is this usable on Ubuntu? I'm use it.
Regards and sorry my bad English
Click to expand...
Click to collapse
This word in'valid
Change Legend to buzz
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
Click to expand...
Click to collapse

If you're on Windows, have you that in the recovery installation folder?:
AdbWinApi.dll, adb.exe, fastboot.exe and recovery-X.img

Good call, copy paste error
Also if you don't have the fastboot command, you'll need to download the "Android SDK Platform Tools" (under "Tools") from the SDK manager (how did you get adb working though without the platform tools?!)
Should be under the same directory...

Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"

First, I go to "android-sdk/platform-tools" with the terminal.
Then, run this command:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-buzz.img
And the terminal return this:
Code:
< waiting for device >
What's happen? If I run "adb devices", my HTC Wildfire is founded.
Regards!

Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that

Kwen said:
Did you highlight fastboot in the bootloader/hboot and pressed power to select it?
It should say fastboot usb plug or something like that
Click to expand...
Click to collapse
Problem solved!!!
I believed that the device reboots to fastboot when the command executed it.
Sorry ¬¬
Thank you very much!

slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
I think you'll need a flashable zip, the one koush provides is just a img and a fake flash .zip

@Kwen, yes copy/past error xD

how can i call the yes/no event in this recovery with an updater-script?
other phones have recovery that have a list of comand,that you can add to an updater-script to call some recovery functions.
also this?

slymobi said:
Just rename the zip to pc49img.zip making sure you DONT name it pc49img.zip.zip place it on the root of your sdcard (ie.not in any folders) boot your phone into hboot via volume down and power whilst phone is off and when prompted press volume up to update then reboot into recovery to see your new cwm. SIMPLES.
"sent from me2u"
Click to expand...
Click to collapse
How do I do this if the OS itself is crashed and I get a white screen and HTC logo???