[Unlock ] Official Unlock via HTCdev! - HTC ChaCha

The HTC Chacha can now be officially unlocked via HTC's HTCdev bootloader unlock tool:
{
"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"
}
(This is also confirmed to work on HTC Status, thanks jlopez0978)
1) Unlock: Prepare for Unlock via HTCDev then unlock as explained here (you can find a small fastboot & adb kit here, no need to install the whole sdk).
2) Root: You should be able to root using the Doomlord root tool.
3) Install CWM Recovery: Download CWM 5.0.2.7 for Chacha and flash it using fastboot (see detailled instructions by Yorzua here)
Code:
fastboot flash recovery recovery.img
4) Flash custom rom like SuperOSR / CM7
5) Enjoy!

YES! F*****G YES! I'm already S-OFF'd via the XTC-Clip, but gonna do this unlock anyways.
12:45am where I live, and this just made my day!
EDIT 1: I kept getting "model ID" errors, so I had to extract the rom.zip from the RUU.exe and apply it manually from HBOOT.
EDIT 2: Just a tip, the recovery can be fastboot flashed. From what I've read in the Wildfire S section, boot.img's will need to be fastboot flashed too if you didn't S-OFF via the XTC-Clip.
EDIT 3: Seems like you can fastboot flash everything but radios and HBOOTs - I fastboot flashed a boot.img and a system.img of a nandroid backup of the 1.54.401.2 stock ROM - I could see this being very useful.

now that there is s-off available, should we request that the htc chacha be shifted back to the main forum instead of allow it to remain in the legacy section?

fi3ry_icy said:
now that there is s-off available, should we request that the htc chacha be shifted back to the main forum instead of allow it to remain in the legacy section?
Click to expand...
Click to collapse
Let the activity build up for a couple of days then message an admin.
I'm from the wildfire s forum and we were put in legacy, but after a polite message to admin (not from me) we're back in action.

I unlocked the boot loader but it still says s-on!

ts3010 said:
I unlocked the boot loader but it still says s-on!
Click to expand...
Click to collapse
It won't s-off
Bootloader unlocked means you can root and flash custom roms
You can't flash hboot and radios
Also your phone wont be network unlocked

ts3010 said:
I unlocked the boot loader but it still says s-on!
Click to expand...
Click to collapse
I'm not sure that's relevant... You could't be S-On but unlocked (being able to flash non signed files)
Have you done the fastboot oem unlock part? Did it fail??
Can you report the output of:
Code:
fastboot.exe getvar -all

I followed the guide in this topic http://forum.xda-developers.com/showthread.php?t=1184118 and put PH06IMG.zip in the root of sdcard and when i boot in boot loader it find the file and say
Parsing...[PH06IMG.zip]
that's it and do nothing after that so what is the problem?

ts3010 said:
I followed the guide in this topic http://forum.xda-developers.com/showthread.php?t=1184118 and put PH06IMG.zip in the root of sdcard and when i boot in boot loader it find the file and say
Parsing...[PH06IMG.zip]
that's it and do nothing after that so what is the problem?
Click to expand...
Click to collapse
Same problem here.
UPDATE: Tried with the chinese one: http://forum.xda-developers.com/showthread.php?t=1280569 ,
and then it said: "Main version is older" and made me reboot.

All the guides for chacha are friggin confusing anyways. Everybody assumes HTCDEV bootunlocker put your phone to S-OFF.
Well it doesnt... After HTCDEV unlock it is still S-ON but UNLOCKED. Which still has its limitations.
Its so annoying, all I want is root so I can delete some of the stock apps to free some space. I dont need fancy custom roms etc. Because after the 5-6 apps I installed, the phone basically is unusable because after a few weeks there will be only 10-15mbs left. And mind you, I moved everything possible to the SD card.
If this phone isnt so unusable, I wouldnt even bother rooting/unlocking it.

dapaua said:
Same problem here.
UPDATE: Tried with the chinese one: http://forum.xda-developers.com/showthread.php?t=1280569 ,
and then it said: "Main version is older" and made me reboot.
Click to expand...
Click to collapse
ok, let's try that:
extract the recovery.img from the PH06IMG.zip and flash it using fastboot, now that you should be able to do it:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img

laapsaap said:
All the guides for chacha are friggin confusing anyways.
Click to expand...
Click to collapse
Feel like helping and write some clearer instructions?

adlx.xda said:
ok, let's try that:
extract the recovery.img from the PH06IMG.zip and flash it using fastboot, now that you should be able to do it:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
when i do this i got
C:\android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.000s
I tried fastboot flash recovery recovery.img with out erase and it worked finaly

ts3010 said:
when i do this i got
C:\android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.000s
Click to expand...
Click to collapse
thanks, edited the OP.
what is the output of :
fastboot getvar -all

>moto-fastboot.exe getvar -all
getvar:-all FAILED (remote: unknown command)

I rooted my chacha

laapsaap said:
>moto-fastboot.exe getvar -all
getvar:-all FAILED (remote: unknown command)
Click to expand...
Click to collapse
damn it! could you try those?
fastboot getvar secure
fastboot getvar unlocked

But
I have an Arabic Version and I did follow all the above steps and i cant get any sign that it working .. I really need Root what shall i do now
This is my Bootloader after i did flash the ( PH0611000_Chacha_hboot_1.10.0000.exe ) from the HTCdev.com

ts3010 said:
I rooted my chacha
Click to expand...
Click to collapse
how you did it

your boot loader is still locked you need to unlock it first from htcdev

Related

HTC sensation bootloop

Hi!
On my phone I have venom rom until yesterday work very good , but today, when i installed one kernel via venom hub, my phone on restart keep bootloop
I can access to 4ext recovery, I try to wipe all, to reistall rom, to install another rom but nothing, is always bootloop
How can I fix that problem?? Please help meeee
Thx to all
Dario
dariodisgusto said:
Hi!
On my phone I have venom rom until yesterday work very good , but today, when i installed one kernel via venom hub, my phone on restart keep bootloop
I can access to 4ext recovery, I try to wipe all, to reistall rom, to install another rom but nothing, is always bootloop
How can I fix that problem?? Please help meeee
Thx to all
Dario
Click to expand...
Click to collapse
S-ON or S-OFF?
if you are S-ON enable smartflash from recovery and then flash the rom
otherwise flash the boot.img of the rom manually
see here http://forum.xda-developers.com/showthread.php?t=1631861 (extra 1 step)
rzr86 said:
S-ON or S-OFF?
if you are S-ON enable smartflash from recovery and then flash the rom
otherwise flash the boot.img of the rom manually
see here http://forum.xda-developers.com/showthread.php?t=1631861 (extra 1 step)
Click to expand...
Click to collapse
Sorry, the phone is S-OFF
When i enter to 4ext, it says "4EXT smartflash is currently set to update your boot partition on next system start.
Is this wanted or should it be removed?
Remove smartflash? YES or NOT
dariodisgusto said:
Sorry, the phone is S-OFF
Click to expand...
Click to collapse
ok let's do this
from 4ext recovery go
tools
format all partitions except sdcard
then flash the rom
if that doesn't work too follow the second option in my previous post(flashing boot.img manually)
but in any case don't enable smartflash because you are S-OFF
rzr86 said:
ok let's do this
from 4ext recovery go
tools
format all partitions except sdcard
then flash the rom
if that doesn't work too follow the second option in my previous post(flashing boot.img manually)
but in any case don't enable smartflash because you are S-OFF
Click to expand...
Click to collapse
I try to format all and then install the rom but not fix the problem, now I try with boot.img (but what is boot.img? where I found this file?)
Thx
dariodisgusto said:
I try to format all and then install the rom but not fix the problem, now I try with boot.img (but what is boot.img? where I found this file?)
Thx
Click to expand...
Click to collapse
open the rom.zip and you will see the boot.img
extract it and place it in the folder where you have adb and fastboot files
check in settings from your device if you have usb debugging enable
boot your device into bootloader
connect it to pc(it will say fastboot usb)
now in the white space of the folder do shift + right click and choose open command window
then do these commands
fastboot flash boot boot.img
fastboot reboot
then see if it will boot up
best wishes
rzr86 said:
open the rom.zip and you will see the boot.img
extract it and place it in the folder where you have adb and fastboot files
check in settings from your device if you have usb debugging enable
boot your device into bootloader
connect it to pc(it will say fastboot usb)
now in the white space of the folder do shift + right click and choose open command window
then do these commands
fastboot flash boot boot.img
fastboot reboot
then see if it will boot up
best wishes
Click to expand...
Click to collapse
When I launch command: "fastboot flash boot boot.img" I have this message;
"sending 'boot' (4904 KB) ...OKAY
writing 'boot' ...FAILED (remote; not allowed)
finished. total time 1.467s"
What is this?
dariodisgusto said:
When I launch command: "fastboot flash boot boot.img" I have this message;
"sending 'boot' (4904 KB) ...OKAY
writing 'boot' ...FAILED (remote; not allowed)
finished. total time 1.467s"
What is this?
Click to expand...
Click to collapse
maybe it requires to have htc drivers installed
do you have them?
dariodisgusto said:
When I launch command: "fastboot flash boot boot.img" I have this message;
"sending 'boot' (4904 KB) ...OKAY
writing 'boot' ...FAILED (remote; not allowed)
finished. total time 1.467s"
What is this?
Click to expand...
Click to collapse
You need the juopunut hboot to allow fastboot flash commands.
The easiest option is disable SmartFlash in 4EXT
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
rzr86 said:
maybe it requires to have htc drivers installed
do you have them?
Click to expand...
Click to collapse
I installed "HTCDriver3.0.0.007" is it right? Then I disable smartflash from 4ext but I ave the same error!
Please helpppp
dariodisgusto said:
I installed "HTCDriver3.0.0.007" is it right? Then I disable smartflash from 4ext but I ave the same error!
Please helpppp
Click to expand...
Click to collapse
what is your hboot version?
maybe you need the juopunut hboot as Jonny suggaested
i can't think something else right now
rzr86 said:
what is your hboot version?
maybe you need the juopunut hboot as Jonny suggaested
i can't think something else right now
Click to expand...
Click to collapse
I have that HBOOT:
{
"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"
}
probably then you need the juopunut hboot as Jonny suggested before which is also unlocked and you can perform commands
rzr86 said:
probably then you need the juopunut hboot as Jonny suggested before which is also unlocked and you can perform commands
Click to expand...
Click to collapse
but now it is easier to return to the stock version? Because I saw that joupunut hboot is not very easy to do
dariodisgusto said:
but now it is easier to return to the stock version? Because I saw that joupunut hboot is not very easy to do
Click to expand...
Click to collapse
i think the only thing you have to do is to follow the instructions where are mentioning at the top of the site
where did you see of returning to the stock version?
dariodisgusto said:
but now it is easier to return to the stock version? Because I saw that joupunut hboot is not very easy to do
Click to expand...
Click to collapse
nahh ..you are already SOFF ...no need to do wire trick again ..
you just need to flash juopunutbear HBOOT ..its as simple as flashing custom recovery from fastboot ..thats all
check troubleshoot point #3 from my soff guide(link in my signature) ...the easiest way to flash juopunutbear hboot is given there

I can't change the rom HOX AT&T, why?

I follow almost every tutorial on our forum but i can't change the rom.
I unlock the bootloader with All in one toolki by hasson, unlock the root, I check with HxD the CID (11111111) but I can´t make s-off, I tryed cyanonenMod, CarbonRom, and another else but my HOX don´t work, always return to RUU (Relocked the bootloader).
I'm sure some people would love to help you but your post is in the wrong section. This should be in the Q&A section.
Sent from my One XL using Tapatalk 4
rammx said:
I follow almost every tutorial on our forum but i can't change the rom.
I unlock the bootloader with All in one toolki by hasson, unlock the root, I check with HxD the CID (11111111) but I can´t make s-off, I tryed cyanonenMod, CarbonRom, and another else but my HOX don´t work, always return to RUU (Relocked the bootloader).
Click to expand...
Click to collapse
Wrong topic.
You need to give us the phone's status rightnow. If it locked bootloader and running original RUU, the work will be simple for you.
Also tell us why you could not soff, and another thing is you are very lucky when flashing RUU before s-off, ur 1x not brick.
Thread moved to proper section, please next time read the rules before posting
This information can help?
{
"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"
}
You're s-on so you need to flash the boot.img manually using fastboot after you flash the ROM, that's why the ROMs aren't booting.
Extract the boot.img from the ROM zip on your pc, it's in the root folder of the zip. Put it in your fastboot folder.
After you flash the ROM, reboot to bootloader and connect your phone to the pc, wait for it to say fastboot usb on your phone screen.
Open a command prompt from within your fastboot folder and issue this command:
fastboot flash boot boot.img
Now you can reboot your phone and the ROM should boot up.
Sent from my Evita
timmaaa said:
You're s-on so you need to flash the boot.img manually using fastboot after you flash the ROM, that's why the ROMs aren't booting.
Click to expand...
Click to collapse
Yup yup. This is by far the most common reason for ROM not booting.
Boot.img will not work if you are s-on (and any hboot 1.14 or later). You simply have a kernel mismatched to your ROM.
timmaaa said:
You're s-on so you need to flash the boot.img manually using fastboot after you flash the ROM, that's why the ROMs aren't booting.
Extract the boot.img from the ROM zip on your pc, it's in the root folder of the zip. Put it in your fastboot folder.
After you flash the ROM, reboot to bootloader and connect your phone to the pc, wait for it to say fastboot usb on your phone screen.
Open a command prompt from within your fastboot folder and issue this command:
fastboot flash boot boot.img
Now you can reboot your phone and the ROM should boot up.
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
Yup yup. This is by far the most common reason for ROM not booting.
Boot.img will not work if you are s-on (and any hboot 1.14 or later). You simply have a kernel mismatched to your ROM.
Click to expand...
Click to collapse
Humm... I need change the Kernel or update the boot.img by fastboot? (How to?)
I would like install this rom to test http://forum.xda-developers.com/showthread.php?t=2382933
I explained how in my last post.
Sent from my Evita
rammx said:
Humm... I need change the Kernel or update the boot.img by fastboot? (How to?)
Click to expand...
Click to collapse
The post you just quoted (from timmaaa) explians how to do it.
timmaaa said:
You're s-on so you need to flash the boot.img manually using fastboot after you flash the ROM, that's why the ROMs aren't booting.
Extract the boot.img from the ROM zip on your pc, it's in the root folder of the zip. Put it in your fastboot folder.
After you flash the ROM, reboot to bootloader and connect your phone to the pc, wait for it to say fastboot usb on your phone screen.
Open a command prompt from within your fastboot folder and issue this command:
fastboot flash boot boot.img
Now you can reboot your phone and the ROM should boot up.
Sent from my Evita
Click to expand...
Click to collapse
Hi Timmaaa
Ok, let me understand something:
I have the Carbon Nighttly, I need extrac the boot.img from them, and install by fastboot to HOX, after copy the Carbon ZIP to the sdcard and from recovey install the ZIP rom??
I have the TWRP 2.5.0.0 Recovery.
Yes that's exactly right.
But.....
You need to change your TWRP recovery version to 2.6 because the version you have (2.5) is full of bugs and doesn't install/wipe properly. You can download TWRP 2.6 here. Then put the file in your fastboot folder and issue the following commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter your new version of TWRP and install Carbon, then reboot to bootloader and flash the boot.img.
Sent from my Evita
timmaaa said:
Yes that's exactly right.
But.....
You need to change your TWRP recovery version to 2.6 because the version you have (2.5) is full of bugs and doesn't install/wipe properly. You can download TWRP 2.6 here. Then put the file in your fastboot folder and issue the following commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you can enter your new version of TWRP and install Carbon, then reboot to bootloader and flash the boot.img.
Sent from my Evita
Click to expand...
Click to collapse
One second....
After install the TWRP 2.6 by fastboot I need make the WIPE?
Steps:
1.- Install TWRP 2.6
2.- Fastboot boot.img
3.- Wipe delvin, system and cache
4.- install the rom from zip
I´m ok?
(sorry I´m beginner on Android)
rammx said:
One second....
After install the TWRP 2.6 by fastboot I need make the WIPE?
Steps:
1.- Install TWRP 2.6
2.- Fastboot boot.img
3.- Wipe delvin, system and cache
4.- install the rom from zip
I´m ok?
(sorry I´m beginner on Android)
Click to expand...
Click to collapse
No need to be sorry. But yes, you must follow my instructions above exactly to change your recovery.
When you wipe in TWRP use the advanced wipe feature and select cache/dalvik cache/factory reset/system. Then flash the ROM, then reboot to bootloader and flash the boot.img. Then you can reboot your phone into the ROM.
Sent from my Evita
---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
By the way, instead of using a Carbon nightly, you should use the stable 1.8 release which is the most recent and is also a very good/stable ROM. You can find it here.
Sent from my Evita
timmaaa said:
No need to be sorry. But yes, you must follow my instructions above exactly to change your recovery.
When you wipe in TWRP use the advanced wipe feature and select cache/dalvik cache/factory reset/system. Then flash the ROM, then reboot to bootloader and flash the boot.img. Then you can reboot your phone into the ROM.
Sent from my Evita
---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
By the way, instead of using a Carbon nightly, you should use the stable 1.8 release which is the most recent and is also a very good/stable ROM. You can find it here.
Sent from my Evita
Click to expand...
Click to collapse
timmaaa, thanks!!!! it's working my new rom!
Great news
PS. if someone helps you here, please hit the thanks button :thumbup:
Sent from my Evita

Relock bootloader of LeEco Le 1S ?

Is it possible to relock the bootloader of LeTV Le 1S ?
er.davinder said:
Is it possible to relock the bootloader of LeTV Le 1S ?
Click to expand...
Click to collapse
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
Thanks for replying, what if someone with custom recovery/boot image lock the bootloader. It would hard brick the device ?
Use sp tool method to flash stock recovery/boot image and userdata to recover after bricking.
By the way to to unlock bootloader
er.davinder said:
Thanks for replying, what if someone with custom recovery/boot image lock the bootloader. It would hard brick the device ?
Click to expand...
Click to collapse
You can backup necessary partitions and restore them after lock or unlock with SP Flash Tool.
vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
after jumping back to stock recovery and relocking boot loader can we able to download and flash OTA directly?
vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
cmd print
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to solve this?
letv le 1s stuck on eui
hello guys
I am sorry to write this random mesage here
I have Letv Le 1s phone tried to root it but messed it up, now my phone stuck on eui logo.
basically my phone was encrypted with password and fingerprint.
now I have downloaded original stock rom but unable to flash that to get my phone back, as when I am in recovery not seeing sd card and no other option.
In flashboot mode it was saying orange lock mode now saying red lock cant unlock it and not sure how to flash stock rom and recover my phone back.
your help will be much appreciated.
many thanks
hjunqq said:
cmd print
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to solve this?
Click to expand...
Click to collapse
I have the same situation, how to resolve this?
The PC doesn't see the device while its in fastboot mode. When should I press the Volume + key?
{
"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 want to lock the bootloader to get the stock OTA fw update.
I am still on 5.9.020S
I can only use the local update with update.zip fw file to move to 023S. I earlier switched back to 020S.

(SOLVED)Help with fastboot for install twrp downloading boot.img

Hello , sorry for my bad english , i have a moto z3 play model xt1929-6 , i unlock the bootloader with program "minimal adb and fastbood", now i try to boot the img of recovery but the program say "
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp-3.5.0_9-0-beckham.img
downloading 'boot.img'..." and stays there.. .
the command what i use is " fastboot devices----fastboot boot "boot.img or name of img".
pls 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"
}
try renaming twrp-3.5.0_9-0-beckham.img to a.img then place a.img into My Computer>Local Disk ( C: )
then type
Code:
fastboot flash boot C:\a.img
ADB hate spaces and symbol on .img files ...
ineedroot69 said:
try renaming twrp-3.5.0_9-0-beckham.img to a.img then place a.img into My Computer>Local Disk ( C: )
then type
Code:
fastboot flash boot C:\a.img
ADB hate spaces and symbol on .img files ...
Click to expand...
Click to collapse
still the problem , downloading boot.img
danilolegenda said:
still the problem , downloading boot.img
Click to expand...
Click to collapse
what error?
ineedroot69 said:
what error?
Click to expand...
Click to collapse
danilolegenda said:
View attachment 5241261
Click to expand...
Click to collapse
why you using
Code:
fastboot boot
and not
Code:
fastboot flash boot
are you trying to backup your partition before going full root??
don't do fastboot flash boot you will not have stock boot.img backup you can try
Code:
fastboot erase boot
fastboot boot a.img
ineedroot69 said:
are you trying to backup your partition before going full root?? don't do
fastboot flash boot you will not have stock boot.img backup you can try
Code:
fastboot erase boot
fastboot boot a.img
Click to expand...
Click to collapse
i try to boot the twrp for install this like a see in tutorial, try fastboot flash boot ?
i try to follow this tutorial
danilolegenda said:
i try to boot the twrp for install this like a see in tutorial, try fastboot flash boot ?
Click to expand...
Click to collapse
fastboot flash boot command is permanent (you will have permanent TWRP recovery installed on your phone)
fastboot boot command is temporary (It would just load TWRP temporary and used for mainly file recovery or backup)
it's depends on your decision
ineedroot69 said:
fastboot flash boot command is permanent (you will have permanent TWRP recovery installed on your phone)
fastboot boot command is temporary (It would just load TWRP temporary and used for mainly file recovery or backup)
it's depends on your decision
Click to expand...
Click to collapse
ahhh ok, then can I install the twrp using the img and the command "fastboot flash boot"? is it just to install the recovery? Sorry I haven't done these procedures for a long time.
that video is not full guide its does not show how to backup partition incase your phone does not boot anymore after installing TWRP ...
do you have stock rom of your phone just incase it does not boot again?
yes fastboot flash boot just make sure it's correct version of TWRP you are flashing
ineedroot69 said:
that video is not full guide its does not show how to backup partition incase your phone does not boot anymore after installing TWRP ...
do you have stock rom of your phone just incase it does not boot again?
yes fastboot flash boot just make sure it's correct version of TWRP you are flashing
Click to expand...
Click to collapse
i have a stock rom of android 9 but no have a back up of this, the file is corretly from this link "https://dl.twrp.me/beckham/twrp-3.3.1-0-beckham.img.html" I thought it was installed with the zip but in the video they show with the img.
ineedroot69 said:
that video is not full guide its does not show how to backup partition incase your phone does not boot anymore after installing TWRP ...
do you have stock rom of your phone just incase it does not boot again?
yes fastboot flash boot just make sure it's correct version of TWRP you are flashing
Click to expand...
Click to collapse
I have already tried to flash the recovery but it tells me that the file is too big to send it, the latest version of twrp weighs 33mb
danilolegenda said:
I have already tried to flash the recovery but it tells me that the file is too big to send it, the latest version of twrp weighs 33mb
Click to expand...
Click to collapse
Did it success? The biggest img file I fastboot flash is 2.4GB which is system.img. Just ignore the filesize warning
ineedroot69 said:
Did it success? The biggest img file I fastboot flash is 2.4GB which is system.img. Just ignore the filesize warning
Click to expand...
Click to collapse
i try with one command "fastboot flash recovery (and here the img file) with this say the file is so much bigger, I was scared by what you said that I could stay without starting the phone anymore D:
danilolegenda said:
i try with one command "fastboot flash recovery (and here the img file) with this say the file is so much bigger, I was scared by what you said that I could stay without starting the phone anymore D:
Click to expand...
Click to collapse
I agree with that mindset kinda risky also it's kinda terrible how to tell to your mother you broke your phone because you followed an Indian tutorial on youtube
thou like Adolf Hitler said " Your strength is only as strong as your commitment "
ineedroot69 said:
I agree with that mindset kinda risky also it's kinda terrible how to tell to your mother you broke your phone because you followed an Indian tutorial on youtube
thou like Adolf Hitler said " Your strength is only as strong as your commitment "
Click to expand...
Click to collapse
I can't agree with you so much
ineedroot69 said:
I agree with that mindset kinda risky also it's kinda terrible how to tell to your mother you broke your phone because you followed an Indian tutorial on youtube
thou like Adolf Hitler said " Your strength is only as strong as your commitment "
Click to expand...
Click to collapse
i try again but have the same problem look at this.
The problem has been solved , the problem is a windows 10 , i try with windows 7 pc and I was able to do the whole. procedure.

HP Slate 21 S100 Booting Failed

Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
{
"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"
}
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
gokhanc5 said:
Spoiler: didnt want to clog the thread with repeats of your pics
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
Click to expand...
Click to collapse
id reflash the stock firmware and re-root from there should you choose to do so
Youdoofus said:
id reflash the stock firmware and re-root from there should you choose to do so
Click to expand...
Click to collapse
thank you you answered. I'm uploading boot.img and recovery.img via fastboot. it does not give an error but comes to the same screen again. where am I doing wrong. Can you tell me exactly how to do it one by one.
@gokhanc5
As I can see your phone stucks in Fastboot ( AKA Bootloader ) mode: in Android device's boot-mode is set by ro.bootmode property - what can be normal, recovery or fastboot - which is set in Android's system file named build.prop.
Simply flashing some images as you did doesn't cause this property gets reset.
Typically you reset device's boot-mode property by means of ADB and/or Fastboot commands
ADB
Code:
adb devices
adb reboot
Fastboot
Code:
fastboot devices
fastboot reboot
jwoegerbauer said:
[USER = 11583799] @ gokhanc5 [/ USER]
Telefonunuzun Fastboot (AKA Bootloader) modunda takıldığını görebildiğim gibi: Android cihazının önyükleme modu, Android'in build.prop adlı sistem dosyasında ayarlanan ro.bootmode özelliği tarafından ayarlanır - normal, kurtarma veya fastboot olabilir .
Yaptığınız gibi bazı görüntüleri basitçe yanıp sönmek, bu özelliğin sıfırlanmasına neden olmaz.
Genellikle aygıtın önyükleme modu özelliğini ADB ve / veya Fastboot komutları aracılığıyla sıfırlarsınız.
ADB
[kod]
adb cihazları
adb yeniden başlatma
[/ kod]
Fastboot
[kod]
fastboot cihazları
fastboot yeniden başlatma
[/ kod]
Click to expand...
Click to collapse
OEM lock is on.
I'm installing recovery.img in fastboot mode.
fastboot flash recovery recovery.img
then when I turn it off and on again it comes to the fast boot mode screen.
I tried all the recovery.img files.
but it didn't happen.
Fast Boot Mode screen
Start - restart booting failed
Power Of
Recovery Mode - restart booting failed
Restart bootloader - restart booting failed
Can you describe how to do it from the very beginning?
gokhanc5 said:
...
Can you describe how to do it from the very beginning?
Click to expand...
Click to collapse
Already told you what to do.
jwoegerbauer said:
Sana ne yapacağını zaten söyledim.
Click to expand...
Click to collapse
I cannot enter anywhere except fastboot.
I cannot install TWRP.
fastboot devices
fastboot reboot
I'm doing these things, nothing changes.
i'm a beginner
sorry
jwoegerbauer said:
Already told you what to do.
Click to expand...
Click to collapse
I tried what they said
usb debugging is turned off
What will I change in the build.prop file.
What should I do for ro.bootmode?
I will be glad if you answer
I tried a lot but couldn't find a solution.
my hope is you
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
jwoegerbauer said:
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
Click to expand...
Click to collapse
thank you for everything.
but I could not.
-------------------------
fastboot oem unlock
(bootloader) Bootloader is already unlocked.
OKAY [0.008s]
finished. total time: 0.008s
-----------------------------------------
fastboot devices
3CQ3400QG9 fastboot
-----------------------------------------
fastboot flash bootloader Bootloader_phobos_4.4.2.img
target reported max download size of 641728512 bytes
sending 'bootloader' (7137 KB) ...
OKAY [0.266s]
writing 'bootloader' ...
FAILED (remote: (InvalidState))
finished. total time: 0.422s
-------------------------------------------------- ------
thank you for your help
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
jwoegerbauer said:
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
Click to expand...
Click to collapse
gave the same error again.
I downloaded it from 3 different places, the same error in all of them.
fastboot flash bootloader command fails
fastboot flash boot command works but the problem is the same

Categories

Resources