Develop Bugs

Big time unrooting problems

Hi, Last night i rooted the phone, partitioned the sd card, installed radio .08 and so on.
Rom were working fine but i just wanted unroot cuz of the warranty issue. Heres to the problem. When i connect the phone it all looks fine. The computer finds it and i can mount the sd card and so on. But when i try to boot with the official ruu it just loses the connection to the computer and stops with the "black" "htc" logo on the screen.
Here's what i've tried: Reformated my SD card with fat32, nandroid back to stock rom (the one you get directly after rooting) and i've tried degrading my radio image to the one .04. have also reinstalled htc sync twice and get same problem...is the phone bricked in any way? im pretty noobish at this so it was foolish of me to try it on my own i know.
I can still flash roms i looks like, just not go back to unrooted
I've done the unrooting process before and it worked like a charm. why not now?
the ROm was Leedroid 1.4 if it helps

Pop onto the #modaco irc channel on chat.freenote.net
This sounds sortable.
Sounds like its just a matter of flashing the stock rom directly from the SD card....Feel free to pm me whilst in the channel

Have you try to boot your phone into Hboot/Fastboot before you execute the RUU?

After you have run the RUU file and it asks you to connect the phone, go to your windows temp folder (start->run->%temp%)
Sort folders by date and open the most recent, inside there you will see a file called rom.zip (about 120 megs) copy that to your SD card and rename it to PB99IMG.zip.
Turn the phone off and reboot holding the vol down key, enter recovery and it should scan the SD card and offer to flash the PB99IMG.zip.
Job done!!
This will also downgrade the radio images, so beware it takes a couple of boots.

I unrooted today and had the same problem, its a simple solution. When you run it the first time it gets stuck on the black screen, dont do anything with the phone, leave it connected, exit the ruu, then run it again and it'll work

I had something like this too. Just close flashing software in windows when it says connection error, unplug usb, plug it back and start firmware flash in windows again.
edit:i was too late.. lol
edit edit: i did unplug, but looks like its not needed

My solution is more elegant though

pmcguire said:
My solution is more elegant though
Click to expand...
Click to collapse
It sure is nerd way to go!

[Q] Need Help For Droid Inc *Major Problems* 5 beeps and green flashing light

OK. Im new to XDA and i have read alot of articles trying to fix my screwup. Hopefully someone can help. I was once rooted and i had redemption rom on and i tried to install cm30 nightly and got stuck somewhere and started to try to do wipe and clean amopngst other things and almost bricked it totally.The main thing that happens is when i press power i get 5 vibrate beeps and a blinking green light. i can go to hboot by pressing power and down but i cant go into recovery. Among other things i can plug usb and shows hboot usb but computer only shows android boot loader under device manager.
Now here's where it gets even weirder. I tried to install the pb113img.zip. when i did everything said ok while installing and when i got the choice to reboot it went to a green recycle looking thing then it went to a blank screen and 3 beeps with green blinking light.
I went into fastboot and hit reboot and it did boot into the stock 2.2 rom but if i disconnect a usb cord or when plugged into the wall the phone dies and goes to the blank screen with 5 beeps and blinking lights.
while in hboot the recovery choice is not working and neither is factory reset.
I hit fastboot the choice for bootloader takes me back to hboot.
Now while the usb plug is in the hboot says hboot usb but when i did get it to boot and plugged the usb in it doesnt show on my computer it does however show android bootloader interface on my device manager. Also the sdcard will not read on the phone but the sd card will read in a sdcard adpater where i can transfer files.
I have 2 sdcards and a sd adapter and htc usb cable and htc outlet charger and 2 batterys.
Here are my stats:
S-On
H-boot 0.92
touch panel-ATMEL224_16
radio- 2.15.00.07.28
Please somebody help me i been trying different methods but running into circles here.

If your S is on and it looks like it is and your running the stock 2.2 bring it in to the store and they will warranty it for you.

I did think about that because stock rom looks to be on and s-on as well just wondering if they could be able to tell through h-boot

Unfortunately this is a hardware error code, and you'll probably have to get it replaced.. My Inc came out of the box doing this (had it shipped to me), and the only option I had was to take it right back to the store.
I was able to boot mine normally if it was plugged into the computer at the time, so you might want to try that and see if you can at least verify the installed firmware. Otherwise, a warranty exchange is your only choice.

My incredible started doing the same, it all hapened when i mounted sd in recovery mode and then i was playing with diag mode to flash it. Since then its doing the vibrate and green light thing. Also I rooted it and my s is on. Also I can use the phone if i plug in the usb while turning on and then quickly take it out. Only problem is the phone doesn't detects the internal or external storage. I even got phone to be detected by unrevoked, but it is stuck as pushing recovery since phone doesn't detects the storage. BTW I already tried the Official PB31IMG zip.
Please any help is greatly appreciated.

Same issue flashing CM7 RC2. Could not fix it, Verizon is replacing it.
Here's a few threads to follow:
http://forum.cyanogenmod.com/topic/18381-bricked-my-incredible-installing-cm7-rc2/
http://forum.xda-developers.com/showthread.php?t=808294

It is probably a USB brick
I had the same problem with my HTC Legend a few days ago, it turns out to be a USB brick, which means something had corrupted the misc partition. The fix is simple, just flash a good misc image back to that partition and everything is back to normal, there are tons of USB unbrik TUTs out there.
Hope this could help.

[Q] Tried to root phone failed now SD and debugging don't work

I tried to root my phone but on the last step it said the internal memory ran out.
I Restarted the phone and it kept restarting at the boot screen. so I went to recovery mode and used a recovery file name (Esprimg.zip). After that My phone would only start if there was (A) no SD card when starting. or (B)the phone was connected to the computer but after I unplugged it from the computer it would reboot. Now with the phone on it will not pull up the SD card it does not even see it in normal operation but it does see it in boot mode(volume down + power).Also debugger mode will not work on my phone the box is checked but no icon appears at the top and when plugged into my computer it won't recognize the device.
Please help me even if just to get it to normal operation I've already done a hard factory reset.

76 reviews and I have not even got an idea I guess I'm alone on this problem.

I don't know lol, all I got was, have you tried a differend sd card or formatting the one you have? I am not sure what the essential things you need in there, but I would try to remove things till you only had the essentials. Back it up first of course.

[Q] Rooted Desire Hd help please

Hi had all different roms on my DHD and settled on Ice cold sandwich which it has been running for a few months now, earlier on today I noticed that it had gone off and only the backlight was on, So I restarted it and it started loading the screen up but then just went into a loop.
So i pulled the battery and went into recovery and reloaded the ICS rom, but know it just vibrates 5 times and shows the splash screen and goes off with just the backlight on again.
I can get into fastboot but when i press the button for recovery it does the same I've tried every pd98img I could find and it says wrong image after I try and load them.
And when I connect it to the pc it can't be recognised by htcsync or thru any adb commands, and windows tried to load a driver called Q_USB-DLOAD or something similar then loads a qualcom usb driver but adb commands still won't recognise it, been looking all bnight for an answer getting desperate.
Thanx in advance Michael

1. Remove your sd card and try to boot up again if it boots up then there might be something corrupted on your sd. (Possible sd may have gone bad)
2. Try to enter hboot with power button and volume down at same time to see if you can get into hboot. If it dont your boot img may be damaged and you may need to push it again thru ADB.
3. If you can get into recovery try full wipe and reflashing rom. (You may have to use an adapter to get rom on to sd since computer dont see phone then place sd back in phone)
These are just a few ideas you can try hope it helps.
EDIT: Also there is no need to create a double post of the same issue. This is what causes clutter among the forum. When you post a question you need to wait for an answer not ask again when there is no reply on your first post. Thank you

[Q] recovery without USB connection?

Is there any way to recover the fairphone if the OS doesn't boot any more and the USB connector is broken (out of the mainboard; irreparable)? I have used the phone with the broken USB connector for about half a year now with an external charger, alternating between two batteries, without any further problems.
This morning when trying to get around the restrictions of an app on the Play Store I backed up my build.prop, made a couple of changes to it ('ro.product.model = Nexus S', and 'ro.product.manufacturer = samsung') and then overwrote the changed file again with the backed up original. Everything worked fine until I turned the phone off. Now the booting process gets stuck on the blue 'Fairphone' screen. I can enter recovery mode and have attempted a hard reset (step 2 of fairphone.zendesk.com/hc/en-us/articles/201134418-How-to-perform-a-Hard-Reset-on-my-Fairphone – unfortunately I can't do step 1) – alas, to no avail, factory reset and cache wipe don't seem to help. Perhaps this is not too surprising if the boot failure is in fact due to some hangup with the build.prop (it could be something completely different as well though, these things may have just happened to coincide).
I'd be really grateful if anyone can help with any of the following (again, all of this with the caveat the USB connector has broken out of the mainboard):
1) Is there any way at all to access the external SD from recovery mode (if so, I could download the Kola Nut installer and see if an update sorts the problem)?
2) Is there some way to check what's wrong with the system from within recovery mode, i.e. have a look at the build.prop (if 1) doesn't work)? Enable ADB over WiFi from recovery mode somehow?
3) Is there any way to get the user data backed up off of the mainboard (say onto external SD) from within recovery mode or otherwise (if everything else fails and I have to get a new mainboard)?

Hey, I#m also interested in a solution. My usb is also broken and I just bought a second Battery and external Charger, a few days ago I flashed the unofficial 4..4.4 Rom and I won't to update it from time to time, so I hope that is possible without a Connection to the PC.
P.S. : Its a shame that the USB Port is so fragil, I think there are many users out there with this problem...