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] Accidentally flashed wrong SBF

Hello, I'm struggling around with a problem for 3 Days now and just cant get it to work.
I accidentally flashed Android 2.3.6 Blur_Version.5.8.25.XT861.ACG.en.US from sbf.droid-developers.org/phone.php?device=15 on my XT862. It boots up okay, but I cant get ROM Manager or Safestrap to work.
So i want to go back to 2.3.4. I tried 5.5.959, 5.6.890 and 5.7.906 from URL mentioned above with RSD Lite, but i get "6/21 flash cdt.bin -> Phone returned FAIL" error.
I also tried using "1-CLICK DROID 3 SBF BY OVELAYER" but i get error "Preflash validation failure" when writing boot and recovery. (Everything else gets "OKAY".) After that the Phone boots 2.3.4, but I'm not able to install Recovery via ROM Manager or even Safestrap.
Does anyone have an idea how to fix this? Or is it not revertible and do i have to live with Stock 2.3.6?

iso2k said:
Hello, I'm struggling around with a problem for 3 Days now and just cant get it to work.
I accidentally flashed Android 2.3.6 Blur_Version.5.8.25.XT861.ACG.en.US from sbf.droid-developers.org/phone.php?device=15 on my XT862. It boots up okay, but I cant get ROM Manager or Safestrap to work.
So i want to go back to 2.3.4. I tried 5.5.959, 5.6.890 and 5.7.906 from URL mentioned above with RSD Lite, but i get "6/21 flash cdt.bin -> Phone returned FAIL" error.
I also tried using "1-CLICK DROID 3 SBF BY OVELAYER" but i get error "Preflash validation failure" when writing boot and recovery. (Everything else gets "OKAY".) After that the Phone boots 2.3.4, but I'm not able to install Recovery via ROM Manager or even Safestrap.
Does anyone have an idea how to fix this? Or is it not revertible and do i have to live with Stock 2.3.6?
Click to expand...
Click to collapse
try flashing 906 with fastboot.exe
see my Unbrick Moto device with moto-fastboot.exe

Gives me "Preflash validation failure" too.
Code:
E:\droid>moto-fastboot.exe devices
0910E0550801501A fastboot
E:\droid>moto-fastboot.exe flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.525s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
E:\droid>moto-fastboot.exe flash recovery recovery.img
sending 'recovery' (9216 KB)... OKAY [ 0.588s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
E:\droid>moto-fastboot.exe flash preinstall preinstall.img
sending 'preinstall' (262144 KB)... OKAY [ 16.434s]
writing 'preinstall'... OKAY [ 15.184s]
sending 'preinstall' (229376 KB)... OKAY [ 14.373s]
writing 'preinstall'... OKAY [ 11.762s]
E:\droid>moto-fastboot.exe flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.426s]
writing 'system'... OKAY [ 15.193s]
sending 'system' (175872 KB)... OKAY [ 11.021s]
writing 'system'... OKAY [ 9.058s]
E:\droid>moto-fastboot.exe -w
erasing 'userdata'... OKAY [ 0.013s]
erasing 'cache'... OKAY [ 3.935s]
E:\droid>

read [Q] black screen on the xt883 rom - droid 3 (xt862)
maybe something there will help
.
you can root current version? verified with root checker? what safestrap versions have you tried?
have you tried Droid 3 bootstrap?

sd_shadow said:
read [Q] black screen on the xt883 rom - droid 3 (xt862)
maybe something there will help
.
you can root current version? verified with root checker? what safestrap versions have you tried?
have you tried Droid 3 bootstrap?
Click to expand...
Click to collapse
I may have a similar issue. In my 2+ years of using my Droid 3, I have messed up the stock ROM partition to an unbootable state. (Of course I have working Safestrap.) I can use custom ROM slots very well - I have Avatar running in slot 1 and minimoto in slot 3 and can switch between them at will.
I now want to clean up this phone. Safestrap (I guess by design) doesn't let me flash anything to the stock ROM slot. Somewhere along the way, my Droid 3 seems to be happy with fewer computers for adb access. I have one computer where adb is happy with this phone. Even on that computer, I can't get RDSlite 5.5 to work - it does not show the device when it is in fastboot mode. I would try the fastboot.exe method tonight.

kernelguy said:
I may have a similar issue. In my 2+ years of using my Droid 3, I have messed up the stock ROM partition to an unbootable state. (Of course I have working Safestrap.) I can use custom ROM slots very well - I have Avatar running in slot 1 and minimoto in slot 3 and can switch between them at will.
I now want to clean up this phone. Safestrap (I guess by design) doesn't let me flash anything to the stock ROM slot.
Click to expand...
Click to collapse
You can restore a nandroid to stock rom, try mine Stock Nandroids
---------- Post added at 11:31 AM ---------- Previous post was at 11:25 AM ----------
kernelguy said:
Somewhere along the way, my Droid 3 seems to be happy with fewer computers for adb access. I have one computer where adb is happy with this phone. Even on that computer, I can't get RDSlite 5.5 to work - it does not show the device when it is in fastboot mode. I would try the fastboot.exe method tonight.
Click to expand...
Click to collapse
Likely it's window that does not like your Droid 3 see my Installing Drivers and Driver errors
and Flash xml recovery files (Stock Rom) with RSD Lite
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
several other flashing methods in my list under Stock Rom but I would try the nandroid first

[Q] Need help for bricked Razr i / firmware links

Hello Forum,
as a newbie in Razr i I tried today to unblock my Bootloader and of course made an error during this
I downloaded the file "RAZRi_Root_Linux.zip" from user "mattlgrof".
Unpacked it and run the file "Root.sh".... yes I know. I have read the HowTo, but ...I don't know what I thought!?
And of course the shell said reboot and the phone stuck on the red Motorola logo
Looking into the file, I saw that the last command executed was:
"sudo $fastboot flash boot ./files/razr_i_boot_insecured.img"
And the output was:
"< waiting for device >
sending 'boot' (11264 KB)...
OKAY [ 1.657s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 2.021s
rebooting...
finished. total time: 0.240s
Phone is rebooting please dont touch anything."
As I have read until know I could restore the phone by installing a astock firmware via RSD, right?
But in the last 5! hours I couldn't find a valid link for a firmware download.
So my question/request are:
- Can I solve this by installing a stock ROM via RSD?
- Can someone provide me an link to a firmware download?
The specs of my phone:
- European ( germany), unbranded
- OTA update to JB 4.1.2
- previously rooted with windows using a "android trick", I don't exactl remember how
If you need more information, please ask.
Thank you in advance, and have a nice day.
Kind regards.
giderBey

Since you are German, you can follow this how-to: http://www.android-hilfe.de/anleitu...owto-razr-i-mit-rsd-lite-flashen-windows.html
It also includes mirrors to the firmware
Once you are back to stock, you can use this root method: http://forum.xda-developers.com/showthread.php?t=2541398 and no bootloader unlock is needed.

Gra-l09c432b399

http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2199/g1604/v100315/f1/full/update.zip

Thnx for the tip!!
Downloaded with Firmware Finder.

Have you modified EMUI logo or it's a theme, or it's stock?

eldin_96 said:
Have you modified EMUI logo or it's a theme, or it's stock?
Click to expand...
Click to collapse
is theme

TOP! runs smooth...
Thanks for information, update runs smooth and without any problem.

Anyone tryed to root it yet?

Huaway said:
Anyone tryed to root it yet?
Click to expand...
Click to collapse
I just wanted to write about it. I cannot root the firmware, or more precisely I cannot flash TWRP. All I can get is
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (26226 KB)...
OKAY [ 1.209s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.225s
Any ideas?

yokozuna said:
I just wanted to write about it. I cannot root the firmware, or more precisely I cannot flash TWRP. All I can get is
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (26226 KB)...
OKAY [ 1.209s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.225s
Any ideas?
Click to expand...
Click to collapse
I have the exact same problem, installed this firmware via dload method, it also updated modem version, did factory reset and tried to flash TWRP and I got that problem.. Tried to relock bootloader, it didnt work.. When I run the command it says my bootloader is unlocked. I think we have some issues with this firmware. lol

Try to unlock your bootloader again.

erayrafet said:
Try to unlock your bootloader again.
Click to expand...
Click to collapse
I have tried, no success whatsoever.

eldin_96 said:
I have tried, no success whatsoever.
Click to expand...
Click to collapse
Very strange. I had same problem with same message " FAILED (remote: Command not allowed)", but, when I re-unlocked the bootloader , I resolved the problem.

In my case it did not work so I guess that in my case the ROM cannot be rooted but I have to write some impressions about the ROM compared to v.403 (contrary to its number v.403 is around 4 months EARLIER than b.399).
I write about my case only. Your mileage can vary.
v.399 feels less swift than v.403 (but ain’t bad anyway), moreover it brought me some games that I do not need because I do not play any games with my P8 (Dragon Mania, Puzzle Pets, Spider-Man, there is an app called Vmall). Pity that the ROM is not clean but never mind.
There is one thing that makes me love this ROM, the battery life is simply second to none. I talk around 60-90 minutes every day as well as I videocall several minutes daily (Skype Lite), send messages to my friends (WhatsApp), surf pretty intensively, check my email, use my bank app, and use some other apps. With v.403 I had to charge my P8 every morning. With v.399 if I charge my smartphone in the morning I can charge it next day but in the evening, or if I use it less intensively even after 2 days. Maybe the ROM is so good, or maybe it blocked some battery hungry apps that needed root acccess (I used Battery Charge Limit, AdAway, L-Speed, System App Remover, and Magisk with some audio modules).
I will call a spade a spade, it will be very nice if I will be able to root my P8 but if not I will not grumble anyway.

Hi! I try to reunlock bootloader, but I can't flash twrp. I try versions 3.0.2, 3.1.0 and 3.1.1
"Error data transfer"

anyone can post link ? the links are dead

[Stock ROM][Applied 1 October OTA Update]Trying to get TWRP custom recovery flashed

Hello. So, I got my Moto G5s Plus around the last week of October or beginning of November. It is a great device, but I learned about the camera flaws by Motorola and unlocked the bootloader to fix it by following this XDA thread here for camera fixing and the Chromatix mod. I learned that I could edit build.prop without flashing the TWRP recovery but using it temporarily following the guide here. build.prop edit would enable cam2api for third party cam apps. The Chromatix mod threads/posts were for the G5 Plus, which I didn't realize at the time and didn't backup original Chromatix files. However, That went successfully and I could still use my phone with better camera quality. Note that prior to doing this fix and before unlocking the bootloader (I believe) I had updated my device from Nougat to Oreo. My bootloader is indeed unlocked.
Now, when the 1 October OTA Update came I was hesitent because I had came across some rooting/custom rom/custom recovery/mod articles while learning about unlocking the bootloader. Yet and before reading more to get educated on this, I applied the update to my phone. I was hoping it wouldn't brick it or that it would fail if it didn't work. It failed (because of the modification on the stock ROM) at the last bit of the update and rebooted my phone. My phone worked and it let me know nothing was changed by the failed update. However, my phone since then has shown as if it is up-to-date in system updates.
So, basically I have been trying to flash TWRP for my Moto G5s Plus after that was done. I want to see about backing up my stock ROM (or the most important parts) possibly getting a good custom ROM installed (which I believe they have their own official Android security updates from Google?). However flashing TWRP hasn't worked. I get the following in PowerShell (cmd):
PS C:\Android SDK\platform-tools> fastboot flash recovery twrp.img
Sending 'recovery' (10236 KB) OKAY [ 0.407s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.172s]
Finished. Total time: 0.594s
Note that I renamed twrp-3.1.1-sanders.img to twrp.img as it was a suggestion I followed at the time. This I heard is normal, but when I go to Recovery Mode on my phone I see this:
Start Up Failed:
Repair message stuff
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
~~~
Error: failed to load kernel!
~~~
I also tried to find the latest stock ROM to flash because I believe I read I may need to do that. I found SANDERS_RETAIL_8.1.0_OPSS28.65-36-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and tried to use "Apply update from ADB" from the stock Recovery (when it was working normally after powering off and not with kernel errors because of this). It failed.
I couldn't find the right answer(s). Thank you to anyone that can help me or others who have done the same!!
EDIT (11/19/2018):
So, last night I tried wiping my data in stock recovery and then I tried to do this again. It still didn't work. I also tried to apply the same stock zip as well as boot_magisk.img from this thread here https://forum.xda-developers.com/moto-g5s-plus/development/stock-kernel-prerooted-8-1-0-t3863301.
PS C:\Android SDK\platform-tools> fastboot flash boot boot_magisk.img
Sending 'boot' (10702 KB) OKAY [ 0.391s]
Writing 'boot' (bootloader) Image not signed or corrupt
OKAY [ 0.141s]
Finished. Total time: 0.563s
It all still fails. However, now when I boot up my phone it goes straight to the bootloader instead of loading the OS right away. I can select START to start the phone normally from there.

I got all this resolved through XDA's Telegram group (& specific group for G5s Plus/sanders)! I have TWRP (Treble) and custom rom working after getting an official stock rom from them flashed using fastboot commands!
I don't know if I should or a mod can close/erase this thread now?

Try typing fastboot oem fb_mode_clear while in bootloader

Coala990 said:
Try typing fastboot oem fb_mode_clear while in bootloader
Click to expand...
Click to collapse
Thanks for the suggestion/tip. I will probably try that if I reflash twrp treble (or another version of twrp for Sanders) again. This has been resolved.