Develop Bugs

Problem restoring backed up roms

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:

HELP. HOX is dead

Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?

How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?

I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?

the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/

It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.

BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.

I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?

BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.

IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.

IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.

BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/

IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.

What I dont get is why you didn't just root/unlock bootloader via htcdev.com

RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.

IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.

BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.

I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.

BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.

IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.

BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.

[Q] I'm worried I killed my phone

I decided earlier today that I'd try to root my one X, but I wound up screwing up to the point that I'm lost. I accidentally wiped the system while in recovery, and when I rebooted, it kept looping. By pressing the power/down button, I can get into the bootloader, and from there into recovery. In the recovery, I was able to look around using a file manager but only found empty folders.
I used adb push to try to get a rom onto the phone, but I'm not able to flash it. When I go to reboot, it informs me that there's no OS installed.
If anybody has any idea what I can do, it would be much appreciated.

im assuming you already unlocked your phone
1.Enter fastboot by holding power + volm down.
2.Select fastboot
3.plug in USB
4.flash recovery with the command: 'fastboot flash recovery <name of recovery here>
5.flash the boot.img that came with the ROM, usually it's located within the zip file
6.erase cache using command: 'fastboot erase cache'
7.select Hboot to return to main menu
8. go to recovery
9. wipe data/factory reset, wipe cache, wipe dalvik from advanced options, format system from mounts and storage menu
10. in mounts and storage, select mount usb
11. copy over ROM zip
12. Install from ZIP
13. reboot system
PS. your phone is only bricked if it can't turn on. obviously it's not going to boot up if there is nothing to bootup, lol

Just ensure your recovery is a recent version, like clockworkmod 5.8.4.0, otherwise mounting won't work.

Thanks for the quick reply. I don't entirely understand how to flash the recovery, however.
I assume I'm running the command on the computer. How do I know what to type in as the recovery?

Mate, did you even do your research before attempting any of this?
Anyway,
Make sure you got HTC sync installed, also Android SDK
1/ Open to a command prompt by going: start -> type in cmd
2/ browse to your folder containing fastboot and adb using the 'cd' command
e.g. My fastboot folder is located at "C:/htc/fastboot" so I would type: 'cd C:/htc/fastboot'
If you're using the one from SDK it could look like C:\Users\Steven\AppData\Local\Android\android-sdk\platform-tools
3/ enter the commands -fastboot flash recovery ...., fastboot flash boot.... etc.

Not nearly as well as I should have. I learned the hard way I guess. Thanks for putting up with my cluelessness though.
I've done as you said, but when I tried to boot into the recovery, I got stuck on it looping the "htc quietly brilliant" screen.

You sure you flashed it Successfully?
and downloaded clockworkmod from here?
http://forum.xda-developers.com/showthread.php?t=1594819

Code:
D:\Android>fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
< waiting for device >
sending 'recovery' (5742 KB)... OKAY [ 1.021s]
writing 'recovery'... OKAY [ 1.506s]
finished. total time: 2.528s
D:\Android>fastboot flash boot boot.img
sending 'boot' (4988 KB)... OKAY [ 0.885s]
writing 'boot'... OKAY [ 1.257s]
finished. total time: 2.142s
D:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.116s]
finished. total time: 0.116s
Could it be that I have a bad boot.img? I'm using one out of the renovate 8.1.0 ROM.

I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?

seaneschen said:
I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?
Click to expand...
Click to collapse
what command are doing? to unlock i mean
or better yet run through the steps u do to unlock bootloader

ali3nfr3ak said:
what command are doing? to unlock i mean
Click to expand...
Click to collapse
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev

seaneschen said:
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev
Click to expand...
Click to collapse
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2

elmonen said:
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I have the US version.

seaneschen said:
I have the US version.
Click to expand...
Click to collapse
i would suggest that you post this in the in the AT&T, Rogers HTC One X, Telstra One XL forum as thiforum is for the international one x

Oh my....... never noticed. Please don't use Clockworkmod and instead use TWRP, you might brick

Help! I can't flash!

Hi guys! I'm with a big stupid problem. I'm trying to flash the stock rom 4.2.2 (JDQ39)
When I try to flash the system.img i get this message:
writing 'system'...
FAILED <Write Fail>
Finished. total time 43.266s
I'm very desperate...
My nexus is a Yakju Maguro, from Brazil. I'm stuck at bootloader. Can't flash the system. Without that, I cant boot my phone. I even can't user a recovery to flash a zipped rom.
What should I do?

Roraito said:
Without that, I cant boot my phone. I even can't user a recovery to flash a zipped rom.
Click to expand...
Click to collapse
wrong.
'fastboot flash recovery twrp_or_cwm.img', then directly from bootloader select for Recovery Mode with volume keys, press power, done you're in recovery, use 'adb push /path/to/rom_filename.zip /sdcard/', reflash.

Twrp disappears after loading, recovery Red Triangle NO Command

Getting confused.
Loaded Nougat on my Nexus 5x... unlocked boot loader, loaded TWRP 3.0.2-2 rebooted, saw TWRP,
Moving files to the phone to restore using TB, but have not yet done SUPERSU.. reboot back into recovery, Android Flat on back Red Triangle, No command??
Can reboot into the phone it works, just can't get back to TWRP for reasons I can't figure out.
Feels like I missing a step, but can't figure out what. Looked at a lot of pages, but nothing really stands out.
Update: Used fastboot boot [twrp imagename].img
And it got me directly to TWRP. Able to load SuperSU then.
Update #2: What I didn't make clear in this original post was I did in fact flash the TWRP recovery, it just didn't stick.
Command used originally:
Code:
C:\SDK\platform-tools>fastboot flash recovery twrp-3.0.2-2-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.579s
My mistake was to then reboot where it was apparently overwritten hence the confusion.

krelvinaz said:
Getting confused.
Loaded Nougat on my Nexus 5x... unlocked boot loader, loaded TWRP 3.0.2-2 rebooted, saw TWRP,
Moving files to the phone to restore using TB, but have not yet done SUPERSU.. reboot back into recovery, Android Flat on back Red Triangle, No command??
Can reboot into the phone it works, just can't get back to TWRP for reasons I can't figure out.
Feels like I missing a step, but can't figure out what. Looked at a lot of pages, but nothing really stands out.
Update: Used fastboot boot [twrp imagename].img
And it got me directly to TWRP. Able to load SuperSU then.
Click to expand...
Click to collapse
The reason that happens is if u fastboot boot twrp.img u will only have a temporary twrp until u reboot..if u had typed fastboot flash recovery recovery twrp.img then when u reboot the recovery would be permanent...
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
The reason that happens is if u fastboot boot twrp.img u will only have a temporary twrp until u reboot..if u had typed fastboot flash recovery recovery twrp.img then when u reboot the recovery would be permanent...
Click to expand...
Click to collapse
Actually, I did use flash the recovery. It came up just fine. However, after a reboot, when I booted back to recovery I got the No Command.
I had to re-flash TWRP, and then reboot back to Recover from TWRP, then reboot, then it worked like it should.

The command you posted was to boot a recovery, not to flash one in the recovery partition.
Anyway, you can't just flash TWRP and boot, because the boot will replace stock recovery, you got to flash supersu/another kernel from the recovery after flashing for it to stick.

You Can try this adb command :
fastboot flash recovery twrp_3.0-2-2.img
fastboot boot twrp_3.0-2-2.img
And normaly it's ok you have twrp installed

Thanks for the other responses...
Just to confirm what I did originally (I just unrooted so that I could use Magisk and PPH Root)
Code:
C:\SDK\platform-tools>fastboot flash recovery twrp-3.0.2-2-bullhead.img
target reported max download size of 536870912 bytes
sending 'recovery' (16433 KB)...
OKAY [ 0.421s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.579s
However, If after doing this I rebooted the phone etc... TWRP was no longer there again. I had to do the same, force a boot to twrp, and then install Magisk before rebooting for it to stick.
Just in case someone else runs into this confusion.
I am now on Android 7 Nougat on a Nexus 5X with Magisk using PPH Root and can now use Root, Android Pay and some other apps which won't run with root enabled. Happy Camper for now.

The step your missing is after you fastboot flash the recovery don't reboot the phone just yet. You have to reboot the bootloader by typing fastboot reboot bootloader. After doing that use the volume up button to access recovery. Once you do that then you can start the phone.
Sent from my Nexus 5X using Tapatalk

krelvinaz said:
However, If after doing this I rebooted the phone etc... TWRP was no longer there again. I had to do the same, force a boot to twrp, and then install Magisk before rebooting for it to stick.
Click to expand...
Click to collapse
If you boot with a stock boot.img the android boot process will replace your recovery partition with stock if the SHA256 for the recovery doesn't match what it expects. The way you can stop this is to modify your boot.img, which would happen if you install SuperSU prior to first android boot after a new flash.