[Q] m8 possibly corrupt hboot - One (M8) Q&A, Help & Troubleshooting

Hi
I am not really sure what i have done wrong here, but i have got myself to a stage where i can get to fastboot, but i cannot get to the recovery, if i select hboot then i get the following:
TWRP: teamwin screen flashes a couple of times then the device reboots
CWM: black screen the the device reboots
Stock recovery: android driod with a red exclamation mark then the device reboots
I have tried multiple recovery's as you can see.
I know that i am currently in a state where i have NO os on the phone.
**TAMPERED***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.14.2133156.UA24G
OpenDSP-v26.2.2-00538-M8974.0106
OS-
eMC-boot 2048MB
Feb 26 2014,21:38:56.14307
This all started when i somehow got in a reboot loop when SuperSU tried to push the su binary to TWM.
Any help or directions to get me back ontrack would be appreciated.
Thanks
Darren
--
addition, just following some instructions about restoring to stock boot, recovery and rom from android reolution, output below:
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash boot boot.img
target reported max download size of 1830711296 bytes
sending 'boot' (8262 KB)...
OKAY [ 0.971s]
writing 'boot'...
OKAY [ 0.666s]
finished. total time: 1.638s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash recovery recovery
mg
target reported max download size of 1830711296 bytes
sending 'recovery' (15236 KB)...
OKAY [ 1.605s]
writing 'recovery'...
OKAY [ 0.992s]
finished. total time: 2.599s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot -w
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.020s
C:\Users\darrend\Desktop\s-off\platform-tools>fastboot flash update update.zip
target reported max download size of 1830711296 bytes
sending 'update' (1387053 KB)...
OKAY [ 59.626s]
writing 'update'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 137.319s

Try fastboot erase cache

Related

Saving Data from locked, bricked device

Hey there,
as the title of the threat already indicates, my HTC One X got bricked.
As this usually happens when trying to flash some custom roms or recoverys, in my case it is the result of an official HTC update for android.
I can boot into Fastboot, and via cmd "fastboot devices" does show me the connected phone.
Now my approach for solving this matter was to flash the clockwork mod and then boot into recovery.
From there i wanted to pull data from the phone via adb commands.
The only problem is that my phone is locked. I cannot unlock it at the moment without wiping all data (which obviously would miss the whole data recovery point).
When i try tp flash the CWM in fastboot i get:
sending 'recovery' (8100 KB)...
FAILED (unknown status code)
finished. total time: 0.933s
I also tried to directly boot a recovery via fastboot boot recovery.img.
This resulted in
downloading 'boot.img'...
FAILED (unknown status code)
finished. total time: 0.933s
Well now I am seriously frustrated and dont know how to get my data.
Any help is very much appreciated.
Cheers
Josef
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
joe1000 said:
Update:
fastboot flash recovery recovery.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8100 KB)...
OKAY [ 1.066s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.720s
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.066s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.068s
fastboot boot recovery recovery.img
cannot load 'recovery': Permission denied
any help?
Click to expand...
Click to collapse
You must to unlock the device qith locked you can't do anything but if you unlock it is possible to wipe all data on the SD card
well but thats exactly the problem...

Bricked -unable to use Wug tool kit to revive it

i can only get to fastboot mode. My nexus Bootloader version - FLO- 04.04, and it's unlocked. I've tried to use Wug tool kit but got stuck at "erasing cache". See log below. I've tried different cables and different USB ports. Any tips or guidance is greatly appreciate. Thanks
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.742s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
sending 'boot' (7448 KB)...
OKAY [ 0.245s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.166s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.010s
erasing 'cache'...
i have the same problem
the nand flash is broken, change your mainboard and you will be happy again
i will never buy a asus device

fastboot erase cashe

HELLO
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
enrecovery-twrp-2.6.3.3-m7.img.
< waiting for device >
target reported max download size of 1826414592 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.827s]
finished. total time: 2.027s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>
some one help me to fixe this problem
i have HTC one M8 T-MOBILE V6.1
+212629891194 its my whatsap
1. What/why M7 recovery for M8
fastboot flash recovery NameOfRecovery.img is correct command
https://twrp.me/htc/htconem8gsm.html
2. cache not cashe
fastboot erase cache is correct command
Kharbas said:
HELLO
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
enrecovery-twrp-2.6.3.3-m7.img.
< waiting for device >
target reported max download size of 1826414592 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.827s]
finished. total time: 2.027s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>fast
erasing 'cashe'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\YOUSSEF\Desktop\OneDrivers_Fastboot\Fastboot>
some one help me to fixe this problem
i have HTC one M8 T-MOBILE V6.1
+212629891194 its my whatsap
Click to expand...
Click to collapse
Dude that's a m7 recovery
Sent from my HTC One (M8) using XDA Labs
Always check your command syntax is exactly right, when performing fastboot and adb commands.
And yeah, the proper TWRP for your phone would help.

Stuck in the Fastboot/ Recovery

I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
matthew.bridell said:
I was trying to root and install a custom rom. When I installed the rom and reboot the device it said no OS installed. I have been trying to send the taimen-opm1.171019.018-factory-e96a86ae.zip file over I realized I have never done that and don't know if there is a fastboot command for push. Any help will be very nice. thanks
Click to expand...
Click to collapse
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
CyberpodS2 said:
You don't send it to the phone but instead you unzip it in a folder with your adb/fastboot files and flash it.
Click to expand...
Click to collapse
flash the zip? Would I just use fastboot flash image-taimen-opm1.171019.018.zip ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
CyberpodS2 said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
I was able to install Lineage-15.1-20180219 and boot into it. Tried to restore from that point and it now when I run flash-all it now says
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.006s
rebooting into bootloader...
FAILED (remote: unknown command)
finished. total time: 0.003s
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
error: cannot load system.img from flash
Press any key to exit...
matthew.bridell said:
when I do that I get
C:\Users\matth\Downloads\fastboot>flash-all
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.003s
< waiting for device >
And the phone phone goes into bootloop with twrp recovery poping up with errors.
Click to expand...
Click to collapse
You need to update your platform-tools.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
just tried the zip and no luck
C:\Users\matth\Downloads>cd "platform-tools-latest-windows (2)"
C:\Users\matth\Downloads\platform-tools-latest-windows (2)>cd platform-tools
C:\Users\matth\Downloads\platform-tools-latest-windows (2)\platform-tools>flash-all
target didn't report max-download-size
sending 'bootloader' (36344 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.003s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
target didn't report max-download-size
sending 'radio' (60428 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.221s
target didn't report max-download-size
error: Failed to identify current slot
Press any key to exit...
I do now have default Recover but don't know why it won't work.
I feel dumb. I got it to work with using a usb-a to usb-c cord. was trying to use the usb-c to usb-c cord thanks for all the help.

Z2 Force dead, just turn on with USB connected, don't charge

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

Categories

Resources