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
Bought a OTG from China, used one, left plugged into the phone as I slept...don't know if it's the cause of my troubles to start happening, or if the Twitter app I installed at the same time is the cause.
The phone became TROUBLE and I eventually decided to try going back to stock. I did manage to get stock on but couldn't use because the phone immediately would display the dreaded "Unfortunately.......", which pops up so often that you cannot do anything. So I decided to do a full wipe from factory recovery. Since then, the phone wont power on at all! I have left it to charge overnight, all day, NO POWER!!!! I have read many similar accounts. I lost as what to do! I had ZERO power issuses before. Saw a vid where a guy says the power switch is faulty. He ordered one from eBay and replaced it. 1) I don't think it's the case. 2) don't think I wanna try soldering, etc.
Any help would be appreciated!!!
I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.
Wow! NOBODY?!
kojam said:
I have the 910W8 from Rogers in Canada. ODIN flashed with no problems (used the latest firmware from sammobiles for my phone) but would get that error after the flash, causing it to be unuseable. I flashed a second time and same thing. That's when I decided to do a wipe from recovery. Now it won't boot up.
Click to expand...
Click to collapse
Cannot believe nobody has replied. I did get one of the usb things from a very nice member (i have to register myself as someone who now has one) but the phone is still not working.
Having done some confusing reading to try to fix mine but don't think i can.
Wondering if there's a good, reliable, store in the GTA (north end preferrably) that can do repair with JTAG? Wondering if there's any hope in recovering this phone. I get the impression that there's a good chance JTAG repair can bring it back to life.
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.
Updated with AU March update and reinstated TWRP and root - all good. Did a backup of this - all good.
Then restored Havoc OS3.12 and ended up hard bricked - unable to enter recovery or bootloader and a new error screen.
Anyone seen this and recovered from it?
O.K, gave the phone 24hrs sitting in the corner to think about things and gave it another go. Managed to fluke getting into bootloader and reload stock O.S. Re-establish TWRP and quickly install ProjectSakura to get away from the Samsung tricks and traps. Seems to be getting harder and harder to avoid falling down the rabbit hole with every Samsung update Thankfully this phone isn't elevated to primary phone status and never will because it is crap.
Thanks for sharing.
Do you still have issues and need some help?
A while back I discovered my OP6T running /e/ OS had a crack in the back glass. OnePlus very helpfully repaired it at a reasonable rate, and very UNhelpfully flashed it back to OxygenOS 11. I figured, no issue, I got /e/ on the device on my own last time, I'll be back up and running by this afternoon.
I'm an idiot, apparently.
I'm not sure what I did, but when I attempted to flash the recovery I ended up on the Qualcomm Crashdump screen. Luckily, I knew from my experience with the 9 Pro that I could use the MSM Download tool to save my device. I did so, but it reloaded it to Android 9. I expected to be able to go into System Updates and upgrade to 11, but the device is insisting that my version of Android is up to date.
Now looking at /e/'s install doc it appears that the device needs to be on the latest possible firmware before any flashing can take place. Is there anyway I can "force" an OTA update to take place? Or (gulp) execute another flash to get the device on 11, and then to /e/?
There's not a huge rush on this given that this is simply a backup device to my 9 Pro, but the thing about backup devices is they need to be ready at a moment's notice, hence why I would like to get /e/ back on my device. Anyone know of a solution to this?
Thank you and Merry Christmas to all!
Nevermind, figured out how to do a local upgrade that got me where i needed to be!