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.
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
hey guys
i just brick my phone (no idea how, flashed android 7 firmware) after flash my phone was working for like 2 hours, then i let himself update a security options. After update my phone went brick
As far i found :
- installed Qualcoom QDLOADER 9008 driver
- found QFIL programmer
i need to have programmer path (something related to JTAG) and build xmp path
Where i can find them? Or is it a other way to resscue my phone?
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
dsnunes said:
I feel your pain. My timeline:
- The phone was unlocked but still in Stock Nougat (7.0?). Got that from OTA in Brazil.
- I tried to update to LineageOS 7 via TWRP. After a full wipe (everything, system, data, card, cache etc) I installed the new ROM. Turned on, bootlooped forever.
- Searching around I found out that there was no modem in the Nougat roms and for some reason I needed to flash a Marshmallow modem for my region to make that work (I think there is no Nougat modems around or something).
- I found a LA_DS modem for 6.0, flashed that using TWRP, still bootloop. Tried other roms using TWRP, still bootloop.
- I then downloaded a full stock old 6.0 firmware to go back to stock but the phone wouldn't accept some files ("preflash validation failed").
- Searched around and found out that you can't downgrade a bootloader from Moto.
- Using fastboot, I flashed the files the phone was willing to accept and it finally booted the 6.0 Marshmallow stock rom, but with no networking (radio/modem/baseband/IMEI missing).
- Flashed the 6.0 modem for my region again and everything worked. Connected on WiFi, dual sim cards detected etc.
- I started to install every update the phone showed to try to update it back to latest MM version.
- The three first updates went ok, the fourth turned off the phone to never turn on again.
Looks like there is no way out of this. My phone is pretty old and MotoCare in Brazil will charge a lung and a half for repair.
Click to expand...
Click to collapse
Pretty similar situation on my part. I downgraded back to 6.0 and when it tried to take the December update I ended up with the same thing as you. I ended up getting a replacement from Moto for under 100 dollars which was worth it rather than trying to find a solution that doesn't exist.
Okay guys firstly i have a hope that some one would definitely help to come out of this ....
lets directly jump into the matter
i unlocked boot loader started using Custom ROM everything was fine until i got this into my mind
planned to re flash the stock rom and to be honest i had a november patch before flashing Lineage 15.1 custom ROM or unlocking boot loader and i totally forgot to Take a back up of my Nougat 7.1.2.
Today morning when i Flashed stock Rom for my device it booted up properly, but there was no service when i checked my IMEI they were 0 and asked for an update due to wifi connectivity .. Okay this is where the problem started i used
i downloaded the update and i just gave install then it restarted and went to the boot loader saying installing updates then my phone is switched off in half way ... now when i connect it to my PC it just makes noise like it is connected but when i try to switch on it is no switching on ..... when i put for charge notification light next to the speaker keeps blinking .....
is it hard bricked ?? or is it my phone dead or literally i cannot do anything at all ?
Please........
Any help would be appreciated
not able to switch on my phone
please delete this thread ... i fixed my issue
Tried Flashing TWRP and I did what I was told, as soon as ODIN rebooted the tablet, I pressed Power+Home+VolUP, and I ended up getting a black screen with lines through it. Whenever I try to turn the Tablet off, the screen flashes. I was told to fix this by flashing stock firmware via odin. Wanted to make sure I'm downloaded the correct firmware. This is the link I'm downloading from -
https://samfrew.com/download/Galaxy__Tab__A⑥__/d0qj/XAR/T580UEU4CSC1/T580XAR4CSC1/
Also - was wondering why this happened ? I used what I believed to be the latest TWRP
Silicon Knight said:
Tried Flashing TWRP and I did what I was told, as soon as ODIN rebooted the tablet, I pressed Power+Home+VolUP, and I ended up getting a black screen with lines through it. Whenever I try to turn the Tablet off, the screen flashes. I was told to fix this by flashing stock firmware via odin. Wanted to make sure I'm downloaded the correct firmware. This is the link I'm downloading from -
https://samfrew.com/download/Galaxy__Tab__A⑥__/d0qj/XAR/T580UEU4CSC1/T580XAR4CSC1/
Also - was wondering why this happened ? I used what I believed to be the latest TWRP
Click to expand...
Click to collapse
I have no idea about the correct firmware, but I believe you used a "bad" TWRP. When I first got my tab in November I searched through all TWRP threads and kept finding mentions of those lines. I then flashed the OMNI6 version and never had an issue.
The last one is HERE - maybe try that one?
Good luck either way :fingers-crossed:
Hi, I get a notification to update magisk. then I update it and use the recommended action to update it. After that it asks me to reboot the device. After rebooting the device it goes to fastboot only. And I see the device now changes to US996 while what I have is H990DS.
Can someone explain to me what's wrong and how to fix it without losing all my data?
thanks...
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
aliks00 said:
Hi there,
all I can say is that is happened exactly the same to me just some minutes ago, I installed latest magisk update like I've been doing with no problems, just that today, after reset, its always booting stuck into fastboot mode.
I have a H910 and I also see the message about US996, maybe this is related to the method used to root the phone, If I recall correctly it had something to do with installing a US996 modified bootloader.
I still haven't found a way to get my phone back to life. All I can say is that I do manage to boot into recovery (TWRP, via the appropriate key combination at power on), so I guess I'll manage to flash something to fix this and return it back to life I hope
Click to expand...
Click to collapse
It's common knowledge that if you root your phone you never apply an OTA
Sent from my LG-H910 using XDA Labs
cnjax said:
It's common knowledge that if you root your phone you never apply an OTA
Click to expand...
Click to collapse
Thanks, but who said I ever applied an OTA? It was magisk that wanted to update itself, I've been performing magisk updates regularly for quite some time and never had a problem, in fact I can't even perform an OTA phone update as I have AT&T variant but with a different sim...
Other times, when updating magisk, I lost root but never lost the ability to boot...
I was running alpha-omega oreo with mk2000 kernel and updating rom, kernel and magisk regularly through TWRP (or direct install in case of magisk though magisk app) and never had this problem before... at least I can manage to boot from recovery/TWRP so hopefully I will soon manage to get things working again... that is, if I can copy some images to my SD card that windows insists that is corrupted but that's another story...
I ended up flashing whole rom again and everything is back to normal