Hi there,
Trying to get custom recovery on a defy 850mhz model (Telstra Australia)
TL;DR: Loading a custom recovery gives a black screen when you attempt to boot into recovery from the app. When booting into recovery from power off, it takes you to the motorola one.
More detail:
PaY did a pretty good job with his desire roms, so i decided to give them a shot for defy. Instructions below that i followed:
PaY87 said:
README - Step by step flashing guide:
Please do this steps also if you come from v1.2 or from any other ROM.
You can go to step 5 if you already flashed UK 3.4.2-117 SBF, rooted and installed clockwork recovery or have ROM v1.4 or higher.
1.) Wipe your phone in recovery mode
2.) Flash UK 3.4.2-117 Motorola SBF with RSD Lite in bootloader mode
(The sbf is packed in a rar image just extract it and then you get the sbf. The problem is, that the filename is to long and windows cuts off the extension "rar" on some PCs. Be sure to unpack the download else RSD Lite don't can flash it because it is a rar and not a sbf. )
3.) Enable ADB in the settings and root your device with SuperOneClickRoot for Froyo. Then do a reboot.
4.) Disable ADB and install clockwork recovery image
5.) Put the ROM.zip to your SD Root and boot into clockwork recovery
6.) Flash the ZIP + reboot and enjoy
When everything fails:
-If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse
So i had the stock telstra rom, used z4root and loaded the recovery that was linked to above. This worked, and i was going to just flash the new rom but decided to follow the instructions.
Then proceded to follow the instructions above, loading that 3.4.2 rom. Flashed it, rooted with superoneclick and then loaded recovery again.
Then when i pressed boot into recovery, it simply gives a black screen. The screen is on, you can see the backlight, it just has nothing.
I tried the other recovery made by another user, the latest clockworkmod, with the same apk tool for installing recovery. Same thing again.
Holding vol down + power makes it boot into the motorola recovery.
Reflashed the rom several times, tried z4root instead, no idea why it isnt working.
I guess im just spoiled with Unrevoked when it comes to my own phone.
disabled usb debugging?
had the same problem, disabe usb debugging solved it for me thanks !
I'm on telstra as well, like the other replies disable usb debugging then it will work.
Sent from my MB525 using XDA App
Related
earlier, i managed to brick my defy by first deleting google talk and then using terminal emulator to push the google talk back in system apps.
after flashing a stock sbf through rsdlite, i got my phone working again. my problem started when i flashed another rom (followed instructions from pay's rom tutorial). i was able to flash the sbf file, then root using superoneclick, then install clockwork mod (downloaded the apk and installed manually). i rebooted after cmw install just to be sure and when rebooting to cm recovery only a blank screen shows. i was puzzled as on m original 2.51 rom before, the clockworkmod recovery screen shows up when i reboot in recovery. i tried installing other stock roms (nordic froyo), the problem still persists (blank screen). it also seems to have affected the standard recovery (volume down+power), after showing the exclamation mark with the android guy, no matter where i press on the screen nothing happens, whereas before pressing on the lower right hand screen brings up the menu. what did i screw up this time?
i needed cm recovery to work for i can't flash custom roms without it. any help would be much appreciated. thanks
I had the same problem with clockworkmod so I installed the 2nd init recovery http://forum.xda-developers.com/showthread.php?t=1032212 and used clockwork mod from its recovery menu.
I think the problem was caused by installing clockwork mod with USB debugging enabled.
namzuf9 said:
I had the same problem with clockworkmod so I installed the 2nd init recovery http://forum.xda-developers.com/showthread.php?t=1032212 and used clockwork mod from its recovery menu.
I think the problem was caused by installing clockwork mod with USB debugging enabled.
Click to expand...
Click to collapse
so should i try uninstalling clockworkmod and install again? this time un-enabled usb debugging?
what exactly is a 2nd init recovery?do i just flash this over the existing sbf?
sorry for the questions, am still a newbie when flashing defy.
to access stock recovery when the android appears press vol down + up at the same time, my touch screen didnt work in recovery before either
once you can access stock recovery wipe data/factory reset, and flash a new ROM fresh
Hi,
what i did so far:
1) I came from 2.1 Eclair original Stock ROM from T-Mobile Germany (JRDNEM_U3_2.21.0 Blur Tmobile --OTA updated to--> JRDNEM_U3_2.51.1 Blur Tmobile)
2) Replaced Stock Rom with Nordic 3.4.2-177-005 by using this Guide: [FAQ] Cyanogenmod 7 by Quarx [7) How to install CM7 and keep downgrade-ability? (Froyo or Eclair]
3) Downgrade to my original Backup of Eclair with Nandroid/fixed SBF from the Guide above.
4) Installed Nordic 3.4.2-177-005 ROM without CM (Nandroid/Fixed SBF)
5) Finally installed Leaked 4.5.1_85 / android 2.3.3 / Orange GB (Nanbroid/Fixed SBF)
Now if I want to use Custom Recovery its not working anymore... My Android 2.3.3 Device is Rooted, System Recovery said "Installation complete" if I tab on Install Recovery System. But if I tab Recovery Boot the Device Reboots but stucks with an Black Screen with Backlight on ....
I read some more posts on the 4.5.1_85 rom and installed the bootmenu_v0.8.6.update.zip via Stock Backup (hold VolDown while switching on, press VolUp and VolDown simultaniusly after Android Logo apeares).
But that "fix" doesn´t work for me...
Seems that my preffered method to recover my old Eclair doesn't work anymore... How to get my old Nandroid Backup back?
If I turn my Device on, it shows first a white Motorola Icon (like in Eclair) than after a short time it shows the new red Motorola Icon with animations... and starts the working 4.5.1_85 rom ... i can launch the Bootloader for RSD (VolUp) or Stock-Recovery (VolDown) but not custom Recovery...
Greetings HH
[Fixed] Back to Stock
Ok,
took me a while, but now I'm back to Stock Eclair^^
Here is what worked for me:
- install 2ndInit for Defy from the Market
- re install Bootloader via 2ndInit (may not be nessesary)
- boot normal ... than deinstall bootloader via 2ndInit
- reboot
- install Recovery System via System Recovery (Custom Recovery)
- boot Recovery System (now works again)
- restore Backup from 2.1
- replace fixed sbf with rsd (restart, VolUP...)
Greetings HH
Seams for me, that System Recovery (Custom Recovery) App is not working with 2ndInit + Gingerbreed^^
I successfully rooted my phone using the superoneclick method through the computer. I then followed the video guide and downloaded the system recovery app which allows you to install a custom recovery.. i clicked on the button and asked to accept root access which I allowed.. I then rebooted my phone and went into recovery.. no custom recovery was installed.. so i booted my phone back and phone started up properly.. I then did the process once again and after booting into recovery I again noticed that the factory recovery was still on the phone. I then rebooted the phone again and thats when the constant reboot happened..
I did a wipe from the factory recovery and still not success..
I'm having trouble finding a suitable rom i can rename update.zip and attempt to install a rom that way..
also .. what are my options..
NOTE: This is the recovery installation method I used http://forum.xda-developers.com/showthread.php?t=875233
NOTE: While in the stock recovery on the bottom of the screen this is what it reads.
E:Can't mount CACHE:recovery/command
E:Can't mount CACHE:recovery/caller
E:Can't mount CACHE:recovery/log
.
One thing: the installation of custom recovery is not expected to erase stock recovery; they can coexist. In order to enter stock recovery you switch on with volume down pressed, in order to enter custom recovery you press volume down while booting and the led turns blue.
In your present situation I think you are forced to flash a full sbf with rsdlite (fro windows) or with sbf_flash (from linux). You can find plenty of them in a sticky thread.
You did a factory wipe after a boot loop...... you have to flash full sbf.
patroclo7 said:
One thing: the installation of custom recovery is not expected to erase stock recovery; they can coexist. In order to enter stock recovery you switch on with volume down pressed, in order to enter custom recovery you press volume down while booting and the led turns blue.
In your present situation I think you are forced to flash a full sbf with rsdlite (fro windows) or with sbf_flash (from linux). You can find plenty of them in a sticky thread.
Click to expand...
Click to collapse
I understand that while holding down the down volume button then pressing the power button will get you into the stock recovery..
but can you break it down in the same simple manner on how to get into the custom rom?
I held the down volume button after pressing the power button and no light turned on..
one2wan said:
You did a factory wipe after a boot loop...... you have to flash full sbf.
Click to expand...
Click to collapse
Yes I did.. didn't know what else to do.. wasn't near a computer was at work..
is an sbf file same as a zip file for rom?
With boot loop, have to test wipe cache/Dalvik cache first from custom recovery. If nok, test apply ZIP. If nok so ok, full flash is needed... You can't solve a boot loop with wipe from factory recovery...
But now, before flash full sbf, do a wipe from factory recovery ! It's better.
And no ! SBF isn't as ZIP ROM !
SBF is applied via bootloader and ZIP is applied via recovery. It's definitively not the same thing ! You have to understand that before customize your Defy !
one2wan said:
With boot loop, have to test wipe cache/Dalvik cache first from custom recovery. If nok, test apply ZIP. If nok so ok, full flash is needed... You can't solve a boot loop with wipe from factory recovery...
But now, before flash full sbf, do a wipe from factory recovery ! It's better.
And no ! SBF isn't as ZIP ROM !
SBF is applied via bootloader and ZIP is applied via recovery. It's definitively not the same thing ! You have to understand that before customize your Defy !
Click to expand...
Click to collapse
I see.. I can't seem to get into the custom recovery.. hold down volume button and blue light doesn't turn on and nothing else happens.. i get sent back to factory recovery..
I have done a full wipe from the factory recovery and downloaded a file from here http://and-developers.com/sbf:defy but after running rsdlite and selecting the file.. nothing happens.. the phone still shows its in recovery and nothing happens after pressing start on the program..
Have you entered the bootloader to flash the sbf?!
Sent from my MB525 using XDA App
Make sure you turn on your defy holding the up volume (not down) and power button to enter bootloader. Then you can use usb + rsdlite to flash a new sbf file (not zip rom!)
You have to know what custom recovery you installed. From your post above. You had installed the bootstrap recovery which is an app to enter the recovery. This bootstrap recovery doesn't have the blue light when you booting the phone. Only 2nd-init will have the blue light in booting and pressing volume down goes to boot menu.
1) you don't have to wipe anything for installing bootstrap recovery nor the 2nd-init.
2) if bootstrap recovery is installed, launch it from the app provided.
3) stock recovery don't flash custom update.zip.
4) I would suggest installing 2nd-init as it works even if phone is messed up.
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.3 - XDA Premium
SpookyAwol said:
Make sure you turn on your defy holding the up volume (not down) and power button to enter bootloader. Then you can use usb + rsdlite to flash a new sbf file (not zip rom!)
Click to expand...
Click to collapse
Thanks..I managed to get into the bootloader, I loaded up rsdlite 4.9 and found a sbf file (had to rename it from gz?)
After clicking on start it says
"Failed flash process. phone connected"
Just realized I have to extract the sbf from the gz files ... try when I get home.
Sent from my MB501 using XDA App
I get an error from rsdlite when I use the sbf file for T-Mobile 2.2.1 it won't flash. I used the German and UK sbf files and does work but won't allow me to have internet.
Sent from my MB501 using XDA App
I finally managed to install a working SBC and am now running cyanogen but noticed I now have only. 128mb of internal memory???
Sent from my MB525 using Tapatalk
My phone stuck at mi logo even the recovery can't be opened
I was using cynogen 12.1 and then i download its update after that it sticks at mi logo
Unable to open recovery
Thanks in advance help as soon as possible
Don't worry, if you can enter fastboot, you can fix it. Follow this guide http://en.miui.com/forum.php?mod=viewthread&tid=23234&page=1#pid459792 If you do everything right, stock miui5 or miui6 will be installed, depends what you choose. I recommend you to download v45 miui5, I have used that version few times. You will have to install custom recovery and root again if you want a custom rom later. If the Miflash program does not recognize your phone in fastboot mode, then download and install these drivers, I think it should work. http://forum.xda-developers.com/redmi-1s/general/tool-adb-drivers-redmi-1s-t2904411
You need not go back to stock miui. If you update the rom, the recovery should still be intake, unless you did something to it, which is quite unlikely unless you selected to flash it as well.
Make sure your phone is completely off. Remove battery and insert back. Pressing the vol - and power button should boot your phone into the recovery(if i rmb correctly). From there, reflash the first cm12.1, not the update which you download, and it should boot fine again. Preferably, go for a clean install, unless you have data which u haven't backup, then go for the first.
If you flash a recovery and if indeed your recovery is corrupted, just reflash using adb.
Flashing a rom should not cause any damage to your recovery as it doesn't touch your recovery files.
Hello everyone,
This morning, I wanted to recover OxygenOS on my Oneplus3. I'm currently running Cyanogenmod 13.
I used the following guide: "[GUIDE] How to Unroot your OnePlus 3 / 3T and go back completely to stock" (Since I'm a newb, I can't post the link. But Google will get you there)
I booted into fastboot, issued the fastboot flash recovery recovery_op3.img and fastboot oem lock commands from my Linux termina, and rebooted in recovery mode.
In recovery mode, I then erased the cache and all that, selected the "Upgrade android from USB" and issued the adb sideload ota.zip command. This is where my problems began.
After running the command, I got the error "error: protocol fault (no status)". I tried to look this error up, but couldn't find useful information.
I started to panic a bit, fearing that my phone would be bricked. However, after booting back into fastboot mode, unlocking OEM, and rebooting, my phone would boot back into Cyanogenmod 13 (A clean install).
So now I don't have a bricked phone. However, I really would like to go back to OxygenOS, so my question is whether anyone knows how to solve my problem.
Summary:
Running Linux (Debian 8) on my PC;
Running Cyanogenmod13 on my Phone;
Want to recover OxygenOS, but adb sideload gave me "error: protocol fault (no status)";
Tried running the adb sideload command as root, however that did not work;
Can still use the Cyanogenmod13.
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Tybalt said:
I've seen that error once before. I had to disconnect the phone, kill the ADB process, reconnect the phone and restart ADB to get it to work.
That worked for me. Hope that helps.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for responding.
I forgot to mention that I also tried killing the adb process several times, using the adb kill-server command and by killing the process sending SIGKILL.
Another thing I tried was using another Debian machine, which is my laptop. Still, those things did not solve my issue.
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
null0seven said:
Backup youre working rom..
First, you need unlocked bootloader.
1.Flash twrp 3.0.4.1 or twrp-3.1.0 x v.26 blu_spark. Reboot to recovery.
2.Clean flash (wipe data-dalvik-system-cache) Oxygen OS, since you come from a custom rom. Flash SuperSu or Magisk, if you want root. Reflash recovery. Reboot to recovery.
If youre phone does not boot in recovery, press Power till phone vibrates. Press vol. down & choose:
1. Select Bootloader. Flash recovery from PC. Safest way to flash recovery.
or
2.Select recovery. Reflash recovery. Reboot recovery.
After you are sure that you got a working recovery reboot to system.
Click to expand...
Click to collapse
Thanks for responding.
Since I don't understand everything yet, I will spend this evening looking up everything in detail, before I start giving it another try. Do you perhaps know of a tutorial about this specific situation? I don't want to bother you by questioning everything you stated in your instructions. They seem clear enough to be able to be looked up on Google :laugh:
drmuruga said:
Never relock your boot loader, most bricks are due to relocking.
Flash twrp, flash oxygen os ,boot, enable everything,if you want complete stock, flash stock recovery ,flash oxygen os boot to complete stock os.
Click to expand...
Click to collapse
Thanks for responding.
By the steps after "if you want complete stock", do you mean that I should keep the bootloader unlocked, and then perform the same steps as in the tutorial that I used?
EDIT:
@ null0seven: I found these steps online as I was looking up some things you said (I don't have much time since I will celebrate eastern with my family today)
Rooted Users or users with ROMs other than OxygenOS having new bootloader (Official CM 13,CM 13 Based ROMs dated later than 04 June 2016,H2OS Marshmallow)
Step 1 :- Download the OxygenOS 3.0.2 full zip from the top of the post.
Step 2 :- Boot into TWRP.Wipe Dalvik,System,Data and Cache.After that,flash OxygenOS 3.0.2.
Step 3 :- [OPTIONAL] Flash SuperSU from here :- https://www.androidfilehost.com/?fid=24459283995297946
Step 4 -> Reboot System.
Of course, this is about an old version of OxygenOS. But it looks the same as you said.
I think this, combined with your instructions, will make it a bit clearer. Still one question: What do you mean exactly by flashing?
dvbeck
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733