[Q] Desire reboots while making nand backup? - Desire Q&A, Help & Troubleshooting

Hi all!
So I go into recovery and try to do a backup. It works fine until about halfway in the process, when the phone suddenly reboots and I'm back into the main ROM.
I've tried different versions of clockwork recovery and RA-desire recovery, reformated/repartioned SD-card, reinstalled ROM but so far I am unable to make a backup. SD-Card is close to empty and phone is fully charged.
This never happened before.
Current CWM is recovery-clockwork-5.0.2.0-bravo
Phone is PVT-1 Bravo. S-off
Please help if you are able.
cheers!

this is a longshot but you could try ERASING the recovery, then flashing one you haven't tried before (links on my guide in #resources)..
Also, have you tried using a different SD-Card? or your SD-Card in a different phone?

Longshots are the only thing left to me my friend. Is erasing covered in your guides? Can you show me where?
Haven't tested SD card in another phone yet, but it "seems" to work fine in windows and Gparted. but it's also a prime suspect..

to erase recovery:
Code:
fastboot erase recovery

Ha! After unrooting and doing the whole root process all over again I discovered what might be the real problem. It's not that my phone reboots while doing nand back up, it's that my phone reboots after a period of time in recovery!
And because backing up takes some time, it usually occurs while doing just that.
So OK, new problem: My recovery randomly reboots after a period of time, any thoughts/ideas?

Related

Ridiculous Boot Loop - Two bricked DINCs

Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Both phones are completely useless, not sure what to do at this point and CM6's owner was leaving town.
Any ideas? Ultimate way to unbrick a DINC? If you know of anything, please help.
A boot loop is not a brick. I would nandroid back to stock(you did this right?) or use an RUU.
grnmons said:
Both experiencing the same problem,
One UD 8.0 got stuck in loop after I tried installing Koush Kernel
2nD one is running CM6.0.1, was fine until I tried using to read Phone #1s MicroSD to figure out what was wrong.
2nd phone (CM6) then restarted randomly while plugged into PC, which started the bootloop.
Tried everything, nandroid (Couldn't mount /Data), I wiped, factory reset, tried reflashing update.zip for CM6 phone.
Click to expand...
Click to collapse
Does this mean you can get into hboot?
If yes, you should be able to ruu an official release..
Sent from my ADR6300 using XDA App
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
ziggymanILT said:
I do not have a great deal of experience, but since you can get in recovery, place King Kernel #3 on your SD card, boot into recovery and apply the KingKernals #3 zip file from your SD card for the 1st phone. See if that fixes it. Just sounds like incompatibility with the kernel if it happened right after you flashed it.
Click to expand...
Click to collapse
UD is an AOSP Rom, King's kernel does not support it at this time.
I would try a fresh install of the 8-26 leak. Do wipe first, then do dalvik wipe under advanced settings. Get deodexed version of rom Here
If that does not work let's get some information
Did you run unrevoked forever and get S-off status?
What radio version are you using?
You should not be borked if you are getting into recovery you should be fine.
@ToyTank
BOTH phones are - 2.05.00.6.11 S-ON, Neither are unrevoked forever.
Problem with phone 1 (UD) is that the SD card is completely messed up now. It's an 8GB that has nothing on it, the compuiter is reading it at 758MB. Any function of Recovery leads to errors mounting, so flashing stuff isn't working, nandroid as well.
Phone 2 (CM6) let's me flash stuff onto it, "Install from sdcard complete." but will continue into a bootloop when I restart the phone.
I attempted RUU last night and maybe I'm doing it wrong but the software is giving me an error connecting to USB. How should I go about installing the 8-26 leak? Just wipe > throw in PB31IMG and install?
I assume I don't need unrevoked forever for this, I tried 8-26 and flashed PB31IMG.zip, Device 2 Starts dancing until it says "Main Version is older! Update Fail". Anybody know a workaround?
Try formating the sd card to FAT32 using a computer. That might help with phone #1. Error with usb can be solved using these steps.
1. Try the RUU executable. it will give you that usb error, taking you to the black htc screen.
2. Exit the ruu program (leaving phone in that state) and run it again. This worked for me when I RUU'd mine.
Who knows though. It may have been a one shot deal.
sounds like you are trying a bunch of stuff without READING about what you are doing. you flashed kernels with a rom that CLEARLY states that they will not work and then you tried to flash unsigned roms through hboot which will not work without s-off and then you try to downgrade when you have the ota leak (radio 2.05) which will not work.
you either need to get the ruu working, get s-off applied or follow the steps to go back to stock hboot.
time for you to start doing your homework to get yourself out of this mess.
Neither are bricked. Ruu back to stock.
yeah bro not good practice
@Fretless, @Lafester, @GermanBrat. Thanks for the comments - going to try RUU 3.21.605 and report back.
Hey guys RUU worked for Phone 2 (CM6) but is not playing nice with Phone 1. USB connection error. I appreciate the help so far, any more ideas for this phone?
It's basically stuck in white htc inc screen and will go no further. It's completely wiped and nothing will mount in recovery. RUU can't detect a usb connection but the PC beeps when I connect via usb

[Q] Flash new ROM after boot or recovery no longer works

I recently installed Leedroid 2.2d with A2sd on my HTC desire (unbranded) and it no longer boots (it doesn't make it past the HTC logo). It did this with the previous version but if I removed the battery and left it for a while it would eventually turn on again. Before this happened it started randomly restarting and I think that might be the problem.
Possibly useful information:
I can boot into the fastboot menu but it won't go further than the HTC Logo from there.
I can plug it into my PC and it will display "HBoot USB Plug"
Booting into recovery also only shows HTC Logo, it goes no further.
I have HBoot 0.92.0001 and the radio is 5.10.05.23.
I am trying to work out how I can re-flash in the hopes it will sort this out possibly with the RUU program and connecting from windows.
It has been a few days now and I can't get my phone working and I'm starting to get a little desperate, any help is appreciated as I'm a little overwhelmed by the amount of information available and the endless options.
I have downloaded the RUU from forum.xda-developers.com/showthread.php?t=695667 (RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe) and run it.
It starts working and then stops with the message "Error[140]: Bootloader version error". How do I get the correct RUU for my bootloader (HBoot 0.92.0001)?
I have also tried Froyo downgrade (forum.xda-developers.com/showthread.php?t=768256) but it just returned a whole lot "Error: Device not found" messages.
Tried flashing RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed and received an error about a file not being able to be opened for writing.
Just ran RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe and it completed successfully but it still doesn't go past the screen with the white background and the green HTC logo.
RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.0 0.32U_5.09.05.30_2_release_142828_signed.exe didn't work originally but I charged until it was fully charged and then tried booting it again and it worked.
I had taken my sim and sd card out so I switched it off and put those back in and again it booted up fine. I was then switching Wi-fi on and it suddenly restarted and now it refuses to boot again.
Any ideas?
I can now consistently get it to boot by doing the following:
1. Remove battery
2. Put battery back
3. Charge until full and then leave plugged in for about 15 minutes.
4. Switch phone on.
Unfortunately it is still randomly re-booting while using the phone, could be it be a bad partition on the sd card?
trancehead said:
I recently installed Leedroid 2.2d with A2sd on my HTC desire (unbranded) and it no longer boots (it doesn't make it past the HTC logo). It did this with the previous version but if I removed the battery and left it for a while it would eventually turn on again. Before this happened it started randomly restarting and I think that might be the problem.
Possibly useful information:
I can boot into the fastboot menu but it won't go further than the HTC Logo from there.
I can plug it into my PC and it will display "HBoot USB Plug"
Booting into recovery also only shows HTC Logo, it goes no further.
I have HBoot 0.92.0001 and the radio is 5.10.05.23.
I am trying to work out how I can re-flash in the hopes it will sort this out possibly with the RUU program and connecting from windows.
It has been a few days now and I can't get my phone working and I'm starting to get a little desperate, any help is appreciated as I'm a little overwhelmed by the amount of information available and the endless options.
Click to expand...
Click to collapse
try flashing the bootfix on the first post of LeeDroid thread
EDIT: here it is http://db.tt/QLu5cPL
Thanks for replying. How do I flash the bootfix?
Also, I don't have Leedroid anymore and I am back on stock Froyo ROM.
you flash it the same way you flash leedroid. through recovery.
have you rooted after you flashed the RUU? if you have, flash LeeDroid, flash bootfix and then reboot.
w.0.o.t said:
you flash it the same way you flash leedroid. through recovery.
have you rooted after you flashed the RUU? if you have, flash LeeDroid, flash bootfix and then reboot.
Click to expand...
Click to collapse
I used ROM manager to flash leedroid so I'll try a that again. I'll have to try it later as luck would have it, I can no longer boot using the fully charged battery method
trancehead said:
I used ROM manager to flash leedroid so I'll try a that again. I'll have to try it later as luck would have it, I can no longer boot using the fully charged battery method
Click to expand...
Click to collapse
have you rooted? you can do it manually via recovery. hold down volume button while turning the phone on, then choose recovery. you can choose zip file to install.
i've never flashed anything using ROM manager so i don't know how it works. does it reboot automatically after flashing something? if that's the case, then you might need to do it via recovery. because you need to flash the fix before rebooting.
More frustration. If I take the sd card out it will boot up so that I can see the home screen but then it just reboots again, and again, and again at the same point.
When I put the sd card back again it gets to the HTC logo and stops again.
This is really starting to annoy me
w.0.o.t said:
have you rooted? you can do it manually via recovery. hold down volume button while turning the phone on, then choose recovery. you can choose zip file to install.
i've never flashed anything using ROM manager so i don't know how it works. does it reboot automatically after flashing something? if that's the case, then you might need to do it via recovery. because you need to flash the fix before rebooting.
Click to expand...
Click to collapse
I have yet to get recovery to actually run, always stalls on the HTC logo. I also can't get the phone to start with the SD card in so I can't load files onto it.
One thing I've noticed (unless I've missed something) is you've not tried another SD card. I'd give this a go as it may be corrupt
EddyOS said:
One thing I've noticed (unless I've missed something) is you've not tried another SD card. I'd give this a go as it may be corrupt
Click to expand...
Click to collapse
I don't have a spare one but I might be able to get a mini sd card reader and then format it via windows. Would that work as well?
trancehead said:
I don't have a spare one but I might be able to get a mini sd card reader and then format it via windows. Would that work as well?
Click to expand...
Click to collapse
i'd try that if i were you. this goes without saying but make sure you back up first.
I actually don't think any of the above made any difference...
I just put back my SD card and the phone is working perfectly again. The only thing I can think of is that during the day it is too hot and it is cooler now (at night). This seems to be backed up by this thread - forum.xda-developers.com/showthread.php?t=676402
has been running since yesterday evening without a problem. Weird...

[Q] Please help - Desire very poorly.

Hi. I hope someone can help.
I've been using my desire rooted and S-OFFed running Defrost for sometime, all has been fine. Was playing Angry birds yesterday and the phone froze.
Pulled the battery and rebooted, carried on playing. Froze again.
Pull the battery again but phone stuck on the first splash screen. Fiddled a bit, couldn't get into recovery. So I left the phone on charge until the light went green, then removed the battery and left it overnight.
This morning I put the battery in and switched it on. It booted fine, but froze when I tried to unlock it.
I've tried pulling the battery again and again. I can get into HBOOT, but the phone isn't recognised for ADB or fastboot commands via USB. It often freezes even in fastboot mode.
I tried to do a clear storage, but that froze as well. Although a subsequent attempt appeared to work but the phone still won't boot normally.
So I can't reflash or do anything else. HAs anyone actually sent a phone back for repair with custom firmware/splash screen installed, as I don't think I'm going to be able to revert it to stock.
I've tried numerous restarts with and without a sim and an sd card inserted. Not sure what else to try.
Any help greatly appreciated.
did you wipe the dalvik cache through recovery?
try this if you can.
No I haven't wiped the dalvik cache. I have managed to get in to recovery on a couple of occasions. But the phone has frozen again navigating the menu.
I will try that if I get into recovery again though.
Thanks
Quick update.
After leaving the battery out for a couple of hours. I tried again and the phone started to boot. It got to the splash animation and the wipe had obviously worked because it was the DeFrost default of the X. This then looped a few times then froze.
I pulled the battery and managed to get in to Clockwork Mod recovery and did a wipe from there, which appeared to work, but then it rebooted by itself and I still didn't manage to do a dalvik wipe.
Now I'm back to the same point again. I can't get into recovery.
I guess I'll try again after leaving the battery out for a while.
One thing I did notice when in recovery was that the trackpad didn't work. I had to use vol and power keys. If I get into recovery again, I'll try a keytest if I get into recovery again.
And another update.
I got into recovery again and did a wipe dalvik cache.
I got the following error.
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
Dalvik cache wiped.
So I'm not sure if it actually did it or not.
I then tried to do a nandroid restore and got a similar error.
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount /sdcard
Then the phone froze again.
So I'm guessing something is corrupted here.
Should I try formatting the SD card. (I have backed up all the data I could using my PC).
i think your dalvik will have been wiped. i always get the same message.
have you tried it again but without trying to restore a nand?
Yes, I tried it again. I only seem to be able to get in to recovery after leaving the battery out for a while.
This time I did a dalvik wipe then rebooted, but it's just stuck on the initial splash screen again.
I'm pulling my hair out here (what little I have)
have you considered going back to a stock rom using an RUU or PB99IMG?
then you'd have to root again and restore your nand if possible/needed.
I'd be happy to try reverting to stock, but don't you need to get the phone to boot before you can do that?
I have sent this phone back for repair previously and done just that (it suffered from the overheating problem and had a whole new motherboard less than months ago).
After leaving the battery out again for a while, a normal switch on got to the animation splash then rebooted twice before freezing again.
Is this likely to be a corruption in the flash memory, or a hardware problem?
Hello,
I've got exactly the same problem! The phone freezes on the first splash-screen (not the Rom's bootanimation) and I can't get into recovery.
I'm running Oxygen Rom (2.0-RC6) and using Apps2SD in combination with an 8GB Transcend microSD card. I've only "rooted" it once using Unrevoked (long time ago), so I assume it is still S-On. I'm using clockwork's recovery, too.
At the moment I really don't know what to do.
What could I try?
pc99mk:
At the moment I'm leaving the battery out the phone until afternoon, hoping to get into recovery
Thank you in advance for every bit of an answer
Read up on the PB99IMG process if you can get into recovery (power & vol down).
Otherwise, the RUU will work if you can boot into fastboot (power & back key).
Sent from my HTC Desire using Tapatalk
Hi spadoleo.
Sorry to hear you're having similar troubles.
I'm sure mine must have some sort of hardware problem now.
After leaving the battery out for a while again last night, I managed to get into fastboot and flash the latest alpharev hboot, and clockworkmod 3.0.0.5 in the hope that my freezing problems there were due to a slight corruption.
Clockworkmod has definitely updated as the colour of the menu has changed, but it still freezes soon after entering.
I just want to try and get the phone looking as much like a stock phone prior to sending it back now.
Does anyone have a fasstboot flashable image of the following:
UK TMobile 'Pink Circle' splash1 image
Standard HBOOT
Standard recovery
Otherwise I'm just going to have to send it back to HTC as is, and hope they still fix it under warranty.
Or is there any way of getting a RUU to start doing anything with the phone in fastboot?
Or indeed anything else I can try?
See my post above.
You can run an RUU in fastboot.
Sent from my HTC Desire using Tapatalk
Hi mikep99.
Ok thanks for the advice. I'll have a read of the pb99img stuff.
I tried the RUU this morning in fastboot mode, but every time it justs sits at the 'Verifying information on your Android phone' for a while, then times out with a USB connection error.
I seem to have best results after leaving the battery out for a while (no idea why that should make any difference but it does), so I'll try it again in an hour or so.
Cheers
Install htc sync if you haven't already.
And try turning off antivirus and firewall on your PC
HTH
Sent from my HTC Desire using Tapatalk
Ok. I read up on the PB99IMG process.
I found a PB99IMG.zip file posted by Teppic74 which is a stock Froyo.
I copied it to the root of my goldcard and booted the phone.
It loaded the file and came up with
Incorrect CID error
update fail
I then kicked myself. I created the gold card to revert the phone to stock before sending it to HTC previously.
They replaced the motherboard. Would this have changed my CID?
I then thought 'no problem I'll just go through the gold card creation process again'
But although I can do stuff on the phone in fastboot mode, adb doesn't work in that mode. So trying adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
just gives an error.
So if my CID has changed, any idea how I can create a gold card with the phone in this state. Should adb only work when the phone is booted, or should it work in hboot or fastboot?
i'm not sure which PB99IMG you're trying to flash but i'd use this (if its not the same):
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.zip
with regards to the goldcard, have you mounted the sdcard when in recovery? and then running
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
again?
if that doesn't work, you can use another TMobile Desire to create it.
therefore, i don't think the mbo change should affect your goldcard????
EDIT - when you got your phone back from repair, was it completely wiped? Tmobile may have wiped/swapped etc.. the goldcard you previously made.
I think it was that image that I used. But I'll download it again just to be sure.
When the phone was repaired before, I sent to HTC directly and I didn't send any sd card or battery. So it should still be as it was.
So if the CID isn't motherboard specific it should still work.
Is there any way to check whether it is still a goldcard? I may have formatted it again (don't recall).
Although thinking about it, I still have the image file emailed to me when I created the gold card originally, so I could just reapply it and try again.
I'm out tonight, but will try a few things and post back with my results.
Thanks for your help so far.
Another update and things have moved forward.
It turned out I'd trashed my gold card, but I did still have the image file so I recreated it.
I then booted the phone again and it loaded the PB99IMP.zip file.
It then asked me if I wanted to perform the update. I said yes, and it updated the bootloader and rebooted. Then it froze on Checking PB99IMP.zip....
After leaving it 10-15 minutes I pulled the battery again and left it for a while.
I tried again just now.
I can see that it has updated the HBOOT, so I'm no longer S-OFF.
Just now I thought it was going to work it got about halfway through updating the system partition before freezing.
If only it had updated the splash1 image before the system, I might've had the phone in a suitable state to return. But it still shows my custom splash1 screen when powering on normally - then it changes to the piccy with the green arrows.
I'll try it again later after leaving the battery out for a while.
But the fact it freezes in the middle of such an update suggests it's definitely a hardware problem of some sort.
If anyone has any other ideas I could try, please let me know. But once again thanks for all the help so far.
Sounds like you're getting somewhere
Just keep on trying every now and again.
Hopefully it'll go through...
Sent from my HTC Desire using Tapatalk

[Q] Help! My desire keeps in the first screen after flashing the ROM

Hello, I got a problem when I flash the ROM for my desire with Clockwork 3.0.0.5 , need your help !!!
Thanks at first !!!
before flash the ROM, I have do the completely wipe and right partition for SD card (Fat32 +EXT4+EXT4+SWAP) or (FAT32+EXT4) according to the ROM requirement.
then after flashing, the flashing successful is displayed. but when I reboot the phone, it will keep in the first screen, and dead there.
And I have also connect it to the computer with ADB logcat, but nothing reported , it seems dead .
I have tried so many ROMs, only one or two ROMs can be flashed successfully and working ,also the information can be reported via the ADB logcat, others just display successful in recovery mode, but dead after reboot( I have waited for nearly 40 minites, nothing happed only the first screen ).
I only want to flash a ROM with new sense and data2EXT, but failed all the times!
please help me and tell me why !
thank you very much!!!
Does anyone know why?
I only want to flash a ROM with new sense and data2EXT, but failed all the times!
Click to expand...
Click to collapse
Why does it fail?
Try booting up with a completely FAT32 SD card and see if that changes anything. You could also try flashing with ClockworkMod 2.1.0.7 (what ever version it is) because you can get some errors with CWM 3.
Yes, I have tried for many times, and every time it is successful in the recovery mode and no error message reported,
but after reboot, it still dead at the first screen
why?
No idea. Devices are tempremental sometimes
I guess you could just wipe your phone clean with an RUU, root it again and then see if anything changes. Something could be corrupted.
Help! no one knows why???

Please help - Desire just wont boot up after flash!

Okay guys, here's the deal:
I decided to go for a new ROM, and now I can't get the phone to boot up after installing any ROM. Even the last ROM that I KNOW worked wont start up. They install fine, bit wont boot. I wanted to repartition my SD card, so I did, which I have now set to a 1GB etx4 partition and all the rest to FAT32.
All I get is that white HTC screen, and it'll stay there infinitely.
Any ideas?
Did you wipe before flashing the ROM? You need to do a full wipe (in. Dalvik cache) before flashing a new ROM otherwise it will hang on the boot screen. Another thing to bare in mind is if you're moving to a ROM using A2SD/D2SD that first boot can take a good few minutes so patience is also needed
I did, yes. Wiped absolutely everything, and it still wont boot. I've left it for at least 20 minutes and still had nothing
Was there a specific way my card should be formatted? I basically followed this guide:
http://forum.xda-developers.com/showthread.php?t=905089&highlight=partition
Except, I did all the work in Ubuntu, and with the memory card plugged into an Xperia X10 (I don't have a card reader.
Your first partition needs to be fat, the second ext. Also if you did it while the xperia was booted it probably messed up the process, best bet is to redo the partitioning while in recovery.
DAE_JA_VOO said:
Okay guys, here's the deal:
I decided to go for a new ROM, and now I can't get the phone to boot up after installing any ROM. Even the last ROM that I KNOW worked wont start up. They install fine, bit wont boot. I wanted to repartition my SD card, so I did, which I have now set to a 1GB etx4 partition and all the rest to FAT32.
All I get is that white HTC screen, and it'll stay there infinitely.
Any ideas?
Click to expand...
Click to collapse
I am experiencing the same thing at the moment. Except I can flash the latest CM7 stable (7.0.2.1) and it works fine. Any other ROM however, just won't boot.
I have tried all Alpharev HBOOT images and several other Sense based ROMs.
My SD has first partition FAT32 and 1GB ext3
I have tried wiping everything with ClockworkMod Recovery 2.0.5.7 and 3.0.2.7 and still no success with loading other ROMs apart from CM7.
The wierd thing is that I have been happily flashing ROMs for months now. The last one I successfully loaded was ][Sense2.1 GingerBread]InsertCoin CM7 v07 and the first one that failed for me was AuraxTremeGinger v8.5-test Gingerbread 2.3.3ยท (GRI40 |720p|A2SD+|Fast)
It's almost as if the Boot.img is not being correctly written to the boot partition?
Any ideas?
Which recovery do you have ? I had the same issue until I've flashed Ra-Recovery or you have to upgrade your CWM.
paul.c said:
Which recovery do you have ? I had the same issue until I've flashed Ra-Recovery or you have to upgrade your CWM.
Click to expand...
Click to collapse
I currently have ClockworkMod 3.0.2.7 but I tried with 2.0.5.7 as well.
Have not tried RA yet.
hey I too have the same problem of the white HTC screen after bootup.
Background: upgraded the Orange FR 2.1 Desire to the OTA upgrade recommended without thinking. It went through partially and finally wiped out the bootloader or corrupted the bootloader on the phone. There was no backup take nor an gold card made with the phone.
So. even I am struck with a non-booting Orange FR Desire at the moment.
Boot menu shows HBOOT 0.93.001. There is no recovery program either. Can only enter into the system menu for recovery.
Tried the following:
1. Tried update using some orange ROM (update.zip) through the sdcard, but the signature verification failed.
2. Tried a couple of RUUs, but it fails with error 131. I do not have a gold card with me nor do I know the CID.
3. Access through ADB : Does not list the device itself with the 'adb devices' command. Hence no access to the phone memory. So, goldcard ultility wasnt really helpful to get the CID
RUU is able to talk to the phone. This means that the USB port is still functional.
What can I do? suggest please.
It depends on which ROM you intend to install. Desire S ports didn't support ext4 until a today when baadnewz and snq (not necessarily in that order) issued a patch. This can cause bootloops.
I had CWM 2.0.5.7 and tried to install Robocik's RCMixS and it stuck at splash screen until I switched to RaRecovery. Subsequent versions of CWM are reported to work. That is my experience.
If you need further assistance please state which ROM do you intend to install. Good luck !

Categories

Resources