I got a bootloop after whiping the cache, now I'm trying to fix it by following a tutorial, i downloaded the firmware and I'm flashing it with fastboot, here's the log:
Code:
C:\Users\Hellix\Desktop\FlashTools>fastboot devices
F7AZFG03Y479 fastboot
C:\Users\Hellix\Desktop\FlashTools>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.635s]
writing 'fastboot'...
OKAY [ 0.614s]
finished. total time: 1.250s
C:\Users\Hellix\Desktop\FlashTools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.537s]
writing 'recovery'...
OKAY [ 0.600s]
finished. total time: 1.137s
C:\Users\Hellix\Desktop\FlashTools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.600s]
finished. total time: 1.133s
C:\Users\Hellix\Desktop\FlashTools>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
Why it is taking so much time(almost one hour) to erase the system? Is it normal? What should I do?
Please answer fast, I really really need help
Let it, it can take 30-1hr
It can excruciatingly slow process
Sent from my Nexus 7 using Tapatalk
I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3
lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s
lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.
Hi all!
I'm not so called an "expert" on android. (I work normally on Linux ) so, my *final* goal is to install a custom rom on Google Pixel XL (marlin).
For the moment i'm trying to install the official google 8.1.0 (OPM1.171019.016, Feb 2018).
I carefully followed these 4 links:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
https://developers.google.com/android/images#marlin
https://forum.xda-developers.com/pi...stock-soft-t3494478/post69476498#post69476498
I unlocked and rooted the "marlin" with no problems.
I installed TWRP (twrp-3.2.1-0-marlin): it works but seems do not persist and every time i want to use it i have to reinstall via fastboot (strange... what i missed?).
This is the guide followed: https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-unlock-root-flash-pixel-xl-t3507886
I downloaded the official rom google 8.1.0 (OPM1.171019.016, Feb 2018) following these guides:
https://forum.xda-developers.com/pixel-xl/development/rom-pixeldust-marlin-t3581750
https://developers.google.com/android/images#marlin
https://forum.xda-developers.com/pi...stock-soft-t3494478/post69476498#post69476498
With flash-all-sh and OPM1.171019.016, Feb 2018 give me this error " fastboot too old " ( adb version revision 1:7.0.0+r33-2 )
If i write into shell this procedure at a certain point all stops and an error appears:
.......
sending 'boota' (30149 KB)...
OKAY [ 1.391s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist) <----this
finished. total time: 1.801s
Please, what i did wrong?
how to recover this error?
how to make persistent TWRP?
Anyway, is it possible that the 8.1.0 version is too new for my configuration?
Thanks a lot for any advice!
Lele
Log
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (30149 KB)...
OKAY [ 1.404s]
writing 'boot_a'...
OKAY [ 0.695s]
finished. total time: 2.100s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (30149 KB)...
OKAY [ 1.381s]
writing 'boot_b'...
OKAY [ 0.694s]
finished. total time: 2.076s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash bootloader bootloader-marlin-8996-012001-1711291800.img
target reported max download size of 536870912 bytes
sending 'bootloadera' (32248 KB)...
OKAY [ 1.505s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 15.811s]
finished. total time: 17.317s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.145s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot flash radio radio-marlin-8996-130091-1710201747.img
target reported max download size of 536870912 bytes
sending 'radioa' (57320 KB)...
OKAY [ 2.613s]
writing 'radioa'...
OKAY [ 1.053s]
finished. total time: 3.666s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.145s
[email protected]:/home/lele/Documenti/G Pixel XL/marlin-opm1.171019.016# fastboot -w update image-marlin-opm1.171019.016.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1711291800
Baseband Version.....: 8996-130091-1710201747
Serial Number........: HT69H0207206
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boota' (30149 KB)...
OKAY [ 1.391s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.801s
UPDATE:
At the moment it's working with Android 7.1.2..... But i can't install Android 8.1...
Someone can help me?
bye
lele
Chancellor said:
UPDATE:
At the moment it's working with Android 7.1.2..... But i can't install Android 8.1...
Someone can help me?
bye
lele
Click to expand...
Click to collapse
Make sure you have the latest fastboot and ADB.
To get TWRP permanently, you have to fastboot boot the twrp.img, booting into a temporary TWRP, then flash the twrp.zip.
borxnx said:
Make sure you have the latest fastboot and ADB.
Click to expand...
Click to collapse
adb version revision 1:7.0.0+r33-2 it's the latest version?
To get TWRP permanently, you have to fastboot boot the twrp.img, booting into a temporary TWRP, then flash the twrp.zip.
Click to expand...
Click to collapse
ok i will do it
Thank you
Here is a link to the latest ADB and fastboot tools, which is what I've been using without issue on my Pixel XL on 8.1
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
Sent from my Pixel XL using Tapatalk
Hi There.
After you installed fastboot and adb on linux (I installed adbLink for my aftv from https://www.jocala.com/ and that brings the necessary files, too. It creates a directory called adbfiles, where you can use ./adb and ./fastboot devices - worked for me), you can boot into recovery and install the 8.1.0 version for the pixel from here:
https://developers.google.com/android/ota -- you need marlin and 8.1.0 (OPM1.171019.016, Feb 2018). mv the image to the directory with the adbfiles. I find this way the easiest.
The update can easily be installed if you boot into fastboot and there chose apply update from adb and then follow the instructions on your mobile or steps 2 - 8 from the download page.
That is to update your firmware to 8.1.0 - twrp install comes after that.
OK friend, i will try !!! Thank you
borxnx said:
Here is a link to the latest ADB and fastboot tools, which is what I've been using without issue on my Pixel XL on 8.1
https://www.androidpolice.com/2017/...ble-without-full-sdk-android-studio-download/
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Hi, guys!
I just found XDA on internet search and hope you guys help me
I have a Z2Force and it don't turns on unless the USB are connected on charge or PC. When I connect the cable, the charge icon display appears but stays on an infinite loop and does not show the charge percentage.
When I try to turn on the phone (with charge connected), it goes into infinite loop on Motorola logo.
I can get into the fastboot menu pressing power + vol - , but only with USB connected. There on that screen, it says "Power OK".
I tried to flash stock rom using Minimal ADB and fastboot, I got the ROM on "lolinet dot com" (I can't post links, 'cause I'm new user). I downloaded on nash/official/RETBR (my Z2F is from Brasil). I used this commands:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
the installation goes to the end, but after restarting, the phone keeps looping on the logo screen...
I don't know if this information will be helpful, but the bootloader is locked (oem_locked).
I don't have developer knowledge, but I can follow your guidance, just tell me what to do.
I will be happy to pay a beer for those who help me
Please, guys, help me, I don't have another phone
Thank you very much in advance.
Edit: I got this phone from a friend, he tried to use a custom ROM, the phone worked but without Play Store, he tried to restore to stock ROM and got to this situation. So, he gave me the phone, because my Z2Play fell on water and died
Anyone??
Please, can anyone help me? :/
Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.
41rw4lk said:
Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.
Click to expand...
Click to collapse
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/
AgrippaJr said:
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/
Click to expand...
Click to collapse
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
Yeah, this one...
41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
AgrippaJr said:
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
Click to expand...
Click to collapse
Not adb/fastboot, the flashall.bat that you're using where did you get that?
41rw4lk said:
Not adb/fastboot, the flashall.bat that you're using where did you get that?
Click to expand...
Click to collapse
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...
AgrippaJr said:
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...
Click to expand...
Click to collapse
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
OK... I will try here... I'll let u know
Test result, questions
41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?
AgrippaJr said:
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?
Click to expand...
Click to collapse
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.
41rw4lk said:
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.
Click to expand...
Click to collapse
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...
AgrippaJr said:
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...
Click to expand...
Click to collapse
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.
What is your battery voltage when you fastboot getvar all?
Uzephi said:
What is your battery voltage when you fastboot getvar all?
Click to expand...
Click to collapse
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...
41rw4lk said:
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.
Click to expand...
Click to collapse
I follow all the tutorial steps, in two different PC's, windows versions and cables, cmd says 'waiting for device'... It don't detect the phone...
When i do the 'devices' command at adb and fastboot:
C:\Users\Junior\Desktop\adb and fastboot>adb devices
List of devices attached
C:\Users\Junior\Desktop\adb and fastboot>fastboot devices
0042953957 fastboot
Did i miss something?
AgrippaJr said:
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...
Click to expand...
Click to collapse
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.
Uzephi said:
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.
Click to expand...
Click to collapse
I see... And where do you think the defect is? Maybe the battery or something else? What can I do about it? :|
maybe I should open and measure the battery voltage with a multimeter... What do you think?
If you have another solution, let me know