A relative brought me his Moto G3 (XT1542) because it did not turn him on, he told me that the device was being updated and turned it off without knowing that something bad could happen, then he wanted to turn it on and send it to the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When "Start" was selected using the power button, the Motorola logo was displayed for a fraction of a second and the following screen appeared:
No matter which option is selected, "Bootloader Log" appears in all.
I have already tried to load the stock firmware but it does not take it, the same error continues.
I already thank you if you can help me solve this, it is already giving me headaches
Sorry for my bad English, I had to translate it because I don't speak that language.
As our phones are old this software may or may not work but give it a try,
https://support.lenovo.com/gb/en/downloads/ds101291
HTH
R1ffR4ff said:
As our phones are old this software may or may not work but give it a try,
hXXps://support.lenovo.com/gb/en/downloads/ds101291
HTH
Click to expand...
Click to collapse
did this work? I am stuck at the same problem
This error is indicative that either the ramdisk or kernel is corrupted. However, this is a soft brick and can be restored by using fastboot mode or RSD-Lite to flash an official firmware package to your device. Doing so will restore the device back to a factory stock state (but will not relock the bootloader if it has been unlocked. But, since relocking the bootloader carries no advantage except warranty related advantages, this is of little consequence). Official firmware packages for the Moto G 2015 can be found here https://mirrors.lolinet.com/firmware/moto/osprey/official/
Select the most current package for your variant. There are numerous guides here on XDA for restoring Moto devices using fastboot or RSD-Lite. The best fastboot guide I have seen is @lost101's tutorial & firmware repo here https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
(Official firmware is available at either of the above links. Just choose a link and find the most current build for your device.) @R1ffR4ff's earlier post linking the Lenovo Motorola Smart Assistant should also fully restore your device, and is less complicated than manually flashing an official firmware package. As such, the methods outlined in my post should only be used if the Smart Assistant did not do the trick.
Related
Hey guys,
My phone offered me the upgrade to Lollipop which I mistakenly accepted.
After a week I began to despise the changes and "features" and decided to go back to what had come with the phone originally.
In my haste to return my phone to it's former glory I followed this guide : http://forum.xda-developers.com/showthread.php?t=2542219
I didn't get far, see the error message below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After looking at other guides, including this one http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010 I've now hit a dead end.
When I plug my phone into my computer in Device Manager it's listed as "Android Device -> Motorola ADB Interface" so I'm not seeing "qhsusb_bulk" that's specified in that unbrick guide. Perhaps it's not as bad as I think it is?
My phone is currently sitting in bootloader mode and I'm hoping someone can suggest something I can try to resolve this, even if it means going back to lollipop.
Thanks in advance.
numbchuck said:
Hey guys,
My phone offered me the upgrade to Lollipop which I mistakenly accepted.
After a week I began to despise the changes and "features" and decided to go back to what had come with the phone originally.
In my haste to return my phone to it's former glory I followed this guide : http://forum.xda-developers.com/showthread.php?t=2542219
I didn't get far, see the error message below :
After looking at other guides, including this one http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010 I've now hit a dead end.
When I plug my phone into my computer in Device Manager it's listed as "Android Device -> Motorola ADB Interface" so I'm not seeing "qhsusb_bulk" that's specified in that unbrick guide. Perhaps it's not as bad as I think it is?
My phone is currently sitting in bootloader mode and I'm hoping someone can suggest something I can try to resolve this, even if it means going back to lollipop.
Thanks in advance.
Click to expand...
Click to collapse
Perhaps try this? http://forum.xda-developers.com/moto-g/general/guide-restore-softbricked-phone-t2965459
The following guide resolved my issue :
http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.
Successfully Done
✓ bootloader unlock
✓ TWRP Recovery twrp-merlin-2.8.7-r7.img
All most try all super user
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but after flash super user zip phone stop work at bootloader warning
same thing happen to me too..plz someone answer.
Prior to flashing supersu.zip, open twrp>advanced>terminal and enter (without quotes) enter the command
Code:
"echo SYSTEMLESS=true>>/data/.supersu"
Now SuperSU would install in systemless mode. The latest betas automatically install in systemless mode (I am using 2.74). Check if now it works.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, that is the command needed to make it work... note that since you already tried flashing several SuperSU versions the old way, if it continues to be a problem you may need to reflash the factory images and verify booting prior to trying the mentioned systemless method.
mindjek07 said:
...after flash super user zip phone stop work at bootloader warning
Click to expand...
Click to collapse
I had the exact same issue on my 16 GB xt1540, running stock, fresh 6.0. Trying to root with SuperSU's (over TWRP), several versions up to 2.74, earlier versions down to 2.4 ish... I'd freeze at boot logo every time, after what appeared to successful installs.
After reading somewhere about someone else's luck, I gave 2.65 a go, a version I must not have tried (and one I notice is not on your screen shot), and it worked. I certainly didn't expect it to, and obviously it could be completely coincidental. I'm pretty sure, however, that I did nothing differently on that install to what I had done other times.
HTH
Buena suerte
Love you!!!
You pacified my pain.
I am editing this post as I have become more educated in the last three months since I made the original.
I bought a broken phone. It had a bad battery and could not switch on in order for the phone to be reset. Neither could the seller provide me with any account info in order to remove the account before or after the reset was done I bought the phone from a repair shop as it was abandoned by the first owner as it was deemed uneconomical by them to repair.
I have replaced the screen and the battery with OEM items and have been trying for 2 months to get the phone unlocked.
Details that may be important
P30 ELE-L09
EMUI 10.1
What I have tried:
Every tutorial on YouTube related to P30 FRP lock and EMUI 10, and even some for other related Huawei devices like P20 and P30 lite.
I have tried eRecovery methods of update and restore, USBOTG method to update and both downgrade firmware. Everything fails. The recovery has buttons for emergency backup, but if I select this it reboots the phone back to the OOB setup. Also if I try to reboot to Safe mode, it does the same thing just in Safe mode.
HiSuite Proxy. @IProfessor This is still where I have issues as I feel that this is the most likely to succeed. Sadly every time the firmware reaches the point it will begin to install, it stalls and fails. I have logged it and will post them up here.
I believe the FRP lock is blocking me from resetting this device somehow, I just cannot figure out how and how to circumvent it. I am am being patient and I have time, the phone is not for daily use, yet.
Deleted.
New update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The process fails after the files are decompressed
Up.
Anybody with a solution that doesn't involve paying for it?
I'm looking for an answer too..
I took the phone to my local cellphone repair guy.
He had a guy that flashed the firmware directly to motherboard. The only downside is these guys sometimes use the wrong region firmware, as is my case.
Total spend was R350 ZAR.
P.S. are you not also on the vwclubsa forum?
So I got the first step, flashing TWRP. But, there's only a version of TWRP for the a10, would this work?
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
imalreadycrying said:
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
my phone doesn't show an oem bootloader unlock option
is it grayed out or do you just not see it
imalreadycrying said:
is it grayed out or do you just not see it
Click to expand...
Click to collapse
doesn't exist.
do you have dev options?
imalreadycrying said:
do you have dev options?
Click to expand...
Click to collapse
yes
send me a screen recording if you can, dev options should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have previously tried Kingo/King Root which worked on my KitKat Nabi tablet, I tried that on my a10e it failed. Root checker says there is no root for andr 11 on the a10e
whatever you do, do NOT use kingoroot, it basically installs a outdated version of SuperSU (which isn't liked by the community anymore because the original developer sold it to some random company) and bloats ur system up.
Yep, no OEM bootloader unlock option in dev settings
it may be possibly locked to your carrier. again, you can send me a screen recording or get an unlocked phone
My phone appears to be unlocked already, there is no sign of Verizon still being on here. I have since upgraded phones and the SIM card isn't in anymore.
Do I have to factory reset to fully get rid of the OEM?
i found this youtube video with some quick searching. it's in hindi but you can get the gist of it.
I most certainly dont have to disable automatic time right?
i don't know, after you get the option maybe you can set it back
i followed and nothing happened
did you reboot your phone after the fact?
yep, nothing works