HI I have just been trying to return to stock my XT1570 Motorola X Style.
Originally i unlocked the bootloader and rooted the original 5.1.1. software.
Later the OTA update came out and i cant get it as the phone is rooted.
I did have backups but have lost them now.
The boot loader is intact, the TWRP recovery is there and I can access it.
I flashed a new system using fastboot this system "fastboot_clark_retcn_ds_user_5.1.1_LPH23.145-7_7_release-keys-cid11-retcn_CN.tar" which i believe should be the correct one for China.
The phone boot normally, the warning about unlocking the bootloader and then the motorola graphics, but when all that is done the screen is just blank, the screen is obviously on, as you can see the back light, but it is in the totally black state.
Anyone got any ideas what has happened there.
I have tried flashing other roms for XT1572 and XT1575, however while they work to an extend, obviously some of the internals for the XT1570 are different, modem for instance.
Some expert help would be greatly appreciated.
Related
I have an XT907 I used with Verizon for a while in NJ, then gave it to my kid for playing games once I changed carriers (mid-contract). I've looked at the phone and it would get stuck at the red eye screen. I've gone to recovery and wiped the user data/cache, no help.
The bootloader is LOCKED (and doesn't seem eligible to unlock). I've tried using Matt Groff's Razr utility to restore the system/boot images, but my guess is that since the bootloader is locked, it won't let me overwrite critical system files. I think I may have messed something up by trying to update some of the files but not the core system files. Maybe that's not even the problem, I dunno.
I've looked at how to unlock a bootloader but it seems to require root access, which I can't get since the device is unbootable. The device is also ineligible for unlocking normally (thanks, Verizon). Now it's stuck on an infinite loop with the red eye for about 25 seconds, then reboots. Repeat forever. Do I have any other choices for recovering my system? Can the device be unlocked via fastboot (maybe a custom recovery image)? Or is the problem not even the system/boot images?
Or am I SOL? I can't go to Verizon because I bailed from the contract. Not sure if they were (somehow) responsible for messing up the phone in the first place?
blakeloverain said:
I have an XT907 I used with Verizon for a while in NJ, then gave it to my kid for playing games once I changed carriers (mid-contract). I've looked at the phone and it would get stuck at the red eye screen. I've gone to recovery and wiped the user data/cache, no help.
The bootloader is LOCKED (and doesn't seem eligible to unlock). I've tried using Matt Groff's Razr utility to restore the system/boot images, but my guess is that since the bootloader is locked, it won't let me overwrite critical system files. I think I may have messed something up by trying to update some of the files but not the core system files. Maybe that's not even the problem, I dunno.
I've looked at how to unlock a bootloader but it seems to require root access, which I can't get since the device is unbootable. The device is also ineligible for unlocking normally (thanks, Verizon). Now it's stuck on an infinite loop with the red eye for about 25 seconds, then reboots. Repeat forever. Do I have any other choices for recovering my system? Can the device be unlocked via fastboot (maybe a custom recovery image)? Or is the problem not even the system/boot images?
Or am I SOL? I can't go to Verizon because I bailed from the contract. Not sure if they were (somehow) responsible for messing up the phone in the first place?
Click to expand...
Click to collapse
Do you know what system version your device was on before this incident?
If you were on Jelly Bean - I would suggest flashing 183.46.10 (the first KitKat build) with RSD Lite - then root and unlock the bootloader.
If you were already on KitKat - then you can restore with RSD Lite.
Everything you need > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Hello! I have just upgraded to Android M and I have two quick questions: 1 is , is it a problem if my system did not have any problems updating , even though I am S-OFF and my boot-loader is unlocked, this system being installed from a zip? 2 is, I do not have the brightness bar in the notification area, and that is a feature I used to use a lot, yet it isn't there, and I can't find it anywhere in settings. Please help on the second one and tell me if this is supposed to happen or not, also BTW in the boot loader it says System status: official, but it is S-OFF and the boot loader is unlocked.
1-Did you unlock the bootloader or it was unlocked when you got the phone? maybe you have the developer edition phone.
2-I think this option is not available for the M9+ you need to use an app like Brightness slider control or any other app from google play
Reply
About your first question: I was the one who unlocked the boot loader because I had the clean slate ROM installed and just reverted to stock, yet the stock ROM was a very old version and because it was S-OFF and the boot loader was unlocked I feared that I might not get the marshmallow update, yet I decided to try and install the update anyways, and to my surprise it worked flawlessly. Is this normal lol
Hello, i have a Moto g4 Amazon edition (XT1625) and all of a sudden, it got into a bootloop for no reason. it is not bootloader unlocked, not rooted, totally stock. so i did some research and tried some things, wiping cache, wiping data and nothing. so my next bet was to try to flash the same firmware or anything that would make the phone Boot up.
I tried flashing the 6.0 firmware, 7.0 firmware, at least, i tried 6-7 different firmware with no success (all of them said pre-validation error, like i was trying to flash a older version) but one. the only one that actually flashed, got me booting into recovery saying "this is an unauthorized sw" and that's it.
i got another exact same phone fully working and i noticed it recieved the OTA update NPJS25.93-14.7-3 and as far as i know this the December Security patch.
is there any link to download the full ROM with this update? or the September 2017?
i'm guessing those are the only firmware that could resurrect this phone right now...
Try this link for stock firmware
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/
Thanks for the reply.
i downloaded the rom and tried flashing it without the .gpt and the bootloader.img for safety reasons...
it flashed all okay and when it booted it shows the moto logo and turns off every time i try to turn it on... if it's connected to my computer, it just reboots into boot logo.
and yes, i then tried flashing the rom with the .gpt and bootloader file and no result.
is there any way i can fix this bootloop?
this was actually the first problem the phone had, no root, no unlocked bootloader and all of a sudden went into bootloop..
mtvictor said:
Thanks for the reply.
i downloaded the rom and tried flashing it without the .gpt and the bootloader.img for safety reasons...
it flashed all okay and when it booted it shows the moto logo and turns off every time i try to turn it on... if it's connected to my computer, it just reboots into boot logo.
and yes, i then tried flashing the rom with the .gpt and bootloader file and no result.
is there any way i can fix this bootloop?
this was actually the first problem the phone had, no root, no unlocked bootloader and all of a sudden went into bootloop..
Click to expand...
Click to collapse
You found some solution, I have the same problem.
mauri550 said:
You found some solution, I have the same problem.
Click to expand...
Click to collapse
Nothing has worked so far, the phone is laying like a brick for the moment.
My friend has an odd phone. I believe it to be an XT1680 - the latin american model.
Prior to this issue it showed in the device info as a moto g4.
We suspect maybe it had a tech or service rom flashed to it at *some point*
The IMEI listed could not get him an unlock code. The IMEI on the sim tray however did.
He tried to unlock the bootloader and in the process wiped the phone. So now he's stuck with a locked bootloader and no OS on his phone.
How do we salvage this?
We've tried reflashing several different firmwares, but with no luck. The motorola rescue tool does not recognize his phone.
English is his second language (He speaks it fantastically well!) so I told him I'd post this to get him started.
Thanks guys, I want to see this phone function again!
XT-1680 is a G5 Plus so device info showing G4 is odd. Unlocking wipes data not the system partition. Also you don't need an unlocked bootloader to flash firmware files. Fastboot might show some error. Is it booting into fastboot? Try flashing the latest firmware. What firmware was it on before trying to unlock.
Good evening. I got a second G7 as a project phone. It's badly damaged but was running a stock OS when I got it. I unlocked the bootloader and patched a boot.img file with my other G7, then flashed it to the boot partition. The receiving phone demanded a factory reset, so I did and now it's bootlooping.
The two phones are identical except for the back panel color and the damage, both XT 1962-1, 64 GB ROM, 4 GB RAM, both running Pie. TWRP will boot on both but will neither install nor make a backup of the one that's running.
I know there are a number of mistakes I might have made. It's been two years since I rooted the other G7. I think I lost the AVB keys and can correct it by flashing a blank vbmeta.
I wanted to ask though in case there's something I am missing.
Thanks!