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!!

[Q] Bootloop troubles

I was trying to unlock and root my Vivid and seem to be stuck in a bootloop.
I used the All in one kit v 1.2 (Thanks Hansoon) unlocked my bootloader, and installed CWM.
The problem occurred when I tried to install the HoliCake kernel, after that step I couldn't boot into the base OS.
At the moment I can access hboot, fastboot and CWM.
When I try to boot, all that happens is the HTC logo is visible indefinitely.
Trying to install the stack kernel gives me the following output, and i'm not really sure where to go from here.
Code:
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>adb push Kernels/Module
sStock/system /system
error: device not found
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>adb reboot bootloader
error: device not found
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>fastboot flash boot Ker
nels/Kernel-HereStock/boot.img
sending 'boot' (2838 KB)... OKAY [ 0.658s]
writing 'boot'... OKAY [ 1.578s]
finished. total time: 2.236s
C:\Users\Rohit507\Desktop\Vivid_All-In-One_Kit_v1.2\data>fastboot reboot
rebooting...
finished. total time: 1.879s
Thank you all, since this device is also my main phone, it would be appreciated if I could get it working again before the day is out, but even if that's not possible i'm gratefull for all your help.

I use the same tool. It is amazing.
Were I you, I'd download the stock ROM from the "Revert your phone to stock from ICS" thread in the dev section and start over just to be on the safe side.
Sent from my HTC PH39100 using xda premium

Okay, i'm back to stock, now to figure out how to actually mod this thing when adb doesn't seem to want to connect.

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

Help flashing recovery failed

So I wanted to flash TRWP recovery via fastboot but everytime I try it it fails saying:
Code:
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12534 KB)...
OKAY [ 1.593s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.740s
My bootloader is unlocked and S-off
(Maybe its worth mentioning that my phone is stuck in the bootscreen)
Anyone who knows what the problem could be?

zabdelicious said:
So I wanted to flash TRWP recovery via fastboot but everytime I try it it fails saying:
Code:
D:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img
target reported max download size of 1514139648 bytes
sending 'recovery' (12534 KB)...
OKAY [ 1.593s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.740s
My bootloader is unlocked and S-off
(Maybe its worth mentioning that my phone is stuck in the bootscreen)
Anyone who knows what the problem could be?
Click to expand...
Click to collapse
Ok I managed to flash TWRP, but theres another problem... I wanted to flash a stock htc m7 rom via an otg cable and flash drive. The rom is in the root of the stick but when I select the stick in twrp its empty

zabdelicious said:
Ok I managed to flash TWRP, but theres another problem... I wanted to flash a stock htc m7 rom via an otg cable and flash drive. The rom is in the root of the stick but when I select the stick in twrp its empty
Click to expand...
Click to collapse
What format is your usb stick? NTFS won't work with otg, try formatting the usb as fat32 copy the rom back on and try again.
What version of TWRP are you using? Newer versions use MTP in recovery so you can just 'drag and drop' the rom to your storage from recovery mode
Sent from my SM-T230 using Tapatalk

Danny201281 said:
What format is your usb stick? NTFS won't work with otg, try formatting the usb as fat32 copy the rom back on and try again.
What version of TWRP are you using? Newer versions use MTP in recovery so you can just 'drag and drop' the rom to your storage from recovery mode
Click to expand...
Click to collapse
Thanks now it worked, however there occurred another problem. When I flash the rom via otg, the phone reboots and is again stuck in the htc logo screen. I've waited couple of minutes but nothing happened

zabdelicious said:
Thanks now it worked, however there occurred another problem. When I flash the rom via otg, the phone reboots and is again stuck in the htc logo screen. I've waited couple of minutes but nothing happened
Click to expand...
Click to collapse
Which version of twrp are you using? And which rom are you flashing? Also normally I would recommend copying the rom from the OTG to the internal storage then install it from there. :good:
It's also worth noting a successful clean install can take 15 to 20 min to pass the htc boot logo, on first boot.
Sent from my SM-T230 using Tapatalk

Question Problem entering/flashing custom recovery

Hello everyone I have been havinng some issues with my realme 8 RMX 3085. I was planning to install Lineage OS and custom recovery. I followed tutorials on xda. Fortunately i unlocked bootloader with official method - deeptest.apk, to do this firstly I flashed rom with thailand one. Everything seems to be succesfull, in settings bootloader is unlocked.
fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (131072 KB)...
OKAY [ 5.336s]
writing 'recovery'...
OKAY [ 0.451s]
finished. total time: 5.788s
However after that I am not able to enter recovery (even stock one). I kept flashing recovery image via fastboot. Everything seems to be all right until I try to enter it. Using command fastboot reboot recovery nothing happens. Another one adb reboot recovery tries to enter recovery several times with no success, then reboot to os.
I read couple of threads about that issue, tried using different computers, with different os - still the same. Tried using different cables and usb ports also nothing changed.
Does anyone have any idea what can couse the problem? Appreciate any advices.

Same here, trying few days but nobody help

Ok..did you installed magisk by flashing magisk patched boot.img ? If yes..then you need to restore/flash stock boot.img to enter recovery..this problem occurs on android 12 only..

https://telegra.ph/Flash-LineageOS-on-Realme-8-06-05
try follow this tutorial, worked for me