If anyone looking for root method, I can inform that magisk pre-patched boot.img works fine.
I just did a bootloader unlock tonight, patched the boot.img, and flashed through fastboot. Once booted I could install magisk from magisk manager.
{
"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"
}
If you want to flash through TWRP instead, have a look at this post by @Bartoshevsky : https://forum.xda-developers.com/showpost.php?p=79358364&postcount=89
I will add pre patched boot.img's here
Can you post a guide or the a link for a magisk pre-patched boot.img ?
Woh, great!
Thanks for trying. For me this will be the best way, without any TWRP. Please, which version did you used: 17.1 (stable) or 17.3??
dare2k said:
Can you post a guide or the a link for a magisk pre-patched boot.img ?
Click to expand...
Click to collapse
I'll try to make a guide during the night, or tomorrow.
Here's a link to the pre-patched boot.img in this post. it's taken from XT1941-4 , buildnr OPKS28.63.18-3.
https://www.androidfilehost.com/?fid=11410963190603856664
Here's a good guide for bootloader unlock: https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
So, short version here:
Unlock bootloader.
Install Magisk manager.
Go to fastboot and flash the patched boot.img
Reboot and open Magisk manager to install Magisk.
Profit!
Sylvia said:
Woh, great!
Thanks for trying. For me this will be the best way, without any TWRP. Please, which version did you used: 17.1 (stable) or 17.3??
Click to expand...
Click to collapse
I used 17.1, as seen in the screen shot
Don't use beta for everyday use unless you have to. It does a lot a verbose logging for debug, so it can even decrease performance of the device.
tys0n said:
I used 17.1, as seen in the screen shot
Don't use beta for everyday use unless you have to. It does a lot a verbose logging for debug, so it can even decrease performance of the device.
Click to expand...
Click to collapse
Sorry, I haven't noticed the screenshot.
And meanwhile I tried it myself. The result was a bootloop (17.3):crying:
Now I have seen your reply, downloaded the pre-patched boot.img and flashed this one. AND: All is fine now, I have a rooted device:good:!!!!!
Thank you so much, you saved my weekend
I presume for Pie we need another patched boot.img
dare2k said:
I presume for Pie we need another patched boot.img
Click to expand...
Click to collapse
Yes, that's right. I got the Pie update yesterday so hopefully I'll try to root it tonight.
tys0n said:
Yes, that's right. I got the Pie update yesterday so hopefully I'll try to root it tonight.
Click to expand...
Click to collapse
Wow nice! That would be awesome!
tys0n said:
Yes, that's right. I got the Pie update yesterday so hopefully I'll try to root it tonight.
Click to expand...
Click to collapse
How did you install the update? OTA doesn't work for me and when I try to unroot it says that there is no original file (of course not, I used your prepatched file)
dare2k said:
Wow nice! That would be awesome!
Click to expand...
Click to collapse
Unfortunatly that didn't work out well for me. I got in to some nasty boot problems and no matter what I did, it was always stuck at bootlogo. I gave it to a friend who's good at fixing these kind of problems but to no avail.
I really don't know what went wrong. Factory reset, re-flash firmware etc..nothing worked. As a last attempt we tried to boot slot _b instead but that was fatal.
It is now recognized as a Qualcomm HS-USB QDLoader 9008 so I can't even reach fastboot. lol Got no hope in finding a blank flash for it neither.
Sylvia said:
How did you install the update? OTA doesn't work for me and when I try to unroot it says that there is no original file (of course not, I used your prepatched file)
Click to expand...
Click to collapse
Sorry for late answer. I unrooted from magisk and flashed back stock boot.img taken from the firmware-package.
Anyway, I got a used one cheap so I still own the device. Won't try to root Pie again though. Not without TWRP.
Now I'm not sure whether I should upgrade or run it on rooted Oreo :/
tys0n said:
Unfortunatly that didn't work out well for me. I got in to some nasty boot problems and no matter what I did, it was always stuck at bootlogo. I gave it to a friend who's good at fixing these kind of problems but to no avail.
I really don't know what went wrong. Factory reset, re-flash firmware etc..nothing worked. As a last attempt we tried to boot slot _b instead but that was fatal.
It is now recognized as a Qualcomm HS-USB QDLoader 9008 so I can't even reach fastboot. lol Got no hope in finding a blank flash for it neither.
Sorry for late answer. I unrooted from magisk and flashed back stock boot.img taken from the firmware-package.
Anyway, I got a used one cheap so I still own the device. Won't try to root Pie again though. Not without TWRP.
Now I'm not sure whether I should upgrade or run it on rooted Oreo :/
Click to expand...
Click to collapse
Do you have the Dean codename? @tys0n
---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------
If so, Alberto posted on my thread with TWRP attempt
tys0n said:
Unfortunatly that didn't work out well for me. I got in to some nasty boot problems and no matter what I did, it was always stuck at bootlogo. I gave it to a friend who's good at fixing these kind of problems but to no avail.
I really don't know what went wrong. Factory reset, re-flash firmware etc..nothing worked. As a last attempt we tried to boot slot _b instead but that was fatal.
It is now recognized as a Qualcomm HS-USB QDLoader 9008 so I can't even reach fastboot. lol Got no hope in finding a blank flash for it neither.
Sorry for late answer. I unrooted from magisk and flashed back stock boot.img taken from the firmware-package.
Anyway, I got a used one cheap so I still own the device. Won't try to root Pie again though. Not without TWRP.
Now I'm not sure whether I should upgrade or run it on rooted Oreo :/
Click to expand...
Click to collapse
I have updated without unrooting! Found a script how to do here: https://forum.xda-developers.com/showpost.php?p=78302865&postcount=22 And without erasing data partion.
Than I rooted as you describe for 8.1...
Sylvia said:
I have updated without unrooting! Found a script how to do here: https://forum.xda-developers.com/showpost.php?p=78302865&postcount=22 And without erasing data partion.
Than I rooted as you describe for 8.1...
Click to expand...
Click to collapse
Wooh, that's awesome! I have no idea why it didn't work for me on P, but yeah..
I'll probably update and try again then Thanks for sharing.
borksek said:
Do you have the Dean codename? @tys0n
---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------
If so, Alberto posted on my thread with TWRP attempt
Click to expand...
Click to collapse
Yes, it's deen, XT1941-4
Sylvia said:
I have updated without unrooting! Found a script how to do here: https://forum.xda-developers.com/showpost.php?p=78302865&postcount=22 And without erasing data partion.
Than I rooted as you describe for 8.1...
Click to expand...
Click to collapse
So, if I understood well, now you have Rooted Pie on the One? I am really interested in knowing how you got to do this, and I got lost in the Root-Update-reroot thing. Could you please explain what you did?
Thanks a lot
It works for me under Pie, too.
I patched the Stock boot.img with Magisk Manager and then flashed the created patched_boot.img with fastboot.
fastboot flash boot_a patched_boot.img
Finish...root at Android P
(XT1941-4 - OPENNEU)
1. Unlocked the bootloader: UNLOCK YOUR BOOTLOADER
2. Flashed the patched_boot.img via fastboot (even from OPENEU on RETEU ROM)
3. Completed the Magisk v17.1 installation from the Magisk Manager v6.0.1
4. Enjoying root on Pie 9.0 One.
To what partition do you flash the image?
Polyparadox said:
To what partition do you flash the image?
Click to expand...
Click to collapse
"fastboot flash boot patched_boot.img" works fine
Skickat från min Moto G5 via Tapatalk
tys0n said:
"fastboot flash boot patched_boot.img" works fine
Skickat från min Moto G5 via Tapatalk
Click to expand...
Click to collapse
Thanks, but I've got root. Although I'm not exactly sure how but I think it was this way:
Boot up TWRP
Format Data (not wipe)
Install Magisk (I used sideload)
Start your phine normaly and waot till its booted up
I installed Magisk Manager and saw that I was rooted.
Link to TWRP.
Related
{
"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't forget about the Mac users right?
What Can These One-Click Mac Toolkits Do?
Root Nexus 6
Unroot/Unbrick Nexus 6 back to complete stock
What Does The Nexus 6 One-Click Root Toolkit Do?
The root toolkit will unlock the bootloader, install TWRP recovery, and give you step-by-step intructions on installing SuperSU to get full root access on the Nexus 6.
What Does The Nexus 6 One-Click Unroot Toolkit Do?
The unroot toolkit will completely restore the Nexus 6 back to stock using the included Google factory images and it will also lock the bootloader. This toolkit also comes in handy if you want to completely wipe the Nexus 6 or if you need to unbrick the Nexus 6.
Download all the Mac toolkits here:
http://www.androidrootz.com/2014/11/nexus-6-one-click-mac-toolkit.html
Updates:
12/17/14
Both the Root and Unroot Nexus 6 Mac Toolkits have been updated, all issues including bootloops should be fixed! :good:
XDA:DevDB Information
[Toolkit] Nexus 6 One-Click Mac Toolkit [Root/TWRP/Unroot], Tool/Utility for the Nexus 6
Contributors
techfanatic9
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2014-12-17
Created 2014-11-29
Last Updated 2014-12-17
This is awesome! Had a new device arrive. Going to try right now!
Trying this now as well!
OP, I hate you.....
I just got my Nexus 6 today and just went threw hell unlocking and rooting it. Had to boot camp my MacBook Pro!
Finally got done and poof this thread appears!
Good job man, good job!
@Moostafa29 @konaman Did the toolkit get the job done, any issues along the way?
kdoggy said:
OP, I hate you.....
I just got my Nexus 6 today and just went threw hell unlocking and rooting it. Had to boot camp my MacBook Pro!
Finally got done and poof this thread appears!
Good job man, good job!
Click to expand...
Click to collapse
I'm unlocked but it didn't root for some reason. I have to leave for work soon so I'll try again tomorrow
---------- Post added at 03:20 AM ---------- Previous post was at 03:19 AM ----------
konaman said:
I'm unlocked but it didn't root for some reason. I have to leave for work soon so I'll try again tomorrow
Click to expand...
Click to collapse
Oops I meant to quote tech but tapped that other guy.
techfanatic9 said:
@Moostafa29 @konaman Did the toolkit get the job done, any issues along the way?
Click to expand...
Click to collapse
Worked for me! Only issue I had was when I clicked on the green Android, it wanted to open up in Adobe Flash Creator or something like that. After I right clicked and opened through terminal, everything worked great!
Anxiously waiting to get off work so I can try this on my newly purchased Nexus 6.
It didn't copy over UPDATE-SuperSU-v2.35.zip, but in the end that was my only issue. Thanks!
seattleweb said:
It didn't copy over UPDATE-SuperSU-v2.35.zip, but in the end that was my only issue. Thanks!
Click to expand...
Click to collapse
The toolkit wasn't suppose to transfer the SuperSU, the user is suppose to transfer that file manually as stated in the directions.
THANK YOU SO MUCH FOR THIS. I was about to just go through hell and back to root my phone with VM. Is it possible to use this to unencrypted also? Or is that a later update?
Thanks so much for this. Mac users definitely need some love too!
Now if only there was a better way to transfer files than using Android File Transfer...
V1ViD said:
THANK YOU SO MUCH FOR THIS. I was about to just go through hell and back to root my phone with VM. Is it possible to use this to unencrypted also? Or is that a later update?
Click to expand...
Click to collapse
Hmmm, haven't thought about encryption. I might add a new toolkit for that later on, right now I'm getting ready for college finals! :crying:
I am stuck in a bootloop with twrp. I tried using the unroot but it says that some files are missing. It re-locked the bootloader but won't flash the stock image. I tried downloading the windows toolkit but it won't recognize the device in adb.
slimc84 said:
I am stuck in a bootloop with twrp. I tried using the unroot but it says that some files are missing. It re-locked the bootloader but won't flash the stock image. I tried downloading the windows toolkit but it won't recognize the device in adb.
Click to expand...
Click to collapse
Make sure the bootloader is unlocked before you start the unroot toolkit and it may say that some things are missing, it happens with all Nexus devices. If you're still stuck on a bootloop after the unroot toolkit enter into Recovery mode and do a factory reset and reboot.
techfanatic9 said:
Make sure the bootloader is unlocked before you start the unroot toolkit and it may say that some things are missing, it happens with all Nexus devices. If you're still stuck on a bootloop after the unroot toolkit enter into Recovery mode and do a factory reset and reboot.
Click to expand...
Click to collapse
I tried followed those steps but it won't boot into recovery at all. It boots to the google screen twice and then tries to boot into twrp but boot loops.
Edit: for some reason the computer recognized the phone when I flashed everything manually. Thanks for the help!
techfanatic9 said:
@Moostafa29 @konaman Did the toolkit get the job done, any issues along the way?
Click to expand...
Click to collapse
Hats off to you sir! My issue I had with it not rooting was my fault. I was trying to hurry because I had to leave for work.
I got my phone rooted in like 2 minutes just now with no issues at all.
Thank you so much!!
slimc84 said:
I tried followed those steps but it won't boot into recovery at all. It boots to the google screen twice and then tries to boot into twrp but boot loops.
Edit: for some reason the computer recognized the phone when I flashed everything manually. Thanks for the help!
Click to expand...
Click to collapse
Hi there, I got into the same problem as you but can't get out of it. Can you elaborate on how you fixed it? Thanks!! Appreciate it very much!
hoaindao said:
Hi there, I got into the same problem as you but can't get out of it. Can you elaborate on how you fixed it? Thanks!! Appreciate it very much!
Click to expand...
Click to collapse
I followed the steps outlined in this thread.
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Note: I had to use the second option to get adb to recognize the device. I used this on a Windows machine as well.
I'm stuck in the same boot loop. Currently at a loss on how to proceed.
Restarted the tablet just now and noticed a Dell update. Installed it and, something definitely has improved as the tablet seems much quicker. Ran Antutu and the Ram speed has gone way up. Is it possible Dell has addressed an issue with these tablets? Anyone else get this update?
Yes i did receive this update, it fixed some of the browser issues in chrome.
I can't install the update is just fails mid Install with an Android Caution sign and constantly gives me the OTA Notification.
Maybe it depends on how new your Venue 8 is?
petewr said:
Maybe it depends on how new your Venue 8 is?
Click to expand...
Click to collapse
Mine is the newest 8340 - I think I messed something up but I am not sure how to return to stock as the only fastboot images I could find are rooted ones with disabled OTAs.
Haxxa said:
Mine is the newest 8340 - I think I messed something up but I am not sure how to return to stock as the only fastboot images I could find are rooted ones with disabled OTAs.
Click to expand...
Click to collapse
Were you rooted or stock?
My wifes 8340 was rooted and the updater rebooted and promptly failed. Tablet didn't loose root but something is definitely messed up now. I've not had time to figure out what happened yet.
LinuxTom said:
Were you rooted or stock?
My wifes 8340 was rooted and the updater rebooted and promptly failed. Tablet didn't loose root but something is definitely messed up now. I've not had time to figure out what happened yet.
Click to expand...
Click to collapse
Yes I am rooted but no root apps were used and I unrooted to no avail. So it must be to do with the root process or something it has changed in the system partition. If we had fastboot images it would be easy enough to revert to stock and upgrade...
Haxxa said:
Yes I am rooted but no root apps were used and I unrooted to no avail. So it must be to do with the root process or something it has changed in the system partition. If we had fastboot images it would be easy enough to revert to stock and upgrade...
Click to expand...
Click to collapse
Aren't stock images available on the mykit_batch thread?
LinuxTom said:
Aren't stock images available on the mykit_batch thread?
Click to expand...
Click to collapse
Not for the Dell Venue 8340 (New Version) as far as I can see.
Haxxa said:
Not for the Dell Venue 8340 (New Version) as far as I can see.
Click to expand...
Click to collapse
You all can make your own, that's how those are made.
vampirefo said:
You all can make your own, that's how those are made.
Click to expand...
Click to collapse
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Haxxa said:
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Click to expand...
Click to collapse
I think someone has http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
quote from post below, I don't have this tablet to confirm, I have 3830, have made my own back ups since day one.
Code:
Stock Build YTP802A128630 Images
Note, unless you are doing development, you won’t need to download the following file. For Developers, here are the stock Android 4.4.4 (not rooted) boot.img, recovery.img, system.img.gz:
Dell_venue8_3840_4.4.4_Stock_Images.zip 822.1MB md5sum: 995db36a2daa6bd9955e75fa5a14a519
Haxxa said:
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Click to expand...
Click to collapse
Looks like OEM 4.4.4 images are at http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427/post57209175#post57209175
LinuxTom said:
Looks like OEM 4.4.4 images are at http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427/post57209175#post57209175
Click to expand...
Click to collapse
vampirefo said:
I think someone has http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
quote from post below, I don't have this tablet to confirm, I have 3830, have made my own back ups since day one.
Code:
Stock Build YTP802A128630 Images
Note, unless you are doing development, you won’t need to download the following file. For Developers, here are the stock Android 4.4.4 (not rooted) boot.img, recovery.img, system.img.gz:
Dell_venue8_3840_4.4.4_Stock_Images.zip 822.1MB md5sum: 995db36a2daa6bd9955e75fa5a14a519
Click to expand...
Click to collapse
No Dice!
So I have tried everything to return to stock, the stock images provided in the thread refuse to flash with fastboot outputing error 121, It is a big image and gets half way through downloading system.img when this error occurs, I have tired unbricking but it will not detect my device when pressing download button and have tried about every driver available & 3 computers. I tried using CWM temp boot to flash the system.img put inside a update.zip but it did not work and now I am prepared to return the tablet as it will not restore
Any ideas left to help here?
Here's the error when using fastboot-
{
"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"
}
& The xFSTK Flasher gives no error as I can't no matter what I do get it to detect.
I have now spent 20 Hours trying to fix this - I have run through the guide 3 times and used 3 different computers I have no idea what to do?
Haxxa said:
No Dice!
So I have tried everything to return to stock, the stock images provided in the thread refuse to flash with fastboot outputing error 121, It is a big image and gets half way through downloading system.img when this error occurs, I have tired unbricking but it will not detect my device when pressing download button and have tried about every driver available & 3 computers. I tried using CWM temp boot to flash the system.img put inside a update.zip but it did not work and now I am prepared to return the tablet as it will not restore
Any ideas left to help here?
Here's the error when using fastboot-
& The xFSTK Flasher gives no error as I can't no matter what I do get it to detect.
I have now spent 20 Hours trying to fix this - I have run through the guide 3 times and used 3 different computers I have no idea what to do?
Click to expand...
Click to collapse
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
vampirefo said:
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
Click to expand...
Click to collapse
My deep apologies I have never flashed a .gz in fastboot before file I just assumed it need to be unachieved and it was compressed for the purpose of size...
I did try to build a Rom however it would not build on my Linux Server for some reason so I gave up on that after a few hours.
vampirefo said:
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
Click to expand...
Click to collapse
Well I just managed to restore the system image found on the thread on to the tablet however when updating I encounter the same issue with the update failing. Even after flashing system, recovery, boot and wiping data back to original. There should be no trace of root at all....
Haxxa said:
Well I just managed to restore the system image found on the thread on to the tablet however when updating I encounter the same issue with the update failing. Even after flashing system, recovery, boot and wiping data back to original. There should be no trace of root at all....
Click to expand...
Click to collapse
How did you root? What are the errors you get from OTA update?
sent from my kingSing T1 via taptalk
vampirefo said:
How did you root? What are the errors you get from OTA update?
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Using Tethered Recovery by Social, and the error is half way through installing OTA in Recovery it goes from a loading (Progress bar) to a red caution symbol and then it reboots. Upon boot the version number and details remian the same....
Also should add this is stock without any mods or installed apps (just flashed and went straight to updating) ... root should have disappeared entirely when I flashed system.
Haxxa said:
Using Tethered Recovery by Social, and the error is half way through installing OTA in Recovery it goes from a loading (Progress bar) to a red caution symbol and then it reboots. Upon boot the version number and details remian the same....
Also should add this is stock without any mods or installed apps (just flashed and went straight to updating) ... root should have disappeared entirely when I flashed system.
Click to expand...
Click to collapse
That doesn't help, if I had that tablet, I would run the ota update through my cwn recovery, all failures are recorded so would know what was wrong.
Stock recovery I don't think records failures, without a log can't help you.
sent from my kingSing T1 via taptalk
This is my first post, so I apologize if I am in the wrong section, but I really need help.
After running diferent custom roms on my KIW-L21, I saw the official MM update on the forum, so I restored my TWRP backup of B140 and tried updating but with no luck, so I tried restoring stock B130. Because the force update wouldn't work I flashed the files manually using adb and fastboot and succeded. The problem is that now, when I go to the 'about phone' panel all the informations except for the version number are wrong :
model is unknown
CPU shows quad core 1,2 GHz
RAM 1,0 GB
Memory 4,0 GB
Resolution 540 x 960
Android version 4.3.
Has anyone encountered anything like this?
Once again, I am very sorry if I posted this in the wrong section, but I could really use some help.
cosminvr27 said:
This is my first post, so I apologize if I am in the wrong section, but I really need help.
After running diferent custom roms on my KIW-L21, I saw the official MM update on the forum, so I restored my TWRP backup of B140 and tried updating but with no luck, so I tried restoring stock B130. Because the force update wouldn't work I flashed the files manually using adb and fastboot and succeded. The problem is that now, when I go to the 'about phone' panel all the informations except for the version number are wrong :
model is unknown
CPU shows quad core 1,2 GHz
RAM 1,0 GB
Memory 4,0 GB
Resolution 540 x 960
Android version 4.3.
Has anyone encountered anything like this?
Once again, I am very sorry if I posted this in the wrong section, but I could really use some help.
Click to expand...
Click to collapse
you need this > http://forum.xda-developers.com/honor-5x/how-to/kiw-l21-c432b130-uk-revert-package-t3368480
clsA said:
you need this > http://forum.xda-developers.com/honor-5x/how-to/kiw-l21-c432b130-uk-revert-package-t3368480
Click to expand...
Click to collapse
I already tried that, but at the start of the installation it gives me 'system file instalation failed'.
cosminvr27 said:
I already tried that, but at the start of the installation it gives me 'system file instalation failed'.
Click to expand...
Click to collapse
yeah well where did you get the files you flashed with fastboot ?
use the Huawei Update Extractor and get the files from the link i posted
clsA said:
yeah well where did you get the files you flashed with fastboot ?
use the Huawei Update Extractor and get the files from the link i posted
Click to expand...
Click to collapse
Will try, but after the extraction wich files should I flash?
On a post I saw it said that I should flash only cust, system, recovery and boot.
Is it necesary to flash all the files from the update?
cosminvr27 said:
Will try, but after the extraction wich files should I flash?
On a post I saw it said that I should flash only cust, system, recovery and boot.
Is it necesary to flash all the files from the update?
Click to expand...
Click to collapse
System and data
You may also need cust from paulobrian rom
Sent from my SM-N920C using Tapatalk
clsA said:
System and data
You may also need cust from paulobrian rom
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I managed to flash a stock rom using gopinaidu77's [RoM][StOcK][Kiw-L22/L21]B140.Debloated, because it is the only one I found that is stock but .zip file.
The only question now, if you can help me with an answer, is what could go wrong if in the 'about phone' panel model number is MSM8916 for arm64 and the file version is kiw-l24c567b140.
I mean, taking to consideration that my phone is KIW-L21 and the original file version it was originally for KIW-L24.
Anyway I really apreciate the help.
cosminvr27 said:
I managed to flash a stock rom using gopinaidu77's [RoM][StOcK][Kiw-L22/L21]B140.Debloated, because it is the only one I found that is stock but .zip file.
The only question now, if you can help me with an answer, is what could go wrong if in the 'about phone' panel model number is MSM8916 for arm64 and the file version is kiw-l24c567b140.
I mean, taking to consideration that my phone is KIW-L21 and the original file version it was originally for KIW-L24.
Anyway I really apreciate the help.
Click to expand...
Click to collapse
this rom contains the /cust partition you need
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
after flashing it with TWRP
Flash stock recovery with TWRP / Install / Install Image >> https://www.androidfilehost.com/?w=files&flid=51004
when you are done leave twrp with power off
now with the update.app files in the sdcard/dload boot the phone with
Power+ vol+ and vol-
EMUI will flash the phone
if you want complete stock boot to stock recovery (power + volume up) and choose factory reset
cosminvr27 said:
I managed to flash a stock rom using gopinaidu77's [RoM][StOcK][Kiw-L22/L21]B140.Debloated, because it is the only one I found that is stock but .zip file.
The only question now, if you can help me with an answer, is what could go wrong if in the 'about phone' panel model number is MSM8916 for arm64 and the file version is kiw-l24c567b140.
I mean, taking to consideration that my phone is KIW-L21 and the original file version it was originally for KIW-L24.
Anyway I really apreciate the help.
Click to expand...
Click to collapse
Download twrp backup for KIW-L21C432B130 from here and restore using twrp
After restoring backup flash stock recovery before booting into system then update as normal through OTA to B140 firmware
https://r.tapatalk.com/shareLink?ur...share_tid=3328288&share_fid=3793&share_type=t
[Repository] The Honor 5x File Depot
Sent from my KIW-L21 using Tapatalk
chubby65 said:
Download twrp backup for KIW-L21C432B130 from here and restore using twrp
After restoring backup flash stock recovery before booting into system then update as normal through OTA to B140 firmware
https://r.tapatalk.com/shareLink?ur...share_tid=3328288&share_fid=3793&share_type=t
[Repository] The Honor 5x File Depot
Click to expand...
Click to collapse
I am sorry guys,it didn't work.
Tried everything but it seems that the only rom working is the one I mentiones above.
Thank you very much,both of You,though,but for now I guess I'll stock to this one.
The only question now remains how will the fact that it show 'KIW-L24' will afect future updates ?
cosminvr27 said:
I am sorry guys,it didn't work.
Tried everything but it seems that the only rom working is the one I mentiones above.
Thank you very much,both of You,though,but for now I guess I'll stock to this one.
The only question now remains how will the fact that it show 'KIW-L24' will afect future updates ?
Click to expand...
Click to collapse
Did you extract the backup from the zip
Sent from my KIW-L21 using Tapatalk
chubby65 said:
Did you extract the backup from the zip
Click to expand...
Click to collapse
Yes I did, the only problem is that it will not boot. It gets stuck at the first honor logo.
It only booted when I tried the first solution but in that case again it was showing 'unknown device' '1 gb of ram' etc.
cosminvr27 said:
I am sorry guys,it didn't work.
Tried everything but it seems that the only rom working is the one I mentiones above.
Thank you very much,both of You,though,but for now I guess I'll stock to this one.
The only question now remains how will the fact that it show 'KIW-L24' will afect future updates ?
Click to expand...
Click to collapse
what didn't work ? if you can't follow simple steps how do you expect to fix the phone ?
Did you download and flash the customromtemplate-5x-plk21-b130-r3.zip from paulobrien ? if you did your phone would not still say L24 it would be L21
The phone boots very slow wait at least 10 - 15 min before you give up on it
clsA said:
what didn't work ? if you can't follow simple steps how do you expect to fix the phone ?
Did you download and flash the customromtemplate-5x-plk21-b130-r3.zip from paulobrien ? if you did your phone would not still say L24 it would be L21
The phone boots very slow wait at least 10 - 15 min before you give up on it
Click to expand...
Click to collapse
I read the description of the rom and saw that it boots slow and left it 35 minute by the watch before giving up. That was the only thing that it didn't work,the fact that it didn't boot.
cosminvr27 said:
I read the description of the rom and saw that it boots slow and left it 35 minute by the watch before giving up. That was the only thing that it didn't work,the fact that it didn't boot.
Click to expand...
Click to collapse
well i have no idea what you flashed with fastboot but you seem to have messed up good if the factory stock rom won't boot
cosminvr27 said:
Yes I did, the only problem is that it will not boot. It gets stuck at the first honor logo.
It only booted when I tried the first solution but in that case again it was showing 'unknown device' '1 gb of ram' etc.
Click to expand...
Click to collapse
When it sticks at logo boot in bootloader mode and fast boot flash the stock boot image then the phone WILL reboot as normal mate
Trust me it happened to me and that sorted it
Sent from my KIW-L21 using Tapatalk
chubby65 said:
When it sticks at logo boot in bootloader mode and fast boot flash the stock boot image then the phone WILL reboot as normal mate
Trust me it happened to me and that sorted it
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
It worked, thank u very much mate1
cosminvr27 said:
It worked, thank u very much mate1
Click to expand...
Click to collapse
No worries mate glad you're all sorted
Sent from my KIW-L21 using Tapatalk
This happened to me also. I flashed SuperSU on my GR5 and it went on bootloop. So I searched for TWRP Backup but I flashed KIW the first time, so I searched again and found the file. After boot, my about phone is displaying the wrong info. And also the pc detects it as MSM8916 for arm64 with only 2GB space. Please help
{
"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"
}
---------- Post added at 05:47 AM ---------- Previous post was at 05:25 AM ----------
I can't edit or post another link ><"
ht*tp://i.imgur.com/IXvNPEr.png
ht*tp://i.imgur.com/79HFKGq.png
{
"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"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
hello guys in last few days ME and my friend Dhruv worked so hard to finally got Twrp ready to use so please makr sure to hit thanks ( it's free and easy way to help me )
Notice1:
both phones they share same kernel and tree and both have A/B partitions, this twrp based on nokia7+
Notice2:
take a backup for your data and your important files or folders before you start your Warrenty will be lost
I'm not responsible for any damage in your phone but I'll always and as usual do my best to help you in case something goes wrong
Notice3:
to reboot recovery from buttons follow this steps:
first of all you have to plug your phone to pc or charger and switch off your phone totally then press and hold volume up and power at the same time untill the bootloader`s unlock message disappear after that release power button and keep holding volume up
there you are
Notice4:
to boot to fastboot switch off your phone plug it to charger or pc wait till the screen charging become black now press and hold volume down and power buttons you`ll get fastboot page there you are
Nokia 6.1 (6 2018) Twrps:
October
https://drive.google.com/file/d/1bF1oNRzH0Kj1i5PZ7E_OijCVNvvy8gcF/view?usp=sharing
September
https://drive.google.com/file/d/1bupZhAXIik0LTEJVReSAO6yGAEEYvpSL/view?usp=sharing
August
https://drive.google.com/file/d/1V_3ORXibJUm12IGsYWCs_D3hBHNpvgG2/view?usp=sharing
July
https://drive.google.com/file/d/1XoUAbzPbx_JHccxttXtXGHDGHwDBqQO7/view?usp=sharing
June
https://drive.google.com/file/d/11kEZTItYhiU_U372a2cXadafJJZE3hAr/view?usp=sharing
Twrp for Nokia 6.1 plus
August
https://drive.google.com/file/d/1u4tcdcWsA-C6LKEWr6wwFmEn3RlNOS3s/view?usp=sharing
INSTALLATION
required :
1- unlocked bootloader
2- ADB and fastboot
3- enable usb debugging in developer settings.
4- use those codes
Code:
adb shell
Code:
reboot bootloader
now we flash it
Code:
fastboot flash boot <image`s name>.img
then
Code:
fastboot reboot
it will boot to system dirctly so reboot to recovery
Code:
adb reboot recovery
6- install magisk.zip v17.1 + download it with latest apk from here (( thanks for Magisk developers )
https://forum.xda-developers.com/app...80cb6-t3618589
7- that`s all please if you like my work hit like and if you want to share cup of cappuccino with me
paypal.me/MaherAbdulghani
Nokia6.1 group on Telegram go here
https://t.me/nokia6_1
Nokia globle group on Telegram go here
https://t.me/joinchat/EDAqGkPkzNQG5b7q28b1yw
Special thanks to:
Team Win Recovery Project developers
my friend Dhruv for his help
Reserved
#Reserved
Ok cool but this nokia phone can't be bootloaded into; it's always locked, even if you tick on allow oem unlocking in dev settings fastboot will tell you it doesn't have permission. Whats the purpose of this? Is there some kind of way to get past it that I am not aware of?
pixeloite said:
Ok cool but this nokia phone can't be bootloaded into; it's always locked, even if you tick on allow oem unlocking in dev settings fastboot will tell you it doesn't have permission. Whats the purpose of this? Is there some kind of way to get past it that I am not aware of?
Click to expand...
Click to collapse
You need to unlock bootloader, it is a paid service....
@Maherabed1986 can you add link to the bootloader unlock to your guide?
Sent from my Lenovo TB-8704F using XDA Labs
Ja_som said:
You need to unlock bootloader, it is a paid service....
Sent from my Lenovo TB-8704F using XDA Labs
Click to expand...
Click to collapse
I have not seen this service anywhere, I did see that a page containing this service was deleted due to paid services, though. Regardless, I can imagine only a few handfuls of people being able to make use of this, which is a shame.. I hope in the future some method of unlocking it at home gets discovered, but that probably won't happen knowing nokia.
pixeloite said:
I hope in the future some method of unlocking it at home gets discovered, but that probably won't happen knowing nokia.
Click to expand...
Click to collapse
I also hope, not because $5 is much for it, but I rather do it myself w/o giving my IMEI or any other infos to someone. As it was on Nexus devices.
Sent from my Lenovo TB-8704F using XDA Labs
Ja_som said:
You need to unlock bootloader, it is a paid service....
@Maherabed1986 can you add link to the bootloader unlock to your guide?
Sent from my Lenovo TB-8704F using XDA Labs
Click to expand...
Click to collapse
No i can't but you can ask the guys on the groups
I'm new here and I don't know much about phones but I'll ask a dumb question anyway. Can't you do something about unlocking the bootloader now that you have a working rooted version w/ twrp ? If the answer is no please elaborate on why not.
madddking said:
I'm new here and I don't know much about phones but I'll ask a dumb question anyway. Can't you do something about unlocking the bootloader now that you have a working rooted version w/ twrp ? If the answer is no please elaborate on why not.
Click to expand...
Click to collapse
Because no one still now how to generate serial number and Imei number to get unlock file only one who knows that and he selling it for others and others resell it to me /you/ and othere users
@Maherabed1986 Thank you for getting this device rooted. Why does Magisk has Preserve force encryption selected by default?
Is the Nokia 6.1 encrypted by default? I had many Android devices and none were encrypted by default. I didn't know this Nokia was encrypted until I saw it on Magisk.
@Maherabed1986 Thanks so much for your efforts, I would like to contribute a dump of my boot.img for my model of Nokia 6.1 (TA-1045) but the instructions didn't quite work the way I expected, when I attempt to temp boot into the bootloader linked for the Nokia 6.1 it just boots into regular Android and then trying to su in the adb shell it tells me the command can't be found (because I am not rooted yet, of course). Am I missing something? How can I help?
spyda256 said:
@Maherabed1986 Thanks so much for your efforts, I would like to contribute a dump of my boot.img for my model of Nokia 6.1 (TA-1045) but the instructions didn't quite work the way I expected, when I attempt to temp boot into the bootloader linked for the Nokia 6.1 it just boots into regular Android and then trying to su in the adb shell it tells me the command can't be found (because I am not rooted yet, of course). Am I missing something? How can I help?
Click to expand...
Click to collapse
Contact with me on telegram will help you more
Maherabed1986 said:
Contact with me on telegram will help you more
Click to expand...
Click to collapse
Just sent you the boota and bootb imgs, hope that helps develop TWRP for the TA-1045! Thanks for helping get me to a point where I could get the boot dump.
Rooting with KingRoot app and than using this TWRP-Recovery possible?
I'm new here and I don't know much about phones, rooting etc., so i have this question:
Can i root my phone (TA-1068) in the first step with the KingRoot app and than install this TWRP-TA-1068-Recovery on this rooted phone?
(mayme per simple installing with Root Explorer - and without computer and adb...?)
Hello... yesterday night at Nokia 6.1 I try 2 times to flash recovery but I didn't succed. I use adb and phone stuck at fastboot (download mode) PC write wait for phone.. any help?
chriskleov said:
Hello... yesterday night at Nokia 6.1 I try 2 times to flash recovery but I didn't succed. I use adb and phone stuck at fastboot (download mode) PC write wait for phone.. any help?
Click to expand...
Click to collapse
What model do you have (TA-10xx)? And did you try to just boot before trying to flash the img?
spyda256 said:
What model do you have (TA-10xx)? And did you try to just boot before trying to flash the img?
Click to expand...
Click to collapse
Can you understand from screenshot? No I don't boot before flashing.
Just tired this on my USA Nokia 6.1 TA-1045 ... Used Twrp-N6.1-TA-1045.img (md5 6e9b859f6fe6138aa14beaea6cbdb26d ) in slot a and b using the commands provided and now my phone can't get passed the NOKIA screen. Any ideas?
---------- Post added at 08:13 AM ---------- Previous post was at 07:54 AM ----------
After doing a "fastboot -w", I was able to boot into TWRP but I am bootlooping when trying to boot into the system. Will do further research
prg318 said:
Just tired this on my USA Nokia 6.1 TA-1045 ... Used Twrp-N6.1-TA-1045.img (md5 6e9b859f6fe6138aa14beaea6cbdb26d ) in slot a and b using the commands provided and now my phone can't get passed the NOKIA screen. Any ideas?
---------- Post added at 08:13 AM ---------- Previous post was at 07:54 AM ----------
After doing a "fastboot -w", I was able to boot into TWRP but I am bootlooping when trying to boot into the system. Will do further research
Click to expand...
Click to collapse
That's why i dont try it. Did you wipe all cache like dalvik.
{
"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"
}
Natesu53 said:
View attachment 5826507View attachment 5826509
Click to expand...
Click to collapse
?????
DrScrad said:
?????
Click to expand...
Click to collapse
Do you have a question
I managed to capture a full ota, and a --diff-incremental ota...
Natesu53 said:
I managed to capture a full ota, and a --diff-incremental ota...
Click to expand...
Click to collapse
well, would youliek to share your capture or you just gonna flaunt it? lol.. and were you able to achieve root and succesful boot thereafter ?
DrScrad said:
well, would youliek to share your capture or you just gonna flaunt it? lol.. and were you able to achieve root and succesful boot thereafter ?
Click to expand...
Click to collapse
Yes sir
I was able to capture ota extract the "payload.bin" get the boot image patched it with magisk app . Then I flashed it using fastboot on the computer.
I booted up the device installed root checker and it worked.
Natesu53 said:
I booted up the device installed root checker and it worked.
Click to expand...
Click to collapse
And this was android 12? I'm assuming you had to disable vbmeta as well yeah?
My only question to you... , but that's why I'm here . Is do you correctly have a nord n20 GN2200, and if so does your device turn on properly. Is it bricked .
DrScrad said:
And this was android 12? I'm assuming you had to disable vbmeta as well yeah?
Click to expand...
Click to collapse
Yes I disabled vbmeta
And yes it was android 12
My OnePlus is booting just fine. How'd you go about capturing that ota BTW
Natesu53 said:
My only question to you... , but that's why I'm here . Is do you correctly have a nord n20 GN2200, and if so does your device turn on properly. Is it bricked .
Click to expand...
Click to collapse
Currently** corrections
Natesu53 said:
Currently** corrections
Click to expand...
Click to collapse
I'm trying to show you but it won't let me post the pics cause too much too process with xda
Natesu53 said:
I'm trying to show you but it won't let me post the pics cause too much too process with xda
Click to expand...
Click to collapse
Hit me up on telegram
Or hell just email me with what you're trying to post
[email protected]
Images
So basically you connect your phone to the computer. Make sure you have automatic updates shutoff. Start downloading the update, but don't download it all the way . Pause it after 15 seconds. Type " adb logcat > ota.txt " without quotation . In you platform tools folder there should be a file called it's.txt open it . In the search type " googleapis " and you will find a httpslink.zip copy it and paste it in your browser it should start downloading. Extract the downloaded file. The payload will be in the extracted folder.
Ota.txt** not it's.txt
I have steps for you on how to extract the payload.bin file with payload_dumper-master... Once you got a capture of your ota
Also I have telegram, but I need to download it.
I sent message on telegram
Platform-tools directory in terminal type that command*
Also I had android 11 at first . I did end up bricking my phone trying to install a unofficial TWRP. I thought I was never get my phone back working then I tried to flash different boot.img . I flashed it with different ppls images. Still nothing. Kept doing research. Flashed it more had a phone that finally turned on , but no wifi .... I flashed the October patch android 11 flashed vbmeta , boot image , system.image system_etc.img . I finally was able to turn on my phone have wifi. I noticed there was a new update . I was just gonna download the update to fully get my phone back to normal, but this was my chance to root it cause all the software lined up . I figured out how to capture ota . I capture the ota to my version of the new update. I downloaded my update for Android 12. I patched the boot.img . BOOM flashed it phone successfully rooted . New update to Android 12 and root.
So my phone is currently rooted on the android 12 , but there is a new update . What I'm trying to figure out is how to update it. It seems you can only get the boot.img with full ota . With be android 11 at first . Android 12 was a full ota. Since I'm on android 12 there is a new update, but it's not a full ota . It's a incremental meaning not all the software is getting modified. I did manage to capture my incremental update , and you'll know it's not a full ota if it's only like 100mb. full ota are like 4gb . So I have the payloads for both updates. I'm trying to combine/extract both payload.bins boot.img combine them together to have a new updated root . My phone is still rooted properly . I would just like to stay up to date.
Natesu53 said:
I'm trying to show you but it won't let me post the pics cause too much too process with xda
Click to expand...
Click to collapse
I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my mouse on it.
DrScrad said:
My OnePlus is booting just fine. How'd you go about capturing that ota BTW
Click to expand...
Click to collapse
Start the OTA & then logcat - link will be in there
nam*eerf said:
I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my
Click to expand...
Click to collapse
nam*eerf said:
I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my mouse on it.
Click to expand...
Click to collapse
Umm what android version are you on , and what model . I could possibly upload the images for you to flash. , But my theory is you have to flash all the images on both slots to get it back working . If you're interested lmk.
Like system.img boot.img vendor.img modem.im ect... All the core images
Yes I believe it is possible. It's like getting a new update. And I have it all extracted from the payload bin. I check Here every so often if anyone interested. Like every image
Gotta flash all them so they all line up
Don't wanna just post anything and someone bricks there phone. But if your phone is already bricked , them it don't hurt to try.
I don’t usually post I just kinda hang back and read but I have an n20 gn2200 that I bricked trying to get rw on the system. I have tried so many combinations of flashing this that and the other that I don’t really know what firmware I’ve downloaded anymore. I know I was on 12 before I crashed the phone and was going to try getting twrp on my slot b partition but haven’t got there. If you have flashable imgs for android 12 I’ll give them a shot. Don’t mind trying it out like you said can’t hurt right
I got you . And the thing about twrp . You gotta flash it to your recover.img. it replaces your recovery. I've flashed it to my boot.img , and that's what bricked my phone.
And Nord doesn't have an official twrp that works. And I'm not seeing any recovery.img partitions.
Once I upload to Google drive . I will upload the link to all the images for download. I just need set my computer down and let them upload it'll take a lil time .
Uploading...
I've managed to figure out how to modify partitions and flash them. Like anyone interested in following along with this new project I'm working on. Like I mounted my_product.img to my computer edited some files deleted the carrier boot animations . If you try to mount it it'll mount, but it won't let you edit or delete files. OnePlus partitions are erofs not ext2, ext3, or ext4. Erofs is a read only file system I've came across this program that converts it to ext2. I was able to mount it I edited some files deleted some files. Flashed it .it flashed without a problem. The original my_product.img was like 300 mb. When it got converted it was like 600mb. So I deleted the carrier boot animations, and it reverted to the OnePlus boot animation. When I deleted the OnePlus boot animation it reverted to a stock android boot animation. And when I use a root explorer on the phone it allows me to create folders delete files. So the my_product which contains the boot animations flashed without a problem. So I did the same thing to system.img it lets me convert it edit files. When I go to flash it. I get an error. " fastboot flash system systemsu.img" the error says " invalid sparse file format at header magic Resizing 'system_a' FAILED (remote: 'not enough space to resize partition')". the original system.img was like 700mb then it changed to 1.5 gb once I converted it. If there is a way to reduce the size of the partition it it'll work . Or if you increase the size available, so you don't get an error.