Related
need to exchange the phone, so i need to revert the phone back to fully stock. phone currently has cyanogenmod 7. just want to make sure i'm doing this right...
so as i understand it, following the g2\desire z wiki, i can just use clockword mod recovery to install the stock image and flash it with CWM right, via the "flash alternate recovery" option?
and more importantly, the wiki says that to install the stock rom, i need to make sure my main version is not higher than 1.19.531.1, but i was not able to find my version. i booted into hboot, which number is that? and regardless, if i use misc_version to set the main version, does it matter what version i have? also, i used gfree to root before, and still have the original partition 7 saved on my pc, if that matters. thanks
Here follow my guide, it describes how to return to stock. Only change you might want to make is use a proper stock rom to flash instead of my modded ones.
-Nipqer
thanks! how do you flash stock recovery???
i did fastboot recovery recovery.img and it said:
"sending 'recovery' (4652 KB)... OKAY [1.021 S]
writing 'recovery'... FAILED <remote: not allowed>
finished. total time : 1.031s
Fastboot flash recovery only works on eng hboots or htcdev unlocked hboots.
-Nipqer
Sent from my HTC Vision using xda premium
so then what can i do? thanks again
Use the xda wiki to get full root. That will give you recovery in the process
-Nipqer
Sent from my HTC Vision using xda premium
Similar-sounding problem
I've attempted to install ClockworkMod and CM7 on my G2 with Gingerbread 2.3.4, and have wound up putting it in a semi-bricked state. (Whole process went fine on my old G2 last year, but had to return that due to a wifi problem). Here's what I've done so far:
1. Started the root/CW process (http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting). Once I got to the psneuter step, I got "Failed to set prot mask (innappropriate ioctl for device)", which I figured meant I needed to do the downgrade, since that was the only difference I could see between my new G2 and the old one (which had Froyo when I went through this process).
2. Downgraded to Froyo (http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Firmware_Downgrade_(Froyo). That seemed to go just fine.
3. Re-did the root/CW process. That also seemed to go just fine, until I rebooted into CW, at which point I got:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
At this point, attempting to select any of the items in the CW menu just showed the hat-with-ring logo, no text. I figured I must have screwed something up, and decided I'd best roll back to stock (I'd just done that on my old G2, so I could send it in, and that process had also worked fine).
4. Rolled back to the original PC10IMG.zip (http://theunlockr.com/2010/12/01/how-to-unroot-the-t-mobile-g2-htc-vision/ but without the OTA part). When I rebooted, I got the green-on-white "HTC" screen, for at least 10 minutes. Retried several times. Using power-volumedown, I could still get into recovery, which was still Clockwork, but with the same errors as in step 3. I could still connect via ADB (when in Clockwork) and get a root shell with that, at this point.
5. Big goof: I decided I should rollback to stock recovery. Did that using the http://forum.xda-developers.com/showthread.php?t=834545 guide. Rebooted. Phone still sticks at the initial HTC screen, forever. Using power-volumedown, I can get to the screen whose name I do not know, the one that's white with three skateboarding androids at the bottom, and the "Fastboot, Recovery, Factory Reset, Simlock, System Info, Image CRC" menu.
6. Recovery now takes me to what I presume is stock recovery, which has a "E:Can't mount /cache/recovery/command" message at the bottom of the screen. Menu is "Reboot system now, Apply sdcard:update.zip, Wipe data/factory reset, Wipe cache partition." Factory reset and wiping the cache partition, then rebooting, still results in the eternal HTC screen.
7. If I do reboot and do power-volumedown to get back to the three-skateboards screen (someone please tell me the actual name, so that I can sound like less of an idiot), I can select fastboot, and then connect via fastboot-windows. I haven't done anything with that yet, however, as I figured I've gone too far already without stopping to ask for help, and don't want to cut myself from off from fastboot the way I cut myself off from adb.
Right now, I just want to get the phone to a usable state again. Not expecting any hand-holding, but I'd appreciating someone pointing me to the start of the path back.
...the three skateboards screen is called bootloader
is it still s-off and what hboot-number does it show?
At the top of the bootloader (thanks!) screen, I get:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1010000)
MICROP-0425
RADIO-26.01.00.17_M2
eMMC-boot
Sep 8 2010, 15:56:38
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
emamid said:
Thanks immensely. Going to try this in the morning (hitting 2am for me). Just one final question: at the "flash a new ROM" step, should that be the stock T-Mobile ROM, or does it matter? My original intent was to install CM, so if it makes no difference I'll go with that, but right now I'd be happy just to have a phone that boots, so if I need to I'll use stock and count my blessings.
Click to expand...
Click to collapse
no do not flash a stock rom (you will get in troubles doing this with a rooted phone and s-off)... cm7 is a good way to go
if you don´t mind pls hit the thanks button
damnit... now i can't seem to downgrade the new phone, with the 1.22 firmware. following the cyanogenmod wiki, at the step where you enter:
Code:
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
adb shell
i get a whole bunch of:
Code:
An error occurred while running the exploit (-1) (errno: 25)
Scanning region fffe0000...
An error occurred while running the exploit (-1) (errno: 25)
adb shell
adb: permission denied
$
help, what am i doing wrong?
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
hoffmas said:
first of all you do have gingerbread (2.3+)? because you asked this in a different thread...
and you did chmod it as described in the guide?
Click to expand...
Click to collapse
nope, it's android version 2.2, but the build number is 1.22.531.8, so that means i have to downgrade it, right?
you need a different guide for a froyo downgrade - try this guide:
http://forum.xda-developers.com/showthread.php?t=905261
i´m not sure if it works... other thing you could do is make a official update to gingerbread and then downgrade with the guide you used before.
hoffmas said:
if you don´t mind pls hit the thanks button
Click to expand...
Click to collapse
Weird, I had to open the page in Firefox rather than Chrome for the "Thanks" button to show up.
---------- Post added at 03:03 PM ---------- Previous post was at 02:43 PM ----------
hoffmas said:
ok, this looks good.
first i would flash a recovery.img through fastboot (you do have eng hboot so it should work)
download the 3.0.2.4 image from here and put it into your platform tool folder:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
then connect your phone to pc go to your platform tool folder and type:
"fastboot flash recovery recovery.img"
enter recovery and wipe data&cache&dalvik cache afterwards flash a new rom...
if you get the same error as before, have a look here:
http://forum.xda-developers.com/showthread.php?t=1448441
Click to expand...
Click to collapse
Installed clockwork, and can get to it through the bootloader. However, when I try to wipe the cache -- or select any of the other menu items -- I just get the hat-and-ring logo, with nothing else. Power button takes me back to the CW menu again. No error messages at any stage, but nothing happens either.
Should I proceed with the steps in the second link you pointed to? Or does this sound like a different problem?
Hm don't know... Maybe try to find out if your cache is corrupted or your emmc chip. So yes follow the link i posted, but before you do the same as the op there (means using your sdcard instead of emmc) try everything else... (i think nipqer posted a link there related to corrupted cache...)
Sent from my HTC Vision using XDA App
Thankfully, I didn't have to go through hardly any of the contortions CollegeBound had to in that thread. Installing 4EXT was enough -- it was able to get past the "E:Can't mount /cache/..." errors (which started again when I used fastboot to erase the cache), whereas Clockwork was stymied by them. Did an update using a CM ROM, and everything seems fine.
Thanks again for your help. I don't think T-Mobile would have let me RMA two phones in two weeks.
Originally posted here:
This happened to me yesterday; my phone told me I had some updates from the market, and it froze mid-updating an app (don't remember which one).
I pulled the battery and the phone went directly into recovery, and it has stayed there ever since.
I tried everything, wiping the cache, the boot, dalvik, EVERYTHING. I even did the factory reset/data wipe, and in the end it tells me the same thing:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is there something that I overlooked? My phone isn't even able to be "seen" by my computer, the only way I can turn it off is by doing a battery pull, and when I put the battery back in, it goes straight into CWMod's recovery.
Click to expand...
Click to collapse
jrizk07 said:
re flash your ROM since you're in recovery. otherwise restore a nandroid backup and that'll get you up and running again.
Click to expand...
Click to collapse
I 've tried flashing trinity 2.6 and it aborted the installation citing a (status 7), I had tried to previously install coredroid multidevice (3.5) and it had aborted it as well, citing a (status 1); I downloaded clockwork 5, as well as 2 other roms; miui.us vivow 1.12.30, which was also aborted with a (status 1) and JmzRunyInc2v1, this one managed to go through "deleting stuff", "Installing stuff", "Symlinking stuff", "Installing bussybox stuff", "Flashing kernel stuff" and then "done" followed by "Install from SD card complete", but when I chose "Go back" it gave me the same message:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
So, when I rebooted, it went again into CWMod.
Is there anything else I'm missing?
Doing some reading it looks like your recovery image is corrupted. You'll need to re flash your recovery manually.
You can get into the bootloader correct?
Noob's Guide #6: I just HTC Unlocked, what now?
Thank AgalychnisCallidryas
yeah, when I turn on my phone, it goes directly into CWMod, but I can go into Hboot, and select fastboot, recovery, etc., but the problem is my computer isn't able to identify the phone when it gets plugged in.
EDIT: I tried HBoot USB, and it tells me the drivers aren't correctly installed, something about android 1.0.
Do you have any access to a Linux/Mac machine?
A friend of mine has a mac, yeah. However, my brother also has a droid phone (Incredible 1) and may have the needed drives, would that work?
Edit: I was able to get the android dsk and platform tools from an old backup, I'll try to give this a go with it.
cowboyv said:
A friend of mine has a mac, yeah. However, my brother also has a droid phone (Incredible 1) and may have the needed drives, would that work?
Click to expand...
Click to collapse
Use a windows computer, it's pretty simple. You'll probably need to uninstall the current drivers on that computer (Control Panel> Add Remove Programs or Programs under windows 7, Make sure all HTC Drivers are uninstalled)
Then go here
http://forum.xda-developers.com/showthread.php?t=1298990
Install the HTC USB drivers and go from there.
LOL. I just use mac, no drivers required.
Ok, I was able to download the sdk, and reinstalled the htc drivers, everything's groovy, but the computer is still not able to "see" my phone, it's telling me "device not found".
Should I be using the "push" adb command to push in a new recovery image from CWMod?
EDIT: I tried doing the recovery again, this time, it went through checking the MD5 sums, erasing and restoring the boot image, but when it got to the system restoring, it tells me there was an error formatting the system.
So, since adb can't connect to the phone, what are my options?
cowboyv said:
Ok, I was able to download the sdk, and reinstalled the htc drivers, everything's groovy, but the computer is still not able to "see" my phone, it's telling me "device not found".
Should I be using the "push" adb command to push in a new recovery image from CWMod?
EDIT: I tried doing the recovery again, this time, it went through checking the MD5 sums, erasing and restoring the boot image, but when it got to the system restoring, it tells me there was an error formatting the system.
So, since adb can't connect to the phone, what are my options?
Click to expand...
Click to collapse
Read this and take note http://forum.xda-developers.com/showthread.php?p=18016711#post18016711
You need to be in the bootloader and not recovery in order to do what you need to do.
You cannot re flash the recovery from CWMod. Remember the white screen with the android guys skating? That's where you need to be.
Either hold down the volume down button and hold power, or if you have your device detected by adb you can
adb reboot bootloader
This is where you flash the recovery image via fastboot.
http://forum.xda-developers.com/showthread.php?t=1134520
Or you might even want to consider re flashing the stock RUU to unroot and just start over from scratch.
That worked, but...
jrizk07 said:
This is where you flash the recovery image via fastboot. Or you might even want to consider re flashing the stock RUU to unroot and just start over from scratch.
Click to expand...
Click to collapse
Ok, thank you! That did work. I just flashed the vivow, vut after trying to restore to the my latest backup, it still gives me the same error logs: it goes through checking the MD5 sums, erasing and restoring the boot image, but when it gets to the system restoring, it tells me there was an error formatting the system before giving me the same error message.
Code:
Error while formatting /system!
E:Error in /cache/recovery/log (Read-only file system)
E: can't open /cache/recovery/last_log
So I guess I'll have to flash the stock RUU and start from scratch. Just a question, though; to flash the RUU, I just follow the same procedure, go into fastboot, plug into computer, and use adb, correct?
cowboyv said:
Ok, thank you! That did work. I just flashed the vivow, vut after trying to restore to the my latest backup, it still gives me the same error logs: it goes through checking the MD5 sums, erasing and restoring the boot image, but when it gets to the system restoring, it tells me there was an error formatting the system before giving me the same error message.
Code:
Error while formatting /system!
E:Error in /cache/recovery/log (Read-only file system)
E: can't open /cache/recovery/last_log
So I guess I'll have to flash the stock RUU and start from scratch. Just a question, though; to flash the RUU, I just follow the same procedure, go into fastboot, plug into computer, and use adb, correct?
Click to expand...
Click to collapse
Right, Just follow this procedure and start over from scratch completely. Do not restore a backup because it seems to be corrupt.
http://forum.xda-developers.com/showthread.php?t=1298990
Ok, I downloaded the zip file vwhk-12102011-c and have extracted it to my C: root, however, when I try to do the first code
Code:
adb shell rm -r /data/local/tmp/*
ADB tells me "error: device not found".
Now, apologies beforehand, as you may have noticed this is my first android phone and I am a noob, so some of my questions may seem a bit obvious to you.
1. I read that I rename the ruu to PG32IMG.zip, is this true?
2. Should I continue and flash the RUU zip via adb, or should I push the RUU?
3. Should I simply put the zip in a microsd and then restart the phone in bootloader?
EDIT: Nevermind, went ahead and did 1. and 3. and that worked. I still have the root access, but I need to re-install a recovery.
Once again, thanks.
Hi Everyone,
I did a boo boo. I flashed my One X without a supported CID with the Android Revolution 14.2 ROM. Is there a way to correct this and revert back to my previous ICS? Help please.
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
ClydeB1 said:
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
Click to expand...
Click to collapse
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Is there any other way to flash the phone? I tried "fastboot flash zip rom.zip". It showed OKAY for the copy, however, a second line remark "writing 'zip' ... FAILED (remote not allowed)" appeared. The process then was aborted.
I also tried formatting the sdcard and then tried to mount the sdcard. Same 'unable to open ums lunfile...' error constantly appears. Just afraid that my phone is now a brick. Can anyone help? Thanks in advance.
kevintan12 said:
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Click to expand...
Click to collapse
Install a version of CWM that isn't ancient, I.e., 5.8.4.0.
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
kevintan12 said:
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
Click to expand...
Click to collapse
No, everything is recoverable, if your phone won't turn on at all, then you're bricked for real.
Just flash the one from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
then put in the same folder as fastboot and use command:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Thanks everyone for the advice. Really appreciate it. I finally managed to use TeamWin Projects and it allowed me to mount the USB. Managed to then transfer an ICS ROM for flashing.
Hi there !
I have a little problem with the JellyBean update on my rooted One X. I didn't know that I must go back to a stock recovery before doing the update so i discovered it when it refuse to do the update.
I have done some research and i find how to flash a stock recovery (i did it with fastboot) but now i'm stuck. I reboot with holding power+volume down to get acces to the recovery, then i choose it and the update icon appear but then i have an warning panel with a phone on his side (i hope you know what i'm talking about..). Now i have a boot loop and i don't know how to fix that..
I hope someone will be able to answer me !
And sorry for my english, tell me if something is not clear.
P.S: If possible, i would prefer not having to lose my data
Did you flash the stock recovery or were you stuck before that??
Yes i flash it and i get stuck after. Now when i boot i press power+volume down and when i am in the menu i choose "Recovery", a black screen with the icon update, and then the same black screen but with a phone and a warning panel on his side.
Popofthepop said:
Yes i flash it and i get stuck after. Now when i boot i press power+volume down and when i am in the menu i choose "Recovery", a black screen with the icon update, and then the same black screen but with a phone and a warning panel on his side.
Click to expand...
Click to collapse
Are you sure you got the right stock recovery, did u modify something in your rom, did u change the stock kernel to custom kernel ?
did u restore to fully stock (not just the recovery)
stock rom
stock kernel
stock recovery
I have a stock rom and a stock recovery (i guess, i have downloaded a file named endeavoru_recovery_signed.img) but i don't know for the kernel, how can i check it? The only thing i did was unlock the bootloader and root the phone, does it change the kernel?
it's much easier if you just relock the bootloader and run the RUU.
I would prefer to keep my data and installed data if it's possible.
Popofthepop said:
I have a stock rom and a stock recovery (i guess, i have downloaded a file named endeavoru_recovery_signed.img) but i don't know for the kernel, how can i check it? The only thing i did was unlock the bootloader and root the phone, does it change the kernel?
Click to expand...
Click to collapse
No that does not change the kernel.
Put the phone in Fastboot USB mode and Do
Fastboot getvar version-main
You might have a old recovery installed.
Ok i have the version 2.17.401.2, is it good or not?
Edit: It's the ICS version so it isn't the right recovery version, right? I have to search a 4.0.4 version? The higher version of recovery i have found is version 1.29.401.11
This is the 2.17 stock recovery
http://db.tt/U5CK4noo
If your main version says 2.17.***.** you need this recovery !
Thank you for the link, i flashed this recovery but i still have the same problem :-/
Edit: Now i can acces to the recovery menu when i press power+volume up on the screen with the warning panel. I have some error message:
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
Edit 2: I forgot to say that I wipe and format some things (don't remember which one, i try to find again the tutorial that i found) but nothing that delete data.
Edit 3: Ok i find it, that's what i did:
Wipe the cache partition
Go to Advanced and wipe dalvik and batt stats
Go to Mounts and Storage and format system, then data, then cache.
Popofthepop said:
Thank you for the link, i flashed this recovery but i still have the same problem :-/
Edit: Now i can acces to the recovery menu when i press power+volume up on the screen with the warning panel. I have some error message:
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
Edit 2: I forgot to say that I wipe and format some things (don't remember which one, i try to find again the tutorial that i found) but nothing that delete data.
Edit 3: Ok i find it, that's what i did:
Wipe the cache partition
Go to Advanced and wipe dalvik and batt stats
Go to Mounts and Storage and format system, then data, then cache.
Click to expand...
Click to collapse
The errors ...that's fine because the stock recovery can't mount the sdcard that's normal.
The wiping caused it that it not boots. You did practically a full wipe ! Do you have the RUU or a nandroid backup from the rom.
Give your cid here, we have the main version already ... going back with a ruu is the easiest now....
Popofthepop said:
Thank you for the link, i flashed this recovery but i still have the same problem :-/
Edit: Now i can acces to the recovery menu when i press power+volume up on the screen with the warning panel. I have some error message:
E:Can't open /cache/recovery/command
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
Edit 2: I forgot to say that I wipe and format some things (don't remember which one, i try to find again the tutorial that i found) but nothing that delete data.
Edit 3: Ok i find it, that's what i did:
Wipe the cache partition
Go to Advanced and wipe dalvik and batt stats
Go to Mounts and Storage and format system, then data, then cache.
Click to expand...
Click to collapse
OMG...
Dude, you better go RUU way, really.
I assume you have a Windows computer and HTC drivers are installed on it properly.
Looks like you've lost your data and cache but you may still have the data in your sdcard, so first, try to backup them...
Launch the CWM recovery... Connect your USB cable to the phone and then in the CWM custom recovery window, go to "mounts and storage" and select "mount USB storage".
This shall allow your computer to access the storage of your phone.
You shall see a drive on your computer named "HTC STORAGE".
That is your phone storage so copy everything you think that you need.
Then...
Download the correct RUU for your phone >> http://www.htcruu.com/?dir=Endeavor
Note: One X is called "Endeavoru", if international model. Otherwise "Endeavor".
When downloaded, power off the phone.
Press Vol down and Power buttons together till you reach the HBOOT screen.
Select fastboot.
Plug your USB cable and "fastboot" will change to "fastboot usb".
From your computer, which is on the other end of the USB cable, launch command line, from the folder which you keep your adb, fastboot files.
type "fastboot devices" and hit enter.
You shall see some serial number if you have correctly installed the drivers of the phone and if it is correctly plugged.
Now, you need to re-lock you bootloader.
This is required for RUU to perform; if your bootloader is not in "locked" or "relocked" state, RUU won't perform.
Next, type "fastboot oem lock" and hit enter.
Now, bootloader is "relocked".
Now, run the RUU executable you've downloaded and follow the instructions on the screen.
This will take you back to stock status, then, without messing with it, do the 4.1.1 update from system settings and right after your first boot of 4.1.1, go to CWM recovery again and get a BACKUP.
Good luck.
erol.savas said:
OMG...
Dude, you better go RUU way, really.
I assume you have a Windows computer and HTC drivers are installed on it properly.
Looks like you've lost your data and cache but you may still have the data in your sdcard, so first, try to backup them...
Launch the CWM recovery... Connect your USB cable to the phone and then in the CWM custom recovery window, go to "mounts and storage" and select "mount USB storage".
This shall allow your computer to access the storage of your phone.
You shall see a drive on your computer named "HTC STORAGE".
That is your phone storage so copy everything you think that you need.
Then...
Download the correct RUU for your phone >> http://www.htcruu.com/?dir=Endeavor
Note: One X is called "Endeavoru", if international model. Otherwise "Endeavor".
When downloaded, power off the phone.
Press Vol down and Power buttons together till you reach the HBOOT screen.
Select fastboot.
Plug your USB cable and "fastboot" will change to "fastboot usb".
From your computer, which is on the other end of the USB cable, launch command line, from the folder which you keep your adb, fastboot files.
type "fastboot devices" and hit enter.
You shall see some serial number if you have correctly installed the drivers of the phone and if it is correctly plugged.
Now, you need to re-lock you bootloader.
This is required for RUU to perform; if your bootloader is not in "locked" or "relocked" state, RUU won't perform.
Next, type "fastboot oem lock" and hit enter.
Now, bootloader is "relocked".
Now, run the RUU executable you've downloaded and follow the instructions on the screen.
This will take you back to stock status, then, without messing with it, do the 4.1.1 update from system settings and right after your first boot of 4.1.1, go to CWM recovery again and get a BACKUP.
Good luck.
Click to expand...
Click to collapse
I was already on it....... Now we have one big block of jungle info, that will come across as pretty confusing
MarcelHofs said:
I was already on it....... Now we have one big block of jungle info, that will come across as pretty confusing
Click to expand...
Click to collapse
sorry, I had to check the answers before posting. I'll double check next time.
Ok thank you guys, i guess i have no choice i will do it with RUU, I juste have a question, i don't know which RUU i have to download.. @MarcelHofs My cidnum is HTC_203. Don't worry for the jungle info, just tell me which RUU to download and i should be able to follow your tutorial
Popofthepop said:
Ok thank you guys, i guess i have no choice i will do it with RUU, I juste have a question, i don't know which RUU i have to download.. @MarcelHofs My cidnum is HTC_203. Don't worry for the jungle info, just tell me which RUU to download and i should be able to follow your tutorial
Click to expand...
Click to collapse
Gonna give it tonight . I'm at work right now
Is that one good?
http://htcruu.com/Endeavor/RUU_ENDE...Radio_2.1204.135.20_release_274900_signed.exe
If it's not i will wait tonight, don't worry i'm not in a hurry
Popofthepop said:
Is that one good?
http://htcruu.com/Endeavor/RUU_ENDE...Radio_2.1204.135.20_release_274900_signed.exe
If it's not i will wait tonight, don't worry i'm not in a hurry
Click to expand...
Click to collapse
Jep should be the one ! Lock the bootloader
Put the phone in bootloader Fastboot USB mode
Command
Fastboot oem lock
And then run the ruu from pc WITH admin rights :thumbup:
I will test that as soon as my phone will have at least 30% battery, i have reflash CWM to charge it but it's very very long -_-
Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!
I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.