This is a beta project, you and you alone assume all responsibilities of what happens to your tablet.
This thread is for Dell Venue 8 3830 tablets running 4.4.2 android,
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is now flashable via fastboot,
CWM recovery
http://www.mediafire.com/download/29v8t83u3g4c2kx/4.4_recovery.img
to install
fastboot flash recovery 4.4_recovery.img
Credits
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
If I missed anyone on credits let me know, I will add them.
@ Everyone
Everyone is free to use my recovery in their projects under two conditions.
If you can't abide by these conditions don't use my recovery in your project.
1. Give me credit for the recovery in your thread and link back to my recovery thread,
2. You can not sell my recovery or your project if it contains my recovery is must be free to all users.
You can accept donations, charge for one on one help but not charge for your project if it contains my recovery.
I made some changes to mounts will upload later, as well as changed back ground, also put in zip file a step closer to being final.
I changed instructions in first post slightly, some people where having problems with adb shell commands. So instead of adb shell each command just adb shell then run commands.
Backup on this recovery isn't going to work as expected due to recovery wanting to backup data/media/0. Doesn't matter I use command line anyway, faster and straight to the point for backing up and restore.
Couple of queries:
1) Do i have to use SDC myKIT to get root & flash unlocked_firmware or just the steps in the post you linked
2) Can you tell more about- CWM recovery is ram mode, as i get it once we have a working version we will have a update which flases it permanently
Waiting for the updated zip
vampirefo said:
I made some changes to mounts will upload later, as well as changed back ground, also put in zip file a step closer to being final.
I changed instructions in first post slightly, some people where having problems with adb shell commands. So instead of adb shell each command just adb shell then run commands.
Backup on this recovery isn't going to work as expected due to recovery wanting to backup data/media/0. Doesn't matter I use command line anyway, faster and straight to the point for backing up and restore.
Click to expand...
Click to collapse
haruitk said:
Couple of queries:
1) Do i have to use SDC myKIT to get root & flash unlocked_firmware or just the steps in the post you linked
2) Can you tell more about- CWM recovery is ram mode, as i get it once we have a working version we will have a update which flases it permanently
Waiting for the updated zip
Click to expand...
Click to collapse
You have to be rooted and you have to install the unlocked firmware, to be able to flash unsigned recovery and boot images.
The unsigned recovery image allows root via adb which is required for CWM.
Running CWM from ram is the same as running from installed, recovery will work just the same.
The next stage is to get the recovery binary from either dell venue 8 3840 or from dell venue 8 3830 dev version.
These recovery.img are packed in a way I can't unpack, So I asked SDC if he knows how to unpack them.
sent from my kingSing T1 via taptalk
Recovery has been updated, and is now flash able via fastboot, see OP for recovery and flash method.
vampirefo said:
Recovery has been updated, and is now flash able via fastboot, see OP for recovery and flash method.
Click to expand...
Click to collapse
so this version is permanent and will remain after a reboot?
joanthanmajh said:
so this version is permanent and will remain after a reboot?
Click to expand...
Click to collapse
Yes any recovery flashed via fastboot remains after reboot.
The latest recovery is faster, more stable and correctly backs up to micro sdcard, can flash zip files, and boot.img in zip file.
Which is needed for dual boot, next step is setting up dual boot.
Hopefully be able to run 4.4.2 from phone and 4.3 from sdcard.
sent from my kingSing T1 via taptalk
Now have dual boot setup running just fine Kitkat on tablet, 4.3 running from sdcard, 4.3 downloads kitkat update as soon as it connects to internet. just don't install update, as it would install to tablet not sdcard.
Below shows 4.3 mounting sdcard instead of tablet.
Code:
[email protected]:/ # busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 989.4M 64.0K 989.3M 0% /dev
tmpfs 989.4M 0 989.4M 0% /mnt/secure
tmpfs 989.4M 4.0K 989.4M 0% /mnt/asec
tmpfs 989.4M 0 989.4M 0% /mnt/obb
/dev/block/mmcblk0p3 126.0M 4.0M 121.9M 3% /factory
/dev/block/mmcblk1p2 1007.9M 716.8M 291.1M 71% /system
/dev/block/mmcblk0p6 755.9M 353.1M 402.8M 47% /cache
/dev/block/mmcblk0p5 126.0M 4.1M 121.9M 3% /config
/dev/block/mmcblk1p3 3.0G 716.5M 2.3G 24% /data
/dev/block/mmcblk0p7 23.6M 5.9M 17.7M 25% /logs
/dev/fuse 3.0G 716.5M 2.3G 24% /mnt/shell/emulated
/dev/block/vold/179:51
10.8G 6.4G 4.5G 59% /storage/sdcard_ext
[email protected]:/ #
I unpacked the 4.3 image social-design-concepts uploaded, created a zip file install, to install to my sdcard, modified the boot.img, after boot manually rooted, as boot.img is unsecure.
as always more testing, lol. dell venue 8 can dual boot 4.3 and 4.4.2 without any problems, from what I can see.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you make a flashable 4.4.2 rom? Would like to flash stock 4.4.2 rom through recovery if you have one.
tomtom1265 said:
Can you make a flashable 4.4.2 rom? Would like to flash stock 4.4.2 rom through recovery if you have one.
Click to expand...
Click to collapse
Yes, I should be able to, I made one for 4.3, so I could install 4.3 to sdcard.
I may look into twrp recovery also, right now I want to roll back the kernel in the recovery to 4.3
I believe the 4.3 kernel will offer more flexibility, 4.4.2 kernel is 3.10 not ideal for android.
sent from my kingSing T1 via taptalk
How to flash the unlocked_firmware? I am confused with SDC's steps in the link you gave...can you clarify them. Does that not happen when you use his myKIT_BATCH with ASSET zip included ( i have already unlocked using it)
vampirefo said:
Yes, I should be able to, I made one for 4.3, so I could install 4.3 to sdcard.
I may look into twrp recovery also, right now I want to roll back the kernel in the recovery to 4.3
I believe the 4.3 kernel will offer more flexibility, 4.4.2 kernel is 3.10 not ideal for android.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
haruitk said:
How to flash the unlocked_firmware? I am confused with SDC's steps in the link you gave...can you clarify them. Does that not happen when you use his myKIT_BATCH with ASSET zip included ( i have already unlocked using it)
Click to expand...
Click to collapse
If you can flash recovery and boot don't worry about flashing unlock firmware.
I was referring to below.
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin (from v8 dev-edition)
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin (from v8 dev-edition)
fastboot reboot-bootloader
I manually rooted my tablet as I was more interested in the rooting process than the actual root itself.
I can't say for certain if you have already unlocked your bootloader or not, try and flash recovery if it flashes you are good to go, if not flash unlocking firmware.
sent from my kingSing T1 via taptalk
Got it, I am able to flash CWM now using the followin steps(after rooting with SDC's myKit):
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin (from v8 dev-edition)
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin (from v8 dev-edition)
fastboot flash recovery cwm_recovery.img
But everytime i reboot CWM goes away and i have to repeat steps above...Thats is the expected behaviour because we want to work in RAM mode, right?
vampirefo said:
If you can flash recovery and boot don't worry about flashing unlock firmware.
I was referring to below.
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin (from v8 dev-edition)
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin (from v8 dev-edition)
fastboot reboot-bootloader
I manually rooted my tablet as I was more interested in the rooting process than the actual root itself.
I can't say for certain if you have already unlocked your bootloader or not, try and flash recovery if it flashes you are good to go, if not flash unlocking firmware.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
haruitk said:
Got it, I am able to flash CWM now using the followin steps(after rooting with SDC's myKit):
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin (from v8 dev-edition)
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin (from v8 dev-edition)
fastboot flash recovery cwm_recovery.img
But everytime i reboot CWM goes away and i have to repeat steps above...Thats is the expected behaviour because we want to work in RAM mode, right?
Click to expand...
Click to collapse
.28 recovery is used in ram .37 recovery is permanent, if you flashed the latest recovery, it should remain.
What is the number on the recovery that you are using?
Sent from my Venue 8 3830 using Tapatalk
I am using the one in this link https://docs.google.com/file/d/0B_6NtXCtTLkHSEdrVk1qVTNQeTA/edit , Its says v 6.0.3.7
If i reboot i see an android lying down with excalmation mark image & 'no commad' message
I reflash the recovery it works again
vampirefo said:
.28 recovery is used in ram .37 recovery is permanent, if you flashed the latest recovery, it should remain.
What is the number on the recovery that you are using?
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
That's not how this recovery works, two things come to mind.
1. You may have stock recovery patch in system, if so you would need to either rename or delete it.
2.Your fastboot was patched during rooting, if so you would need to reflash the one from dev edition and not patch it.
When I get off work, I will be able to tell you files exact name, I dont have tablet with me.
sent from my kingSing T1 via taptalk
The asset kit supplied by SDC for venue8 has this file fastboot-jb4.3v1.25.img, may be thats causing 2. Can you share where do i look for recovery patch and dev fastboot image. Plz take ur time
PS: May be i should manually root by ur steps, can you share steps/files...I am new to this so understanding how it all works, still reading...
vampirefo said:
That's not how this recovery works, two things come to mind.
1. You may have stock recovery patch in system, if so you would need to either rename or delete it.
2.Your fastboot was patched during rooting, if so you would need to reflash the one from dev edition and not patch it.
When I get off work, I will be able to tell you files exact name, I dont have tablet with me.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
haruitk said:
The asset kit supplied by SDC for venue8 has this file fastboot-jb4.3v1.25.img, may be thats causing 2. Can you share where do i look for recovery patch and dev fastboot image. Plz take ur time
PS: May be i should manually root by ur steps, can you share steps/files...I am new to this so understanding how it all works, still reading...
Click to expand...
Click to collapse
The recovery patch is called recovery-from-boot.p it's located in system, either delete it or rename to something like, recovery-from-boot.p.bak.
flash fastboot-jb4.3v1.25.img then reboot into fastboot then flash cwm recovery, and it should remain from now on.
rename or delete recovery-from-boot.p
adb reboot bootloader
fastboot flash fastboot fastboot-jb4.3v1.25.img
reboot
adb reboot bootloader
fastboot flash recovery V8_CWM.img
reboot recovery
That worked thanks!
vampirefo said:
The recovery patch is called recovery-from-boot.p it's located in system, either delete it or rename to something like, recovery-from-boot.p.bak.
flash fastboot-jb4.3v1.25.img then reboot into fastboot then flash cwm recovery, and it should remain from now on.
rename or delete recovery-from-boot.p
adb reboot bootloader
fastboot flash fastboot fastboot-jb4.3v1.25.img
reboot
adb reboot bootloader
fastboot flash recovery V8_CWM.img
reboot recovery
Click to expand...
Click to collapse
Related
My phone is rooted with the help of hasoons2000 toolkit, and it was done succesfully, but this morning, when i tried to flash a rom (cm 10.1) its now stuck on "initiating swagger" and i simply cant get past that
Need some help, ive rooted the right version of cwm recovery, cleared my download cache before the flash, and backed up my previously rom (stock)
What do i do!!?
Eddie5850 said:
My phone is rooted with the help of hasoons2000 toolkit, and it was done succesfully, but this morning, when i tried to flash a rom (cm 10.1) its now stuck on "initiating swagger" and i simply cant get past that
Need some help, ive rooted the right version of cwm recovery, cleared my download cache before the flash, and backed up my previously rom (stock)
What do i do!!?
Click to expand...
Click to collapse
Did you flash the boot.img?
gattzzz said:
Did you flash the boot.img?
Click to expand...
Click to collapse
No, i flashed the zip
I have acces to the bootloader menu now by the way
I'm pretty sure i need a RUU for my device now, but I don't know how to do that at the moment.
You have to go back to Fastboot, get the boot img, place it in your fastbood folder and navigate to ist.
then do the following
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
Then Reboot the device and it should be Start.
Cold Ice said:
You have to go back to Fastboot, get the boot img, place it in your fastbood folder and navigate to ist.
then do the following
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
Then Reboot the device and it should be Start.
Click to expand...
Click to collapse
How do i access the boot.img, when the file is in a zip? when i press it, it starts the rom, and gets stuck on "initiating swagger"
1. Download the ROM on to your PC.
2. Transfer a copy of the ROM Zip file to the phone.
3. On the PC, extract the ROM Zip file.
4. Open the extracted folder.
5. You will find the boot.IMG in the extracted folder. Using a toolkit or a command line, write the boot image to the phone while it is in bootloader mode.
6. Flash the ROM.
7. Flash any additional packages.
8. Reboot.
Edit: For adb sideload:
Follow steps 1, 3, 4, and 5, then sideload, then reboot
Sent from my One X+ using xda premium
Eddie5850 said:
How do i access the boot.img, when the file is in a zip? when i press it, it starts the rom, and gets stuck on "initiating swagger"
Click to expand...
Click to collapse
Open the .zip with 7zip or winrar and extract the boot.img or look in the rom thread if there is a downloadable boot.img, there's also a boot.img flasher around here in a toolkit. Don't know which one it is, didn't rooted/Unlocked yet.
Which ROM did you download?
The boot.img is either pointed out in the first post of the Custom ROM or it is in the download .zip
You need to copy the boot.img you find in the ADB/fastboot folder, then boot the X+ into the bootloader, select the fastboot option with the vol+/- and then connect the X+ with your computer.
I am not familiar with the all-in-one-toolkit but if I remember correctly you can flash it within the program.
The Insert Coin ROM and others have a kernel flasher. But I never used one of those either.
Look around a bit. Once the appropriate boot.img of the ROM you want has been flashed the ROMM will boot up.
sarcasticphoenix said:
1. Download the ROM on to your PC.
2. Transfer a copy of the ROM Zip file to the phone.
3. On the PC, extract the ROM Zip file.
4. Open the extracted folder.
5. You will find the boot.IMG in the extracted folder. Using a toolkit or a command line, write the boot image to the phone while it is in bootloader mode.
6. Flash the ROM.
7. Flash any additional packages.
8. Reboot.
Edit: For adb sideload:
Follow steps 1, 3, 4, and 5, then sideload, then reboot
Sent from my One X+ using xda premium
Click to expand...
Click to collapse
All right, since I have no access to the usb debugging, i tried to sideload the rom (Cm 10.1 4.2.2), but when i use the toolkit with the script cmd
It says this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried it again, and it says this:
Sorry if i am a complete noob here
Eddie5850 said:
All right, since I have no access to the usb debugging, i tried to sideload the rom (Cm 10.1 4.2.2), but when i use the toolkit with the script cmd
It says this:
Tried it again, and it says this:
Sorry if i am a complete noob here
Click to expand...
Click to collapse
adb kill server
fastboot flash boot boot.img
done. Quite honestly you should read up before flashing rom's ALL the info is in this forum.
Sorry if I'm thread jacking, but is there a way to flash a kernel from in the phone itself? my PC took a dump, it'll be a few weeks till i can afford to replace it.
Great news everyone!
I saved my phone, and its now working like stock normal
The problem was that i flashed an entire zip file instead of a boot.img file, causing my phone to bootloop, after countless tries to fix this, I decided to unroot the phone with fastboot, recovery and a RUU file.
My phone is now working, thanks for helping!
Until we get S-OFF, we can't flash kernels from the phone itself.
Sent from my One X+ using xda premium
So, sorry if i'm thread bumping, but if I want to give it a try again at flashing a rom, and try avoiding what happen last time
Are these the following step correct?
Do a backup of current rom in cwm recovery
Wipe data/factory reset 3 times in cwm recovery
Wipe cache partition in cwm recovery
Wipe dalvik cache cwm recovery
Flash the zip containing the cm10.1 zip
And can I do all this without the need of installing rom manager?
Don't forget that you need to flash the kernel separately. Because we don't have S-OFF on our device, we have to flash the kernel from a PC.
1. Extract boot.img (this is the kernel) from the ROM zip file
2. Open a cmd prompt and cd to the directory containing the extracted boot.img
3. Connect your device and reboot it to the bootloader with the command:
adb reboot bootloader
4. Flash the kernel with the commands:
fastboot flash boot boot.img
fastboot erase cache
5. Reboot your device with:
fastboot reboot
You can do these steps before or after flashing the ROM but remember that you should have the android SDK platform-tools folder in your PATH before it'll work (assuming you use windows).
Sent from my cellular telephone using xda premium
o_O said:
Don't forget that you need to flash the kernel separately. Because we don't have S-OFF on our device, we have to flash the kernel from a PC.
1. Extract boot.img (this is the kernel) from the ROM zip file
2. Open a cmd prompt and cd to the directory containing the extracted boot.img
3. Connect your device and reboot it to the bootloader with the command:
adb reboot bootloader
4. Flash the kernel with the commands:
fastboot flash boot boot.img
fastboot erase cache
5. Reboot your device with:
fastboot reboot
You can do these steps before or after flashing the ROM but remember that you should have the android SDK platform-tools folder in your PATH before it'll work (assuming you use windows).
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
Can't I just use the toolkit for my hox+? Hasoon2000 says you can just flash a kernel? I could be wrong though.
I believe you can, and that the way I described above is actually the way Hassoon's toolkit does the job. Just make sure the boot image is named correctly for the toolkit to pick it up, and make sure you put it in the correct folder (from memory, it's the "kernels" folder).
I use Linux, so Windows users feel free to correct me if I made any mistakes.
Sent from my cellular telephone using xda premium
Dell has updated their open source site with the developer files for the Lollipop update for the Venue 8 7840:
http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
This includes the kernel source, a guide Doc, and a "blankphone" image which will re-partition the device and leave it in the fastboot interface OS and wait for a system image to be flashed. It does not erase or provision a system image or boot image. The documentation mentions a separate "fastboot" image paired with the "blankphone" image, and traditionally (based on files posted by other OEMs) the "fastboot" zip is what contains the OS images. So hopefully (maybe?) they will be posting that at some point. We should be able to get images pulled off working devices for people to flash.
This "blankphone" zip should function as an "unbrick" and put a mis-flashed device back into a functioning (flashable) state, but you may end up without an OS. (This is why I called it "partial" unbrick, because you won't have a brick but you won't necessarily have a booting-to-Android device either.)
ALSO A WARNING: This should be all fine and good but proceed with caution.
I have flashed the IFWI-only.xml and successfully booted back to Android.
The zip file can be flashed with Phone Flash Tool Lite, available here from Intel for Windows and Linux.
There is a "Flash file" selector in Phone Flash Tool.
To unbrick and format, use the file: flash-DDO_BB.xml
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To just flash the unlocked bootloader firmware, use the file: flash-IFWI-only.xml
DO NOT use the EraseFactory xml; I'm not certain but I think there are DRM keys in the /factory partition, and you could permanently break things like Netflix if you erase it.
Since mine is currently useless, I may as well try this. Will the image you uploaded here work?
Don't have access to the tablet at the moment but I'll try when I get in (couple of hours).
I know @wirebook tried on the older bootloader and failed but not harm in trying with this new stuff I suppose...
That system.img doesn't flash I think... Though it sounds like it's just an issue of repacking it somehow.
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
wonglynn2004 said:
This is great news!
If bootloader can be unlocked, does it mean someday (if best) it is possible to install windows os on this little pad?
Click to expand...
Click to collapse
Windows is unlikely, as it would require additional drivers and a custom bootloader OS to be created, among other issues. Linux may be possible though.
I've managed to unbrick my device, but I'm honestly not sure how.
So using the intel flash tool, I used the option flash-DDO_BB.xml, understanding that it would wipe the device (erase system, repartion, etc). I then had access to fastboot. From fastboot I attempted to flash the system.img @xBIGREDDx uploaded, obviously that failed with the sparse image header issue.
Next I converted the system.dat.new in the OTA to a system.img, attempted to flash that from fastboot, no go.
I decided it might be a good idea to flash the boot.img from the OTA, so I did that. Ended up on the original Dell/Intel boot animation (progress?). This seemed to infinitely bootloop (however maybe I was just impatient?).
I then booted CWM using the temp. recovery method (T4), wasn't able to do much at all, most directories were empty and nothing was mountable. Rebooted the tablet once more, went to get a drink and it's booted into Lollipop!?
I'm both confused and pleased... Can anyone shed any light?
anggusss said:
I'm both confused and pleased... Can anyone shed any light?
Click to expand...
Click to collapse
Hahaha not sure, maybe the reboot caused it to process the update again? The OTA may have been in the cache still.
Update: I have looked at the xml files and it turns out they are not erasing the boot or system partitions after all. That has been the standard procedure in the past so I didn't think to check. They are, however, wiping the data partition, and they wipe the cache twice. Maybe they've been reading XDA too much?
Ah I see. So if my system was never wiped, I assume flashing the new boot.img from fastboot is what kicked it into life.
I probably should have posted somewhere that I wrote a second query to Dell and heard back from someone in Legal six days ago stating that they were going to go bug the team and get the images posted online. They promised to follow up- never did- but looks like the rest of you were a lot more diligent in checking out the open source repository.
Anyway, the tablet I was working on belonged to a family member now living in a different city. Seems like we've figured out more or less how to unbrick this thing, so that's fantastic! I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
wonglynn2004 said:
For now, I wanna ask how to unroot the device with 5.0.2 if an OTA out there that I'm gonna update but don't wanna brick my device?
Click to expand...
Click to collapse
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
anggusss said:
Wait for someone else to confirm, but I don't think it was the rooting that caused the OTA to fail, it was the developer unlock. I imagine you're safe to OTA with root applied although someone correct me if I'm wrong.
Click to expand...
Click to collapse
Yes, it was the developer unlock firmware that broke the OTA, not rooting. With the new Lollipop boot firmware, I think even if it's the unlocked firmware we should be good moving forward.
If you still want to unroot, there should be a menu option in SuperSU, it's like "cleanup" or something.
wirebook said:
I'm a bit confused as to which guide / instructions I should be passing along to convert the "it's-okay-it-makes-a-pretty-doorstop" back to working condition? Much appreciated!
Click to expand...
Click to collapse
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
xBIGREDDx said:
1) Install Phone Flash Tool Lite from Intel.
2) Download the blankphone zip from Dell's open source site.
3) Load the zip file with Phone Flash Tool and select "Flash file: flash-DDO_BB.xml"
4) Boot the tablet with the Volume Up button held for about 10 seconds. You won't see anything on the display.
5) Connect USB to the computer. Phone Flash Tool should recognize the device and list the "Status:" as "FW_DNX" mode. If not, try powering off the tablet by holding the power button for ~12 seconds, and then try booting again with the Volume Up key held. Eventually you'll get the right mode.
6) Click "Start to flash" and wait.
7) Even after it hits 100% in the Flash Tool, maybe wait another 5 minutes or so, just in case.
If all goes well you'll end up in the fastboot OS. If all goes really well, you'll end up with a functioning Android device.
Click to expand...
Click to collapse
Thank you so much for posting that! I'll attempt to walk my father through the process this weekend.
Stuff wasn't quite working right for me, the screen was turning on randomly, reboots took a ridiculously long time, and a few other things. Decided that it may be better to start with a fresh system partition.
Tried converting both the system.img from @xBIGREDDx and the one from the lollipop OTA to sparse imgs and flashing, however I'm getting
FAILED (remote: flash_cmds error!
When I try to flash system, during the write stage. I'd like to think they're correct sparse images since fastboot reads and sends them to the device.
If I look at the tablet screen during the flash, it complains of an "Unknown chunk type" before failing.
I can get to the default recovery and fastboot, I just don't seem to be able to flash something to my now empty system partition from fastboot...
EDIT: Managed to flash system through the tethered recovery, but I'm still met with a black screen on regular boot.
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
anggusss said:
EDIT2: Fixed, had to push xBIGREDDx's system.img to the device over adb and then dd it to the system partition. The advantage of using that is that it's pre-rooted! I guess we just can't flash system through fastboot.
Click to expand...
Click to collapse
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
wirebook said:
Can you explain how you did this? Through the tethered recovery or through fastboot or....? Trying to walk someone through this via Skype turns out to be a lot harder than I expected...
Click to expand...
Click to collapse
Sorry, I could have been clearer.
The steps I performed:
First, booted to fastboot
Trigger the tethered recovery (T4)
Once in the recovery, I then formatted /system using the graphical menu. (Probably not necessary since we're DDing the img directly?)
I had a microsd card in the device which was EXT4 formatted, so I pushed the system.img to that after mounting it by hand.
Code:
mount -t ext4 /external_sd /dev/block/mmcblk1p1
Then from the PC side
Code:
adb push system /external_sd/system.img
You could probably push to the data partition if you can get it mounted in the event you don't have a microsd.
Once you have the system.img on the device, you can dd it onto the system partition
Make sure /system is unmounted
Code:
umount /system
dd if=/external_sd/system.img of=/dev/block/by-name/system
NOTE: /dev/block/by-name/system may be wrong, I'm going from memory. I'll correct it when I get in from work.
After flashing system, reboot to fastboot again
Code:
adb reboot fastboot
And finally flash the boot.img from the OTA zip I uploaded
Code:
fastboot flash boot boot.img
Perform a normal boot, and it should be working. First boot takes a while, 3-4 minutes.
anggusss said:
Another note, I wasn't able to ever get the tablet booting straight into fastboot mode using power/volume buttons. I had to keep sticking it into DnX mode and then using a cut-down xml config along with the flash tool lite to get it to fastboot.
Click to expand...
Click to collapse
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
xBIGREDDx said:
It's possible your fastboot partition is broken. After using the Flash Tool to get into fastboot, you could try:
fastboot flash fastboot droidboot.img
There is a droidboot.img in the update.zip from the OTA.
Click to expand...
Click to collapse
I did try that quite a few times but no luck. I just seem completely unable to boot straight into fastboot. I either have to reboot to it using ADB or use the flashtool. Not necessarily a problem, just an inconvenience.
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition.
The new Twrp is out now 3.0.0-1 HERE
Let me know if this helps guys and gals.
jerflash said:
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition. This never happened to me before so it must be something in the new bootloader image or boot image that is causing this.
Does anyone else see this? I was going to test downgrading the bootloader later on today to see if the block is gone but it looks like the "default password" for encryption may have changed.
Let me know guys.
Click to expand...
Click to collapse
New TWRP test builds already out there that take care of the issue.
rebretz000 said:
New TWRP test builds already out there that take care of the issue.
Click to expand...
Click to collapse
yes i see that and i am going to flash it now. i had to read through that whole thread though. i will post it above for others.
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Awesome test build! It works like a charm
havanahjoe said:
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Click to expand...
Click to collapse
this happens because you booted into Android before flashing SuperSu or disabling the recovery-from-boot
when you flash the last item, in my case it was vendor.img, i clicked volume down on my phone, and went into recovery. i then selected SuperSu2.68 and flashed that. Then rebooted.
chaco81 said:
this happens because you booted into Android before flashing SuperSu
Click to expand...
Click to collapse
That would explain it. I didn't know SuperSu took care of this. Thank you
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Yes. I use the same version.
allen099 said:
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Click to expand...
Click to collapse
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
mickyw1980 said:
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
This allows you to keep encryption?
jerflash said:
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
floepie said:
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
Click to expand...
Click to collapse
That may be true but if you don't know to do that it will wipe everything. Just always been safer to do it individually.
Sent from my Nexus 6P using Tapatalk
gts24 said:
This allows you to keep encryption?
Click to expand...
Click to collapse
Looks like it does. Is there another way to tell?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6P using Tapatalk
I always flash system, boot, vendor through fastboot. Sometimes I also update the bootloader and the radio if there is a newer version available. All other IMG files are not necessary. It´s true that flashing the stuff one by one gives you more control ( and a dirty flash is also great for lazy guys like me who want to keep all their Apps, settings etc. ).
johnny2678 said:
Looks like it does. Is there another way to tell?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just followed your flow chart , worked here as far as I can tell as well. (proper thanks button clicked )
When I flashed this morning and entered TWRP recovery it must of tripped something as the yellow "cannot check for corruption" warning changed to a red "Your device is corrupt" message. It still only shows for a few seconds before booting like normal. I can't really try anything until I get home, but will flashing the patched TWRP and booting into it be enough to change that back to the old yellow warning? Or do I need to reflash the system/boot packages again?
Hello,
Can somebody explain me how to upgrade to, everytime i try my phone bricks and im not able to boot it back.
This is what i do:
Xperia z2 d6503 eXistenZ 4.7 Marshmallow
i download twrp-3.0.2-0-sirius.img from https://dl.twrp.me/sirius/
i reboot on recovery to install the .img and it only shows (Kernel) to select after flash/reboot /breaks.
So what i do is recover using
fastboot flash boot boot.img
fastboot flash recovery twrp.img ( this is twrp 2.8.7.0)
fastboot reboot
and restore using a backup.
Any ideas?
what am i doing wrong,
how do i install TWRP 3.0.2.0?
newproyect said:
Hello,
Can somebody explain me how to upgrade to, everytime i try my phone bricks and im not able to boot it back.
This is what i do:
Xperia z2 d6503 eXistenZ 4.7 Marshmallow
i download twrp-3.0.2-0-sirius.img from https://dl.twrp.me/sirius/
i reboot on recovery to install the .img and it only shows (Kernel) to select after flash/reboot /breaks.
So what i do is recover using
fastboot flash boot boot.img
fastboot flash recovery twrp.img ( this is twrp 2.8.7.0)
fastboot reboot
and restore using a backup.
Any ideas?
what am i doing wrong,
how do i install TWRP 3.0.2.0?
Click to expand...
Click to collapse
/boot and /recovery are two DIFFERENT partition. So what you did is just flashing the right thing ( TWRP .img ) into the wrong partition.
I am wondering if you know how to play with those fastboot command, why dont you just simply flash the TWRP 302-0 using the fastboot method (?) using the following command:
Code:
fastboot flash recovery twrp-3.0.2-0-sirius.img
iXaidyiu said:
/boot and /recovery are two DIFFERENT partition. So what you did is just flashing the right thing ( TWRP .img ) into the wrong partition.
I am wondering if you know how to play with those fastboot command, why dont you just simply flash the TWRP 302-0 using the fastboot method (?) using the following command:
Code:
fastboot flash recovery twrp-3.0.2-0-sirius.img
Click to expand...
Click to collapse
i know boot and recovery are 2 dferrent things
i tried
Code:
fastboot flash recovery twrp-3.0.2-0-sirius.img
But after restarting my android flash on red and doesnt boot anymore.
i should read first next time:
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Click to expand...
Click to collapse
I did that, still shows 2.8.7.0 installed.....
Well, eXZ 5.1 comes with TWRP installed, so you may consider upgrading to it.
1. Flash a custom kernel out there with TWRP installed using flashtool by androxyde.
2. Flash base rom and update zip.
3. Flash addon ( if any ).
4. Reboot into system.
5. Done.
iXaidyiu said:
Well, eXZ 5.1 comes with TWRP installed, so you may consider upgrading to it.
1. Flash a custom kernel out there with TWRP installed using flashtool by androxyde.
2. Flash base rom and update zip.
3. Flash addon ( if any ).
4. Reboot into system.
5. Done.
Click to expand...
Click to collapse
eXZ 5.1 doesnt allow to set color notification on led
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