Hello,
So I tried to get CM 10 or 11 on my AT&T S4 a year ago and bricked it (so I thought). Got a Moto E and switched to Cricket. Back in November I was fiddling with the S4 and I could get it in to download mode. Odin wasn't able to see it. I formatted and restored default OS, which I think was a mistake.Samsung setup won't finish. I was really struggling to get anything to work.
Can anyone hold my hand and walk me through the steps to determine if this thing is totally useless?
Thanks!
Did you perform a factory reset/wipe before booting the newly restored rom?
Yes. 99.9% sure.
hippomofatumas said:
Hello,
So I tried to get CM 10 or 11 on my AT&T S4 a year ago and bricked it (so I thought). Got a Moto E and switched to Cricket. Back in November I was fiddling with the S4 and I could get it in to download mode. Odin wasn't able to see it. I formatted and restored default OS, which I think was a mistake.Samsung setup won't finish. I was really struggling to get anything to work.
Can anyone hold my hand and walk me through the steps to determine if this thing is totally useless?
Thanks!
Click to expand...
Click to collapse
Do you have samsung usb drivers installed correctly? If so, try another usb cable or another usb port.
The only way to restore your phone is flashing the firmware via odin.
Hey Sway,
Thanks for helping me out. Can you lay out the steps to check these things and run Odin? I've totally forgotten how to do any of this.
Thank you
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.
thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI
thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.
I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.
tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired
It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app
uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.
Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...
Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.
[HELP THREAD] Stuck in a "Your device has been unlocked and can't be trusted" loop
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
lologke said:
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
Click to expand...
Click to collapse
Ask and answered yesterday in help thread for example. Please have a look at here and the posts before and after https://forum.xda-developers.com/mo...-question-noob-friendly-t3526598/post72528225 for the message at boot.
Because of your bootloop after displaying of the message your device can't be trusted": why you install the abandoned cm14.0? Use newer LineageOS or other supported roms instead of that discontinued one.
I think it's because of the newer twrp maybe. Did you tried an older version like twrp 3.0.2? Did you tried installing the rom without gapps? Maybe the gapps doesn't play well with the old rom?
I got same problem but i solved it.. if u need to solved this problem Flash your device. It works 100%.^_^
Mariashaik said:
I got same problem but i solved it.. if u need to solved this problem Flash your device. It works 100%.^_^???
Click to expand...
Click to collapse
If you have nothing useful to say, say nothing. It can irritate new users.
I guess you should try some other ROM as suggested! You can go to Recovery by using Power+vol down Button for 5 sec... that should take u to bootloader and then recovery and other options!
Let me know if that works!
Ummm.. just read the post again... moto g4 plus (12 GB)... I hope that's a typo!
lologke said:
Hello,
I am using a Motorola Moto G4 Plus (12GB, Android Nougat 7.0) and i tried unlocking the bootloader/ flashing a custom rom because I already managed to do the same with my Moto G3.
After unlocking the bootloader I successfully installed TWRP 3.1.0 on my Phone.
I then wiped all of my data including the system and flashed Cyanogenmod 14.0 (2016-09-13 UNOFFICIAL athene) and installed open_gapps-arm-7.0-mini-20170603.
My problem is that when I booted my phone there is a message saying:
Your device has been unlocked and can't be trusted.
To learn more, visit:
motorola.com/unlockbootloader
ID: N/A
Your device will boot in 5 seconds.
And i have absolutely no way of getting rid of it or shutting down my phone. Every 5 seconds my screen turns black for like one second and the message appears again.
I would appreciate it if you guys could help me access my phone.
P.S. It's my first time posting, please tell me when I did do something wrong
Click to expand...
Click to collapse
umm. why do you flash unofficial cyanogenmod instead of lineageos?
Try flashing the latest roms, with latest twrp and see if it works or not. If it still doesn't, flash stock ROM and start again. I hope you have a backup made.
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.
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