Hi friends,
I have just bought Moto G 2nd generation smart phone with 16 gb internal memory. To root device, I tried to unlock bootloader. But it didn't go smooth. When I hit command fastboot oem unlock <key>, I got success message with status Device unlocked. Status 3.
But what the heck this status 3?. I am not getting any info about this.
Google search is showing that, at time of unlocking bootloader, few messages are shown like 'unlocked' then 'restarted' and device restarts. But this didn't happen with me. So I manually restarted my device for custom recovery. And flashed rom using TWRP2.7.1.1-titan-motog-2014. This command also showed me success message. Before this I copied UPDATE-SuperSU-v2.02.zip in device.
But after restarting and hitting recovery, device is not showing any thing and just black screen and then turning off.
Apart from this device is working fine, with normal boot.
P.S. RootChecker is showing that Root access is not properly installed on this device.
So what is the way out to root the device again properly?
Thanks in advance.
zoozope said:
Hi friends,
I have just bought Moto G 2nd generation smart phone with 16 gb internal memory. To root device, I tried to unlock bootloader. But it didn't go smooth. When I hit command fastboot oem unlock <key>, I got success message with status Device unlocked. Status 3.
But what the heck this status 3?. I am not getting any info about this.
Google search is showing that, at time of unlocking bootloader, few messages are shown like 'unlocked' then 'restarted' and device restarts. But this didn't happen with me. So I manually restarted my device for custom recovery. And flashed rom using TWRP2.7.1.1-titan-motog-2014. This command also showed me success message. Before this I copied UPDATE-SuperSU-v2.02.zip in device.
But after restarting and hitting recovery, device is not showing any thing and just black screen and then turning off.
Apart from this device is working fine, with normal boot.
P.S. RootChecker is showing that Root access is not properly installed on this device.
So what is the way out to root the device again properly?
Thanks in advance.
Click to expand...
Click to collapse
Status=0 is Locked never been unlocked
Status=2 is relocked HAS been unlocked
status=3 is UNLOCKED
you will never get status 0 back its a once only condition (some says a poly fuse blows- i personally think it's more a case of write once memory has a marked added, and thus cant be reverted back)
but dont worry there is no need to relock boot loader to 2 (as 2 and 3 both void warranty)
Boot loader lock or unlock has NO relation to being able to receive OTA updates or installing them.
TWRP is now 2.8.40 for moto g 2014 use search
super su is now 2.45 again search
Hey folks,
I need your help;
After a forced shutdown due to a depleted batterie, my device only boots into Fastboot.
My Nexus 6 is unrooted and has stock Android 6.
If I try start, recovery mode, or factory reset, I only get the following error;
"failed to validate boot image: ret=-1"
Connecting it to a PC does not help, as the pc does not recognise the device (so I can not install the usb drivers).
I managed to boot the device once, but all the google aps crashed, and finally android itself crashed.
Now on around every 30th try (in starting android in normal mode), I'll get the follwing message:
"Decryption Unsuccessful, The password you entered is correct, but unfortunately your data is corrupt"
What can I do?
Olikay said:
Hey folks,
I need your help;
After a forced shutdown due to a depleted batterie, my device only boots into Fastboot.
My Nexus 6 is unrooted and has stock Android 6.
If I try start, recovery mode, or factory reset, I only get the following error;
"failed to validate boot image: ret=-1"
Connecting it to a PC does not help, as the pc does not recognise the device (so I can not install the usb drivers).
I managed to boot the device once, but all the google aps crashed, and finally android itself crashed.
Now on around every 30th try (in starting android in normal mode), I'll get the follwing message:
"Decryption Unsuccessful, The password you entered is correct, but unfortunately your data is corrupt"
What can I do?
Click to expand...
Click to collapse
sounds like you should flash a factory image.
ok, heres the problem. to flash a factory image, you need to unlock your bootloader. to unlock your bootloader, you have to enable to oem unlock setting in developer options. which means, you need to try to boot again, 40 times if need be. when you boot up, you need to go into settings, about phone, the press build number 3 times in a row. that will enable the developer options. go back one page, scroll up, and youll see it. go in there and enable oem unlock. now you can flash a factory image.
Yea dude, that doesn't look good at all. Have you ever installed any mod of any kind on the device before? Or was this just random and happened while 100% stock? Your best bet as Simms said, would be to try and get into your developer settings and turn on "allow oem unlocking" and "USB debugging". Then flashing a stock image.
Sent from my Nexus 6
There is no modification to the rom.
Unfortunately, I don't think I so get it booted anymore, the only think that might happen is that it brings me to decryption unsuccessful window and from there on reboot is the only option (also after waiting more than 10 seconds or hitting the power button to try and dismiss the message). Even if I did get into the OS which I succeed once close to the beginning of the problem, I would get so many popups of crashed Google apps that you could do nothing before it would crash the OS completely.
Olikay said:
There is no modification to the rom.
Unfortunately, I don't think I so get it booted anymore, the only think that might happen is that it brings me to decryption unsuccessful window and from there on reboot is the only option (also after waiting more than 10 seconds or hitting the power button to try and dismiss the message). Even if I did get into the OS which I succeed once close to the beginning of the problem, I would get so many popups of crashed Google apps that you could do nothing before it would crash the OS completely.
Click to expand...
Click to collapse
Damn, that's awful dude, I wanna say your Nexus isn't recoverable. Might have to send it in for repair to Google. If there was no modification to it at all, bring that up! You might get it fixed cheaper or free!
Sent from my Nexus 6
It's really sad, and it makes me think why the USB debugging mode is not enabled on default on every device for this very reason.
I did not root the device yet, as I did not wanted to risk to lose the warenty which it still should be under. So I guess I have no choice than to send it in.
I will try one last thing, and that is to hook it up to a Ubuntu powered computer, let's see if I can mount the phone' s drive with it.
I'll keep you folks updated.
UPDATE: negative on the Ubuntu idea, there is nothing mountable (Disk utility)
It works again! At least it seams for now...
This worked for me video ID: 0nDLvy8F5qk on youtube "Nexus 6 Hard Factory Reset Fastboot Bootloader Recovery Mode" from Jamie Wagner (I am not allowed to post links yet)
But I needed 20 tries to boot into factory reset.
if ya know your going to mod it at some point...maybe unlock it so if it does happen...you can fix it. thats my main reason for running an unlocked device. if you know what hits the fan...you can always fix it yourself. just a suggestion though.
Yourgodtim said:
if ya know your going to mod it at some point...maybe unlock it so if it does happen...you can fix it. thats my main reason for running an unlocked device. if you know what hits the fan...you can always fix it yourself. just a suggestion though.
Click to expand...
Click to collapse
Definitely! I would highly recommend just unlocking your bootloader and leaving it unlocked, with USB debugging on! This does not affect OTA updates at all and really, it's a last resort form of protection! My opinion of course!
Sent from my Nexus 6
unlock tbe bootoader
that the best thing youll do for your device, just in case. you dont have to modify anything, and itll still be unmodified.
Hello
I recently got my mi5 after ordering from aliexpress and not a big fan of MIUI and wanting the cyanogenmod experience I applied for opening up the bootloader.
Today I recieved message that the request was granted and i happily started the progress with opening up the bootloader via the miflashunlock tool.
When I used the tool it gave me a message in lines of "No need to unlock this device" So i thought " Ok, maybe the seller had to unlock the bootloader to flash the global ROM or whatever.
I proceeed to flash TWRP and it flashed fine, so my bootloader must obviously have been open all the time?
Then I did a full wipe, instralled CM13 and opengapps and rebooted.
Now the trouble started.
All I boot into is a black screen, nothing happens.
If I try to boot into recovery I get a black screen.
I CAN boot to fastboot
So i go back to fastboot to check bootloader status.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
How can this happen? How the hell can flashing CM lock my bootloader? I never checked the bootloader in fastboot before this, but since I was able to flash TWRP I must have had an open bootloader.
I have tried to flash different ROMS via the MiFlash tool and it gives me message that the devices is locked (duh!)
I have tried to open the bootloader via the unlock tool but it says that the currenct account is different from the account info on the device. Not very strange since I installed CM13...
I have tried to both flash and boot into TWRP via fastboot but I can't do this since device is locked...
Is my only option to try this
http://en.miui.com/thread-299790-1-1.html
Or can i just throw the phone in the bin after three days and buy a new phone from another company that values openess a little more?
---------------
Booting to EDL-mode with this suggestion:
http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
After this you can flash whatever rom you like with the miflash tool
I still end up in the same situation when trying to flash CM13
Phone boots to black screen, I boot back to fastboot and phone is locked gain.
But this is something I can try to figure out on my own
Just an update so if anyone else who ends up in my situation searches forums they might find answer here.
Every time i flash CM13 the same thing happens. Bootloader gets locked and phone can only start in fastboot.
I tried installing RessurectionRemix instead and it worked straight away.
Why the hell this happens I have no clue, but this some of you geniouses maybe knows.
Right now I really don't care since RR works just fine for me
any solution ? I have the same problem
After the last OTA update, my Moto G5 started to boot with the following warning:
"Your device has failed verification and may not work properly.
To learn more visit:
motorolacom/unlockbootloader
ID: N/A
Your device will boot in 5 seconds"
It also started to restart randomly.
I did some research on the web and found out that this warning appears when someone unlocks/roots the device. But I ever never unlocked the bootloader or rooted the device.
I reinstalled the OS with the help of Rescue and Smart assistant. Now it stuck at moto boot logo. Please help me.
thank you
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Weltraumpenner said:
I got two brand new Pixel 4a (5G) for my girlfriend and me. Mine worked perfect, hers was freezing and rebooting all the time. To solve this, I wanted to reflash the factory image.
I messed up the two devices and didn't notice, that the bootloader on hers wasn't unlocked yet. So I ran flash-all.sh on locked bootloader. Now the Pixel says "Can't find valid operating system." and I'm stuck in fastboot-mode with locked bootloader. Neither can start Rescue-, nor Recovery mode.
After I'm not able to unlock bootloader (because I never allowed it on her phone), I will bring it back to the shop tomorrow and ask for an exchange/repair.
But how can that be? Shouldn't a locked bootloader protect the device from a brick like that? I mean the flash-all.sh runs some "fastboot flash" and a "fastboot update" command, and they should just fail on locked bootloader, shouldn't they?
Click to expand...
Click to collapse
Try fastbooting the newest ota instead of the full factory image. Also, try going to Android recovery and hitting the factory reset inside the menu there. I believe to access the recovery through fastboot you wait for the dead Android guy and then press volume up and power at the same time.
Sent from my Pixel 4a using Tapatalk
Did you ever figure this out? Google had a chrome extension flag tool. Instead of cmd/cli adb.