Hi,
I've spend 3 days on this now, I tried to update my ROM, but it failed to load and whilst trying to sort it managed to wipe everything on my phone. So I'm now stuck with only being able to get into recovery either TWRP or CWM. But I've tried reverting back to the RUU, but this just stops with error 158 wrong image, which I have tried on three different machines running windows 7 and 8.1. I then tried to access the internal storage via TWRP to either place a backup on there or a new rom to update from, but this will not allow me access, I can see the drive and open it, but as soon as I try and do anything with it, it stops and says device has either stopped working or has been disconnected every time. I then tried to sideload a ROM via TWRP but that doesn't connect. I then tried to install from a sideoaded ROM in CWM and I managed to get it to work once and send the file OMNI rom, but it failed to update with a error 7. Now I cant get it to work at all and I can't get ADB to start and find my device. Im now also fighting a battle to keep the battery charged and using a BAT to charge it currently at 3888mV. FASTBOOT works fine and so I can flash the boot and recovery parts but everything else is not working
Can any one please help me.
My phone is a UK spec HTC One X+
CID HTC__001
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-None
MICROP-None
RADIO 3.1204.171.33
eMMC bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH : OFF
Jun 21 2013,17:36:36
i've managed to get sideload to work in CWM, but every ROM I've tried to install will not work, can anyone recommend a ROM that may work
Thanks
Phil
Hi, thanks for everyone who viewed this, but managed to get my phone working, I managed to push a rom zip to my phone with ADB and used TWRP to install it. Fully working again!!!
Please could you kindly put the steps you went through as a tutorial for others?
Related
Hi Guys,
So only one hour after getting my phone, I decided to try and flash a new rom... Coming from a HD2 that was so easy, maybe I didn't read 'all' the information that I should.
Anyway, I flashed with HTC original unlock code, and that seemed to work... Over the past 12 hours or so, I've tried to flash several roms, but with no luck... I've then tried to do various recoveries, but no luck.... (I don't have all the details of what I've done, so that isn't probably going to help!).
I've been reading the forum and trying various things for days now, but no luck... what I am stuck with is the following.
When pressing the power and down button, or boot up, I get:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 15 2001, 14:39:25
If I just reboot normally, then it just shows white background, with green HTC in the middle, then pauses for about a minute, then just reboots again (Yep, I have left it on for hours, same result).
So, I am able to talk to the device via fastboot, but not adb...
I have downloaded the HTCDriver3.0.0.007.exe and unloaded HTC software, but still no luck with adb..
Obviously looking at the boot screen, it still S-ON, so that probably isn't helping...
I'm happy to pass on any more information or try any suggestions that the experts may have At the mo, back using my HD2, but would love to use this new phone (the back's been off so many times that it's already starting to look old!)
So, what's next guys? Does this classify this as a brick ! ???
bro you need to visit this site.... revolutionary.io
Follow the instructions to the t on their. You are on h boot 1.4... DO NOT update anything. Just root and flash a 2.3.4 rom in the dev section
---------- Post added at 12:41 AM ---------- Previous post was at 12:40 AM ----------
also, what carrier are you with?
jnrdavo said:
Hi Guys,
So only one hour after getting my phone, I decided to try and flash a new rom... Coming from a HD2 that was so easy, maybe I didn't read 'all' the information that I should.
Anyway, I flashed with HTC original unlock code, and that seemed to work... Over the past 12 hours or so, I've tried to flash several roms, but with no luck... I've then tried to do various recoveries, but no luck.... (I don't have all the details of what I've done, so that isn't probably going to help!).
I've been reading the forum and trying various things for days now, but no luck... what I am stuck with is the following.
When pressing the power and down button, or boot up, I get:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 15 2001, 14:39:25
If I just reboot normally, then it just shows white background, with green HTC in the middle, then pauses for about a minute, then just reboots again (Yep, I have left it on for hours, same result).
So, I am able to talk to the device via fastboot, but not adb...
I have downloaded the HTCDriver3.0.0.007.exe and unloaded HTC software, but still no luck with adb..
Obviously looking at the boot screen, it still S-ON, so that probably isn't helping...
I'm happy to pass on any more information or try any suggestions that the experts may have At the mo, back using my HD2, but would love to use this new phone (the back's been off so many times that it's already starting to look old!)
So, what's next guys? Does this classify this as a brick ! ???
Click to expand...
Click to collapse
When the device boots and hangs on the HTC screen and then reboots, this generally indicates there is an issue with the kernel. Either the kernel itself is experiencing trouble or the ramdisk portion of the kernel is experiencing trouble. Usually the kernel portion.
The best solution will be to reload a known working kernel. The best method to do this, w/o being able to boot into Android will be to go through the custom recovery.
If you're currently using the HTC unlock method, it only unlocks the kernel partition for writing in three boot modes: bootloader, normal android and fastboot. Since normal android mode is out of the question at this point, bootloader is usually best used for flashing the full system back to stock, that leaves fastboot mode.
There are two ways to flash the kernel through the fastboot:
1) fastboot boot c:\cwm-recovery.img . this will boot temporarily boot the custom recovery image and grant it write access to the kernel partition. while in the temporarily booted custom recovery, flash any ROM or custom kernel .zip file and it will have write access to properly complete.
2) fastboot flash boot c:\boot.img . this will boot just the kernel image and will not load the kernel modules which include WiFi and WiMAX. this will allow the phone to boot the kernel. once the phone is booted on the new kernel you'll need to copy over the modules from the new kernel manually in order for wifi and wimax to work.
for future reference, if you want to avoid these work around methods which can be confusing to some, my application, Flash Image GUI, will allow you to properly flash a kernel from normal android mode.
it should be considered best practice to be familiar with how to properly boot the custom recovery in order to do backups and restores of the full system.
Also, if you are able to use the revolutionary (http://revolutionary.io) method to s-off the device, this will grant the standard custom recovery access to write the boot partition/kernel and help avoid a lot of this hassle. if you're not able to use the revolutionary method then you're next best method is using the HTC unlock method and follow the steps/guidelines i posted above.
hope that helps!
Many thanks Guys... I have tied the revolutionary recovery a few times, but it the program just sits on my screen trying to connect to the phone - unsuccessfully.
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
I'll give the other go a shot..
I really appreciate all your help on this one..
I think my eagerness to get a better ROM on overtook my safety net in reading ALL the instructions!....
ok, further info...
Just to answer previous question, I am with Telstra in Australia... Phone came from web, with rogers rom on it...
I can now boot to ClockworkMOd Recovery v5.0.2.0 (I had to use fastboot to get the loader on)....
It's great, I get the menu and everything, but when I select on of the options (actually, any of the options), by pressing the power button, I just get the blank screen with the hat logo... nothing happens (ie, if I select load zip from sdcard).... I can press the power button again to get to the main menu, but nothing else...
I'm assuming that I still need to get s-off functioning prior to being able to flash the rom?
I've also loaded the flashimageGUI.apk file to the phone on the SD card... Rebooted in both hboot and recovery, but nothing seems to happen...
Actually, at the bottom of ClockworkMod, the following is displayed in white (rest of the text is in blue):
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
Just to clarify, I'm on 3G...
Hi Guys, still stuck...
I've followed the instruction on:
http://forum.xda-developers.com/showthread.php?t=1193540&page=3
... but still no luck... I still have S-ON and not able to flash any ROMS...
I am also unable to get any response from ADB, and also revolutionary.exe just sits there 'waiting for device'...
Any more suggestions... getting desparate here!
have you flashed a custom rom if so that may be the problem what has happen is you lost your boot.img exract it from the zip file on your pc or laptop now go the that folder and open it up scroll down untile you come across your boot.img now copy it to the same folder that you have your adb and your fastboot in now open up cmd and typ fastboot flash boot boot.img press enter and your back up and running
Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks
*UNLOCKED*
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Originally Vodafone branded, in the UK
Hello all, Ive lost several days to this now and have finally signed up to ask you all for help on "unbricking" my Evo3d.
Ive done so much i cant quite remember a full list, but alas my problem is essentialy i have deleted the OS on the phone and now every time i try to flash a .zip to the phone (i am using TWRP which seems to be working fine) it says FAILED and gives me an error whilst trying to find /cache.
So it appears my /cache folder has dissapeared aswell? The cure for this (from what i have read online) is to boot into your rom and then restart to bootloader, however there is no rom to boot into on the phone.
ALL I WANT IS STOCK.
Just to be able to use the phone again, before it was on 4.0.2 i think and even though i have S-ON i still tried to load a custom kernal and rom, this then obviousely put me into a bootloop which was ok, except i have no idea how to go back to stock.
I have tried several RUU files (at 400mb a pop) ALL of which fail and give me the error 155 unknown error during the installing on my computer.
I believe the image that the RUU.exe says my phone is was 3.*** (i cant remember exactly but if anyone needs to know i can boot it up again)
I have tried the RUU to return it to 1.21 or something similar but that also failed.
Seemingly i cant do anything with the phone and hours apon hours of googling is getting me no where.
Please help somebody it would be greatly appreciated.
EDIT- I can now no longer boot into recovery for an unknown reason, i tried another RUU it failed in exactly the same fashion, now i boot the phone and it loads a small picture of a phone with a green circle icon next to it, this then turns into a red triangle with a "!" inside of it, then i have to remove the battery.
Crap.
I think I have found why the RUU were not working, its because my bootloader was unlocked.
I have relocked my bootloader, ran the RUU and it has errored again except this time it says Customer ID number.
I presume this means the CID number on my phone is incorrect? Which would sort of make sense because i think i may have changed it at the very beginning whilst i was following a guide.
How on earth do i find out what to change it back to? I have no idea what the original was
EDIT-
************FIXED**************
Use the fastboot commands to change your CID to what is required (HTC or Vodafone) This must be done with unlocked bootloader.
LOCK YOUR BOOTLOADER
Run the RUU file that you wish to apply and voila.
Thanks xda!
so I bricked my device. it boot loops at the htc screen. several hours later or repair attempts and I still am back to where I started. Initially was able to load elegencia, but when the wifi was not responding I tried to load another ROM and everything has just gone downhill from there.
on my boot screen I see
***UNLOCKED***
EVITARE_UL PVT SHIP S-ON RL
HBOOT1.32.0000
CPLD-None
MICROP-None
RADIO-SSD: 1.09.55.17
EMMC-bootmode: disabled
CPU-bootmode: disabled
HW-Secure boot: enabled
modem type : mdm9215m
I dont really want to re-trace all my steps as I have tried many things to get this back up and running. I may have put the wrong ROM on as I got confused thinking this was a HTC OneXL. I think I want to put venom on here and leave it be. As of now I can no longer see the oneX+as a removable hard drive when i plug it into my pc. windows reports missing hardware ID once and a while. I have recovery as an option when I boot to hboot, but I cannot figure out how to load a boot able image from there. my backups got deleted. When I check my hardware with adb I cannot see it, but my pc detects a device being plugged in. I can flash to the device. So I think I also deleted my hardware ID trying to put in 11111111 superCID. not sure what else I can add. Any help would be appreciated.
sorry if this type of thing has been played out, I just dont want to follow another guide that gets me nothing or makes things worse.
Well, if it makes you feel any better, as long as it boots it's probably not "bricked". Since you can still flash.. can you not just reflash recovery, wipe it all, and flash stock?
hastings101 said:
Well, if it makes you feel any better, as long as it boots it's probably not "bricked". Since you can still flash.. can you not just reflash recovery, wipe it all, and flash stock?
Click to expand...
Click to collapse
it does. thanks. I am kind of nervous to do anything else without specific instruction or guidance. Where can I find a stock rom? what command sequence should I use in flash boot to get it back to normal? I know I can force ROM onto the unit with adb but adb isn't seeing my unit while fastboot is. so how do I get the rom onto my phone?
U changed the Rom with another one thin it's looping ?
Maybe it's the kernel !!
Boot into bootloader and flash a new kernal that support ur new Rom .. don't forget boot.omg
Sent from my HTC One X+ using Tapatalk 4
I did more than change the rom. I tried several things to recover the device and may have made things worse. The last rom I tried to upload, was probably not for my unit. for whatever reason I convinced myself that the reason I was having issues was because I had an htc oneXL and not a htc OneX+, and that may have compounded issues. I also tried to flash superCID to 11111111 and I was never able to do it, and at around that point my unit dissapeared as a removeable storage in windows. SO I am unsure how to put roms on the phone now. adb does not seem to see my unit.
I tried running the android phone ROM update utility but am getting a Error 155: unknown error, when I run it.
I dl'ed and ran the two top most ones here http://www.androidruu.com/index.php?developer=EvitaRE . the update went pretty far but never completed due to the first saying it was incorrect version and the second the Error 155. One thing that is different now, is I re-updated my drivers using Hasoons HTC OneX+ all in one toolkit and I can now see a drive in windows when I boot into recovery. The removable storage drive in windows tell me to insert a disk when I click on it, though. Before I could see 59 gigs of storage, it now has 0 bytes.
I think I am ok for now. I was able to get viperxl+ 2.0 to load via side loader on my second attempt. I rebooted and no more loop. still cannot see my storage in windows when plugged in via usb. but running is running. thanks for your suggestions.
drioddead said:
I think I am ok for now. I was able to get viperxl+ 2.0 to load via side loader on my second attempt. I rebooted and no more loop. still cannot see my storage in windows when plugged in via usb. but running is running. thanks for your suggestions.
Click to expand...
Click to collapse
don't try to change the [CID] u cant do it on OneX+ because (S-ON) and no way to make it off ( as i know )
try flashing stock RUU after re-lock ur Bootloader and thin u will get the OTA update its awesome
+1 to flashing a stock RUU, in theory, this should fix any issue you're having. Once back to stock and 100% working you can start flashing other ROMs.
REMEMBER: AT&T and the International phones ARE different and require matching ROMs. ie if you have ATT phone, make sure you flash an ATT ROM/kernel
Hello All,
I've spent hours on this forum and other, reading related subject, and I've tried so much things (probably some of them worsening my situation) so I'm asking for help now. I'm kind of a newbie so please be comprehensive.
So I've an HTC Desire X and thanks to Hasoon2000's Desire X All-In-One Kit v1.1 I've unlocked bootloader and flashed clockworkmod 6.1.5.
My phone worked perfectly until there was an official update for my android version, and it was impossible to install it.
So i needed to go back to stock basically. And that's where i screwed.
Obviously i didn't make a backup or nandroid before starting to play around.
I think i might have install kernel and recovery from earlier version that the one i had and this caused the problem? any way now the status is:
I cannot start my phone normally. I can only start it in fastboot mode. When i want to reboot it in recovery the HTC screen with "starting recovery" appears for 1 sec and then i've got a black screen and the only way out is reboot it to fastboot mode again.
when connected to my computer i can load boot.img or recovery.img via fastboot in cmd; but it doesn't change the situation.
I think the problem may come from the fact that when i cmd "adb devices", he cannot find any device. Even though i've installed the HTC drivers!
Details:
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
eMMC-boot
Apr 3 2013, 15:50:50:0
my CID is HTC__E11
So then in order to fix that i've tried to RUU using the only RUU availables (with relocked bootloader): RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed
RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
but it doesn't work: a part from the fact that there's a blank after "From: Image version: ", when i try to update to image version 1.14.401.1, during the install it stop with ERROR 158 : IMAGE ERROR , telling me that i've to find a ROM that is adapted for me.
Well. Somebody have any idea how i can get my phone functionning again?
chirou321 said:
Hello All,
I've spent hours on this forum and other, reading related subject, and I've tried so much things (probably some of them worsening my situation) so I'm asking for help now. I'm kind of a newbie so please be comprehensive.
So I've an HTC Desire X and thanks to Hasoon2000's Desire X All-In-One Kit v1.1 I've unlocked bootloader and flashed clockworkmod 6.1.5.
My phone worked perfectly until there was an official update for my android version, and it was impossible to install it.
So i needed to go back to stock basically. And that's where i screwed.
Obviously i didn't make a backup or nandroid before starting to play around.
I think i might have install kernel and recovery from earlier version that the one i had and this caused the problem? any way now the status is:
I cannot start my phone normally. I can only start it in fastboot mode. When i want to reboot it in recovery the HTC screen with "starting recovery" appears for 1 sec and then i've got a black screen and the only way out is reboot it to fastboot mode again.
when connected to my computer i can load boot.img or recovery.img via fastboot in cmd; but it doesn't change the situation.
I think the problem may come from the fact that when i cmd "adb devices", he cannot find any device. Even though i've installed the HTC drivers!
Details:
PROTO PVT SHIP S-ON RL
HBOOT-1.25.0002
RADIO-1.15.40.04
eMMC-boot
Apr 3 2013, 15:50:50:0
my CID is HTC__E11
So then in order to fix that i've tried to RUU using the only RUU availables (with relocked bootloader): RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed
RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
but it doesn't work: a part from the fact that there's a blank after "From: Image version: ", when i try to update to image version 1.14.401.1, during the install it stop with ERROR 158 : IMAGE ERROR , telling me that i've to find a ROM that is adapted for me.
Well. Somebody have any idea how i can get my phone functionning again?
Click to expand...
Click to collapse
i'm not sure if you're able to install a ics-ruu when you're on hboot for jellybean (1.25).
get twrp-recovery for jellybean, install it via fast boot and install a jellybean rom via recovery, like the stock one
http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
http://forum.xda-developers.com/showthread.php?t=2239511
btw. using adb in bootloader doenst work, so its no surprise it doesnt find any device.
Worked out perfectly! My phone is working again!
Thank you so much realCyphox !
:good:
Now I'll try to see if it's possible to install the official updates.