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?
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.
Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome
Hey there folks, so did anyone tried to Downgrade from 11 to 10? is it safe? or it can cause Hard Brick on our devices?
Blackbird918Sr said:
Hey there folks, so did anyone tried to Downgrade from 11 to 10? is it safe? or it can cause Hard Brick on our devices?
Click to expand...
Click to collapse
I did that, then my phone was bricked and i must bring it to service center to fix. I think that process triggered android verified boot (anti rollback). You can try to fix using QFIL and EDL flash but not recommended (can't use Miflash because you cannot flash through EDL without xiaomi authorized account)
rain_effect said:
I did that, then my phone was bricked and i must bring it to service center to fix. I think that process triggered android verified boot (anti rollback). You can try to fix using QFIL and EDL flash but not recommended (can't use Miflash because you cannot flash through EDL without xiaomi authorized account)
Click to expand...
Click to collapse
That's not necessarily the case with this unbrick file. You do not need an authorized account to flash in edl using QFIL with the unbrick files
The Anti-Rollback was actieve since 10 but While 10 was out, because of TWRP and other recovery some users were able to rollback. and for 11 there isn't any Recovery that could flash a rom properly
is not a good idea... wait the uptades... also the initial release of a10 was buggy... my suggestion is make a clean install of a11 december patch. is very stable. better than january... otherwise wait february update
I Think it's Worse then January however i am doing a Factory Reset lets hope for the best
Blackbird918Sr said:
Hey there folks, so did anyone tried to Downgrade from 11 to 10? is it safe? or it can cause Hard Brick on our devices?
Click to expand...
Click to collapse
Try lot of methods like flash stock 10 by recovery 9 pie and by fastboot rom to but no luck yet but still trying hope any dev will do any thing abt it.
You can try with miflash tool via edl mode. But i'm not shire. downgrade is a bad idea. Maybe you can do but problably you may have some issue
Hello,
I tried to downgrade from G981U1UEU1DUB7 to G981U1UEU1CTKJ (both Android 11).
After odin it failed to get pass bootloader. It gave me the option of factory reset. I didn't want to lose my settings.
Flashing back to DUB7 revived the phone. I really want to get back to CTKJ because Samsung disabled third party fast chargers.
Any idea guys?
fatwok said:
Hello,
I tried to downgrade from G981U1UEU1DUB7 to G981U1UEU1CTKJ (both Android 11).
After odin it failed to get pass bootloader. It gave me the option of factory reset. I didn't want to lose my settings.
Flashing back to DUB7 revived the phone. I really want to get back to CTKJ because Samsung disabled third party fast chargers.
Any idea guys?
Click to expand...
Click to collapse
Back everything up and wipe data/factory reset when it boots to stock recovery and it'll boot..if not you're stuck i suppose
Were you ever able to downgrade from DUB7? I'm currently on DUB7 on my S20 and want to downgrade to a firmware with UI 3.0 so I can root my phone.
scarletwahoo said:
Were you ever able to downgrade from DUB7? I'm currently on DUB7 on my S20 and want to downgrade to a firmware with UI 3.0 so I can root my phone.
Click to expand...
Click to collapse
Did you find a way??
I am currently on UI 2.5 and want to upgrade to 3.0 but want to find the correct firmware that is rootable..
Hello guys,
Last week i updated my phone to MIUI 13 EEA rom. Phone came in a bootloop right after the update. Did a factory reset. Debloated with ADB fastboot tool. Everything seemed fine until i downloaded some videos. The next day all the folders were empty, the files just disappeared.
Now i want to downgrade to MIUI 12 but i have to wait 168 hours before i can unlock the bootloader.
I was wondering if more people have this problem and if there is a fix.
mierlo420 said:
Hello guys,
Last week i updated my phone to MIUI 13 EEA rom. Phone came in a bootloop right after the update. Did a factory reset. Debloated with ADB fastboot tool. Everything seemed fine until i downloaded some videos. The next day all the folders were empty, the files just disappeared.
Now i want to downgrade to MIUI 12 but i have to wait 168 hours before i can unlock the bootloader.
I was wondering if more people have this problem and if there is a fix.
Click to expand...
Click to collapse
FIX ? INSTALL A CUSTOM ROM
jefffrom said:
FIX ? INSTALL A CUSTOM ROM
Click to expand...
Click to collapse
I don't like custom roms. They always come with a lot of downsides, and i don't have time to tinker with my phone all the time. I did that so much in the past, and i am too lazy these days
mierlo420 said:
I don't like custom roms. They always come with a lot of downsides, and i don't have time to tinker with my phone all the time. I did that so much in the past, and i am too lazy these days
Click to expand...
Click to collapse
but xiaomi.eu is a custom ROM pretty clean and fast, it's better than EEA
I use Xiaomi.eu Custom ROM and updating from Android 11 to Android 12 I had some problems, which I expected.
But it's not acceptable that your phone gets in a Bootloop on a Stock ROM with locked Bootloader... So I feel your frustration.
I think you might not even need to unlock the bootloader to downgrade:
He uses a bug in the MIUI Updater-App to install an Update which is actually a lower version. And I think it's even safe to do. You should try it.
I found that video through a conversation I had with someone on Reddit.
jefffrom said:
FIX ? INSTALL A CUSTOM ROM
Click to expand...
Click to collapse
Not everyone wants to do that.
There are some significant downsides to even just unlocking the bootloader.
I just had a similar problem. It's an old problem I had that somehow got fixed temporarily without my knowing. Then last night it happened again!