Related
Is it possible to manually update to 4.04 without installing a custom recovery? I downloaded the file, named it update.zip, put it in the root and rebooted holding down volume +/- and power. I chose to go into recovery and it just presented me with the red triangle with an exclamation point. Is there no stock recovery on these?
The problem you'll run into is that in order to update, the update needs to be in the cache folder, which you cant access without root.
im in same boat... tried this but got nowhere
http://www.androidauthority.com/ver...id-4-0-4-update-unofficially-available-50690/
williamthegoat said:
The problem you'll run into is that in order to update, the update needs to be in the cache folder, which you cant access without root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=22182181&postcount=1
You can use the toolkit I guess to run a temporary copy of cwm. You might need to have the boot loader unlocked. Be careful if you are tempted to unlock your boot loader. It will wipe the phone of everything including your photos.
bunklung said:
http://forum.xda-developers.com/showpost.php?p=22182181&postcount=1
You can use the toolkit I guess to run a temporary copy of cwm. You might need to have the boot loader unlocked. Be careful if you are tempted to unlock your boot loader. It will wipe the phone of everything including your photos.
Click to expand...
Click to collapse
Will applying the 4.0.4 update relock your bootloader? I know you will have to reroot.
It did not relock my bootloader.
I only had to reroot.
I'm having an issue with my friend's GN,
He suffers from random reboots which automatically restore the phone information to a specific date in the past.
I tried the toolkit, manual root and unlock but no luck.
the bootloader itself relocks itself right after i try the "fastboot reboot-bootloader" command.
I cant flash CWM permanently.
Can this be the recovery partition kicking in? I tried renaming it and I didn't get an error.
I managed to root the device, but then I cant install any programs from the Market, I was trying to get Root Explorer to work to ensure that the recovery is renamed or removed.
Whenever I flash the bootloader to primela03 it goes back primekk15.
Is this a GSM GNex (i9250)?
i9250
To me it sound like you actually never unlocked the bootloader in the first place..
Edit: To be more constructive... I have no idea what "the toolkit" does or how it works.
To unlock your bootloader you boot into it and run "fastboot oem unlock". That's the whole process. I personally don't see the value of a toolkit obscuring that process.
Unlocking your bootloader will cause your phone to factory reset and wipe everything on it. Have you done this? Have your phone asked you to confirm this? Did you click the volume-rockers to "yes" and then confirm with the power-button? And then, did the phone get wiped?
If you cannot answer "yes" to every question asked above, you have not unlocked the bootloader. End of story.
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
This is a wacky situation,
I tried using GNex toolkit 6 (http://forum.xda-developers.com/showthread.php?t=1392310) and it never worked.
"fastboot oem unlock" unlocks the device, but the as soon as I try "fastboot reboot-bootloader" it goes back to it's locked state.
I tried flashing another bootloader right after I unlocked it, but it reverted to the old one after rebooting.
BlindWolf8 said:
When you boot the phone up there should also be an unlocked lock icon under the Google logo at the bottom of the screen.
Click to expand...
Click to collapse
Did that, but as soon as I reboot the lock icon goes away.
aGoGo said:
Did that, but as soon as I reboot the lock icon goes away.
Click to expand...
Click to collapse
Strange
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
DeezNotes said:
There is a file that will put the stock recovery back when you reboot. I'm not sure what else that file does but maybe that's your problem?
Going from memory, I think the process is unlock via fast boot, flash clockwork recovery, boot into recovery, flash super user, I also removed that recovery file at this stage via adb even though other directions have you do it later with root explorer. And that was it. If you do it the way others wrote it up (using root explorer) you'll have to reflash the recovery again.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer via adb
5- deleted recovery-from-boot.p from /system
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
aGoGo said:
Here's what I just did:
1- Unlocked the recovery
2- Booted insecure image
3- pushed superuser
4- installed root explorer, ROM Manager via adb
5- in root explorer I deleted recovery-from-boot.p from /system and it came back then tried "adb shell rm /system/recovery-from-boot.p" and it's gone.
6- Tried downloading CWM from ROM manager and the phone reboots whenever it starts download and goes back to stock
rebooted and the damn thing still living in the past!!! even the recovery file is back!
Click to expand...
Click to collapse
O_O
the only thing I can think of is a hardware problem is causing the device to do a hard reset every time you boot.
j.go said:
When you "Unlock the recovery," do you mean you flash a custom recovery or do you mean you unlock the *bootloader*? It's not the same thing.
Click to expand...
Click to collapse
I unlock and then flash or sometimes reboot another boot image.
DeezNotes said:
You have to go back in and re-apply the recovery. That file "recovery-from-boot.p" is like a "reset" file that puts the stock recovery back during the boot process. I suspect it may be re-locking your bootloader too, but this is just a guess.
After you do step 5, repeat steps 1 and 2.
Click to expand...
Click to collapse
Did that, the moment I reboot, everything goes back to normal :s
I'm also unable to wipe from the normal system settings, the phone reboots when we try that.
can it be related to this issue? http://www.galaxynexusforum.com/forum/rescue-squad/4093-data-not-wiping-cant-return-stock-3.html
If you have problems doing data wipe/factory reset, it's quite possible that storage is corrupted/failing. It may be whats causing all the random reboots and reverting to old info. Best to bring to a samsung center and make that warranty claim.
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Theshawty said:
Don't just delete the file recovery-from-boot.p, as there's one more file that can do bad things. It's called "install-recovery.sh" and is to be found within /system/etc
Click to expand...
Click to collapse
Actually, don't delete either file.
Don't touch recovery-from-boot.p at all, and rename the sh.
If you want to be able to install otas in the future, renaming the patch file will break the MD5 check. The file is harmless if the sh file is out of commission.
DeezNotes said:
I'm not sure what you're doing wrong... but its something.
You shouldn't have to flash another boot loader. I'm not sure what you would gain from that with the phone being a nexus?
Flashing another recovery is necessary for flashing different roms, kernels, mods, root, etc.
If you are indeed flashing a different boot loader, may i ask why?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm trying another loader because nothing else works, the phone is stock and running 4.0.2. auto update causes it to crash and reboot.
Hey guys,
I flashed clockworkmod recovery via fastboot and made a complete system backup on my htc desire hd.
But now I've a problem. My brother unlocked the bootloader with the official htc tool, in fact my phone is still s-on with hboot 2.00xx.
Now I've flashed a custom rom but my phone keeps staying in the bootscreen with te green htc logo.
Any1 any idea how to fix this ?
Thanks in advance
IQ_QI said:
Hey guys,
I flashed clockworkmod recovery via fastboot and made a complete system backup on my htc desire hd.
But now I've a problem. My brother unlocked the bootloader with the official htc tool, in fact my phone is still s-on with hboot 2.00xx.
Now I've flashed a custom rom but my phone keeps staying in the bootscreen with te green htc logo.
Any1 any idea how to fix this ?
Thanks in advance
Click to expand...
Click to collapse
Your problem is that the HTC dev method unlockt the boot loader but you are eng s-on.
So you can flash a custom ROM but you can't flash a kernel. So you need to root and unlock t again.
What I should do is relock the bootloader and flash a ruu.
After that search for the (aahk) advance ace hack kit and root t again. The good way:laugh:
Hey thx for your reply,
where do I get these ruu roms , and sould I lock the bootloader after I flased the ruu rom and how do I lock the bootloader angain ?
Thx in advance
Btw if i lock my bootloader again and run this hackkit, do I still have my recovery mod and a possibility to flas my ruu back?
IQ_QI said:
Btw if i lock my bootloader again and run this hackkit, do I still have my recovery mod and a possibility to flas my ruu back?
Click to expand...
Click to collapse
Here can you find a ruu http://www.filefactory.com/f/efa28fefafc4af9c/
You can lock the boot loader whit adb " I don't know the command for that"
CWM make a backup to sdcard you never lose them.
Edit: the boot loader relock if you flash a ruu.
You can flash the ruu with the bootloader
Well i tried to flash my rom, I made with CRM and then ran the hack kit. I said i've to downgrade my android version.
After it downloaded the rom it said failed to update cuz my main version is older.
Any idea?
Does the phone boot into the rom?
If it does, is it now on a froyo rom?
Sent from my Desire HD using xda app-developers app
IQ_QI said:
Hey guys,
I flashed clockworkmod recovery via fastboot and made a complete system backup on my htc desire hd.
But now I've a problem. My brother unlocked the bootloader with the official htc tool, in fact my phone is still s-on with hboot 2.00xx.
Now I've flashed a custom rom but my phone keeps staying in the bootscreen with te green htc logo.
Any1 any idea how to fix this ?
Thanks in advance
Click to expand...
Click to collapse
Ok, it's like this. The way most people get root and recovery (and the recommended way) is through the AAHK. It gives you an option to flash a completely unlocked ENG S-OFF bootloader, which allows recovery to flash the boot image to the /boot partition too. This is what makes the phone start, otherwise it'll be stuck at the HTC Quietly Brilliant screen. Most people will tell you that you should run an RUU and get back to locked bootloader state and then run the AAHK. This IS the preferred method if you want to have a fully unlocked phone, but if you're finding it difficult to do, don't do it.
You've unlocked the bootloader using the htcdev unlock tool. What that does is partially unlock your bootloader. It allows you to flash zips to the system partition and data partition, but not the boot partition. So what happened to you was that you flashed CWM recovery, used it to flash a ROM, but it didn't boot - this is because though the ROM flashed fine, the corresponding boot image for the ROM was not flashed, so the ROM cannot start. The main headache with htcdev method of unlocking is that it leaves you with a S-ON bootloader preventing the flashing of boot image directly from recovery. You will need to flash it manually each time you flash a ROM.
The procedure to do that is -
1. Download the attached zip file, extract it to Desktop or wherever you want using 7-zip/WinZIP.
2. Open the ROM zip file you downloaded. Extract boot.img from this zip to the previously folder which you just extracted in the above step.
3. Turn your phone completely off (pull out battery). Then hold 'volume down' while pressing power and continue holding it till you see a white screen with 3 green skateboarding Androids. This is the bootloader.
4. FASTBOOT will be the first selected option in the list. Press 'Power' to select it. Make sure that now it shows FASTBOOT in red under the initial green text.
5. Connect your phone to computer. See that the red FASTBOOT changes to FASTBOOT USB.
4. Open the adb_fastboot folder, open 'Start here.bat'. It will open a command prompt window in that folder.
5. Type 'fastboot flash recovery recovery.img'. You only need to do this once. It will flash 4ext Touch Recovery, which is better than CWM (thanks to madmaxx82 for the awesome recovery).
6. Type 'fastboot flash boot boot.img'. You will need to do this everytime you flash a custom ROM, but before you do so be sure you've copied the boot.img from the ROM zip to the adb_fastboot folder.
7. You should see some stuff like 'Sending data... data sent successfully'. If there's any error at this step report it here.
8. Once it has done everything and displayed a successful confirmation, disconnect phone.
9. Hightlight BOOTLOADER and press 'power' to select it. Press 'volume down' to highlight RECOVERY and 'power' to select it.
10. Once you're rebooted into 4ext Touch Recovery, go to 'install zip from SD card', browse for the ROM zip file in your SD card. If you haven't copied the zip to SD card, go back a step, connect phone to computer, select 'toggle USB storage' and then copy it onto the SD card. Once you have the ROM zip on the sdcard, go to the main screen of the recovery, choose 'wipe/format'->format all partitions (except SD card). Now go back to main screen, choose 'install zip from sdcard' and browse to the ROM zip location, select it and confirm that you want to flash it.
11. When the flash process is done, go back to the main screen of recovery, and press reboot now. You will reboot into the custom ROM.
This is the process to flash a custom ROM and get it to boot properly IF you have unlocked the bootloader using www.htcdev.com. For AAHK unlocked S-OFF bootloaders, you can just flash the ROM zip from recovery. The boot image will be flashed too.
Before trying the above try this and you might get lucky.
Boot into clockworkmod wipe data/factory reset. Wipe cache. Wipe dalvik cache. Flash the custom rom again and wait 15 mins for it to boot before giving up.
Sent from my Desire HD using xda app-developers app
@sashank, probably the most informative reply I've read on here for a long time, very helpful to me as well :thumbup:
Sent from my Desire HD using Tapatalk 2
hans moleman said:
Before trying the above try this and you might get lucky.
Boot into clockworkmod wipe data/factory reset. Wipe cache. Wipe dalvik cache. Flash the custom rom again and wait 15 mins for it to boot before giving up.
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
What you're saying is correct for fully unlocked S-OFF boot loaders. The ROM take sometime to boot the first time because it has to build the dalvik cache. The time it takes depends on the number of apps. Same thing happens when you wipe dalvik cache, it has to be rebuilt on boot.
But the problem here is, the OPs phone is unlocked using htcdev. With that method, the boot loader remains on S-ON. So the boot partition cannot be flashed to using recovery. The boot.img will have yo be manually flashed through fastboot, otherwise the ROM won't boot no matter how long he waits.
Sent from my Desire HD using xda premium
That htcdev unlock sounds like a nightmare. Glad I stayed away from that one... I used to flash different roms with s-on on my desire (not DHD) for a while with no problem. There was a rooting method called unrevoked that flashed clockworkmod with s-on. I guess DHD must have a different version of nand lock which restricts flashing part of the rom from zip?
hans moleman said:
That htcdev unlock sounds like a nightmare. Glad I stayed away from that one... I used to flash different roms with s-on on my desire (not DHD) for a while with no problem. There was a rooting method called unrevoked that flashed clockworkmod with s-on. I guess DHD must have a different version of nand lock which restricts flashing part of the rom from zip?
Click to expand...
Click to collapse
Yes. The boot image does not get flashed. This is what sucks about htcdev unlock, and the reason why HTC pissed off so many people. The community asked for bootloader unlock, HTC gave a half-assed bootloader unlock. Alternative methods to gain S-OFF are always preferred. Some devices unfortunately don't have S-OFF methods yet, so they have to use htcdev unlock. HTC One X for instance, don't know about the other One series phones.
HDPC said:
Try to remove battery and then add battery again, then go to cwm and do factory reset and delete those cache
Click to expand...
Click to collapse
Why are you answering a thread that is an year old??
Hello, I'm not sure if this has been discussed before, but atleast I didn't find a complete answer to my question.
I unlocked my bootloader some time ago, and I flashed a new Image, a stock 4.2 maguro image, but the problem is that I forgot to root the new image, i've been using my phone for some time now, and I wanted to root the phone, but is there a way to root the phone without wiping all the data and settings?
Braien
is your bootloader still unlocked?
if so, just flash or boot into a custom recovery and then flash the supersu.zip package. this will not wipe your data.
Zepius said:
is your bootloader still unlocked?
if so, just flash or boot into a custom recovery and then flash the supersu.zip package. this will not wipe your data.
Click to expand...
Click to collapse
Should be unlocked, but how can I be sure of that?
And how can I enter the custom recovery, I can't remember.
braien334 said:
Should be unlocked, but how can I be sure of that?
Click to expand...
Click to collapse
2 ways,
when you reboot your phone, do you see a little unlocked lock?
other way: boot into fastboot mode and the lock status will say "UNLOCKED"
braien334 said:
Should be unlocked, but how can I be sure of that?
Click to expand...
Click to collapse
During the boot, the padlock in the lower half is open if the device is unlocked .
Okay, it's unlocked, but how to enter the recovery mode?
If I press volume up+down and power, and I select recovery, it just says no command.
Is there some tutorial for rooting like this?
http://forum.xda-developers.com/showthread.php?t=1529058
follow the section after unlocking your device.
I used Nexus toolkit, but I guess it works the same, but is automatic.
But thanks anyways:good:
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?