Related
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Thanks for the thought but you don't need to credit me here
You should mention that running "fastboot format userdata" wipes the entire phone including pics/vids, texts, etc. Someone will run this command ignorantly.
Sent from my Nexus 5X using Tapatalk
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
chucky8 said:
I recently installed nougat myself on my nexus5x. Couldn't install twrp. Thanks for the explanation and tutorial.
I have 2 questions.
Why do I need a modified boot.img?
And in a future update to final nougat, how do I proceed then with a modified boot.img and custom recovery?
Click to expand...
Click to collapse
First off. TWRP couldn't decrypt N right now, so to overcome this, we decrypt the device.
Forced encryption is implemented through the kernel. The modified boot image disables that. So now upon booting, your device shall not be encrypted.
As for the future, you will have to do the same and flash the corresponding modified boot.img, when it comes out.
How do i know if my nexus is decrypted or not ?
ariefabuzaky said:
How do i know if my nexus is decrypted or not ?
Click to expand...
Click to collapse
If you don't know, then you are Encrypted. Look under Settings/Security/Encryption. It will either read "Encrypted" which is obvious or "Encrypt Phone" which means you are decrypted.
Sent from my Nexus 5X using Tapatalk
You don't have to decrypt. You can just push things you wanna flash to /tmp instead of decrypting data
farshad525hou said:
You don't have to decrypt. You can just push things you wanna flash to /to instead of decrypting data
Click to expand...
Click to collapse
Exactly. But then again, it is all about personal preference. I personally don't like connecting any external device to flash anything. Too slow to first download the files, then push 'em up to the HDD or Pen drive and then connecting it to the device to flash. I believe there are more users here, just like me.
For those who would need to decrypt, this is aptly the right process to begin with. Appreciations to @hackarchive for making this thread. Over at the three N based threads, I see several people asking about the decryption process, and this thread would definitely help the newcomers to get their foot in the right direction.
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
lbcary said:
Just so that I'm clear on this. Is this the correct way/order
1. fastboot flash the boot.img
2. fastboot format userdata
3. fastboot format cache
4. flash twrp
Just want to be sure before I format userdata. Thanks
Click to expand...
Click to collapse
NM, read that as flash userdata ...
Sent from my Nexus 6P using Tapatalk
I just did this and it worked but now I rebooted to TWRP to flash suhide, all I did was to swipe right on the warning twrp gives at the start and flash suhide, now I'm stuck at the splash screen again
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Sent from my ONEPLUS A3003 using Tapatalk
shamps said:
What if i decrypt my phone prior to unlock boot loader? Or it doesn't work that way?
Click to expand...
Click to collapse
Doesn't work that way.
The Fix is not needed anymore, newest TWRP is able to decrypt your phones storage. Only use newest twrp.
hackarchive said:
I was recently in a hot bowl of $h!t when I unlocked my bootloader for my new 6P already on 7.0 N90G latest build. Little did I know that it would be this hard to get twrp as it was relatively painless on my previous device prior to N. Anyways I'm making these for those who get stuck on the Twrp splash screen on any Android N build.
Explanation:
Your device isn't decrypted. You need to decrypt it before flashing TWRP.
Process:
Get a modified boot.img for the build you use. Flash it in fastboot. They can be found here.
Decrypt you device. Do this by rebooting into bootloader. The on your PC in a fastboot command use the commands below one after the other
"["fastboot format userdata" wipes the entire phone including pics/vids, texts, etc.]" @SlimSnoopOS
Code:
fastboot format userdata
Code:
fastboot format cache
Now install twrp using any method you know. Get the imgs here.
Yeah I lied it wasn't hard but just tricky. Enjoy!
Credit:
@Heisenberg
@Tigerstown
Click to expand...
Click to collapse
Dude you saved my ass. My phone would not show correct battery % reading and I decided to drain it completely. Then my phone got stuck in bootloop and recovery stuck on splash screen. I am really lucky I found out your post.
Tysm.
Stock kernels with the "forceencrypt" flag changed to "encryptable".
These are "IMG" files that need to be flashed with fastboot.
(Oct) N6F27M-noencrypt-boot.img - https://mega.nz/#!e4AmQJTa!-b9VEDCUHMa2YedScgHpSpStmKfhVWQMFWQf93L0OCU
(Oct) NGI77B-noencrypt-boot.img - https://mega.nz/#!XsBR0QBb!nkNQibCAT-IMpGH3pPVKLmHsGzE90JQfBcDzkWWwHEM
(Sept) NGI55D-noencrypt-boot.img - https://mega.nz/#!6sYSUbTb!dT-pBFhY4iJuHcqGWnRZiFvnUHLxVlNxrDDfgl0L_9w
(Aug) N6F27I-noencrypt-boot.img - https://mega.nz/#!atxQSZYK!y4H4uFt8pNW0szhUyWrp_QinytKIE3WhszAQMNJ4rO0
(Aug) N8I11B-noencrypt-boot.img - https://mega.nz/#!voxiWQqY!DtV5VWhRRLH3cvpxL37QJDFGMUjZU9uubBP8NuADG0k
Hi, and which one is to use? Are these carrier specific versions?
day242 said:
Hi, and which one is to use? Are these carrier specific versions?
Click to expand...
Click to collapse
Sounds like the N8I11B build has some Verizon specific code. After reviewing, it appears they devs used the same kernel in both builds, so it should not matter which is flashed.
Lose data?
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
TheTomahawk said:
Can these be flashed without losing data?
My Nexus 6 is currently not encrypted and I'd like to keep it that way, but don't want to have to reinstall all my apps and files. Again.
Thanks.
Click to expand...
Click to collapse
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release and maintain the exisiting data)
Re: lose data
jbaumert said:
You can update your phone and stay un-encrypted by flashing the latest "system.img", "cache.img", and the appropriate "noencrypt-boot.img" from the OP. (This is how I update each release any maintain the exisiting data)
Click to expand...
Click to collapse
Cool. Em, could you provide instructions, please?
Tnx
TheTomahawk said:
Cool. Em, could you provide instructions, please?
Tnx
Click to expand...
Click to collapse
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Much obliged.
im assuming one of these brings back ota? probably N6F27I
guessing one is official ota from 7.0 to 7.1.1
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
dudikaz said:
hello. can anyone please explain to me how do i get rid of encryption if i'm on lineage os? i am trying for hours now but every time my phone boots it is still encrypted. what i'm doing is i flash this modified boot.img through fastboot, then format userdata through fastboot, then go into recovery and wipe everything possible and then i flash latest los build from usb-otg. reboot and it's still encrypted :|
Click to expand...
Click to collapse
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
jbaumert said:
After flashing LOS and before booting the first time is when you need to flash a non-encrypted kernel. Flashing the boot.img before isn't doing any good as it's overwritten by the LOS install....
Click to expand...
Click to collapse
if i flash it after los it gets stuck on google logo and doesn't boot at all :/
---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------
ok so now i've went back to stock N8I11B which is force encrypted. could you tell me exactly what steps should i take to make it not encrypted please? also what about the franco kernel does it get rid of encryption as well maybe?
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
jbaumert said:
If your flashing stock via fastboot, then you just need to replace the boot.img with the non-encrypted. That said, you will need to erase "userdata" also and start fresh. (Once user data is encrypted, it can't be "un-done" it's a start from scratch)
As for LOS, I've never used it with the stock kernel, but it sounds like its not compatible. Franco should work fine and is also not force-encrypt.
Click to expand...
Click to collapse
it's really confusing as this is what it says in the official los thread here on xda - "Current lineage 14.1 shamu nightlies are based on the N8I11B August 2017 update from google. So you should be using the radio and bootloader img from that update. " also how do i erase this userdata properly? "fastboot format userdata"? i think last time i did it my device didn't boot at all afterwards. going to try it again now.
Added September 2017 "no encrypt" boot.img to OP
Added October 2017 "no encrypt" boot.img to OP
thumbs up !!!
i was looking all over for the latest img. really grateful for your work. thanks a lot
Thank you very much
jbaumert said:
Boot the phone to the bootloader and run the following commands (after extracting the various files from the downloaded image)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot flash system system.img
fastboot flash boot noencrypt-boot.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Jeffro64 said:
Would we want to change the name of noencrypt-boot.img to boot.img before flashing or leave as is? Also, can we make a backup in TWRP of our userdata and just restore after flashing as long as it's before booting the phone?
Click to expand...
Click to collapse
You can leave the name of the file (unless you just want to type in a short command with fastboot). As for the backup of "userdata", if you are updating the phone from one stock version to another and following the instructions you quoted, there is no need to backup. Coming from another ROM you would want to wipe and then yes, a backup is a good idea (needed).
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.
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
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