Alright I have a semi-bricked mytouch 4G. (a friend's phone) I followed the gfree guide and did the hboot flash and now I'm in a boot loop. I have the original boot screen loaded and I can get to the recovery menu. S is off so the phone is rooted. How do I get CWM on the phone so I can install a new ROM and kernel so I can unbrick this thing. With my verizon fascinate I have options to go from where I am stuck (Odin and .md5 files). Where do I go from here? Can somone give me a step by step without pointing me to a different forum? I have searched for more than a couple of hours and this is where I have found myself.
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
darinmc said:
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
Click to expand...
Click to collapse
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
fsuagentsmith said:
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
Click to expand...
Click to collapse
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
I get sending recovery failed... any help from there?
fsuagentsmith said:
I get sending recovery failed... any help from there?
Click to expand...
Click to collapse
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
neidlinger said:
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
Click to expand...
Click to collapse
yes, I see that
fsuagentsmith said:
yes, I see that
Click to expand...
Click to collapse
ok I changed it to that screen on the phone while trying to push the recovery image. It worked!!!
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
neidlinger said:
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Where is the reboot recovery option? As I said in original post I'm familiar with Samsung Galaxy and CWM not so much this phone.
fsuagentsmith said:
Where is the reboot recovery option?
Click to expand...
Click to collapse
are you in Recovery or in Hboot? what color is the screen? black or white?
neidlinger said:
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
Click to expand...
Click to collapse
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
neidlinger said:
are you in Recovery or in Hboot? what color is the screen? black or white?
Click to expand...
Click to collapse
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
fsuagentsmith said:
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
Click to expand...
Click to collapse
Awesome!!! I see what you told me to do! When I select recovery this is CWM 3! Awesome. I will see where I can go from here. I still may have questions.
fsuagentsmith said:
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
Click to expand...
Click to collapse
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
neidlinger said:
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
Click to expand...
Click to collapse
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
fsuagentsmith said:
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
Click to expand...
Click to collapse
glad to see you got it going.
just make sure to do nandroid backups prior to flashing any new Kernels and make sure they are compatible with AOSP 2.3 ROMs.
neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
steb0ne said:
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
Click to expand...
Click to collapse
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Well, I was rooted and had been running the leaked 2.3 stock rom. Decided I wanted to try CM7...and flashed it and it appeared to flash okay b/c I was able to boot up, but I couldn't get gapps to install, so I ended up trying to restore from my backup, and that failed, and I couldn't get back to CM recovery. So, I'm stuck in a constant boot loop.
Related
Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is
lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)
pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.
behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)
hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?
breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho
I am hanging at booting while trying to do this any ideas?
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
truss said:
Hi,
I have a mt3g, TMobile. CyanogenMod 6.1.0, ClockWork recovery. Used ROM Managed to flash Amon Ra recovery, since I needed to re-calibrate the battery. It asked me to pick phone model, picked Ion/MyTouch 3G. After reboot:
- Stuck on splash screen if I try to go to recovery
- When booted up - a bunch of force closures, keeps playing a ringtone over and over and...
Everything I tried to do through ROM Manager didn't help.
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Do you still have root? If you can get into ROM manager, reflash clockwork recovery, then wipe cache, dalvik, and run a fix permissions. That should get you back up and running long enough to try again to flash amon ra.
Not sure if the oem spl will let you fastboot flash a new recovery but that's your most reliable bet.
It sounds like it might be time to do a full wipe and reflash anyway. Have you heard of Ohsaka's SuperWipe?
I tried reflashing Clockwork through ROM Manager. It says "root granted", "clockwork flashed" immediately. When I try to boot into recovery - I get stuck on green MyTouch screen forever. Battery pull is the only way out.
I guess the problem is that I cannot get to any recovery anymore. Any ideas?
Do you have fastboot. If so you can flash recovery from there.
kodjo said:
Do you have fastboot. If so you can flash recovery from there.
Click to expand...
Click to collapse
Can I do that through adb shell? I don't think I built fastboot.
truss said:
Can I do that through adb shell? I don't think I built fastboot.
Click to expand...
Click to collapse
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B. http://www.filefactory.com/file/caa48b0/n/recovery-RA-sapphire-v1.7.0G-cyan.img
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Phateless said:
Fastboot is a different mode. Boot into hboot (vol down + power I think) and then select fasboot from the menu. Then plug into computer. From a command prompt type:
fastboot flash recovery recovery.img
The recovery needs to be in your tools or platform-tools folder and named recovery.img for this to work. Otherwise it would be fastboot flash recovery c:\path\to\recoveryfilename.img. Make sense?
Link to Amon_Ra Recovery 1.7 for MT3G 32B.
Otherwise keep trying with ROM Manager. Might take a few attempts to get recovery to stick, even temporarily. It did for me. Flash once then flash again. There's also an option in ROM Manager settings to erase recovery prior to flashing. Check that and see if it helps.
Click to expand...
Click to collapse
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
truss said:
I appreciate your help.
When I try to flash recovery.img, I get this: error: cannot load `recovery.img`
When I try running fastboot with absolute path, I get: FAILED (remote: not allow). Is there a way to fix this?
Tried flashing through ROM Manager many times - no result.
Click to expand...
Click to collapse
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Phateless said:
Interesting... Where are you trying to flash recovery.img and getting that error? What method are you using? Are you sure you have the path to recovery.img correct?
As for fastboot, you need an S-OFF/engineering spl so I guess that's out.
What happens if you use Terminal Emulator?
su
flash_image recovery sdcard/recovery.img
Does that work? Keep at it, you have root so not all is lost. Eventually you will get there.
EDIT - make sure you rename the recovery to "recovery.img" and leave it on the root of your sdcard for my italicized instructions above to work. What ROM are you running? If flash_image doesn't work I need to know which version of the binary to give you.
Click to expand...
Click to collapse
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
truss said:
Thank you very much.
Running flash_image recovery command using adb shell a few times did the trick. I was able to boot to Amon RA recovery, wipe and flash CyanogenMod 6.1.0.
Click to expand...
Click to collapse
Nice! Glad you got it sorted out.
i just got another nexus s that had the old 2.3.2 stock rom i unlocked bootloader then tried to use paul obreins superboot to root phone and its screwed now.. it will boot into bootloader but thats it... wont boot into stock rom just sits at google icon with unlock icon and buttons lit but nothing else.,.. anyone that can help get paid right now!!!!!!!!!!
flash clockwork recovery and install a ROM
eiabea said:
flash clockwork recovery and install a ROM
Click to expand...
Click to collapse
thats the problem i have tried to flash clockwork through adb but it says error something about the partition... do you have a clockwork img download you can link me that you know will work.. agian i was on 2.3.2
TheKenAnthony said:
thats the problem i have tried to flash clockwork through adb but it says error something about the partition... do you have a clockwork img download you can link me that you know will work.. agian i was on 2.3.2
Click to expand...
Click to collapse
Are you using adb or fastboot? Gotta use fastboot
Sent from my HTC Glacier using Tapatalk
...Download the clockwork recovery http://forum.xda-developers.com/attachment.php?attachmentid=514416&d=1297369766 image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter...
you tried that?
Follow this thread to ODIN back to stock and have it repartitioned to avoid any corruptions.
http://forum.xda-developers.com/showthread.php?t=947950
Since you've unlocked your bootloader, you can get into download mode by turning off phone, holding volume rocker up, plug into usb of computer.
After that, follow this guide step by step for success.
http://forum.xda-developers.com/showthread.php?t=895545
**Follow these threads if all else fails.** Try all small solutions first. This is merely to start from scratch.
eiabea said:
...Download the clockwork recovery http://forum.xda-developers.com/attachment.php?attachmentid=514416&d=1297369766 image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type fastboot flash recovery recovery.img and hit enter...
you tried that?
Click to expand...
Click to collapse
ok did that and it says OKAY and OKAY but when i go to reboot to recovery it just goes back to bootloader.. at the top of the screen in red it says fastboot mode- no boot or recovery img
TheKenAnthony said:
ok did that and it says OKAY and OKAY but when i go to reboot to recovery it just goes back to bootloader.. at the top of the screen in red it says fastboot mode- no boot or recovery img
Click to expand...
Click to collapse
Your probably booting into the bootloader not recovery...there is no option to scroll to recovery?
Sent from my HTC Glacier using Tapatalk
brian6685 said:
Your probably booting into the bootloader not recovery...there is no option to scroll to recovery?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
well i cant boot into recovery for nothing.. im talking about when your in fastboot mode there is a option to reboot and blah and one for recovery.. i cant get to recovery no matter what i try.. im gonna try odin method
peeturr i sent you a PM...
Fixed>>>used odin!!
TheKenAnthony said:
Fixed>>>used odin!!
Click to expand...
Click to collapse
I'm having the exact same problem. How did you solve this? (I'm on a stock, rooted, Nexus S)
As posted, us Odin, first you need to download Odin and the rom to use with it, I think the only one available is a 2.3.1 100% stock, I'll try to get the link for you, on the phone, power it off, and hold down the up/down volume then connect your USB to the phone, you phone should indicate downloading ., from then follow the info posted, I'll get you the link.
http://forum.xda-developers.com/showthread.php?t=947950
When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
When a wipe is issued:
C:\adb>fastboot -w
erasing 'userdata'... FAILED (remote: : partition doesn't exist)
finished. total time: 0.002s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
I think I'm having the same problem. When I try to boot the bootnew.img for intersectRaven's kernel, it hangs at the FIREFIREFIRE yellow triangle with an amber light. No fastboot commands will take me out of it. If it makes a difference, I installed the custom WiFi driver.
Thats the exact same thing is for me.
TyHi said:
Thats the exact same thing is for me.
Click to expand...
Click to collapse
I guess we're in the same boat then. I think my problem came from booting the kernel up, then installing the custom wifi driver, then trying to boot it up again.
When I flashed a kernel I did boot boot.img first and it worked so I did flash boot boot.img with fastboot. Well that didn't work. So I just got the other boot.img for cm7 and tryed to do that. Well I got this error:
C:\adb>fastboot flash boot boot.img
sending 'boot' (3196 KB)... OKAY [ 0.875s]
writing 'boot'... FAILED (remote: partition does not exist)
finished. total time: 0.885s
I am in fastboot but I can not get into twrp2 because when I hold down the power button to enter recovery it just turns amber and just hangs. I do have some mmcblk0pXX .img's if it helps.
Click to expand...
Click to collapse
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
rwphwp said:
Did you follow precisely the commands given here? It sounds like you did, but I just wanted to make sure. I was going to suggest you reset the bootmode to 4000. Have you already tried that?
Click to expand...
Click to collapse
Since apparently the OP and I have the same problem, yes I tried that. The command "fastboot -i 0x1949 oem idme bootmode 4000" doesn't work for me. It just boots into fastboot again.
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Yes I have. It just hangs on the yellow boot with a green light.
Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
The thing is that I cant even root it. It is just stuck it at boot screen for FIREFIREFIRE v1.0.
Smmoph said:
I read someplace when I rooted 6.2.1 with perhaps a Burrito Root prog. The recommended order to get CM7 and TWRP . Is to go - in this order. Root, then TWRP AND lastly update.zip to sdcard for install of CM7. I made space avail. for TWRP'S Backup ( STRONGLY RECOMMEND ) BACKUP. ======which saved me a few times already on a couple frozen boots. Cause I experiment with various launchers, I think.
Click to expand...
Click to collapse
I suck at pushing buttons on forums now (hence the accidental thank), but I'm not really trying to install CM7.
Have you tried the hard reset? Hold power button for app. 18 seconds till screen goes totally dark, then press power bttn on again, once.
Yes I have many times.
I can suggest changing the driver on usb in pc or rebboot pc after uninstall and the change it . But I wanted to show a procedure. win utility 7 gave me the necc. usb driver v. 6 did not have.
TyHi said:
Yes I have. It just hangs on the yellow boot with a green light.
Click to expand...
Click to collapse
Gotcha. Any luck with this method?
There was also A kindlefire utility v.? with an option in red for "factory reset" on the device, perhaps.
rwphwp said:
Gotcha. Any luck with this method?
Click to expand...
Click to collapse
Yes I have. Can't even do adb push. When I get into adb with using boot boot.img from cm7. I get, exec /system/bin/sh' failed no file or directory.
I would not give in, but try to stay calm with all methods to reclaim functionality. I started with rootwiki and Jayce Ooi's And Burrito in order to stay clear of CMD console cause I was not even recognised till Win_usb drivers eventually fell in place. Saw some stuff about editing path's also. Reading alot helped.
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Vashypooh said:
I'd join IRC and see what we can accomplish there. You all are all over the place, and some of you aren't even bricked at all.
Click to expand...
Click to collapse
I was in there all day, and I never got a working solution.
TheMagicPancake said:
I was in there all day, and I never got a working solution.
Click to expand...
Click to collapse
Join there ~12:45-1am EST, ill be available to help then.
Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs like the new kitkat rom that was recently relased for our tablet. It is recommended that you flash this in secboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
To flash this rom in your secboot, you must have skrilax bootloader installed from http://forum.xda-developers.com/showthread.php?t=1619913
Download link of recovery: http://www.mediafire.com/view/?myy59371lsrs6u4
Instructions:
1. Use this awesome tool from http://forum.xda-developers.com/showthread.php?t=2588979 to install adb and fastboot on your windows pc easily. (Remember to run the downloaded exe as administrator)
2. Install Acer A500 usb drivers from http://us.acer.com/ac/en/US/content/drivers (Just search for A500 in the search by product model search box.)
3. Make sure you have Skrilax_CZ's bootloader installed on your A500.
4. Turn off your A500 and turn it on again, this time holding the volume up button.
5. When the bootloader screen appears, scroll with the volume buttons and select Fastboot with the power button.
6. Now, copy the recovery.img which you downloaded from the download link above to the root of your C:/ drive.
7. Press start and open cmd.
8. In cmd, type cd C:/
9. Now, connect your A500 to the PC via usb and wait for a while before typing
Code:
fastboot flash secboot recovery.img
in cmd.
10. After the process is done, type
Code:
fastboot reboot
into cmd.
11. When the tablet boots, hold volume up and when the bootloader screen shows, scroll to Boot Secondary Kernel Image with the volume keys and select it with the power button. CWM should load and have fun!!!
Thanks to @pjsports for his 4.3 device source and vendor blobs
nelsontky said:
Well here is cwm 6.0.4.5 for our beloved a500. You will need this to flash KitKat ROMs in the future. It is recommended that you flash this in seboot as I am not very sure what works and what does not. It pays to have a working recovery in your recovery partition.
Download link: http://www.mediafire.com/view/?myy59371lsrs6u4
Installation:
fastboot flash secboot recovery.img (recommended)
Or
fastboot flash recovery recovery.img
Thanks to @pjsports for his 4.3 device source and vendor blobs
Click to expand...
Click to collapse
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange
I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify
nsciucco said:
ok this is what i get when i try to flash this or any recovery
C:\sdk-tools>fastboot flash recovery recovery.img
sending 'recovery' (5132 KB)... OKAY [ 1.278s]
writing 'recovery'... FAILED (remote: (00030003))
finished. total time: 1.675s
C:\sdk-tools>
any ideas?
ok I got a recovery on there but now it is not seeing any files within my folders- this is so strange
Click to expand...
Click to collapse
Erm what ROM are u using. And yea do you have like zip files in your folders cos I think the recovery only see zip files
tire_007 said:
I tried flashing this recovery but i get this error
also i tried flashing the img recovery with this app but i don't work either
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Click to expand...
Click to collapse
Dun use the app (idk those apps never worked for me, well except for the Acer recovery installer) and when using fastboot, make sure the recovery.IMG is in the same directory as fastboot
I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app
nsciucco said:
I was on cm10.2. My tablet froze so I held the power button down to hard reset. Then it never booted up. I tried to go into recovery to install a new rom and I'm not even able to get into downloads. If I click sd or sd-ext there is no folders anything. It's like my device is wiped. I'm stuck. Only thing I can do is get into bootloader or apx mode. I've downloaded roms that I can supposedly flash in apx mode with that blackthunder tool. But I can't figure it out. I'm not an idiot either. I've rooted well over 200 phones . I do it for extra cash...and never had a issue like this
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Hmmm download a working recovery and flash into your recovery partition. Then flash this into secboot
Flash what?
Sent from my SM-N900P using xda app-developers app
nsciucco said:
Flash what?
Sent from my SM-N900P using xda app-developers app
Click to expand...
Click to collapse
Well you can download twrp from http://teamw.in/project/twrp2/88 and flash it to your secboot partition with "fastboot flash secboot [name of recovery].img" Then go to your boot menu (hold volume up when booting) and choose the akb partition (second partition) This should get you booted into twrp where your files should be there. If there are still no files, you have to use an external sdcard good luck
any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.
kronflux said:
any chance you can build this: http://forum.xda-developers.com/showthread.php?t=2201860
against our device + CWM version 6.0.4.8?
I'd do it, but I have no idea where to start. I love PhilZ touch recovery, it's very customizable and also very useful.
Click to expand...
Click to collapse
Well i can try but no promises
thanks! apparently it's easy.
Once you can build stock CWM, just replace your bootable/recovery folder with this one and lunch for your device
Click to expand...
Click to collapse
I just don't have the sources, or the knowhow to compile this myself.
nelsontky said:
Well i can try but no promises
Click to expand...
Click to collapse
had a chance to try yet? not to bug or nag, just curious for an update
Now updated with instructions
Now this is updated with instructions!
thanks man.
good work
nelsontky said:
Now this is updated with instructions!
Click to expand...
Click to collapse
can you provide building instructions? I tried using the sources you used, but I get errors using his repos. He's got some repos from "loosethisskin" which don't allow building. I can't remember the exact errors, but I'm wondering what you did to avoid this(if you encountered this at all)
By simply not replacing those repos(ie: removing them from the manifest before syncing) I get a resulting recovery.img that fails to fastboot flash.
I've even tried using acer recovery flasher, and a couple other tools, but it doesn't boot.
I'd like to try building 6.0.5.0 as well as PhilZ Recovery, but again, I can't get it to build.
@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.
bovirus said:
@nelsontky
Thanks for your job.
I want to make a backup before to install the new Bootloader ( Skrilax_CZ's), but to that I cannot do it with stock recovery (the stock recovery didn't have the option to backup/restore).
Is there some problem/incompatibility that avoid to load your recovery (6.0.4.5) before to load Skrilax_CZ's bootloader?
Or in another way the function of your recovery are based on Skrilax_CZ's bootloader?
Could you update your recovery with new file from CWM Github (recovery version is now 6.0.5.0)?
Could you post the configuration file (Board parameters) that you use to compile the recovery.
I downloaded the source of CWM and I want to test it myself.
If you update your CWM repository via GitHub pull command just recompile the recovery.
Proposal to download the file: could be better to distribute the recovery as zip (like A500_CWM_recovery_vx.x.x.x.x.zip - it's self explantory) with inside the recovery.img file. It's always better to avoid to download native recovery image to avoid partial download or corrupted file.
Thanks.
Click to expand...
Click to collapse
The Skrilax_CZ bootloader is absolutely necessary, because it allows flashing and booting from the secboot. The recovery is too large to fit in the recovery partition. That having been said, I may be able to shrink it to fit, if I could get it to compile and boot.
I've had to do the same thing to the recovery for the HTC ChaCha,
He's not using a straight up CWM repo, he would be using the repos for CM10.2, which automatically compiles CWM along with it(or if you give it the arguments, it can compile just recovery)
The bootloader can only be flashed using nvflash, and for a backup, you'll need an older copy of CWM and flash that via fastboot. I personally recommend the tegraowners recovery(I don't like the tegraowners team, but their recovery really is best out of the older ones) you can find it here
Apparently windows 8 hates my tablet. so I tried it on a windows 7 machine, the result was a working recovery. although oddly, it build 6.0.4.6, not 6.0.5.0. weird. maybe I'll poke at it later and try to update just the cwm repo. whatever the case, this gives me a working setup to try PhilZ Touch Recovery
I believe that the main scope should be to have a recovery that use no more space than the partition size.
It's due to avoid not use unofficial bootloader and to avoid overwiting importan partition like NVRAM (IMEI).