I'll be very specific, something most people lack of. Okay lets get to it,
I recently bricked my LG G2 (D801) by installing a ROM that wasn't compatible with my model. I fixed it by doing the following steps.
This worked for me using Windows 8.1 pro on a 64 bit architecture computer without using compatibility mode.
I will be showing you how to unbrick your phone by using the .TOT method.
If your cellphone looks like the image below, then you are bricked.
{
"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"
}
Prerequisites:
A) LG G2 Driver (Virus Scan)
B) LG FlashTool v1.8.1.1023 (Virus Scan)
C) Fastboot w/ adb (Virus Scan)
D) Choose the correct model image for your cellphone, This step is very important, you DO NOT want to install the wrong images.
D800 (Mirror)
D801 (Mirror)
D802 (Mirror)
D803 (Mirror)
D805 (Mirror)
D806
F320L (Mirror)
F320S (Mirror)
LS980 (Mirror)
VS980 (Mirror)
Places you can download your phones .TOT files
Here or Here it will be in a form of .ZIP file or .TOT
For the F320S .TOT file you can download it => Here
1. Install the LG G2 driver onto your computer
2. Install the LG G2 Flashing Tool
UNCHECK "Run LGFlashTool 1.8.1.1023" then click "Finish"
Now go to your LG FlashTool directory like the image below, and replace the MegaLock.dll with the one I provided in the zip file "C:\LG\LGFlashTool"
3. Now run fastboot.exe inside a Command Prompt window (while your phone is connected to the computer)
You will need to run these commands inside Command Prompt
Code:
fastboot erase aboot
fastboot flash aboot aboot.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase dbi
fastboot flash dbi dbi.img
fastboot erase laf
fastboot flash laf laf.img
fastboot erase misc
fastboot flash misc misc.img
fastboot erase modem
fastboot flash modem modem.img
fastboot erase persist
fastboot flash persist persist.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase rpm
fastboot flash rpm rpm.img
fastboot erase sbl1
fastboot flash sbl1 sbl1.img
fastboot erase tz
fastboot flash tz tz.img
fastboot reboot
4. Hold the volume + (up) key, then plug in your phone to the computer using the USB cable your phone came with or a compatible cable that fits. Do not let go of the volume + (up) key until you see Download Mode.
Once your cellphone is in Download Mode, we need to change the COMPort your phone is connected to, in order for LG FlashTools to read the cellphone. To do this, Click on Start > Click on Control Panel > Click on Device Manager
Right Click on "LG Mobile USB Serial Port (COM4)" then click on Properties
Then click on "Port Settings" then "Advanced"
Make sure that, the COMPort goes from COM4 to COM41
Then click okay
Before I start on step 5, here's are some errors you would have seen, if you followed other tutorials or did not follow my step 5.
These two errors happen for the following reasons,
Picture 1: I used a different .dll than what the .TOT file needed
Picture 2: The .TOT file is not pointing correctly to our Model installed on our phone (which isn't my real model btw, it's what bricked my phone in the first place, by installing a none compatible ROM it changed my phones model. So we need to modify the .TOT file using a Hex editor so that LG FlashTools could read the .TOT file.
5. Download any Hex editor and install it on your computer (I already have one installed, so ill skip the boring installation pictures)
Then drag and drop your .TOT file to modify it, Then click on search => Find
Type in the Model of your phone, before the ROM changed the model (my original phone model is D801)
You will see this Hex string (not the same exact one but something similar)
To change the Hex string, you have to have the Model your phone is bricked to .TOT file (which in this case for me is the F320S .TOT file)
Then copy the Hex string like I have in the image below
Then paste it to the .TOT file we want to modify (which for me is my D801 .TOT file)
Click on "Paste Write" because if you click "Paste Insert" it will write more space into the .TOT file not letting LG FlashTool to read the modified .TOT file.
Finally just click on the save button
6. Now open up LG FlashTools and choose your phones bricked model .dll (which for me is F320S.dll)
Then choose the modified .TOT file, like the image below.
Click on the yellow arrow, then you will see "Bin CRC Check"
In order for LG FlashTools to read your phone, unplug and replug your phone to the computer (if done correctly you should see this)
Now the phone is being Fixed and installing the original operating system the phone came with. (which for me is D801, not F320S)
I hoped I helped you guy's fixed your phones, if I did hit me up with a Thanks!
You may now, re-root and mess around your phone again
OMG thanks so much for your time and this wonderful guide!!! I will be trying this sometime soon on my VS980. I get random power offs and then it won't boot. I have flashed the 11A .tot file several times and try upgrading through the verizon OTA. This started happening on several ROMS I tried after flashing xdabbed's 26A bootstack zip... I assume I messed up my partitions, but I'm not sure. Flashing the .tot file has not fixed the problem.
I can't say how much appreciate for your work. It saves my G2. I was stuck for 1 day and could take longer if I couldn't find your guide. Thanks a lot.
Thank you. this is extremely helpful for me bc I bricked as well. I followed your instructions and now my phone is alive again. All the photos helped tremendously.
ihave a d802 but listed as G2
my phone is listed as G2 , not d802 or d800 or d801
i trayed editind tot file but the flash tool faile to load it . plz help
No photos help me
Good afternoon, Friend me know if you can see photos of tuturial, I have some doubts of the process and do not want to fail at some step. My phone is the LG G2 D805 but will install the rom GROLA ROM V2 and stick with LG L01F, or F320K want to know if I served this tuturial
THANKS!!!!!!!!!!!!!!!!!!!
Thanks to you i all ready save my g2, this TOT METHOD REALLY works.
Thanks for posting this.
Does this method wipe everything including internal storage?
Yes, it wipes everything
Hello, after step 3, my screen comming black and don't instert in DM or RM. Even when I put for charging is still black!
In the end, inside in devise manager I see this "QHSUSB__BULK"
I have an internation G2 D802 32gb.
Any ideas?
i now get this error
I Tried Using the .dll For LS980 Instead of the LGUP_8974.dll (F320S) and still get this error. What should i do ?
mkeeoma said:
i now get this error
View attachment 3262653
I Tried Using the .dll For LS980 Instead of the LGUP_8974.dll (F320S) and still get this error. What should i do ?
Click to expand...
Click to collapse
Make sure you downloaded the right dll for that tot file. If you did (not sure if you did or not) you should check the tot file that its been hex edited for that dll file.
You probably don't have the right driver installed or driver installed at all?
If not install them, if you do have the driver install then this TOT method wont work for you, and this one is your next hope.
You probably flashed the wrong images.
Extosis said:
You probably don't have the right driver installed or driver installed at all?
If not install them, if you do have the driver install then this TOT method wont work for you, and this one is your next hope.
You probably flashed the wrong images.
Click to expand...
Click to collapse
are on the D855 port
I downloaded the dll file D855
I changed the model D855
Lg flash tool always error
Bin model is different
You sure? because the program says otherwise.
Extosis said:
You sure? because the program says otherwise.
Click to expand...
Click to collapse
Solved
I put the dll F320S
Lg tool saw it as D855
but I had installed a rom F320S
Thanks for great guide
please help me im having d same problem and i was stuck on 3rd step please help me,
i 'm having the same screen and bricked my device by flashing on D80210b with D80230a and i've followed the steps but its showing me like "FAILED (status read failed (too many links))
saagii said:
i 'm having the same screen and bricked my device by flashing on D80210b with D80230a and i've followed the steps but its showing me like "FAILED (status read failed (too many links))
Click to expand...
Click to collapse
You are using the wrong image files.
Also install the driver (if you haven't already)
will this restore my lost imei?
Dooblay said:
will this restore my lost imei?
Click to expand...
Click to collapse
To be honest with you, I don't know and probably don't think it will.
Related
Hello,
After stuck flash to ICS, i decide to flash using JB files from sbf.droid-developers.org/umts_spuder/list.php
I used O2 JB and tried "Unknown Carrier" and "Retail British" also.
My XT910 get bit progress now. This device can turn on stable without any self reboot.
But again I can't boot to BP Tool
Now I only able boot to BP HW Diag.
Kindly help me to fix this issue.
idwijayaku said:
Hello,
After stuck flash to ICS, i decide to flash using JB files from sbf.droid-developers.org/umts_spuder/list.php
I used O2 JB and tried "Unknown Carrier" and "Retail British" also.
My XT910 get bit progress now. This device can turn on stable without any self reboot.
But again I can't boot to BP Tool
Now I only able boot to BP HW Diag.
Kindly help me to fix this issue.
Click to expand...
Click to collapse
Install the Boot Menu Manager in playstore. The recovery allows you to boot without BP Tools and BP HW Diag
TheMrcool212 said:
Install the Boot Menu Manager in playstore. The recovery allows you to boot without BP Tools and BP HW Diag
Click to expand...
Click to collapse
I have to root my device first.
But I'm not sure root for XT910 JB is available now.
anyone?
Turn off your phone, remove the sim card and reboot. Then, power off your phone again and insert sim card and reboot.
TheMrcool212 said:
Turn off your phone, remove the sim card and reboot. Then, power off your phone again and insert sim card and reboot.
Click to expand...
Click to collapse
OMG.... you saved my phone.. thanks a lot !!
It works, I can boot in BP Tools now..
Next step is how can I restore my cid and change my baseband without root?
Because upgrade to JB makes my baseband doesn't work in my region.
Also I found usb debugging notification on my phone, but it's not connected in pc.
idwijayaku said:
OMG.... you saved my phone.. thanks a lot !!
It works, I can boot in BP Tools now..
Next step is how can I restore my cid and change my baseband without root?
Because upgrade to JB makes my baseband doesn't work in my region.
Also I found usb debugging notification on my phone, but it's not connected in pc.
Click to expand...
Click to collapse
There are two methods to restore cid. One of the methods need root and other not needed. Since you have no root, download the file ( here ) in your PC. Then extract the file. make sure those files are in a folder. Put your cid.img file into the extracted file. Hold Shift + left click and select "open the command window here".
Turn off your phone. Go to the bootloader (like one you boot to bptools) but this time select the 'AP Fastboot mode' . Connect your phone to your PC. In the terminal, run this line:
Code:
fastboot flash cid cid.img
Make sure no errors when flashing it. And reboot
TheMrcool212 said:
There are two methods to restore cid. One of the methods need root and other not needed. Since you have no root, download the file ( here ) in your PC. Then extract the file. make sure those files are in a folder. Put your cid.img file into the extracted file. Hold Shift + left click and select "open the command window here".
Turn off your phone. Go to the bootloader (like one you boot to bptools) but this time select the 'AP Fastboot mode' . Connect your phone to your PC. In the terminal, run this line:
Code:
fastboot flash cid cid.img
Make sure no errors when flashing it. And reboot
Click to expand...
Click to collapse
Thank you for file
- so i download the file and use file for windows
- i start the command prompt and I got this error:
{
"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"
}
is there some steps that i missed?
and, after yesterday i sucessfully boot to BP Tool, today I can't boot on that mode again, although i did same like before
- power off phone in BP HW Diag
- take out the sim card
- boot again in BP HW Diag
- power off the phone again
- insert simcard
- boot in BP Tool
- now it's just stuck in O2 logo.
Please help me again
Never seen that problem before, but it worked for me. Try to follow these instructions.
1. Download the file ( Here! )
2. Extract the file. You will see a file named allow-mbmloader-flashing-mbm
3. Put the .bin file in the fastboot folder.
4. Put your phone in AP Fastboot mode, connect it to PC
5. Run these commands
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash cid cid.img
All thanks to the therazrguy
TheMrcool212 said:
Never seen that problem before, but it worked for me. Try to follow these instructions.
1. Download the file ( Here! )
2. Extract the file. You will see a file named allow-mbmloader-flashing-mbm
3. Put the .bin file in the fastboot folder.
4. Put your phone in AP Fastboot mode, connect it to PC
5. Run these commands
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash cid cid.img
All thanks to the therazrguy
Click to expand...
Click to collapse
Thank you again..
Those command line executed very well.
Suspend screen is not appear again.
But i got another error
Invalid CG OTV (CG: cdrom): Invalid SP Data
Invalid CG HAB (CG:cdrom, status: 0X0056)
Invalid CG OTV (CG: cdrom)
Please help me how to get my phone back..
idwijayaku said:
Thank you again..
Those command line executed very well.
Suspend screen is not appear again.
But i got another error
Invalid CG OTV (CG: cdrom): Invalid SP Data
Invalid CG HAB (CG:cdrom, status: 0X0056)
Invalid CG OTV (CG: cdrom)
Please help me how to get my phone back..
Click to expand...
Click to collapse
Try to flash the jelly bean fastboot file on RSD Lite. I think the European jelly bean fastboot files are out. But i am not sure.
Sent from my GT-I9300 using xda app-developers app
I flashed with O2 and Retail UK, but this error still exist.
I just erase cid using your command, so I can get back to BP HW Diag again, still can't boot to BP Tools.
idwijayaku said:
I flashed with O2 and Retail UK, but this error still exist.
I just erase cid using your command, so I can get back to BP HW Diag again, still can't boot to BP Tools.
Click to expand...
Click to collapse
You had just erased cid? did i just told you how to restore cid?
But anyway, after few minutes of searching, i have found someone posted how to flash the cdrom partition. It is by TeddyOFLove
I will try. But remember this is all HSD-Pilots work, i only try to make it clear to you.
1) download These fastboot files.rar (clink on text)
2)download retailEU. jellybean OTA
3)Download HSD-pilots UNBRICK.rar
4)UNRAR HSD-pilots UNBRICK.rar from step (3) to any new folder (lets name it UNBRICK)
5) UNRAR Fastboot files:
cdrom_signed
cdt.bin_signed
devtree_signed
ebr_signed
mbr_signed
recovery_signed
radio.img
system_signed
from step (1) to Folder from step (4) we named UNBRICK ONLY extract files i said
6)Connect your device to pc
7)open UNBRICK folder Hold shift and right click on white space -> then press OPEN COMMAND WINDOW HERE
8)flash files from step (5) by writing in the command window you opened:
mfastboot flash cdrom cdrom_signed
mfastboot flash devtree devtree_signed
mfastboot flash ebr ebr_signed
mfastboot flash mbr mbr_signed
mfastboot flash recovery recovery_signed
mfastboot flash radio radio.img
9)with the phone still connected to PC open UNBRICK folder and tun Unbrick.bat.
10) after unbrick.rar flashed press power button once, and immediately hold volume up + volume down and press power again
11) go down to recovery and press volume up
12) when you just follow instructions in bat file. see android picture press volume down and volume up at the same time and wait for radio to install
13) after installation of radio wipe data and catch -> navigate to factory reset and do it
14) Then go to install update from external memory and install retailEU. jellybean OTA that you downloaded (you have to put it to your external SD card)
15) If all is fine it will update, just reboot and its unbricked
Click to expand...
Click to collapse
Also, i forgot that HSD-Pilot posted a thread how to unbrick on the jelly bean OTA, use this thread if its doesnt work.
thanks again for another how to.
i'm downloading the files now there are two question:
1. TeddyOfLove require fastboot files on ICS I guess SPDREM_UMTS_01.6.7.xxx but why tutorial from HSD-Pilot doesn't require this file? which one should i follow
2. Based on above tutorial there are no CID restore? so when I restore it? after all works or before all steps start?
idwijayaku said:
thanks again for another how to.
i'm downloading the files now there are two question:
1. TeddyOfLove require fastboot files on ICS I guess SPDREM_UMTS_01.6.7.xxx but why tutorial from HSD-Pilot doesn't require this file? which one should i follow
2. Based on above tutorial there are no CID restore? so when I restore it? after all works or before all steps start?
Click to expand...
Click to collapse
1. I think you have to use HSD-Pilot's thread. If its doesnt work, use TeddyOfLove's post. Yes, download the fastboot files if you follow TeddyOfLove's post.
2. Use my tutorial how to restore it.
Sent from my GT-I9300 using xda app-developers app
I tried HSD-Pilot's step but stuck after update from external storage.
During "updating BP..." process I got this error
asserted failed: motoflash ("/tmp/bp.img")
now I will try teddyoflove step
I will update you asap.
TheMrcool212 said:
You had just erased cid? did i just told you how to restore cid?
.
Click to expand...
Click to collapse
I just wrote this part.
I have to erase my cid again, coz i can't go to any boot.
Screen just stuck on that error.
TheMrcool212 said:
1. I think you have to use HSD-Pilot's thread. If its doesnt work, use TeddyOfLove's post. Yes, download the fastboot files if you follow TeddyOfLove's post.
2. Use my tutorial how to restore it. Restore it after
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I've done tried with HSD-Pilot but stuck on updating BP process,
then I tried TeddyOfLove's post also:
still stuck on updating bp.. process:
I guess this is why I can't go to BP Tools
Did you restore the cid and flash the OTA?
Sent from my GT-N7100 using xda app-developers app
TheMrcool212 said:
Did you restore the cid and flash the OTA?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
As you said earlier, I must flash the OTA first then restore the cid.
This error appears during flashing the OTA
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.
How to flash a factory image | Return to stock | Unroot your Nexus 6P
Hello Nexus 6P Users!
This tutorial will show you how to reset/unroot/save your Nexus 6P by flashing the Google Factory Images.
{
"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"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC and Linux users: simply follow these instructions:
http://forum.xda-developers.com/showthread.php?t=2638673
Off-topic: installing ADB and Fastboot so easily, what a time to be alive!
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#angler
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already). Only follow step 1 from this thread:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Flashing the factory images
There is more than one way to flash these images. Each give the same results, but the first is for lazy (or smart) users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case first one does not work)
★Extract the image-angler-xxxxxx.zip from the previously extracted folder somewhere easy to access (On C:\images for example. Make it easy to type). You will have the following files:
★In the new folder, from the original archive/folder, extract "bootloader-angler-angler-XX.XX.img" (rename it to bootloader.img) and "radio-angler-angler-XX.XX" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:/images/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/images/radio.img
fastboot reboot-bootloader
fastboot flash system C:/images/system.img
fastboot flash vendor C:/images/vendor.img
fastboot flash userdata C:/images/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/images/boot.img
fastboot flash recovery C:/images/recovery.img
fastboot erase cache
fastboot flash cache C:/images/cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
And now you have a brand new Nexus 6P (software wise, at least). Congratulations!
Credits and Thanks:
@Mr hOaX
Got some fastboot command "updates" from you
@Heisenberg
Really cool root tutorial
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
abaaaabbbb63 said:
Credits and Thanks:
Mr hOaX
Got some fastboot command "updates" from you
Heisenberg
Really cool root tutorial
Click to expand...
Click to collapse
Nice to see you here bro
Good job
This guy's tutorial will really save your nexus for sure
gd6noob said:
err.... Heisenberg's already have a tutorial on how to return to stock... not sure why we need a duplicate posting..
#9 How To Flash The Factory Images (And Return To Stock)
Click to expand...
Click to collapse
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
abaaaabbbb63 said:
I thought that a separate thread would raise its visibility and would be easier to spot for users that do not know their way around XDA that well.
Click to expand...
Click to collapse
Followed the instructions and im getting an error cant find the files
joeyac02 said:
Followed the instructions and im getting an error cant find the files
Click to expand...
Click to collapse
Can you describe what exactly did you do?
At which point did you encounter the error?
When I download the images it doesn't contains Angler-bootloader and Radio.img. It only contains one file with the boot.img, etc... I tried downloading all the 6.0.0 link and it's all the same . I don't understand.
Thank you for the post. Hope I don't need to use it tho. :good:
I cannot make phone calls through the phone app?
I followed directions step by step but every time I get to the dead android guy and hold vol up + pow. I do not get the "stock" recovery where I could choose to data/factory reset, I just get the little dead android guy again.
Any help?
Nice guide
Sent from my Nexus 6P using Tapatalk
From Heisenberg post says that
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have.
Click to expand...
Click to collapse
And I have 64gb of storage. should I wipe or flash?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
You can do both. Just in case, your storage spaces shows reductions after flashing (Like my 64GB variant shows 32 GB), you can fix it by wiping data from stock recovery.
If you're not willing to remove the data on your internal storage, you can skip flashing userdata.img.
tried to go back to stock but stuck on google logo..what to do?
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you flash the the correct vendor.img, corresponding to your factory image?
DJBhardwaj said:
Did you flash the the correct vendor.img, corresponding to your factory image?
Click to expand...
Click to collapse
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
jordy787 said:
nope just the factory image from google..can you send me the link to the vendor img for latest stock build? and do i fastboot flash it? thanks
Click to expand...
Click to collapse
Vendor.img is already included in the factory image. If you used flash-all.bat script, it must have been flashed. What commands did you precisely use to flash the factory image?
cediedc said:
From Heisenberg post says that
And I have 64gb of storage. should I wipe or flash?
Click to expand...
Click to collapse
Don't ever flash it. It has no benefit and only causes problems. If you need to wipe your storage use this command:
Code:
fastboot format userdata
jordy787 said:
tried to go back to stock but stuck on google logo..what to do?
Click to expand...
Click to collapse
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Heisenberg said:
Did you wipe data with TWRP first? That's probably what's causing your problems. Vendor most likely has nothing to do with it.
Click to expand...
Click to collapse
I used the wug tool kit and it worked
Hi all,
I have asked this on the miui forums but no one was unable to assist,
I was updating my phone to the MIUI version that contained the new Android OS, and my stupid cat pulled the cable, causing the phone to unplug during flashing procedure, big no no
Firstly the phone would would just flash red which I believe was EDL mode, so I was able to after several goes reflash the chinese variant of MIUI rom onto the phone.
it would then be stuck on the MI screen, so I reflashed again and it started to proceed with the initial setup
However every couple of seconds the phone would crash, restart, get a bit further, crash and repeat till it finished the initial setup, this is where the device is today
I managed to flash twrp to see if there was anything I could do, I noticed it was complaining that /persist was missing/unable to process, I tried to reflash /persist using the online guides available but all of them ended up as the same result of "could not be flashed to device"
My bootloader is unlocked as confirmed by offical Xiaomi unlocker tool,
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Cexitime said:
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Click to expand...
Click to collapse
Hey there, Have you tried this method:
https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Hoping that it may help you.
Cexitime said:
Hi all,
I have asked this on the miui forums but no one was unable to assist,
I was updating my phone to the MIUI version that contained the new Android OS, and my stupid cat pulled the cable, causing the phone to unplug during flashing procedure, big no no
Firstly the phone would would just flash red which I believe was EDL mode, so I was able to after several goes reflash the chinese variant of MIUI rom onto the phone.
it would then be stuck on the MI screen, so I reflashed again and it started to proceed with the initial setup
However every couple of seconds the phone would crash, restart, get a bit further, crash and repeat till it finished the initial setup, this is where the device is today
I managed to flash twrp to see if there was anything I could do, I noticed it was complaining that /persist was missing/unable to process, I tried to reflash /persist using the online guides available but all of them ended up as the same result of "could not be flashed to device"
My bootloader is unlocked as confirmed by offical Xiaomi unlocker tool,
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Click to expand...
Click to collapse
Try to flash some custom rom through custom recovery and see if it works. I think your device isnt bricked because I've done the same when I realised that clean all and lock was ticked so I just unplug the cable in the middle of the flash process and flash the ROM again. Go to recovery and wipe all Dalvik, system and cache and then flash custom ROM and gapps. After that go and flash official rom through mi flash tool from fastboot.
GabrielScott said:
Hey there, Have you tried this method:
https://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Hoping that it may help you.
Click to expand...
Click to collapse
Hi, I tried the link and got the following;
C:\adb>adb shell
~ # [6nmake_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
open: No such file or directory
~ # [6ne2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.42.9 (28-Dec-2013)
e2fsck: No such file or directory while trying to open /dev/block/platform/msm_sdcc.1/by-name/persist
Possibly non-existent device?
~ # [6n
bpodnar said:
Try to flash some custom rom through custom recovery and see if it works. I think your device isnt bricked because I've done the same when I realised that clean all and lock was ticked so I just unplug the cable in the middle of the flash process and flash the ROM again. Go to recovery and wipe all Dalvik, system and cache and then flash custom ROM and gapps. After that go and flash official rom through mi flash tool from fastboot.
Click to expand...
Click to collapse
I tried to install lineage OS according to their instructions and got this error during installation
{
"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"
}
Cexitime said:
I tried to install lineage OS according to their instructions and got this error during installation
Click to expand...
Click to collapse
Error 7 issue is probably due to corrupted zip.
Redownload the ROM again.
This time, format data or wipe everything then flash.
GabrielScott said:
Error 7 issue is probably due to corrupted zip.
Redownload the ROM again.
This time, format data or wipe everything then flash.
Click to expand...
Click to collapse
I downloaded the rom again and this time it flashed, however the phone just got stuck in a boot loop till it went flat, still have the /persist error in twrp that I cannot fix utilizing the above commands,
I think shes dead jim
Cexitime said:
I downloaded the rom again and this time it flashed, however the phone just got stuck in a boot loop till it went flat, still have the /persist error in twrp that I cannot fix utilizing the above commands,
I think shes dead jim
Click to expand...
Click to collapse
Last Try , did u already tried flashing persist img from official fastboot ROM?
@_ sorry, out of ideas
So you just had corrupted persist partition, and cant mount persist partition right?
Have you tried flash persist.img from fastboot?
fastboot erase persist
fastboot flash persist persist.img
Sent from my Redmi Note 4 using Tapatalk
Someone please share persist.img file, the one present in fastboot file is low in size, & after flashing that file it keeps on rebooting.
I had to flash sensorfix file that comes with coloros to restore it to normal, & again this creates a new problem "this device associated with another mi account".
Hii tired to do that in twrp as well, however when selecting the persist.img the /persist isn't a selectable option in twrp
arshy said:
So you just had corrupted persist partition, and cant mount persist partition right?
Have you tried flash persist.img from fastboot?
fastboot erase persist
fastboot flash persist persist.img
Click to expand...
Click to collapse
Hi,
Tried that as well, it comes up with the error in one of my replies
Try this way:
first go here and download "Redmi Note 4X ( (3GB+32GB) Latest China Developer Version Fastboot File Download";
then follow this guide but only the PART II (the guide is for locked bootloader, but it doesn't matter on our case, because on mido you must have an unlocked bootloader to enter EDL).
The guide will modify some text file to flash only the persist.img, but if need you can flash all the firmware's files (but remember to insert the "persist.img" in the bat file, because it's not present by default). You will got a Chinese language phone (I don't know if English is present) but you can test if everything works and then re-flash a Global ROM or a custom ROM.
The summary of the procedure is flashing the China Developer ROM (including the persist.img) with MiFlash when the phone is in EDL mode (RN4 can be put in EDL mode with this tool but only if bootloader is unlocked).
Let us know if this works for you.
I can help may be.... Read my post .... We can reflash stock ROM with all partitions and stuff(I know how to edl RN4) I believe it will work for sure..
i have tried all the methods both locked as well as unlocked bootloader methods but for me none works. i have no persist file and it wont get flashed with miflash.
Cexitime said:
Hi all,
I have asked this on the miui forums but no one was unable to assist,
I was updating my phone to the MIUI version that contained the new Android OS, and my stupid cat pulled the cable, causing the phone to unplug during flashing procedure, big no no
Firstly the phone would would just flash red which I believe was EDL mode, so I was able to after several goes reflash the chinese variant of MIUI rom onto the phone.
it would then be stuck on the MI screen, so I reflashed again and it started to proceed with the initial setup
However every couple of seconds the phone would crash, restart, get a bit further, crash and repeat till it finished the initial setup, this is where the device is today
I managed to flash twrp to see if there was anything I could do, I noticed it was complaining that /persist was missing/unable to process, I tried to reflash /persist using the online guides available but all of them ended up as the same result of "could not be flashed to device"
My bootloader is unlocked as confirmed by offical Xiaomi unlocker tool,
so I am stuck with a phone that bootloops and has no /persist, is there any hope for this device?
I am located in Australia so sending it to a service centre will not be an easy process if I can even get the seller to do so (dx.com)
Thanks for reading
Click to expand...
Click to collapse
http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz
Flash this file via fastboot, if you are getting reboots.
arshy said:
So you just had corrupted persist partition, and cant mount persist partition right?
Have you tried flash persist.img from fastboot?
fastboot erase persist
fastboot flash persist persist.img
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
t only says C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase persist
erasing 'persist'...
FAILED (remote: Error: This image isn't allow download
)
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash persist persist.i
mg
target reported max download size of 536870912 bytes
sending 'persist' (4716 KB)...
OKAY [ 0.162s]
writing 'persist'...
FAILED (remote: Error: This image isn't allow download
)
finished. total time: 0.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I think that means this isn't working.
BubuXP said:
Try this way:
first go here and download "Redmi Note 4X ( (3GB+32GB) Latest China Developer Version Fastboot File Download";
then follow this guide but only the PART II (the guide is for locked bootloader, but it doesn't matter on our case, because on mido you must have an unlocked bootloader to enter EDL).
The guide will modify some text file to flash only the persist.img, but if need you can flash all the firmware's files (but remember to insert the "persist.img" in the bat file, because it's not present by default). You will got a Chinese language phone (I don't know if English is present) but you can test if everything works and then re-flash a Global ROM or a custom ROM.
The summary of the procedure is flashing the China Developer ROM (including the persist.img) with MiFlash when the phone is in EDL mode (RN4 can be put in EDL mode with this tool but only if bootloader is unlocked).
Let us know if this works for you.
Click to expand...
Click to collapse
Hello. I have a Redmi Note 4 Snapdragon with the Bootloader unlocked because I bought it used and I have an account lock that prevent me to use it (it is like a bricked phone because the vendor doesn't know about the MI account and xiaomi cannot unbind the device from the MI account because I have not the registration email neither invoce of purchase).
Searching a way to avoid the lock of the MI account I am trying to flash persist.img because I read that the data of this account is saved in this partition.
- I downloaded the mido_global_images_8.12.20_20181220.0000.00_7.0_global_3947ba5143.tgz
- I modified the flash_factory.bat in order to add the line 28:
Code:
fastboot %* flash persist %~dp0images\persist.img || @echo "Flash persist error" && exit /B 1
- I modified rawprogram0.xml in order to add the "persist.img" in line
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="persist.img" label="persist" num_partition_sectors="65536" physical_partition_number="0" size_in_KB="32768.0" sparse="true" start_byte_hex="0xf4000000" start_sector="7995392"/>
- I entered in EDL using the test points, flashed with MiFlash20191206 and it says "flashSuccess" (attached is the log of the MIFlash)
But when the new ROM starts and connects to the internet, the MI account lock appears again. Then I have a device that cannot be used when connects to internet.
I have read in some threads that persist partition cannot be flashed in EDL mode with the unlocked Bootloader but it seems that I can do it (not in FastBooot that says explicitly that this partition cannot be flashed).
I have flashed the persist image that comes with the original ROM but I haven't tried with the ones that users upload in order to avoid another conflict of MI Accounts.
I have another Redmi Note 4 working with the unlocked BL, TWRP and LineageOS 16. I tried to make a backup of persist from TWRP in order to flash it in the locked device but it says that the partition uses 0 MB and the persist.ext4.win file has 473 KB that makes me think I am not doing it right.
Please, let me know what you think. Am I in the right way?
Thanks
I had success rooting this device (Moto E6 Surfna) by following the "Boot Image Patching" method here: https://topjohnwu.github.io/Magisk/install.html
mingkee had success with the same method on the G7 https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
Summary:
1. Unlock bootloader, this can help https://forum.xda-developers.com/moto-g7/how-to/guide-unlock-g7-bootloader-t3906858
2. Download the firmware for your variant: https://mirrors.lolinet.com/firmware/moto/surfna/official/
3. From the firmware zip, extract the recovery.img
4. Install the Magisk Manager https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 on the phone
5. Push the recovery.img to the phone
6. From the Magisk Manager, tap "Install" then "Select and Patch a File", find the recovery.img and patch it.
7. Pull the patched img to the PC, Magisk Manager will put in /sdcard/Download/magisk_patched.img
8. Flash the patched img as recovery (fastboot flash recovery magisk_patched.img)
I used the recovery.img instead of the boot.img because the boot.img didn't work for me. Check out the "Magisk in Recovery" section https://topjohnwu.github.io/Magisk/install.html
Start the phone in recovery mode and Magisk will start the phone normally. In the future, the phone will need to boot in recovery mode to start Magisk. A normal boot will cause Magisk to deactivate.
Proceed at your own risk. I give no guarantees, implied or otherwise.
Also, I might've missed a step here or there.
Good luck, happy rooting.
Makes me wonder if you can flash the magisk-patched recovery to the bootloader partition. On other devices I've flashed boot to recovery so it would always boot normally, kids would sometimes trigger it otherwise.
Nice work @mer2017. These recent Moto devices -- some of them at least -- have proven difficult to root. The Moto G7 Play is among those devices that, despite adamant efforts, does not presently have a viable rooting method. Methods which have been confirmed successful for other Moto G7 variants are not effective on the G7 Play, despite the fact that an unofficial and seemingly stable TWRP build has been compiled as well.
I have been reading the Magisk support topics you referenced for recovery image patching versus boot image patching. The answer is most likely some utilization of a patched recovery image, perhaps somehow flashed to the /boot partition?? This is where things get muddled for me, as the G7 Play -- being an A/B partition index device -- is devoid of an actual /recovery partition. Anyway, OP, I apologize in advance for my somewhat off-topic post. I realize this thread is intended for Moto E6 subject matter regarding root. When I read your thread, a light bulb sort of illuminated for me with respect to a working root method for my device. I will provide links to a couple of the tentative root threads for the Moto G7 Play. If you could perhaps give some input based on your experience, it would be a huge help to us. Again, I humbly beg your pardon for posting about a different device, and nice work on the Moto E6. :good:
https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page19
https://forum.xda-developers.com/g7-play/help/successfully-rooted-moto-g7-play-t3930747/page4
my verizon moto e6 (Your device does not qualify for bootloader unlocking) tells me when I want to release the bootloader
Just rooted my tmo e6 using above. :good::silly:
Almost?
I was able to get the root to stick by after a few hours I plugged my phone in and it randomly turned off. I tried to boot it back up and it booted into bootloader. I tried to restart it and it still kept going to bootloader. I then used the fastboot reboot command and it rebooted and OS popped up. However of course. Magisk was deactivated. Went back and tried to boot to recovery and the flash had been erased and it booted me into the regular recovery mode. Also with no magisk. What could I have done wrong.
Code:
[email protected]:~/Downloads/adb - platform tools v28.0.0# fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16331 KB)...
OKAY [ 0.530s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.279s]
finished. total time: 0.809s
Now this is the message I get when I flash it still will boot into OS with root enabled.
after about 5 hours it did the continous fastboot boot up and the log said something like
"fastboot reason: reboot mode set to fastboot"
I did oem fb_mode_clear to no avail and not sure why it changed regardless.
Dead to the touch
I followed the guide linked and attempted to root by patching the boot.img with magisk. My device boots, but touch screen appears to be shot. I've reflashed the boot.img file without the patch, and factory reset several times, unfortunately my device's touch functionality seems to be gone... Any suggestions on how I can fix this?
sasuke33 said:
I followed the guide linked and attempted to root by patching the boot.img with magisk. My device boots, but touch screen appears to be shot. I've reflashed the boot.img file without the patch, and factory reset several times, unfortunately my device's touch functionality seems to be gone... Any suggestions on how I can fix this?
Click to expand...
Click to collapse
If you're using a boot image you downloaded from somewhere else rather than the one from your own device, you might be out of luck. You can probably grab the proper stock firmware through Moto Smart Assistant on PC and reflash, but that might wipe your data.
The original post is a bit misleading, as Magisk can't be installed into the boot partition of the e6 due to the system-as-root setup. You'll need to install it in the recovery partition - re-read the guide and make sure you're aware of the caveats before proceeding.
FEGuy said:
If you're using a boot image you downloaded from somewhere else rather than the one from your own device, you might be out of luck. You can probably grab the proper stock firmware through Moto Smart Assistant on PC and reflash, but that might wipe your data.
The original post is a bit misleading, as Magisk can't be installed into the boot partition of the e6 due to the system-as-root setup. You'll need to install it in the recovery partition - re-read the guide and make sure you're aware of the caveats before proceeding.
Click to expand...
Click to collapse
Thanks for responding. I actually figured out the issue this afternoon, but didn't get a chance to edit my post yet. I needed to flash the vendor.img file that came with the boot.img file. Once I did that, it restored touch capabilities. And yes, I ended up patching and flashing the recovery.img file to flash. While I was able to patch and flash the boot.img file it didn't do anything as you said.
I have root as long as I boot to recovery, so all is round in my world. It'll be even more awesome if it ever gets a twrp release, but for now this root method serves my needs ?
Again thanks for responding to my post, and I hope my little anecdote can help someone from making my mistakes or help fix the issue.
i got to step 8
but when i reboot normally, on root.
When i reboot to reocovery , the E6 displays android pic with No command
I thought no command was an error at first, it's just how the android system is. It is saying 'no command' because you have not inserted a command. If you hold down power button and volume up it should go into recovery options.
I was able to root my phone, using a similar method as the OP. Magisk offers a good guide actually. The reason it may not be working for other people is when you make the image make sure you include recovery option in magisk options. Otherwise it's not going to work.
Downside of this is you have to boot into recovery mode all the time. But at least its rooted.
getprop ro.build.ab_update returns nothing!
I unlocked the bootloader, and am now trying to install magisk manager.
Attached is the return of the commands it wants me to check. Since its not returning true do I just assume that its false?
{
"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"
}
awesome, i have root. Here's my steps
download LMSA Tool https://www.motorola.com/us/lenovo-motorola-smart-assistant
Install, Go to rescue, download firmware, flash the phone.
LMSA downloads the firmware to C:\ProgramData\LMSA\Download\RomFiles
SURFNA_PPBS29.73_81_5_3_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
In that folder, save a copy of recovery.img
Then do these steps, credit to OP.
Summary:
1. Unlock bootloader, this can help https://forum.xda-developers.com/mot...oader-t3906858
2 Install the Magisk Manager https://forum.xda-developers.com/app...mless-t3473445 on the phone
3. Push the recovery.img to the phone
4. Open Magisk Manager, tap Advance Settings. Tap Recovery mode
5. Magisk Manager, tap the first "Install" then "Select and Patch a File", find the recovery.img and patch it.
6. Pull the patched img to the PC, Magisk Manager will put in /sdcard/Download/magisk_patched.img
7. Put phone in fastboot
8. Flash the patched img as recovery (fastboot flash recovery magisk_patched.img)
9. use phone buttons to Boot to recovery mode, it will say "Signature missing or corrupted"
10. Wait, Let phone boot to OS
11. OS loaded with Root
Exceptions:
•If I let the phone boot up just once normally, i loose root. I have to do setp 7,8,9,10 again.
---
Recovery mode instructions from motorola site
1. With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on. [Bootloader mode]
2. Press the Volume Down button until the flag says RECOVERY MODE.
3. Press the Power button to restart into Recovery mode.
4. You'll see an image of an Android robot with a red triangle. [and No command]
5. While holding down the Power button, press the Volume Up button. [you'll see the recovery menu]
If you need to reboot the phone for any reason, use Reboot to recovery option in Magisk. Or any other third party root app which provides option to reboot to recovery.
Hey, Guys. Just unlocked the bootloader. Need help choosing which firmware. I got the phone from this company, Visible, which Google tells me is by Verizon. However, the VZW directory files don't match my model or build number.
From the phone settings:
Model number: XT2005-5
Build number: PPBS29.73-81-5-3
USC, RETUS, and CC directories have files that match these numbers. They all have the same file size too. Which one should I use if I'm on T-mobile?
EDIT: Thanks, fcohen! RETUS worked fine for me as well.
Charuto said:
Hey, Guys. Just unlocked the bootloader. Need help choosing which firmware. I got the phone from this company, Visible, which Google tells me is by Verizon. However, the VZW directory files don't match my model or build number.
From the phone settings:
Model number: XT2005-5
Build number: PPBS29.73-81-5-3
USC, RETUS, and CC directories have files that match these numbers. They all have the same file size too. Which one should I use if I'm on T-mobile?
Click to expand...
Click to collapse
RETUS worked fine on mine.
mer2017 said:
I had success rooting this device (Moto E6 Surfna) by following the "Boot Image Patching" method here: https://topjohnwu.github.io/Magisk/install.html
mingkee had success with the same method on the G7 https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084
Summary:
1. Unlock bootloader, this can help https://forum.xda-developers.com/moto-g7/how-to/guide-unlock-g7-bootloader-t3906858
2. Download the firmware for your variant: https://mirrors.lolinet.com/firmware/moto/surfna/official/
3. From the firmware zip, extract the recovery.img
4. Install the Magisk Manager https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 on the phone
5. Push the recovery.img to the phone
6. From the Magisk Manager, tap "Install" then "Select and Patch a File", find the recovery.img and patch it.
7. Pull the patched img to the PC, Magisk Manager will put in /sdcard/Download/magisk_patched.img
8. Flash the patched img as recovery (fastboot flash recovery magisk_patched.img)
I used the recovery.img instead of the boot.img because the boot.img didn't work for me. Check out the "Magisk in Recovery" section https://topjohnwu.github.io/Magisk/install.html
Start the phone in recovery mode and Magisk will start the phone normally. In the future, the phone will need to boot in recovery mode to start Magisk. A normal boot will cause Magisk to deactivate.
Proceed at your own risk. I give no guarantees, implied or otherwise.
Also, I might've missed a step here or there.
Good luck, happy rooting.
Click to expand...
Click to collapse
When I try to flash I get "Bad Key". I can't flash no-verity-opt-encrypt without TWRP though, so I don't know what to do.
I messed up. Rebooted regularly and lost root. Can't seem to get root back. Followed the directions again starting with unlocking the bootloader. Read later that wasn't necessary. Is it possible I corrupted something by trying to unlock the bootloader more than once?
In any case, I'm flashing the magisk_patched.img and rebooting to recovery. From there it says "Signature missing or corrupted" and just bootloops this error message. I let this go on for over half an hour and nothing changed. Taking out the battery and booting normally gives the same error message and bootloop.
I can start normally again if I start in bootloader mode and select the start option--this gives me the normal phone without root. Below I've included more notes which may have some clues to what I did wrong.
Here is the result when I flash recovery:
Sending 'recovery' (16335 KB) OKAY [ 0.577s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.316s]
Finished. Total time: 0.904s
Here's the text when I start bootloader mode:
AP Fastboot Flash Mode (Secure)
BL:MBM-2.1-surfna_retail-eed5d2a-200205
Baseband: M8940_32.127.01.130.01R SURF_NA_CA_CUST
Product/Variant: surfna XT2005-5 16B PVT
Serial Number: ZF6522C3LK
CPU: MSM8940
eMMC 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
DRAM: 2GB SKYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=1F
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK (Charging)
flashing_unlocked
Transfer Mode: USB Connected
Charuto said:
I messed up. Rebooted regularly and lost root. Can't seem to get root back. Followed the directions again starting with unlocking the bootloader. Read later that wasn't necessary. Is it possible I corrupted something by trying to unlock the bootloader more than once?
In any case, I'm flashing the magisk_patched.img and rebooting to recovery. From there it says "Signature missing or corrupted" and just bootloops this error message. I let this go on for over half an hour and nothing changed. Taking out the battery and booting normally gives the same error message and bootloop.
I can start normally again if I start in bootloader mode and select the start option--this gives me the normal phone without root. Below I've included more notes which may have some clues to what I did wrong.
Here is the result when I flash recovery:
Sending 'recovery' (16335 KB) OKAY [ 0.577s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.316s]
Finished. Total time: 0.904s
Here's the text when I start bootloader mode:
AP Fastboot Flash Mode (Secure)
BL:MBM-2.1-surfna_retail-eed5d2a-200205
Baseband: M8940_32.127.01.130.01R SURF_NA_CA_CUST
Product/Variant: surfna XT2005-5 16B PVT
Serial Number: ZF6522C3LK
CPU: MSM8940
eMMC 16GB SKHYNIX HAG4a2 RV=08 PV=A5 FV=00000000000000A5
DRAM: 2GB SKYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=1F
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK (Charging)
flashing_unlocked
Transfer Mode: USB Connected
Click to expand...
Click to collapse
Download the stock firmware for your e6 model and flash it via ADB.
EnokiPPT said:
Download the stock firmware for your e6 model and flash it via ADB.
Click to expand...
Click to collapse
I was hoping I wouldn't have to go all the way back to stock I'll report back when I get it done. Thanks.