I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
gocks said:
I rooted my Moto Z Play but I think I screwed up since I can´t no longer flash anything.
The TWRP is working fine (i guess) but when I try to install a ROM I get the following message:
"Failed to mount '/firmware' (invalid argument)"
I tried everything but can´t get it working properly.
Prior to this error I think I tried a diferent version of PAC-MAN and ended up with this situation.
Any sugestions?
Thanx in advance!
Click to expand...
Click to collapse
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
dandrumheller said:
As far as I know no one has built PAC ROM for moto z play. My guess is TWRP just saved you from bricking your phone. Better make sure you're trying to flash a ROM build for MZP.
Click to expand...
Click to collapse
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
gocks said:
C´mon guys, give me a break, I´m not a tech savy or something like that, just a regular lawyer.
Since I didn´t break my MZP what do I have to do to get it working again??
Click to expand...
Click to collapse
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Flash the correct ROM, in the updater script it checks your phone version prior to flashing the ROM.
Go to the development threads and find yourself moto z play specific ROM and flash
Sent from my XT1635-02 using
Click to expand...
Click to collapse
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
gocks said:
I´ve already tried the specific ROM from 3 diferent sources but the problem persists. I´ve tried the custon one and other ROMs but the same erros keeps showing.
Click to expand...
Click to collapse
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Does the phone boot to the stock ROM?
You may want flash the specific firmware for your phone.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
gocks said:
It does not boot to the stock ROM.
Just flashed the Nagout that you uploaded on another thread. It install but when I do the swipe after flashing the same error appears and the phone don´t boot. The error always appear after the "Updating partition details...." message.
After the installation I got this message:
Moto Z Play Nougat Installed
script suceeded: result was [Moto z P`lay Nougat Installed]
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
Then I wiped the cache/dalvik and this occurs:
Formating Cache using make_ext4gs....
Updating partition details....
Failed to mount '/firmware' (invalid argument)
....done
Wiping Dalvil Cache Directories...
Cleaned: /data/dalvik-cache...
--Dalvik Cache Directories Wipe Complete!
Updating partition details...
Failed to mount '/firmware' (invalid argument)
....done
And when I reboot the system twrp ask to install a su wich I don´t install, the system reboot and after the message warning that my device is unlocked it goes to a dark screen and nothing happens.
AP Fastboot Flash Mode (Secure), is that correct?
Thanks again.
Click to expand...
Click to collapse
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
Download your firmware and flash in fastboot. Flash only the 10 sparsechunks,recovery, OEM.img and boot.img and erase user data.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
gocks said:
Dont know how to flash oem.img. It´s just fastboot oem unlock? If it is it gave me back invalid boot state.
Are the others commands and the order something like that:
fastboot flash system system.img_sparechunk.0 till 10
fastboot flash recovery recovery.img
IDK what´s the OEM.img command
fastboot flash boot boot.img
fastboot erase userdata
Thank you so much again!
Click to expand...
Click to collapse
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
This is the commands
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
Fastboot flash system system.img_sparsechunk.0
Fastboot flash system system.img_sparsechunk.1
Repeat all 10 sparsechunks
fastboot flash oem oem.img
Fastboot erase userdata
Fastboot reboot
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did exactly what you told me and this happened:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.371s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.683s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (10820 KB)...
OKAY [ 0.235s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.235s]
finished. total time: 0.501s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257307 KB)...
OKAY [ 5.493s]
writing 'system'...
OKAY [ 3.985s]
finished. total time: 9.478s
The othes lines seems to be ok, but the phone continue stucked on the "Your device has been unlock...." and don´t reboot.
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
gocks said:
Downloaded another custom ROM (ADDISON_RETBR_6.0.1_MPNS24.104-44-7)
Unzipped into Minimal ADB and Fastboot folder
Openned Fastboot
Loaded bootloader and connected USB
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.376s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.704s
>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.296s]
finished. total time: 0.672s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257311 KB)...
OKAY [ 5.505s]
writing 'system'...
OKAY [ 3.971s]
finished. total time: 9.477s
>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (105020 KB)...
OKAY [ 2.245s]
writing 'oem'...
OKAY [ 1.439s]
finished. total time: 3.688s
>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.151s]
finished. total time: 0.154s
>fastboot reboot
rebooting...
And nothing happens again after the reboot.
When I try to boot to recovery it gives me a "no command" screen with a "no command" message and just it.
Flashed the recovey.img from twrp and it is working ok.
My bootloader:
AP Fastboot Flash Mode (Secure) => in red
BL: C0.14 (sha-9325e5f, 2016-07-11 16:32:03)
Baseband: <not found>
Product/Variant: addison XT1635-02 32GB P7
Serial number: xxxxxxxxx
CPU: xxxxxx
eMNC: xxxxxx
DRAW: xxxxxxxxx
Console: [NULL]: null
Battery: OK
flashing_unlocked
Software status: Modified
Transfer Mode: USB Connected
Trying now ROM XT1635-02_ADDISON_RETBR_MPNS24.104-44-10_cid50_
Any clue? Thanx again.
Click to expand...
Click to collapse
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
You flashed all the sparsechunks from 0 to 10?
The stock recovery has a dead Andy robot, so that flashed.
Did you flash the boot.img?
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
gocks said:
Yep, exactly the way you told me to do.
ADDISON_RETBR_6.0.1_MPNS24.104-44-7 has a corrupted file, but it didn´t work with the ADDISON_RETBR_MPNS24.104-44-10_cid50_ too.
Will try another one. And thanx again.
Click to expand...
Click to collapse
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
flashallthetime said:
Obviously the pacman rom screwed up your partition, normally every rom will check if you're flashing a rom to a specific device.
I don't think flashing any other firmware will help cause it's all the same from one carrier to another.
I think you may need to flash the entire firmware package but it MUST BE YOUR SPECIFIC FIRMWARE PACKAGE otherwise you'll really be bricked.
I'm pulling at straws
Click to expand...
Click to collapse
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
gocks said:
Don´t say the word brick, please!!!
What I have to do to know what is my specific firmware?
Click to expand...
Click to collapse
Which carrier are you with?
And don't sue me if things get worse
flashallthetime said:
Which carrier are you with?
And don't sue me if things get worse
Click to expand...
Click to collapse
Vivo, its a brazilian one.
Relax, if my phone bricks I wont sue you because my wife will kill me first!
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
gocks said:
I flashed TWRP recovery.img and found that I have diferent kinds of partitions, is it corret?
/data is f2fs
/cach /system /persist ext4
/efs1 emmc
/external_sd and usb-otg vfat
Click to expand...
Click to collapse
Yes and it seems like you can't right to the system and or data partitions. There's more partitions but they're locked or hidden
Try to format your data in TWRP
and wipe system
Related
@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak
Thnkx buddy ...!!
thanks..Anyone tried it? it works?
Sent from my HTC Desire 300 using XDA Premium 4 mobile app
FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300
Is this confirmed working?
will this work on chinese 301e ....because these is no playstore in chinese version
aamszia said:
will this work on chinese 301e ....because these is no playstore in chinese version
Click to expand...
Click to collapse
Can I have a copy of your build.prop?
MameTozhio said:
@SPSPaWn posted the Russian Desire 300 dump on 4pda, so I decided to mod it with Android Kitchen.
It's deodexed, zipaligned, rooted and has busybox and init.d support added.
Flash it in recovery and do a full wipe before flash (system also has to be wiped as well)
Download link - http://d-h.st/t4R
@xaak
Click to expand...
Click to collapse
i got status(0) error while flashing this rom :'( . what's wrong ?
MStevie said:
i got status(0) error while flashing this rom :'( . what's wrong ?
Click to expand...
Click to collapse
maybe this was created to kill your phone?
so i recieved another phone ... still no rom
chinese 301e
SPSPaWn said:
FOR HTC Desire 300/Zara Mini
CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn enhanced
How to install CWMRecovery:
1. extract archive CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn.rar
2. folder clockworckmod copy to your sd card
3. reboot device into fastboot
4. flash recovery - fastboot.exe flash recovery recovery.img
5. reboot device
How to install root:
1. download UPDATE-SuperSU-v1.86.zip and copy in your sd card
2. reboot device into CWMRecovery
3. select - install zip from sd card and install SuperSU
my Thread in 4PDA HTC Desire 300
Click to expand...
Click to collapse
i got status(0) error while flashing this rom
I also have this error when I try to flash the HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox + init.d
Stock ODEX root 1.10.401.4 updated works without a problem.
what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....
maplegsm said:
what is problem ?
C:\>fastboot devices
SH3CRWL00209 fastboot
C:\>fastboot flash recovery recovery.img
target reported max download size of 421527
sending 'recovery' (6910 KB)...
OKAY [ 1.250s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.016s
---------- Post added 12th October 2014 at 12:05 AM ---------- Previous post was 11th October 2014 at 11:40 PM ----------
i need coustom rom ....
Click to expand...
Click to collapse
You need to unlock the bootloader go to http://www.htcdev.com/ and click "Unlock Bootloader" select other device from the list and follow the instructions. Hope this helps.
where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????
RamHa said:
where is dev? say something? Ram cosuption, speed, specs, changelog(or in OP is what it has done?), where are testers??? Nobody could confirm that rom is: fully working, partially, not working, bugs...??????
Click to expand...
Click to collapse
This is just a stock system dump I did about 2 years ago that was meant to be flashable with root but it doesn't flash properly for some, I won't be updating it any further.
Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy
Riski3Run said:
Hello!
I flashed CWMRecovery_Philz-cmw6-v5.15.9_base_6.0.3.7_by_SPaWn to Unofficial TWRP Recovery 2.6.1.0 and wipe all data and installed from zip via Recovery this ROM [G3U] HTC Desire 300 Stock Russian-deodexed, zipaligned, rooted, busybox+init.d and I have to tell you that is working.
Finally this phone get some speed.Wife is happy
Click to expand...
Click to collapse
That's good! Just be sure to disable automatic receiving of MMS messages as this is vulnerable to all the stagefright exploits.
f
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
< waiting for device >
sending 'recovery' (6910 KB)... OKAY [ 1.463s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.563s
C:\Users\mwesiga2015\Desktop\htc\ADB> fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.310s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.410s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.347s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 9.641s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.382s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.482s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.340s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.440s
C:\Users\mwesiga2015\Desktop\htc\ADB>fastboot.exe flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY [ 1.330s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.430s
C:\Users\mwesiga2015\Desktop\htc\ADB>
hi guys
i have lg g3 D855 after update its dead and now its only stay on lg logo i tried to flash new rom but when i try to go the download mode its going to fastboot mood then i try to flash laf.img its give me this error
C:\New folder\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 2147483648 bytes
sending 'boot' (12800 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 10.470s
C:\New folder\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (17408 KB)...
OKAY [ 0.552s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 10.617s
C:\New folder\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.036s
also i get the same error with flashing the recovery file
so whats wrong and what should i do to fix this?
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
itsbighead said:
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
Click to expand...
Click to collapse
thx for replay me
i did that (fastboot boot laf.img) its say done with showing some words on the phone monitor but nothing happen also still cant go the flash mode
Try this
Boot into TWRP
Enable MTP and copy laf.img to sdcard
Go to Terminal Command in Advanced
Run the commands below using TWRP
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Hello,
I have a M9 rooted with android 5.0.2.
I downloaded this file:
https://www.androidfilehost.com/?fid=95916177934550733
I compiled the desired kernel into Image.gz and then create boot.img on Ubuntu.
Code:
cp boot_signed.img boot.img
abootimg -u boot.img.test -k Image.gz
I then do in download mode:
Code:
fastboot boot boot.img
I get this error on boot in cmd window:
FAILED (remote: dtb not found)
How can it be fixed?
Did not saw any information about this problem on M9 forum.
Thank you in advance!
adryyandc said:
Hello,
I have a M9 rooted with android 5.0.2.
I downloaded this file:
https://www.androidfilehost.com/?fid=95916177934550733
I compiled the desired kernel into Image.gz and then create boot.img on Ubuntu.
Code:
cp boot_signed.img boot.img
abootimg -u boot.img.test -k Image.gz
I then do in download mode:
Code:
fastboot boot boot.img
I get this error on boot in cmd window:
FAILED (remote: dtb not found)
How can it be fixed?
Did not saw any information about this problem on M9 forum.
Thank you in advance!
Click to expand...
Click to collapse
The file you downloaded is a HTC RUU. To install it you need s-off and a Developer Edition M9
rename it 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32, reboot your hima into DOWNLOAD_MODE, agree and it flashes the phone
clsA said:
The file you downloaded is a HTC RUU. To install it you need s-off and a Developer Edition M9
rename it 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32, reboot your hima into DOWNLOAD_MODE, agree and it flashes the phone
Click to expand...
Click to collapse
Ok, Thank you! Don't really need RUU then.
I will read boot image from device with:
Code:
dd if=/dev/block/mmcblk0p63 of=/sdcard/boot.img
beacause boot is linked with /dev/block/mmcblk0p63
and then replace zImage with my kernel zImage with abootimg.
but remeber you need to be S-Off.
LLegion said:
but remeber you need to be S-Off.
Click to expand...
Click to collapse
I was able to extract boot partition and use abootimg on it to update the kernel successfully (the boot.img has 64 MB.), but
Code:
fastboot boot boot.img
does not work.
It says:
Code:
downloading 'boot.img'...
OKAY [ 3.980s]
booting...
and cmd does not return to normal after waiting 30 mins.
Is fastboot boot command deprecated? Could be a driver problem?
adryyandc said:
I was able to extract boot partition and use abootimg on it to update the kernel successfully (the boot.img has 64 MB.), but
Code:
fastboot boot boot.img
does not work.
It says:
Code:
downloading 'boot.img'...
OKAY [ 3.980s]
booting...
and cmd does not return to normal after waiting 30 mins.
Is fastboot boot command deprecated? Could be a driver problem?
Click to expand...
Click to collapse
The M9 uses aboot not hboot .. as far as I know you can't "boot" anything from fastboot
clsA said:
The M9 uses aboot not hboot .. as far as I know you can't "boot" anything from fastboot
Click to expand...
Click to collapse
Thank you!
I give the following commands:
Code:
fastboot flash boot boot.img.test
fastboot reboot
and i get:
Code:
target reported max download size of 800000000 bytes
sending 'boot' (65536 KB)...
OKAY [ 4.850s]
writing 'boot'...
(bootloader) HOSD CL#xxxxxx
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.870s]
finished. total time: 8.720s
but the device will return to fastboot menu.
I want to flash stock image and now i'm stuck.
Code:
fastboot flash boot boot.img
I get the following message:
Code:
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.160s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 2.180s
adryyandc said:
Thank you!
I give the following commands:
Code:
fastboot flash boot boot.img.test
fastboot reboot
and i get:
Code:
target reported max download size of 800000000 bytes
sending 'boot' (65536 KB)...
OKAY [ 4.850s]
writing 'boot'...
(bootloader) HOSD CL#493992
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.870s]
finished. total time: 8.720s
but the device will return to fastboot menu.
I want to flash stock image and now i'm stuck.
Code:
fastboot flash boot boot.img
I get the following message:
Code:
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.160s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 2.180s
Click to expand...
Click to collapse
The error message says your not S-OFF
Sent from my HTC One M9 using Tapatalk
clsA said:
The error message says your not S-OFF
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How can i put the device in S-OFF mode if the device does not boot?
As i could flash a bad kernel in first step it means i had S-OFF previously?
I was able to upload my stock boot.img (the one backed-up) even i had S-ON with:
Code:
fastboot oem rebootRUU
fastboot flash boot boot.img
fastboot reboot
Don't know why in download mode i was not able to do this.
I have build number 1.32.617.6 CL493992 release-keys
Do i really need to be S-OFF to upload only my custom kernels? According to HTC i don't need to because bootloader is unlocked and:
"What is meant by unlocking the bootloader is that certain partitions are unlocked to provide write access. Specifically: boot, system and recovery. "
http://www.htcdev.com/bootloader/about_unlock_process
Answer: Yes, i need too!
Thanks!
I was able to S-OFF the device. Now the problem is that my compiled unmodified kernels from HTC site won't boot. Any ideea why?
Would i be able to convert this device to Developer Edition using AT&T RUU?
Fixed my problem by using right tool to unpack and repack boot image.
I used this one:
https://github.com/xiaolu/mkbootimg_tools
Help
I have a big problem with my HTC ONE M9. I used a custom rom and I tried to get beck to stock rom without any back up of custom or stock rom. I lost everything and I tried more but I couldn't do anything. The situation now is that I stuck in the logo with no recovery mode or bootloader mode. just download mode. S ON, RELOCKED, Software Modified.
I need your help.
elmasry82 said:
I have a big problem with my HTC ONE M9. I used a custom rom and I tried to get beck to stock rom without any back up of custom or stock rom. I lost everything and I tried more but I couldn't do anything. The situation now is that I stuck in the logo with no recovery mode or bootloader mode. just download mode. S ON, RELOCKED, Software Modified.
I need your help.
Click to expand...
Click to collapse
Sorry, can't help you much in this matter! I won't do it for the money anyway.
You could maybe re-flash a stock ROM since you have access to download mode with fastboot flash zip command. Ask a more experienced user!
adryyandc said:
Sorry, can't help you much in this matter! I won't do it for the money anyway.
You could maybe re-flash a stock ROM since you have access to download mode with fastboot flash zip command. Ask a more experienced user!
Click to expand...
Click to collapse
I tried many stock flashes but doesn't work. I don't know the stock flash of my phone. I couldn't reach fastboot. SD card is my only way
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.
I have searched and searched but cannot find anywhere that tells me what these messages mean in fastboot.
Example:
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Please help.
Thank you.
Did you do something before this happened?
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
myjess said:
LOL, yes, I completely fecked it up.
I have got the recovery back now, but when I try to flash a stock image,
1. Obviously will not flash the bootloader cos it is now unlocked. So I deleted the bits in the bat file that try to flash the bootloader so that the rest can complete.
2. Now will only get to various Systemchunks and then hangs, having installed previous system chunks ok.
Seems to get to here and then hangs.
Executing ".\Windows\fastboot.exe -s SERIALNUMBER flash system systemchunk10.img"
target max-download-size: 512MB
sending 'system' (262143 KB)...
I though about erasing system, butbut the I now get this message bootloader message.
fastboot erase system
(bootloader) has-slot:system: not found
Erasing 'system' OKAY [ 0.025s]
Finished. Total time: 0.062s
So, I had to go to Qualcomm fix, and I have lineage 16 on it now, but I have lost my IMEI's
Thanks for reading.
Click to expand...
Click to collapse
probably u just delete system image file
Is ok, got it all working again.
Thanks.