Database Develop

Question about installing latest recovery

Hey guys. Right now my Hero has the old recovery image flashed to it. It's also running Fresh ROM 1.0. Now I'm going to flash the latest recovery image right now using the first method in the thread for the recovery image. So I typed "adb shell" and it brought me into the shell. Then I typed "mount -a", and I just got errors, such as "No such file or directory" or "No such device". And I'm entering those commands while I'm in the recovery on my phone. Can anyone tell me what I'm doing wrong? I also put the recovery image on my sdcard by dragging it from windows into it... I don't think ADB really has to be used to push it. But yeah can anyone help me out here? I don't want to proceed any further if I'm getting errors... my parents would be mad if I bricked my phone haha.
-Mike

mrinehart93 said:
Hey guys. Right now my Hero has the old recovery image flashed to it. It's also running Fresh ROM 1.0. Now I'm going to flash the latest recovery image right now using the first method in the thread for the recovery image. So I typed "adb shell" and it brought me into the shell. Then I typed "mount -a", and I just got errors, such as "No such file or directory" or "No such device". And I'm entering those commands while I'm in the recovery on my phone. Can anyone tell me what I'm doing wrong? I also put the recovery image on my sdcard by dragging it from windows into it... I don't think ADB really has to be used to push it. But yeah can anyone help me out here? I don't want to proceed any further if I'm getting errors... my parents would be mad if I bricked my phone haha.
-Mike
Click to expand...
Click to collapse
I did this using flashrec, I dont know how you rooted your phone, here is the link
http://zenthought.org/content/project/flashrec
install it and run it, you have to backup your current image then install the new one, pretty simple, did it on both of my hero's.

You can also use my auto-rooter (check my sig) to update you from 1.2.3 to 1.5.2. Just make sure that "i have a with google phone" is unchecked.

Haha I think I will use your method, flipz. Thanks!

G1 not starting up

So I tried rooting my girlfriend's G1 and it didn't workout so well, so now I'm trying to fix it for her (I feel terrible, my poor android friend.. I mean my poor girlfriend!) . I rooted it and it was working find, but I wanted to flash a ROM on there. I tried flashing CM5 following the directions on the wiki. I made sure I installed Amon_Ra's recovery and did a nandroid backup. Then I flashed the DangerSPL. 2 things then happened, when I tried starting up the phone it would just hang on the "G1" startup screen until I pulled the battery, and when I went back into recover it switched back to the old recovery I had after root (JFv1.42). So I can't go back. But when I go into Fastboot, the HBOOT is at 1.33-2005, which indicated the DangerSPL was flashed correctly. So should I flash CM5( or 6 or 7) now? I just don't wanna get the phone to a point where it's unusable (unless it is already) =/ Can you guys help me out?

If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.

Your girlfriend G1 still fine.
The CM5 that you have flashed is not compatible with the SPL(HBOOT)/radio combination. (to my understanding) That is why it gets stuck at G1 screen (that had happens to me).
For G1, you can only flash up to CM 6.1 (to my knowledge), Cyanogenmod 7 will not (according to the DEV) works on G1.
You can try other ROM, recommending ezGengerbread, or Gingerbread Yoshi, and also my favorite (I am currently using it.) SuperAosp DM 2.8.2.
You will need to use 2708 SP and 13d radio for the newer ROM.
First load the radio, then the SPL. After both have been flashed (you can check it in the fastboot mode) then flash the ROM that you want.

AndDiSa said:
If you can go to hboot, everything should be fine. Check again, that you have a 2.x or 3.x radio installed (should be the case, because otherwise I doubt you would be able to go to hboot).
If this is the case, you can flash what you want. Probably I would flash Amon-RA recovery first
Code:
fastboot flash recovery <amon-ra.img>
To be sure, that you have a clean phone, I would do an
Code:
fastboot erase system -w
Then you can boot into recovery and flash the ROM you like.
Click to expand...
Click to collapse
Where do I put in these commands?

Vulf said:
Where do I put in these commands?
Click to expand...
Click to collapse
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.

BeenAndroidized said:
You have to connect the G1 to the PC and run ADB. Then flash it using the command line indicated.
Click to expand...
Click to collapse
No, it's not adb, it's fastboot, a different program, but you are right, it's a program that runs on your PC. You have to make sure to have fastboot installed. Then open a command window and enter the commands above having your G1 connected to your PC and beeing in fastboot mode (boot with back + power).

@ AndDiSa - Sorry for the short explaination, I should have explain in more detail.

Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now

Vulf said:
Alright. I'm on Ubuntu so I'll let you know how it goes. I'm gonna install SDK/ADB/Fastboot now
Click to expand...
Click to collapse
Have fun.

So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..

Vulf said:
So a problem with flashing amon ra's recovery. My fastboot (or adb) aren't recognizing my G1, but they recognize my EVO, which is strange since they're both HTC..
Click to expand...
Click to collapse
Hmm, someone post an instruction in one of the forum that I saw yesterday. Not sure which one. It would fix the problem you are having with not see your G1 on ubuntu..

You can solved your problem with unroot like me.even my g1 lost function home & call button.
Sent from my T-Mobile G1 using XDA App

[Q] Milestone flashing recovery issue

Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.

tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.

I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks

tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.

Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.

Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?

tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!

Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.

[Q] Nexus One stuck on reboot screen

My Nexus One is stuck on boot screen and keeps recycling/vibrating. To condense information, here are bullet points of the situation:
-Nexus One 2.3.6 with unlocked bootloader
- PASSIMG.IMG is wrong or missing in HBOOT
-Can't access the sd root because I lost my sd adapter
-I've tried to fastboot recovery-RA-v2.2.1.img and Clockorange but I think that because I don't have the SU files in a folder titled SU on my sd, it doesn't go into the recovery menu
-When I cmd fastboot devices the serial comes up, but when I cmd adb devices, nothing comes up
-Can't access sd storage to move the SU folder via cmd
I've been working on this the past two days and searching and trying anything and everything. And nothing has worked. Any help would be great.

You don't need anything on your sdcard (or your sdcard itself for that matter) to put a custom recovery on your phone. Try this after putting your phone into fastboot mode and getting your cmd prompt up on the computer:
Code:
fastboot flash recovery "c:\location\to\recovery.img"
fastboot boot recovery "c:\location\to\recovery.img"
From here, try a factory reset.
And adb won't be able to see your phone until you are either in recovery or fully booted up in Android (only with USB Debugging enabled).

When I do "fastboot boot recovery recovery-RA-v2.2.1.img" it comes up cannot load recovery.
Any ideas?
And once that goes through, do I boot through recovery on the phone or through command prompt?
Thank you for the reply.

Is the recovery in the folder where you are typing the command? And have you verified that the md5 sum of the recovery is correct?
And, I always just change the command from flash to boot to boot into the recovery the first time. Otherwise, if you are running a stock Android version, your recovery might get restored back to the stock recovery (Android has checks in place for that).

Nevermind, I did get it to go through, but then my N1 reboots on its own and is still stuck at the bootscreen

Ok, do you want to continue running stock, or would you like to try a custom ROM? Because, it sounds like you will need to reload your ROM (assuming the Factory Reset/Data Wipe didn't work). They have a couple of rooted extremely close to stock versions on here, or you might want to give CM7 or MIUI a shot. I would also go and get temasek's system-only format since Amon_RA doesn't give you the option to format your /system partition. You can find the file in his mediafire folder http://mediafire.com/temasek

My original intentions were to put CM7 on my phone because Gingerbread began to crash a lot. So in that case, how am I supposed to install the CM7 ROM onto my phone if I can't get past the bootscreen?

So, the fastboot boot command doesn't work?

fastboot does work, adb doesn't

No, does the
Code:
fastboot boot recovery "c:\location\to\recovery.img"
get you into recovery? Or does it still freeze on the X screen (when you say bootscreen, I assume you mean the X)?

Sounds like the recovery isn't installing with fastboot? Do you get any error messages?

It will still freeze at the X and never boots into recovery.

seb0 said:
It will still freeze at the X and never boots into recovery.
Click to expand...
Click to collapse
I got exactly the same problem as you. Didn't you see my post?
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
I got an idea, but not sure about it:
Get someone who has a working Nexus One to make an nandroid backup, and send the boot.img and system.img and fastboot it into our devices?

mrBira said:
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
Click to expand...
Click to collapse
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?

bassmadrigal said:
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
Click to expand...
Click to collapse
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"

mrBira said:
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
Click to expand...
Click to collapse
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?

bassmadrigal said:
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
Click to expand...
Click to collapse
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.

I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.

mrBira said:
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
Click to expand...
Click to collapse
Have you tried any additional recoveries? It has been awhile since I used that command, but I know it has worked in the past.
seb0 said:
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
Click to expand...
Click to collapse
You won't have adb access unless you are in recovery or booted into Android with USB Debugging enabled.
Where did you get the system.img and boot.img files from?

http://forum.xda-developers.com/showthread.php?t=1061648
This was the only system.img and boot.img file I could find.

Doesn't go into recovery

I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?

It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618

I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.

Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta

Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.

samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.

Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123

Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?

The stock recovery says it's not available anymore.

If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.

I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.

This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?

aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?

tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.

Would ADB be any better?

Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.

I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol

aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again

tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.

There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.