Related
First, take your own risk!
Be sure you knwo what you are doing now and familiar with fastboot and your Xoom.
I am not responsible for anything.
The following founding are just proved to be work on my Xoom and I guarantee nothing.
===========================================
Rom Source:
Obtained from this thread
[!!Thanks changguangyu for his (and his fd's) kind sharing!!]
http://forum.xda-developers.com/showthread.php?p=21096478
Download the leaked rom
Extract the sbf using "MotoAndroidDepacker v1.3"
CG57.smg rename to recovery.img
CG58.smg rename to boot.img
CG59.smg rename to system.img
Issue the following command:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Done.
Tried on my own Hong Kong Wifi version Xoom(MZ604).
Run smoothly.
can this be flash to canadian xoom ?
Probably can but I would probably wait for eos version with the good bits taken out....
Sent from my HTC Desire using xda premium
thanks ...good to go
In case somebody wondering where to find MotoAndroidDepacker
http://www.mediafire.com/?pk0gb8tgxg4uecg
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
ojdon said:
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
Click to expand...
Click to collapse
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Firefox OS in Galaxy Nexus, I want to take a look! Keep us up to date man!
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Ah didn't know this thread had replies so sorry for a bit of a bump. I was kind of after directions on how to create a flashable zip? It's just that I was aiming to avoid end users from using adb and fastboot. Do you know how to create a flashable zip instead?
Thanks for the guidance!
I was following Heisenberg's guide "How To Flash The Factory Images (And Return To Stock)" and it said to extract the factory images but I always get an error from Winrar and 7zip. I downloaded many times from google page.
Anyone know whats up?
Also, if I just do:
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot format userdata
and leave the bootloader and radio alone, it should put me back to near stock erasing everything so its like from factory state? TWRP doesnt touch some partition even when formatting...
Just download the facory image use 7zip to extract it put everything extracted in your adb fastboot file and in adb type flash-all.bat it will take you back to stock but your boatloader will still be unlocked so just re flash twrp
Must be something wrong with IDM.. downloaded through chrome and it extracted fine...
I use the new Windows 10 browser so I don't know I believe I extracted the tar then theirs a white folder I had to extract a second time to get the multiple files needed also I opened the file in 7zip to make sure it was right
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
try http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
then flash android 6.0 maybe trupure 2.9 and then get the modem from trupure and flash it
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
goldentequila said:
Hi,
I was flashing many different ROMs in attempt to find a solution to something I was trying to accomplish. In the end, I gave up and decided to go back to stock. I used this instruction to revert back to stock: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I followed the instruction under Android 6.0, MPH24.49-18-3 FIRMWARE that said to do:
fastboot flash partition gpt.bin
fastboot reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
I remember when flashing system, there was an invalid sparse header message, but it kept going, so I let it. After that I rebooted bootloader and flashed TWRP again. I then rebooted bootloader once more and entered TWRP. There, I proceeded normally. But then I realized that there was something wrong when I couldn't do the full wipe. I went to look in the mount setting and saw that TWRP was not able to mount internal. The internal was also listed as 0MB. I'm guessing that I need to re-partition/format the internal (or I don't know what I'm talking about lol). Either way, I'm now unable to flash a ROM. Can someone please help me?
Thank you in advance.
Click to expand...
Click to collapse
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
acejavelin said:
Find 18-4 firmware, it's newer anyway... the sparse chunk size error is the problem, the system.img file in that firmware file is too large for the phone to flash via fastboot (thus, it probably isn't an official image, or it's an image for the engineering flash tool, not fastboot). The proper image file with have 6-11 sparce chunks you need to flash individually.
Click to expand...
Click to collapse
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
goldentequila said:
I think i made it worse lol... Because I was getting many errors (random reboots), I decided to do a full wipe to install a ROM fresh. When wiping in TWRP, I accidentally wiped "internal" too. I'm guessing that I need to do something to correct this before I can flash 18-4 firmware. Please let me know if you know what I need to do. Thank you.
Click to expand...
Click to collapse
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Sagar_1401 said:
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
---------- Post added at 04:06 PM ---------- Previous post was at 04:00 PM ----------
Its incomplete comanda... Where is the main spunk files??
These are the main firmware files
Check all the files that u have flashed
Click to expand...
Click to collapse
The instruction in that post said to not worry about the sparse error message, so I went with it. This is what the post said.
"You may notice a "sparse header error" when flashing at the beginning. Don't worry about it, all is well. The current AutoFlashFirmware.bat file doesn't work with this Firmware file. Flash the files manually!"
Also, i posted above too, but I just accidentally wiped internal via TWRP too. Do you know what I need to do now in order to get my phone back? I've found solutions for other phones regarding this situation, but I haven't come across one for Moto X Pure. This is what happens when you work on your phone all day long and some more into late night lol...
acejavelin said:
TWRP shouldn't be a part of this, nor should it matter whats on your internal storage, this is all done with fastboot.
Factory reset in stock recovery, reboot to bootloader, then flash the complete image with fastboot.
Click to expand...
Click to collapse
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
goldentequila said:
Thank you for your ongoing support. I just want to make sure I'm doing this right. I found this firmware: http://forum.xda-developers.com/showpost.php?p=69103575&postcount=243
Could you please tell me if you think that's what I should flash?
Also, if you don't mind, will you please share exact fastboot commands/process? I just don't want to make any more mistakes and make things worse. I apologize for being needy.
Click to expand...
Click to collapse
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
acejavelin said:
Yes, look in my signature and use the non-relock option: http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
goldentequila said:
Thank you very much for that. You mentioned that I would need to factory reset in stock recovery first. Do I just fastboot flash a stock recovery from the firmware zip file from 18-4, boot into its recovery, reset, and then follow the instruction above?
Click to expand...
Click to collapse
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Oh ok. Thanks again. I'll report back if I succeed (or not) later today. I appreciate your help.
acejavelin said:
Boot, flash, whatever... It is best to do a factory reset in the default recovery first, but it isn't essential.
Click to expand...
Click to collapse
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
goldentequila said:
Thank you so much for your help. It worked perfectly. Now I have my phone back :victory:
Click to expand...
Click to collapse
Glad I could help. You're welcome.
Lol it was sparsechunk i just got confused with it and said spunk??
I have been trying to root my phone. I have been have problems with twrp. I have installed twrp through both the moto g5 plus toolkit and manually(command prompt and adb/adb fastboobt). I have had several problems with twrp. Firstly I can't seem to install it without wiping everything off my phone. Secondly twrp won't install stock rom, flash zip files and sometimes img files. Thirdly It keeps failing to mount data.
Every time I install TWRP I have to use the moto g5 plus toolkit flash stock rom so I can use my phone.
After flashing twrp I reboot to recovery mode, go to wipe, then "swipe to factory reset." I the go to reboot or reboot to recovery. Most of the installation instruction regarding twrp say to do this. The problem is I have to install/re-install stock rom in my phone via the toolkit because there is nothing on my phone but a twrp after I swipe factory reset an I can't get twrp to install stock rom.
Since I can't get twrp to install stock rom from a zip file I have to use the moto g5 plus toolkit which wipes twrp and flashes the stock rom.
After flashing stock rom I tried again and was prompted for a password. I don't have password and there was something about decryption on the screen. I hit cancel went to Wipe then Format Data and typed yes at the prompt. I went to reboot hit recovery(reboot to recovery). My phone was wiped clean and I had nothing but twrp on it again. I tried install stock rom off my sd but I got allot of errors( can't mount data, ect...) I tried to fix this by using twrp to flash an install img of the latest version of twrp. This did not fix the problem.
I can't use twrp to install stock rom, or zips nor can I install twrp without having to flash stock rom and erase twrp from my phone because installing twrp removes everything and renders my phone useless. Every time I install twrp I'm left with nothing but twrp on my phone. Everything is wiped there is nothing there but twrp.
Could someone please tell me how to install twrp without wiping my phone completely and how to get around the problems I have been having. I have tried several different things but I can't fix the mount error nor can I get twrp to install stock rom. I just can't figure this out.
I have attached several screenshot below. If you are willing to help please take a look at them.
first of all stop using that toolkit. if you were flashing stock rom the right way you wouldnt be replacing recovery.
follow these steps PRECICELY
1. download the actual stock xml.zip and extract it
2. inside the folder make a txtfile called flash rom and rename it to flashrom.bat
2a. right click and select edit, paste this into notepad ans save it (as a .bat --important)
Code:
@echo off
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery twrp.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot flash recovery twrp.img
mfastboot oem fb_mode_clear
pause
mfastboot reboot
3. https://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280 download this and extract all files into where the stock xml.zip is extracted
4. place the twrp youre trying to use (should be the 64bit one from the 64bit thread) in the place you extracted the xml.zip named twrp.img
5. double click the batch file (flash rom.bat) and let it finish (ignore any errors about signature verification and/or corrupt image). when the flash is done it will say "press any key to continue" once you press a key it will reboot your phone, MAKE SURE YOU ARE HOLDING VOLUME DOWN WHILE YOUR PHONE REBOOTS FOR THE FIRST TIME AFTER THE FLASH
6. at this point you WILL have twrp, AND STOCK ROM. THIS IS A PROBLEM. stock rom will replace twrp at first boot, heres how to solve that, first by decrypting data:
6A. wipe cahce SPECIFICALLY by going to wipe, selecting advanced wipe, check cache, and then tap repair or change file system. then tap change file system then ext4 and swipe to apply
6B go back to twrp's main menu and tap reboot>recovery
6C. once back in recovery wipe data SPECIFICALLY by going to wipe, selecting advanced wipe, check data, and then tap repair or change file system. then tap change file system then f2fs and swipe to apply; reboot to recovery again
7. at this point you are running stock rom, decrypted, and have twrp BUT STOCK ROM WILL STILL REPLACE TWRP IF YOU BOOT, the easiest way to do this is by flashing magisk.
thats it, you should be at stock rooted decrypted with magisk and twrp.
8. come back if that doesnt work. but it should, i literally did the whole process while writing this to make sure i didnt steer you in the wrong direction
Ae3NerdGod said:
2. make a txtfile inside the folder called flash rom and rename it to flashrom.bat
Click to expand...
Click to collapse
The stock rom I downloaded doesn't have a folder call flash rom in it. Is the folder you extracted the Stock Rom called flash rom or should there be a folder called flash rom be in my extracted stock rom folder.
place the twrp youre trying to use (should be the 64bit one from the 64bit thread) in the place you extracted the xml.zip named twrp.img
Click to expand...
Click to collapse
I don't have an xml.zip name twrp.img. I have an image file.(img) not a zip name twrp.img. Did you mean place the twrp image file into the extracted xml.zip.
Would it be easier to place the replace the recovery.img in the extracted xml.zip with the twrp.img and then rename the twrp.img recovery(basicaly replace the recovery.img in the zip with twrp).
no, name the txtfile flash rom, i see the ambiguity though. ill reword it:
inside the folder make a txtfile called flash rom and rename it to flashrom.bat
Click to expand...
Click to collapse
also i meant to name the twrp image file you are using to "twrp.img" and drop it in the folder that contains all the files youve extracted from the xml.zip
and no, it wouldnt be easier because the batch file i wrote flashes "twrp.img" to recovery
attached is roughly what your xml.zip directory should look like (ive deleted a couple unneeded files you do not have to also)
I did everything correctly however when I run the batch file(flashrom.bat) the command prompt displays <waiting for device> and nothing happens.
I have developer setting enabled and usb debugging and my boot loader is unlocked(oem unlocking enabled). I have all the correct drivers for my phone and adb installed on my computer. I do not know why it cannot detect my phone.
:|
Why make it difficult and act like a ****. There no reason to make a .bat file or removing anything. Keep it simple FFS.
This >>> "mirrors . lolinet.com /firmware /moto /potter /official /RETAIL /POTTER_RETAIL_ 7.0_NPN25.137-92 _cid50_subsidy- DEFAULT_regulatory-DEFAULT_CFC .xml .zip" is the Nov 1st firmware for retus, assuming you have that. Extract "mega . nz / #!dqwE1ZJT!OA9N1pxNnDAs9UVkeiVKoVIkvSrZQNWUyKvtORB3" to your desktop for easy access, they are standalone adb/fastboot files. Now take the firmware and extract that into the folder with the adb/fastboot files. Press Shift+Right-click in the folder and choose "open command window here." Make sure you're phone is connected to your PC in bootloader mode. Run "adb shell" and let adb load. Then run "fastboot devices" to assure your device is being discovered. Now you can start manually entering or copy+pastaing the commands to install the firmware one line at a time after the previous command finishes. If you get an error after the "fastboot reboot" reboot, turn your phone off and on again. It should boot up just fine.
EXTREMELY sorry for breaking up the links. I'm not a huge poster and XDA only allows links after 10 posts. so just rebuild the links with h t t p s : / / ahead of them. Stupid rules.
I literally just did this myself because I'm unlocked with a custom kernal, so I do OEM updates manually. It's a slightly tedious task but you can see that everything is installs properly.
If you're not on retus, my time isn't in vein, we can find get the firmware for your device. Here's the commands: Some might say parts are unnecessary, but when you're not sure what's what, it's best to stick with the normal commands.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
ALSO: Install twrp after you've booted up once, not with the firmware. To make it simple drop the twrp.img into its own folder with the adb/fastboot files, run command prompt with the folder the same way you did before and enter these commands:
adb shell
fastboot devices
fastboot flash recovery twrp.img
fastboot reboot recovery
If theres's s password when twrp loads, cancel writing and wipe your data only. Then reboot back into TWRP again before rebooting the system.
Hope this helps and goes smooth for you.
User0666 said:
Extract "mega. nz/#!dqwE1ZJT!OA9N1pxNnDAs9UVkeiVKoVIkvSrZQNWUyKvtORB3"
Click to expand...
Click to collapse
When I go to the above site I get a message asking for a Decryption Key. I don't know what the decryption key is. You a said that the download was a standalone add/fastboot package. Is the stand alone files you were referring to the same as the googles standalone platform-tools for Android.
Also my moto g5 plus is on retus but it is currently running on Potter NPN 25.137-35. I am going to assume that firmware you said to use(Potter NPN 25.137-92) will work.
Ae3NerdGod said:
first of all stop using that toolkit. if you were flashing stock rom the right way you wouldnt be replacing recovery.
follow these steps PRECICELY
1. download the actual stock xml.zip and extract it
2. inside the folder make a txtfile called flash rom and rename it to flashrom.bat
2a. right click and select edit, paste this into notepad ans save it (as a .bat --important)
Code:
@echo off
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash boot boot.img
mfastboot flash recovery twrp.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot flash recovery twrp.img
mfastboot oem fb_mode_clear
pause
mfastboot reboot
3. https://forum.xda-developers.com/attachment.php?attachmentid=2427667&d=1385958280 download this and extract all files into where the stock xml.zip is extracted
4. place the twrp youre trying to use (should be the 64bit one from the 64bit thread) in the place you extracted the xml.zip named twrp.img
5. double click the batch file (flash rom.bat) and let it finish (ignore any errors about signature verification and/or corrupt image). when the flash is done it will say "press any key to continue" once you press a key it will reboot your phone, MAKE SURE YOU ARE HOLDING VOLUME DOWN WHILE YOUR PHONE REBOOTS FOR THE FIRST TIME AFTER THE FLASH
6. at this point you WILL have twrp, AND STOCK ROM. THIS IS A PROBLEM. stock rom will replace twrp at first boot, heres how to solve that, first by decrypting data:
6A. wipe cahce SPECIFICALLY by going to wipe, selecting advanced wipe, check cache, and then tap repair or change file system. then tap change file system then ext4 and swipe to apply
6B go back to twrp's main menu and tap reboot>recovery
6C. once back in recovery wipe data SPECIFICALLY by going to wipe, selecting advanced wipe, check data, and then tap repair or change file system. then tap change file system then f2fs and swipe to apply; reboot to recovery again
7. at this point you are running stock rom, decrypted, and have twrp BUT STOCK ROM WILL STILL REPLACE TWRP IF YOU BOOT, the easiest way to do this is by flashing magisk.
thats it, you should be at stock rooted decrypted with magisk and twrp.
8. come back if that doesnt work. but it should, i literally did the whole process while writing this to make sure i didnt steer you in the wrong direction
Click to expand...
Click to collapse
I'm in a similar position... how ever I have no issue mounting my phone. I follow your steps to the T and I end up with my phone failing to load the operating system....Can you please let me know what I can do? I'm on the XT1687. If I try to flash other roms I get a TWRP error 255...
---------- Post added at 12:02 PM ---------- Previous post was at 11:49 AM ----------
bboygmoney said:
I'm in a similar position... how ever I have no issue mounting my phone. I follow your steps to the T and I end up with my phone failing to load the operating system....Can you please let me know what I can do? I'm on the XT1687. If I try to flash other roms I get a TWRP error 255...
Click to expand...
Click to collapse
OMG If you were here I'd kiss you!!!! Fixed. Had to wipe system then I believe i had the wrong firmware....Thank you soo!!!!!!!!
I followed the instructions, but I can't boot to anything except TWRP. No matter what I select in the reboot menu, the phone reboots to TWRP.
salsolomon said:
I followed the instructions, but I can't boot to anything except TWRP. No matter what I select in the reboot menu, the phone reboots to TWRP.
Click to expand...
Click to collapse
Open up adb command window and type these three commands,
Code:
adb devices
adb shell
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Then reboot.