Related
Some info first:
Carrier: Sprint
Running the Latest TWRP (packaged with Pantheon Kernel), and SuperSu (Huge thanks to joemossjr, Uzephi, and enetec for their respective works, and others!)
So, I'm just trying to grab a little clarity...
Currently I am on "Slot A". When I first purchased the phone, I was on Slot B, and the series of events occurred as such:
Performed all security updates to October
Unlocked Bootloader
Flashed TWRP
Flashed SuperSu
-profited-
Stuck a fork in electrical socket and pressed "reboot system [SLOT A] (When I was on Slot B) - *womp womp*
Was unable to boot to anything except fast-boot
Flash-alled fresh system (Thanks again to all the work over in the development section!)
Performed all security updates to October
Flashed TWRP
Flashed SuperSu
-back in the money-
^^^ Where I am at now, except on SLOT A
So... here's where I need some clarity... if the Slot A / Slot B system works as a pass/trade system between two OS's, effectively allowing consecutive updates.. why did my system hit the crapper when i switched slots?
Theoretically, it should have simply booted into whatever my prior to flashing [what goes here? was it SuperSu that caused the derp, or TWRP?]
Also, now that we have a functioning TWRP as well as a functioning Security check for October, will we get to the point where we are able to actually just flash to separate partitions easily, and thus boot into separate roms easily?
I totally assume I'm missing some vital information above with my understanding about the discrepancies between Slots, as well as other partitions , so feel free to point at laugh at the short-bus kid... so long as you fill me in the gaps in my understanding.
Thanks!
My experiences are according with all you reported... I've done some "stock system" backups too (both A & B...) and I can confirm they differ from day one too...
It seems to be clear that things are a bit more complex than our speculations on them...
So far what I've tested: When you flash all, you go back to slot A (I assume the fastboot erase DDR is what causes it to go back to slot A). In essence, I have had October update on slot A and B by choice by choosing a different flashall zip.
oem is one partition. it is one HUGE partition, but one none-the-less (about 600 MB). The phone sees it as two though (sde19 and sdf19) User data is one partition. (sdb21) SSD is one partition (sdb1).
This means dual booting an OS needs to be similar (where they can share userdata and not cause boot loops) as user data (/data) is shared across both boot-a/boot-b ; system_a/system_b (sde17/sdf17 ; sde18/sdf18)
A lot of vendor specific issues in /crypto of the kernel causes some idiosyncrasies with encryption. any kernel update I do that involves /crypto or /fs edits causes a plethora of headaches.... one kernel update broke ADB and partially broke fastboot
Edit: your user data was decrypted with SU. So slot B was not encrypted. when you went to slot A (was encrypted) your phone couldn't read it.
Uzephi said:
...
This means dual booting an OS needs to be similar (where they can share userdata and not cause boot loops) as user data (/data) is shared across both boot-a/boot-b ; system_a/system_b (sde17/sdf17 ; sde18/sdf18)
Click to expand...
Click to collapse
I agree. When I made some speculations about dual booting (in another thread) I was thinking the same OR switching/recovering different /data by TWRP backup/restore...
Uzephi said:
...
Edit: your user data was decrypted with SU. So slot B was not encrypted. when you went to slot A (was encrypted) your phone couldn't read it.
Click to expand...
Click to collapse
If things here works as on Moto Z (Griffin) your sentence should be... "You have /data decrypted since of SuperSU tweak. Slot B has no more force encryption enabled since of this tweak. When you went to slot A (still with force encryption enabled since of no tweak installed), your phone will begin to encrypt /data partition again (it can read both encrypted and not encrypted, but if not encrypted it will encrypt at first boot) and, since of the long time required by operation on any /data partition not just formatted, it seems to hang/bootlooping..."
enetec said:
If things here works as on Moto Z (Griffin) your sentence should be...
Click to expand...
Click to collapse
The Griffin is different. The kryo msm8998 has it's own encryption chip built on the CPU. our kernels disable that so then everything goes software encryption which causes a bunch of issues. It's the only way we could get TWRP to decrypt the phone.
Uzephi said:
The Griffin is different. The kryo msm8998 has it's own encryption chip built on the CPU. our kernels disable that so then everything goes software encryption which causes a bunch of issues. It's the only way we could get TWRP to decrypt the phone.
Click to expand...
Click to collapse
...interesting!
enetec said:
...interesting!
Click to expand...
Click to collapse
https://www.qualcomm.com/documents/snapdragon-835-mobile-platform-product-brief Page 2 of the PDF, they call it "Qualcomm Haven Suite."
So essentially, Qualcomm took the initiative to "secure" us... For **our** benefit... Potentially against our will... Whereas before, we could choose to software encrypt if we wanted, and software decrypt at our discretion...
Obviously I'm being facetious, this seems to me to clearly be for the benefit of OEMs and Providers. Don't get me wrong, hardware microchipped encryption is kick-ass, especially how fast it manages it.... Just not how it's been utilized here.... As a massive firewall against 3rd party fingers in the pie.
Some_Donkus said:
So essentially, Qualcomm took the initiative to "secure" us... For **our** benefit... Potentially against our will... Whereas before, we could choose to software encrypt if we wanted, and software decrypt at our discretion...
Obviously I'm being facetious, this seems to me to clearly be for the benefit of OEMs and Providers. Don't get me wrong, hardware microchipped encryption is kick-ass, especially how fast it manages it.... Just not how it's been utilized here.... As a massive firewall against 3rd party fingers in the pie.
Click to expand...
Click to collapse
Yes, it's a simple flag in the defconfig file
Here is the slot swappin' solution you were looking for!
Download the most current official Google fastboot:
https://developer.android.com/studio/releases/platform-tools.html
Go into fastboot mode and type on PC:
fastboot set_active _a
(then boot to recovery, check TWRP to see you are on slot _a)
fastboot set_active _b
(then boot to recovery, check TWRP to see you are on slot _b)
Please note: I am sure the a/b switch inside our phone's TWRP will eventually work, but it doesn't currently (as of 17NOV2017); other a/b phones have had the same issue.
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Some_Donkus said:
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Click to expand...
Click to collapse
this method works for me
https://forum.xda-developers.com/showpost.php?p=74543389&postcount=10
jhofseth said:
this method works for me
https://forum.xda-developers.com/showpost.php?p=74543389&postcount=10
Click to expand...
Click to collapse
Oh, haha! I totally missed this post in the thread. Herp-A-Derp! Thank you! (I've been peepin' stuff via the XDA labs on my phone and I'm not used to the notifications and such, thanks for the rewind redirect!)
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
jhofseth said:
Download the most current official Google fastboot:
https://developer.android.com/studio/releases/platform-tools.html
Go into fastboot mode and type on PC:
fastboot set_active _a
(then boot to recovery, check TWRP to see you are on slot _a)
fastboot set_active _b
(then boot to recovery, check TWRP to see you are on slot _b)
Please note: I am sure the a/b switch inside our phone's TWRP will eventually work, but it doesn't currently (as of 17NOV2017); other a/b phones have had the same issue.
Click to expand...
Click to collapse
Great!
Anyway, looking at my a & b backups, it seems to me TWRP a/b switch is already working (they are different...).
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
Some_Donkus said:
What is interesting to me is that flashall flashes both slots, and you can manually choose to flash a specific boot with $flash boot_a or $flash boot_b. With this ability and enough experimenting I'm sure there's a workaround somewhere.
Click to expand...
Click to collapse
I could be wrong but... I've intended from my tests that fastboot without any slot specified flashes only the current one, not both...
---------- Post added at 02:56 PM ---------- Previous post was at 02:52 PM ----------
Some_Donkus said:
...
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
Click to expand...
Click to collapse
Theoretically... yes!
(But don't bet your ass on it... :laugh
Some_Donkus said:
Oh, haha! I totally missed this post in the thread. Herp-A-Derp! Thank you! (I've been peepin' stuff via the XDA labs on my phone and I'm not used to the notifications and such, thanks for the rewind redirect!)
So... theoretically... if I used the above method to swap into the "other" slot and flash both slots identical, with TWRP and SuperSu... I would be able to swap slots back and forth as I pleased... (even though they would be the same.. and thus making swapping between them.. kind of pointless...) because both would then have the same flag...
If i wanted to modify -ONE- of them, I would have to ensure that it matched the encryption state of the other... correct?
Click to expand...
Click to collapse
Once you have successfully booted into the other slot's boot (TWRP), you can see what condition the data partition is in with respect to encryption. If files are encrypted and you already backed up important data (i.e., same data partition shared by both slots, but different systems, boots, etc.), I would recommend formatting data in TWRP. After that, you should do this:
https://forum.xda-developers.com/showpost.php?p=74540731&postcount=21
This way, you will always be able to access data on the data partition, because it won't be encrypted.
(Either system partition can cause data to become encrypted again, so if you have to format data in one and run the above linked command, you would need to do the same in the other boot (TWRP).)
jhofseth said:
Once you have successfully booted into the other slot's boot (TWRP), you can see what condition the data partition is in with respect to encryption. If files are encrypted and you already backed up important data (i.e., same data partition shared by both slots, but different systems, boots, etc.), I would recommend formatting data in TWRP. After that, you should do this:
https://forum.xda-developers.com/showpost.php?p=74540731&postcount=21
This way, you will always be able to access data on the data partition, because it won't be encrypted.
(Either system partition can cause data to become encrypted again, so if you have to format data in one and run the above linked command, you would need to do the same in the other boot (TWRP).)
Click to expand...
Click to collapse
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Uzephi said:
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Click to expand...
Click to collapse
That all sounds like an insane amount of redundant PitA!!
I really wish I could be of more service in the coding department to help chip away at these types of lockdowns. Unfortunately, my skills are limited to Python and basic C++ console stuff.
This kind of stuff makes me pine for the days when my biggest challenge was trying to modify the UI in Qbasic and installing a power supply without a keyed molex lol.
So, IF we end up at a wall regarding this severe encryption despite the progress made so far, would we be able to patch in security updates "off the cuff" via custom made twrp or fastboot packages?
Uzephi said:
https://plus.google.com/+DeesTroy/posts/i33ygUi7tiu
Hopefully... Encryption won't be a worry
Click to expand...
Click to collapse
Very interesting article about how much Google "love us"...
Please note that at lower level even Motorola did the same on old Griffin (Moto Z)... if you upgraded bootloader (by OTA or by a flashall) during MM->N upgrade, you'll never able to install MM or downgrade bootloader (soft brick in first case and refuse to flash in second one...).
Obviously newer bootloader was't required and gave no benefits on older one...
For this reason on Moto's I ever hint not to flash bootloader even during flashall/debrick...
enetec said:
Very interesting article about how much Google "love us"...
Please note that at lower level even Motorola did the same on old Griffin (Moto Z)... if you upgraded bootloader (by OTA or by a flashall) during MM->N upgrade, you'll never able to install MM or downgrade bootloader (soft brick in first case and refuse to flash in second one...).
Obviously newer bootloader was't required and gave no benefits on older one...
For this reason on Moto's I ever hint not to flash bootloader even during flashall/debrick...
Click to expand...
Click to collapse
Tried adding the code from the pixel 2 because the xl 2 is it's own beast and due to the fact were not running Oreo like there it broke right around 78% and it was due to missing proprietary Google files
I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.
DualSix - Dual Boot for OnePlus 6!
Before You go further, keep in mind that it's mostly recommended for advanced users! And those who can calmly read instructions, preferably twice!
What does this tool do? And what are the benefits? DualSix allows You to boot two ROMs at the same time! You can flash OOS on one slot and AOSP on another or MIUI or GSI etc. How awesome is that? It also gives You as secure virtual mSD Card that will never get encrypted so Your files will be always safe!
How is this Tool different compared to Zackptg5 version for OP7 Pro? Well.. let's be honest.. he's a great Developer and his skills in making scripts and other stuff are a lot better than mine so his version of Dual Boot is definitely better but since he doesn't have OnePlus6 and 7 Pro received great feedback + people wanted me to resurrect DualSix which I made 2 months ago, I decided to finish the project and release it. It will most likely be the last "big project" for this device before 8 Pro.
Now short Q&A:
Q: Can I use on mido, raphael, x00td, vince etc?
A: No! Only use it on OnePlus6 and 6T.
Q: Can I use it with EPR?
A: No. You can't use them on top of each other.
Q: What ROMs does it support?
A: Ports (soon), AOSP ROMs and GSIs.
Known Issues
Storage Settings in ROMs might report incorrect storage size
Currently only 128GB is supported
Shared Storage is sadly only accessible by using any root explorer (/data/media/0/SharedStorage)
This directory is accessible in TWRP as Micro SD Card (keep important files there)
How to Use:
MAKE SURE TO BACKUP EFS, DATA AND PERSIST (if possible) BEFORE USING IT!
MAKE SURE YOU HAVE LATEST OPEN BETA / OOS STABLE IN BOTH SLOTS!
Also make sure You're not currently using EPR!
It is recommended for You to keep most important files in Shared Storage / MicroSD Card.
It won't get corrupted if something goes wrong.
If You mess up and end up without DualSix TWRP. You can also use Emergency DualSix TWRP from Emergency files!
1. Run RUN_BEFORE_DUALSIX.bat/sh in Fastboot Menu.
2. Boot into TWRP of Your choice.
3. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6.zip
4. Flash Dual Six for Your storage
5. Reboot into recovery
6. Format all new partitions (Data A, Data B, Shared Storage/MicroSD Card)
7. Reboot recovery again, confirm that new TWRP log shows no red error messages
8. Now follow ROM specific guide below
-------- Ports ---------
Because ports are slightly more difficult to patch
Future ports will come with separate DualSix flasher.
REMEMBER. FORCE WIPE ONLY WIPES CURRENT SLOT.
YOUR SECONDARY ROM WILL BE FINE.
--- Once that happens follow ---
1. From fastboot, run flasher.
2. Most flashers auto reboot, if that happens, just boot into TWRP (even if You see boot animation))
3. Now when You're in TWRP, copy Dual Six ROM Patcher to Your MicroSD Card Storage
4. Flash Dual Six ROM Patcher
5. Done! Now reboot into the ROM and once it boots, You can root.
------- AOSP ROMs / GSIs --------
1. Flash AOSP_ROM_NAME.zip
2. Flash dual-six-twrp-3.3.1-x_blu_spark_v9.109_op6/op6T.zip
3. Reboot Recovery
4. Flash Dual Six ROM Patcher
5. Flash GApps (if needed)
6. Reboot and enjoy!
Note: if AOSP ROM / GSI stays on boot animation for longer than 10 minutes, flash a permissiver.zip.
You should apply same guide for both slots.
Download:
DualSix v1.1 - Mar25
If You have any other problems, just ask here on XDA or for the fastest support PM me or ask someone in my group on Telegram
Join my group!
If You want to support this and other projects, buy me a coffee!
https://www.paypal.me/protodevnano
Credits
MounirHero - for 6T support
eng.stk - for his amazing TWRP
CosmicDan - for his sgdisk guide that helped me with EPR and DualSix
My group for motivating me to resurrect this project!
OnePlus for creating this amazing phone!
XDA:DevDB Information
DualSix - DUAL BOOT for OnePlus6 & 6T, Tool/Utility for the OnePlus 6
Contributors
ProtoDeVNan0, MounirHero
Source Code: https://github.com/engstk/android_device_oneplus_enchilada
Version Information
Status: Stable
Created 2020-03-24
Last Updated 2020-03-24
What a wonderful thing....!
Thanks Jay! Can't wait to try this out!
Awesome!! Well Done Bro... [emoji16]
Sent from my RMX1971 using Tapatalk
Great job Jay, hoping 64gb comes soon! One of your ports on one slot and GSI on the other would be amazing!
DualSix TWRP not flashing or booting, OnePlus 6T
I cannot get the dualsix twrp to flash to my device. In twrp it says device not compatible and aborts the installation. I also cannot boot the emergency twrp image from the emergency files folder in fastboot mode, when I try it boots back to the rom. I have a OnePlus 6T 128GB model. My guess is that the twrp is only for the OnePlus 6 and that's why it's aborting? But the OP mentions it working on both the 6 and the 6T. I have tried with and without running the "RUN_BEFORE_DUALSIX_WINDOWS.bat" beforehand. Not sure what to try now.
edit: nevermind, the link hadn't updated yet when I first downloaded it earlier so I did have the twrp that was only for OnePlus 6, sorry about that
Nice, will try it when I have time
This is what I thought/hoped the stupid A/B partition nonsense was going to be.
NICE!!
Will this wipes all. Internal storage
Can't wait to try this. Awesome work
Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.
That's terrific ! This sounds promising !
I'll try to get OP6 OOS latest OB and Havoc OS 3.3 alongside
Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Edit: Posted a message in my channel where I test ROMs and confirm if they work or not
ProtoDeVNan0 said:
Just updated DualSix to 1.1 which includes external_sd fix which for some reason was missing from previous zip.
Thanks to Lord_Vicky & MounirHero for letting me know.
Click to expand...
Click to collapse
I need access to your g drive to download
david72262 said:
I need access to your g drive to download
Click to expand...
Click to collapse
Oops. Never happened to me before. But fixed it. Enabled file access for everyone. Not sure why mobile uploads have different sharing options
Awesome man. Great going.
What the f*, I though nobody was gonna attempt to do this !
I'll have to try that
oscarmaldonado said:
Hello everyone, question, just in case if I want to revert back to stock a and b is it just MSM tool? Thanks Dev.
Click to expand...
Click to collapse
I was wondering the same thing
Hi...Thank you very much for this mod.
I am willing to do this but i have a few questions regarding it
1st: after we flash this mod...can we go back to the original partition table and if so...could you explain what files to use and in which order.
2nd: if i want to flash OOS on slot a then my current boot slot would have to be active slot b because roms flash to opposite slots right?
3rd: if i have OOS on slot a and a custom rom on slot b...when i have an update for OOS i must be on active slot b and flash the whole OOS full rom zip and flash all the other files like magisk and recovery and patchers or is it a different way?
4th: can we set a password for slot b's rom or will it brick the device like the 7/7Pro' guide section?
5th: does the shared storage have a fixed size or is it dynamic...and if so, if we put photos and media there will the normal apps like gallery and music players be able to access them at all?!
6th: do we have to stay unencrypted?
7th: if we want to flash magisk to slot a....does our active slot has to be slot a or slot b?
8th: if i want to change rom on slot b...then what do i have to wipe to be able to clean install the rom i want?
i know i asked a lot of questions and some may be stupid but i would really like to try this with all the knowledge beforehand so i dont get myself into a perma-brick like the guys over at 7/7Pro's section
Thanks again for this mod and i hope you reply soon .
joepas said:
I was wondering the same thing
Click to expand...
Click to collapse
I tried, I couldn't get it to boot so I was able to revert it back by running DualSix Remover 128GB.zip in the same folder, reformatted everything and reinstalled OOS.
need help
can anybody tell me for certain how bad i just wrecked my phone. So I was on step 4. Flash Dual Six for Your storage, and after it flashed i hit the restart button on accident. My phone was stuck in the op6 3 dot bootloop. Then i might have put the nail in the coffin by fastboot flashing the images out of the 9.0.9-OnePlus6Oxygen_22_OTA_034_all_1909112343_dd26-FASTBOOT.zip. I’m pretty sure im autistic can anyone help me fix my phone?
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
NOSS8 said:
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
stercorarius said:
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
Click to expand...
Click to collapse
Not sure that the Twrp for this device is 100% functional, especially since this device has A/B partitions and A13 has write restrictions.
You can try a Xiaomi Eu rom and flash the rom in fastboot mode with the first install.bat script included in the extracted folder.(xiaomi.eu_multi_MI11LE_XM11Lite5GNE_V14.0.6.0.TKOCNXM_v14-1)
Xiaomi.eu Multilang MIUI ROMs - Browse /xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv14 at SourceForge.net
OFFICIAL mirror of MIUI Multilang ROM by https://xiaomi.eu/
sourceforge.net
Format data, erase your data and create a new partition if necessary (Twrp format data type yes, Miflash and Xiaomi Eu rom do it too).
The recovery roms do not contain all the system imgs unlike the Fastboot rom and Xiaomi Eu rom.
Could also be a HW problem.
stercorarius said:
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Click to expand...
Click to collapse
Which twrp version were you using and which version of MIUI did you try to flash when you hard bricked?
There's no system partition nowadays, it is now included in the "super" partition (system, system_ext, product and vendor) and developer removed the option to wipe it because you are not intended to wipe it.
My recomendation is to flash any fastboot rom, I've flashed 7 roms with fastboot and it always worked flawlessly.
Hi, I'm the person that has been helping.
Of course we flashed miui (in fastboot). Global and chinese. We haven't tried eu yet.
I think I've found the source of the problem, but I'm not sure if solving it will fix the bootloop. A partition that's called switch is corruped. It reports as 16EiB (yes that is correct, 16 exabytes, 18446744073709551607 sectors, reported by gptfdisk, full report). It could just be a program issue. The switch partition in located in /dev/block/sda1 and /dev/block/dm-5. I also found that a dummy.img file is being flashed to that partition.
I also got this error from trying to open the switch partition from a newer version of gptfdisk.
I'm not sure if that's the reason for the bootloop, but I think it can be.
These reports have been from /dev/block/sda1. From /dev/block/dm-5 it's like this.
If someone wants to look at the tools I found, they're here.
If someone has any suggestions or possible answers for us, please reply.
What is the error generated by Mi Flash?
Miflash log folder
NOSS8 said:
What is the error generated by Mi Flash?
Miflash log folder
Click to expand...
Click to collapse
Hi, there was is no error in miflash.
You can take a look here if you want to.
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
NOSS8 said:
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
Click to expand...
Click to collapse
Can we somehow repair the sector?
Sucharek 233 said:
Can we somehow repair the sector?
Click to expand...
Click to collapse
I saw that you changed a transistor, maybe there is a problem elsewhere that is causing this to happen.
Changing the motherboard with the flex cable might be preferable.
I doubt that what you are trying to do is possible due to the complexity of the current system and especially for boot sectors which are not likely to be accessible with current tools.
Especially since the problem has not been identified with precision.
A little update:
We tried flashing EU rom and the oldest rom, but still no luck. Phone is still bootlooping and switch partition is still broken.