HTC Driod Incredible 2 with 2.3.4
Can not downgrade the system to 0097 instead of the 0098
failed message
FAILED (remote: 43 unknown fail
(before root)
failed message
FAILED (remote: 99 unknown fail
(after root)
HBOOT still 0098
s-on still
orginal message
C:\vwhk-12102011-c>fastboot oem rebootRUU
< waiting for device >
... OKAY [ 0.156s]
finished. total time: 0.172s
C:\vwhk-12102011-c>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 0.234s]
finished. total time: 0.234s
C:\vwhk-12102011-c>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.
605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip
sending 'zip' (292817 KB)... OKAY [ 50.188s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 55.969s
C:\vwhk-12102011-c>fastboot reboot
rebooting...
finished. total time: 0.156s
C:\vwhk-12102011-c>
pls help
If you already have Fastboot enabled on your computer then you need to make sure Fastboot is enabled via Bootloader.
You can test this by rebooting into Bootloader, enabling Fastboot, and then typing into your console
fastboot devices
If your device shows up you are good to go.
Then reboot into system and start attn script. It works a charm!
Oh, also, make sure the proper boot image is located within your ADB environment (unless you have a global setup)
Good luck.
Did you follow this:
http://forum.xda-developers.com/showthread.php?t=1298990
I just used it myself. The only problem I had was not putting usb in debug mode.
Once I did that it work flawlessly.
I was doing this this weekend and ran into problems because I had unlocked the bootloader using HTCdev. I was also using a long USB cable and ran into what I think was signal degradation causing some commands in that script to fail.
Once I relocked the bootloader and switched to the stock cable that came with the phone the downgrade script worked perfectly.
phufford said:
I was doing this this weekend and ran into problems because I had unlocked the bootloader using HTCdev. I was also using a long USB cable and ran into what I think was signal degradation causing some commands in that script to fail.
Once I relocked the bootloader and switched to the stock cable that came with the phone the downgrade script worked perfectly.
Click to expand...
Click to collapse
U screwed yourself with HTC unlock I believe.. relock it then try again
Sent from my Incredible 2 using Tapatalk 2
faehsemc said:
U screwed yourself with HTC unlock I believe.. relock it then try again
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
U would be correct there sir. Relock the bootloader and then run the downgrade tool.
Sent from my Incredible 2 using XDA
+1 on the relocking tip, relock and then everything will work, revolution tool relocks it if you were wondering
I ran into the same issue and relocked the bootloader with "fastboot oem lock" command and then i was able to downgrade properly. Leasson learned. Thanks everybody for their replies.
if all fails, just copy RUU...zip file to sdcard, rename to PG32IMG.zip and do upgrade. It will work without problems
2 yrs to late haha
Sent from my One using xda app-developers app
chillybean said:
2 yrs to late haha
Sent from my One using xda app-developers app
Click to expand...
Click to collapse
There are a lot of noobs lol
Sent from my VS840 4G using Tapatalk
Related
Hello,
I don t have recovery anymore,
and my new room crash on startup...
I m stock, what should I do please.
gatinho75 said:
Hello,
I don t have recovery anymore,
and my new room crash on startup...
I m stock, what should I do please.
Click to expand...
Click to collapse
More info needed.
Which ROM, what did you do?
Sent from my Nexus 7 using XDA Premium HD app
Hello, It is impossible to brike a device, so worry no more.
And regarding your Room crashing, I'm not sure what that means but please go to the relevant home improvement forums to discuss it.
chrisjcks said:
More info needed.
Which ROM, what did you do?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Its was a rooted phone on ICS, I think it was a stock rom, I was unable to change the rom or make OTA update (installation aborted)
then I try to reinstall CWN, but then when I lance back I have a message like : the bluid is for developement process only
When I try to reinstall I have installation failed
on One X ON Click I try to change ROM with RUU - advence table, same issue
gatinho75 said:
Its was a rooted phone on ICS, I think it was a stock rom, I was unable to change the rom or make OTA update (installation aborted)
then I try to reinstall CWN, but then when I lance back I have a message like : the bluid is for developement process only
When I try to reinstall I have installation failed
on One X ON Click I try to change ROM with RUU - advence table, same issue
Click to expand...
Click to collapse
Bootloader locked, relocked or unlocked? (Hold power and volume down till your bootloader screen shows)
Also, I'm right in saying you have the tegra3 quad core international HOX, right?
Sent from my Nexus 7 using XDA Premium HD app
gatinho75 said:
Its was a rooted phone on ICS, I think it was a stock rom, I was unable to change the rom or make OTA update (installation aborted)
then I try to reinstall CWN, but then when I lance back I have a message like : the bluid is for developement process only
When I try to reinstall I have installation failed
on One X ON Click I try to change ROM with RUU - advence table, same issue
Click to expand...
Click to collapse
You must have stock recovery for OTA updates. You also probably need to be unrooted.
Sent from my Inspire 4G using Tapatalk 2
chrisjcks said:
Bootloader locked, relocked or unlocked? (Hold power and volume down till your bootloader screen shows)
Also, I'm right in saying you have the tegra3 quad core international HOX, right?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
The bootloader was unlocked butt I relocked using fastboot oem lock .
yes I have a international HOX
gatinho75 said:
The bootloader was unlocked butt I relocked using fastboot oem lock .
yes I have a international HOX
Click to expand...
Click to collapse
Either install a RUU
Or
Unlock the bootloader, and flash the correct boot.img for the Rom you tried to install
Sent from my HTC One X using XDA Premium HD app
chrisjcks said:
Either install a RUU
Or
Unlock the bootloader, and flash the correct boot.img for the Rom you tried to install
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
I trying with a RUU now but the battery is to low for the moment
i try to flash to manytime with onex click but evrytime failed
[29-08-2012 08:02:30] Booting Into RUU
[29-08-2012 08:02:53] Flashing Zip
[29-08-2012 08:04:22] sending 'zip' (570044 KB)...
OKAY [ 76.367s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 76.569s
[29-08-2012 08:04:22] Clearing Cache
[29-08-2012 08:04:30] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.001s
Process Took 2 Minutes And 24 Seconds
[29-08-2012 08:05:00] Booting Into RUU
[29-08-2012 08:05:23] Flashing Zip
[29-08-2012 08:12:07] sending 'zip' (563907 KB)...
OKAY [ 75.738s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 75.949s
[29-08-2012 08:12:07] Clearing Cache
[29-08-2012 08:12:15] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.000s
Process Took 7 Minutes And 40 Seconds
gatinho75 said:
I trying with a RUU now but the battery is to low for the moment
i try to flash to manytime with onex click but evrytime failed
[29-08-2012 08:02:30] Booting Into RUU
[29-08-2012 08:02:53] Flashing Zip
[29-08-2012 08:04:22] sending 'zip' (570044 KB)...
OKAY [ 76.367s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 76.569s
[29-08-2012 08:04:22] Clearing Cache
[29-08-2012 08:04:30] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.001s
Process Took 2 Minutes And 24 Seconds
[29-08-2012 08:05:00] Booting Into RUU
[29-08-2012 08:05:23] Flashing Zip
[29-08-2012 08:12:07] sending 'zip' (563907 KB)...
OKAY [ 75.738s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 75.949s
[29-08-2012 08:12:07] Clearing Cache
[29-08-2012 08:12:15] erasing 'cache'...
FAILED (remote: (00000008))
finished. total time: 0.000s
Process Took 7 Minutes And 40 Seconds
Click to expand...
Click to collapse
Charge the phone then.
Unplug cable from PC.
Enter bootloader on phone
Select power down
Plug phone into mains (not pc)
Sent from my HTC One X using XDA Premium HD app
chrisjcks said:
Charge the phone then.
Unplug cable from PC.
Enter bootloader on phone
Select power down
Plug phone into mains (not pc)
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
actually I can't when I select power off and put on charge then the phone boot again,
when I put on charge and I try to select power off is not working, its still under 30, I ll will cheek tonight
Thank for your help
gatinho75 said:
actually I can't when I select power off and put on charge then the phone boot again,
when I put on charge and I try to select power off is not working, its still under 30, I ll will cheek tonight
Thank for your help
Click to expand...
Click to collapse
I try to recharge the phone all day, no I can't power on anymore.
and when I put on charge nothing happen even the red light..
This thread might be your only solution, I made it pretty simple for that guy to understand.
It requires doing a fastboot charging using a script.
http://forum.xda-developers.com/showthread.php?t=1840156
from my HTC One X using XDA Premium HD app
chrisjcks said:
This thread might be your only solution, I made it pretty simple for that guy to understand.
It requires doing a fastboot charging using a script.
http://forum.xda-developers.com/showthread.php?t=1840156
from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Can I assume that this is working for you?
Let it charge, (Don't be impatient) then run the RUU whilst in fastboot usb. (which you should already be in for the fastboot charging script)
Sent from my HTC One X using XDA Premium HD app
Yesterday I was playing around and almost bricked my phone, had to do a RUU restore and for this I had to Relock the bootloader, after bringing my phone back to life and trying to unlock it again I just can't achieve it.
I follow the same instructions from HTC Dev, used the same code and got an error, then got a new code and I get this error:
Code:
C:\fastboot (android root)>fastboot flash unlocktocken Unlock_code.bin
sending 'unlocktocken' (0 KB)...
OKAY [ 0.022s]
writing 'unlocktocken'...
FAILED (remote: not allowed)
finished. total time: 0.229s
Any ideas?
Thanks!
Try spelling "token" correctly not tocken
sent from my One X using xda venom premium
bogfather said:
Try spelling "token" correctly not tocken
Click to expand...
Click to collapse
I've never been so ashamed in my entire life.
Thanks hahaha
I bought a bnib tmobile g2 off swappa the other day. I want to install a newer rom and started following the instructions to gain permaroot and install a recovery in the wiki here http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
First I downgraded by following this guide http://forum.xda-developers.com/showthread.php?t=1178912 which worked fine.
But now my phone is no longer recognized as a usb device when I am in android, so I can't obtain adb access. After messing around a bit, changing usb cables, plugging it into different computers, etc I booted into hboot by holding down+power. When I am in hboot I can see the phone over usb and see it when I run fastboot devices. I tried flashing cwm recovery with fastboot but it didn't work.
Code:
[email protected]:/home/necronian/xfr/root# fastboot flash recovery recovery-clockwork-5.0.2.7-vision.img
sending 'recovery' (3652 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
Hboot lists the following
Code:
VISION PVT SHIP S-OFF
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010,17:59:38
Does anyone have any idea where I should go from here? I can't follow any of the wiki instructions without adb access. Otherwise everything on the phone seems to be working fine although I haven't transferred my sim over from old G2 so I don't know if the cell works.
I tried letting it install a system update that brought me to 1.22.531.8 but it still isn't detected as a usb device. I know that I have the correct drivers (I'm on linux anyway) because I previously used adb to downgrade the phone and I've tried several usb cables and computers.
Any help would be appreciated.
Looks right to me, try running fastboot as root and see if this helps ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Looks right to me, try running fastboot as root and see if this helps ya
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, I was actually already running fastboot as root. I tried a few more things is morning, but no luck.
Code:
[email protected]:/home/necronian/xfr/root# fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]:/home/necronian/xfr/root# fastboot oem rebootRUU
...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
[email protected]:/home/necronian/xfr/root# fastboot flash recovery recovery-clockwork-5.0.2.7-vision.img
sending 'recovery' (3652 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[email protected]:/home/necronian/xfr/root# fastboot flash zip ../vision.hboot-0.76.2000.zip
sending 'zip' (216 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I don't the issue is the phone, try to update your fastboot binaries, try another USB cable or port, try renaming the images to something simple like recovery.img or bootloader.img (don't know why but I have seen this work) or try another PC or run a virtual box
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
I don't the issue is the phone, try to update your fastboot binaries, try another USB cable or port, try renaming the images to something simple like recovery.img or bootloader.img (don't know why but I have seen this work) or try another PC or run a virtual box
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ended up downloading visionary and put it on an sdcard, then I gained temproot and installed clockworkmod from the play store and the engineering hboot. I'll try flashing a new rom later but I should be good to go now.
That's your choice, but if you don't root with gfree method you could run into issues down the road, happens a lot on these forums.
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
That's your choice, but if you don't root with gfree method you could run into issues down the road, happens a lot on these forums.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just installed cyankat and I have adb access again, thanks for the help.
Hello All,
need urgent help on this issue. I am a so called novice is posting to forums , so please excuse me if I have inadvertently done or not done something important.
Following are the device details , can't provide a screenshot so typing all info -
-------------------------------------
****unlocked****
ENDEAVORU PVT SHIP S-ON RL
HBOOT-0.94.0000
CPLD-None
MICROP-None
RADIO-1.1204.103.14
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure Boot: enabled
MODEM PATH : OFF
Apr 11 2012,02:27:11
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SHOW BARCODE
IMAGE CRC
--------------------------------
Used fastboot from a windows 7 command prompt and flash the recovery few times , I see the following
E:\fastboot>fastboot flash recovery recoverycwm.img
sending 'recovery' (8832 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
E:\fastboot>fastboot flash recovery recoverycwm.img
sending 'recovery' (8832 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
E:\fastboot>fastboot flash recovery recoverycwm.img
< waiting for device >
sending 'recovery' (8832 KB)...
OKAY [ 1.073s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.245s
E:\fastboot>fastboot flash recovery recoverycwm.img
< waiting for device >
sending 'recovery' (8832 KB)...
OKAY [ 1.159s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (0000000a))
finished. total time: 1.390s
E:\fastboot>fastboot flash recovery recoverycwm.img
sending 'recovery' (8832 KB)...
OKAY [ 1.071s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.276s
Initially I had Viper ROM , then I have tried to update my HTC One X with the following ROM
SkyDragon v 2.0 HOX
but failed to do so , then I tried to recover from the Stock Rom , also failed to do it successfully.
I have tried using adb commands to transfer the rom onto the sdcard too , but fails to transfer with error
Earlier I could go to recovery mode and see the rom zip files on my storage , but now I can access the storage too.
I am in a kind of fix which I am not sure if I can come out of , so all help would be appreciated.
Hboot is to low for newer roms. They don't run on that. What's the outcome of :
Fastboot getvar version-main
Sent from my HTC One X using XDA Premium 4 mobile app
E:\fastboot>fastboot getvar version-main
version-main: 1.28.708.10
finished. total time: 0.006s
http://androidruu.com/getdownload.p...Radio_2.1204.122.17_release_268338_signed.exe
Here is a ruu for you.
Sent from my HTC One X using XDA Premium 4 mobile app
seems to be the wrong ruu , I hit the following error
The ruu is correct
Did you relock the bootloader if it's unlocked ? Did you put the phone in the bootloader/fastboot usb mode ? Did you run the ruu with admin rights ?
Sent from my HTC One X using XDA Premium 4 mobile app
yes, I did put the phone in the bootloader/fastboot usb mode and all the activity was run with admin rights.
However I am not sure how do I do this relock the bootloader if it's unlocked.
Can I unlock it or relock it as many times I need?
what is the command please? I will re-run the whole sequence again once I am able to charge the phone beyond 30%.
Charge the phone to 100% if you can. Go for safe !
Fastboot oem lock
That's the command.
Sent from my HTC One X using XDA Premium 4 mobile app
Thanks much , now I am back to stock rom and booted
I guess now I have to update HBOOT , turnback to unlocked status and try to update the ROM to some other version if I wish to ?
Yes now you have to do all official ota's you can get. After those updates you unlock the bootloader and make a nandroid backup with the custom recovery and then you start flashing other roms
Sent from my HTC One X using XDA Premium 4 mobile app
Dear All,
I have run into a issue with my HTC Desire Bravo. I had to replace the Main Flex Cable Ribbon since the Volume control was not working. After the replacement now my Desire no longer boots. I tried erasing from recovery & realised that my SD card no longer mounts.
I tried using the process # 13 found here : http://forum.xda-developers.com/showthread.php?t=1275632
However I am unable to get the device recognised on my LapTop.
After I issue the command fastboot oem enableqxdm 0, All I get is waiting for device. Device Manger shows My HTC with a exclamation mark. Tried different versions of HTC drivers found on XDA, but to no luck.
Need Help.....
Regards,
Nagesh Raghavaiah
nageshr4u said:
Dear All,
I have run into a issue with my HTC Desire Bravo. I had to replace the Main Flex Cable Ribbon since the Volume control was not working. After the replacement now my Desire no longer boots. I tried erasing from recovery & realised that my SD card no longer mounts.
I tried using the process # 13 found here : http://forum.xda-developers.com/showthread.php?t=1275632
However I am unable to get the device recognised on my LapTop.
After I issue the command fastboot oem enableqxdm 0, All I get is waiting for device. Device Manger shows My HTC with a exclamation mark. Tried different versions of HTC drivers found on XDA, but to no luck.
Need Help.....
Regards,
Nagesh Raghavaiah
Click to expand...
Click to collapse
Won't it install in device manager where the ! Mark? Try another sd card see if it recognises.
Sent from my HTC Desire S using XDA Free mobile app
No, I have tried 3 different SD Cards...the same issue
nageshr4u said:
No, I have tried 3 different SD Cards...the same issue
Click to expand...
Click to collapse
Whats your bootloader info?
Sent from my HTC Desire S using XDA Free mobile app
Take the phone apart, something tells me the sdcard flex wasnt connected right. If it is connected then disconnect it then re connect it to be sure then if it still dont work then flash 4ext recovery and use the unbrick option. Click link below to install fastboot drivers and u can try that enableqxdm command aswell.
http://forum.xda-developers.com/showthread.php?t=2588979
HBoot: 0.80.0000
jmcclue said:
Take the phone apart, something tells me the sdcard flex wasnt connected right. If it is connected then disconnect it then re connect it to be sure then if it still dont work then flash 4ext recovery and use the unbrick option. Click link below to install fastboot drivers and u can try that enableqxdm command aswell.
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
1. I took the phone apart. reconnected the Flex Cable.
2. Installed ADB and device driver from the link as suggested.
3. I boot into Fast boot using Volume down, back & power button.
4. Device Manager lists the phone as Android 1.0 with a exclamation.
5. Unable to proceed further :crying:
Okay a new issue: I tried it on my friend's laptop.
The 1st command was successful, but not the 2nd.
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>fastboot oem enableqxdm 0
...
OKAY [ 0.026s]
finished. total time: 0.026s
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>
Recovery is still unable to mount my SD Card.
nageshr4u said:
Okay a new issue: I tried it on my friend's laptop.
The 1st command was successful, but not the 2nd.
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>fastboot oem enableqxdm 0
...
OKAY [ 0.026s]
finished. total time: 0.026s
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>
Recovery is still unable to mount my SD Card.
Click to expand...
Click to collapse
What recovery you got?
Sent from my HTC Desire S using XDA Free mobile app
lilsafbig said:
What recovery you got?
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
ClockworkMod Recovery V 2.5.0.1
Tried to update recovery too, but I get the below error
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>fastboot flash recovery recovery-clockwork-5.0.2.0-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.499s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.920s
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>
nageshr4u said:
Tried to update recovery too, but I get the below error
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>fastboot flash recovery recovery-clockwork-5.0.2.0-bravo.img
sending 'recovery' (3054 KB)...
OKAY [ 0.499s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.920s
C:\Users\nagesh\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-to
ols>
Click to expand...
Click to collapse
Have you even unlocked your bootloader?
Sent from my HTC Desire S using XDA Free mobile app
I am not S-Off if thats your Question...
nageshr4u said:
I am not S-Off if thats your Question...
Click to expand...
Click to collapse
They are different things. Unlocking your bootloader can be done from htcdev, your phone will still be s on but unlocked so you can flash roms and root or recovery from fastboot.
Sent from my HTC Desire S using XDA Free mobile app
lilsafbig said:
They are different things. Unlocking your bootloader can be done from htcdev, your phone will still be s on but unlocked so you can flash roms and root or recovery from fastboot.
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
My Phone is unlocked I had custum Roms on it before I had to change the strip.
nageshr4u said:
My Phone is unlocked I had custum Roms on it before I had to change the strip.
Click to expand...
Click to collapse
Change what?
Sent from my HTC Desire S using XDA Free mobile app
lilsafbig said:
Change what?
Sent from my HTC Desire S using XDA Free mobile app
Click to expand...
Click to collapse
I had to replace the Main Flex Cable Ribbon since the Volume control was not working.
nageshr4u said:
I had to replace the Main Flex Cable Ribbon since the Volume control was not working.
Click to expand...
Click to collapse
So what did it do to your phone like did it reset everything?
Sent from my HTC Desire S using XDA Free mobile app
I don't know, probably the guy who replaced the flex cable also replaced my sd card that had the custom rom. I did not realize that. The moment I switched on the phone it went to a boot loop. I thought of re-installing the Rom, hence wiped everything. that is when I realized that the recovery is unable to mount the sd card. Now I am stuck....
nageshr4u said:
I don't know, probably the guy who replaced the flex cable also replaced my sd card that had the custom rom. I did not realize that. The moment I switched on the phone it went to a boot loop. I thought of re-installing the Rom, hence wiped everything. that is when I realized that the recovery is unable to mount the sd card. Now I am stuck....
Click to expand...
Click to collapse
Hmm cos of u had your bootloader unlocked u cant flash the ruu back on. But flash another Rom. So in your bootloader does it say unlocked?
Sent from my HTC Desire S using XDA Free mobile app