Need TWRP flashable version of ROM update - Android Q&A, Help & Troubleshooting

Hey guys.
I'm trying to update my F1 but since it's rooted, OTA is not happening (it caused my phone to TWRP bootloop) and other's have reported that they had a better working version flashing the update via the SP Flash Tool. So last time I tried using the Flash Tool was a mess getting it to work (because drives and all) so I was hoping someone might have an image of this update that I could flash via TWRP or is there's a way to convert the extracted RAR folder. Thanks for any help.
David C.

mantarkus said:
Hey guys.
I'm trying to update my F1 but since it's rooted, OTA is not happening (it caused my phone to TWRP bootloop) and other's have reported that they had a better working version flashing the update via the SP Flash Tool. So last time I tried using the Flash Tool was a mess getting it to work (because drives and all) so I was hoping someone might have an image of this update that I could flash via TWRP or is there's a way to convert the extracted RAR folder. Thanks for any help.
David C.
Click to expand...
Click to collapse
The OTA update may be used in Twrp, with some edits, depending on what all has been changed on phone .
I do not have time this weekend to look at it. But can in few days
***UPDATE***
This can update from version 20190316 only
If you open the update.zip you have from the OTA and replace the 'updater-script' with the one attached here. It should perform the update. Remove the ".txt" from the file name first
I say should , because if you have done significant modifications then that may effect its effectiveness.

@mantarkus
I put together an OTA style zip, that has the same images as sp flash install, with only exception being the preloader. The preloader from stock OTA update is different format to the preloader used in flash tool. ( Assume it has to do with the way it gets intalled ) So I have the preloader from OTA in the zip.
I have not uploaded the zip, or tested it out. Before i use the data to upload it. Let me know if you are interested.

mrmazak said:
@mantarkus
I put together an OTA style zip, that has the same images as sp flash install, with only exception being the preloader. The preloader from stock OTA update is different format to the preloader used in flash tool. ( Assume it has to do with the way it gets intalled ) So I have the preloader from OTA in the zip.
I have not uploaded the zip, or tested it out. Before i use the data to upload it. Let me know if you are interested.
Click to expand...
Click to collapse
Hey, thanks a lot. Yes, I am interested. Is this flashable via TWRP?
David C.

mantarkus said:
Hey, thanks a lot. Yes, I am interested. Is this flashable via TWRP?
David C.
Click to expand...
Click to collapse
It should be. Have not tested it. So busy lately.
Best option is to use the flash tool, but after I test this, I will uploaded it. But who knows , rumor us, there had been updated every 2 months so far. Maybe new update is out soon anyway

Anyone know if this is working on the normal F1 (Non-play) version? With the minimal differences including same SoC shouldnt it work? Anyone tested?
wtf rip, i refreshed and i landed here somehow (by my own fault probably). Mean't for: https://forum.xda-developers.com/android/development/twrp-twrp-3-3-0-0-umidigi-f1-play-t3933829
flashing this recovery on my non-play if anyone knows. Soz '

Nexus Radical said:
Anyone know if this is working on the normal F1 (Non-play) version? With the minimal differences including same SoC shouldnt it work? Anyone tested?
wtf rip, i refreshed and i landed here somehow (by my own fault probably). Mean't for: https://forum.xda-developers.com/android/development/twrp-twrp-3-3-0-0-umidigi-f1-play-t3933829
flashing this recovery on my non-play if anyone knows. Soz '
Click to expand...
Click to collapse
Yes, I have been told it does work for both play and not play. I am using the ported version of that official build , done by "ghost"

Oh right. I did a bit of searching before asking for a link but I did find this
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Will this work fine? I know it's a test version. As long as flashing works properly, decryption and mtp works I guess that's all I need?
Otherwise what would you say is the best available twrp version right now? ?

Related

[Solved] Firmware, scatter and PMT: TWRP happiness with new TS.

Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
MrTip said:
Hi all, I have a TS 1/8/2100, firmware 20140513.
TWRP and Bluetooth tether ROM are available for firmware 20140328 only. Past conversations make me think there won't be any update soon.
A solution would be to install previous firmware, then TWRP, then update firmware. But partitions changed in between.
According to this SP Flash Tool can also physically format a partition if you can get a partition management table (PMT). The scatter file describes logical partitions, but it seems you can also add PMT. (After backup with MTKDroidTool, click "prepare Blocks for FlashTool")
Knowing this, provided that hardware is relatively unchanged, it could be possible for newest TS to enjoy TWRP happiness.
I would like to try, if someone could be kind enough to give me a stock backup for TS 1-8-2100 firmware 20140328 with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
I need you to help me help you to help me help you.
thx.
Click to expand...
Click to collapse
Here you go - hope it's what you're looking for..
Tigerite said:
Here you go - hope it's what you're looking for..
Click to expand...
Click to collapse
No, it's not. The key element of my message is
with PMT. (there sould be a file called MT6572_Android_scatter_emmc_PMT.txt)
Click to expand...
Click to collapse
Thank you anyway.
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Tigerite said:
That's all that was generated by the tool I'm afraid, I followed the steps from the link you provided too, but still no joy. It only produces the standard one, no PMT suffix.
Click to expand...
Click to collapse
That's unfortunate. Did you click on "prepare Blocks for FlashTool" after backup ? I'll try myself asap to confirm the procedure.
Yes I did, but no PMT text file in the relevant folder..
Tigerite said:
Yes I did, but no PMT text file in the relevant folder..
Click to expand...
Click to collapse
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
MrTip said:
Well, the procedure is correct. It appears that PMT can be (or not) in scatter file without any difference in the filename. So you have to check by yourself, as I did, if you want to format. (look for many lines per partition, like 'physical_start_addr' and 'linear_start_addr')
You have to select "format+download" in "sp flash tools" to format everything (including preloader, so be carefull).
Take all precautions: Backup everything, including userdata and cache partition, because sp flash tools will ask for it if you have to format. Do not forget to backup nvram.
Doing this, I successfully formatted the TS and installed previous firmware, 20140328.
Sadly, the TS won't boot. Here lies my hope to get TWRP and bt tether ROM working without update from its creator...
So, back to firmware 20140513.
After the new format+backup, TS boot normally, but I had a "IMEI invalid" error. So, I used MTKdroidtools to restore nvram the same way I previously backed it up.
Complete 'format+download' is to be used if you messed up with partitions or if partitions changed.
Could be usefull, this was to let you know how.
Click to expand...
Click to collapse
What exactly are you trying to do?
kuronosan said:
What exactly are you trying to do?
Click to expand...
Click to collapse
Install last firmware known to be working with twrp.
Did that.
The device doesn't boot anymore.
Revert to previous backup.
Did that.
I like to see things by myself.
It's not your firmware that's the problem. I'm running twrp on the latest firmware without issue.
kuronosan said:
It's not your firmware that's the problem. I'm running twrp on 20140513 firmware without issue.
Click to expand...
Click to collapse
I can only rely on testimonies on this very forum, but I have not seen a single person succesfully installed twrp on firmware 20140513.
I have seen successfull install on previous firmware, and then OTA upgrade.
What is it for you ?
It is exactly what I told you. It's up to you to believe me or not.
kuronosan said:
It is exactly what I told you. It's up to you to believe me or not.
Click to expand...
Click to collapse
You didn't told me if its an install on 20140513 firmware or if it's an upgrade from previous firmware.
kuronosan said:
EU 1/8 users who have the new aluminum watch or who received their units after May 13th need to click here and also need to remember that recovery may not work (although it probably won't work before this anyway).
Click to expand...
Click to collapse
I understand you agree there is a problem with twrp 2.7.1.0 on newer devices.
You'll notice I did say new devices. Not new firmware.
kuronosan said:
You'll notice I did say new devices. Not new firmware.
Click to expand...
Click to collapse
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Tigerite said:
Anyway to get back to the thread.. I've tried everything, booting in recovery, running MTK Droid Tools as Administrator, installing busybox again - but still no PMT file. I'm all out of ideas now..
Click to expand...
Click to collapse
That's OK. It appears that PMT can be (or not) in scatter file without any difference in the filename. (If you look in the file and see many lines per partition, like 'physical_start_addr' and 'linear_start_addr', you have PMT)
So I found what I was looking for, thank you.
MrTip said:
Ok then, you win by default. Look at me asking a simple question while you obviously rather going back an forth playing fallacy pong. Please forgive me if I cut this short. I'll click on Thank You anyway.
Click to expand...
Click to collapse
No one is trying to win. I have a good deal of experience with MTK devices based on my researching various methods of backup/restore/flash/etc and I was offering a hand.
You can play one-person pong with yourself and claim fallacy all you want or you can get off your high horse.
Up to you. I have work to do.
TWRP Install on newest firmware + OTA
got watch on 7/26. did OTA. firmware date 5/27/2014. unable to install TWRP via any method including shell DD command. well it installs but on entry I just get on the old andy with red ! showing. It seems like a watchdog timers reboots it after a few minutes and all is back to the way it was.
Which TWRP did you use?

Download link for Elephone_P9000_20170112 Rom

can anybody please create a download link for the latest ROM so people that cant update via OTA can update via spflash tools
thanks
Look here: http://bbs.elephone.hk/forum-349-1.html
but the rom is not yet available.
haidar123 said:
can anybody please create a download link for the latest ROM so people that cant update via OTA can update via spflash tools
thanks
Click to expand...
Click to collapse
More to the point WHY cant we update from OTA been trying for days
Bradco said:
Look here: http://bbs.elephone.hk/forum-349-1.html
but the rom is not yet available.
Click to expand...
Click to collapse
Updated it yesterday via OTA.
Anyways its just some bug fixes. Also my fingerprint scanner works better now.
I've heard some ppl who cant update via OTA, has to do it with their SD card taken out. Try that.
OTA is just a update, not a full rom
full rom is installed with flashtool
can this rom rootet?
badf said:
can this rom rootet?
Click to expand...
Click to collapse
I tried a few methods, none worked.
I flashed latest Johnny's TWRP but then the system didn't boot.
I tried to "fastboot boot custom-recovery.img" but the prompt gave me a "locked bootloader" error, and the "fastboot oem unlock" didn't work because of the old stuck volume up issue.
I also tried kingroot, both from pc and through apk. Nothing.
****
haidar123 said:
can anybody please create a download link for the latest ROM so people that cant update via OTA can update via spflash tools
thanks
Click to expand...
Click to collapse
Hi,
Elephone posted a link to download the 20170112 update on Twitter
Twitter: https://twitter.com/ElephoneMobile/status/821973296371503104
Firmware 20170112: https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8RJKw
Cheers
anyone having problem with back camera?
after installing this the phone cant detect/access the back camera anymore.
I've just managed to update my P9000 to 20170112 after the update last year that stopped it being able to OTA.
Lucky for me there were some users on the elephone "Official" forum although I can't see any official help being offered.
Anyway, since getting it running all appears ok except now instead of poor GPS I don't have any working GPS at all.
Just a warning for anyone who relies on GPS.
I gave up using the inbuilt GPS ages ago and just use a Bluetooth unit I had lying around since the dark ages of smartphones.
Good luck with the new rom should you decide to install it.
That sounds aweful man...considering all the problems, i'll never buy Elephone for sure, and maybe also leave my hands of Chinaphones
I also have the problem that i downloaded the Rar-File, but there is no information to be found on how to exactly flash the ROM. What files of the ROM do I need,
and which hooks to activate in SP Flash tools.
phil-w said:
I've just managed to update my P9000 to 20170112 after the update last year that stopped it being able to OTA.
Lucky for me there were some users on the elephone "Official" forum although I can't see any official help being offered.
Anyway, since getting it running all appears ok except now instead of poor GPS I don't have any working GPS at all.
Just a warning for anyone who relies on GPS.
I gave up using the inbuilt GPS ages ago and just use a Bluetooth unit I had lying around since the dark ages of smartphones.
Good luck with the new rom should you decide to install it.
Click to expand...
Click to collapse
thx

Which Rom is the best for the Mate 10 Pro

Hey Guys,
what do you think is the best costum rom (stable) for the Mate 10 pro?
Is it possible to flash it with Pie 9.0.161?
Thanks for Help :victory:
Just wait for the ota update to pie.
that's definitely a worse rom. i'm on it right now.
wooley4766 said:
Just wait for the ota update to pie.
Click to expand...
Click to collapse
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Pie Update
HauAbDuLauch said:
I already have the Pie Update via Firmware Finder.
But i want to flash to a stable Pie Rom :fingers-crossed:
Click to expand...
Click to collapse
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
revjamescarver said:
If you have the Pie update from firmware finder it's an approved ROM unless you have a modified recovery it checks and you wouldn't be able to install it if it wasn't approved so you probably have the latest approved ROM
Click to expand...
Click to collapse
but no custom
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
93starletgt said:
Hi! Quick question. My BLA-L09 is on build number 8.0.0.131(c782). I'm rooted with Magisk via Pretoriano's TWRP using the all in one tool. I can't receive firmware updates because of this (they fail to install).
If I update to Pie, will I be able to root again with Magisk? How can make this update? I suppose I would need stock recovery back and don't know where to get it from it how to flash it. It was my first time doing this on a Huawei, I'm used to Samsung devices. Any help would be appreciated.
Thanks!
Click to expand...
Click to collapse
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
mirandam said:
Nope, you won't. Any version from 8.0.0.146 and above will contain the new bootloader which won't let you unlock it or install twrp, magisk or whatever, most probably you will brick your phone like I did.
You'll be a lot safer to stay on what you're on. Huawei did a nifty development to make life miserable to anyone which likes to customize their phone. Maybe they should be called Huapple from now on...
I was in a similar situation as you, 141 if I remember correctly. Installed Xposed via magisk, got a bootloop, did a system restore via erecovery, got it working again and lost magisk/root so thought it would be the time to do the ota, didn't know about the bootloader change so found I was on emui 9, tried to install twrp but that bricked the phone. So I tried to do the system restore via erecovery again, but that didn't work.
After that tried every possible way (inc. paying funkyhw etc.) to recovery the phone, no way. If you try to downgrade it to a version before 146 it will hardbrick leaving you with a paperweigth.
So if I were you, I wouldn't touch a thing. I gave up and am waiting for my Oneplus 6, much better phone for this stuff.
Click to expand...
Click to collapse
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
93starletgt said:
Thank you for the info! And what about staying on my current bootloader and flash a custom ROM on my already installed TWRP?
Click to expand...
Click to collapse
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
mirandam said:
There is a ResurectionRemix rom that can be used for that. Just search for RR-O-v6.0.0-20180402-bkl-OpenKirin.zip it should work as this one's flashable by twrp. I haven't tried it so can't tell if it does. I have the file but I don't know if it's complete as it only contains system.img which seems strange as normally there would also be a boot.img or at least a kernel.img
Click to expand...
Click to collapse
Thanks! Last question. If I would like to go back to stock using the All In One Tool, how can I flash stock recovery? And where can I find it? Many thanks for your help.
are there custom roms for the huawei mate 10 pro??
cause cant find it on xda.
mine is stock it works but the no status bar pull down on lockscreen is anoying ;( sometimes and that only the stock sms app show on the always screen on...

[Help needed]Fixing OTA on BlackShark 1 Global

Hello (hopefully) Black Shark Owner,
Unfortunately, it seems that rooting the Black Shark prevents the ability to use OTA on the phone.
What i need, is your help:
if you have a Black Shark on G66X1901082OS00MPX, Please reply to this thread.
I will give you instruction to help me fix my phone, and if that works, i should be able to create an Image that can be flashed to Black Shark Global phones, to restore them to Stock condition (and allow OTA again)
Thanks to @leipnacht, i was able to fix my phone, update from pre-2019 version, to the latest security update at june 2019.
I will post instructions later for everyone with broken OTA.
gilbert32 said:
Hello (hopefully) Black Shark Owner,
Unfortunately, it seems that rooting the Black Shark prevents the ability to use OTA on the phone.
What i need, is your help:
if you have a Black Shark on G66X1901082OS00MPX, Please reply to this thread.
I will give you instruction to help me fix my phone, and if that works, i should be able to create an Image that can be flashed to Black Shark Global phones, to restore them to Stock condition (and allow OTA again)
Click to expand...
Click to collapse
Just an FYI for the link I posted on your JoyUI thread, I have here the dsp files for G66X1901140OS00MPX version.
G66X1901140OS00MPX dsp images
leipnacht said:
Just an FYI for the link I posted on your JoyUI thread, I have here the dsp files for G66X1901140OS00MPX version.
G66X1901140OS00MPX dsp images
Click to expand...
Click to collapse
Your dsp files worked!
unfortunately, now my bluetooth partition is also changed (possibly others too).
Can you share bluetooth_a.img? (turns out your slot a is on the system version i have, so i only need slot a files).
Hopefully bluetooth is the only other broken partition
BTW, you can zip them, so that upload goes much faster.
gilbert32 said:
Your dsp files worked!
unfortunately, now my bluetooth partition is also changed (possibly others too).
Can you share bluetooth_a.img? (turns out your slot a is on the system version i have, so i only need slot a files).
Hopefully bluetooth is the only other broken partition
BTW, you can zip them, so that upload goes much faster.
Click to expand...
Click to collapse
These are the bluetooth images. Here you go. For other files. I'll upload it if there's free time here at work
bluetooth images SKR-H0 (G66X1901140OS00MPX)/
leipnacht said:
These are the bluetooth images. Here you go. For other files. I'll upload it if there's free time here at work
bluetooth images SKR-H0 (G66X1901140OS00MPX)/
Click to expand...
Click to collapse
Bluetooth works now
The next partition i need is modem. :fingers-crossed:
@leipnacht did you have a chance to upload the backups?
I only need slot a backups, and right now my OTA fails on the modem partition.
gilbert32 said:
@leipnacht did you have a chance to upload the backups?
I only need slot a backups, and right now my OTA fails on the modem partition.
Click to expand...
Click to collapse
Just go on this link
G66X1901140OS00MPX Backups
This is a shared folder. I'll just upload all the stuffs there. Just check it time to time
leipnacht said:
Just go on this link
G66X1901140OS00MPX Backups
This is a shared folder. I'll just upload all the stuffs there. Just check it time to time
Click to expand...
Click to collapse
Awesome, Thanks!
The backups from @leipnacht seem to be working for me. Once i test it completely, if my phone resumes OTA, i will try to make a backup and package it into a flashable zip.
That way, anyone should be able to restore his phone completely.
gilbert32 said:
The backups from @leipnacht seem to be working for me. Once i test it completely, if my phone resumes OTA, i will try to make a backup and package it into a flashable zip.
That way, anyone should be able to restore his phone completely.
Click to expand...
Click to collapse
have you done with the ota ? thx
kanded said:
have you done with the ota ? thx
Click to expand...
Click to collapse
Yes. I used ota and got 2 updates. After updating, i rerooted and got magisk back.
Edit: did you mean the flashable zip? No i didn't, but i uploaded a full backup in another thread.
gilbert32 said:
Yes. I used ota and got 2 updates. After updating, i rerooted and got magisk back.
Edit: did you mean the flashable zip? No i didn't, but i uploaded a full backup in another thread.
Click to expand...
Click to collapse
hi gilbert i have black shark 1 china how to i get ota update? can you help me? (my phone unlocked, twrp and magisk installed)
Can Somebody Know How To Fix Null Imei, I Converted My Black Shark 1 CN To Global
I have a blackshark global after dead recovery got null imei and unknown baseband . QCN cannot be restored on the device . I have used many programs and boxes to restore qcn but i get unknown response from phone . any help ?

Question Which version of the phone do I have and how to root?

Build number
DE2117_11_C.17
Hardware version
DE2117_11
I keep seeing T-Mobile version, INTL version, DE18 and all that. I'm so confused, I just need root.
I believe that's the international version since mine is DE2117. Not sure because of the "_11" at the end of yours. Maybe that signifies you updated it, in which case you will probably have to downgrade it.
Rooting this phone is a headache btw. I'm not even sure if I should be providing instructions because I bricked mine multiple times while attempting and had to keep restoring with MSMtools, and now I'm not even sure I can update it without losing root. I don't even think I did anything differently when it finally worked, it's just luck.
Anyway, first step is to download the international version of the MSMtools and payload dumper. look up how to dump the boot image with payload dumper from the MSMtools. And make sure you don't attempt to do anything to the device before unlocking your bootloader (and you'll have to unlock it again everytime you restore with MSMtool).
From there you should be able to follow guides.
@swee08315
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
jova33 said:
I downloaded the latest update available from https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
But the phone is updated to July. Hmmmm.....
I've extracted the boot.img from there. Patched it with magisk. I'm about to fastboot flash it..... Wish me luck, I'm going in.
Unless there's a way to extract the boot.img that's currently installed. I think I'll poke around and look for that rather than simply hoping this is the right one.
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
justauserthatusesaphone said:
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
A1.1 will get the boot.img your device currently has.
Edit: if you flashed the boot.img from the official site, then your device is most likely bricked. I'll fetch my boot.img and link it here (won't be magisk patched).
Click to expand...
Click to collapse
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
jova33 said:
yeah, I bricked it
Nothing a few beers won't cure.
Once I unbrick, I will do A1.1 though.
Click to expand...
Click to collapse
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
justauserthatusesaphone said:
here's the boot.img (not rooted)
I hope you haven't wiped yet
boot.img
drive.google.com
Click to expand...
Click to collapse
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
jova33 said:
nah, I don't wipe until I get into the shower.
But yeah, I completely reset everything with MSM tools. In the process of letting all the updates go through. Thanks for the boot img though, It'll save me the trouble of having to pull it using the msm tools.
Edit: I forgot to do the vbmeta stuff after flashing the magisk patched. How do I fix? Can I borrow your vbmeta, @justauserthatusesaphone ?
Click to expand...
Click to collapse
I'll get it when I'm on my PC
the c17 one, correct?
justauserthatusesaphone said:
I'll get it when I'm on my PC
the c17 one, correct?
Click to expand...
Click to collapse
Don't worry about it. I redid the MSM tool since the phone wasn't even setup yet, no big loss.
swee08315 said:
So I can update my oneplus and then patch and use this bootimg to regain root? Or will trying to update my rooted device brick it and I'd have to wipe everything and start from scratch anyway?
Click to expand...
Click to collapse
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img.
jova33 said:
So, I don't know how this phone handles updates. I've had previous phones that if it was rooted, the OTA would fail to install, and others that the OTA would install and replace the boot.img, so root would be removed.
The first case, I would have to unroot, restore the stock boot.img, and then it could take the OTA update.
The other case I would have to block OTAs until I could get the boot.img for it, so that I could root the update.
The guide posted here https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
part B explains how to update and maintain root. Seems like it's the first case. Restore stock boot.img
Click to expand...
Click to collapse
You could turn off automatic system updates so it doesn't reboot automatically and then you install the update and when it asks you to restart, go into magisk and click install and install to inactive slot then you go back to the system update page and click restart. I don't know whether Google's ota system makes it easier or not.
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
swee08315 said:
Late reply but I can confirm that all updates fail on this device and you would have to unroot to get the update, and then root again. Very annoying that it's constantly notifying me that an update is available or that it tried to update last night and failed
Click to expand...
Click to collapse
I never had that issue but if you do, press uninstall and restore images (DON'T REBOOT), then after installing the updates (DON'T REBOOT) press install and install to inactive slot. Press the reboot button and you're done.

Categories

Resources