I can't seem to get phone to finish Fastboot or RSD boot. I can put the phone into either mode, and it gives me the screen Starting Fastboot (or RSD) protocol support. Then it stops there. If I plug in the phone, Fastboot devices returns nothing.
I had updated my phone to the latest OTA, 2.3.4, and then used the Fastboot method of rooting phone with these instructions.
http://briefmobile.com/motorola-atrix-4g-root
Phone is definitely rooted, have several apps loaded that need SU. When I boot phone normally it is recognized as a mass storage device in both windows and linux (I can drag and drop files from and to phone).
So why would fastboot quit working after root, and would that have caused it?
Related
I've had this phone for about a good 4 months now, was getting bored so i decide to unlock the bootloader, root, and install a new rom. Then i heard youwer able to activate the HTC logo button to wake and sleep your device with using a different kernel. tbaldens kernel v3.6. I have TWRP recovery installed with trickdroid as my rom.After i ran threw all the procedures to flash in Aroma installer. My phone won't turn on, when i connect it to my computer it shows up as a MTP device. When I do get it to power on its stuck at the "quietly brilliant" screen. cant get into recovery to restore from back up. PLEASE HELP! SOLDIER DEPLOYED!!!!!!!! dont have the means of sending it in. Any suggestion. Mac is my primary means of rooting. windows 8 drivers are kinda funky:crying::crying::crying::crying::crying::crying::crying:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
crashfocus said:
If you have access to a Windows 7 PC, then download the RUU for your device. Next, relock your bootloader (fastboot oem lock) Next step, if you have bootloader access to your device, then you can go into fastboot (make sure it says fastboot USB). Open a command prompt, and type in fastboot oem rebootRUU. You're in RUU mode, where you can run the RUU and reset everything back to stock.
Click to expand...
Click to collapse
can i do this from a mac? and i can't get into fastboot because it wont go past the htc logo screen. it is identified as a MTP device in windows
Ahhhh thankfully i was able to get into my bootloader and flash my recovery! but thanks for the reply bro
A few days ago, my Razr Maxx HD crashed and won't boot. It is locked, and not rooted. Initially, it wouldn't ever get past the red circle initial splash screen and would stay on that for hours. I was able to press the Power+VolUp+VolDown to get to the menu to Restore, Normal Boot, etc... I was able to get to the dead android guy one time and one time only thus far. I tried to take it into a store, but they did a very half-hearted attempt and trying to get it to work again. Since then, I have never been able to get as far as I did prior in trying to recover anything.
Now, it almost immediately just boots into fastboot with an error of Kernel Boot Failure.
My phone does/did have Developer Options enabled, and I was previously able to use it with Android Studio, and deploy apps to it, so I know the drivers are loaded on my computer fine, and I am using the same cable.
Ultimately and if possible, I am wanting to retrieve the data off the phone. From what I am seeing I THINK it is still possible.
When I connect the phone to my computer, and it is in fastboot, I can type this in the cmd prompt: "fastboot devices". It sees it and lists it as a device. On my phone, I also get the message of "USB connected", or "USB disconnected" (if I disconnect it). In the Windows Device Manager, when I plug it in, it detects the hardware change, and I get the entry for "ADB" in the Device Manager. If I disconnect it, it goes away. So, windows does see it on some level. In that same command prompt, if I type "adb devices", it does not see any devices attached.
If I can get adb to work, I should be able to pull the data off. Knowing that it goes into boot failure, should adb even work? Does it need to boot up far enough for adb to work, or should adb work no matter what?
I've looked into unlocking to install TWRP or similar, but doing so, deletes data which defeats the purpose in all of this.
I can still get to the menu to boot into Normal, Recovery, BP Tools, etc... but so far any option I try puts me back into Fastboot.
Any thoughts? Anything for me to try?
Unfortunately, you're out of luck in this situation. ADB only functions while booted or in a recovery (for retrieving data, it would need to be a custom recovery, which is not an option at this stage for your type of phone). You can not retrieve info in fastboot mode and restoring the phone's software/firmware via fastboot or RSD Lite will also wipe the data.
I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
My K7 is T-Mobile LG-K330, Android 5.1.1, kernel 3.10.49, Build LMY47V, vers K33010j
I have searched and tried many root guides. All end the same way. This isn't new for me as I have rooted and installed mod roms on several phones and a tablet.
The main problem seems to the phone will not show as connected to the root tools. I have triple checked the developer mode ena and usb debugging ena and tried OEM unlock both ways.
I have the latest (as of today from XDA, minadb and kingroot (PC)). Both are installed on my Win10Pro comp.
The phone USB drivers must be in place as I can plug in the usb and the K7 comes up in the This PC list and I have access to the folders. I must be missing something.
adb devices -l
daemon starts but no devices are listed
fastboot devices
none listed
kingroot
all is well up to the point where it tries to "connect" it just fiddles in circles
I waited 15 min and Xed out.
This may be related: I cannot boot to the recovery screen. No matter how I hold the power and up volume I always get the T-Mobile screen and android.
Has anyone seen this or have any suggestions?
Happy Trails
I had similar problems with my K7.
I had to download a different minimal ADB / Fastboot tool from http://forum.frandroid.com/topic/246460-root-and-recovery/ .
Once the bootloader was rebooted the phone had on-screen instructions.
Use this https://forum.xda-developers.com/lg-k7/how-to/t-mobile-lg-k7-thread-t3481844 and the site above for instruction.
Put your recovery twrp-image-3.img and the SuperSU.zip on a micro sd and insert it in your phone before you start.
Also put the twrp-image-3.img in the ADB program folder on your computer.
Once the bootloader is unlocked, instead of typing: fastboot flash recovery twrp-image-3.img .
Type: fastboot boot recovery twrp-image-3.img or fastboot boot twrp-image-3.img (I don't remember) (only one will work).
Then once in twrp install the recovery ( twrp-image-3.img ) and then the SuperSU.zip from the SD card.
Also make sure you check the box and allow your computer permission to connect to your phone when you first connect them, after you enable usb debugging on you phone.
Good Luck.
Long story short: installed custom rom, went into TWRP bootloop, tried to flash back to stock ended with bootloop.
Is there a way to enter into fastboot? So I can at least flash TWRP back.
Currently it's booting, displaying the boot screen with the orange state warning and almost immediately rebooting
Fastboot on Android side gets activated by bootloader. Hence you should be able to run Fastboot commands.
To test this you run on Windows computer
Code:
fastboot devices
jwoegerbauer said:
Fastboot on Android side gets activated by bootloader. Hence you should be able to run Fastboot commands.
To test this you run on Windows computer
Code:
fastboot devices
Click to expand...
Click to collapse
Tried to spam sudo fastboot devices on linux, but to no avail.
Trying on windows as soon as I find the drivers
Installed the drivers from here and rebooted: https://gsmmobiledriver.com/umidigi-f1
Spammed fastboot.exe devices in admin power shell, but again no output at all
While it doesn't respond to fastboot, I noticed that, while booting, lsusb displays the preloader:
Bus 003 Device 010: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
Is there a way to interact with it?
It seems it's possible to unbrick the phone with SP Flash Tool, I can't find a guide or how to do it however...
Edit: all guides I had foudn require to device to be powered off. Given that my case is a bootloop, I will try to wait until the battery has dried up
Ended up following this: https://forum.xda-developers.com/t/stuck-in-a-boot-loop-and-cant-access-recovery-mode.3818742/
Standard procedure with SPFlashTool: no preloader, download all else. Results in a "PMT changed for the rom; it must be downloaded", so I probably have a faulty firmware copy
Edit: wrong firmware, my phone uses the global instead of the EU one for some reason