Hello dear people !! ^^
Since we have in a short time Android 10
We don't have recovery for it.. Sadly enough but..
I found this on a chinese forum and make a guide of it.
I don't own the Xperia 1.. Not yet but next week i have one,
So i hope all you people understand this guide because i
explained it as far i can do it.
----------------------
.. Requirements ..
Unlocked bootloader
Xperia 1 Or 5
Android 10
Knowledge howto flash
----------------------
Important !!: rename your patched boot.img what you did
with magisk to kernel.img in put it in this zip Here
1: Remember to back up all your data
2: Make a clean install of the firmware,
!! don't boot after flashing !!
3: Turn the phone into fastboot mode
and connect and type this command in cmd window:
fastboot flash boot twrp-xperia1.img
Here the fastboot twrp file
4: fastboot this command of vbmeta:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Here the vbmeta file
5: Press and hold the volume down and power at the same time,
release the powerbutton but keep
pressing volume down button till you enter twrp.
6: Copy the 3 zips:
The boot.zip where your own kernel.img is inside
what you did at the beginnig of these steps
twrp-Xperia1-3.3.x.zip: Here
Magisk-v20.1.zip: Here
to the phone storage, and flash in twrp
7: Start it up and done
Note: If you encountered
damaged internal storage, format internal memory in twrp
and all went just fine.
... Credits ...
M-Rom
Res
This doesn't lead to success with an Xperia 5. Once you try to boot into TWRP at step 5, you got a note that the device is corrupt and will shut down in 5 seconds.
Thanks ASap people try this I will install and try it! Know bug? Is this still in very testing version? For the moment I don't want to touch my device.
The clean install is necessary? Any incompatibilities with some magisk modules? Im currently using: smali patcher, taichi, youtube vanced
Why isn't there a Thread in the Xperia 5 Forums? Just found this out of Luck...
Instructions are also bit confusing... Where is the vbmeta.img from? Google? And why do i need a boot.img if we have already a TWRP boot.img? Will the one boot.img not replace the other?
Flashing a new Firmware makes also no sense if you just do "fastboot -w" to erase all Userdata. (If coming from a clean Firmware like i do, or You do right after unlocking Your Device)
Edit: So in a nutshell
-We do boot up the twrp boot.img to be able to flash Zips!?
-We do flash vbmeta to unsecure our booting!?
-We do flash our own boot.img with the Zip that the Device can work right!?
-We do flash the TWRP Zip which edits our Ramdisks to add TWRP
-We do flash Magisk (Optional!?) for only Root? Or also needed Kernel changes!?
Would be nice to also make links to XperiFirm and UnSin to get the boot images...
You could also edit the boot.zip script for "magisk_patched.img" so users don't have to rename it
Just want to support that btw. Thanks for Your work anyways!
---------- Post added at 15:47 ---------- Previous post was at 15:07 ----------
Xperia 5 booted well into TWRP but it freezes everytime i start a flash or wipe. Got the storage to work with fastboot -w after flashing the twrp and vbmeta images. Adb Sideload does also not work. Looking forward to a working version!
TWRP unable to flash zips
Well, the title says it all. I can flash the twrp image, but it freezes when flashing zips or starting sideload. I'm using a J9110. I understand you're not supporting here, but just in case you had some tips. Oh and by the way, hoi vanuit Leiden
EDIT: Found the fix: don't change the language to english before opening twrp, and it will flash just fine!
xperia 5 fix plz
I've installed this, it work but boot in chinese and cant load the usb mtp driver on my pc, I cant move the boot.zip to flash, had it put on sd card, cant find the sd card on this crappy twrp, for me is a no. I'd just stick with patched boot until something better will work.
mtp should work if you follow every instruction and boot twrp in chinese.
Having the same issue as others... it appears as though the internal storage is encrypted, but I have no lock screen enabled in the ROM. No Passwords or Fingerprint either. Tried wiping data from within TWRP froze the system. Performed a wipe from within ROM, and now the ROM shows internal data folders as though they're encrypted. Need a pinch of help here.
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Is there any update to this?
Hopefully with 3.4 will bring a more stable twrp. It includes changes for devices updated to Android 10
I hope can teach how to get your patched boot.img
It's not too much complex to make it work
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
benben233 said:
I hope can teach how to get your patched boot.img
Click to expand...
Click to collapse
It's not too hard to get one
Get the origin boot.img from xperiFirm, twrp.zip
boot into any twrp on any device
backup your own boot paritition
install the boot.img, twrp one by one
then backup the boot partition, you get the patched-boot.img
Tenhow.XDA said:
download firmware from xperiFirm
unsign the boot.sin to get boot.img for your xperia 1
flash the twrp.img to your boot slot_a/b
boot into twrp
install the boot.img, twrp.zip, magisk.zip
now everything works
Click to expand...
Click to collapse
On latest android 10 and fw .28 it works ? @Tenhow.XDA
Any sign of Android 11 TWRP for Xperia 1?
MrMmmkay said:
Any sign of Android 11 TWRP for Xperia 1?
Click to expand...
Click to collapse
No
Related
Huawei recently shipped update B180.
They advised to unroot the phone first, but I have been stupid and updated with TWRP installed on the second recovery partition (e-recovery?) and the update failed.
My phone now won't boot. I can put it in fastboot/recovery mode and access TWRP, so I guess all I need is a stock ROM.
I cannot find anything useful for Honor 7 with Google, I would like a recent ROM (most recent I found is a B130).
I would also appreciate some advice on how to recover from this boot freeze.
Would flashing a stock ROM with TWRP be enough?
Thank you very much.
I'm kinda pissed since that phone is quite expensive.
You cannot flash a stock rom with TWRP.
You have to flash the stock recovery then a stock rom, using fastboot.
The more recent stock rom available is the B130, unfortunatly.
Have a look at my posts, I have done similar (although I had the normally recovery.img installed) you need to downgrade using the marshmallow downgrade ROM then to the full 121 or 130 ROM after putting the stock recovery back (for the version your phone was on before this happened I assume it was 170 if you were going to 180) once you are back on 130 you can then upgrade up to 180 through the usual process. I have done this a few times and it has been fine whilst experimenting with the device.
The current version of the phone appears to be burned in to it (I think curver.img is doing this inside the UPDATE.APP but I haven't found a way of flashing this file back to the phone to play around with downgrading without the MM downgrade ROM), this I think is what causes it to hang if it has a boot.img and recovery.img that does not match the version the phone thinks it is.
I am in the same boat with @rbuccia.
I can only access fastboot and recovery (twrp).
I also found that I must have something wrong with 3rdmodem because if i wipe form inside twrp I always get an error message on that partition.
Also I have a rom from Kangvip flashable with twrp but veven this has no effect.
I think that we cannot unbrick it without a completely and full stock rom but I think there is no one.
Any idea?
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
james194zt said:
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
Click to expand...
Click to collapse
Thanks for the tips, but
1. Where can i download the B180 full firmware?
2. I can't access the VOL+ VOL- POWer AKA updater mode, it just bootloops.
Thx :laugh:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
james194zt said:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
Click to expand...
Click to collapse
I must be blind, but i can only find the ota updates, not the full stock firmware :/
Thx tho, i'm starting to understand a bit better how it works and how i can fix it.
I'll just try to flash boot and recovery for B100 and B130 untill i cant make it work, for the system.app tho i can't take the B180 as i can't find it.
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
james194zt said:
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
Click to expand...
Click to collapse
Thx for the reply ! But that's what i said earlier, when i flash boot.img, system.img and recovery.img from the B130 update.app, the phone still bootloops.
I have access to the Huawei E-recovery if i do VOL+ POWER while the phone is plugged in the pc
I have access to the fastboot mode if i do VOL- POWER while the phone is plugged in he pc
I DON'T have access to the software mode upgrader if i do VOL+ VOL- POWER, no matter is the phone is plugged in or not
The phone still bootloops, plugged in or not.
:/
You need to flash boot.img and recovery.img from 180 and system.img from 130, sorry if that was not clear above! the boot loop is being caused because the boot.img doesn't match the version your phone thinks its on, if 180 doesn't work try the version before you upgraded i.e. 170 the system.img is just the android OS if you see HONOR glowing then you are booting system.img at that point but if it isn't glowing then you are still in the bootloader at that point so you need to sort out boot.img.
I've never been in 180, and as i said, i can't take the boot and recovery.img from the OTA update, i need a full stock firmware of B180 ! :/
Thx for the help tho.
I already tried to flash boot.img from B100 b121 and B130, and the phone still bootloops :/
http://forum.xda-developers.com/hon...dating-to-b180-fastboot-t3317249#post65420964
This fixed it!
Found this and it worked for me.
Download latest Official Full ROM from EMUI's site, HuaweiUpdateExtractor and adb / fastboot.
2. Unzip ROM and open UPDATE.APP with HuaweiUpdateExtractor.
3. Extract SYSTEM.img and RECOVERY.img (delete .header files that HuaweiUpdateExtractor generates you need only .img files) and put them in adb folder.
4. Boot in fastboot and conect to PC. (You can achieve this from TWRP to boot to bootloader, adb dosent work but fastboot will there is also key combination to get to bootloader/repair mode or what it is).
5. Open cmd.exe from adb folder and type (or copy-paste) the follow commands one by one:
Code:
fastboot devices
Code:
fastboot flash recovery RECOVERY.img
Code:
fastboot flash system SYSTEM.img
And finally where i had some trouble:
If you got no permissions try again or take usb cable off etc. Took me while to get back from same situtation. Few reboots to TWRP and to bootloader and USB replugging while in bootloader.
And for LINUX: i used split_updata.pl-master from github to extract the .APP/Firmware needed to sudo fastboot aswell.
Hiiiii guys
Please help me respected sir and other friends.
Anyone have twrp backup of stock rom ?
Because I want go back to stock rom and I have only twrp not pc please thanks in advance
Hi,
After much read of guides, I post here my SIMPLE guide for OTA upgrades when your Moto G is unlocked and you use systemless root and TWRP.
This guide is safe and works!
For example, with this guide you can upgrade from STOCK MPJ24.139-23.4 to MPJ24.139-63:
Warning: I assume you know the concepts "fastboot", "systemless root" and TWRP.
For the original stock firmware search here for your exact MODEL and VERSION: http://mirrors.lolinet.com/firmware/moto/athene/official/
1) Reboot to TWRP and make a FULL BACKUP of your current firmware. Use the SD-Card and not the internal memory.
2) To Apply the OTA you need to restore BOOT.IMG and SYSTEM.IMG.
2a) If you rooted your device, for sure your BOOT.IMG isn't the original one. You can:
- Option 1: Restore it from an original backup of your firmware (if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "boot.img" and flash it in the fastboot mode using "fastboot flash boot boot.img".
2b) If you use Systemless SuperSU then your system partition can be untouched. In case of doubt, or if the patch shows an error, you can restore it...
- Option 1: Restore it from one backup of your firmware (only if you backup it prior to root).
- Option 2: Download the STOCK and ORIGINAL firmware for your device, extract "system.img_sparsechunk.0-7" and flash them in the fastboot mode using these 8 commands (execute one, wait until completes, then execute the next one):
Code:
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 system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
3) Boot to the TWRP Custom Recovery (you don't need to restore the original Recovery partition).
4) Download the OTA (Blur_Version.24.24.4.athene.retail.en.US.zip) or copy it from the downloaded directory. Copy the ZIP file to a computer, extract the file "/META-INF/com/google/android/updater-script" and edit it... Remove these three lines (this only removes the check of the running build, because you like to execute it inside TWRP):
Code:
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-63/64:user/release-keys" ||
getprop("ro.build.thumbprint") == "6.0.1/MPJ24.139-23.4/4:user/release-keys" ||
abort("Package expects build thumbprint of 6.0.1/MPJ24.139-63/64:user/release-keys or 6.0.1/MPJ24.139-23.4/4:user/release-keys; this device has " + getprop("ro.build.thumbprint") + ".");
After that, copy (repack) this edited file to the ZIP file of the OTA. I suggest to change the name of the ZIP, for example to "Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip". Now, you can run this patch file running TWRP.
5) Copy the patch OTA file to the SD-CARD, boot to the TWRP and apply the OTA... After several minutes the task completes. Reboot and check if the update is done and all works well. Your data needs to be already there...
6) Reboot into the fastboot mode and reflash the TWRP Custom Recovery using "fastboot flash recovery twrp-3.0.2-0-athene.img". Then boot in the recovery mode and do another Backup (for save untouched "system.img" and "boot.img" partitions).
7) Now you can re-root using the TWRP mode and SuperSU 2.78 in Systemless mode (remember to execute "echo SYSTEMLESS=true>>/data/.supersu" prior to install the SuperSU.zip)
I hope this helps you!
This guide only uses the minimum and required steps.
:good:
If you like to download one already patched OTA, then download it from here (join the two files first!):
Part 1: http://www.sendspace.com/file/dkws7p
Part 2: http://www.sendspace.com/file/xaompg
Part 1: http://www.sendspace.com/file/e3of46
Part 2: https://www.sendspace.com/file/a3tl4r
CRC:
filename=Blur_Version.24.24.4.athene.retail.en.US-TWRP.zip
size=508332365
crc32=AFEC5752
Thank you, I was wondering about just this. Will come In handy.
Do you need to resign the zip with signapk?
Thanks for you guide!
I used it to update my Lenovo P2 to Nougat.
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Indianvixen9 said:
I would love to unlock my phone, alas, I am on an amazon variant of the G4, so it cannot be done. I would love to try out the OS listed here.
Click to expand...
Click to collapse
I've heard this from a few people. I got the Amazon variant little more than a week ago. Unlocked BL and rooted lickety splits, no issues.
I consider myself pretty tech savvy, but the post might as well have been in Swahili. Can it be dumbed down any further?
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
t0mm13b said:
Do you need to resign the zip with signapk?
Click to expand...
Click to collapse
No, just re-zip! :victory:
Dbush72 said:
The links at the end of your post for the two patched ota downloads aren't any good, would you please upload them again? Thanks
Click to expand...
Click to collapse
Done! :highfive:
Thank you for the reply and refreshing the download links
As far as I can tell you are flashing this via TWRP which is why the zips dont need signed is that correct?
I have an xt1625 non-amazon version that im working with.
I tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-49_cid50_subsidy-DEFAULT_CFC.xml which didnt work with this error:
E3005: "EMMC:/dev/block/bootdevice/by-name/boot:
has unexpected contents
I also tried flashing Blur_Version.25.11.12.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
Failed with the same error as last time
I also tried flashing Blur_Version.24.31.48.athene.retail.en.US on top of ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml which does seem to pass the version checks but gives this error:
"eom/app/BRApps2/oat/arm/BRApps.odex" has unexpected contents.
Hello, I'm kind of new at this (this is my first post) so be gentle
So, the last few days I've been trying to install a new rom on my phone (Redmi Note 4X) and the problems started with the model. I only seem to find Redmi Note 4 roms, and as I've come to find, mine is supposed to be the mido one (correct me if I'm wrong though). I have unlocked the bootloader, I have installed and enabled the fastboot on my phone, so the next step was to install the latest TWRP.
There came more problems; I tried doing this through the app and it just wouln't flash it. So I found a guide on how to root my phone and install a new recovery through adb and I followed it. It didn't work. I couldn't find the right twrp version for my phone. When I finally did realise my phone needed mido, I found the latest from the TWRP website. It wouldn't load through adb again. I found a thread about a fixed mido version, which finally worked for me. But my brother who was helping me, and isn't as much of a noob as I am (he has flashed rom and recoveries many times on his Nexus 5X), decided that I necessarily need the latest twrp if I'm going to flash a new rom, so he flashed the new twrp through the old one, and soft bricked my phone (I think). So I'm searching for a guide to unbrick it. (Which I can't seem to find to work at least).
To conclude;
I have unlocked my bootloader
I have access to the fastboot
I tried to flash a recovery
I failed many times, but I managed it
I flashed the latest twrp and bricked my phone
I don't have access to the recovery
My phone is still on a bootloop
I am not sure about which phone model I have
Help!
Thanks in advance.
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Dyt199412syam said:
1. Just check your phone model on its box. If its Snapdragon version (Mido), then just install it via fastboot. (code: fastboot flash recovery twrp-midoxx.img). If you are success, then try to reboot to recovery (fastboot boot twrpmido-xx.img). After booted, then you just manage to rom.zip you want to install. If you don't have it, then download it before from your PC and push it to your phone. Or just enable Mtp checklis from TWRP n copy that file to your internal phone/sdcard. Wipe all/factory reset except internal storage. Then you dan install rom.zip normally. N reboot. (Note: if you are on MIUI and wanted to always stay on it, just flash the file called lazyflasher.zip. n' wipe cache n art cache only then reboot). Flashing custom recovery on stock MIUI Will manage the device Going to bootloop)
2. If you have mediatek version (nikel), searching the fastboot Rom from miui website and flash it normally via fastboot. (SP Flash tool)
Warning: flash the wrong rom file into wrong phone Will make your device brick. So becarefull n knowing what model/code name you have.
Click to expand...
Click to collapse
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
fionik said:
Hello and thanks for the reply. I have the snapdragon version, but all I'm asking is how am I supposed to flash the lazyflasher without accessing the recovery? Through adb?
Click to expand...
Click to collapse
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Dyt199412syam said:
Firstly, enter fastboot mode on your device. Connecting to pc and flashing the twrp for mido. "fastboot flash recovery twrp-mido.img". Then boot to it using " fastboot boot twrp-mido.img". Then you will enter the recovery (twrp) in a second. Copy the lazyflasher into your phone (enable mtp first in Mount option in twrp) that you downloaded from pc. Just flash the lazyflasher.zip and reboot.
And why you don't want to flash lazyflasher when it very easy to flash it using recovery twrp? adb? You mean android debugging? Actually, you cant flash a .zip file into your system partition except through fastboot mode. However, fastboot mode (in cmd) only recognize a .img file. I just try to tell you the easier method to make your device boot up.
Click to expand...
Click to collapse
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
fionik said:
As I said above, I can only access the fastboot, and I get errors in the adb when I try to flash the twrp image.
Click to expand...
Click to collapse
Share your error please.
Try fastboot boot twrp.img
Ok, I am new to this. My op3 was on oxygen os 5.0.8. I first unlocked my bootloader, then flashed twrp, and through twrp i have flashed Magisk 18.1. Then I cleared data, dalvik and cache and started a reboot. I am now in a bootloop, tried to uninstall Magisk through the uninstaller, but still i am in a bootloop. So please help me with the bootloop or guide me on how to get back to stock rom and recovery.
N1mbus17 said:
Ok, I am new to this. My op3 was on oxygen os 5.0.8.
Click to expand...
Click to collapse
Hello, have you tried flashing the stock boot image from fastboot?
I donno how to flash stock boot image with fastboot, can i flash that img with twrp?
N1mbus17 said:
I donno how to flash stock boot image with fastboot, can i flash that img with twrp?
Click to expand...
Click to collapse
What happens when you place your stock boot image somewhere you can access from TWRP and try?
If you want to try fastboot method:
Download the version of OxygenOS you’re currently on
Extract the contents of the ZIP file from Step 1
Copy/move the boot.img file to the same directory as your ADB/Fastboot tools
Launch a Command Prompt, Terminal or PowerShell in that directory
Boot the OnePlus 3 into Fastboot Mode
Connect the OnePlus 3 to the PC with a USB cable
Type the following into the Command Prompt, Terminal or PowerShell. . .
Code:
fastboot flash boot boot.img
. . .then press Enter on the keyboard
Wait for the boot IMG file to be sent and written
Then press the Power button on the OnePlus 3 to reboot back into Android
adapted from https://www.androidexplained.com/oneplus-5-stock-kernel/
united_we_stand said:
What happens when you place your stock boot image somewhere you can access from TWRP and try?
If you want to try fastboot method:
Download the version of OxygenOS you’re currently on
Extract the contents of the ZIP file from Step 1
Copy/move the boot.img file to the same directory as your ADB/Fastboot tools
Launch a Command Prompt, Terminal or PowerShell in that directory
Boot the OnePlus 3 into Fastboot Mode
Connect the OnePlus 3 to the PC with a USB cable
Type the following into the Command Prompt, Terminal or PowerShell. . .
Code:
fastboot flash boot boot.img
. . .then press Enter on the keyboard
Wait for the boot IMG file to be sent and written
Then press the Power button on the OnePlus 3 to reboot back into Android
adapted from Link
Click to expand...
Click to collapse
Ok I will try this method, but what will happen to twrp if I flash through fastboot, will it get removed and replaced by stock recovery?
N1mbus17 said:
Ok I will try this method, but what will happen to twrp if I flash through fastboot, will it get removed and replaced by stock recovery?
Click to expand...
Click to collapse
Hi! in the following command
Code:
fastboot flash boot boot.img
fastboot is the tool
flash is the operation
boot is the destination partition
and boot.img is the source
so to answer your question, TWRP should remain unaffected, as it should reside on your recovery partition
united_we_stand said:
Hi! in the following command
Code:
fastboot flash boot boot.img
fastboot is the tool
flash is the operation
boot is the destination partition
and boot.img is the source
so to answer your question, TWRP should remain unaffected, as it should reside on your recovery partition
Click to expand...
Click to collapse
Ok i did a wipe on cache, dalvik and system, flashed the official os zip file with TWRP and i am still stuck in a bootloop. I haven't tried your method yet where you flash the boot.img as it's just 15mb while the zip file is 1.5gb. What am i missing here? Is my TWRP recovery installing the os zip file correctly? I am stuck.
This is what i have done till now:
Unlocked my bootloader
Flashed official TWRP (twrp-3.2.3-1)
Then cleared data, cache, dalvik and flashed Magisk
Rebooted and got stuck in a bootloop
Used magisk uninstaller but didn't work
Downloaded official Oxygen OS 5.0.8 and then went to twrp, wiped dalvik, cache, data, system and then flashed the zip file.
Rebooted and still stuck in a bootloop
I am now scared that this phone won't startup. Please provide a solution.
Ok, i have followed the mega unbrick guide for oneplus 3 and it has finally come out of the bootloop, it's now updating to the latest oxygen os. Sadly i donno what went wrong the 1st time i tried to root with Magisk, maybe the oreo on the op3 doesn't support magisk. If it's possible can you guide me into rooting the phone with magisk, as most of the tutorials are old and for marshmallow rom and recovery. Thanks.
Current State:
TWRP Installed, no OS, no system partition, instead a super partition.
I also flashed an orange_state_disabler which seems to have worked just fine.
ADB Sideload:
When I try to start ADB Sideload Feature this is what I get:
https://pastebin.com/k3gJ048P
when trying to use the adb sideload command:
Code:
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
I converted the lineageos img file I have to a flashable zip using the tool from here:
https://forum.xda-developers.com/nu.../swapper-generate-flashable-zips-img-t4133591
but when I try to flash that zip file tho it returns this:
Code:
Installing zip file '/usbotg/system.zip'
Checking for Digest file...
Unmounting System...
Invalid zip file format!
Error installing zip file '/usbotg/system.zip'
Updating partition details...
...done
so... yeah, I don't know what else to do right now.
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
jwoegerbauer said:
A Custom ROM like LineageOS can only get installed via TWRP, not by any other means: in no case by "adb sideload".
Click to expand...
Click to collapse
Heh, I was just trying to get the ROM on the device so I could flash it then via TWRP but maybe I just misunderstood what adb sideload does
0
Seppppx said:
The Oneplus 8 Pro has a dynamic partition layout and you flash a system image by doing "fastboot flash system system.img"
See : https://forum.xda-developers.com/oneplus-8-pro/development/rom-lineageos-17-1-t4122983
Click to expand...
Click to collapse
Yeah I tried that already, the problem is that it doesn't have a system partition
MoonPadUSer said:
Yeah I tried that already, the problem is that it doesn't have a system partition
Click to expand...
Click to collapse
Your posted error messsage suggests the zip install has failed. So no change to device should have happened.
Current twrp cannot flash system.img
Only super.img(combined system.img, vendor.img, and product.img)
The systemswapper you refered to is from a qualcom device thread, and uses some *qti* device binaries that are not in your recovery. It is unlikely to have worked. (I might be wrong about the *qti* binary being only a qualcom device tool)
These new devices with dynamic partition have 2 fastboot modes.
The bootloader mode (adb reboot bootloader)
This is used for unlocking bootloader, flashing standard partitions
There is fastbootd mode (adb reboot fastboot)
This mode is only available if stock recovery is installed.
It also requires r30 or higher fastboot binary file on PC.
From fastbootd you can flash the sub partitions on super.img
There is alot of changes that take place with this new partition setup.
As for your phone no longer booting into original system, and bootlooping to recovery, I suggest first try boot to bootloader, and flash stock recovery, see if this stopps the bootlooping.
If not then use sp flash tool and flash full stock room and start fresh
mrmazak said:
From fastbootd you can flash the sub partitions on super.img
Click to expand...
Click to collapse
How?
MoonPadUSer said:
How?
Click to expand...
Click to collapse
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
Code:
fastboot flash system /some-directory-on -pc/gsi-system.img
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
MoonPadUSer said:
How?
Click to expand...
Click to collapse
I did another post about using fastbootd on similar device. The information is all relevant to your a7pro too.
https://forum.xda-developers.com/showpost.php?p=83241985&postcount=3
mrmazak said:
Fastbootd is part of stock recovery, it will look different than what you may be used to as being fastboot mode.
You should see options on screen to select just like stock recovery has.
One for boot to bootloader
One for boot to recovery.
When you confirm you are in fastbootd
You just use
You should see messages on screen
Resizing system
Sending sparce system chunck. 1 of x
Writing system chunck 1 of x
There could be more descriptive guide on flashing gsi on dyniamic partitions if your Search google, (xda).
But it is hard to guide you to fixing device, when I'm not sure how you got stuck. I mean the description you have said should not have made you loose system partition or fail to boot, so I said it before and will suggest it again. If you have a non booting device , the FIRST thing you should do is flash it with sp flash tool and full factory rom, before messing around with other stuff before you get into worse condition
Click to expand...
Click to collapse
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Where I am right now:
I am back to a fully working device after downloading the stock ROM from my manufacturer and plugging that into SP Flash tool
After that I researched and figured out that the super partition I have basically acts like a container for
system.img, boot.img and vendor.img
which explains while simply flashing LineageOS.img to my super partition (
Code:
fastboot flash system Lineage.img
) resulted in
my device not booting anymore.
I found a tool which can unpack those super.img into system, boot and vendor
(using this youtube video: https://youtu.be/J5cQdzivtXk)
I used that to unpack the super.img which I got from my stock ROM and
now I have system.raw, boot.raw and vendor.raw, I do not know what kind of file these are but my plan is to replace system.whatever with the lineageos.img and then repack it into super.img which I can then use to flash the super partition on my phone
MoonPadUSer said:
Ok, I am back to a fully working device again, where I got stuck was that I do not have a system partition, thus I can't flash it. Whenever I try to flash it using fastboot flash system or anything else, it just says that I do not have a system partition
Click to expand...
Click to collapse
Can you show picture of this .
Of both pc screen and phone screen, please
mrmazak said:
Can you show picture of this .
Of both pc screen and phone screen, please
Click to expand...
Click to collapse
I'd love to but how am I supposed to take a picture of my phone screen in fastboot mode? (I don't have any other devices with a camera)
@MoonPadUSer
Code:
fastboot flash system Lineage.img
must have failed.
Reason: This command tries to write a complete Lineage OS ( what itself contains a partition named /system, too ) into phone's Android's current /system partition - what only is 1 partition of multiple ones that exist.
Note: You can't flash a Custom ROM by means of Fastboot.
Re-read post #2
0
Seppppx said:
That's not true when you are flashing a Generic System Image.
Click to expand...
Click to collapse
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
jwoegerbauer said:
ROFL
Remember OP wants to install LineageOS 17.1 what isn't a GSI as it is with LineageOS 18.x
Click to expand...
Click to collapse
Actually... I don't really care about the version all that much, whatever works, just didn't know if 18x is supported
Downside to Lineage GSI is for Umidigi you can't flash gapps. So unless someone adds it to the gsi for you it's best to use something else.
I went with this
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
You have to get the AB version with GAPPS if you want them
Comes pre rooted as well and gave my phone a huge speed boost
Flash the stock ROM
Unlock bootloader
fastboot flashing unlock
(unnecessary if already unlocked)
fastboot flashing unlock_critical
enter fastboot
fastboot reboot (to enter fastbootd)
fastboot erase system
(optional but I had to do this myself)
fastboot delete-logical-partition product - deletes the product partition, allowing a larger system partition
fastboot flash system (gsi file)
And you're good
Don't try to install magisk because it causes a bootloop. Even when installing it through the app. Once the boot image is patched you're in a bootloop until you reflash the stock boot
Made a generic ish Umidigi flashing tutorial because it's the same in all of them I've had so far
https://forum.xda-developers.com/an...ng-rom-gsi-t4182673/post83803205#post83803205