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
Related
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
Hello. I was following a video tutorial named: How To change Hboot + Install Jelly Bean on Your HTC One X - JB on HOX
at the stage where I use flash zip firmware.zip I can not get out of the bootloader. Please can someone guide me on how to recover my phone from this.
******RELOCKED*****
******Security Warning******
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-0.43.0000
CPLD-None
MICROP-None
The commands are below which have lead to this disaster. Please can someone assist me. Thanks.
c:\htc>fastboot-windows.exe flash boot boot.img
sending 'boot' (4974 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
c:\htc>fastboot-windows.exe erase cache
erasing 'cache'... OKAY
c:\htc>fastboot-windows.exe oem lock
... FAILED (command write failed (Unknown error))
c:\htc>fastboot-windows.exe oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
c:\htc>fastboot-windows.exe oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOoffset = 0
INFOUpdate partition data from original MSC...
INFOoffset = 0
INFO[MSG] OKAY
OKAY
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (remote: (00030003))
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... ^C
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (remote: (00120000))
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... OKAY
writing 'zip'... FAILED (remote: not allowed)
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (unknown status code)
I have unlocked my bootloader again (frrom the HTCDEV website). I can now get into recovery. I have restored my backup which i made before.
I then copied an old boot.img from my original rom
c:\htc>fastboot-windows.exe flash boot boot.img
< waiting for device >
sending 'boot' (4290 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
Then thankfully my phone booted ok back to how it was originally.
You can't flash the 1.36 hboot,
coz your hboot is to low, with version 0.43.
The easiest way would be, to flash the 2.17 ruu,
and after that, you could Update your hboot.
Gesendet von meinem HTC One X mit Tapatalk 2
thanks for the reply. so where can i find the 2.17 ruu
Also can you explain a bit on the steps that I need to complete with the 2.17 ruu
uk_network said:
thanks for the reply. so where can i find the 2.17 ruu
Click to expand...
Click to collapse
htcruu.com
Searching would have got you the answer quicker.
BenPope said:
htcruu.com
Searching would have got you the answer quicker.
Click to expand...
Click to collapse
ok thanks. I should add im from the UK. Will this RUU do the job?
tcruu.com/Endeavor/RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
uk_network said:
ok thanks. I should add im from the UK. Will this RUU do the job?
tcruu.com/Endeavor/RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Click to expand...
Click to collapse
If your phone was destined for the UK, yeah.
fastboot get version-main
Will tell you which ROM you had originally, so the 401 needs to match.
I can't get that command to work with my fastboot.
c:\htc>fastboot-windows.exe fastboot get version-main
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
The same also happens if i type.
c:\htc>fastboot-windows.exe get version-main
Sorry
fastboot getvar version-main
BenPope said:
Sorry
fastboot getvar version-main
Click to expand...
Click to collapse
For him it's 'fastboot-windows.exe getvar version-main'
version-main: 1.26.206.2
c:\htc>fastboot-windows.exe getvar version-main
version-main: 1.26.206.2
When I check on htcruu.com/?dir=Endeavor
I can find:
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
This has matching 206 version.
But this doesn't have 2.17 as mentioned previously.
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_sined.exe
Any ideas on which one to choose?
The one that matches. Hopefully you'll get OTA updates to 2.17.206.x
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.120 4.90.13_release_251230_signed.exe
I do notice in the title that it says 02_UK im not on 02 im on three.co.uk would this be an issue? if so its the only RUU that has 206 in the title. Also Is this the only way to update hboot versioin?
Thanks to all who are contributing and for your continued support in this matter. I had a shock when I almost originally bricked my one x.
Well where did you get the phone from?
That's the right RUU.
You can update the firmware by locking it, flashing the updated firmware and unlocking it. Either way your phone is gonna get wiped.
I bought the phone from ebay.co.uk from the UK
I am a little confused by this picture it says 1.29.401.11
Should i go ahead with the upgrade?
When i origianly did the below command i got a different version.
fastboot-windows.exe getvar version-main
version-main: 1.26.206.2
There is a discrepancy between 401 and 206 or does this not matter? or can i now use this ruu??
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
And to confirm the next step, after this update i will need to relock the boot loader and then perform the update and then unlock it.
fastboot-windows.exe oem lock
fastboot-windows.exe oem rebootRUU
fastboot-windows.exe flash zip firmware.zip
then perform the unlock from the htcdev site.
Hey guys, dont know really where else to post this, but i need help upgrading my hboot.
Im currently on hboot 1.12 S-ON, cid VODAPO21
i tried flashing 1.36 firmware and it didnt work, gave an error remote:not allowed
i assume i need to go up in increments.
Trouble is , not sure which ones i should flash first and also where to find it. Ive downloaded RUU for my cid versions 1.26 and 1.29...not sure if you can extract the firmware from them, or how its done. Tried opening it in winrar/7-zip and could open em.
Still not there yet.
Still no luck I am afraid. I have tried both of the below RUU's and receive the error in the attached screenshot.
The RUU's that I have tried both give the same error. They are:
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
Thanks so much to the person who can help get me upgraded to Jelly Bean.
Anyone ?? Im still wanting to update to jellybean and can't yet. Can someone please help me out this this.
You did getvar version main and it said you have a '206 ROM, if a new enough RUU can't be found, you'll have to flash a backup. If you don't have one, check the backups thread for somebody else's. It has to be '206.
BenPope said:
You did getvar version main and it said you have a '206 ROM, if a new enough RUU can't be found, you'll have to flash a backup. If you don't have one, check the backups thread for somebody else's. It has to be '206.
Click to expand...
Click to collapse
I have a backup of my stock rom. But i rooted it and then backed it up. Would this work?
My m8 has an unlocked bootloader with s-on and i recently just used a nandroid backup which flashed the stock recovery and i updated to newest 5.0 update my phone was with t-mobile but it is factory unlocked now. Whenever I try to flash philz or twrp through fastboot it gives me:
target reported max download size of 1826414592 bytes
sending 'twrp' (16086 KB)...
OKAY [ 1.469s]
writing 'twrp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.047s
How am i supposed to flash a custom recovery
Are you trying to do it in fastboot oem rebootRUU or just normal fastboot? You should be in the bootloader and just use fastboot flash recovery recovery.img
EddyOS said:
Are you trying to do it in fastboot oem rebootRUU or just normal fastboot? You should be in the bootloader and just use fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I tried both
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
Red Magic 8 Pro stuck fastboot
It no longer has sideload mode in recovery
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
BoJaXz said:
Did you somehow change your slot? If you haven't upgraded the firmware, then the 2nd slot is empty, and it will not boot anything.
Click to expand...
Click to collapse
I switched both slots, but I can't boot up
Mr.PvT said:
I switched both slots, but I can't boot up
Click to expand...
Click to collapse
What steps did you do before you got stuck in fastboot?
BoJaXz said:
What steps did you do before you got stuck in fastboot?
Click to expand...
Click to collapse
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Mr.PvT said:
I patched the root boot file then flashed it failed, then I flashed each file in the payload, I deleted the super, the files in the super can't be flashed oddly, are you rooted, can backup the whole partition help me
Thank you
Click to expand...
Click to collapse
Did you oem unlock before you tried flashing? You may have to flash the whole image
BoJaXz said:
Did you oem unlock before you tried flashing? You may have to flash the whole image
Click to expand...
Click to collapse
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Mr.PvT said:
I unlocked the bootloader, I flashed all the files in the payload but still can't boot, hang fastboot or boot to the logo and then shut down
I need someone to back up all my partitions, that's the only way I can do it
Click to expand...
Click to collapse
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
BoJaXz said:
Did you flash boot.img or init_boot.img?
It sounds like you are booting the wrong slot.
Click to expand...
Click to collapse
I flashed those 2 files and changed both slots but failed to start the phone
I faced with the problem by locking the bootloader with init_boot.img for magisk. Then I unlocked it again and switched aactive slot to b and then to a in "Fastboot Enhance" tool. After that my phone entered to the system.
[TOOL][Windows] Fastboot Enhance [Payload Dumper & Image Flasher]
Fastboot Enhance What it can do? - Show fastboot vars - Switch between fastbootd & bootloader - Switch between A & B slot - Flash Payload.bin in fastbootd - Flash images - Erase partitions - Delete logical partitions - Create logical partitions...
forum.xda-developers.com
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
DarkestSpawn said:
@Mr.PvT did you ever make any progress with this? I am in the same boat now. Flashed a GSI and tested it out. DIdnt like it so flashed the 3.18 Payload.bin thru Fastboot enhance and am stuck on Bootloader. Cant access anything else as no matter what I choose it boots to bootloader.
Click to expand...
Click to collapse
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
edzchen said:
I also went from a GSI to stock ROM and this worked, some steps may be unnecessary:
In bootloader change active slot to a
Flash all of payload.bin images
Reboot to fastboot and flash all of payload images
Reboot to recovery
Hold volume down for a few seconds to enable sideload
Connect the phone to a pc and ADB sideload NX729J-update.zip
Then wipe data and reboot
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
In bootloader:
fastboot flash odm odm.img
target reported max download size of 805306368 bytes
sending 'odm' (1284 KB)...
OKAY [ 0.032s]
writing 'odm'...
FAILED (remote: (odm_a) No such partition)
finished. total time: 0.038s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_dlkm system_dlkm.img
target reported max download size of 805306368 bytes
sending 'system_dlkm' (428 KB)...
OKAY [ 0.011s]
writing 'system_dlkm'...
FAILED (remote: (system_dlkm_a) No such partition)
finished. total time: 0.018s
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system_ext system_ext.img
target reported max download size of 805306368 bytes
sending 'system_ext' (730792 KB)...
OKAY [ 17.204s]
writing 'system_ext'...
FAILED (remote: (system_ext_a) No such partition)
finished. total time: 17.211s
Nothing happens when I flash system & vendor.
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash vendor_dlkm vendor_dlkm.img
target reported max download size of 805306368 bytes
sending 'vendor_dlkm' (93564 KB)...
OKAY [ 2.181s]
writing 'vendor_dlkm'...
FAILED (remote: (vendor_dlkm_a) No such partition)
finished. total time: 2.187s
In Fastbootd:
Everything that failed in bootloader, flashed beside system. Could only flash _b slots. Nothing seems to exist for slot a. I did not fastboot format or erase anything to my knowledge unless Fastboot Enhance did so when I flashed the playload.bin thru it without having logs on to watch what it did. If it formated or erased any partitions can they be recreated?
And last when in Recovery:
F:\Files\Downloads\RM8P>adb sideload NX729J-update.zip
loading: 'NX729J-update.zip'
error: closed
DarkestSpawn said:
Everything that failed in bootloader, flashed beside system.
Click to expand...
Click to collapse
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
edzchen said:
What is the error when flashing system?
If it has something to do with not being able to resize the system partition, check this link:
Fix FAILED (remote: 'Not enough space to resize partition')
In this comprehensive tutorial, we will show you the steps to fix the FAILED (remote: 'Not enough space to resize partition') error.
www.droidwin.com
I had this problem too.
Which GSI were u on
Click to expand...
Click to collapse
I just retried in bootloader with a new outcome this time:
F:\Files\Downloads\RM8P\NX729J-update>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/6 (786364 KB) OKAY [ 18.742s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I copied the fastboot.exe from fastboot enchanced to the directory of the extracted payload.bin. Was able to recreate partitions. Am attempting to recover from potential brick.
I tried LineageOS TD-based. Didnt attempt calls or messages. Was just checking out the feel of the rom and its capabilities.
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
DarkestSpawn said:
Can someone run this fastboot command in bootloader and fastbootd and save the results in a text file?
fastboot getvar all
Omit the serial number in bootloader and fastbootd's printout.
Click to expand...
Click to collapse
Here you go:
ugene1980 said:
Here you go:
Click to expand...
Click to collapse
So looking thru this, the only difference I have is:
(bootloader) partition-size:userdata: 0x718BCD3000 Mine
(bootloader) partition-size:userdata: 0x35F5CD3000 Yours
as well as:
(bootloader) slot-successful:a:yes Yours
(bootloader) slot-successful:a:no Mine
but thats because it hasnt successfully booted since last flash.
I also need the fastbootd's printout. The one provided was from bootloader. The one from fastbootd will give logical partitions and has slot info.
edzchen said:
Also did your calls and messages work when using the GSI?
Click to expand...
Click to collapse
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
DarkestSpawn said:
Did you install carrier serivces from google play, setup APN settings for your carrier and Installing new IMS package: Treble Settings -> IMS features -> install IMS for Qualcomm -> install package. I cant remember if that was in there. Still trying to get booted again
Click to expand...
Click to collapse
Yeap I did all that but calls and texts only half worked. I could do calls but no audio and I could send texts but couldn't receive. Was the main reason why I switched back to stock