So, I rooted my device via gfree. I flashed CWM Recovery 3 from ROM Manager, and flashed a 2.3 ROM. The ROM started having numerous problems, so I flashed the PD15IMG zip via the bootloader, now I am stuck in a boot loop, and I get a red triangle when I attempt to access Recovery.
I have attempted to use fastboot to flash a new recovery.img, but I get:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y recovery.img
sending 'recovery' (3948 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.293s
I still have S-Off
HBOOT is 0.86.0000
Radio 26.03.02.26_M
Any one know what else I can do? Thanks
troby86 said:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y recovery.img
sending 'recovery' (3948 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.293s
I still have S-Off
HBOOT is 0.86.0000
Radio 26.03.02.26_M
Click to expand...
Click to collapse
i'm assuming you are trying to flash from the hBoot menu.
You have the stock .86 hBoot, you need the .85 hBoot to flash from there.
The stock recovery first shows a red triangle. You have to press Volume Up and Power to show the recovery menu.
Maybe try flashing PD15IMG again. All you need is to get something that boots, then you can work from there. If you're getting bootloops with stock recovery and don't have the engineering bootloader, you may just have to send it in for a new one. As the previous poster stated, you need the engineering bootloader (0.85.2007) in order to flash partitions over USB using fastboot commands.
Didnt he say that he couldn't get to recovery? Too bad you didn't flash eng bootloader, might have been a easier way out of the problem.
Sent from my demonSPEED Glacier using XDA Premium App
Related
Hi, I am following the "Ultimate Guide" (forum.xda-developers showthread.php?t=734617) and "theunlockr" (theunlockr /2010/03/11/how-to-root-the-mytouch-1-2-and-fender-mytouch/) instructions. I have gotten to step 7 with very few issues. Below is the terminal output from my step 7:
$ fastboot flash radio radio.img
sending 'radio' (21504 KB)... OKAY
writing 'radio'... OKAY
[MACBOOK]$ fastboot flash hboot hboot.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
[MACBOOK]$ fastboot flash recovery recovery.img
sending 'recovery' (4520 KB)... OKAY
writing 'recovery'... OKAY
[MACBOOK]$ fastboot reboot-bootloader
rebooting into bootloader... OKAY
[MACBOOK]$ fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: not allow)
[MACBOOK]$ fastboot devices
SH04NPB01763 fastboot
[MACBOOK]$ fastboot reboot-bootloader
rebooting into bootloader... FAILED (remote: not allow)
and that's where I'm stuck. If I try to just straight boot the phone it hangs on "htc magic" screen.
PLEASE! Any help would be enormously appreciated
You should be able to just boot into recovery. Turn the phone off (taking out the battery if necessary) and turn it on holding the home key+the power key. Hod them for a good 1 1/2 minutes as it could possibly take that long to go. Once in, just continue using the guide.
Sent from my HTC Magic using XDA App
THANK You, you were correct.
My mistakes were:
a) I mixed up power+volume with power+back (I figured that out before posting here)
b) I expected the phone to go into a whole operating system, missing touchscreen, but a boot screen which hangs at "htc magic" was just as good. If you turn it off at that point and carry on, it's fine.
c) reboot-bootloader FAILED was irrelevant, continuing to the next step worked
d) I had to hold Power+Home MUCH longer than I thought I would have to.
... also, it takes WAAAAAAAAAY Longer to load the OS from the "htc magic" screen than any other phone Ive ever had.
There goes the gf's htc.
So I was 'upgrading' my gf's htc dream, and now I can only get to either a 'rogers' screen, or into fastboot screen. (holding camera button on power) I cannot access the phone with adb.
I was following:
----------
wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
-------------
Rooting the Rogers Dream & Installing Amon_Ra's Recovery
Everything went fine on that page. The radio is already the correct version. (although the file is on the sd card anyway)
Next I went to install dangerSPL on this page:
----------
wiki.cyanogenmod.com/index.php?title=DreamangerSPL
-----------
DreamangerSPL
Now when I tried to boot into recovery I get the 'rogers' screen and that's it. I held home and power down for over 3 minutes, but it just sits there. Here is what I started with. This information never changed.
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Jun 2 2009,21:33:16
Now I can not see anything with the command 'adb devices', and when trying to do the command 'fastboot flash recovery recovery.img' I get FAILED (remote: not allow)
Any help is welcome.
J
almost there.
I followed the steps here:
wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched&oldid=4000
and now I got through everything, but now the phone has been booting for about 20 min. First boot does not seem to be working.
update
Just to let everyone know, I went back in and did the updates in order, cm6, kernal, then google. Now everything is great.
The web site i mentioned last time is great. Good luck to all.
My son brought me his Nexus S 4g and told me that it doesn't work anymore. He says that he didn't do anything and that it just started doing this on its own. Any help would be greatly appreciated.
When powered on, it quickly goes to the screen with the Google icon and a lock icon. It sits here for about 30 seconds, then reboots to the same thing. If I pull the battery and hold Vol Up and Power when inserting the battery I can get into Fastboot, but when I select Recovery or Reboot, I get the same Google screen.
When I gave him the phone, it was rooted with CWM recovery loaded and a ICS ROM running.
Any help would be greatly appreciated as I have been reading through threads all night long without finding much.
Sounds to me like you need to begin the rooting process again at the "fastboot oem unlock" part. Since you probably don't have anything on your SD card, you might have to push a new recovery via fastboot as well.
Look to this thread:
http://forum.xda-developers.com/showthread.php?t=1078213
for inspiration.
Once you get into the recovery loaded via fastboot, you can get whatever rom that you want onto the SD card by navigating to:
Mounts and Storage > Mount USB Storage
and leave it on that screen while you load the rom onto the SD card.
After that flash the new rom via CWM as normal.
Thanks for the reply. Since I was already unlocked, I followed the steps to return the phone to stock, including flashing boot, system, userdata, recovery and erasing cache. Now when I reboot, it just loops to the Google screen and reboots after 30 seconds. The only difference is that I don't see the lock icon at the bottom or the Google screen.
When I select Recovery, it just goes into the same Google loop. I am going to try to go through the root steps and see what happens. :-(
I was able to unlock the phone, but it will not boot into Recovery. I can get to Fastboot, but I am back to where I started.
When I gave the phone to my son, I had installed SetCPU and configured a profile to throttle the processor down when the screen was off to conserve battery. I am now wondering if he tried to overclock the processor and clicked "set at boot".
Any more suggestions? (please)
Did you successfully flash a recovery.img? Immediately after this you should hit Recovery, then mount the storage, copy a ROM over, do a Full Wipe and flash the ROM.
If all goes well, you'll boot fine. If not, it may be a hardware problem. Try to wipe most of it and lock the bootloader if you need to send it to samsung.
It looks like I successfully flashed a recovery image. I have tried version 5.x and version 3.x. Below is the result of the 5.x command. However when I select Recovery from Fastboot, I go to the Google screen loop.
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery-cloc
kwork-5.0.2.0-crespo4g.img
sending 'recovery' (4136 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>
OK, go to http://wonderly.com/bb/CRESPO4G/OEM/GRJ22IMAGES.zip
That will download the GRJ22 stock images of your phone. Unzip them in your PC. Next, use fastboot like this.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
After it finishes you can reboot your phone with "fastboot reboot". This will installed Stock GB 2.3.4 for NS4G. Setup your phone and you will get OTA to 2.3.5. After that you will get OTA again to 2.3.7. Good luck.
By the way, you must let it OTA all the way up to 2.3.7 to get the latest Radio and bootloader version.
Giving it a shot now. I'll let you know shortly how it goes.
Update: Same result. All commands completed successfully, but I end up in the Google logo boot loop. Is there a kernel .img file that I should flash, in case my son tried to flash an unsupported kernel?
C:\Program Files\Android\android-sdk\tools>fastboot flash bootloader bootloader
img
sending 'bootloader' (1536 KB)... OKAY
writing 'bootloader'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash radio radio.img
sending 'radio' (15232 KB)... OKAY
writing 'radio'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash system system.img
sending 'system' (174451 KB)... OKAY
writing 'system'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash userdata userdata.img
sending 'userdata' (18796 KB)... OKAY
writing 'userdata'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash boot boot.img
sending 'boot' (2904 KB)... OKAY
writing 'boot'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot flash recovery recovery.img
sending 'recovery' (3144 KB)... OKAY
writing 'recovery'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY
C:\Program Files\Android\android-sdk\tools>fastboot reboot
rebooting...
C:\Program Files\Android\android-sdk\tools>
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
rasengan82 said:
That included stock kernel.
Man you might just want to fastboot oem lock and send the phone. Those were factory images... if they don't work it means hw issues.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
I agree. If this does not work, send the phone back to Sprint.
I really appreciate y'all trying to help. I will see if Sprint will be kind enough to exchange it. Thanks again.
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
The Usual Suspect said:
so i unlocked my bootloader using the htcdev guide. this updated my hboot to 1.02.000 and when i try to flash CWM i get this error.
Code:
sending 'recovery' (1685 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
Click to expand...
Click to collapse
how (which method) are you trying to flash the recovery?
Here's the quick guide
Install hTc drivers successfully on pc.
Remove hTc sync and other related apps.
Now download clockworkmod recovery(whichever you want) and fastboot+adb kit on pc.
Open fastboot.
Connect ur phone. Load the bootloader and then fastboot. Fastboot mode(something like that) should be on your phone. Paste recovery and boot image in fastboot folder.
Type fastboot devices
Type fastboot flash boot boot.img(boot.img can be found in ur stock ruu )
Type fastboot flash recovery 'recoveryname'.zip
After that disconnect ur phone.
Select recovery.
(If u dont see anything, it was unsuccessful, hold vol up+power to see default recovery.)
Now install roms like this(http://forum.xda-developers.com/showthread.php?t=1851096):p(my rom) via recovery.
Hit Thanks.
You are done
Note:s off is not required for flashing a custom rom, however an unlocked bootloader is.
help needed.
hey der. i have rooted my phone with s-on. but i am facing the same problem as i cannot boot in cwm recovery mode and hence cannot install a custom rom. i am no developer. so please can you elaborate your above method step by step. sorry i am a noob here.
thanx anywayz
Have you managed to install cwm?
Hi everyone,
I have an HTC Magic 32B (SFR/Vodafone FR).
I updated hboot from 1.33.0013 to 1.33.0014G (*1) to be able to unlock the bootloader with htcdev unlock.
I unlocked it successfully using HTC official instructions.
Now I want to boot or install a custom recovery (recovery-RA-sapphire-v1.7.0G.img) and it doesn't work.
My hboot boot says :
Code:
*** UNLOCKED ***
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0014G (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Jan 31 2012,14:43:52
HBOOT
<BACK> FastBoot Mode
From fastboot (when I hit Return) I have the "FASTBOOT USB" string, from fastboot if I try :
1)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.712s]
booting...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.733s
2)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.712s]
writing 'recovery'...
[B]FAILED (remote: not allow)[/B]
finished. total time: 1.738s
After reading htc instructions to flash img, I also tried from RUU mode using "fastboot oem rebootRUU", that gives me RUU USB on the phone and on the computer :
Code:
C:\android\downloads>fastboot oem rebootRUU
...
OKAY [ 0.012s]
finished. total time: 0.016s
Then I try :
1)
Code:
C:\android\downloads>[B]fastboot flash recovery recovery-RA-sapphire-v1.7.0G.img[/B]
sending 'recovery' (4520 KB)...
OKAY [ 1.718s]
writing 'recovery'...
[B]FAILED (remote: image type not support)[/B]
finished. total time: 1.749s
2)
Code:
C:\android\downloads>[B]fastboot boot recovery-RA-sapphire-v1.7.0G.img[/B]
downloading 'boot.img'...
OKAY [ 1.714s]
[B]booting...[/B]
Here it hangs, I must enter a fastboot reboot to regain the control on the device.
I don't know what's wrong here. Either from fastboot (usb) or ruu (usb) it don't work even if the bootloader is unlocked.
amonra recovery should install and work on this phone right ?
Currently I don't want to root or S-OFF the phone because I like to apply not too much modification on it.
Can you help me ?
Thanks for the attention, and even more if you can help
(*1) 1.33.0013 cannot be htcdev unlocked because it don't accept "fastboot oem get_identifier_token", that's why I updated to 1.33.0014G.
The update was given by htcdev.com through an RUU that didn't work because I started it from adp (phone started normally with usb debugging on) and for an unkown reason adp reboot bootloader didn't work, I made it work be starting RUU exe from fastboot directly.
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
superbob56 said:
I think my problem/solution may be related to the error : "remote: image type not support" when I try to flash recovery being in RUU mode.
From the official updates files (official ruu and fota) I've found that some images are not of the img format but the nb0 format. Maybe I need to flash an image that is of this format (nb0), the problem is that I have no idea how to find or convert amonra recovery image to this format...
If it is the problem, it is lame not to be able to flash img files ...
Also, one idea I had is that I have to flash files through an update.zip file rather than a single img. But it is a lot more complex to figure out (making a valid update.zip package)...
I'm quite lost and decieved about the HTC "unlock" (I think I'm not the first one to be) ... (And I don't want to brick my phone)
Click to expand...
Click to collapse
hi, i have same problem on my HTC Magic, from hboot 1.33.0014 i can`t do enything (flash new recovery or new rom or make RUU)
did u resolved that problem?
I must admit I've given up.
I recently bought myself a fresh Nexus 5...
Gold luck to you if you try to go on with the HTC Magic !
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Did you solve the problem?
i think you can try https://forum.xda-developers.com/meizu-pro-5/how-to/tutorial-restore-hard-bricked-lost-t3838461
ISCYamil said:
Did you solve the problem?
Click to expand...
Click to collapse
Nope. The reason I want to flash stock boot image or patch boot image because of every time flash new flyme rom via TWRP, the phone always rooted and Magisk is not working to hide root. Now I just use as is. The banking app cannot be working with rooted phone.
hall060679 said:
trying to flash boot.img even stock boot or patched image but got failed as message partition does not exist. The device is in fastboot mode with unlocked bootloader and rooted.
Tried Flashify, but freeze when tapping on Boot image.
command: fastboot flash boot boot.img
Result:
c:\adb>fastboot flash boot patched_boot.img
sending 'boot' (16852 KB)...
OKAY [ 0.382s]
writing 'boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.387s
Any idea?
Click to expand...
Click to collapse
I had the same problem just earlier today. What did the trick for me was installing the ROM using TWRP recovery. Move the stock ROM (you need to zip it for the process) into phone's root directory using your computer and then in TWRP tap on "Install" and find the zipped stock ROM and confirm. Let us know.
try fastboot flash bootimg instead.