Yesterday after enabling Motorola Connect (sometime in the following 3 hours) my Moto X locked up. On restart it would only go to the Unlocked Bootloader warning screen and then sit there, no looping. I have access to TWRP, but it cannot access any internal storage from the look of the command line messages and will fail on Wipe with E: Unable to mount for each partition. I can get into Fastboot mode and can use mfastboot to push the latest VZW image and recovery to the phone, but on reboot TWRP is still there and the phone sticks at the Unlocked Bootloader screen. When using Fastboot or RSD Lite I get no errors when pushing files over, but the phone will not boot.
To verify if I actually was getting data to flash and rule out that it was bad images I tried flashing CWM6.0.3.6 (since TWRP isn't doing anything anyway) and it completed as expected, but on reboot TWRP was still present.
I don't know what is keeping data from getting permanently written to flash, but that seems to be where my problem is. My bootloader is unlocked and the phone was rooted but was stock VZW firmware other than a mod to enable WiFi tethering and Titanium Backup freeze of some VZW bloat.
Any help would be appreciated. Had to reactivate my old Droid 1 from 2010. It's not the device it used to be (actually it is, and thats the problem) but the CyanogenMod 7 on it works great .
Related
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
Yep, probably again a noob that bricked his phone.
As there was no info on my phone that wasn't on google servers or something I was so stupid to start installing the latest official CM12 built on my XT1068 without any decent backups.
- I think the moto/google service for lost devices encrypted my phone without me really noticing it. :crying:
- I was on Lollipop, the latest update I got here from in Benelux/Europe.
- I unlocked my device, worked fine. device also tells in bootloader
"Device is UNLOCKED. Status Code: 3"
- when than having installed TWRP 2.8.0.1, os started but gave problems installing superSU.
(no prob I thought, I go immediately forward with CM12 installation, so don't have to bother with the old ROM) :silly:
- wiping everything for clean install I already saw some messages coming up. on hindsight; Difficulties with opening /data folder etc...
- tried to install CM, and several other more stock roms, but never get through the message. All bad installs.
- maximum I got is CM12 booting up, preparing some apps and than a message describing the encryption problem, asking to reboot.
TRIED:
- install from usb drive (with OTG cable)
- erase and reinstall from TWRP 2.8.0.1 and other recoveries.
- fastboot flash a standard recovery again, to wipe data from there,
(from this standard recovery installers never got through even the verification to install, so tried than installing from other recoveries, same problem.)
Can still try but hesistant:
Unlock my mothers phone (same month, same model, same place, probably same encrypted) to try backup there in TWRP, recover this on my phone, and this way flash standard rom again. From there I could probably get rid of encryption. (as found already in several places)
I would afterward immediately try to lock my mothers phone again, don't know so much of how to get recovery to standard one again though. Can I backup this before. When I try now "adb backup - all" on my phone from my mac, I get "unable to connect for backup" message though. Even when phone is saying "phone connected".
Anyone an idea of how to get out this trouble?
Greetings
Otto
[email protected]: try "fastboot erase userdata"
have the feeling I'm getting there. Gapps still don't work but rom boots. Recovery has to be standard one to make encryption to work. Thats the key.
Hi,
I was unlocked and rooted and I tried using the NRT to flash the M system image. It worked and I got the phone to boot once. It went through the Android is upgrading process and I used it for a few seconds and then it froze. I rebooted it by holding the power button. It now will not leave the bootloader. When I try to start it just flashes back into the bootloader. In the BL log it says "failed to validate boot image: ref=-1" So I tried re-flashing both manually and in the NRT. This is the error I get when flashing
(bootloader) failed to write primary GPT
(bootlaoder) failed to flash partition
FAILED (remote failure)
Any help would be appreciated.
Thanks
Try fastboot erase before fastboot flash
-----_--------_--------_----------_---_--------_------------
....read......read more........think.........think more.......read...........read more........
Stop using a toolkit and do it manually https://developers.google.com/android/nexus/images?hl=en
I said that I did it both manually and with the toolkit. Sorry you feel that since I didn't want to type all that in you are better than me. I figured it out though. I couldn't get into any recovery so I used the toolkit to boot into the temporary twrp. Formatted all the partitions and got it to flash successfully.
From what I can tell it tried encrypting and it ruined the partitions.
My nexus 6 received the update by ota and I have experienced the same thing.... Tech support was no help telling me to go to a sprint store. I'm not sure what caused the issues here... My phone did the normal Android is upgrading thing and and I left I to do its thing it booted up and I used to it. Make a phone call. After the call my phone froze when I tried to open all apps. I restarted the phone in the same way the first post did. How ever my phone booted up to the new Android boot screen , however the phone restarted again and this time into the bootloader. Can anyone help me with this?
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)
Hey all,
First a massive thank you to the XDA people out there! You guys have done some amazing work and I am humbled by your level of awesomeness!
I'm working on a friends XT1254 who's phone started coming up with an endless loop of "Unfortunately, System UI has stopped." I can never get into the OS as the error message repeatedly opens up immediately after tapping OK. We're not concerned with salvaging the phone, but his contacts and photos (and potentially other data) are my only concern and what I'm working on retrieving.
Bootloader is locked. Phone is on the latest version.
Stuff I've tried;
- RSD Lite. Cannot recognize the phone regardless of everything I've tried. (original cable, different cables, drivers, different computers, different OS's)
- Recovery -> Format cache. (Completed successfully, but same system ui has stopped comes up)
- Fastboot & ADB sideload. (I can get the device recognized but have been unsuccessful at flashing anything)
- Verizon Motorola Software Assistant (This does reload the firmware successfully, but doesn't fix anything)
I feel confident in that I know how to get the phone back to working condition by using Recovery to wipe all user data and reset to factory, then I could do some magic and get the bootloader unlocked and go from there... but that's not the goal. The goal is just to get all data off first. I've looked into adb push/pull but since I can only access adb sideload, those commands do not work.
The closest I've gotten to ever seeing a filesystem is in Recovery -> "Apply update from sd card".
I've read some users were able to access the filesystem when in fastboot or recovery. The device is recognized under fastboot, but no filesystem displays for me (tried multiple systems including a linux system). In recovery, the phone is not recognized by my computers until I enter adb sideload.
I might be out of options here... but since y'all are extraordinarily smart, I thought I'd reach out and see if anyone had suggestions of how I can get the data off or maybe fix the system ui has stopped error.
Thank you!