[Q] Bootloader Options Boot Into OS - Droid RAZR M Q&A, Help & Troubleshooting

Hey everyone,
I'm going insane. I just purchased this phone. It's stuck on Android 4.1.1. I can't seem to get it to update and I'm not trying to root, as this is a gift for a friend. After doing research, I found out about the RSD Lite 6.1.5 tool and fastboot to flash over an updated firmware. However, there's another problem now. I was able to successfully get the bootloader up (volume +, -, and power button) and select fastboot. This worked the first time. RSD Lite didn't recognize my phone, even with Motorola Device Manager and drivers installed. So I thought lets reboot the PC and the phone. Well, the phone can get to the options of fastboot, recovery, factory, etc., but despite selecting any of them, it just boots into the Android system. I've factory restored within the system 3 times and still can't get fastboot, or any of the other options, to work.
Any suggestions?

Try RSD flashing the KitKat sbf and unlocking the bootloader. A lot of the time, the carrier chooses to lock the bootloader options when the bootloader is locked itself.
Sent from my DROID RAZR M using XDA Free mobile app

Related

[Q] Defy stick on boot logo

hello fellows, tried to flash ms2ginger3.0 and the device got stuck on boot logo, boot menu wont load, and stock recovery (vol down + power button) doesn't work either. Tried also to attend to the operator, but they won't fix an none stock version.
any suggestions?
use rsd lite and flash a new sbf to it.
In case you don't know how to flash a new sbf with RSD Lite, here's a quick tutorial:
1) Install the Motorola drivers and RSD Lite on your computer. See this guide for installing Moto drivers and RSD Lite:
http://forum.xda-developers.com/showthread.php?t=853674
2) Download the sbf file that you want to flash, and save it to your PC. Many sbf files can be found here: http://forum.xda-developers.com/showthread.php?t=966537 WARNING: If you flash a full stock SBF file, in most cases you will lose the ability to downgrade to earlier firmware versions. NEVER flash a full stock SBF file with a higher Android version than 2.2 (Froyo). Any stock firmware with Android version 2.3 or higher is made for the DEFY+, which has different camera hardware than the DEFY. If you flash the stock DEFY+ firmware, your camera will be broken and you won’t be able to downgrade back to Froyo again.
3) Make sure the phone battery is fully charged. Power off your phone, then hold in the volume+ button and the power button at the same time. After about 5 seconds, release the buttons. The bootloader should display – it will show the version and a battery check. (If that doesn’t work, pull the battery, then put it back in while holding the volume+ and power buttons.)
4) Start RSD Lite on your computer, then connect the phone with a USB cable. In RSD Lite, the Status column should say “Connected…”. Click on that, and some information about your phone should show up under Device Properties. Next, click the “…” button and browse to select the SBF file that you want to install. After opening it, information about the file should show up under File Properties. Then click “Start” and wait for the flashing process to complete. Wait until the phone has fully rebooted and RSD Lite says “Pass” before closing RSD Lite and disconnecting the USB cable. As an extra precaution, I usually power off the phone before disconnecting the cable.
Good luck!
Thank you guys, just reallized the combination to stock recovery is (power botton + volup) now sbf Froyo.
help me out
i too faced the same issue.My phone is dead pls help me out
Hi
I installed CM7.1 in my defy and worked good but no market applications.
To install those i did something in boot loader mode and i think i deleted something and gave reboot dats all but after that my mobile shows only google.
I can able to go in boot mode.
Follwing options in boot mode:
2nd-int
2nd-boot
normal
But in recovery mode Follwing options availiable;
Latest recovery
Stable recovery
stock recovery
reboot
i tried all
result: no such file found
When entered into stock mode
result:
the recovery gets stuck with the android man and an exclamation mark.
While i put charge it showing questionmark inside the battery logo.
But i can able to enter into boot mode.
But without put charge i cant able to power on:
Please help me out i cant use my phone.
please guys help me.
[email protected]
madhavandeffy said:
Latest recovery
Stable recovery
stock recovery
reboot
i tried all
result: no such file found
Click to expand...
Click to collapse
Do you get the "no such file found" error as soon as you select a recovery option, or does the error happen later?
If all else fails, just flash a new sbf using RSD Lite. (See my previous post, above.) If you're planning to install CM7 again, I recommend using the 3.4.2-179-2 CEE DEBLUR sbf. Then follow this guide to install CM7 with working google apps: http://forum.xda-developers.com/showthread.php?t=1065798

Unroot(Lock of the Bootloader) Huawei P9 Lite

Hello,
I just bought this phone and I would like to know if it is possible to fully unroot the phone after unlocking bootloader and rooting. Cconcretely if there is a way how to lock bootloader the way how stock is (not relocked message etc.) so it could be send to assistance without problems.
Thank you.
1st, extract update app with huawei update extractor. go to custom recovery, flash stock boot IMG and stock recovery IMG. Power off, use three button dload method, reboot, when booting press vol up for three second, now you are in e-recovery. Press shutdown. Press and hold power and vol up for stock recovery. Do factory reset. If need do the factory reset 2/3 times. Now you are with locked bootloader.
But, before send to service center. Recheck OEM unlocked in developer section.
You can use this method at any time, any situation.
You can do any experiment with your device now.
Sent from my NEM-L21 using Tapatalk

P8 Lite turns itself off while booting to TWRP/CWM recovery

LATE EDIT: solved, read bottom of this topic for solution
Hi, so I have a P8 Lite and after properly unlocking the bootloader, I flashed TWRP (versions/ports found on XDA for P8 lite).
After using fastboot fastboot flash recovery twrp.img properly, it outputs OK, indicating it successfully flashed.
Now, assuming all went fine, I tried booting into recovery with powerbutton and volume up, after a few seconds only it turned off, the whole device just shuts itself down.
I then noticed it'd go into Huawei eRecovery when you keep holding it, so I just briefly pressed both keys until it started up, immediately released, and it still failed to boot into recovery.
To make sure I made no mistakes with triggering the recovery boot, I used adb to perform ''adb reboot recovery'' and so it attempted to boot into it, resulting yet again in the same black screen shortly after the Huawei (powered by android) logo, where that black screen is actually the device shutting itself down.
So the conclusion I draw is that the recovery is broken after installing it, the question is how. I'm not a novice to this kind of stuff, as you might have noticed, but still I cannot think of what went wrong, as my bootloader is successfully unlocked through the EMUI method, and I made proper use of fastboot to flash recovery, after which it tells me it succeeded, using the proper recovery for this device.
To double check I also installed the CWM recovery released for the P8 Lite (https://forum.xda-developers.com/p8...overy-clockwork-mod-recovery-cm-12-1-t3342209), as TWRP's for it (multiple versions/releases..) failed thus far, and also with CWM the same happens.
I really want to proceed flashing recovery to then root the phone and install a custom ROM, so any help or ideas what the cause might be, will be appreciated, or anyone that encountered the same problem!
SOLVED (was too lazy to post on time, i fixed it shortly after posting this).
The problem was that I flashed a bad recovery, basically the ALE-L21 has different TWRP versions advertised in the P8 lite section, i happened to choose a not too good one, it may have even been one that didnt belong to my model (like P8 lite generation year), not sure as the section is co-shared between P8 lite model generations, this mistake is easily made.
If you have this issue, just keep trying additional (TWRP) recoveries, the subsequent 2 versions from different publishers that I tried were working fine and the issue stopped.

How do I unbrick a bricked P9Lite with a locked bootloader and without USB debugging?

Greetings all,
I recently got a P9 Lite but I bricked it trying to install a newer firmware on it (tried to go from 6.0 to 7.0). I've read various unbricking guides over the past two days but to no avail. I'd like to know what my options are at this point and if it is possible to unbrick it and bring it back to a usable state even if on a different rom.
How I got here:
The firmware that came with my phone was L23C605B120. I tried to update it to L23C605B362 and downloaded 2 zips (update.zip and update_data_full_VNS-L23_hw_la.zip). I unzipped update.zip into the dload folder of my sdcard and updated it via the dialer. The update installed and my device rebooted but now to this bootloop state.
What I can do:
If booting up normally, I end up in Huawei's erecovery. I can also boot to recovery mode where I can either "Wipe data/factory reset" or "Wipe cache partition". I can boot to fastboot & rescue mode but it says my phone and frp are locked. When pushing all three buttons I can boot to where the phone will attempt to update with the dload folder in the sd card again.
Stuff I have tried:
In erecovery when I select "download latest version and recovery", I can connect to my wifi but it always fails at "Getting package info failed". In recovery mode the factory reset fails and I don't think wiping the cache partition did anything meaningful. In fastboot & rescue mode it tells me to open HiSuite where there is a recover option but clicking it says "Your device is not supported for system recovery". I can see my device using fastboot on my computer but it seems almost useless here since its useful commands fail with "command not allowed" probably because my bootloader is locked. On my computer I installed the USB drivers adb needs and rebooted but adb cannot see my device presumably because I hadn't enabled USB debugging prior to getting bricked. At this point I'm downloading different roms to my sdcard and trying to flash with the 3 buttons method but pretty much all of them fail at 5% or 7% including the rom with the same version that my phone came with. The only one that doesn't fail at 5% or 7% is the rom I tried to flash that bricked my phone which fails at 99%.
So I cannot flash TWRP because my bootloader is locked, I cannot unlock my bootloader because adb cannot see my device, adb cannot see my device because I probably never enabled USB debugging and I cannot enable USB debugging because I cannot boot to the OS. At this point my only option seems to be trying to flash a working rom with my sdcard but I have yet to find one that works.
Where should I go from here and what are my options at this point? Is there a specific rom I should be looking for? Is there some intermediate downgrade rom I have to flash or is there a way to undo the update I just did? Is there a way to somehow enable USB debugging or to unlock my bootloader without it (perhaps via an exploit)?
Any help would be much appreciated!
TL;DR: title

Install of LOS, hit snag at TWRP update

Hey everyone,
I was running through the process of installing LOS 15.1 official when I hit a snag. I unlocked the bootloader, installed the Universal O bootloader, and was in the process of updating my version of TWRP. After flashing the image to recovery, I noticed that the TWRP version hadn't updated to the new one. I tried rebooting and that's when the problem started. Now, when I hit power + volume up, I get the ZTE powered by android screen, then 3 flashes of the notification light, and then it powers off. If I hit the power button, it sits on that same ZTE splash screen for what seems like indefinitely. I can't figure out how to get back into TWRP.
Any help is greatly appreciated
You can try flashing twrp via the twrp app
Hey!
Try to reboot the phone, press volume button to get the selection menu and reboot to fastboot.
connect the phone to your PC and using the a7toolkit flash the recovery again.
I think I did exactly the same thing as you and I fixed it this way
daaper said:
I unlocked the bootloader, installed the Universal O bootloader, and was in the process of updating my version of TWRP.
Click to expand...
Click to collapse
I assume you are coming from stock because you're unlocking your bootloader. I have a question about this process, did you install an older twrp first before flashing the O bootloader?
Chris axon 7 said:
You can try flashing twrp via the twrp app
Click to expand...
Click to collapse
I'm not sure how to do this if my phone won't boot.
rzarectha said:
Hey!
Try to reboot the phone, press volume button to get the selection menu and reboot to fastboot.
connect the phone to your PC and using the a7toolkit flash the recovery again.
I think I did exactly the same thing as you and I fixed it this way
Click to expand...
Click to collapse
When I connect my phone to my computer, none of the toolkits I've tried can see it. It comes up as "Handset Diagnostic Interface (DFU) (Com4)". When I attempt to enter EDL mode with volume +, volume -, and power I don't get a flashing LED, just a solid one. As near as I can tell, this means my phone is hardbricked. I've got an EDL cable on order to hopefully fix this, but it's going to take almost a month to get here :crying:
tprfd said:
I assume you are coming from stock because you're unlocking your bootloader. I have a question about this process, did you install an older twrp first before flashing the O bootloader?
Click to expand...
Click to collapse
Yes, the toolkit I used (Axon7RootToolV4) first unlocked the bootloader and then had a step to flash TWRP. When I was attempting to update TWRP, per the LOS instructions, it wasn't updating like it has in the past on other phones. I now know that restarting was the worst thing to do at that point. If the version of TWRP doesn't also match the bootstack and ROM, you're going to have a bad day if you restart.

Categories

Resources