[Q] Bricking? Non-stop looping/cant get into Recovery Mode - G2 and Desire Z Q&A, Help & Troubleshooting

Hello G2 Forum users/developers.
I used ROM Manager today to upgrade Virtous Radio.
After this, my Tmobile G2 goes into perma loop. I get the HTC "quietly brillant" screen.
However, it would be in some sort of perma loop.
I am super newbie. I used this forum to unlock a few phones. I have ADB at home.
When I plug my unit/G2 into my computer via USB
and type "adb devices", this is what I get:
"SH12PR208475 recovery"
QUESTION:
What in the world do I do from here on?
BACKGROUND:
I have downloaded a bunch (5-7 different) of ROM via Rom Manager. The phone was acting up a bit, in that it would sometimes not go into Recovery Mode from ROM Manager menu. I would select it; it would turn off and then blank screen. To solve this problem, I would remove battery and turn it back on. This would remedy the situation.
After updating the radio via Rom Manager (choosing Virtous (Free) one), the phone appears to be "Brick like".
Please help. Thank you.
If you are local vancouver, pls call 604 838 5805. Thanks again

masadatech said:
Hello G2 Forum users/developers.
I used ROM Manager today to upgrade Virtous Radio.
After this, my Tmobile G2 goes into perma loop. I get the HTC "quietly brillant" screen.
However, it would be in some sort of perma loop.
I am super newbie. I used this forum to unlock a few phones. I have ADB at home.
When I plug my unit/G2 into my computer via USB
and type "adb devices", this is what I get:
"SH12PR208475 recovery"
QUESTION:
What in the world do I do from here on?
BACKGROUND:
I have downloaded a bunch (5-7 different) of ROM via Rom Manager. The phone was acting up a bit, in that it would sometimes not go into Recovery Mode from ROM Manager menu. I would select it; it would turn off and then blank screen. To solve this problem, I would remove battery and turn it back on. This would remedy the situation.
After updating the radio via Rom Manager (choosing Virtous (Free) one), the phone appears to be "Brick like".
Please help. Thank you.
If you are local vancouver, pls call 604 838 5805. Thanks again
Click to expand...
Click to collapse
Im confused about how you updated your radio via rom manager.
But im wondering if you flashed the virtuous unity rom and you have the G2 Hboot.
If this is what you did your device is not bricked.
Can you tell me exactly what you flashed.
And pull you battery out, put it back in and then press and hold the power button and volume down. This will take you in to the bootloader. Can you let me know what it says the top 2 lines of that screen.
Also from the bootloader you can access recovery, using to volume keys to navigate and the power button to select
Also the latest version of clockwork mod recovery has some issues when you try to boot directly in to it. You can either use an old version of cwm or have a look at 4ext recovery in the dev section
Sent from my HTC Vision using Tapatalk

Hello there. Thank you for replying. I just remember I did something silly last night. I downloaded a something called "ASTRO File Manager" via Market, using the search protocol "file manager".
I then used this program to delete "su" (super user), and one called "Super User" (the ones with the crossbones I think).
This morning, I used ROM Manager; there is a "premium" section and there is a "free" section. I used the second one, the 'free' section. At the end, they had "Virtuos" ROM(wrong spelling I think). In the subsection, there is a "Radio Config" or "radio" something. I clicked onto this. It downloaded. Then it told me to say OK to install. It did all of that. Then the screen went blank, as it should, because it was being auto booting. After that, nothing. Just a loop of "HTC" and then "quietly brilland" after that.
I had not mentioned about the deleting of 'su' file and 'superuser' [crossbone] before because I had forgotten it.
Right now, when I use ADB on my computer, I see the device name and besides a series of numbers is the word "recovery"
Like this:
C:\ANDROID\G2\MISC>adb devices
List of devices attached
SH12PR208475 recovery

Oh, you asked about what I see when I press Volume Down button and Power. This is what I see.
VISION PVT ENG S-OFF
HBBOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.03.02.26_M
eMCC-boot
Aug 20 2010, 16:51:01
HBOOT
<VOL UP> to preview item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SYSTEM INFO
IMAGE CRC

masadatech said:
Oh, you asked about what I see when I press Volume Down button and Power. This is what I see.
VISION PVT ENG S-OFF
HBBOT-0.76.2000 (PC1010000)
MICROP-0425
RADIO-26.03.02.26_M
eMCC-boot
Aug 20 2010, 16:51:01
HBOOT
to preview item
to next item
to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SYSTEM INFO
IMAGE CRC
Click to expand...
Click to collapse
OK, can you access recovery via the bootloader. If you can you just need to either restore a back up. Or do a full wipe and flash a new rom.
The file you tried to flash was it radio to ril auto matcher?
And as you are rooted anything to do with super user on your phone is absolutely essential.
Sent from my HTC Vision using Tapatalk

You wrote: "If you can you just need to either restore a back up. Or do a full wipe and flash a new rom."
Sir. I have no idea how to restore a back up or how to do a full wipe. I would prefer to do a full wipe but again, I have no idea how to begin. I follow instruction on XDA here and managed to unlock and root 1. HTC TMOBILE G2 and 2. HTC TMOBILE 3G and the 3G Slide.
I think I can follow instruction; having said that, there is a huge huge amount of information on here and I am not sure where to start. Please help.
You wrote: "ril auto matcher"
I believe I did this; this morning I did this.
You wrote: "And as you are rooted anything to do with super user on your phone is absolutely essential."
Yes, the phone was unlocked and rooted. I used the intruction on the Wiki portion of XDA Forum.
Please reply at your convenience. Thank you again for taking the time out to help me. Thank you, thank you and more thank yous (from Vancouver BC Canada)
phillip

PROBLEM FIXED
This is what I did. Some is due to reading replies above. Thank you CJWARD23
Some I just played around. Not sure what happened, but I think it is better I post something here since I already spent enough bandwidth above.
When I tried to get the phone back to the Bootloader screen in order to do a "backup and restore", all I got was a black screen, with a "HAT" and an orange curvey ARROW.
I was freaked out and scared. The screen had "reboot" and a series of things you can do, ie wipe the cache, wipe the davik cache; I am not sure if this is a bootloader screen or not. But I wanted to get the the "backup and restore" function. Well, when I push the power button to execute this command, I got the HAT and ORANGE ARROW.
This is why I posted this post on here.
Since I unlocked and rooted the phone using intruction on here (XDA), I went back to my old files on my desk top.
Because I had used "Astro File Manager" the night before to delete "su" file aka superuser file, as well as the file with the crossbones (Super User).
Please dont ask me why I did this. We in the recovery world calls it a temporary lapsed of insanity.
Anyhow, I used ADB on desktop to put back SU and SUPERUSER
then i went back to do the powerdown and power button, to get at the recovery screen
i then had the same HAT and ARROW deal
this time, I use the button on my g2, it is not the power button, it is the one with the glowing light (when you receive a call), it is actially the only button on the surface of the phone, it is below the screen. that one. i push that button to exectute. I got a list of all my old ROMS, i click onto one and walla..... recovery
I am still not sure what I did wrong, or what I did right. I just know that I had a lot of help from the gentleman/gentlewoman above - mr/mrs CJWARD23
and in the mean time, i did a lot of praying and did a lot of reading on here as well as trying this or that.
If I were you, try to avoid deleting SU, su, or anything with da crossbone. Laughs.
I hope this helps. Have a nice day from Vancouver BC Canada. 1422hrs/pacific standard time.

Related

[Q] Can not escape bootloader - volume and power keys unresponsive?

Hey guys,
I hope you're all well.
Great forum by the way.
I've searched extensively for solutions to my problem, yet I've been unable to find anything.
I think the problem started yesterday, when I restarted my phone and for some reason it went into safe mode.
I didn't lost any functionality so I didn't care too much until this morning, when I tried to get out of safe mode.
My phone has taken me to the bootloader (white screen with skateboarding Android) and for some reason, the power key (used to select options) and the volume keys (used to scroll) are not functioning.
As a result I cannot click or choose anything and the white bootloader screen persists in limbo.
I desperately need some suggestions, any help is very much appreciated.
Just so you know:
I've taken the battery out and put it back in, which takes me straight back to the bootloader screen, same with sim card.
The phone is running Coredroid (can't remember which version).
Has S-OFF.
Sorry I'm not much of an expert...
Also, on startup, phone says something along the lines of:
SD Checking...
LOADING... [PD98DIAG.zip]
NO IMAGE!
LOADING... [PD98DIAG.nbh]
NO IMAGE OR WRONG IMAGE!
LOADING... [PD98IMG.zip]
NO IMAGE!
LOADING... [PD98IMG.nbh]
NO IMAGE OR WRONG IMAGE!
Kind regards,
- Ric
Something has become corrupted.
Best bet would be to use an ruu 2.36.405.8 and lower, once loaded up, skip through the setup and then root again.
http://driphter.com/index.php?topic=3867.0
after you've done all that, install rom manager, and then restore your last backup.
Just a quick update.
Managed to get into Clockwork Mod Recovery.
Got the SD Card to mount.
Formatted it in windows.
Copied over Coredroid.
Went thru the install process.
Installed without error.
Booted up.
Took it's time, displayed the Coredroid animation but then vibrated and took me straight to Bootloader again.
Any advice or best to do this RUU thing?
Would this:
RUU_Ace_HTC_WWE_1.32.405.3_Radio_12.28b.60.140e_26.03.02.15_M3_release_155032_signed
Be ok?
Am I in the right ballpark?
Truly got no clue when it comes to this stuff
use the 2.36.405.8 RUU, then you wont have to spend your time updating the radio and such, that version of gingerbread is rootable using gingerbreak (so just follow that path of my method and you're set)
JSLEnterprises said:
Something has become corrupted.
Best bet would be to use an ruu 2.36.405.8 and lower, once loaded up, skip through the setup and then root again.
after you've done all that, install rom manager, and then restore your last backup.
Click to expand...
Click to collapse
Hello mate,
Just a quick question.
How do I get my computer to recognize my phone prior to running this RUU thing?
Considering I can't scroll or select anything in bootloader screen?
Can I run this RUU thing from ClockworkMod?
Kind regards,
- Ric
you run it from your pc. its an advaced installer that pushes the stock rom to the device and overwrites everything... it will put the phone into a different bootloader state than the one you can nav through.
Also, sometimes the phone is booting into bootloader, while other times it is booting into ClockworkMod.
It seems I have no control over which screen it initially boots to.
I DO HAVE options in ClockworkMod because my volume keys allow me to scoll and my power button allows selection, whereas in bootloader, the keys do not function.
Could you PLEASE provide some advice on how to boot into ClockworkMod rather than bootloader?
Kind regards,
- Ric
JSLEnterprises said:
you run it from your pc. its an advaced installer that pushes the stock rom to the device and overwrites everything... it will put the phone into a different bootloader state than the one you can nav through.
Click to expand...
Click to collapse
Yes I do realize I run the RUU from the PC.
I don't think I was very clear.
I was trying to ask you what state the phone needs to be in?
Do I have to mount the SD Card from ClockworkMod?
Or can I run the RUU while in Bootloader?
Does it matter?
Neither have worked.
I get a 170 error (USB Connection error).
The RUU cannot see my phone.
I was wondering if there's a way to fix this?
I have also now tried to install Leedroid and Gingervillian.
Both have installed perfectly but refuse to boot all the way.
Instead taking me back to Bootloader...
Ok, Leedroid somehow booted.
No network or anything though.
Very unstable...
if the phone is running leedroid now and you have the htc sync tools installed (but without sync running, just needs to be installed for the drivers)
leave it as it is connected to your pc, doesnt matter if debugging or anything else is on or off. just leave it alone sitting where it is on your desk or wherever it is...
Start the RUU, and then just follow the path the installer takes you through, then let it do its magic...
Ended up d/l Cyanogen.
Installed it.
Working, detected networks, wifi is connected.
All good I suppose.
That was a bit scary!
Thanks for your help mate.

[Q] Evo 4G Near Death? Desperately Seeking Help!

Hello all. I am a noob to working on rooting or doing anything of the sort with phones. I am more for desktops. With that said, I am in DESPERATE need of some guidance with my EVO 4G. I did not attempt to root the phone, I assume someone else did before I got it (from EBAY)..the phone itself appears to be brand new with no scratches, or any other markings. When the phone turns on, the screen shows:
SUPERSONIC UNKNOWN_ENG_ S-OFF
HBOOT-2.10.0001 (0?n eso=10 noig"t-"><gtredfutre
MICROP-041f
TOUCH PANEL-AMTELC03_16ac
RADIO-2.15.00.05.02
Mar 30 2010, 11:24:04
<vol UP> to previous item
<VOL DOWN) to next item
<POWER> to select
Bootloader
Reboot
Reboot Bootloader
Powerdown
ON THE OTHER MENU:
the only difference is that is says clear and SIMLOC
Since, I am new....I of course researched what the issue could possibly be. I read that some have issues with the memory card so, after trying the two that I have...I went and bought a new one. I proceeded to try various PC36IMG files and each time I got the 'MODEL ID INCORRECT' message. I tried downloading items like unrevoked and RUU software (I also downloaded two different drivers) but, with one driver my device shows as 'my htc' and with the other drivers, it shows as 'android bootloader'.
So, I cannot actually access the device through the computer. I downloaded a 'pack' called Evo Brick Fix but, had no luck with it when trying to put on the sd card and then into phone. I have tried putting Amon Ra on the sd card and attempting to load on the phone but, whether it is Amon or another PC36IMG, I will say that a pc36diag file one other file cannot be found. It tried to load the PC36IMG file and as soon as the bar is all the way filled, it says Model ID incorrect.
Somehow, through my fumbling around, I managed to change out some files between PC36IMG downloads and I managed to get the phone to BEGIN loading the PC36IMG but, it says parsing for about 1-2 seconds and then very quickly flashes something about NV so (loading NV - I think...it flashes that extremely fast) and goes right back to the screen you see pictured above. It does not do differently if I try it on phone in hboot or fastboot.
Can some please help with any advice? It would be greatly appreciated as I am at my wits end and feels this Evo is as good as dead.
Thanks,
Anna
Try and search here on XDA for 3.70 ruu tutorial.I've tried posting the link but it won't work unless its directed.The 3.70 ruu is the one you want to run with your current radio and hboot versions and it should get you up and running.

My noob review of WildChild 3.3

Howdy y'all.
I thought I would make my first post in here, since this is the entire reason I found xda-dev in the first place
I have a WFS from T-Mobile that was constantly giving me low-memory errors and FC's of T-Mobile's bloatware. I was tired of it, and decided to do something about it. I unlocked the bootloader via htcdev, flashed Clockwork Mod recovery, and installed WildChild 3.3 ROM as my first adventure into rooted androids.
My first impression of it was "meh". I had grown accustomed to the Sense stuff, and WC3.3 just didn't seem as polished. I haven't quite figured out where the logs are, or I'd attach them for the few bugs I found. The first one I discovered, if I go into settings, then "Personalize", it goes right back to the home screen.
Bug #2, I can't remember the name of the app but it was one of the two file managers. Root Browser Lite is still on the phone, so it's the one with the file cabinet icon. It would FC as soon as it opened, so I uninstalled it.
Another bug that popped up today - I was multitasking by running the stopwatch in the clock app (timing the chicken on the grill :silly: ), listening to Pandora, and browsing Google Play looking for the battery app that shows which apps are using the battery. The phone locked up hard - no buttons, even the power button, gave any response. I had to remove the battery, which isn't easy in an Otterbox case.
I'm going to try and find the logs for tigger before I throw RobotoMod on it tonight, but I have a feeling I'm not going to find them.
You forget to mention invisible caller id picture during call receive . You can try dragon fire Rom or wait for kims mod supreme .
I didn't notice that because I don't use picture Caller ID. I'm an old phart - my first mobile phone had an lcd screen, and this is only my 4th phone ever
what type wilddire s? CDMA or GSM?
im on a VM Wildfire S (CDMA), i have found to get things working right on WC3.3 i have to use the hense mods Virgin Mobile Patch, also before i switched to the CWM Touch Recovery the first config seems to hang or crash cause of the use of Flash Player in startup somewhere. Sometimes it works better to start first, do config, then install Hense VM patch in recovery.
It's a T-Mobile GSM. I didn't use CWM Touch, and I never even tried the flash player. The phone worked, though - had no problems booting.
Im gonna stick with Wildchild 3.3 coz i can feel really good performance from my phone. My antutu score is 2101. i was under the impression that the caller Image not showing up was due to improper flashing. Yesterday, i was trying to use a live wallpaper, but It seems i cant select one even though i have it installed. and I also noticed that sometimes when you attend a call while the phone is locked and you drag the green call answering ball into the ring, the phone simply unlocked instead of answering and then i had to answer it by clicking on answer(like how you normally do it when the phone is unlocked). And one more thing, i am unable to play GTA 3. Now i can only hear the sounds...... the screen goes blank as soon as it loads. it was fine on all the other roms(though it was a bit laggy[cant expect too much on ARMv6]).
My wife has a Htc Wildfire S and i tried to install Wildchild 3.3
I ve done everything you said in the instructions but when it restasrts it stucks in the white screen with the green logo HTC.
When i press the power button and the left down i see this in my screen
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.08.0099
MICROP-0451
RADIO-7.53.39.03M
Nov 28 2011, 19:09:21
I think that these are correct. CWM is version 5.0.2.6. When it starts its looking for a file named "PG76IMG.zip". This file does not exist. So i am doing this steps : Recovery --> Wipe data/factory reset (twice) --> Advanced --> Wipe Dalvik Cache (twice). Then i go back and i choose install zip from sd card --> toggle signature verification until i see Signature Check: Disabled. After that i choose the ROM i want to install. After the succes of the installation i reboot the system and it stucks in the white screen with the green logo HTC.
I have created partition in SD card. I have made an partition ext4 of 1,2 GB. Fat32, and primary
What am i doing wrong? Please i need your help!

May have bricked DHD after using AAHK

So, figured I'd attempt to root the thing today via the AAHK on my locked DHD. According to the effen manual, I won't need to gold card it beforehand either.
I went through the process, and I was told that the ROM that I had installed (2.5.3? Sense 3.0) had to be downgraded, so I went ahead with it. After downgrading, I was brought to an unresponsive bootloader. Being patient enough, I let it sit while I watched a movie, yet nothing happened after. I took out the battery and restarted it, and all I got was the Hutchinson 3G (my carrier) logo and it just stops there.
When I try booting in recovery mode to get to the bootloader, it does so, but it hangs.
After enough tinkering, I noticed the bootloader was only responsive once I rebooted without the memory card inserted. The phone itself is still inaccessible as it just stops at the 3G logo.
So far, I've tried to restore it through an RUU, but since it's still (I assume) carrier locked, I have to find the ROM that shipped with it. Unfortunately, I can't find a ROM that caters to Hutchinson 3G ROI (Ireland), so right now I'm downloading a UK version of it to see if it works. Apart from that, any recommendations on what I could do next?
Thanks :3
people are gonna need a little more info eg. what does it say on the boot screen s-off etc
what rom your trying to flash, formatted sd-card or not, possibly a corrupted download
AAHK does the business well, but can baulk at the slightest thing.
fairly new to some of this myself, but learning, my DHD took 4 attempts to finally do now on JT R4
Oh, mmkay:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
eMMC-boot
Apr 12 2011, 0:55:45
-----------------------------
Anything else I should include up there?
As for the ROM, I wasn't trying to flash anything bar the one that was downloaded through the AAHK client itself during the downgrade process.
After more tinkering, I've decided to leave it till today afternoon. Though I've made a few observations; so far
- The bootloader works fine when I turn it on WITHOUT the memory card
- The phone gets detected under the name "Android 1.0" when plugged in via USB both in hboot and fastboot. The fact that it gets detected I'll assume is a good thing
- Which leads to the second bit; it can be restored, since I've tried an Asian DHD ROM. It didn't complete because I was apparently supposed to find the appropriate ROM for it, which I assume is the H3G ROI version of it
- Aaand, the ROM still won't load up, and gets stuck at the H3G boot logo.
- According to the effen manual, it could be that my SD card was corrupt, so now my intention is just to merely restore it until I can actually afford to attain another memory card, which will be in a good few weeks and I don't wanna be smartphone-less for that period of time. But the only problem is; how?
if memory serves there isnt a rom in AAHK. the zip you intend using should copied be on your sdcard and initiated via recovery - vol down and on button. you should also be "s" off - did it offer to downgrade first [if needed]
from the manual
Insert the SDCard into the phone
Boot the phone
Turn on USB Debugging (Yes, plug it IN - use original cable plugged directly into the system board.)
IMPORTANT: Turn phone to charge-only mode. The phone stays in charge-only mode throughout this entire process. To make sure of this, check the default (menu > settings > connect to PC > charge only)
Win7/Vista: Right click on hack-ace.cmd and start as administrator (This will start the tool and bring you to the main menu)
option - 1
Install Clockworkmod
Clockworkmod version 5.0.2.7 -- yes
How to flash a custom ROM with ClockworkMod Recovery
Place the zipfile to be flashed on the sdcard. Do NOT unzip it.
Froyo disable Fast Boot: Menu > Settings > Applications > uncheck fast boot
Gingerbread disable Fast Boot: Menu > Settings > Power Options > uncheck fast boot
Turn phone off, no usb connected
Hold down vol- button, then press power to start, keep holding the vol- down button until Hboot menu shows up
Use the vol- down button to scroll down to recovery after some file checks are done (they will flash by quickly)
Press power to start recovery
Use vol down button to navigate, and the capacitive search button (bottom row of buttons, far right) to select
NOT VERY OPTIONAL/STRONGLY RECOMMENDED: If recommended by rom author or if flashing over another rom type (ex: cyanogenmod over anything else), wipe data/factory reset in Clockworkmod Recovery
Install zip from sdcard > choose zip from sdcard > select zipfile > Yes - (name of zipfile)
Repeat choose zip from sdcard for any add ons (gapps, themes, kernels, etc)
Press back button when flashing is complete until "reboot system now" is at the top of the screen.
Press power to reboot the system.
If desired, return the fast boot setting to ON in settings. (See above)
once yu crack it you'll see where you were going wrong
radio flashing is the easiest way to brick if you dont know exactly what your doing 99.9% of other stuff is recoverable
restoration is a more complicated path than rooting for noobs
I'm aware that there's no ROM included with the AAHK, I'm referring to the one that was downloaded THROUGH the AAHK when it said I'm gonna have to downgrade it beforehand.
And with reference to hboot, that's where another problem lies; my memory card is the one causing hboot to freeze. Hence, removing it prior to booting is the only way to get to it.
can you rerun AAHK and make a goldcard during setup and go that route -- wont help i know but being as its still "s"on you can return under warranty aslong as you dont send sim and sd-card tell them it wont go past h-boot.
if you have a card reader then format the card to make sure its clean, the drag and drop the required files on it - i have a lappy solely for this job with AV etc permanently turned off
Well, I'll rerun AAHK when I can find the SD card adapter, but since I've only recently moved house, it's gonna be near impossible until I get time off to unpack, which, till then, I'm still gonna need a functioning phone, so right now, I'm just looking for ways to return it to stock :3
i cant assist any further then as i've not yet RUU'd any devices as of yet.
hope you get it sorted
Thanks for trying anyways :3
I've been searching for an Irish RUU. Currently trying a UK version of it hoping it MIGHT just work. Anyone have more ideas?
Edit: Ok it didn't. Posted on the Three Ireland support boards trying to see if I can get an RUU

[Q] can someone Help with fixing my DINC after Unrooting gone wrong?

Ok, so have a serious issue
at first i was able to successfully root and flash clockwork mod recovery on my DInc using the rooting method from unrevoked 3 and was running Clockwork mod recovery +Cyanogen mod7 through the Rom manager (cannot remember exactly which versions.) it was all running fine, then just decided to unroot it with a few different methods (one didnt work and the others failed as well, maybe because i mismatched the stuff i used during the First try at the unrooting process..but because i tried one method after the other, and it was soo long ago, i forgot exactly how i ran into this problem
basically somehow i screwed up the Unrooting process.
SO now I am Having the System UIDs are inconsistent message every time i start my Incredible, Tried recovery that didnt work, tried factory reset+ erase all data on phone SD card (i probably accidentally erased the recovery image) it seems to reboot and be all restored, like a stock image, but weirdly the Superuser Ninja holding the AR15 still shows up in my app drawer (even after i unrooted and restored everything.) so i i decided to check out if the permissions were still enabled and they were not... SU shows up and doesnt function (just blank). I investigated further by downloading ROMmanager and then everything ended up forceclosing over and over again...I went to download "# Root Checker" and pressed "check" and it proclaims that its not rooted but under "User" it said "root"... i guess that its saying im rooted but im not?!?! LOL
anwhyo here are my DInc Specs as of Right now:
my DInc is an SLCD, running android 2.3.4. baseband is 2.15.10.07.07
Kernel 2.6.35.13-g03546aa
[email protected]#1
Fri Oct 7 10:52:52 CST 2011
software number 4.08.605.2
im still able to Access HBOOT and the screen says
*** UNLOCKED***
INCREDIBLE XD SHIP S-ON,
HBOOT-1.02.0000
MICROP 0417
TOUCH PANEL- ATMELC03_16ac
RADIO-2.15.10.07.07
DEC 21 2011,23:37:16
when i tried to see if i can reflash it through fastboot, the device manager in my W8.1 Pro 64 bit says "Device failed Enumeration" and USB notification popped up from the system tray saying that the device wasn't recognizable
so the drivers provided by Unrevoked for enabling the phone to be detected dont work, and the HTC Sync program doesnt even detect the Incredible.
However,,,,
the Fast boot, Boot Loader, and HBOOT still works upon pressing the Volume-down + Power and am still able to access Internal Phone Memory AND the SD card when the Phone is plugged into my computer via micro USB (so it looks like im able to flash things to it, but stuck as to how and what)
Because im still able to access the the SD card and internal Memory,
I tried putting PB31mg.zip on the root of the SD and ran HBOOT> and i gave it a second to detect the file.. then it said "Main Version is older Update Fail!"
the guy in this thread http://forum.xda-developers.com/showthread.php?t=1286223 seems to have had Similar problems..... I have added symtoms and issues on top of the whole 2.3.4 with S-on and Radio 2.15.10.07.07....
I just want to get back to vanilla-stock on my incredible with absolutely no modifications and without the System UID/feeling lucky pop up bugging me. and dont care what route i take, weather it be rerooting and reflashing , just reflashing. i just dont know what to do to get it that way from here.
Can anyone please help me figure out how to get back to normal with this DInc???
Im sorry if i dont make any sense im having a hard time explaining it. if you do understand me, i would appreciate your help. also if you need me to clarify things just ask me.
I'm a little rusty, but I remember this was the preferred method for rooting because of problem with the 1click unlockers,
(nuts, can't post links yet)... Google, "[HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev" and look for it on androidforums.com
Try picking it up from step2, just keep the unlock_code.bin from miniadb_inc files from step1 on the phone. As long as typing 'adb devices' displays your phones serial number, you should be ok. As a long shot, you could try a PC with Windows7.
Try this ruu thru hboot http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip

Categories

Resources