Ok, so when I turn on the phone, it gets stuck on the HTC screen logo forever. With the volume down and power button, I'm able to get into hboot/hboot usb plug when connected to the computer. The recovery, factory reset, image crc options don't work. In my linux computer, when I type fastboot devices, I'm able to get serial number of the phone. The picture links below summarize my current state
{
"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"
}
The commands that I've tried are below.
(command): /fastboot devices [output] SH******** fastboot -- (note: here I did get my serial number but I know better than to post it here.
(command): ./fastboot oem rebootRUU [output]... FAILED (status malformed (1 bytes))
(command): ./fastboot flash zip PD15IMG.zip [output]: sending 'zip' (322693 KB)... FAILED (status malformed (1 bytes))
Tools in hand: android-sdk-linux, linux mint, PD15IMG.zip and phone
note: I also tried all of the above commands on windows 7 home premium 64 bit with adb installed and got the same error messages from fastboot. I tried the official htc bootloader unlocker but kept getting that error: 120 battery less than 30%.. although my battery is fully charged and that stopped the tool from unlocking the boot loader.
I read somewhere If i find the orginal stock recovery image, I might get out of this but I cannot find it anywhere yet.
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
RUU?
gesange said:
Just find the stock RUU and you can revert it back to life
When you cant find it google it and for sure you will get the RUU
Sent from my shooteru using Tapatalk 2
Click to expand...
Click to collapse
Yeah I tried RUU and it gets stuck all the time at Rebooting bootloader or waiting for bootloader
Related
Next Sunday,I was downgrading the hboot(from 7.00 to 1.13,I want to install RUU in my mobile phone) by this course:
Enter there command in the cmd.exe:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img :*maybe this backup.img can solve this problem.but how can I do?*
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 :*the hboot.img is a hboot_7.96 image*
reboot bootloader
:waiting for reboot
fastboot flash hboot hboot_1.13.0000.img :*when I run this command,a power failure has happened,the computer has shutdown*
And after I rebooted my computer.my mobile phone's screen is went out.I can't boot my mobile phone anymore.No matter how I press [power key], the screen is still dark !!!
Luckly,when I reconnect the USB cable,the power light was bright.And computer has identific my mobile phone.
The adb command is disabled.And I have tried some fastboot command.These are some result:
fastboot devices
{
"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"
}
*why my devices became #00000000000*
fastboot getvar all
*the program is stop,but never exit.*
*but why it is all in messy code except version&version-baseband&imei*
fastboot flash hboot hboot_1.13.0000.img
*I would retry this command.buy I failed....*
*why sending OK,But writing FAILED?*
*and I have tried write the hboot 0.98(the hboot_0.98.0002_0e35ea5b_0318.img in RUU) in.but it FAILED ,too!*
fastboot erase HBOOT
*someone tell me to erase it before writing it in,but I found I can't do it*
fastboot reboot & fastboot reboot-bootloader
*as like very normal,but the screen never bright*
*and we also tried the fastboot oem command,maybe it is the only way to repair my smart phone*
But when I disconnect between the phone and computer,the power light never put out,why?
Who can help me to save my mobile phone?
Don't tell me the hardware has broken down.I will crazy,because there is no one in our city can repair it !!!
if you have any idea ,please send a email to me.my email is [email protected] ,thank you!!!
Congratulations you have destroyed your bootloader. There is no hboot for Desire S with number 1.13
Our versions are 0.98.x, 6.98.x, 2.0x.x and 7.0x.x
So you have flashed one that belongs to other device and destroyed your system.
I guess your hardware is fine, but now only JTAG can revive your phone as far as I know.
Of course you can still try to download and flash a proper hboot image but I doubt it will succeed
Sent from my HTC Desire S
Hello guys, last week I installed the unofficial port of MM from here http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 and everything was going well until yesterday the screen got frozen. I tried to reboot the tablet but It got frozen in the nvidia boot logo, so I tried to reinstall the ROM through fastboot. This step is when I realized that I cant write sometimes through fastboot. I can go into this mode but sometimes the writing failed until now everytime it fail. This is the error reported on the screen:
writing 'boot' ...
FAILED (remote: (FileWriteFailed)
This is a screen capture of the command window:
{
"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 think that I have broken the bootloader but I cant find the bootloader img for the tablet. Any help will be thanked!
If fastboot is working you still have a working bootloader. You are in fact in the bootloader. I'm not sure why fastboot write would fail. Perhaps the Windows fastboot driver should be reinstalled.
The bootloader is flashed by a "blob" file and is included with restoration images. If the bootloader does get damaged somehow, you can only boot to APX mode and only Nvidia can repair that.
Try do download and use minimal ADB.
Also reinstall the fastboot driver on your PC (deleting tablet from control panel/system/.... and connecting it again and istall again the driver you download from nvidia site or here on XDA)
best thing you can do if fastboot commadn don't work (happen to me) is download a recovery imagere (again nvidia developer site or here on XDA) and use the flashall.bat.
Magic done for me
and u can use it when u have only Apx? .... i cant find driver for it ... i have only black screen alltime
helllo ..! but still the above case wil work for the deactivated shield's..? my sheilds are now in apx mode..
Sent from my SHIELD Tablet using xda premium
If you can only boot APX mode you are stuck. There's no driver for APX mode so you can't do anything with it. Only NVidia can repair it at that point.
I don't know if this may be important but two days before this happened I encrypted the tablet. this may be affect the bootloader? The tablet is still unusable since I can't flash anything thought fastboot starts.
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"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"
}
Any idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
{
"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 can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
hpernaf said:
I have a Samsung J400M and since the 23rd of May I am trying to solve the error "Could not do normal boot. Invalid Kernel Length". The device was running Android 9 and this error appeared without any explanation.
I can only access the device's download mode.
OEM and FRP are locked and I cannot unlock and I cannot identify my binary number.
I tested firmwares and several versions (new and old) of Odin, but so far I have not achieved any positive results.
I tried to solve by FWRP, but I was also not successful, because I believe that with OEM blocked, I can't get anything. Right?
The image below is the Odin screen. That was as far as I could go so far.
Can anybody help me?
How can I unlock the OEM on this device without having access to Android? Any other solution?
Click to expand...
Click to collapse
Unlock the boot loader with fast boot if possible with Samsung phones. If you can flash twrp which I presume you can't, flash RMM bypass zip and hope for the best. Good luck.
my zenfone 4 problem:
it is charging but i am stuck at asus logo with rotating circle and whenever i am trying to get into droid boot it is showing an android with yellow helmet
{
"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"
}
As long as a phone powers on it's NOT hardbricked, but softbricked if Android doesn't get properly started.
even if it is soft bricked i am not able to get into recovery mode this was showing:
Re-flash phone's STOCK ROM.
damn, i am not able to get into fastboot dude that's what it is all about if i would be able to get into fastboot i would have flashed my phone long time ago.when i ty to get into fastboot android sign with yellow helmet appears.
My zenfone 4 problems:
access to droidboot or recovery (stuck at android icon with a yellow helmet), so i cant flash a rom or firmware.
Tried different combo keys, but always stuck with that android icon.
You typically re-flash a STOCK ROM by means of ADB Sideload method.
ook so for using adb sideload method u need to get into droid boot what i am saying it i am not able to get into droid boot mode and everytime i try an android sign with yellow helmet appears.
You are absolutely WRONG.
What you have to do is running ADB commands as follow
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_FILE_ON_PC_HERE>
i am noob please can u tell me the steps elaborately OKAY,
NOW I HAVE GOT IT BUT IS NOT SOWING ANY DEVIICES I HAVE CONNECTED MY MOBILE SEE:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB commands.
jwoegerbauer said:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB comso
Click to expand...
Click to collapse
so,now what should i do?