Ok, i'm stuck on the bootloader screen.
I've tried every single thing ik. I've tried to reinstall the stock room but EVERY TIME the mFastBoot returns FAILURE for every process, I can even unlock the bootloader since >fastboot oem get_unlock_data returns "Could not get unlock data!" .
All this thing happened after one update that I've received and downloaded.
What should I do now to fix the fastboot?
Thanks for your time =)
Related
So, I have an Atrix 4G (2.3.6) and decided to try rooting in order to install a proper adblock. I'm a bit new to Android so I did some careful research and I found some tutorials that showed to do a fastboot oem unlock.
But I guess the Atrix doesn't unlock from a straight fastboot oem unlock command? Because it now boots directly to the fastboot screen with a "(ap) fastboot flash mode (s) flash failure" error.
I can get it to boot normally by holding the volume and power buttons and selecting 'normal' but that is a pain and can only be done with a good charge on it.
I'm going to say I don't know what I'm doing here. First and foremost I'd like to restore a normal boot, though I wouldn't mind knowing what to do from here to properly root it.
Lt.bird said:
So, I have an Atrix 4G (2.3.6) and decided to try rooting in order to install a proper adblock. I'm a bit new to Android so I did some careful research and I found some tutorials that showed to do a fastboot oem unlock.
But I guess the Atrix doesn't unlock from a straight fastboot oem unlock command? Because it now boots directly to the fastboot screen with a "(ap) fastboot flash mode (s) flash failure" error.
I can get it to boot normally by holding the volume and power buttons and selecting 'normal' but that is a pain and can only be done with a good charge on it.
I'm going to say I don't know what I'm doing here. First and foremost I'd like to restore a normal boot, though I wouldn't mind knowing what to do from here to properly root it.
Click to expand...
Click to collapse
what steps did you take? fastboot oem unlock only works when the bootloader isn't locked anymore. By default, manufacturers lock their bootloaders so also with motorola you need to unlock it first. There are some ways to do this, the sbf method and whatnot but it's not really idiotproof.
Is all you did the fastboot oem unlock? else you might want to relock it by "fastboot oem lock" and just root your phone if you don't want to go custom rom
Have you tried this: - http://forum.xda-developers.com/showthread.php?t=1182871
i was flashing a rom via ruu then when the error that says flush immediately popped up i typed fastboot oem rebootRUU but it said waiting for device so i disconnected the phone and rebooted into fastboot but i might have rebooted into android i can't remember, now fastboot doesnt work. anyone help ? thanks.
also on the bootloader it says OS-3.62.1700.1 (3.10.502.2) in red letters. its relocked bootloader s-off cid1111111 i wanted to go to stock cause its on gpe 4.4.2 and its still there.
Hello there!
I was on Sultanxds Custom rom + kernel and decided to flash another Rom. Therefore i wanted to update my TWRP to Version 3.0.2.0.
So i went into fastboot, connected my phone to the pc as always an ran the comand: "fastboot flash recovery twrp-3.0.2-0-onyx-20161116-113742.img". I got the message: "FAILED (remote: Device not unlocked cannot flash or erase)"
So i checked for oem unlock and this was the message i got.
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false"
I just dont understand why the bootloader is locked... how is this even possible but anyways so i tried to just normaly reboot the device. But now i see the 1+ logo for 1 sec and it vibrates. And then it turns black again and I see the logo again and again...
But i'm still able to enter fastboot mode and i can send command from my PC. Can anyone tell what steps i have to do to make it bootable again? (is this a hardbrick?).
Thx in advice!
I just followed the hardbrick guide and i'm now on stock OS. For some reason the bootloader was locked again... problem solved and this thread can be closed...
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.
Hello all,
I have a Mate 10 Pro that I was having trouble updating, I assumed due to having TWRP installed. So, I tried to restore the stock recovery via fastboot flash.
However, the flash would always fail with "remote: Command Not Allowed" error. Googling showed this to be result of locked bootloader, but my phone was indeed unlocked. Indicated on the screen when in Download mode.
Some threads suggested relocking and then unlocking the bootloader again. So I ran fastboot oem relock, which restarted and factory reset the phone. Then I ran fastboot oem unlock and I am now getting the "remote: Command Not Allowed" error, and my phone remains locked and now it will not boot at all but only to the eRecovery screen which wants to connect to wifi and download a package but getting package info always fails. Oh, and since I didn't think to remove my account, the phone is also FRP locked.
I had found a thread before this incident saying to change the DNS in order to get the eRecovery download to work, and at the time it did. Now the only thread I find with that suggestion (81.177.139.39, not sure it's the same one) it still fails to get package info.
So as it stands I have a FRP locked, bootloader locked Mate 10 Pro that will only boot to eRecovery.
Anyone have any suggestions?