Hello everyone.
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is UNLOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Device Manager
Current version:N/A
What happened:
Phone ran outta charge at 0%.
Plugged it in,on restarting,after the usual startup animation,I was greeted by a dead screen ,much to my horror.
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"
}
Tried a hard reset and several reboots.nothing worked.
I can access:
The bootloader
The recovery mode
Also put in CWM (without touch)
ADB is able to recognise the device.
P.S: My case was exactly that of @ravibhat here in this thread:http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
Initially,my bootloader was locked and everytime I tried recovery it kept saying "boot failed" ,just like in ravi's case.
I unlocked the bootloader using the Motorola website and installed CWM after reading up on it.
Tried flashing stock firmware but in vain.
Went to the service center where I was told my phone has a motherboard defect and needs to be replaced( which I do not believe).
What I want:
My phone restored to normalcy.
Losing data is not an issue.
Bootloader image:
MotoG Bootup Problem - Recovery Mode failed
i have same problem in Moto G XT1033 Dual SIM ( Android Lollipop )
i haven't done anything in phone
I want My phone restored to normalcy
@spanda12 and @M.Mostafa :
I still haven't flashed stock ROM using TWRP in the proper way since i wanted to recover my data.Will be doing this soon.
Few questions :
are you able to mount /data partition in TWRP?
are you able to successfully flash any custom recovery or only able to boot up from it?
in my case,if i flash twrp recovery using "flash" command it still loads default Android recovery but i am able to boot it up using "boot" command.
syntax example :
"mfastboot boot twrp.img" or "mfastboot boot philztouch.img" works
"mfastboot flash recovery twrp.img" or "mfastboot flash recovery philztouch.img" not working.
But here are a few steps that you could follow :
Use the .img file in this zip (attached),boot up using this and then try flashing the STOCK ROM and post the log here.
Hope you're flashing the Official XT1033 5.0.2 STOCK ROM and not something else.
Also,tell us the exact tutorial/steps you followed to flash.
I see that your bootloader is LOCKED.
I suggest you to UNLOCK it first so that flashing becomes easy.
Data MAYBE lost while doing this.
If you want to try and recover your data,refer my thread and maybe try the things i did.
Also,i suggest you open a different thread since this one is for spanda12's issue.
It'll help you document,receive specific responses and resolve your issue in a better way.
M.Mostafa said:
i have same problem in Moto G XT1033 Dual SIM ( Android Lollipop )
i haven't done anything in phone
I want My phone restored to normalcy
Click to expand...
Click to collapse
Related
(first sorry for my bad english)
when i power on my lg nexus 5 it stuck in boot animation like in this pictures
{
"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"
}
recovery mod also error,if i try to unlock bootloader it will succeed but after a restart it come back to normal locked,and i tried to flash firmware with lg flash tool but when it reach 6% got an error user data cant erase
is there any way to bring my phone back to normal?
maneeshpjoseph92 said:
(first sorry for my bad english)
when i power on my lg nexus 5 it stuck in boot animation like in this picturesView attachment 3364557
recovery mod also errorView attachment 3364566,if i try to unlock bootloader it will succeed but after a restart it come back to normal locked,and i tried to flash firmware with lg flash tool but when it reach 6% got an error user data cant erase
is there any way to bring my phone back to normal?
Click to expand...
Click to collapse
How did you proceed to unlock the BL?
To solve your bootloop: from the stock recovery wipe cache then reboot. If needed, wipe data/factory reset but you will lose your data.
unlocked boot loader in command mode it was fine it shows unlocking yes /no option and i selected yes it shows its unlocked but after i fastboot reboots it coming back to locked status and i cant see any options in recovery its blank only icon is green android icon with an red error
when i flash firmware output is userdata erase failed after 6%
maneeshpjoseph92 said:
unlocked boot loader in command mode it was fine it shows unlocking yes /no option and i selected yes it shows its unlocked but after i fastboot reboots it coming back to locked status and i cant see any options in recovery its blank only icon is green android icon with an red error
when i flash firmware output is userdata erase failed after 6%
Click to expand...
Click to collapse
Try again with this guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
i got the stock recovery but when i try to data reset it shows e:system not mounted,e:data not mounted etc.. i think internal card is not mounted can i repaire it?
and still my bootloader is not unlocking permanently
nyone please help me urgently
Looks like a hardware issue.
Hi there
I tried flashing the "[ROM] [NXT-L29] B320 International Rooted **UPDATE 6/14/16** " on my NXT-AL10 after that, it won't get further as to the screen where it says "Your device is booting now" (Picture attached).
Installed is TWRP 2.8.7.0. I'm able to enter TWRP and Fastboot.
I also tried flashing different ROMs but I'm still stuck at this screens.
I also tried the Italian Knife tool Unbrick option.
Do you guys have any tipps?
{
"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"
}
which firmware did u have installed before? 2.8.7.0 is not compatible with B3xx roms, u need to flash 3.0.2 for EMUI 4.1 firmwares. there is also a 3.0.2 version for EMUI 4.0 (B1xx roms), so watch out not to use the wrong one.
best thing to do now is flash a B1xx rom via fastboot and then upgrade from there...
Sent from my Huawei Mate 8 NXT-AL10
jbmc83 said:
which firmware did u have installed before? 2.8.7.0 is not compatible with B3xx roms, u need to flash 3.0.2 for EMUI 4.1 firmwares. there is also a 3.0.2 version for EMUI 4.0 (B1xx roms), so watch out not to use the wrong one.
best thing to do now is flash a B1xx rom via fastboot and then upgrade from there...
Sent from my Huawei Mate 8 NXT-AL10
Click to expand...
Click to collapse
Thank you, you were totaly right.
i just got it up and working with the guid from Germaniac:
http://forum.xda-developers.com/mate-8/general/unbrick-updating-to-b321-t3375934
good, a bricked device is never fun....
post removed by creator
Hi, I need help;
I have a GR3 2017 "PRA-LX1" latest twrp installed. I tried to install many ROMS, none worked except haky's lineage:
https://forum.xda-developers.com/p8lite/development/rom-lineageos-14-1-huawei-p8-lite-2017-t3649292
But it had many problems in the early stages so I tried his other rom, SLIM:
https://forum.xda-developers.com/p8lite/development/rom-slimroms-ng-7-1-huawei-p8-lite-2017-t3714239
It also had problems like fingerprint and cam not working "phone acted like it had no fingerprint sensor". Now problem is, since installing this ROM, every other ROM I install gives error 7 on twrp which I bypassed by editing the script file. However none of them boots, all PRA-LX1 ROMS that I have installed gets stuck at "your phone is booting now" like the OP's screen. Yet the above SLIM ROM gets installed with no error and boots just fine.
I have no one to turn to, even the ROM maker is not responding, please any help would be appreciated
hi friends I have exact this problem
my first rom was c900b180 android 6 nnd twrp 2.8 and unlocked bootloader
because dint get android 7 I try to flash it manually
1- I try to install from twrp not success
2-try dload not success
3-try fastboot use this commands
astboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
============================NOW
PHONE stay on above screen booting now.......
and twrp not installed and try to install more version
oorginal recovery not installe install in fastboot say success bot really not install
please help friends
Hi, this is my first post on XDA after following it closely for a few years.
I currently have a problem with my Huawei Mate 8 after trying to get a custom ROM up and running.
I have unlocked the Bootloader (verified with fastboot) via fastboot after getting the code from DC-Unlocker.
I then flashed TWRP custom recovery successfully. This is when i made a mistake.
I accidentally wiped something i should not have under advanced wipe after trying to get twrp to read storage.
After this i could no longer go into TWRP and the phone would try to boot after showing the unlocked bootloader warning only hanging on a black screen.
Only fuctions I can access is Fastboot Mode and Erecovery (Which I tried to recover from but it would only return a "Cannot find package information error" after trying to retrieve it.
I then tried to unpack an official firmware from the Huawei stock firmware thread and install the pieces separately. This is where I am stuck.
Via fastboot all .img packages i needed succeeded except for "cust.img" giving me an error: "remote: sparse flash write failure" and when trying to erase cust.img i get "Command not allowed"
I hope it can be saved.
Use srk tools to and use unbrick method. It will work for you.
Sent from my HUAWEI NXT-L29 using Tapatalk
Thanks
I was able to get it working again by doing what he did:
https://forum.xda-developers.com/mate-8/help/bricked-huawei-mate-8-pls-help-urgent-t3536810
cyber945 said:
Hi, this is my first post on XDA after following it closely for a few years.
I currently have a problem with my Huawei Mate 8 after trying to get a custom ROM up and running.
I have unlocked the Bootloader (verified with fastboot) via fastboot after getting the code from DC-Unlocker.
I then flashed TWRP custom recovery successfully. This is when i made a mistake.
I accidentally wiped something i should not have under advanced wipe after trying to get twrp to read storage.
After this i could no longer go into TWRP and the phone would try to boot after showing the unlocked bootloader warning only hanging on a black screen.
Only fuctions I can access is Fastboot Mode and Erecovery (Which I tried to recover from but it would only return a "Cannot find package information error" after trying to retrieve it.
I then tried to unpack an official firmware from the Huawei stock firmware thread and install the pieces separately. This is where I am stuck.
Via fastboot all .img packages i needed succeeded except for "cust.img" giving me an error: "remote: sparse flash write failure" and when trying to erase cust.img i get "Command not allowed"
I hope it can be saved.
Click to expand...
Click to collapse
What about your phone model?
NXT-L09, NXT-L29, NXT-AL10, NXT-CL00, NXT-DL00 or NXT-TL00
Mentioned on back of your phone like this image:
{
"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"
}
Hello guys! I'm on a G 2015 bike to find a way around it. Good tried the procedures without unlocking the bootloader, but without success! Then I went and I was able to unlock Bootloader and repeat the process to install Roo Stock. But to no avail as well. Does anyone have any tips for solving this problem?
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Hi there! I had the same problem, but the solution was just wait. It took a full 5 minutes to boot since the warning appeared, but it worked fine. Give it a try, wait 5 minutes (literally) and see what happens. If it still stuck, then try the solution above.
KrisM22 said:
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Click to expand...
Click to collapse
Hi. I tried to do the way you said it, but it did not work. Take a look at the picture
I follow this GUIDE for install
https://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
{
"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 don't think your bootloader is unlocked.
Have you unlocked your bootloader using the Motorola site? No other method will work.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
which recovery are you using - copy/paste full module name.
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Jdoria said:
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Click to expand...
Click to collapse
"when you insert the cell phone" into what?
EDITED POST FOR WINDOWS:
for windows I think type cmd in search bar, right click on cmd.exe and choose administrative (you may have to enter a password) and do everything in that window.
fastboot flash recovery twrp.img
but first tell me exactly which twrp you are using - one is bad.
Better than that just grab the latest from squid and use that. I know it's good.
When it flashes successfully, DO IT AGAIN - don't ask why, just do it - same command.
THEN boot to TWRP and backup your stock if you still have one.
Then and only then, wipe and flash whatever your heart desires.
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
acejavelin said:
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
Click to expand...
Click to collapse
Yeah I put a note at the bottom of that post for that. My bad.
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Jdoria said:
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Click to expand...
Click to collapse
You need to run it in administrative mode.
i tried to install twrp , root and degoogle my galaxy a12, i have no experience at all and nearly bricked my phone
i unlocked my bootloader, go into download mode, i tried flashing twrp 3.7.0 image i downloaded on the official website, it didn't work and everytime i reboot it got into download mode again
i flashed the stock rom again, go to the support thread of twrp on the galaxy 12 here, i did like the tutorial but i cannot flash the rom with the re partition and nand erase because odin will just froze and the progress bar wont appear
after that i tried flashing it like the post said. put the twrp image in the AP box, and the vbmeta.img.md5(i extracted the vbmeta.zip file since i cannot put the zip file into the box) into userdata box, then start, restarted the phone and after that it got the "An ERROR Has Occured While Updating Device Software" with the teal background, i freaked out but luckily i fixed it with the frp hijack software.
after that i'm just too scared to continue, does anyone know what i did wrong? my guess is that it's at the vbmeta file but the support post give that file only and i just extracted it and put the md5 file in the userdata box.
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
{
"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"
}
lil_kyrick said:
I assume that you flashed twrp recovery with vbmeta and you had One Ui 4.0 (Android 12) on stock. It's just that I had a similar thing when I flashed it on TWRP.
Note: WHEN YOU HAVE INSTALLED THE VBMETA AND TWRP FILE AND YOU ARE USING THE STOCK FIRMWARE THEN DO NOT LOGIN TO YOUR SAMSUNG ACCOUNT. YOUR PHONE WILL BE BLOCKED. AND WHEN TURNED ON, IT WILL PROVIDE THE FOLLOWING.
View attachment 5789287
Click to expand...
Click to collapse
no, it is the android 11 version with the A127FXXU5AVC4 stock firmware (vietnam region) and no i didn't login to anything after unlocking bootloader, and the warning shows something like this image here
but without the 2 last line, instead it has a korean and japanese translation below that first 2 english lines
i think i messed up at the vbmeta part, i though my phone was hard bricked but i managed to fix it and flashed a the stock firmware again
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
lil_kyrick said:
Oh ****. So connect your phone to your computer and use the "Emegency Software Recovery" function in the Smart Switch program.
What was your mistake? Yes, the fact is that you have SM-A127F, and you set it for SM-125F. And you need to repair the device now, otherwise, contact the nearest service center. Here is a link to the guide you need for your device.
Click to expand...
Click to collapse
ah i already fixed it myself with frp hijacker, thank you for your consideration
az_r08 said:
ah i already fixed it myself with frp hijacker, thank you for your consideration
Click to expand...
Click to collapse
Can you send a ss of the odin you are using and the settings?
What I assume is you need to use patched odin or you device is encrypted.