Kernel when flashing the device does not work, but when entering Hotbot mode it works
(Kernel does not work I have)
My Phone Is Xperia Arc S
http://www.youtube.com/watch?v=1U0kBrHz3xQ&feature=youtu.be
What exactly You need? If You want to flash new kernel, try with QuickIMG.
darkknightma said:
Kernel when flashing the device does not work, but when entering Hotbot mode it works
Click to expand...
Click to collapse
Use the right command. fastboot flash boot kernel.img
XperienceD said:
Use the right command. fastboot flash boot kernel.img
Click to expand...
Click to collapse
I used the right command but kernel not working
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
pypcier said:
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
Click to expand...
Click to collapse
Lol was just about to post something and you beat me to it
And make sure the kernel img is in firmware folder of flashtool you where flashing it from your desktop folder
tallman43 said:
Lol was just about to post something and you beat me to it
And make sure the kernel img is in firmware folder of flashtool you where flashing it from your desktop folder
Click to expand...
Click to collapse
You seem pretty competent when it comes to fastboot so can you help me with something? Every time i want to flash a new kernel after opening CMD I have to change directory to a folder containing boot.img and its pretty frustrating for me. Is there a folder for img files so fastboot will find them automatically? I've thought about creating a shortcut so CMD will open in right directory automatically but I'm lazy.
pypcier said:
You look pretty competent when it comes to fastboot so can you help me with something? Every time i want to flash a new kernel after opening CMD I have to change directory to a folder containing boot.img and its pretty frustrating for me. Is there a folder for img files so fastboot will find them automatically? I've thought about creating a shortcut so CMD will open in right directory automatically but I'm lazy.
Click to expand...
Click to collapse
To be 100 % honest not sure!I know in windows you can change default opening behavior of directories to open to your favorite folder etc,I once did ita long time ago but forgot how to
But what your suggesting sounds like a good idea:good: yep me lazy too don't use cmd much to be honest I use Doomlord's toolbox lol
So it looks like a customized shortcut is my only option. I like fastboot because its simple and reliable also typing stuff in black window is always cool. Life on the edge *****es!
pypcier said:
So it looks like a customized shortcut is my only option.
Click to expand...
Click to collapse
"Shift + Right Click" opens a command window in whatever folder you are in.
---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------
darkknightma said:
I used the right command but kernel not working
Click to expand...
Click to collapse
If it hot boots then it should flashboot and usually doesn't because People use the wrong command.
ALT + Right Click" opens a command window in whatever folder you are in.
Click to expand...
Click to collapse
Not on windows 8. I could do a shift + right click combo for "open cmd here" but this is useless because fastboot needs to be running with administrator rights. To be honest I don't care anymore because I've made a shortcut for opening cmd in a right folder with admin rights and even fancy blue font (*****es love blue fonts).
pypcier said:
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
Click to expand...
Click to collapse
this image when I flash kernel in fastboot but not working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its pretty bad :c you have a bad block in your kernel "partition" and its preventing you flashing kernels. As far as I know this can't be fixed. You can't flash custom kernels I'm sorry :<
edit
It's a physical error in a memory chip in your phone. After searching for more info I think there is nothing you can do.
Related
Hi all,
It seams to be assumed everyone is using windows these days?
Well if your using Linux this might help -
Get unlock key from sony HERE
Download SDK Manager HERE
Recommend creating folder in home called Android Development and placing zip file in there, then extract in same folder.
Download your selected Kernel & Rom from HERE
Recommend creating folder called Xperia Arc and place both Kernel & Rom there, then copy the Kernel to the Platform-Tools folder which is in the SDK folder, in the adt bundle folder (SDK Manager Download).
Copy the Rom to the sd card (still zipped)
Enable USB Debug mode in Developer Options in phone settings menu
Turn phone off
Hold menu button and plug phone into computer, (blue led will light up, let go of menu button, phone now in fastboot mode)
Open Platform-Tools folder, right click on adb and open as root, then in Platform-Tools (as root) right click adb and open in terminal
./adb start server
./fastboot -i 0x0fce getvar version
You should get a response back, i got 0.3 this means phone is connected correctly, (dont worry if you dont get a responce from ./adb devices)
Next to unlock the bootloader
./fastboot -i 0x0fce oem unlock 0xKEYFROMSONYGOESHERE
If done correctly unlock request will be sent to phone, phone will erase various blocks of memory and response will be OKAY like this
Barks-Laptop platform-tools # ./fastboot -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
Barks-Laptop platform-tools # ./fastboot -i 0x0fce oem unlock 0xEA20A60630F198C7...
(bootloader) Unlock phone requested
(bootloader) Erasing block 0x00001300
(bootloader) Erasing block 0x00001400
(bootloader) Erasing block 0x00001500
(bootloader) Erasing block 0x00001600
(bootloader) Erasing block 0x00001700
(bootloader) Erasing block 0x00001800
(bootloader) Erasing block 0x00001900
(bootloader) Erasing block 0x00001a00
(bootloader) Erasing block 0x00001b00
(bootloader) Erasing block 0x00001c00
(bootloader) Erasing block 0x00001d00
(bootloader) Erasing block 0x00001e00
(bootloader) Erasing block 0x00001f00
OKAY [ 11.095s]
finished. total time: 11.095s
Now to flash Kernel
./fastboot flash boot yournewkernal.img
If all went well you should see OKAY like this
Barks-Laptop platform-tools # ./fastboot flash boot lupus.img
sending 'boot' (7296 KB)...
(bootloader) USB download speed was 9702kB/s
OKAY [ 0.778s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 2.083s]
finished. total time: 2.862s
Barks-Laptop platform-tools # exit
Unplug phone and follow instructions to install Rom.
Cheers
Barkx
barkx said:
Download your selected Kernel & Rom from HERE
Click to expand...
Click to collapse
Nice guide, but this link applies only for Xperia Pro.
Someguyfromhell said:
Nice guide, but this link applies only for Xperia Pro.
Click to expand...
Click to collapse
Cheers dude, updated
Hello. I'll Make Huawei Stuck on Logo fixer to my friend. and i want to share it to everybody! Okay Lets start!
Follow The Instructions :
Download Adb&Fastboot here. and installed the adb&fastboot.
- http://tabletrepublic.com/forum/downloads.php?do=file&id=312
Download HiSuite for Huawei and update it.
- http://consumer.huawei.com/minisite/HiSuite_en/
Download recovery.img here .
- https://www.androidfilehost.com/?fid=23329332407584772
# after you downloaded the recovery.img paste it on adb&fastboot folder.
# Connect your phone to the computer using the supplied USB cable.
# Press and hold the Power and Volume Down button.
# PHONE will be recognized as ABD device. it appears on the side of your desktop.
# Leave the Power and Volume Down button.
# And now go to Adb&fastboot folder , and hold Shift+Right click then Choose "Open command window here"
# and then when cmd appears type this command .
"fastboot devices" without quote ("")
when you see like this ????/??,,? <>?????? it means device is detected .
you can continue . next step type this .
Type: fastboot reboot bootloader
Type fastboot flash recovery recovery.img
after you type the last command , when you see the finish word without FAILED.
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. PHONE will boot now :laugh:
and then your phone fix now , and dont stuck on logo! ENJOY! :angel: :angel: :angel:
Btw if you failed flashing recovery please tell me.
PRESS THANKS IF HELPS!
U flash recovery without unlock bootloader!!!??
Help999 said:
Hello. I'll Make Huawei Stuck on Logo fixer to my friend. and i want to share it to everybody! Okay Lets start!
Follow The Instructions :
Download Adb&Fastboot here. and installed the adb&fastboot.
- http://tabletrepublic.com/forum/downloads.php?do=file&id=312
Download HiSuite for Huawei and update it.
- http://consumer.huawei.com/minisite/HiSuite_en/
Download recovery.img here .
- https://www.androidfilehost.com/?fid=23329332407584772
# after you downloaded the recovery.img paste it on adb&fastboot folder.
# Connect your phone to the computer using the supplied USB cable.
# Press and hold the Power and Volume Down button.
# PHONE will be recognized as ABD device. it appears on the side of your desktop.
# Leave the Power and Volume Down button.
# And now go to Adb&fastboot folder , and hold Shift+Right click then Choose "Open command window here"
# and then when cmd appears type this command .
"fastboot devices" without quote ("")
when you see like this ????/??,,? <>?????? it means device is detected .
you can continue . next step type this .
Type: fastboot reboot bootloader
Type fastboot flash recovery recovery.img
after you type the last command , when you see the finish word without FAILED.
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. PHONE will boot now :laugh:
and then your phone fix now , and dont stuck on logo! ENJOY! :angel: :angel: :angel:
Btw if you failed flashing recovery please tell me.
PRESS THANKS IF HELPS!
Click to expand...
Click to collapse
I try for me but i got this ERROR :
D:\--- MOBILE\Android\android\platform-tools>fastboot flash recovery recovery.im
g
< waiting for device >
target reported max download size of 838860800 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.476s]
writing 'recovery'...
FAILED (remote: flash failure, ErrNo:2)
finished. total time: 0.486s
D:\--- MOBILE\Android\android\platform-tools>fastboot flash boot boot.img
D:\--- MOBILE\Android\android\platform-tools>fastboot flash boot boot.img
target reported max download size of 838860800 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.243s]
writing 'boot'...
FAILED (remote: flash failure, ErrNo:2)
finished. total time: 0.252s
Click to expand...
Click to collapse
after you downloaded the recovery.img paste it on adb&fastboot folder.
Click to expand...
Click to collapse
i think he means c:\adb
because there is no such folder named adb&fastboot
Type: fastboot reboot bootloader
Type fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Correction:Type: fastboot reboot-bootloader
Tried this, FAILED <remote: verify failure : Errno. 8>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
amir_zohaib said:
i think he means c:\adb
because there is no such folder named adb&fastboot
Correction:Type: fastboot reboot-bootloader
Tried this, FAILED <remote: verify failure : Errno. 8>
Click to expand...
Click to collapse
are you on windows 8?
danielpsx said:
are you on windows 8?
Click to expand...
Click to collapse
No, windows 7 ,64 bit.
i think it has something to do with timing
Any news on this?
I also have this problem, is there a fix?
C:\adb>fastboot flash recovery recovery_original_flashable.img
target reported max download size of 838860800 bytes
sending 'recovery' (7804 KB)...
OKAY [ 0.334s]
writing 'recovery'...
(bootloader) OKAY
FAILED (remote: verify failure, ErrNo:8)
finished. total time: 1.519s
any updates i have the same problem
same problem on widnows 10 64bit
benjamin1 said:
I also have this problem, is there a fix?
C:\adb>fastboot flash recovery recovery_original_flashable.img
target reported max download size of 838860800 bytes
sending 'recovery' (7804 KB)...
OKAY [ 0.334s]
writing 'recovery'...
(bootloader) OKAY
FAILED (remote: verify failure, ErrNo:8)
finished. total time: 1.519s
Click to expand...
Click to collapse
Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.
computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much
Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.
my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.
freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?
blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?
sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.
Dear All,
All of sudden Htc one M9 behaves strangely and now i can't get any information from it.
Without tried anything: Software status changes
Software Status "Modified"
Locked
S-ON
Can't be able to go to recovery mode either nor get any fastboot option in Download mode
What i get
C:\platform-tools>fastboot devices
HT54PYJ04176 fastboot
C:\platform-tools>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT54PYJ04176
all:
finished. total time: 0.155s
C:\platform-tools>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.031s
Tried even to flash the TWRP recovery but couldn't succeded
C:\platform-tools>fastboot flash recovery twrp-2.8.5.0-hima.img
target reported max download size of 536870912 bytes
sending 'recovery' (35928 KB)...
OKAY [ 1.391s]
writing 'recovery'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.422s
Read on many threads about OEM unlock but how to unlock if i can't boot and get into system
is there any way to unlock it via fastboot
Any other help will be appreciated
Sorry if that question has already been asked and addressed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If fastboot isn't working in download mode you've probably bricked it. Find the stock firmware it was using, in zip format and flash it via the external sd method.
Thanks for your quick response. But unfortunately i didn't notice its stock FM before Is there any way to fetch that from phone ?
How to know if the phone is charge enough to flash the rom ? or is there a way to do charge as now when i connect it to charger or pc it pop up into boot screen mode where i think it doesn't charge by itself untill there are some specific command via fastboot which i am not aware of it !
Any guidance will be appreciated, thanks for your time and help
There is a way to charge the phone, it will take hours but give it a try:
https://xinyustudio.wordpress.com/2...custom-rom-flashing-battery-too-low-to-flash/
BTW command
Code:
fastboot getvar battery-voltage
will tell you the battery voltage, you should check how many milivolts does your battery have when fully charged.
stgFX said:
There is a way to charge the phone, it will take hours but give it a try:
https://xinyustudio.wordpress.com/2...custom-rom-flashing-battery-too-low-to-flash/
BTW command
Code:
fastboot getvar battery-voltage
will tell you the battery voltage, you should check how many milivolts does your battery have when fully charged.
Click to expand...
Click to collapse
Thanks for your response, but unfortunately it doesn't show any information with that command
C:\platform-tools>fastboot getvar battery-voltage
battery-voltage:
finished. total time: 0.031s
I actually have the same problem with the battery, I start to think that the phone is dead for good...
Just go with the latest firmware for the carrier and region it came from. If it fails report back.
shivadow said:
Just go with the latest firmware for the carrier and region it came from. If it fails report back.
Click to expand...
Click to collapse
It doesn't goto download mode or via sd card method its a same.
Does sd card needs to be in exFat or FAT32, i think i tried 2 different card both doesnt start flashing option
Thanks
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Hey,
I have the same issue, did you ever find a solution?
You must unlock first
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"
bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working
Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.
For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK
Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)
josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?
Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.
Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151
So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?
No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool