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
Related
EDIT: FULL STORY BELOW. SKIP TO SECOND REPLY FOR UPDATE!
900A, AT&T, WAS 4.4.4. I rooted my phone with towelroot by downgrading via ODIN then reflashing 4.4.4. I've had the phone for a year and wanted to experiment with some custom roms--specifically Twi5ted Lollipop. The version I found last night was V3. Anyways I followed the instructions of installing safestrap then attempting to create a partition to host the mod. Every time I tried to boot the partition I would wait 12 minutes with nothing but a black screen (I presume a bootloop.) After reading some posts here I found it requires a clean flash--not a dirty flash. So I used safestrap to backup, then I wiped it and installed the mod. Nothing--still black screen. I then attempted to restore the backup I saved--fails every time.
At this point being the noob I am, I started to get very concerned. I went into advanced wipe and for some reason selected 'system' and wiped it. After a reboot, it shows the Samsung logo, goes blank, vibrates then goes back to the Samsung logo. I went into the standard bootloader and attempted to restore to factory settings but there is nothing to restore of course cause I wiped everything.
I'm currently at work bored as heck cause my phone is wiped. I can still go into download mode thankfully. Should I have no problems flashing stock via ODIN when I get home on my lunch break? Which stock firmware should I flash for this phone?
Thanks!
Unfortunately my lunch break brought me no good news. I downloaded stock found here: http://forum.xda-developers.com/showthread.php?t=2714455
After I flashed all the files (Except BL) when it boots, it get's to the Samsung logo--freezes halfway through then goes blank with the blue LED light on. I waited 10 minutes just to see what it does with no luck.
Another thing I found was weird-why when I boot does it still say 'Custom' when I flashed the stock firmware?
I really hope I don't have to drop $650 on a new phone Any help would be incredibly appreciated. Thanks guys!
DETAILED INFO: KOT49H. 6900AUCU1ANCE
MODEL: SM-6900A UD
FCC ID : A3LSMG900A
GALAXY S5 AT&T
why didn't you also flash the bootloader?
mike-y said:
why didn't you also flash the bootloader?
Click to expand...
Click to collapse
AT&T bootloader is locked right? Regardless I tried flashing the bootloader as a last resort and ODIN failed. Figured it just confirmed what everyone else said that it's locked.
Is there a specific way I need to flash the files? Like one at a time?
Do I need to restore factory settings/delete cache THEN flash each? or vice versa?
Am I basically screwed since I have AT&T?
:crying::crying::crying::crying:
FIXED!
After flashing 4.4.2 several times and trying different things, I came across this thread which finally brought my phone back to life. Thanks XDA!!!
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
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.
Hello!
I've recently got into a big problem while doing stuff I don't know much about (and probably in the wrong way, because of that...). So, let's get to the problem, shall we?!
Well, I wanted to root my Moto G4 Plus (XT1640) but I had never done anything like it, so my phone was basically the way it came out of the factory. Before all of this, my phone was using Nougat 7.0.1 (I do OTA updates). I installed TWRP and followed the steps (even some from this forum). However, at that point my phone was boot-looping in the screen "Your bootloader has been unlocked, your device can't be trusted. Your phone will boot in 5 seconds.". Despite the warning, my phone didn't boot. After a while, screen got black and the only way I could use the phone was while in the bootloader. Then, I've made wipes through the Recovery, hopeful that it'd help, but it didn't. Finally, I surrendered and went looking for an original stock ROM I could flash and maybe get things working again. Found SOME ROM that's probably the right one ("XT1640_ATHENE-RETBR_MPJ24.139-50_cid50_subsidy-DEFAULT_CFC.xml.zip") (I'm from Brazil, btw). Great, downloaded, followed steps in the forum to flash it, great, it boots again! Can login to Google, default settings stuff, etc... HOWEVER.
Then, with my phone working again, I wanted to get rid of the nasty boot screen that said my device can't be trusted, etc. So I looked it up and tried to reflash the same stock ROM as above, but now doing it so I could re-lock the bootloader. To do that, I repeated the flashing commands but added the command "mfastboot oem lock" at the end (also used "mfastboot oem lock begin" as the 1st command). Then the CMD said I had to retype the command to apply. Did that, but then the following message showed: "Waiting for signed boot.img, enter the command again" or something like that (didn't printscreen, sorry). Then I reentered the command a 3rd time and then it said "Please flash a signed ROM" or something. So, basically, it failed. After that, repeating the command just showed the last message again. Unhappy, but hopeful, I entered "mfastboot reboot" to reboot my phone. So, got back into the phone (still with the nasty "Your bootloader has been unlocked" warning) and then I basically gave up. I'm now trying to install an OTA update (for Nougat, since the ROM I installed is 6.0.1) but the WiFi download is REALLY slow (and the problem is not my internet, since I've tried downloading a couple of files in my PC to test it).
So my biggest fear is that I have a ROM that's not REALLY meant for my phone (despite looking EVERYWHERE for it) and that's causing problems with the WiFi. Maybe the OTA update is just slow in the server-side, but I'd like to know. Is there a way to get the ROM I got when I bought the phone (that EXACT SAME ONE)?! I wonder if there's a problem because of Motorola/Lenovo regional things. Otherwise, the phone works (gets 4G signal, making calls and downloading Play store updates is as far as I've tested for now). And I would also like to know if there's a way to relock the bootloader in my case(since when I tried those errors I've mentioned above happened)? What I seemed to have done is downgrade a version (since I was in Nougat and then installed a stock ROM that's 6.0.1) and I don't know where to go from here. Thanks a lot, guys! Sorry for the long post, I just wanted to describe the events in order.
There is no official source for you to get a rom. This is not a nexus. I wonder why people always want to relock bootloaders! (it seems in your case only for the 5 seconds warning). As far as i know only modem can differ but roms...
Do you still have TWRP?
if so: if you are on an N modem right now try to flash an N custom rom. If you are on an M modem flash an M custom rom.
KEEP YOU BOOTLOADER UNLOCKED and also:KEEP "OEM UNLOCKING" in developers options ENABLED AT ALL TIMES! (the last step will prevent you from a 72 hours lockout from your Google account.)
There are other ways to get rid of the bootloader warning. (flash a custom logo.bin)
I obtained an unlocked Moto E4 XT1768 from an independent retailer and rooted it using magisk and following these instructions. https://youtu.be/Pjd74W9IqHU However, I'm not happy with it as for some reason eligible apps can no longer be moved to the SD card without formatting it as an internal and was not aware it would hang on startup with an N/A message. There are other irritating issues. I also wonder if the security is less being rooted. So being a nube have nube questions related to this thread. Motorola keeps asking me to update the system software, I assume to Android 8 oreo. Is that a good idea or will it wipe out the root? Will it install properly? Can I factory reset it back to defaults by following the steps in reverse?
WXSky said:
I obtained an unlocked Moto E4 XT1768 from an independent retailer and rooted it using magisk and following these instructions.
However, I'm not happy with it as for some reason eligible apps can no longer be moved to the SD card without formatting it as an internal and was not aware it would hang on startup with an N/A message. There are other irritating issues. I also wonder if the security is less being rooted. So being a nube have nube questions related to this thread. Motorola keeps asking me to update the system software, I assume to Android 8 oreo. Is that a good idea or will it wipe out the root? Will it install properly? Can I factory reset it back to defaults by following the steps in reverse?
Click to expand...
Click to collapse
Don't accept the update; it won't apply correctly on rooted device; likely end-up in a bootloop that can be challenging to fix w/o a backup image. Probably just a security update. No Oreo for the E4...at least not from Moto.
What about restoring it to factory? Can I relock the bootloader to remove the N/A or speed up the boot?
WXSky said:
What about restoring it to factory? Can I relock the bootloader to remove the N/A or speed up the boot?
Click to expand...
Click to collapse
You can restore stock via RDSLite (Moto's partition maintenance tool) with some effort. There are a few threads floating around the E4 forums with general guidance but no step-by-step guidance. Not that difficult; attention to detail is key.
Relocking the bootloader is harder with variable outcomes. Some claim success while others never get there. Doing so will not speed up boot times; you'll just see the Moto logo longer. Replacing the boot animation effectively hides the 'N/A'; fairly easy task. Look for appropriately titled threads In the E4 themes section.
In your shoes I would focus on understanding/fixing the problem vs trying to relock the device. XT1768 is the cream-of-the-crop when it comes to E4s. It's the model I own and the only one you want if given a choice. Ya just need to do some reading to come up to speed on tools & techniques.
WXSky said:
What about restoring it to factory? Can I relock the bootloader to remove the N/A or speed up the boot?
Click to expand...
Click to collapse
It does that instead of the bootlogo. It's just the way it is for Moto. All motos. Flash a new bootlogo if you want, but it will not reduce boot time. Live with it.
The annoying boot animation still appears. Eliminating that and speeding up the boot were two of my goals after rooting it. Now it is worse. It also hangs on the N/A a lot longer than it hung on the logo.
WXSky said:
The annoying boot animation still appears. Eliminating that and speeding up the boot were two of my goals after rooting it. Now it is worse. It also hangs on the N/A a lot longer than it hung on the logo.
Click to expand...
Click to collapse
It actually doesn't. We have two E4s in the household; one unlocked, the other stock. Boot times are similar.
As mentioned, change your boot logo to obsecure the N/A. On my phone it is hardly noticable. You find a representative sample in the themes thread: https://forum.xda-developers.com/moto-e4/themes
Just wanted to do a quick update to this in case it is valuable to anyone. I was not able to do a system update but it did not fall into a loop either. It just would not take. If I had done it before unlocking it would it have updated to Nougat 7.1.2?
However, I was able to do a factory reset on it and it reset successfully but it remained bootloader-unlocked and rooted.
Hello, I really messed this up... I haven't rooted a phone in over 5 years, but just ordered a moto g7 from google fi because I wanted to play around with rooting and rooted apps again.
Setup:
-got moto drivers, adb, set developer mode, unlocked bootloader
I had tried to just root using the "simple?" method of using Magisk with the lolinet firmware files. I used the PPO files in the Official/FI dir. I thought that I had seen an error when flashing the magisk modified boot.img that there was an issue or that it wasn't valid, I (stupidly) assumed that this was like the notification you get after unlocking bootloader about invalid key or whatever. When trying to boot up it would just keep boot looping, and I went into hard panic mode... I saw other people had mentioned using retail or retus firmware on the google fi variant, so I proceeded to try to just flash those stock boot.img files after the fi one hadn't worked. I then finally got it to boot up fully, I don't even remember which firmware it was (retail maybe) and felt a little bit better about it, but had also seen that some people had said it wouldn't have the full functionality of network switching if I wasn't using the fi firmware. So... back to the fi firmware...
I was able to get it booting up on stock fi firmware, and to be honest I should have stopped there and given up on root, because I'm guessing I would have been perfectly fine up to that point... I again tried magisk modified fi firmware to no avail, and was having trouble getting back on stock fi for some reason... I followed a post to reset to stock and relock bootloader ***I'm guessing this was my major fault***, I must not have been paying enough attention to the command prompts doing this, but I think this is where I messed something up royally. It was able to boot, but then it said it had updated software to the 'PPOS' variant which I thought was strange... After attempting to reflash stock fi and then magisk fi boot.img it is failing and won't even get to boot loop.... when trying the slew of commands to flash full stock firmware I keep getting issues with the "_a" partition being not found.
At this point I can't get to recovery, or boot after attempting to flash a number of times. Any help would be appreciated, even if it is just a confirmation that I f'd this device and to stop wasting my time and give up on ever having a rooted device again lol.
Thanks for your time, and let me know if there is additional info to provide that may help.
Edit: Current status:
"Start Up Failed: Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the software Repair Assistant."
in Bootloader logs, but I don't know what software repair assistant it is referring to, i have tried connecting to pc.
Edit 2: Or I'm just a complete idiot and needed to re-unlock bootloader with the code like previous... which I totally should have known, but again, I'm an idiot...
So, now that I've got it booting up, do I attempt reflashing a magisk img or just admit I'm too stupid to do this? Or should I go with twrp which seemed like more steps and potentially more issues to run into?
Sorry for the scare and immense stupidity!