Related
Hello All.
This is the first time I have tried to put a custom ROM on an HTC so I am still learning the ropes.
I tried to follow the instructions in the first post. So... In sequence, this is what I did...
HTC One X unlocked with htcdev.com (S-ON) or S-OFF (coming soon)
This seemed to go without a hitch. On the HBoot screen (I think that is what it is called) it tells me I am now unlocked.
ClockworkMod Recovery or 4EXT Touch Recovery (coming soon)
I installed the official version as per the instructions here.
The last instruction that seemed to work successfully was this:
Code:
fastboot flash boot recovery-clockwork-touch-5.8.2.4-endeavouru.img
Then I tried
Code:
fastboot reboot
which put me into recovery mode.
<EDIT> The instructions here have now been corrected to:
Code:
fastboot flash recovery recovery-clockwork-touch-5.8.2.4-endeavouru.img
</EDIT>
Choosing the reboot option from recovery just bounces me back into recovery mode but I understand from the instructions I should be able to boot into a working phone!
Has something gone wrong?
If I use the volume down + power button I can enter HBoot mode. From here I can select Fastboot. Connecting via USB to my computer seems to work fine, as I see Fastboot USB on my phone, and I when I execute this...
Code:
fastboot devices
I get something like this
Code:
List of devices attached
HTXXXXXXXXXX device
I am now unsure how to continue because I think something has gone wrong and I should have a working phone at this point.
Do I press ahead and try to install the Firmware package from here? Unless this lets me boot into a working phone (which I don’t believe it will), it still leaves me with the problem that for a One X, without a removable SD card I don’t know how to transfer and run the "Super Wipe" script, nor transfer and flash Android Revolution ROM via recovery.
Do I need to do something with
Code:
fastboot flash
?
Please help as she is threatening to dump me for destroying her 2-day-old phone.
It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.
delete please
anko184 said:
It's
Code:
fastboot flash [B]recovery[/B] recovery-clockwork-touch-5.8.2.4-endeavouru.img
not boot..
Solution for you is to go into bootloader, flash recovery with the command i gave you and then reboot into recovery and install the rom..
After that everything should be ok and your phone will boot into ARHD without any problem.
Click to expand...
Click to collapse
Thanks
It looks like the instructions I followed previously had an error then.
<EDIT> The instructions were incorrect, but have now been corrected </EDIT>
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???
mwhincup said:
Thanks
It looks like the instructions I followed previously had an error then.
I will follow your instructions. But what about the RUU that is mentioned in the instructions? It is not clear how or when I should flash it. Presumably I flash the RUU before I do the ARHD flash... ???
Click to expand...
Click to collapse
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.
anko184 said:
You don't need to flash any RUU or firmware unless your phone wasn't shipped with 1.26, which i don't think it was.
Just try flashing the recovery with the correct command and then the rom. If your phone doesn't boot after that then you may try the firmware but i'm sure you won't need it.
Click to expand...
Click to collapse
So, I understand that you are telling me:
Flashing CWM recovery will rectify my current problem and restore my phone to a workable state.
Booted normally, I can copy the ARHD ROM to the internal SD (not sure what the location for this will be).
I then reboot into recovery and 'Install Zip from SD card'.
Click to expand...
Click to collapse
Is this correct?
mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Sent from my HTC One X using XDA
mwhincup said:
So, I understand that you are telling me:
Is this correct?
Click to expand...
Click to collapse
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.
bagofcrap24 said:
Wait before you flash anything, if you don'talready have arhd on your internal sd you may be in trouble if you do superwipe
Click to expand...
Click to collapse
Good advice, I am sure. However my problem now is getting into a working phone so that I can transfer the ROM onto the internal SD.
Can't wait to get home and try it!
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good
animaleyes76 said:
Without trying to sound like a ****, if you don't understand what you are doing you should read more to understand the whole process before attempting it.
Click to expand...
Click to collapse
You are correct of course, however, there comes a point where the only way to learn is to actually do something. I have flashed numerous ROMS on my Galaxy S, and before doing this I have read numerous guides trying to better understand the procedures for HTC devices.
I have tried to follow what appeared to be a step-by-step guide, however, either there has been a malfunction, or it appears there may be two important bits of information missing from that guide:
Flashing CWM recovery leaves the phone in a state that it won't boot normally, and consequently...
The ARHD ROM should be loaded onto the internal SD at the very beginning of the procedure
Click to expand...
Click to collapse
Thanks all of you so much for your effort. It's much appreciated.
bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
Click to expand...
Click to collapse
@bagofcrap24 I may have misled you with a typo in the first post. (See my edit)
d'oh
edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition
bagofcrap24 said:
edit : just read updated info
so what happens when you choose recovery and press power from the hboot screen
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
power on with voldown
press voldown to select recovery
press power to select recovery
you should either see CWM or the stock recovery
again looking at what you have written, if you just do a normal reboot and its putting you straight into recovery then you probably have flashed recovery onto the boot partition
Click to expand...
Click to collapse
I'll get back to you with some definitive answers in 3 hours or so. Sorry, I'm at work now.
bagofcrap24 said:
so what happens when you choose recovery and press power from the hboot screen
Click to expand...
Click to collapse
power on with voldown
press voldown to select recovery
press power to select recovery
Click to expand...
Click to collapse
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
i'm understanding that when doing a normal reboot it just sends you straight into hboot?
Click to expand...
Click to collapse
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.
mwhincup said:
I get a circular yellow 'recycling' symbol, followed a few seconds later by a magenta triangle with an exclamation mark. (Is this the stock recovery?). Then the phone restarts and I end up back in the Clockworkmod recovery.
No. A normal reboot (without holding the Vol down key) sends me straight to clockworkmod recovery.
I can get to HBoot with Vol down+Power on startup.
Click to expand...
Click to collapse
Right this means you did mess up the boot and recovery partitions, the one where you have the exclamation mark is the stock recovery which means you didn't flash cwm to the recovery partition.
the fact that you get to recovery on a normal boot also suggests as I suspected that you have flashed recovery on to the boot partition, follow the instructions I put up earlier about flashing the boot.IMG and redo the recovery.IMG and you should be fine
Sent from my HTC One X using XDA
bagofcrap24 said:
what you have done is replaced your boot sector with a recovery image, that is the reason why you cant boot your phone as normal so even flashing the recovery correctly will not allow your phone to boot up.
as your phone cannot boot up you cannot transfer any files to the internal memory of your phone in order to flash ARHD
at present there is a problem with the official version of ClockworkMod Recovery so i personally would reccommend using the interim version HERE
and flash with fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img
As you have [email protected]$ked your boot partition up you will also want to download THIS
this is an insecure boot image (thanks to paul from modaco) I have just extracted the part you will need from his package
with this you will need to be in fastboot again and type fastboot flash boot boot.img
obviously you will need to copy both of the files to the same directory as fastboot is on your PC in order to send them
by flashing the boot section with the insecure boot here it will allow your phone to boot up normally again, once it has booted normally you can then copy the ARHD and superwipe to your internal SD card
to access recovery
power off phone by holding power button for 10seconds
power on with power+voldown
select recovery from hboot screen with voldown then power to select
your phone will reboot and then you will be in recovery
do a nandroid backup incase anything goes wrong
then flash the superwipe script
then flash ARHD 1.2.2
all is good
Click to expand...
Click to collapse
Your analysis is quite correct. All is indeed good! Thanks very much. The boot image worked as described. I will now transfer Superwipe and the ROM.
Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA
bagofcrap24 said:
Make sure you do a nandroid backup first, it was lucky this time but if you mess up your system partition you may find yourself with no way of putting files on without unrooting and restoring the ruu
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again
mwhincup said:
Done!
Everything worked as you said it would.
I now have ARHD installed and running brilliantly.
Thanks again
Click to expand...
Click to collapse
Glad you fixed it and sorry for being a bit harsh earlier.. was having a bad day
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
VBQ24 said:
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
Click to expand...
Click to collapse
Download a ROM onto your computer, connect to your phone in recovery, mount the sdcard, move the ROM from your computer onto your phone's sdcard, and flash from recovery. No need for RUU.
Dont forget to wipe.
wipe data/factory reset and format all partitions (except sd card) from recovery.
Go to bananagranolas link in her signature, you'll find everything you need there.
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
VBQ24 said:
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
Click to expand...
Click to collapse
As long as you are S-OFF and have a custom recovery (CMW or 4EXT) you are able to flash any custom rom you like. Just make sure that you make a full wipe before the flashing (wipe data/factory reset, wipe cache partition, format system or in 4ext recovery just choose format all partitions except sdcard).
That should leave you up and running again.
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
EDIT: Upon trying to flash the JellyTime AKOP Rom I get a message saying install from SD card complete but it's still stuck at the HTC screen...
VBQ24 said:
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
Click to expand...
Click to collapse
If you have an unlocked bootloder, then you have to flash the rom (previous full wipe of course) then reboot bootloader (from advanced options in CWM) and then in fastboot (you should see fastboot usb in red in the phone when plugged to the pc) you have to flash the boot.img inside the rom zip folder.
Extract that file only (not the whole rom) and from a cmd session or terminal as root (located where the boot.img file is) type:
fastboot flash boot boot.img
Once that is done (you will get OKAY. finished near the bottom) you can reboot normally by typing in cmd fastboot reboot or choosing reboot from hboot.
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
VBQ24 said:
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
Click to expand...
Click to collapse
Use the token HTC sent you when u unlocked it. and typing in cmd the fastboot unlock command.
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
VBQ24 said:
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
Click to expand...
Click to collapse
then just turn the phone off (power off option) and then boot with power + volume down
glevitan said:
then just turn the phone off (power off option) and then boot with power + volume down
Click to expand...
Click to collapse
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
VBQ24 said:
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
Click to expand...
Click to collapse
Was the boot.img file flashed successfully?
Yes it said so...
EDIT: Not sure if this is an issue with the ROM of if I'm doing something wrong? I went to the "mounts and storage" section of CWM and clicked all the format options accept sdcard. I then installed ROM, went into fastboot and flashed boot.img, it said OKAY twice then finished. Still stuck at black, backlit screen after HTC screen. ROM is JellyTime by randomblame.
VBQ24 said:
Yes it said so...
Click to expand...
Click to collapse
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
glevitan said:
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
Click to expand...
Click to collapse
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
VBQ24 said:
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
Click to expand...
Click to collapse
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
glevitan said:
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
Click to expand...
Click to collapse
No I haven't checked the md5sum of the file, how should I go about doing that?
VBQ24 said:
No I haven't checked the md5sum of the file, how should I go about doing that?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.fab.md5
EDIT: well, don't I feel stupid. I knew full well from reading that your phone wasn't working, but posted a link to an app. Just not paying attention. Sorry about that.
VBQ24,
You can go back to stock by flashing a stock RUU from your PC.
(Edit: You should relock your bootloader first. you can do so from Hboot. There's an option that says relock bootloader or something like that)
The version of the RUU should be equal or greater to the version that came with your phone. Try this v3.13
However, if you want to flash a custom ROM:
You need to downgrade your device first, get s-off and root, then flash a custom ROM
You need to use the Advanced Ace Hack Kit (AAHK), get it from here.
Make sure to read the manual (called 'effin manual) word by word. There are instructions on how to downgrade.
Follow the instructions, and if you have any questions, ask here.
EDIT: After running this "fastboot flash recovery twrp.img" the phone now boots up. The downloaded apps are still there but the userdata partition seems to have been wiped. I'm not sure how flashing a recovery partition wipes the userdata partition but I'm not looking for a way to get the phone to present itself as a Mass Storage Device so I can at least try and use recovery software retrieve as much of the lost data as I can.
Hey guys, long term reader of XDA, first time poster.
I have a friend's HTC One X which just stopped booting up past the HTC Quietly Brilliant logo screen. I am able to get into Recovery mode and doing a "fastboot devices" lists my device. However my friend has many photos on this phone, some of which are of a deceased relative and I'd really like to retrieve the photos if I can.
It's S-ON as I believe there isn't an exploit to go S-OFF yet so my options are likely limited. I've downloaded the most recent RUU file (RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed) but I'm pretty sure this will repartition the phone and delete the photos.
Is there any way I can retrieve the photos? Will the RUU wipe the photos? Is there any other way to get the phone to boot up again?
It would mean so much to me and my friend if there is a solution.
Many thanks,
Rob
Robula said:
Hey guys, long term reader of XDA, first time poster.
I have a friend's HTC One X which just stopped booting up past the HTC Quietly Brilliant logo screen. I am able to get into Recovery mode and doing a "fastboot devices" lists my device. However my friend has many photos on this phone, some of which are of a deceased relative and I'd really like to retrieve the photos if I can.
It's S-ON as I believe there isn't an exploit to go S-OFF yet so my options are likely limited. I've downloaded the most recent RUU file (RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed) but I'm pretty sure this will repartition the phone and delete the photos.
Is there any way I can retrieve the photos? Will the RUU wipe the photos? Is there any other way to get the phone to boot up again?
It would mean so much to me and my friend if there is a solution.
Many thanks,
Rob
Click to expand...
Click to collapse
I dont know about ruu that it will wipe or not. But you can mount sd from the recovery and go to folder DCIM where you can find all photos.
manikdhir said:
I dont know about ruu that it will wipe or not. But you can mount sd from the recovery and go to folder DCIM where you can find all photos.
Click to expand...
Click to collapse
Thank you for the suggestion. However, I can not find the option to mount SD card storage... Could you please elaborate?
My options in recovery made are:
FASTBOOT
RECOVERY
FACTORY RESET (I assume this will wipe photos too?)
SIMLOCK
SHOW BARCODE
IMAGE CRC
Robula said:
Thank you for the suggestion. However, I can not find the option to mount SD card storage... Could you please elaborate?
My options in recovery made are:
FASTBOOT
RECOVERY
FACTORY RESET (I assume this will wipe photos too?)
SIMLOCK
SHOW BARCODE
IMAGE CRC
Click to expand...
Click to collapse
Can you plz tell me which recovery are you using.
manikdhir said:
Can you plz tell me which recovery are you using.
Click to expand...
Click to collapse
HBOOT... Though just tried TWRP as suggested by this guy on another forum... I then went to Recovery and then moments later it just booted straight back into Android! I only intsalled TWRP and it's completely fixed the issue!
Download the TWRP recovery instead of clockworkmod one.
This recovery will let you mount the SD card to copy the ROM file to the phone.
Boot the phone into the Hboot, then go to fastboot.
If you downloaded the ARHD flash file, you have pretty much all you need when you unpack this. There should be a "Flash windows.bat" or something like that, simply run it, and it'll put the boot.img on your phone.
It just uses the command: "fastboot flash boot <filename>.img"
Now to put the TWRP recovery on your phone, use the following:
fastboot flash recovery twrp.img
(Obviously with whatever your version of the twrp.img file is called.)
Reboot the phone into recovery, and you should now be able to mount the SD card, copy the rom across, wipe the caches, and system, install the rom, wipe the caches again, and reboot into ARHD 9.7.2
Click to expand...
Click to collapse
EDIT: The photos are gone... Gallery is completely empty... #%^£$$34!
Robula said:
HBOOT... Though just tried TWRP as suggested by this guy on another forum... I then went to Recovery and then moments later it just booted straight back into Android! I only intsalled TWRP and it's completely fixed the issue!
EDIT: The photos are gone... Gallery is completely empty... #%^£$$34!
Click to expand...
Click to collapse
Did you check the DCIM folder?
manikdhir said:
Did you check the DCIM folder?
Click to expand...
Click to collapse
I did. I have a feeling that my friend may have tried a Factory Reset from HBOOT herself. Although strangely, all her apps are installed. I guess there's no recovery method on this phone? Is there anything I can do?
Robula said:
I did. I have a feeling that my friend may have tried a Factory Reset from HBOOT herself. Although strangely, all her apps are installed. I guess there's no recovery method on this phone? Is there anything I can do?
Click to expand...
Click to collapse
Is there mp3 files in the music player?
manikdhir said:
Is there mp3 files in the music player?
Click to expand...
Click to collapse
No. If I go into the MTP device in Windows Explorer I have Internal Storage saying "25.2GB free of 25.2GB" which is really not a good sign. I'm just wondering how I would at least run a recovery program on this such as Recuva in hope to retrieve the lost data.
EDIT: If I could just work out how to get the USB mode to Mass Storage then I'd be able to do a scan... Any idea how to do this?
Robula said:
No. If I go into the MTP device in Windows Explorer I have Internal Storage saying "25.2GB free of 25.2GB" which is really not a good sign. I'm just wondering how I would at least run a recovery program on this such as Recuva in hope to retrieve the lost data.
Click to expand...
Click to collapse
I think that your frnd has done the factory reset.
manikdhir said:
I think that your frnd has done the factory reset.
Click to expand...
Click to collapse
Well. Thanks for all your help. Too bad I have to be the bearer of bad news!
If anyone knows how to ADB to a One X or knows how to expose the internal storage as a Mass Storage Device then please reply! At least then I can try a recovery program. Thanks.
Was the phone already unlocked ? Or did you unlock the bootloader at the time you wanted to use a recovery to be able to retrieve the photos ?
A first time unlock of the bootloader will delete indeed everything, also sdcard. A factory reset does not delete the sdcard. Tried it myself a couple of weeks ago !
Robula said:
No. If I go into the MTP device in Windows Explorer I have Internal Storage saying "25.2GB free of 25.2GB" which is really not a good sign. I'm just wondering how I would at least run a recovery program on this such as Recuva in hope to retrieve the lost data.
EDIT: If I could just work out how to get the USB mode to Mass Storage then I'd be able to do a scan... Any idea how to do this?
Click to expand...
Click to collapse
You will have to install a custom rom if you want UMS... If you want it on stock rom, then you need to have root access... There's a thread here on XDA but I don't know the link of it... tried searching but can't find it anywhere... strange!
Mr Hofs said:
Was the phone already unlocked ? Or did you unlock the bootloader at the time you wanted to use a recovery to be able to retrieve the photos ?
A first time unlock of the bootloader will delete indeed everything, also sdcard. A factory reset does not delete the sdcard. Tried it myself a couple of weeks ago !
Click to expand...
Click to collapse
No. This was a complete stock phone. Nothing was ever done to with to modify it.
vin4yak said:
You will have to install a custom rom if you want UMS... If you want it on stock rom, then you need to have root access... There's a thread here on XDA but I don't know the link of it... tried searching but can't find it anywhere... strange!
Click to expand...
Click to collapse
I can use fastboot to flash a custom firmware without S-OFF right? Is there even a method of enabling S-OFF and gaining root access on stock ROM? The UMS support would be what I need.
So you unlocked it and then tried to retrieve the pictures, am i right ?
Then its lost because unlocking the bootloader wipes everything including sdcard.
Mr Hofs said:
So you unlocked it and then tried to retrieve the pictures, am i right ?
Then its lost because unlocking the bootloader wipes everything including sdcard.
Click to expand...
Click to collapse
Please excuse me for my lack of knowledge of HTC phones. When you say "unlock", I assume that means to root the phone; to root the phone you need to have S-OFF before you can even flash a new bootloader.
The only this I did was was "fastboot flash recovery twrp.img" from http://teamw.in/project/twrp2/95. This didn't actually change my recovery from HBOOT, it still boots to HBOOT when holding Power+Volume Down (I realise why now because it says on that page "You must be S-OFF or have taken HTC's unlock to use a recovery on your device!"). The phone is S-ON so techinally it didn't really do anything...?
You can unlock the bootloader (not to s-off, not possible as if now) but in unlocked state you can flash recoverys and flashing a recovery with a locked bootloader will also fail.
Did you unlock the bootloader via the htcdev website ? And then flash a custom recovery ?
Mr Hofs said:
You can unlock the bootloader (not to s-off, not possible as if now) but in unlocked state you can flash recoverys and flashing a recovery with a locked bootloader will also fail.
Did you unlock the bootloader via the htcdev website ? And then flash a custom recovery ?
Click to expand...
Click to collapse
I was actually going to do this so in hope that I could flash CWM and then mount the SD card via USB through the CWM recovery, but I got as far as typing "fastboot oem get_identifier_token" which failed with an error so I stopped there.
I think I've missed something here. I still have my CMD prompt open and looked up to see exactly what happened:
C:\Users\Rob\Downloads\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fas
tboot.exe flash recovery "..\..\..\openrecovery-twrp-2.5.0.0-endeavoru.img"
sending 'recovery' (6788 KB)...
OKAY [ 0.955s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.161s
So it actually failed the flash (because the phone is S-ON I guess). Yet this somehow kickstarted the phone and it now boots up flawlessly.
Flashing fail is not due to s-off but because the bootloader is probably still locked. You can check that on the bootloader screen.
But unlocking wipes the whole phone so you lose the pictures at that point anyway
Mr Hofs said:
Flashing fail is not due to s-off but because the bootloader is probably still locked. You can check that on the bootloader screen.
But unlocking wipes the whole phone so you lose the pictures at that point anyway
Click to expand...
Click to collapse
I took a picture to show the details (see attached).
So I'm not able to mount the SD as UMS to run recovery software without unlocking the bootloader, flashing a new recovery and then flashing a custom ROM?
Did S-Off. All good. Then accidentally flashed TWRP over boot.img. No adb in TWRP, so I fastbooted to CWM. Now, CWM starts no matter what I do. Hold buttons, reboot bootloader, adb reboot bootloader....etc. I can not flash recovery from within CWM and I can't get anywhere else. I have tried all I can think of. I have even successfully flashed ROMs. Nothing gets me out of CWM. Any suggestions would be greatly appreciated.
EDIT: Made it back to TWRP through adb shell recovery flash. Still no bootloader. I think I may be screwed.
What happens when you click reboot from twrp then reboot bootloader?
BoneStock S-Off Unlocked Verizon One
dabeastro said:
Did S-Off. All good. Then accidentally flashed TWRP over boot.img. No adb in TWRP, so I fastbooted to CWM. Now, CWM starts no matter what I do. Hold buttons, reboot bootloader, adb reboot bootloader....etc. I can not flash recovery from within CWM and I can't get anywhere else. I have tried all I can think of. I have even successfully flashed ROMs. Nothing gets me out of CWM. Any suggestions would be greatly appreciated.
EDIT: Made it back to TWRP through adb shell recovery flash. Still no bootloader. I think I may be screwed.
Click to expand...
Click to collapse
when you say "Then accidentally flashed TWRP over boot.img."
what does this mean?
you flashed the recovery to the boot partition?
by doing fastboot flash recovery boot.img?
if so you need to fix that partition.
BelievingThomas said:
What happens when you click reboot from twrp then reboot bootloader?
BoneStock S-Off Unlocked Verizon One
Click to expand...
Click to collapse
Straight back to twrp.
andybones said:
when you say "Then accidentally flashed TWRP over boot.img."
what does this mean?
Click to expand...
Click to collapse
I ran fastboot flash boot twrp.img
andybones said:
you flashed the recovery to the boot partition?
by doing fastboot flash recovery boot.img?
if so you need to fix that partition.
Click to expand...
Click to collapse
I have since flashed recovery to the recovery partition and flashed the ROM to get the boot.img fixed. Shouldn't that have fixed the partition?
I am beginning to think I have boot to recovery flagged somewhere. Perhaps in /dev/block....but shouldn't that get blasted when I wipe and install a new ROM?
dabeastro said:
I have since flashed recovery to the recovery partition and flashed the ROM to get the boot.img fixed. Shouldn't that have fixed the partition?
I am beginning to think I have boot to recovery flagged somewhere. Perhaps in /dev/block....but shouldn't that get blasted when I wipe and install a new ROM?
Click to expand...
Click to collapse
Once you flash something to the wrong block, that is not good. I don't want to scare you or anything. honestly I am not sure, the one big thing I do when S-OFF is make sure not to mess up a partition, which it sounds you did, sans I don't know how to fix it, hopefully someone will chime in for you.
andybones said:
Once you flash something to the wrong block, that is not good. I don't want to scare you or anything. honestly I am not sure, the one big thing I do when S-OFF is make sure not to mess up a partition, which it sounds you did, sans I don't know how to fix it, hopefully someone will chime in for you.
Click to expand...
Click to collapse
Even if you are s-on you can flash a recovery to your boot partition. That is the purpose of HTC Dumlock. So good news for him it was safe in this situation.
@dabeastro
Download a Sense or AOSP rom and keep it on a pc. Don't push it to phone just yet. Hold down the Power + Volume Down buttons until you end up in the bootloader. You will eventually make it there. Take the boot.img out of the ROM you downloaded. Then flash the boot.img to your boot partition. Never again flash a recovery to your boot partition . Then boot into recovery from HBOOT and push or sideload the rom. Should be up and running after that.
Flyhalf205 said:
Even if you are s-on you can flash a recovery to your boot partition. That is the purpose of HTC Dumlock. So good news for him it was safe in this situation.
@dabeastro
Download a Sense or AOSP rom and keep it on a pc. Don't push it to phone just yet. Hold down the Power + Volume Down buttons until you end up in the bootloader. You will eventually make it there. Take the boot.img out of the ROM you downloaded. Then flash the boot.img to your boot partition. Never again flash a recovery to your boot partition . Then boot into recovery from HBOOT and push or sideload the rom. Should be up and running after that.
Click to expand...
Click to collapse
I held Power + Volume Down through at least 10 consecutive boots. Always 'Entering Recovery...' I have flashed a Sense rom since all this began and the boot.img should have been rewrote during this right? No matter what I do, recovery. No bootloader.
dabeastro said:
I held Power + Volume Down through at least 10 consecutive boots. Always 'Entering Recovery...' I have flashed a Sense rom since all this began and the boot.img should have been rewrote during this right? No matter what I do, recovery. No bootloader.
Click to expand...
Click to collapse
You can flash a boot.img to the boot block partition inside of recovery.
Flyhalf205 said:
You can flash a boot.img to the boot block partition inside of recovery.
Click to expand...
Click to collapse
Tried that too.
Solved it with lots of help from beaups on irc channel. Many thanks to him. He basically figured out that I had messed up the Misc. I am not totally clear on the fix. He wrote to mmcblk0p19 a couple of times and I flashed it in adb shell. Lo and behold, back into bootloader. From there, I just flashed a new rom and the boot.img was totally straightened out. So, I was stuck in recovery due to a problem in that particular partition. I am going to head back and probe beaups on the solution in the near future. Anyone else having this issue is free to PM me for what little guidance I have to offer.
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?
It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.
k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.
sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.
Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app
The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.
Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.
redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.
I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.
I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)