How do I update to the march patch with twrp installed? - Nexus 6P Q&A, Help & Troubleshooting

When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?

UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.

UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
You can't flash an OTA with TWRP, and you can't take an OTA if you have root/modifications. If you've never rooted or modified in any way you should be able to just flash the stock recovery back and then initiate the OTA process. If you do have root you need to flash the factory images to update. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Sr Vincenzo said:
I'd assume that you have to manually flash it with the zip. I'm not sure how it is with a 6p, but with my Oneplus devices that's how it worked.
Click to expand...
Click to collapse
This is why it's best to stick to giving advice for devices that you own and are familiar with.

Heisenberg said:
This is why it's best to stick to giving advice for devices that you own and are familiar with.
Click to expand...
Click to collapse
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.

Sr Vincenzo said:
I understand that. However it was just an assumption, i never said it would actually work. I'm still trying to learn this device myself as it is my first and only Nexus.
Click to expand...
Click to collapse
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.

Heisenberg said:
Ok, but you need to realise that people could still try whatever you're assuming and posting here. If what you're posting is incorrect, it could cause major problems for them. What I'm saying is this: do your learning for this device first, and then advise people one you know the information you're giving is solid.
Click to expand...
Click to collapse
Alright man...

Some people should never unlock their bootloader or root their phone.

UntamedTyrant said:
When I got my phone last month, I unlocked the bootloader and installed TWRP. I just got the march OTA and it will not update. It just boots into TWRP and doesnt update. How do I update to the newest patch?
Click to expand...
Click to collapse
I used Heisenberg's method yesterday and it worked well. If you copy the commands into notepad, edit them so the file paths and build numbers are correct you can just copy/paste into the command prompt. All settings will be saved with the exception of a couple of widgets I had to redo.
I will say with the latest update the device seems faster so I feel like it is worth it.

Related

Reverting 5.0 to 4.0 OS

I recently updated to the developers preview of Fire OS 5.0 and I had TWRP installed and I was not able to downgrade using the ADB sideload method. So for people that have the same issue here is what you need to do to resolve this and get back to Fire OS 4.0
Summary:
Rolling back to Fire OS 4 is easy! Simply visit the page below and follow the instructions provided to complete the rollback form.
http://www.amazon.com/gp/html-forms-controller/wdp_gen_rb
Note: The rollback process requires you to provide both your email used to participate in the Developer Preview, as well as your device's DSN. Instructions on obtaining your DSN are included in the link provided.
What version of OS 4 does this roll you back to?
junglistknot said:
I recently updated to the developers preview of Fire OS 5.0 and I had TWRP installed and I was not able to downgrade using the ADB sideload method. So for people that have the same issue here is what you need to do to resolve this and get back to Fire OS 4.0
Summary:
Rolling back to Fire OS 4 is easy! Simply visit the page below and follow the instructions provided to complete the rollback form.
http://www.amazon.com/gp/html-forms-controller/wdp_gen_rb
Note: The rollback process requires you to provide both your email used to participate in the Developer Preview, as well as your device's DSN. Instructions on obtaining your DSN are included in the link provided.
Click to expand...
Click to collapse
You had TWRP with OS 5.0. So you had root and OS 5.0? how?
siegesoldier said:
You had TWRP with OS 5.0. So you had root and OS 5.0? how?
Click to expand...
Click to collapse
No I had root on 4.5.4 with twrp and I did not have my nav bar so I decided to try to upgrade to 5.2.0 thinking I would be able to downgrade. I was stuck at this OS because I can't get into the stock recovery or twrp. So basically I need to go back to 4.5.3 to gain root and upgrade back to 4.5.4.
DoLooper said:
What version of OS 4 does this roll you back to?
Click to expand...
Click to collapse
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
Lol, so just to be clear, this isn't something you've even actually done yet. Nice. So what, you're just working on theory and leading people to do it with you blindly? Awesome. Post back when you have something with substance for us.
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
I'm guessing it will be 4.5.4, but if it's lower that would make getting 4.5.3 (and root!) much easier. Hope you can keep an eye on it and block OTA as soon as it comes through. thx.
This is directly from Amazon and the zip is signed. There is no reason it shouldn't work. I am just trying to let anyone in the same boat as me this may help them. No need to be rude.
I apologize if that sounded rude. Wasn't my intent at all. I assumed downgrade would be OTA, and it would help everyone if we can get the developer preview and then downgrade in the way you suggest to 4.5.3 or less.
No not you I was referring to the post above yours
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
Have you gotten the rollback yet? If so has it fixed your ability to get to the recovery?
I finally received the update but I can install it because it still needs to boot to the recovery. Sorry for the misleading post. Just so everyone knows it also was 4.5.4 OTA. So I still need to flash the recovery.img through fastboot so if anyone has this img please share.
junglistknot said:
I finally received the update but I can install it because it still needs to boot to the recovery. Sorry for the misleading post. Just so everyone knows it also was 4.5.4 OTA. So I still need to flash the recovery.img through fastboot so if anyone has this img please share.
Click to expand...
Click to collapse
I have 4.5.3 recovery img somewhere, but I am not sure it'd help you since I doubt you could flash anything through the fastboot. I'll dig it up, and upload.
bibikalka said:
I have 4.5.3 recovery img somewhere, but I am not sure it'd help you since I doubt you could flash anything through the fastboot. I'll dig it up, and upload.
Click to expand...
Click to collapse
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
junglistknot said:
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
Click to expand...
Click to collapse
In the same boat anxiously awaiting for someone to find a stock recovery.img
junglistknot said:
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
Click to expand...
Click to collapse
wyldeice said:
In the same boat anxiously awaiting for someone to find a stock recovery.img
Click to expand...
Click to collapse
Well, this is 4.5.3. I dd'ed from my recovery when doing backups. See if it works!
so after messing with this so much bootloader is locked again and I am not able to flash recovery via fastboot. Looks like I will need to wait until someone can root 5.2.0 OS. Unless anyone else has any ideas because I feel like I have tried everything.
junglistknot said:
so after messing with this so much bootloader is locked again and I am not able to flash recovery via fastboot. Looks like I will need to wait until someone can root 5.2.0 OS. Unless anyone else has any ideas because I feel like I have tried everything.
Click to expand...
Click to collapse
5.2.0 can be rooted, but you'll have to start with a working TWRP, which means you already must have root. For independent 5.2.0 root, you may wait for a long time.
With fried recovery and no root, I don't think you are going anywhere, other than to Amazon customer service
bibikalka said:
5.2.0 can be rooted, but you'll have to start with a working TWRP, which means you already must have root. For independent 5.2.0 root, you may wait for a long time.
With fried recovery and no root, I don't think you are going anywhere, other than to Amazon customer service
Click to expand...
Click to collapse
Well I had TWRP and root beforehand. In fact SuperSU is still in the app drawer but it says the binary isn't installed. I can wait though I know I can bring this thing back to life at some point. I have a galaxy s5 rooted with CM12 on it so that will keep me busy while I wait.
Edit: Amazon is sending me a new Fire HD 7. Be here on Friday
junglistknot said:
Well I had TWRP and root beforehand. In fact SuperSU is still in the app drawer but it says the binary isn't installed. I can wait though I know I can bring this thing back to life at some point. I have a galaxy s5 rooted with CM12 on it so that will keep me busy while I wait.
Edit: Amazon is sending me a new Fire HD 7. Be here on Friday
Click to expand...
Click to collapse
Just curious what you told them? I am in the exact same place as you, but it was with my wife's brand new tablet from prime day.

OTA issue...

Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
USFguy said:
Recieved my 6P on Tuesday, it updated to 6.0.1 and it's currently build number MMB29P but when I hit "System Update" it says it last checked 2 mins ago and my system is up to date but isn't the latest build MHC19I? Any idea what the issue is?
Click to expand...
Click to collapse
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
This seems to happen to done some people, no idea why though. You can update manually pretty easily, just flash the factory images for the latest build. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks, I haven't used adb since 2014 with my HTC One X so I'm a little hesitant but seems easy enough.
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
no, everything will just fine..
USFguy said:
Question if I manually update will that have any interference with future OTA's? As in would I have to manually flash from here on out?
Click to expand...
Click to collapse
Nope, it has no effect on future OTA's.
Heisenberg said:
Nope, it has no effect on future OTA's.
Click to expand...
Click to collapse
Just unlock bootloader and flash?
USFguy said:
Just unlock bootloader and flash?
Click to expand...
Click to collapse
Yeah that's it, unlock your bootloader and flash the factory images for MHC19I and you'll be up to date.
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
samomamo said:
I have the same problem , i got the phone from bestbuy today it updated to MMB29P and thats it no more updates?
Click to expand...
Click to collapse
Did you read the other posts in this thread?
Heisenberg said:
Did you read the other posts in this thread?
Click to expand...
Click to collapse
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
samomamo said:
Yes i don't wanna unlock the bootloader. I know how to do it. But its suppose to update automatically.
Click to expand...
Click to collapse
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Heisenberg said:
I'd suggest unlocking the bootloader anyway. If an OTA fails on you you'll be soft bricked and there'll be absolutely nothing you can do about it with a locked bootloader, apart from sending it for repair. It's happened to a few people.
Click to expand...
Click to collapse
Thanks alot bro, im just lazy to set everything up again.
samomamo said:
Thanks alot bro, im just lazy to set everything up again.
Click to expand...
Click to collapse
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
toddalvandi said:
I'm also stuck on January's patch so I wanted to know if I'll get February, then March or does the ota go straight to the latest security patch? If I decide to manually flash it, would I have to flash the February patch first or go straight to they latest one?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Heisenberg said:
It's worth it, I know I'd rather spend the time setting my phone up again than having to send the thing away because it got bricked.
Click to expand...
Click to collapse
Thanks a lot u convinced me. I unlocked and for the hell of it flashed the Android N. Man is so fast , its like running 60fps, I thought its just gonna be little ui changes, but i was wrong. Its like lightning fast. Thanks
Ok it didnt last long. Back to M latest. The N was fast, but toooo many glitches.
Heisenberg said:
If you decide to flash manually, you have two options.
1. Flash the factory images (via fastboot). With this option you can just download the factory images for the latest build and flash them, no need to go through each update to get there.
2. Flash the OTA zips (via stock recovery and adb sideload). This option means you need to flash the OTA zips in order. But since you're on the January build it would only be two zips: the MMP29P --> MMB29Q zip, then the MMB29Q -- > MHC19I zip.
Personally, I'd just flash the factory images with fastboot, it's easier. You do need an unlocked bootloader though, but in my opinion you should have an unlocked bootloader regardless.
Click to expand...
Click to collapse
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
USFguy said:
Just getting time to sit down and do this, I've gone and got all the SDK tools setup in the general thread you linked, and I know i have to unlock bootloader but for the factory image does it matter if I do post #10 or #11? With the phone being 4 days old would flashing without wiping be a big issue?
Click to expand...
Click to collapse
You should have no issues flashing the images without wiping userdata.
Heisenberg said:
You should have no issues flashing the images without wiping userdata.
Click to expand...
Click to collapse
Ah, but I think I answered my own question, won't unlocking the bootloader wipe all data anyway?

Panic - plz help! applied the wrong ota file from adb by mistake, now bootloop

I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
sumit29 said:
I applied the wrong ota file by mistake and now the phone is stuck in bootloop.
phone is unlocked and "fastboot flashing unlock" won't work as unlocking was disabled in developer options.
Factory reset didn't work. Further, getting the Google's device corrupted message during the bootloop.
Any solutions?
Click to expand...
Click to collapse
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
gasparzim said:
Is it possible to downgrade to an older OTA? I received DP3, got a bootloop. Tried sideloading, wiping, nothing solved.
I´m trying to sideload DP2 but it gives me this error:
Cant install this package over newer build
E: error in /sideload/package.zip (Status 7)
Click to expand...
Click to collapse
No, as per the instructions in my guide you can only install a newer build. I wasn't aware that full OTA zips were even available for the Developer Previews.
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Have already tried doing this...this also gets interrupted mid-way, with the command terminal showing - "connection reset by peer". these are the same OTA files available on the google developers website.
and for some reason, it worked this time around!!!
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
Same problem have you been able to sort it out yet?
Ame123 said:
hey can you help me please? i was on marshamllow and yesterday when the android n beta came i installed it through ota update. after it installed and started booting up for the first time it does not boot up. the android boot animation keeps on going for hours. i tried wiping cache and doing factory reset to but its still the same. i cant flash stock image since i didnt enable oem unlocking.
Click to expand...
Click to collapse
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Heisenberg said:
I don't know what you can do, sorry. I'm not sure why you wouldn't just unlock your bootloader and leave it unlocked, that alone would mean you could fix this issue in a matter of minutes. I know me saying this is of no use to you right now, but hopefully it'll impress on you (and anyone reading) the importance of having a fail-safe when things go sideways like this.
Click to expand...
Click to collapse
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
AlfexOmega said:
Same problem have you been able to sort it out yet?
Click to expand...
Click to collapse
no.:crying::crying:
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Heisenberg said:
An update failing is the single most likely cause of a problem like this. The issue here isn't with the update itself, otherwise pretty much every other user taking the update would be experiencing the same thing. There could be any number of reasons for this update going badly for you.
If you had researched you would have known that you need to unlock the bootloader when you first get the device, before you commit too much data to it. Either that or just back up your personal data, unlock the bootloader and then copy your data back. Surely even that is a better option that being stuck in a situation like this where you essentially have a brick.
All you can do now is contact Google support, explain what has happened, and ship it off to them to have it fixed. You shouldn't have to pay if it genuinely wasn't your fault. And remember to unlock your bootloader when you get it back.
Click to expand...
Click to collapse
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Ame123 said:
i did not think that the update will break the device and since i didnt wish to unlock the bootloader as all my data could have gone. do you know where i can report to google so that they an fix this issue in next ota update?
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------
no.:crying::crying:
Click to expand...
Click to collapse
Mine is also still messed up I'm calling the store where I bought it to see if they can do anything highly doubt they will though
Ame123 said:
the place where i stay does not have any support so that i can ship to them. i bought the device from uk but now i stay in UAE. I dont know what to do now:crying::crying: . Also there are many such cases on xda having the same issue.
Click to expand...
Click to collapse
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Heisenberg said:
Oh, that is not a good situation at all. You might need to find a good repairer in your area and pay for them to fix it for you.
Click to expand...
Click to collapse
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
An accredited repair centre should have access to software tools that can do it.
AlfexOmega said:
I've heard that it's basically unrepairable.. As there is literally no way to flash android again without an unlocked bootloader and with OEM unlocking disabled
Click to expand...
Click to collapse
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
ADB Sideload the developer 3 preview 3 like the other user successfully did.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
did not understood what you said. can you explain a little bit more?
Heisenberg said:
You can use adb sideload to install one of the new full OTA files with the stock recovery, I have instructions in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
These full OTA zips don't require a certain preceding build number to be installed prior to installation.
Click to expand...
Click to collapse
Ame123 said:
did not understood what you said. can you explain a little bit more?
Click to expand...
Click to collapse
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Sure, see the above post.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've tried sideloading multiple times and they succeeded however my phone is still not booting :/

BootLoop after installing twrp and SuperSU

Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
vijn said:
Bit of background.
CID: BS_US001
MID: 2PS650000
Original verizon phone that i sent to sunshine for S-off and to unlock from Verizon. Ever since receiving it, almost a year ago, I've never been able to install a custom recovery I gave up on it for months and yesterday tried again. Finally managed to get TWRP. Then I tried to install SuperSU and bootloop. There's always been an issue getting OTAs. The OTA would download, install, and during boot, would give an error or go into bootloop. So, the plan was to finally get a recovery, root it, see about getting the latest OTA etc. Obviously that didn't work out. I feel like there's an issue with the boot sector and has always been. At this point, I just want to wipe and start over but I feel if I don't get this boot sector fixed the phone will never work properly. Any ideas? An RUU will update the OS and maybe fix the bootloop for now, but it won't deal with the OTA or issues with the boot sector that seem to be ever-present. Could use some advice.
I'm also a bit confused about something. This is originally a verizon phone but has been unlocked. When looking for RUUs from HTC should i be looking for the verizon versions or unlocked version?
Click to expand...
Click to collapse
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Tarima said:
You can't take OTAs as long as you have twrp installed or have a modified system partition, which you got after attempting to install SuperSU.
An RUU would restore all partition to a stock state, not just the OS. That's what I would do to get a clean slate, make a stock backup and then root it. Remember that the ruu will wipe your phone so backup your files. You won't find Verizon RUUs on HTC's website, but you can download them from the stock thread here.
Also make sure to fully read the instructions and FAQ posts in the twrp thread, and do the same in the root thread.
Edit: Re-read your post. Since yours is converted to U.S Unlocked, you indeed have to download the latest ruu from HTC's website. Forget about the Verizon ruu.
Click to expand...
Click to collapse
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
vijn said:
Sorry about the late reply. I was traveling. First off, thanks for your response. I guess my only remaining question then is what RUU do i go for? Unlocked developer? I'm just worried there might be a clash with my CID/MID. It's happened before on a previous phone. At this point, all i really want is to get stock back, make sure it's carrier unlocked, update to Oreo, and then, if I'm feeling lucky, root it, though I might just pass on that. So, would you say unlocked developer RUU is my best bet?
Again, thanks for your help.
Click to expand...
Click to collapse
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Tarima said:
If it's an originally verizon phone which was converted to US Unlocked, then use the latest ruu for unlocked on HTC's website. It won't cause you to lose your carrier-unlocked status. It will take you to latest Nougat version. From there, take the OTA update
Click to expand...
Click to collapse
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
vijn said:
Well, it worked. I'm currently on Oreo which is awesome. So first off, thank you very much. Not sure why it didn't work last year, but water/bridge etc.
This brings me to one more question. I want to get rid of some bloatware but would rather not do a full root. I've heard Magisk will give me the benefits of root without the security headaches that prevent things like Google Pay from working. You familiar with that? I also need 2 apps that require root. Never worked with Magisk but I have rooted a bunch of times and honestly, I kinda don't feel like doing it again, especially if I can maybe get the best of both worlds with Magisk. I just don't know enough about it. Figured maybe you might.
Click to expand...
Click to collapse
I use Magisk myself. I prefer it to flashing the classic supersu for root.
Install latest twrp (make sure its the latest twrp for the 10), then flash Magisk. Then install Magisk manager app. As simple as that.
Read the instructions here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You rock man. Thanks for all the help.
vijn said:
You rock man. Thanks for all the help.
Click to expand...
Click to collapse
No worries, glad it worked.

Trouble updating

Not sure if this is the right place to post this.
This is the first time I've tried to system update my Razer Phone 2 since rooting it. I use Magisk. When I try to update, the download finishes, then a red error message at the top says "Installation Problem." I'm not sure the problem comes from the fact I rooted the phone. But I don't know where to begin to solve the problem.
Benjiax2 said:
Not sure if this is the right place to post this.
This is the first time I've tried to system update my Razer Phone 2 since rooting it. I use Magisk. When I try to update, the download finishes, then a red error message at the top says "Installation Problem." I'm not sure the problem comes from the fact I rooted the phone. But I don't know where to begin to solve the problem.
Click to expand...
Click to collapse
Yes it's due to being rooted.
Depending on which image you're currently running you can start over by reinstalling stock image let it update then root again.
JDBarlow said:
Yes it's due to being rooted.
Depending on which image you're currently running you can start over by reinstalling stock image let it update then root again.
Click to expand...
Click to collapse
Should I re-lock the bl as well? Apparently you can do that. I kind of regret rooting. You can do anything fun with the Razer Phone 2
Benjiax2 said:
Should I re-lock the bl as well? Apparently you can do that. I kind of regret rooting. You can do anything fun with the Razer Phone 2
Click to expand...
Click to collapse
If you'd like to yes you certainly can.
I'm sure you're aware of this site since you've already unlocked. Basically same thing just backwards ?
https://developer.razer.com/razer-phone-dev-tools/general-instructions/

Categories

Resources