Database Develop

N1 will not flash recovery

HELP ME! I cannot get this recovery image to flash for the life of me. here's the story. I have what was a ere27 build N1. 2 weeks ago I did the manual update to Google's prerelease of Froyo. Now my phone is a FRF50 build. As everyone else found out it's buggy as hell and GPS does not work. I searched for weeks to try and find a fix and I couldn't find anything other than to unlock the bootloader root the device and flash a different rom onto the phone. So I unlocked the BL from instructions here. Then in downloaded Pauls 1.0 FRF50 superboot. I tested the root with torch and it works, so the unlock and root must have worked. This is the first time I have ever used the cmd window and I have tried everything under the sun to get this thing to work so I can flash Pauls froyo and have working GPS again.
I followed the instructions found here, but I keep getting this error.
Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.
cd C:\fastboot
C:\fastboot>fastboot-windows devices
HT9C*******8 fastboot
C:\fastboot>fastboot-windows flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... FAILED (remote: not allowed)

have you done 'fastboot-windows oem unlock' ?

Yessir. Unlocked padlock on startup.

Try this:
fastboot devices
fastboot flash recovery recovery.img

C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...

Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
I'm having the EXACT same problem.

Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.

ATnTdude said:
Did you apply root before flashing recovery? Flash Paul's superboot, then install AmonRA recovery.
Click to expand...
Click to collapse
The OP says he is rooted. I am rooted as well. We both have had success in fastboot, but our recovery is defaulting to the standard android one, and not the custom one that we flash.

Hyper4mance2k said:
C:\fastboot>fastboot flash recovery C:\fastboot\recovery-RA-nexus-v1.6.2
sending 'recovery' (3954 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 1.563s]
finished. total time: 2.203s
so it worked once, then it went back to the stock recovery...
Click to expand...
Click to collapse
All you need to do is
Fastboot flash recovery recovery-ra.img
Or whatever the image name needs to be.

I think I figured out the problem. I was running a rooted version of FRF72, and for whatever reason, no matter how I tried to flash the recovery, it would not stick. I could use clockwork's app to flash and reboot into the custom recovery, but if I rebooted again, it would always default to the stock android recovery.
I now have the custom recovery working for me at all times. Here is what I did (Keep in mind, I take no responsibility if you brick your phone into oblivion...):
First: Make sure that you have an unlocked bootloader, and are rooted. I used Paul's Superboot for the FRF50 build on my FRF72 build, and it worked flawlessly.
1. Find a custom ROM such as the MoDaCo MCR18 or 19 build if you want something close to the OTA builds.. or whichever one you'd like to flash. Make sure it is not a stock/rooted OTA build! I personally used Paul's MCR18 build over at MoDaCo.
2. Download it, and then rename the rom to update.zip and transfer to your SD card's main directory
3. Download the clockwork ROM Manager app from the android Market and run it.
4. Flash ClockworkMod Recovery from the app
5. Use the feature in the app to "Reboot into Recovery"
6. You should now be in the ClockworkMod recovery
7. Do a nandroid backup!! (that may reboot your phone normally.. if so, repeat steps 4 & 5 to reboot back into custom recovery)
8. If your rom requires you to wipe prior to install, then wipe cache partition from the main menu, and then go to advanced and wipe Dalvik cache prior to the next step. I did not have to wipe, so if this rebots your phone normally, repeat steps 4 &5 to get back into custom recovery.
9. Select the option to "apply sdcard:update.zip"
It will then flash the custom ROM onto your Nexus One
10. Once your phone has been rebooted, download the ClockworkMod Rom Manager from the market again (if it is not already on your phone), and re-flash the custom recovery. It should now always boot into the custom recovery.
Hope that helps!!

File system slow in recovery. Can't flash ROMS.

Hello!
Having a pretty big problem, as I am trying to help my girlfriend get her phone all recovered and usable again for her. On our HTC Ones, we both use Android Revolution HD and were updating to the latest (4.4 version). With my phone, the installation of TWRP 2.6.3.3, then the rom went completely fine.
On her phone, it is going terribly. I made one mistake and forgot to copy the ROM over to the device before I wiped her system, so I don't have the new file to flash. I attempted to flash the old ROM, which was sitting on her device, but it is extremely slow to the point of we waited about an hour or two and it never installed. I have attempted to sideload, but the file is copying much slower than expected. Heck, everything involving the filesystem is running slow, even data wipes! I tried a full system erase, so now I am at a position where we have no flashable ROMS on the device.
I have tried both adb push and adb sideload to send the file, and both never successfully complete, even after waiting hours.
Where do I go from here? Any idea why flashing roms and file system is running so slow?

Change USB port/cable/computer and try push/sideload again
sent from my mobile device

SaHiLzZ said:
Change USB port/cable/computer and try push/sideload again
sent from my mobile device
Click to expand...
Click to collapse
I tried this already. I know this is not the cause as installing a zip of a new rom literally takes about 2 hours to write to the system.
Even a fastboot flash recovery takes about 30 seconds on her device, tested with multiple cables on two macbook pros. My HTC One flashed normally in less than a second...

When I flashed recovery:
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9184 KB)...
OKAY [ 1.333s]
writing 'recovery'...
OKAY [ 0.696s]
finished. total time: 2.029s
When I flashed her phone with the same recovery file (TWRP 2.6.3.3):
MacBookownloads limitin$ fastboot flash recovery recovery.img
sending 'recovery' (9948 KB)...
OKAY [ 1.450s]
writing 'recovery'...
OKAY [ 35.708s]
finished. total time: 37.158s
Same phone. Some hboot version. Only thing I had to do to hers first (I had done mine previously) was use revone to s-off her device, which was successful after a few attempts.

Flash recovery FAILED (remote: no transfered data)

Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!

calbertuk said:
Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!
Click to expand...
Click to collapse
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.

majmoz said:
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.
Click to expand...
Click to collapse
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP

calbertuk said:
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP
Click to expand...
Click to collapse
I don't know what you are trying to accomplish but here is a possibility: How to : Flash HTC One Mini with out S-OFF and no need RUU Stock ROM and [ROM][M4 - 4.09.401.3] Official Stock Sense 6 Rom v2 & Firmware

[Q] HELP - Bricked HTC One m7 (m7ul)

Hi,
I am after some help trying to get my HTC One back up and running.
I unlocked the bootloader using the htcdev website and installed cyanogen mod.
This was working fine for quite some time, until I recently wanted to download an app that was only available on stock phones.
I tried editing the /system/build.prop file to change the version to fool the app store but that didn't work.
Then when I restored my backup build.prop, I think I got the permissions wrong or something and the phone rebooted and went into a boot loop.
Then I followed a guide to get twrp on the device which worked.
Then I followed another guide attempting the restore the device to stock using the commands
Code:
fastboot oem lock
and
Code:
fastboot oem rebootRUU
.
Now the phone is stuck in a boot loop. All I can do is hold down power and volume down to get to HBOOT and Fastboot. If I try and load recovery it reboots to the same menu.
What else can I try, or do I now have a new paperweight?
Thanks for any suggestions.
- gatamous

Also,
I have tried flashing the stock recovery but I get signature errors.
Code:
C:\Android\android-sdk-windows-r24.0.2\platform-tools>fastboot flash recovery recovery_2.24.980.2.img
target reported max download size of 1443966976 bytes
sending 'recovery' (8752 KB)...
OKAY [ 1.140s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.846s

OK,
Never mind.
I was unable to unlock my bootloader because I was typing fastboot flash unlock token Unlock_code.bin instead of unlocktoken being one word.
One I fixed that the twrp recovery started again.
Once I opened that the phone apeared on my PC as a storage device.
I copied a cyanogen mode zip to that directory then installed it via twrp.
Now I have cyanogenmod working again.
Yay - no longer a brick.
I guess I am out of luck with reverting it to stock if the RUU I need is not available for my carrier - is that right?
If so I'll stay on cyanogen mod and not worry about reverting to stock.
Next time I guess I'll take one of these nandroid backups while the phone is still stock. Hindsight.
- gatamous

Cant install recovery / can't unlock [Xperia Z]

I Unlocked someones Xperia Z and installed Cyanogenmod and TWRP on it some time ago. It was too unstable for their liking so they reset it to its stock settings using Sony Emma (or whatever its called).
Well now that they've got a nexus 6P, they've given the Xperia Z to me, so i tried to install TWRP and i get errors trying to overwrite the recovery.
Upon inspection of the bootloader lock settings i found it to say "bootloader unlockable: Yes", which indicates it is unlockable but not yet unlocked, and it continues to say this no matter how many times i attempt to unlock it.
Below is a demonstration attempt to unlock the phone and install TWRP:
Code:
[email protected] ~/Desktop $ sudo fastboot oem unlock 0xC431F679A4E1ECEB
...
OKAY [ 0.408s]
finished. total time: 0.408s
[email protected] ~/Desktop $ sudo fastboot erase recovery
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
[email protected] ~/Desktop $ sudo fastboot flash recovery twrp.img
sending 'recovery' (10656 KB)...
OKAY [ 0.337s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.339s
[email protected] ~/Desktop $ sudo fastboot flash boot twrp.img
sending 'boot' (10656 KB)...
OKAY [ 0.337s]
writing 'boot'...
OKAY [ 0.563s]
finished. total time: 0.900s
I've also tried it using flashtool on Windows and similarly it doesn't work.
I can't understand why it would work the first time, but now that its been factory reset the unlock doesn't work.

Have you tried with Xperia z dual recovery? (XZ dual-recovery) . It's very simple to install, for more info please refer to the official thread.

aaronkatrini said:
Have you tried with Xperia z dual recovery? (XZ dual-recovery) . It's very simple to install, for more info please refer to the official thread.
Click to expand...
Click to collapse
To do that i'd need a custom recovery, and i can't install one because the bootloader is locked and there is no recovery present on the device.
EDIT: ah i just saw the install exploit for unrooted devices. I'll give it a shot.

Didn't work unfortunately :/
I wasn't able to to use dual recovery to unlock the phone.
I downloaded and then installed a 10.3.x.x version of a stock xperia Z rom using flashtool, then i ran the dual recovery setup. EVERY operation reported that the file or folder didn't exist,and that the install had failed.
I was able to root the phone using Root Genius. I then installed TWRP manager and tried to install TWRP from there (this worked on that phone before), but it corrupted the rom so now it just freezes and restarts on the boot animation.

Recovering with Emma does not relock the bootloader. So bootloader should still be unlocked. Recovering with Emma also removes root so you need to root your device before you can install a custom recovery.
Sent from my E6653 using XDA-Developers mobile app

You are indeed right! although the problem appeared to be a locked bootloader at first, it now appears it was a corrupted recovery partition.
I, again, set the phone to a stock 10.1.x.x ROM (it was still corrupted from last time so i had to reset it again using Sony Emma) using flashtool and rooted using Root Genius. I then tried to use flashify to install XZ-dual-recovery but it told me the recovery partition was missing.... so i searched around and found the cure to my woes may be DooMKernel, so i set it up, and everything fell into place from there! below is how i believe it worked:
1. Used fastboot on my PC to install DooMKernel v22 as per the official page instructions
2. successfully booted into TWRP
3. used TWRP to install XZ-dual-recovery
4. successfully booted into CWM recovery
5. used CWM recovery to format all internal paritions
6. used CWM to install ROM and root
Thank you everyone for your help!

My xperia z has the 5.1.1 rom and is rooted.
The boot loader is locked and I couldn´t unlock it.
I cannot get into recovery with PC, neither with the buttons.
I like to install a custom 6.0 rom.
any suggestion?
thxs in advance for your support.