Related
getting errors when trying to take the january OTA security update
im using systemless root 2.66
twrp wont install the ota. anyone know how?
With TWRP, you can't take an OTA. You need to have stock Android recovery, unmodified /system, and unmodified boot.img (so no custom kernel). Otherwise the OTA will fail.
ugh i thought one of th ebenefit of systemless root was to be able to easily to ota updates. anyone have a flashable zip?
If you need twrp just boot from it in fastboot and retain stock recovery
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Chainfire wrote that if you use the SuperSU unroot function you should be able to apply the "real" OTA (i.e. not a sideload of a downloaded OTA, though maybe that might work too) and then reroot.
Alternatively, download the full image, unzip everything including the zip within the zip, copy the system.img, boot.img, and the TWRP for your device to your ADB folder. Copy SuperSU v2.67 to a folder on your phone. Then boot into bootloader, flash system, boot & TWRP, boot into TWRP recovery, and install SuperSU. Job done. No settings, data or apps lost. I know because I did it last night on my Nexus 6 & Nexus 10.
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
JimSmith94 said:
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
Not_A_Dev said:
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
Click to expand...
Click to collapse
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
RMarkwald said:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
Click to expand...
Click to collapse
Thanks! I have already installed MMB29Q with fastboot, but next time I might try OTA with Chainfire's FlashFire: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx
Sent from my Nexus 6 using Tapatalk
Anyone have the ota from mmb29k?
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot flash system system.img
8. fastboot flash boot boot.img
9. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Not_A_Dev said:
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
13. fastboot reboot-bootloader
14. reflash superSu
15. reflash Xposed
Would this work?
Click to expand...
Click to collapse
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
This method (outlined above) works great. This is exactly the same setup I have (n6 + root + xposed) and is also precisely how I've been applying the monthly updates. Never experienced any issues.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
I'll give it a shot. I agree, and thanks for the suggestion.
Edit: Happy to report that the method in post #13 leads to a successful update of the most recent Shamu image. My device is now updated to MMB29Q, still runs TWRP, is rooted, and runs Xposed. 20 minutes tops for the whole project.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
Excellent may i knidly ask pls
last two steps:
what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Thanks tonnes...I believe my user data is preserved
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Most of the time they don't update bootloader and radio...
90% of the time, you can just fastboot flash only system. Basically the equivalent of dirty flashing your rom.
The above where you clear everything before flashing is basically the equivalent of wiping cache 3x... It wipes the partition when you flash. Think about it, if you flash userdata... you end up with all your data being deleted and a blank userdata partition. It doesn't copy the img on top of what is currently there, it replaces it. You can do extra steps if you want... But you really don't need to.
sunandoghosh said:
Excellent may i knidly ask pls
last two steps: what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Click to expand...
Click to collapse
^ This. One step that's also missing above is that once system.img and supersu have been flashed, there is hardly any space on /system to flash xposed (that's just how Google does things these days). So one would have to remove a few non-essential system apps (files, such as Google Books, Google Newsstand or the like) to make some room for xposed.
This thread is turning into a fastboot flash factory image thread rather than an ota thread. That's ok, it's a good thing ...I've been waiting for a thread like this and your posts inspired me to do my first flash to update security for my rooted phone (with xposed) since I initially set it up in December.
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Quote:
Originally Posted by Not_A_Dev
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
Click to expand...
Click to collapse
I roughly followed above steps, but had some comments/questions along the way:
I skipped the first and second erases as suggested above, but I kept the third erase (cache) because it is included in the xda n6 stock flashing tutorial here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I rebooted to android system between steps 10 and 11 because I wanted to make sure everything was ok. But that was a bad idea because:
A- it overwrote my twrp with stock recovery (even though I never flashed recovery)! So I had to fastboot boot twrp later.
B- it took extra time formatting stuff that was probably undone later.
And yet I still have to boot into android at some point in time to clear space before I flash the xposed zip in twrp. Maybe next time I should reboot to clear space between steps 11 and 12?
I was pleasantly surprised to see when completed flashing the xposed zip that I didn't have to reinstall the xposed apk and that the xposed modules were already enabled and configured exactly the way I left them. Good stuff.
Not used to giving guides
TWRP Backup - https://forum.xda-developers.com/oneplus-6t/how-to/dp3-twrp-backup-t-mobile-magisk-t3952304
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
ayjays said:
-About TWRP- (from my knowledge)
DON'T FLASH TWRP
I think recovery is running in boot.img now I'm not sure
But it seems we may need to patch the bootloader to have the recovery in there
Ive unpack both boot IMG from dp3 and Twrp IDK if they're made different but they look different unfortunately I don't understand enough to patch but hopefully that helps idk
So I wouldn't try flashing or booting into recovery it'll just freeze and flashing will mess up the whole device and you'll have to use msmtool again and redo process
Click to expand...
Click to collapse
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but I have trouble switching to the opposite after rebooting because of set_active command maybe I'm doing something wrong
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
Click to expand...
Click to collapse
Our recovery is built in boot.img.
Uploading now
---------- Post added at 10:10 PM ---------- Previous post was at 09:42 PM ----------
Boot to fastboot
fastboot getvar all
See which slot is active.
If it's slot a then this
fastboot flash boot_a qb3-twrp.img
If it's slot b then this
fastboot flash boot_b qb3-twrp.img
Once flashed choose boot recovery and once it boots u can flash stock boot.img back then flash magisk 19.4 while in twrp.
U must use USB drive decryption isn't working yet. Or adb sideload.
I've only tested this on T-Mobile version running qb3.
All credits to @mauronofrio I used his source with some modifications
https://www.androidfilehost.com/?fid=6006931924117924335
ayjays said:
Thanks, so I'll have to use the "flash recovery Twrp.img" command now?
Or, is it a custom one Twrp only for dp3?
And thank you by the way I'll probably post a guide using a backup from Twrp then
And I'm aware of checking the active slot with a command but switching to it after rebooting because I of set_active command maybe I'm doing something wrong
Click to expand...
Click to collapse
Did you try what I posted
twinnfamous said:
It's not about patching.
Flash stock boot.img to both slots as I'm guessing you aren't sure which one your on.
I'll give u a twrp that works for qb3 also proper instructions.
T-Mobile version downside is we can't flash ota and we can't boot qb3 wth fastboot twrp so flashing the twrp.img now replaces kernel in boot.img.
Click to expand...
Click to collapse
twinnfamous said:
Did you try what I posted
Click to expand...
Click to collapse
Not yet, but if you flash the stock boot image after then would there be any point in flashing the patch boot before hand? And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
ayjays said:
Not yet but if you flash the stock boot image after then would there any point in flashing the patch boot before hand. And, what I was looking for is a more permanent solution. So, that it'll boot and you can go to Twrp whenever without having to use a PC.
If that's the case and it works then nevermind but I remember and if I'm mistaken that, even if you flash the Twrp installer it'll still boot loop after the installation.
If that's still a problem maybe someone more skilled than I, or even you, can patch the stock bootimg themselves. And, eveb get it working for the future time on Q
Maybe unpacking and looking inside the boot.img and Twrp.img, the repacking with the proper adjustments
Click to expand...
Click to collapse
I'm aware of the permanent solution your looking for. This is the first step. With magisk installed u can simply use the installer in my android file host by selecting modules push the + sign and find the installer then without rebooting install magisk direct install. Then u can boot to recovery with advanced reboot menu. U can also just do everything in twrp. After u flash twrp.img .
ayjays said:
Not used to giving guides
But you need to download the the QB3 update zip and upack the payload.bin with a payload dumper
Make sure your device is on international and unlocked of course
Boot into Twrp recovery and copy the system.img and vendor.img onto device
Flash both images in respective partitions and on both A and B slot
Wipe data after flashing and reboot into bootloader
From directory of the rest of IMG you've extracted you'll want use fastboot and flash:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Then reboot and done
Don't delete files just yet
Haven't tried but certain you can root this way:
After you've setup your device you can download magisk manager. Select the boot.img on you pc, in your dump folder, and copy it to your device again. In the magisk manager patch the boot image you copied, and copy that onto your PC
Now boot into bootloader and use command
fastboot flash boot magisk_patched.img
Or if that doesn't work try
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
And if device doesn't boot for any reason just flash back the stock boot.img
Enjoy
Click to expand...
Click to collapse
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
fullofhell said:
Just like my guide last month on OnePlus forums as I am jacksummers, even if u do this we still have no calling ability whatsoever. SMS is barely working and it still blows for us. I have been trying everything to get the whole thing to not only flash and install but be able to boot with no hardware mismatch... It won't work unless we can resign the firmware with OnePlus signing keys after changing everything to say "single" still. Since we cannot change the phone. There is still something in the phone that comes back as op6tsingle
Click to expand...
Click to collapse
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
ayjays said:
My phone is off rn but I receive calls and texts and I've been receiving calls on my T-Mobile OnePlus 6t since I flashed it... Make sure you're on international version
the only problems i ran in myself so far are app optimzations and when i'd recieved calls and answer my voice would sound weird to them but id hear them perfectly (not my problem lol jk jk)
Click to expand...
Click to collapse
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
fullofhell said:
Yeah u need to flash every other partition in the bin dump. If it tells u u cannot bc it's a critical partition then ya can't. Once u do so u will have full function and on calls. It's basically everything in the payload.bin but abl,xbl, hyp, and a few others that tell ya they're critical partitions. Once u do that everything works Perfectly.. my main issue was the call issue u described..but do as I suggest and all will work
Click to expand...
Click to collapse
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
I'm uploading twrp backup soon with root
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
omariscal1019 said:
DO AT YOUR OWN RISK I WONT BE RESPONSIBLE FOR ANYTHING!!!!!!
EVERYTHING SO FAR WORKS WITH JUST A LIL LAG HERE AND THERE
Tmo oneplus 6t fastboot flash one click Android Q DP3. i test it with and without wiping data. i just put all the files together. just run the flash bat. You need to be on latest beta. i tested myself twice.
root= Download patch q boot.img.
fastboot flash boot img after first boot. then just download canary magisk manager. a quick google search will bring it up
have fun and remember anything goes south you can msm tool back to stock!
flash all: https://drive.google.com/open?id=1D_-B5z-rHGDr6RHjDQA0hz-janrsypdv
patch boot img: https://drive.google.com/open?id=1nbiapy6HZH4VNK4JuEF9KxSIlsBRKgsX
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-6t/development/dp3-twrp-backup-t-mobile-magisk-t3952304 TWRP backup good job on the not wiping data though
ayjays said:
That's why I said to flash system and vendor in Twrp wipe data then flash the other ones I stated above in fastboot mode everything should be flashed without a problem just follow my guide it's not hard
Click to expand...
Click to collapse
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
fullofhell said:
Hi, yes we are saying the same thing.. also note, for me, Calls last for a day, then broken again. Cannot use daily if u need to make phone calls. Testing with TMobile modem.img to see if resolved.
Click to expand...
Click to collapse
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
omariscal1019 said:
i made a one click fastboot let me what happens so.ican remove it and add t mo modem
Click to expand...
Click to collapse
Will do buddy. Setting mine up as we speak.. I am down to just my fajita right now, bricked my pixel 3 again as I'm working on an exploit to unlock my locked down version ....
Can you relock bootloader after this? Don't want twrp or root
supaet said:
Can you relock bootloader after this? Don't want twrp or root
Click to expand...
Click to collapse
Not sure try "fastboot oem lock" in the bootloader after
I have a G7 Plus Retail version on stock ROM, rooted and Magisk installed. Via other threads, I have learned how to manually flash updates by extracting the zip file and then running fastboot command lines. Yesterday, I received an alert that QPWS30.61-21-18-7-8 update is available, via OTA updates on my phone - of course I know I can't run the OTA update, even if I uninstall magisk and restore boot image, etc., but I am wondering if anyone knows where to find this update as a downloadable zip so I can manually flash it? It doesn't seem to be on the mirrors.lolinet.com site where all the other g7 plus stock ROMs are.
I've been into custom ROMs in the past but to me this stock ROM is reliable and un-bloated enough that it's acceptable for my needs.
Is your device xt1965-t by any chance?
Could you back up your unmodified /system in TWRP as an image, and send it to me? It should be QPWS30.61-21-18-7-3 right now. I'd greatly appreciate!
Technically, if you booted TWRP externally and did not decrypt /data, you should be able to replace boot to the unrooted stock, and it would take OTA if all the partitions are stock. Then your current partition of A/B will be QPWS30.61-21-18-7-8, and the other one of A/B will be QPWS30.61-21-18-7-3 (the one you are currently running). At this point you can reroot the boot image for QPWS30.61-21-18-7-8.
See this for some details:
rooted XT1965-T, can I boot earlier OS version via A/B switch to apply OTA?
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So...
forum.xda-developers.com
bibikalka said:
Is your device xt1965-t by any chance?
Could you back up your unmodified /system in TWRP as an image, and send it to me? It should be QPWS30.61-21-18-7-3 right now. I'd greatly appreciate!
Technically, if you booted TWRP externally and did not decrypt /data, you should be able to replace boot to the unrooted stock, and it would take OTA if all the partitions are stock. Then your current partition of A/B will be QPWS30.61-21-18-7-8, and the other one of A/B will be QPWS30.61-21-18-7-3 (the one you are currently running). At this point you can reroot the boot image for QPWS30.61-21-18-7-8.
See this for some details:
rooted XT1965-T, can I boot earlier OS version via A/B switch to apply OTA?
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So...
forum.xda-developers.com
Click to expand...
Click to collapse
Unfortunately, I have the xt1965-2 if I do a fastboot getvar -all.
cllewis1 said:
Unfortunately, I have the xt1965-2 if I do a fastboot getvar -all.
Click to expand...
Click to collapse
Ok, nevermind then.
But for you - my recommendation is that you put back the stock boot, and see if takes the OTA update. Unless you installed TWRP & decrypted /data, in that case you are out of luck.
All OTA cares about is that partitions that it's about to patch have the original checksums. If they do, it'll proceed.
bibikalka said:
Ok, nevermind then.
But for you - my recommendation is that you put back the stock boot, and see if takes the OTA update. Unless you installed TWRP & decrypted /data, in that case you are out of luck.
All OTA cares about is that partitions that it's about to patch have the original checksums. If they do, it'll proceed.
Click to expand...
Click to collapse
Yeah, I have TWRP. Therefore I think my only option for the update is to get hold of the zip file, extract it, and manually install it piece by piece (which takes all of 10 minutes to do once I have the file downloaded.)
Hey, when I boot into fastboot I see xt1965-T, which is apparently the non-tmo version since I got it retail direct from moto. Do you need me to backup system or system image and send to you?
cllewis1 said:
Hey, when I boot into fastboot I see xt1965-T, which is apparently the non-tmo version since I got it retail direct from moto. Do you need me to backup system or system image and send to you?
Click to expand...
Click to collapse
Oh, could you back up /system for QPWS30.61-21-18-7-3 as an image if that's what you have? And put it somewhere?
Is your channel RETLA in settings?
I think if you back up your /data (unencrypted I assume?) in TWRP, you could just flash the entire new OS from here:
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Backup of the /data is important in case things go south. You could later pull programs from the TWRP backup using TitaniumBackup. For /sdcard, use TotalCommander, zip it, and if you unpack later, TotalCommander can even restore time stamps if you give it root.
These versions are a bit confusing, that's why I'd rather restore /system, and let it OTA instead of flashing the full ROM. But it does not seem you have this option anymore (if you decrypted /data, your /vendor is probably modified).
Update: If you want, I could give you stock /boot, /recovery, /vendor. But if you are decrypted, you are better off just loading that entire new ROM. If you find a good guide for A/B Moto phones, please let me know (it's important not to mess up A/B stuff).
So it turned out that the RETLA firmware works fine for my phone, which is indeed the xt1965-T. I manually installed the update using the fastboot flash command line for each of the component files, then used fastboot to boot back into TWRP and reinstalled TWRP and Magisk from there.
Where's a good place for me to put that file so you can access it?
cllewis1 said:
So it turned out that the RETLA firmware works fine for my phone, which is indeed the xt1965-T. I manually installed the update using the fastboot flash command line for each of the component files, then used fastboot to boot back into TWRP and reinstalled TWRP and Magisk from there.
Where's a good place for me to put that file so you can access it?
Click to expand...
Click to collapse
Good news! Did you wipe /data too? Or did you keep it? Did you keep the log of commands by any chance? I am still a bit hazy with this A/B business, and as such, want to proceed more carefully than usual
For storage, you can use one of the free options (something like Dropbox or Mediafire, or even Google Drive):
15 Best FREE Cloud Storage & Online Unlimited Drive Space
Cloud storage is a way of storing data online. It requires an internet connection in order to maintain, manage, and share documents, presentations, spreadsheets, images, audio, video, etc. with others
www.guru99.com
You can just PM the file link to me (not in the forum).
Thanks for the effort!
I ran the commands from the command prompt by extracting the zip file and then putting fastboot.exe into the folder where I put the contents of the zip file:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase carrier
fastboot reboot
Note that this is a "dirty" flash and will leave all your apps, all your data, all your settings intact. Note that you will lose TWRP recovery by doing this.
To get TWRP back, after rebooting and letting the update finish installing, you can go back into fastboot and do a
fastboot boot twrp.img (fill in whatever the name of your twrp boot image is)
This will boot you into TWRP. From there you can install twrp recovery and magisk.
Note - do not do:
fastboot flash twrp.zip - attempting to flash twrp recovery from fastboot will soft brick your phone and you'll have to go back and run all these commands again.
cllewis1 said:
I ran the commands from the command prompt by extracting the zip file and then putting fastboot.exe into the folder where I put the contents of the zip file:
...
To get TWRP back, after rebooting and letting the update finish installing, you can go back into fastboot and do a
Click to expand...
Click to collapse
OK!
It looks like TWRP can read /data partition now, which is different from when I tried it last time for a moto g6.
I could not use your TWRP system backup since it is not a bit-for-bit "system image" version (it was just a straight system backup with files). It would not restore "dm-verify" checksum to enable OTA. To have a bit for bit one gotta do "system image" in TWRP.
Your list of commands is slightly different compared to flashfile.xml file. You may want to double check that since it seems you've missed some partitions.
I think your original system image may be gone from your phone - depending on A/B situation, so I better use the full ROM and just install it directly (as you did).
Is everything working fine for you with the updated ROM?
Short answer is yes, everything's working fine.
I skipped
fastboot erase userdata
Because I didn't want to erase all my data.
I knew I hadn't used BTFM.bin, frankly, I didn't know what to do with it, so I just skipped it. Now that I realize it's for the bluetooth radio, I have gone ahead and flashed it just now, after the fact. Hopefully this will improve my bluetooth performance a bit...I've found that if this phone is in my hip pocked and I squat down to work on a piece of lawn equipment, my bluetooth gets very choppy.
I also skipped the
fastboot logo logo.bin
because I don't really care about the boot logo when I turn the phone on.
I also pulled a backup (pre-upgrade) of system_image in TWRP...do you think that would work better for you?
cllewis1 said:
Short answer is yes, everything's working fine.
I skipped
fastboot erase userdata
Because I didn't want to erase all my data.
I knew I hadn't used BTFM.bin, frankly, I didn't know what to do with it, so I just skipped it. Now that I realize it's for the bluetooth radio, I have gone ahead and flashed it just now, after the fact. Hopefully this will improve my bluetooth performance a bit...I've found that if this phone is in my hip pocked and I squat down to work on a piece of lawn equipment, my bluetooth gets very choppy.
I also skipped the
fastboot logo logo.bin
because I don't really care about the boot logo when I turn the phone on.
I also pulled a backup (pre-upgrade) of system_image in TWRP...do you think that would work better for you?
Click to expand...
Click to collapse
YES! It's great if you still have it!!! Could you upload it to your drive that you shared before?
Thank you in advance!
It's good thing I checked - I was already on the way to start getting ready for a more laborious update.
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
Interesting ... Could you still upload that system image file for QPWS30.61-21-18-7-3 to your file storage? I have not updated yet - too busy with other things, and wanted to do it carefully. Much appreciated!
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
Alright, I restored my system with your system image (many thanks!), and put back the stock boot. So it goes through the update (meaning the checksums are good), but then I get the dreaded "software update unsuccessful" message.
You could try this too, put back stock boot/recovery from the ROM, and see if it would update.
Edit: It looks like simply unlocking bootloader makes OTA fail:
"verity mode set to disabled"
I unlocked the bootloader of my G7plus, installed TWRP and then used TWRP to install Magisk. So far, everything is working, root hiding is working as it should and Magisk's "SafetyNet Check" is reporting success. Yay. Almost. a) During the boot...
forum.xda-developers.com
cllewis1 said:
And now I am getting an alert that another new security update is available, this one with the June 1 patches. New version is called QPWS30.61-27-18-7-10. This one isn't on the Lolinet mirror yet.
Click to expand...
Click to collapse
7-10 is available now:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
bibikalka said:
7-10 is available now:
https://mirrors.lolinet.com/firmware/moto/lake/official/RETLA/XT1965-T_LAKE_RETLA_10_QPWS30.61-21-18-7-10_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks, got it installed. Works fine.
cllewis1 said:
Thanks, got it installed. Works fine.
Click to expand...
Click to collapse
Looks like 7-12 is available:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Way too many updates, LOL
Is that 7-12 fie working on your xt1965-T (cause on lolinet its labled xt1965-2) and that doesnt seem right.
Hi everyone, and a happy new year
I need some light please, i don't understand what i'm doing wrong :/
To follow this post, i can't install EU ROM anymore (via TWRP) and i don't know why...
1) i flash the EEA Global via MiFlashTool, all ok
2) i make sure to unlock bootloader, all ok
3) i flash TWRP (official 3.6), all ok
Finally i want to flash 12.5.20.0, or 12.5.17.0 of EU ROM via TWRP/install, the process end up nicelly, no error so reboot, now everytime /data is lost, so it only boot on twrp and nothing is here anymore, need to go back at 1)
That is so frustrating :/
Can anyone enlight me please ?
did you format data after flashing 12.5.20.0
marcel112 said:
did you format data after flashing 12.5.20.0
Click to expand...
Click to collapse
nope, i need to ?
(if i format data, then i'll need to reflash the rom, right ?)
Only fastboot Version available right now bro. Already using it.
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
marcel112 said:
If you want to flash 12.5.20 it's impossible to use TWRP.. it's android 12 and fastboot only
Click to expand...
Click to collapse
Thanks both of you !
Ok, but when i see files like 12.5.20.0 with a twrp flashing procedure labelled Mi11 Ultra, that let me think i can do it that way, it's misleading, at least :/
So, i flashed the latest 12.6 xiaomi eu rom and it worked
New problem, i then try to use twrp to flash magisk, i do fastboot boot twrp.img and then, /data lost again, so impossible to flash magisk :/
I tried both 3.6 official and 3.5.1 unofficial
p.s.: never set security pin/pass or whatever atm, so it's not a problem with the password
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
marcel112 said:
why do you want to try twrp to flash magisk?
copy the boot file from fastboot / images folder to your phone.
boot system, open magisk app, choose install, and search the boot file, patch. once patched, copy the file to the fhe pc.
reboot to fastboot
just type fastboot flash boot yourpatchedbootfile.img
you can type fastboot flash boot and drag the patched file to fastboot line
Click to expand...
Click to collapse
Oh my god, i totally forgot this method
Thank you very much, seems to work !
Solved
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.
lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.
stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.