I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well looks like I can go into the bootloader but if I choose recovery mode it just goes back to the "Device is corrupt screen".
toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I don't have a backup of the tmobile rom :/ I think we ned the modem files from the tmobile version, which would be on my phone yet if I could acess them? The last time I did anything with a phone was the OP6 I'm out of my depth...
hiryupd said:
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I dont have a backup of the tmobile rom :/ The last time I did anything with a phone was the OP6 Im out of my depth...
Click to expand...
Click to collapse
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom
toyanucci said:
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom
Click to expand...
Click to collapse
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/
hiryupd said:
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/
Click to expand...
Click to collapse
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember
toyanucci said:
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember
Click to expand...
Click to collapse
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....
hiryupd said:
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....
Click to expand...
Click to collapse
I got it done with the 7T so it can be done and if you had restored the stock boot image with magisk before you uninstalled it then you are stock, just with an unlocked bootloader.
Re updates, again if you have the stock boot.img restored you'll get Ota updates just fine.
hiryupd said:
I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.
Click to expand...
Click to collapse
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.
inspron said:
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.
Click to expand...
Click to collapse
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?
hiryupd said:
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?
Click to expand...
Click to collapse
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.
hiryupd said:
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.
Click to expand...
Click to collapse
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Well system update always comes back saying it has a problem and cant update. Also yea after I relocked It has a dialogue asking if im sure because it will do a full wipe, just like when I unlocked it. But instead of doing the full wipe it booted into that red text about being corrupt. So right back here again
toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
I wish I had seen this part prior. I flashed img about 3 weeks ago prior to this method was known to me.
toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.
inspron said:
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.
Click to expand...
Click to collapse
I exported them a while ago on a thread, we just moved our company so i dont have those systems and drives set up for me to get on server. We unbrick and all that fun stuff. If you have a telegram send me the info. & ill add you to try to resolve your issue.
Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...
oh
hiryupd said:
Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...
Click to expand...
Click to collapse
if that's the case you can flash with official build, and then you can add the t-mobile bloatware if you want.. Which i take it off most phones by request.
Official Build (Direct DWLOAD)
(Stock - Boot.img (Direct DownL)) Instead if easier...
If you really want the bloatware back that makes T-Mobile T-Mobile then.. here ya go..
pm install -k --user 0 com.mobitv.client.tmobiletvhd
pm install -k --user 0 us.com.dt.iq.appsource.tmobile
I want T-Mobile Boot Up Animation! I Want People to know im using T-Mobile!!
Here ya go, "https://www.hongkiat.com/blog/change-android-boot-animation/" - Add Sound even
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I Hope this helps ya mate ..
You can also use these files I built to follow this post too if you need more help.
BACK TO STOCK 1+9
Related
Hi Guys, as subject really! Is it possible to get the phone in a "Google" state to pull down updates, obviously meaning the impending ICS one!
B
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
frutelaken said:
I'm implying that you're on a custom ROM at the moment. You'll have to flash one of the stock ROM images, then you can get OTA's again.
It doesn't matter if you're rooted or have an unlocked bootloader.
Greetz
Click to expand...
Click to collapse
Hey mate, thankyou for helping. I've not actually received it yet, bought one off ebay and I am just pre-empting - If you flash stock does the root and unlocked bootloader become standard again??
(I'm upgrading from an old Galaxy 3, so am reasonably familiar with flashing, but want a simple life now and am going stock Google )
B
Nope, flashing a stock image will not affect your bootloader being unlocked. You'll have to run the "fastboot oem lock" command to lock the bootloader again. Check one of the turorials here
Greetz
//edit: Actually, I'm suddenly not sure of this. Sunday evenings' got me confused. Please wait for someone else to verify.
Thankyou I'll have a look round
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
n00bfuscator said:
I have been flashing several ROMs using ROM Manager and the bootloader wasn't affected by this. The stock OTAs kept unrooting the phone though.
Click to expand...
Click to collapse
That's normal, the OTA's reset the permissions on key folders, effectively SU looses it's execute permissions, removing root. What i do now is download the OTA to the SD card, apply it, re-apply the SU.zip to keep root, modify the restore-recovery script so i can keep CWM, then reboot.
I'm not sure how it's going to go with ICS, but we shall see.
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
robocuff said:
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
Click to expand...
Click to collapse
Thank you, then I'll have to buy the full version of app
coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
cntryby429 said:
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
Click to expand...
Click to collapse
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
coderch123 said:
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
Click to expand...
Click to collapse
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
cntryby429 said:
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
Click to expand...
Click to collapse
Here's a picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
cntryby429 said:
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
Click to expand...
Click to collapse
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
coderch123 said:
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
Click to expand...
Click to collapse
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
dottat said:
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay. I checked it with fastboot getvar all and it is stock, there's nothing wrong with it. S-ON and locked bootloader.
using OnePlus 9 5g from tmobile and looking to convert to internation.anyone had any issues or tips to make sure I don't mess up?
So I come from the OnePlus 9 Pro forum, but the tips are identical because pretty much the same phone except for a few differences.
1. DO NOT FLASH BOOTLOADER
I can't stress this enough, flashing the bootloader will render the MSM tool that OnePlus provides for you USELESS! I figured this out the hard way!
2. Make a full device backup, if you're rooted already use Partitions backup and restore available on the Play Store
3. Keep OEM UNLOCKING ON THE WHOLE TIME! Don't turn it off until and unless you return to complete stock using a MSM tool! Also, keep your bootloader unlocked please.
4. Don't trust random "conversion" folders that flash everything at once without looking at the files, ESPECIALLY not without looking at the .bat file(s) such as a flashall.bat.
Sounds too risky. It's not so simple anymore .
Can I ask a clarifying question @razercortex ? You're saying to not flash the bootloader; does that mean I could simply take the boot.img, do the magisk thing to it, and at least have root? I don't wanna brick my T-Mobile variant here, but I really want to have root.
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
What if I don't want root, just international version
I am interested to switch from T-Mobile variant to international as well.
Josh McGrath said:
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
Click to expand...
Click to collapse
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
inspron said:
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
Click to expand...
Click to collapse
Do you have magiskhide enabled?
inspron said:
When you run the Safetynet check in Magisk, does it show "pass" ? Mine failed check.
Click to expand...
Click to collapse
Im showing to be passing. There was a magisk issue a week ago or so that cause it to fail but it was updated.
Playstore shows "Device is certified"
I really want international myself. This battery is complete garbage and tmo likes to drag their feet on an update the international got to fix the battery issue weeks ago
jfsat said:
Can I ask a clarifying question @razercortex ? You're saying to not flash the bootloader; does that mean I could simply take the boot.img, do the magisk thing to it, and at least have root? I don't wanna brick my T-Mobile variant here, but I really want to have root.
Click to expand...
Click to collapse
@jfsat If you just want root, patching the boot.img with magisk should be good enough. Just don't forget to keep OEM unlocking checked and keep the unlock code just in case. Also, don't relock until you have flashed stock boot.img.
Josh McGrath said:
You don't need to do any of that to root. I'm running the tmo variant and have had root since I unlocked it.
Just grab the rooted boot.img and Fastboot BOOT! THE IMG, run magisk and choose direct install and restart then you got root. If you flash anything, you'll be in trouble most likely so just Fastboot boot boot.img
Click to expand...
Click to collapse
It literally does not matter, but I would recommend flashing the boot.img instead because I don't know what the Direct Install method does to your phone's firmware. Flashing the boot.img works great, it only touches your boot partition and if you have the stock boot you can just flash it back and relock it, no problem. Direct Install could potentially change something else though it looks like it could be fine, but YMMV.
inspron said:
I am interested to switch from T-Mobile variant to international as well.
Click to expand...
Click to collapse
I know how to do it, you need to extract payload.bin from the EU OTA and flash all the partitions, find a tutorial online. Just make sure to make a full backup using Partitions backup and restore on the play store or manually dump partitions from your phone. You don't need userdata, it's too big and probably incompatible with the region change, just a side note that flashing partitions in the super partition (system, vendor, product, system_ext, odm, etc.) requires you to be in fastbootd, so use fastboot reboot fastboot to do so. Other than that, make sure there's an MSM tool available, you can check with OnePlus support.
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock? I had Grapheneos installed, decided to go back to stock. Even though I followed the instructions for uninstall, If I flash stock ROM I get bricked. If I flash latest ota, my phone boots up and restores OK, but I can't re- lock OEM lock (grayed out) If I try the same things on slot B neither one will boot. So I am thinking maybe Graphene reformatted something? It's been years since I messed with this stuff, back when android would let me install viper4android! I rescued my Moto x4 several times and still have it running as a music streamer. Not so easy on Pixel 6a. I don't really want to root right now, I have considered Lineage, but would just like to get back to stock with OEM locked for now. BTW latest android 13
Click to expand...
Click to collapse
There is no TWRP for this device. To get back to stock and re-lock your bootloader you can try Android Flash Tool or Pixel Flasher.
LankiCat said:
Can I use TWRP to reformat my memory and reinstall stock?
Click to expand...
Click to collapse
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Did you erase the GrapheneOS Android Verified Boot key before you went back to stock?
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
At the bottom of the articel is described how to erase the key.
WoKoschekk said:
No, you can't use TWRP
What means brick? Bootloop or dead phone?
Click to expand...
Click to collapse
I starts to boot, then it goes to white Google screen and stays there until I force it to reboot.
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
WoKoschekk said:
At the bottom of the articel is described how to erase the key.
Click to expand...
Click to collapse
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
LankiCat said:
I'm not 100 percent sure I did that. Is there way to do it if I didn't? Re-install and then uninstall Graphene again? Or just try Android Flash Tool or Pixel Flasher as Lughnasadh suggested?
Click to expand...
Click to collapse
It's described on that page. Just do what the say and all is fine.
It's just one fastboot command. Thereis no reason to find a workaround or sth.
WoKoschekk said:
It's described on that page. Just do what the say and all is fine.
Click to expand...
Click to collapse
I really appreaciate the help, but, the page says: Before flashing the stock factory images and before locking the bootloader, you should erase the custom Android Verified Boot key to untrust it. Since I have already flashed the factory stock image I want to be sure that will work and not cause more problems. It takes a really long time to flash stock with all the setup, updates, restore, and re-loading apps to get back where i need to be. Thanks again for you input.
LankiCat said:
Since I have already flashed the factory stock image
Click to expand...
Click to collapse
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
WoKoschekk said:
Then it is no longer necessary to delete this key or it has already been removed before. The only job of that key is to verify the device before something gets flashed.
Does your phone still stops booting?
Click to expand...
Click to collapse
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
LankiCat said:
No, It's running. The original problem was it locked up when I flashed factory image, once I was able to get it to recovery, I sideloaded the OTA and that worked to get it up and running. Just no OEM lock -greyed out
OK I decided to try the Graphene cutom key erase. CLI said it was successful but as I suspected OEM still greyed out as "Bootloader is already unlocked"
Click to expand...
Click to collapse
Then run fastboot flashing lock
WoKoschekk said:
Then run fastboot flashing lock
Click to expand...
Click to collapse
yeah, tried that too. I'm going to have to wait until this weekend when I can afford some downtime on my phone.