[delete me]
Got a similar problem where I can't even access fastboot.
Looks like there are soft bricks that totally mess up your phone.
Flashed stock via Odin but I'm still in a bootloop :good:
Unbelievable. I even read posts by people with similar problems who are on stock ROM and have neither unlocked the bootloader, nor rooted the device. That makes me assume the fault is not really at my end, is it?!
Mine received an OTA update to Jelly Bean, crashed and the bootloop occurred.
Wasn't rooted or anything. Very weird
It may help to try re-locking the bootloader. I had a similar issue which and was able to get the phone to become responsive again after re-locking the bootloader and then re-flashing a factory image.
domimatik said:
Mine received an OTA update to Jelly Bean, crashed and the bootloop occurred.
Wasn't rooted or anything. Very weird
Click to expand...
Click to collapse
What did you do then? Returned it and got a replacement phone?
-Alex said:
It may help to try re-locking the bootloader. I had a similar issue which and was able to get the phone to become responsive again after re-locking the bootloader and then re-flashing a factory image.
Click to expand...
Click to collapse
Isn't it impossible to flash anything with the bootloader being locked?
I tried flashing a factory image with unlocked bootloader and then locking it after that...
boype said:
What did you do then? Returned it and got a replacement phone?
Click to expand...
Click to collapse
I'm still trying to fix the problem by playing around with Odin but I'm running out of ideas.
Related
After upgrading to 5.1.1 using odin because 5.0.2 was rooted, my T-Mobile edge has issues. Dropping calls (I use AT&T it is unlocked), keyboard not working (Typing random letters that I dont even touch), and a bit laggy (I did have it factory reset). Also, I read this thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
and it says:
"Unlocked Phones: If you have unlocked your phone, you might run into problems with 5.1.1. There have been reports of phones stuck in a boot-loop when upgrading from 5.0.2 -> 5.1.1 when the phone has been unlocked or EFS/IMEI has been tampered with. Combine this with the new "FRP LOCK" (Factory Reset Protection) in 5.1.1, and you might find yourself with a complete brick with no warranty. This issue may or may not have anything to do with rooting or custom firmware:"
So is it safe for me to root/get TWRP? My phone is unlocked but I am kind of afraid with this FRP Lock. And is there a way to fix my problems? Maybe all the bloatware is causing this or I can get some ROM to fix it
smoosani97 said:
After upgrading to 5.1.1 using odin because 5.0.2 was rooted, my T-Mobile edge has issues. Dropping calls (I use AT&T it is unlocked), keyboard not working (Typing random letters that I dont even touch), and a bit laggy (I did have it factory reset). Also, I read this thread:
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002
and it says:
"Unlocked Phones: If you have unlocked your phone, you might run into problems with 5.1.1. There have been reports of phones stuck in a boot-loop when upgrading from 5.0.2 -> 5.1.1 when the phone has been unlocked or EFS/IMEI has been tampered with. Combine this with the new "FRP LOCK" (Factory Reset Protection) in 5.1.1, and you might find yourself with a complete brick with no warranty. This issue may or may not have anything to do with rooting or custom firmware:"
So is it safe for me to root/get TWRP? My phone is unlocked but I am kind of afraid with this FRP Lock. And is there a way to fix my problems? Maybe all the bloatware is causing this or I can get some ROM to fix it
Click to expand...
Click to collapse
There is no rom to fix this, bloat will not cause these symptoms, since you are on odin 5.1.1 you won't have an option to unlock bootloader (disable frp) .
Rooting or installing trwp could be risky and dangerous, one wrong flash and phone security can trigger frp, and that would be the end of your S6edge.
Your safest procedure would be to odin stock Samsung firmware and wait for appropriate official updates. Stock firmware will fix all your issues.
Pp.
PanchoPlanet said:
There is no rom to fix this, bloat will not cause these symptoms, since you are on odin 5.1.1 you won't have an option to unlock bootloader (disable frp) .
Rooting or installing trwp could be risky and dangerous, one wrong flash and phone security can trigger frp, and that would be the end of your S6edge.
Your safest procedure would be to odin stock Samsung firmware and wait for appropriate official updates. Stock firmware will fix all your issues.
Pp.
Click to expand...
Click to collapse
I did Odin stock 5.1.1. Ever since then its been happening. But for some reason when I did stock 5.1.1, my apps were still there. I would expect it to be a full wipe so I manually factory resetted after.
smoosani97 said:
I did Odin stock 5.1.1. Ever since then its been happening. But for some reason when I did stock 5.1.1, my apps were still there. I would expect it to be a full wipe so I manually factory resetted after.
Click to expand...
Click to collapse
I would reflash stock trough smartswitch that will wipe the phone clean before flashing
Sent from my SM-G925T using Tapatalk
PanchoPlanet said:
There is no rom to fix this, bloat will not cause these symptoms, since you are on odin 5.1.1 you won't have an option to unlock bootloader (disable frp) .
Rooting or installing trwp could be risky and dangerous, one wrong flash and phone security can trigger frp, and that would be the end of your S6edge.
Your safest procedure would be to odin stock Samsung firmware and wait for appropriate official updates. Stock firmware will fix all your issues.
Pp.
Click to expand...
Click to collapse
I wish I could offer any advice, but I just wanted to let you know that my experience with 5.1.1 echoes yours entirely, with the lovely addition of it getting so hot I cannot hold it and the battery draining within two hours.
**sigh**
-Collin-
papi5120 said:
I would reflash stock trough smartswitch that will wipe the phone clean before flashing
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Would I need to have OEM switched on or off? I hear some people that try flashing and screwed up their phone with it off? Like if I use SmartSwitch, will I run into any FRP issues and screw up my phone?
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.
As the title states, I successfully sideloaded the most recent ota since I couldn't find a proper guide to flash the factory image (nor the proper image for that matter). Checking the kernel and what not everything appears to be stock, and I know I don't have root anymore or any of the apps that go with that.
This being said, will I be able to relock the bootloader? I need to return my phone to Verizon and want to make sure the phone is as factory as I can get so they don't get all up in my face about it.
or.....
Will the fact that my bootloader is unlocked but nothing else has been changed be acceptable to return the phone? Anyone know from experience?
Anthony825 said:
As the title states, I successfully sideloaded the most recent ota since I couldn't find a proper guide to flash the factory image (nor the proper image for that matter). Checking the kernel and what not everything appears to be stock, and I know I don't have root anymore or any of the apps that go with that.
This being said, will I be able to relock the bootloader? I need to return my phone to Verizon and want to make sure the phone is as factory as I can get so they don't get all up in my face about it.
or.....
Will the fact that my bootloader is unlocked but nothing else has been changed be acceptable to return the phone? Anyone know from experience?
Click to expand...
Click to collapse
I doubt they'd care but the warning when turning the device one might. Anyways, I believe after a flash of the full factory image, you should be able to relock the bootloader.
Don't hold me liable for anything, but I'm almost certain that you just need to be running stock everything.
Sent from my Pixel XL
I couldn't do the factory image flash. Couldn't find exactly everything I needed and didn't want to chance guesswork. So I side loaded the most recent ota and it appears I'm stock everything....
Anthony825 said:
I couldn't do the factory image flash. Couldn't find exactly everything I needed and didn't want to chance guesswork. So I side loaded the most recent ota and it appears I'm stock everything....
Click to expand...
Click to collapse
Hey man, you ever managed to relock your bootloader? I'm thinking of doing it too since I may need to RMA mine as well.
Hello,
I own the 32gb h791 nexus 5x and the phone is bootlooping after android 7.0 update.
so basicly the phone showing google logo and then reboot back..
My bootloader is unlocked, so I tried to flash marshmellow without any success.
I can not access the recovery.
I saw a thread about flashing tot but i read in the thread that It is re lock the bootloader.
I dont have efs backup..
Any help?
Thanks,
Nimrod
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
But that's a hardware bootlop no software
How many files had been flashed when you've tried to flash it? If any, have you done any modifications like root etc ?
If no, just lock bootloader and send RMA
If you can send to Google, you don't have to lock bootloader.
If your warranty expired, try to talk to Google may they will give you a replacement anyway, if not Google, you can try to LG because of 15mo warranty from production date
TypNguy said:
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
Click to expand...
Click to collapse
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
His problem is a hardware issue not software. Might get lucky and volte it back to life but I highly doubtful . LG notorious for certain models that infinite bootloop issue g4 was the worse.
Yes, the root toolkit worked for me. I still don't know how to flash correctly, so if you have the right driver's associated with your phone/laptop it should be a breeze. The best part is that there's a log, so you know what the toolkit is doing. For example, it may unroot your phone before it flashes the new stock image for you.
---------- Post added at 02:40 AM ---------- Previous post was at 02:36 AM ----------
Just found wugfresh's answer to your question I think.
Link
Address: http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
Hello all!
I've gotten too lazy to maintain updating my rooted Pixel XL whenever there's a security patch.
I've re-locked the boot-loader and done a full stock flash from google's stock images, but now i get this warning when it boots up:
"Your device has loaded a different operating system. "
It then boots up fine, barring the fact OTA's still fail, the one thing I was trying to get working.
Any advice?
Thanks in advance.
You skipped flashing the bootloader and radio without those ota will fail.
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Help me
Vacross said:
Am i mistaken in thinking the "flashall.bat" from google does that as well?
Thanks
Edit.
Think i found it, your comment made me watch for the radio and boot-loader when i tried the flash-all batch script again, I believe i Locked the boot-loader before flashing it to stock again.
Unlocked, flashed, re-locked and it appears to be working now.
Thanks!
Click to expand...
Click to collapse
Can you help me... I have same problem...
DR3W5K1 said:
You skipped flashing the bootloader and radio without those ota will fail.
Click to expand...
Click to collapse
Can you pls explain on how to do that
Follow the guide for flashing stock images via fastboot and you shouldn't have this problem.
Stop after step 4
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I also had the same issue on Nexus 6p.. after I realised that I forgot to flash boot.img from stock firmware.. anyway it is resolved...
UI Design Services with Compelling and Engaging User-Experience
Get user-centered UI Design for your mobile app or website.
UI Design services