Problem restoring backed up roms - HTC One X

Hi! i flashed a CM10 rom and i already had two backed up (one is the official and the other is a custom rom).. i have never restored a rom any time before but today i was trying to restore the official one and, as it didn't work, i tried to restore the second one with also no success.. i was able to restore this CM10 though.. what was happening is that after the restore was complete i selected reboot (from clockwork mod) and it started booting but only showing the first boot image (htc quietly brilliant image) and then rebooting at this point repeating this as a loop.. any ideas of what could be happening? could it be the boot.img file? thanks for your help

You have to reflash the appropriate boot.img file for the ROM you're restoring. You can find it the folder with your backups on the sdcard

Porsche.V said:
Hi! i flashed a CM10 rom and i already had two backed up (one is the official and the other is a custom rom).. i have never restored a rom any time before but today i was trying to restore the official one and, as it didn't work, i tried to restore the second one with also no success.. i was able to restore this CM10 though.. what was happening is that after the restore was complete i selected reboot (from clockwork mod) and it started booting but only showing the first boot image (htc quietly brilliant image) and then rebooting at this point repeating this as a loop.. any ideas of what could be happening? could it be the boot.img file? thanks for your help
Click to expand...
Click to collapse
Always keep a backup of your backed up Roms on your PC. (The file can be found in the 'clockworkmod' folder located in the SD card's root directory.
Once you are done with the process of flashing the recovery file through Clockwork Mod, reboot your phone into fastboot, flash the boot.img through command prompt.
fastboot flash boot boot.img
fastboot erase cahce
fastboot reboot
It should reboot after that :good:

thanks a lot for the help!

now that i am trying to flash the boot.img from my first backed up rom (official) i am getting from cmd:
C:\Android\fastboot\fastboot2>fastboot boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 1.109s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.149s
any idea?

wrong command line.. i was missing the "flash".. sorry

Porsche.V said:
now that i am trying to flash the boot.img from my first backed up rom (official) i am getting from cmd:
C:\Android\fastboot\fastboot2>fastboot boot boot.img
creating boot image...
creating boot image - 8390656 bytes
downloading 'boot.img'...
OKAY [ 1.109s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.149s
any idea?
Click to expand...
Click to collapse
hi
use the fastboot tool attached and do this
1. replace the existing boot.img with the one from ur back up
2. get ur phone into fast boot mode
3.connect ur phone via USB to ur pc u will see the fastbootUSB word on ur phone
4. in side the tool click on install-boot window and do as the screen says if it says ok u are good to go:good::laugh:

Related

[Q] HTC One X bricked?

Hi
I rooted and installed a CyanogenMod ROM on my One X and decided to revert back to stock using the backup I had created. I forgot to backup the boot.img though and it's now stuck in a boot loop.
I have access to fastboot but when I select recovery it displays the HTC logo white screen and doesn't progress from there. I've tried to flash the latest CWM recovery however when I send it I get an error message back:
sending 'recovery' (5742 kb)... FAILED (remote: (00000004))
I was flashing the latest recovery in the hope of being able to mount sd card and flash a new ROM/boot.img.
I've searched and searched and I've been unable to find any information that helps. :crying:
Please help me!
Mitch
mitchger said:
Hi
I rooted and installed a CyanogenMod ROM on my One X and decided to revert back to stock using the backup I had created. I forgot to backup the boot.img though and it's now stuck in a boot loop.
I have access to fastboot but when I select recovery it displays the HTC logo white screen and doesn't progress from there. I've tried to flash the latest CWM recovery however when I send it I get an error message back:
sending 'recovery' (5742 kb)... FAILED (remote: (00000004))
I was flashing the latest recovery in the hope of being able to mount sd card and flash a new ROM/boot.img.
I've searched and searched and I've been unable to find any information that helps. :crying:
Please help me!
Mitch
Click to expand...
Click to collapse
If you can enter fastboot USB, you shouldn't have any problems flashing CWM touch, maybe you have a corrupt CWM image - here is a perfectly working version.
http://db.tt/VF9J2eo8
Just in case you don't know,
Place the IMG in the folder that contains fastboot, adb etc in Android SDK - ie platform tools
Open CMD whilst phone is in fastboot USB,
CD c:/Android-SDK/platform-tools
fastboot flash recovery CWM.img
Good luck
Sent from my Nexus 7 using Tapatalk 2
You can only flash the boot.img using fastboot.
The boot.img is in the nandroid backup.
If you can't access recovery you could try fastboot erase cache
sent from my One X using xda venom premium

Boot loop - flashing via fastboot works, adb does not.

Okay, so I tried my best to search the forums and read the Q+A first, but the suggestions I've found so far didn't help me solve my problem.
I started with Hasoon200's tool kit and successfully unlocked the boot loader. Then, however, I got stuck at installing CWRM (it just wouldn't boot into recovery after installing). So I gave it a try with the "One X one Click" tool kit. I downloaded the n3okernel v34 and -modules as well as the newest nightly build of Cyanogen Mod (cm-10.1-20130414-NIGHTLY-endeavoru).
Now my HOX is caught in a boot loop. No matter which option I choose (fastboot / hboot, recovery, factory reset), it'll always go to the white HTC screen and stay there. Since Q+A's Q11 mentions it: yes, the last time I could boot into the OS (then still the stock image) I disabled fast boot in power settings.
Currently I can only access my HOX via fastboot, I already got a stock image and extracted the boot + recovery images, which I then flashed with the fastboot utility, as suggested in the Q+A's Q9. I erased the cache and rebooted to no avail. I also tried the firmware executable (RUU_ENDEAVOR_U_ICS_40_O2_DE_1.26.207.2_Radio_1.1204.90.13_release_251288_signed) to no avail.
Q+A's Q15 suggests sideloading via adb, but adb won't recognize my device.
I've also relocked the bootloader, this was suggested in another online ressource after flashing the stock boot+recovery images.
The phones HBOOT Version is 1.36.0000. I've noticed a different radio version than the one mentioned in my downloaded RUU; phone says 5.1204.162.29, downloaded file says 1.1204.90.13. I've not yet found a working download link with the right version number.
Please help.
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Mr Hofs said:
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Click to expand...
Click to collapse
Unlocking the bootloader works, but I'm not able to enter the recovery mode. It only shows a black screen (see attached picture).
EDIT: ok, wait... after flashing the clockwork recovery, I'm now getting into recovery mode. Will now try the next steps you suggested and give feedback later. Thanks a lot so far!
Press the Power and Volume down buttons which will take you the the hboot screen. From there select fastboot and flash a custom recovery like CWM via fastboot.
Now select hboot again and then select recovery!
Okay, so I successfully flashed CWM. I'm now able to boot into recovery. I also succeeded in flashing a boot.img which i took from cm-10.1-20130414-NIGHTLY-endeavoru.zip
c:\One\One\Data>fastboot flash boot boot.img
sending 'boot' (4960 KB)...
OKAY [ 0.684s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.498s]
finished. total time: 1.186s
Now - when selecting hboot - the phone gets to another screen, the one where it displays the "HTC One" logo; I tried flashing the CM-image using fastboot (adb still doesn't work), but got following error message:
c:\One\One\Data>fastboot flash /sdcard update.zip
sending '/sdcard' (200098 KB)...
OKAY [ 25.507s]
writing '/sdcard'...
FAILED (remote: not allowed)
finished. total time: 25.716s
So close, yet so far...
So you have a working CWM installed right?
After flashing the boot.img... do "fastboot erase cache"
now go to CWM(recovery) and mount your sd card... copy the CM10ROM.zip and the gapps.zip to your HOX...
after that select wipe data and then wipe dalvic and cache...
Now select install zip from SD and install the ROM and then the gapps... reboot!
The problem is that I can't - or could'nt - transfer files any other way than using fastboot. However, I've now flashed Team Win TWRP2, and finally I'm able to access my phone over adb or just mount it and access it via explorer. Phew.
FINALLY!
So, if another noob like me finds this thread in the future...
After installing the TWRP2 recovery with flashboot flash twrp2.img, then booting into recovery and mounting my device, I was able to copy the CM-ROM-zip file onto the HOX. Then I rebooted into fastboot again and flashed the boot.img from aforementioned zip-file using "fastboot flash boot boot.img".
Booted again, selected the recovery system, installed ROM from zip file.
I'm getting too old for this ****. Almost had a heart attack when I thought I had bricked my phone. Thanks everyone for holding my hand, I appreciate it.
Good mate !
CASE CLOSED !

[Q] Cannot Boot Into Temporary Custom Recovery

Hey guys. I am attempting to boot into custom recovery to make a backup of my stock rom with stock recovery intact. Here's what I have done so far:
(Fastboot and ADB is up and running)
1) Downloaded the custom recovery
2) Placed custom recovery in my ADB/Fastboot file folder location
3) Renamed custom recovery img to recovery.img
4) checked md5 sums in adb
5) adb booted to fastboot
6) entered cmd: fastboot boot recovery.img
Once I do that it says :
downloading 'boot.img'...
OKAY [ 1.139s]
booting...
OKAY [ 0.001s]
finished. total time: 1.143s
BUT nothing happened. It stays in fastboot on the phone and freezes the phone. What in the entire hell am I doing wrong?
UPDATE: Nevermind. I pulled the recovery image out of Zar's decrypted RUU file and flashed it. Then I just did a full backup in adb

Help please - bricked/bootloop

Hi guys, posted this under the TWRP thread but realised it might be a more general problem
ISSUE: I believe I bricked the phone or bootloop (sorry not familiar with terminology). After the splash screen the word ASUS shows with a never ending circle loading sign under it. I can't enter recovery using Power + Vol down
BACKGROUND: I am having some issues after doing the Tethered Recovery. I am rooted and have bootloader unlocked. Once I used cai_dat_CWM.bat and was in recovery, I tried to flash the clean rom HarfainX, but before I did, I did a wipe of Cache and it said formatting cache but after 10 minutes didnt load. So I turned off the phone, now it hangs on the ASUS screen. I can enter fast boot, but I cant enter recovery mode.
Can anyone help me in getting it back running again?
Update:
Tried doing a wipe through fastboot -w
and got the following results:
Erasing 'userdata' OKAY
Sending 'userdata' OKAY
Writing 'userdata' FAILED (remote: flash_cmds error!)
Thanks
You should've waited.
Posted using my phone.
jose makalolot said:
You should've waited.
Posted using my phone.
Click to expand...
Click to collapse
I did wait it just didn't do anything for about 10 minutes.
I'm trying to sideload using ADB the stock rom from ASUS / Garbage free ROM by Harfain X and I am getting:
adb.exe sideload update.zip
loading: update.zip
error: device not found
fastboot update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
Anyone can offer suggestions?
...Flashed untethered TWRP... fixed the problem .. thanks TheSSJ for creating it

device unable to boot Error - mdtp image is corrupted

Hi there,
I have a problem i was try to root my phone.
Now i dont have access to ADB but only fastboot works.
If i start my phone it goes on fastboot mode, and if i try "fast boot twrp-3.3.0-0-daisy.img" i get the error "device unable to boot Error - mdtp image is corrupted"
Can some one help me out, if tried to download the image again but without success..
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
a1291762 said:
You don't need twrp for root?!
I guess you need to get a fast boot ROM and flash it. Don't relock the bootloader. Don't flash data. Just all the other partitions.
Maybe even just flash that partition. My phone has a and b. Should just need to flash the current one.
Click to expand...
Click to collapse
Sorry im a little bit noob, but how it works:
flastboot flash a?
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
a1291762 said:
fastboot flash mdtp_a mdtp.img
That file is in the images folder after you extract the fastboot ROM.
Click to expand...
Click to collapse
mj2o said:
Hi,
while having 15 years of Linux experience, I've just dropped into the same issue on my first hour of Android exploration. Currently no OS is installed and the phone boots into fastboot. Booting into twrp-3.3.1-dees_troy-daisy.img failes also with "Error - mdtp image is corrupted".
I've flashed mdtp.img from V10.0.12.0.PDLMIXM as described, but still I get the same error when booting into twrp-3.3.1-dees_troy-daisy.img . Is there somewere a documentation, how to proceed in such a case?
Click to expand...
Click to collapse
No OS installed is maybe cause the last rom that you flashed was not flashed in the right slot or correctly flashed.
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
SubwayChamp said:
Also the fastboot command mentioned here is to flash mdtp in "a" slot but you have to see first which is your active slot and then install it on it.
Click to expand...
Click to collapse
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
mj2o said:
I've searched more for the reason and once got the response: FAILED (remote: partition table doesn't exist)
So it sounds I have to recreate the partition table. I haven't found any fastboot command to request the current partition status.
Click to expand...
Click to collapse
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
I have the same problem, what you have did to fix? please
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
hi
same issue here @mj2o: Can you please provide a link to the site in English; it all in Chinese and I cannot read it
Thanks
mj2o said:
Hi,
I've downloaded and flashed the factory image from miui.com. This way I have reset all my efforts and started all over. You find there the full rom and a flashing guide for the Xiaomi Mi A2 Lite.
Click to expand...
Click to collapse
SubwayChamp said:
I don´t think that exist a command to diagnose status of partitions but I´m sure that if you try to flash on an inactive slot then won´t work, ever an inactive slot will give you a fail.
Check your active slot by typing
Code:
fastboot getvar current-slot
and then flash it on the active slot using "mdtp_a" or "mdtp_b" but ONLY if the active slot is actually with all the system on it it´s mean that if you deleted all your system and any of both are actually with partitions running (no matter that with errors) then won´t work this way as you expect.
Click to expand...
Click to collapse
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
BenG7 said:
@mj2o;80151263:
Code:
fastboot getvar current-slot
returns -->
Code:
current-slot: INVALID
finished. total time: 0.008s
and
Code:
fastboot flash aboot aboot.img
returns -->
Code:
target reported max download size of 534773760 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.055s]
writing 'aboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.075s
please advise.
Click to expand...
Click to collapse
Why do you want to flash the bootloader, what is the issue?
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Device unable to boot. Error - mdtp is corrupted
BenG7 said:
Hi @SubwayChamp
I wanted to flash LO16
Did a wpie data -yes format
Then a wipe system as instructed and now im stuck in fast boot.
Click to expand...
Click to collapse
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Thanks SubwayChamp,
Will try as advised and keep you updated.
I m going to look for the fastboot rom for my daisy.
SubwayChamp said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use
Code:
fastboot flash mdtp_a mdtp.img
and
Code:
fastboot flash mdtp_b mdtp.img
(you will get the images from any of the full fastboot roms)
From there try again the steps recommended by OP in that thread to get that your device boots on LOS but this is other question concerning only to that thread
Click to expand...
Click to collapse
@SubwayChamp
dit it and when I
Code:
fastboot reboot
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
[EDIT]
realised I can
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
and I can flash the twrp-installer-daisy-3.3.1-0-offain.zip
but if I want to reboot; it says
Code:
No OS installed! Are you sure you wish to reboot?
so I went on with flashing lineageos 16
but at the end of the flash, I get
Code:
Failed to mount '/system' (permission denied)
please advise
BenG7 said:
If your issue is related with mdtp partition then you should to install again this image through fastboot in both slots in order to can boot device again to recovery; use and
@SubwayChamp
dit it and when I
it boots straight back to fastboot.
What next? Mi a2 Lite stuck at Fastboot - No recovery, no nothing! Help ?
Thanks for your help!
Click to expand...
Click to collapse
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
SubwayChamp said:
Your recovery is missed now cause when you flashed LOS was overwritten and device can't boot to system cause some step failed in the process.
If you flashed successfully mdtp images now follow the steps to boot to recovery and then follow those indicated to install LOS.
Click to expand...
Click to collapse
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
Code:
fastboot boot twrp-daisy-3.3.1-0-offain.img
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
BenG7 said:
Thanks; this is what I did:
from TWRP I rebooted to recovery
it took me straight to fastboot again
so I
again and mounted system partition then I flashed LOS
and the process went fine this time but when I rebooted to the system
it's back to fastboot again!
Click to expand...
Click to collapse
This is exactly what I tried to tell you: your issue concerning to this thread was solved.
Now you have an issue regarding how to flash and boot to system attempting to install LOS. TWRP is perfectly capable to mount/remount or unmount partitions if needed, no need an action from the user, this is not the reason why you are not booting but the method and steps is discussed more properly in the same thread.
From here you can take one of hese three routes:
- To insist with trying to flash LOS.
- Flash other rom or a previous known working rom.
- Return completely to stock by flashing a full global rom.
Just I could recommend that for the future when you flash a stock rom take a backup of the most important partitions (without userdata) this could avoid that you need to use EDL anymore.

Categories

Resources