what i was doing is that i upgrading my one x through these few step,
1. Download the ROM and place it on your virtual SD card.
2. Relock your bootloader using the commend 'fastboot oem lock'.
3. Go into fastboot mode and type 'fastboot oem rebootRUU'.
4. Flash the new firmware using the commend 'fastboot flash zip firmware.zip'.
5. On first time running the commend you will see FAILED, don't panic and just run the commend again.
6. Reunlock your bootloader via HTCDev.
7. Flash custom recovery using the commend 'fastboot flash recovery recovery.img'.
8. Download boot.img and flash it using the commend ‘fastboot flash boot boot.img’.
9. Use the commend 'fastboot erase cache' to avoid boot issues.
10. Go into recovery and install the ROM.
11. Reboot your device and enjoy from JB!
here are the result, i can't flash the firmware:crying:
{
"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"
}
and in hboot it said:
***relocked***
***security warning***
in starting to boot hboot, some red words appear: " this build is for developing only.....etc"
are these normal?
Well looks like it's corrupted, the firmware.zip isn't meant to be 294kb in size... more like 13mb. Redownload it.
The red words are appearing because you relocked your bootloader and have a custom recovery installed. Once you successfully flash the firmware and reflash Clockworkmod recovery, unlock the bootloader again and it will disappear.
Don't flash software intended for ENDEAVORU phone on the EVITA.
Sounds like you're in the wrong forum, this is for the quad core Tegra 3, yours is the dual core Snapdragon, right?
Related
Hello everyone,
I really could need some help. I'm new to this forum and new to "rooting" an android device. I did a lot of reading before I made my first try, but how it seems not enough :crying:.
I followed the instructions in this thread. Everything worked as described just fine and I didn't get any errors. I did the following:
1) Unlock the bootloader
2) Flash custom recovery from fastboot - fastboot flash recovery openrecovery-twrp-2.8.3.0-m8.img
3) Flash boot.img from fastboot - fastboot flash boot boot.img
4) Fastboot erase cache - fastboot erase cache
5) Boot into custom recovery and flash root and busybox
6) reboot into bootloader
7) flash stock recovery - fastboot flash recovery stock_recovery.img
8) reboot device
The last step doesn't work. I'm stuck in the bootloader. Every time I try to reboot the device, the bootloader starts. When I choose "HBOOT" I get the following messages:
{
"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"
}
Now I think, I did not realize that dual sim version of the m8 is different from the single sim version. Am I right here? Or did I just miss something? Is there any way to fix this and get my device working again? Do I need a boot.img for the m8_dugl? Can perhaps anyone provide it? Every help is really appreciated! I'm totally stuck here
Many thanks in advance
Guss
Problem solved with boot.img from this Post. Thanks to Captain_Throwback.
My phone hasn't gotten OTAs in a while and is still on MDA89E.
I'm trying to update to MDB08M using the factory image from google. So I did 'adb reboot bootloader' and ran the 'flash-all.bat', but ended up getting this error message:
{
"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"
}
Can anyone help me out?
I'm ultimately going to be flashing the modified boot img for 08M so that i can decrypt
You need to update your platform tools. Check file date of fastboot you are using.
nvertigo said:
Can anyone help me out?
Click to expand...
Click to collapse
The flash-all script wouldn't work for me. I kept getting the same error message as you. I flashed each .img file separately. Here are the instructions.
Unzip the factory image, and unzip the .zip within that, so that all of the .img files are within the same folder. Then:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot erase cache
fastboot flash cache
Reboot
Note that I didn't flash data.img, which means your data remains safe.
Witek_M said:
You need to update your platform tools. Check file date of fastboot you are using.
Click to expand...
Click to collapse
Any idea where I can get the latest platform tools without installing Android Studio?
whats this vendor.img? never saw that one yet.
jdawg0024 said:
Any idea where I can get the latest platform tools without installing Android Studio?
Click to expand...
Click to collapse
From here I chose option "Stand-alone SDK Tools".
I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy (SS) I drop SS with Adb comand prompt too
{
"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"
}
Domol™ said:
I have uncloked bootloader and I Flashed TWRP Recovery via ADB and when I send comand "adb reboot recovery" I have the Android guy[/IMG]
Click to expand...
Click to collapse
Hey I had this exact same problem just a few moments ago. I didn't necessarily fix it but I found a different way of installing TWRP:
Basically what I did was temporarily boot into the recovery image I had (instead of properly flashing it) and then flashed a zip version of the recovery which works permanently.
To do that, go into the bootloader as normal (adb reboot bootloader) and then use [fastboot boot {filename}.img] (so replace filename with whatever file you have) to boot into the recovery temporarily, then flash the recovery zip.
Here's the link to the zip I used: https://www.androidfilehost.com/?fid=24407100847292484
UPDATE: OK turns out after a few reboots the recovery went back to not working, but I did try another method which definitely works. Temporarily boot into the recovery image as above, but this type install a Supersu zip. This will root the phone. Then boot into the phone as normal, install Flashify from the Play Store and use that to install the recovery image (which you should move onto the phone).
Here are some links:
Supersu zip I used: http://download.chainfire.eu/supersu-stable
Flashify: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en_GB
Hi,
I have a problem regarding my LG G3 (D852)
I was stupid enough to use someone's .bat file in order to unlock the bootloader.
It deleted the boot partition on it and went into Fastboot mode.
Problem is:
I accidentally replaced the Download Mode with a Recovery mode, which does not even work.
So, I can't access the Download Mode to re-install the stock system.
BUT I do have a backup of my Download Mode in a laf.img file.
I know that I need to use the following code to flash my Download Mode back
Code:
fastboot flash laf laf.img
BUT when I use this command, it sends it correctly but gets stuck in "writing 'laf' ..."
Even if I try to erase Download Mode, it stays stuck in "erasing 'laf'... "
Every command I use (that involves writing and erasing) on Fastboot on this device, it stays stuck for some reason.
What I've tried:
Code:
fastboot continue
Code:
fastboot erase laf
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
What I can't do:
I can't use Download Mode
I can't access my Recovery Mode (needs to be flashed)
I can't Write or Erase on Fastboot
I can't boot my device, it goes automatically in Fastboot
Can it be my drivers? I installed my Fastboot drivers from this thread http://forum.xda-developers.com/showthread.php?t=2588979
{
"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 don't know what else to try. I really need this phone to work.
I have the stock ROM and the flash tool ready to install this phone, but I only need my Download Mode to work.
Thanks in advance, I hope there is someone out there that can help me fix this.
I unlocked the bootloader of my Huawei y6 (atu-l21) 2 days ago. Now the problem is that I can't get working custom roms for twrp.
I had downloaded many .ZIP files but the zip file always contained only one image. When I wanted to download the ZIP file via twrp bottles, I always got a red message "invalid zip file format!
Does anyone have working custom ROMs for the Huawei y6 (atu-l21)
{
"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"
}
By you meaning by one file contains img file, you are trying to flash compressed gsi/treble image.
The installation procedure is different for treble devices. Instead do:
First you must uncompress it & do "adb reboot bootloader" & "fastboot flash system [UNCOMPRESSED_IMG_FILE]", wipe data by "fastboot -w", final reboot ur device "fastboot reboot"
do you think I should e.g. extract the customrom.zip to customrom.img and then the image with the commands Flash
Yes, Only if zip archive contains one *.img file like aonly, ab... etc
can I also flash the .IMG file via twrp. because when i try dan i don't know which partition to select.
System-Image
I just tried it and the message "Image is too large for the device" appears
You may read THIS POST about your device custom rom.
And if ab image doesn't work for you try aonly
Jannikoks06 said:
I just tried it and the message "Image is too large for the device" appears
Click to expand...
Click to collapse
Try with fastboot method
I'll do it later I'll report if it worked
Danielisko said:
Try with fastboot method
Click to expand...
Click to collapse
I did it but the phone doesn't boot, only the screen appears where it says that the bootloader on the phone has been unlocked