Related
Hi all, Its been almost 2 years since i did an OTA update on my play and bricked it. Using the first patch that came out to fix this problem of phone not booting, i "destroyed" the bootloader or something or RadioRom and my phone does not accept any sim. it was originally unlocked.
Has anyone come up with a way to revive the play to make calls or something. cos its really depressing having a phone jus lying there wasting away, only to be brought out when needed for navigation or games.
Someone please helppppppppppppppppppppppppppppppp
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
jayact~ said:
Assuming your radio/sim is in working condition, I don't particularly see how bricking your phone can cause the phone to act like that. Have you tried flashing the stock firmware on again after it was bricked? And have you tried reunlocking the phone and putting on a custom rom/kernel?
Click to expand...
Click to collapse
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
2 years ago, I would've brought my phone to the carrier. While your warranty would have been voided, you still should've been able to tell them that it is THEIR fault that it's not working since it was their OTA update that broke the phone. At the very least, they should've been able to get you a discount on a replacement Xperia Play, or at least I think they would have if they wanted to keep a happy customer.
Waqas said:
about 2 years back, shortly after this phone came out, a problem was noted with OTA updates on unlocked bootloader.
The phone was bought "sim-free" or factory unlocked depending on which nomenclature is correct.
With an unlocked bootloader, the OTA update caused the phone to go dead.
in a haste to get the phone working again, a patch was released which broke the radio rom but got your phone to boot again. i believe the initial patch was released by BLAGUS.
well that killed my radio and now, no sim inserted works.
I reinstalled the stock firmware on it. tried several variants from different regions in the hope that it might work. was getting help from Wazz, Blagus and Bin4ry but seems they've moved on to more important projects now.
Click to expand...
Click to collapse
Alright, I understand now. I wish I knew more, so I could help you out.
Was this the patch you used? I believe I used this ftf to relock my bootloader when my phone was bricked after I accepted an OTA update, just as you did. My radio never had any issues, though.. That said, my phone was sim-locked, since I have the R800x, so maybe that has something to do with it..
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
SM-G960F/DS
RMM State: Prenormal
OEM LOCK: OFF
FRP LOCK: OFF
KNOX tripped: 1
Current binary: Custom
I just flashed TWRP, Magisk, no-verity, and the samsung root preventer disabler following the guide here. I used Magisk 16.6 (supposedly S9 is officially supported now, but it's still in beta).
Everything was going fine, then after an hour or two it froze on the lock screen, and would NOT come out of it. After a couple minutes, I held volume down and power to reboot, and it went into a soft brick.
I can't flash via download mode as it gives the error "Only official released binaries are allowed to be flashed". It gives that error when I try to start the phone or boot into TWRP as well.
So what are my options to fix this, and is it possible to prevent this in the future?
you must flash the latest firmware, yesterday I happened the same.
angel8502 said:
you must flash the latest firmware, yesterday I happened the same.
Click to expand...
Click to collapse
Man, I was hopeful ng that wasn't the case. I've already started downloading from sammobile.
So what are you going to do from here? Try rooting again? Is there a more up-to-date RMM disabler?
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
jcrompton said:
Any one else have any ideas about why this happens ? I just flashed EdyoBlue ROM after being on Soldier ROM --- all was uneventful
Upon first reboot I came to the screen about Custom Binaries --- seemed to have lost TWRP etc.
Only way out was to flash stock, lose root and I assume WAIT ANOTHER 7 DAYS !!!
Any other ideas ? Or ideas on how to prevent in the future?
Click to expand...
Click to collapse
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
LysolPionex said:
Did you also flash the rmm state bypass? I did, and I'm going to try again with v2.
Click to expand...
Click to collapse
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
jcrompton said:
Well I didn't flash anything prior to EdYoBlue ROM -- I had been running Soldier ROM for a while and it was my understanding that the RMM bypass was included in those custom ROMs and or kernels
Obviously I did something wrong
Click to expand...
Click to collapse
Oh... Yeah I don't know about that.
Same problem. Samsung Galaxy S9+ (SM-G965F)
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
1AussieTradie said:
I rooted my Samsung Galaxy S9+ (SM-G965) yesterday with
Odin, Magisk (modified version as official verson doesn't work apparently) and TWRP.
Took about 10 minutes to do all up, and root was successful!!! 20 minutes later it turned itself off!! No matter what i did or tried.....I couldn't turn it back on nor get into recovery (TWRP). All while it was constantly flashing........ (ONLY OFFICIAL RELEASE BINARIES TO BE FLASHED)
Figured it was somehow a soft brick. So i flashed original firmware back onto phone with Odin and all was well. ILL BE TRYING A NEW WAY AND WILL POST RESULTS.
Click to expand...
Click to collapse
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
same issue i had to re flash the stock OS & wait for 7 days for OEM unlock now i have that option but i am not sure which method should i use.
RMM STATE PRENORMAL is also what blocks custom binaries from being flashed
Check the TWRP guide on how to deal with that too
LysolPionex said:
What's the new way? Are you able to flash again already, or do you have to wait 7 days again?
Click to expand...
Click to collapse
Unfortunately no success. Have to wait the 7 days . Currently trying to find a work around. Will keep informed.
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
rockykv2 said:
Any news I got my OEM unlock back any way to root the phone and get a custom firmware to work
Click to expand...
Click to collapse
Once my RMM status is normal, I'm going to try Soldier's Rom. I've heard good things about it.
You'll need to follow the official TWRP guide first. Both in this S9 forum.
I already tested that It gets stuck on welcome screen it will not go forward
rockykv2 said:
I already tested that It gets stuck on welcome screen it will not go forward
Click to expand...
Click to collapse
I'd ask about that in the soldier Rom thread; sounds like it might be a wipe issue (really not sure), but a ton of people love the Rom, so it's probably something random on your end.
I'd stick with a stock-based rom, as they're usually more stable.
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
jonathan_moreno91 said:
That Max Lee tutorial about s9+ root is outdated. He is a ****ing bull****. He did not even cared to update his post that magisk root method always freeze. And also his rmm unlock fix is not updated too. Did you guys have the august 1 security update? I guess that was the cause of this "Only official binaries allowed" after rebooting. Here's hoping somebody here got an answer for that RMM.
Click to expand...
Click to collapse
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
LysolPionex said:
That's kinda the general consensus I've gotten about that tutorial.
I was using the August 1 security update, but I was using v1 of Mesa's RMM bypass. I downloaded v2, and downgraded my Rom to like April or March or something and will try it again, once the prenormal clears.
RMM v2 is here:
https://forum.xda-developers.com/sa...nuary-security-patch-sm-t3739225/post75360965
Click to expand...
Click to collapse
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
jonathan_moreno91 said:
Bro if you are on august 1 security update too then you are in xu2 bootloader... you cannot downgrade to xu1 bootloader which was before august..
Click to expand...
Click to collapse
Really?! This is literally the first I've heard of this. Do you know if there's a thread discussing this?
I unlocked the bootloader & have root (Nemesis Kernel) on my N975F. The BL Unlock/TWRP/root was done using this method from geiti94.
I'm running baseband N975FXXU1BSL4 and would like to update to apply latest security patches, but don't know the correct procedure given some of the hurdles of the N10+.
Can anyone point me to the best way to update and retain root without doing a total wipe in the process? I tried just switching kernels by flashing the Cruel kernel, but that just boot-looped on me so clearly the process is delicate back in the good-old-days with my S3.
Thanks in advance
Youre propably going to have to use odin to flash each update and then reroot afterwards. You could use home_csc to retain your data but i think it will still wipe out root. i just came from huawei so im still trying to get my bearings but i believe that's the right step. If anyone else could chime in and correct me if I'm wrong?
hello, im new to android rooting, and i wanna attempt using magisk on my main phone (a325f) but i do not know if the ability to unlock the phone with the fingerprint will no longer be available after i unlock the bootloader, and im not too sure...any answer?
There aren't enough people who rooted that phone to decide if all models in all countries are safe to root with no issues, I'd say wait till Android 13 update
Hi, I'm currently using rooted A325F-XID (Indonesia Region) and the Fingerprint Sensor is working with One UI Firmware (A325FXXU2BVG3).
But If you want to use GSI ROM, the fingerprint not working at all (the UI crashed), and the fingerprint is working again if it restore with Stock ROM (One UI). But recently I had bug with the mobile data is turned off every 2 minutes in latest One UI Firmware (A325FXXU2BVH1) but it fine before that firmware. I'll report if the bug is fixed on next firmware update
mariangxzyy said:
hello, im new to android rooting, and i wanna attempt using magisk on my main phone (a325f) but i do not know if the ability to unlock the phone with the fingerprint will no longer be available after i unlock the bootloader, and im not too sure...any answer?
Click to expand...
Click to collapse
Hey, I'm using A325F-XDA (South Africa) with root through magisk, the only thing you have to do to ensure everything works is to flash Android 12 April patch, because for some reason the latest patch causes the phone to loose signal for a few seconds every 5-10 min but with the April patch, myself, Captain_cookie_200 and a few others have found 0 problems so far, but if you do decide to unlock your bootloader and root please keep in mind you WILL TRIP KNOX and some features will not work such as Samsung pay, secure folder and some other Samsung security features, but there are some speculation that you could get Google pay/Wallet to work. If you need any help feel free to message me.