Database Users

Can not flash anything, PLEASE HELP

ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks

zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?

yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)

Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.

thats what I have tried, it goes to three skaters center screen does nothing

I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.

zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.

the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens

zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?

correct and like i said I have tried to reflash everything from fastboot but no go

Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error

got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go

What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App

tried a pd15 and it doesn't complete, drops a failed message

Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.

I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks

uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s

Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?

any ideas on how to wipe cm bits atleast?

Need Help. I've Tried Everything.

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

Boot Loop To Google Logo

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.

[Q] [Magic 32B] Can't install or boot cust recovery after htdev unlocked

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 !

Thoughts on bootloop of ZE551KL

Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?

hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...