[Q] can someone Help with fixing my DINC after Unrooting gone wrong? - Droid Incredible Q&A, Help & Troubleshooting

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

Related

[Q] Stupidly Reflashed - Need Help to Recover

Hey all,
I am not a huge Smart phone buff, been dinking around on the tutorials. So I succesfully unREvoked my phone last night and it was working. I was doing an Update to the WiMax and for whatever reason I had an old PCIMG file left on there and I stupididly clicked yes to update to that image.
Well it wiped out my recovery and now I am not able to do anything (no card reader either). When I goto Recovery just a red ! and when I try to boot it just keeps looping me back to the bootloader.
I have tried connecting it to the computer, which has the Android drivers etc installed. The computer detects the device in some form, but when trying to get access via ADB no devices found. I am not really sure how to proceed, I will probably go buy a card reader and try and get the right PCIMG file back on and re-flash it. But if anyone has another method, I am all ears. Here is my information.
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.36.00.04.02
MAR 30 2010, 122:24:04
If nothing else I will try the SD Card and put on the IMG I had used originally, but would like to save a few bucks if I can.
Sorry if there is an answer posted already for this question. I did about 6 hours of research and looked through all the Wiki guides and came up with nothing.
Well, I bought a card reader and put the correct image back on the card which after a re-flash fixed it.
Thanks.

[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.

HTC Desire -- Stuck at HBOOT after RUU

Hopefully I'm just being blind here -- and I have tried a number of guides to fix this -- but I'm pretty stuck.
Couple of days ago the volume down button started playing up, then the menu and search keys stopped working. At the time I had rooted the phone with unrevoked and installed CM7.3 (iirc), and taken the S-OFF with Alpharev 1.8. I figured it was probably a software issue and for some reason decided to go back to run an RUU (rather than just running a different ROM, don't really know why on earth I did that). Kind of having a feeling that I was very dense and ran the wrong RUU, as now the phone is simply stuck at HBOOT.
When I say stuck, I mean as soon as I turn on the phone it goes directly into the stock HBOOT (FASTBOOT -- RECOVERY -- CLEAR STORAGE -- SIMLOCK) yet NONE of the buttons work (so I cannot navigate it at all). Perhaps it is actually a hardware issue, which would make sense as it boots straight into HBOOT, no HTC screen or anything. When it runs the SD check it comes back with wrong / image missing in all the checks.
Tried running ADB, couldn't find the phone. Other RUU's return error 170 as though they can't find the phone. Phone does register "HBOOT USB PLUG" when plugged in though, and my Windows 7 machine does recognise it, but as there's a new RUU on there USB debugging is not enabled and I cannot access the SD card through the phone.
The full info on the HBOOT screen is --
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
Any help would be much appreciated... Later on today I'll pick up a card reader, figure my only option now is to try and get through to it that way?
Hmmmm!
I'm not sure but it actually could sound like a hardware issue. You have the STOCK HBOOT and then ran the RUU for the HTC Desire? If u did so I cant see it as a software brick. PM me if you need some more help. I had a Desire for some month ago that i bricked A LOT more than yours, and i got it fixed (by myself... took some nights thought :/
Yeah I thought that as well, but before I flashed the RUU, although the phone was powering directly into HBOOT, I could use the buttons to navigate the menu. Now, I simply can't.
I should maybe add that when it checks the SD it returns with wrong / missing image (can't remember the exact wording -- pops up then goes pretty quickly).
Also this afternoon I opened up the desire and checked and reseated the buttons, all seem to be working as normal. Seeing as it's stuck at HBOOT, I think I'll just need to buy a new SD card and put whatever the image it's looking for is on it?
Edit: I was thinking that reformatting the SD card (through a PC USB reader) as FAT32, then placing the PB99IMG.zip from the latest 2.3 HTC WWE RUU might work? I can't see any reason why not -- think the Desire is unbranded so no goldcard required.
Edit2: Still waiting on a new adapter, but was wondering why the RUU failed -- the file was RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed.exe from shipped-roms. Don't see any reason why flashing it would have ended up leaving me in this position -- even if it was a hardware issue underlying it.
Sorry to double post...
Tried putting the PB99img from the RUU (and tried the 2.3 update PB99img) to no avail on both the SD card that I'd been using recently and the one that had originally come with the phone -- no luck; once HBOOT detects the img and runs through it, it gets stuck at the "parsing... [1] [2] [3]" etc page.
Any help would be massively appreciated, would be appalled if I have managed to brick this in my enthusiasm for fixing a volume button problem -.-
Already checked bortak's troubleshooting guide?
Yep and anything else I could find really. Starting to think this little droid is doomed.

HTC One M8 upgrade failed

I have a problem. I have a tendency to destroy phones, which is why the last 2 phones I owned has been HTC M8. They are rugged enough for me not to destroy them.
However, 10 months ago the first one had problems with the battery, so I replaced the phone because it was cheaper than replacing the battery. The second one have worked fine, but lately the USB plug is worn out, so charging is becoming a problem.
This leads me to my problem. I (ofcause) bought a 3d one. This one was hardly used, and was 1 owner phone.
As it turns out, the previous owner had made 1 mistake. He had done the factory reset, but half way through it, it ran out of power. This means that booting it up, causes loads of errors: Gapps errors, Sense Home errors, Hangout errors and finally Google play service errors.
Now, I have worked with computers from 1991-2016 (including IT support for all the major companies) so I do know how to fix something like this - if this was windows . But since this is Android, I am a complete noob . I am just too stubborn to give up on this phone just because it has corrupt software . But this is a LOT more difficult than working with Windows I think Prior to this I have only rooted 1 phone, and that was in 2013 . I have been working on this the last 2 days .
So here is what I have managed to do so far:
I have unlocked bootloader through the HTC website and I can access the recovery program. Through that I have wiped cache, Ramdump, and done something like 15+ factory reset.
Through this I am able to get into the phone - sort of. I get a box asking if I want to send an Error rapport - and when I do that, I can get into the settings on the phone.
Through the settings, I have enabled developers options + enabled Debug, and disabled Fastboot.
I also tried to cleared cache on Gapps, google play services and Hangout - but that didnt help - so I disabled those things.
Now I can sort of use the phone. I cant update it, and it doesnt find the sim card. It does however connect find through wifi.
After all of that, I have been able to connect the phone to the computer though USB. I get both computer and phone to accept the connection (type in the code) and I can transfer files to the phone. It also works in HTC Sync software.
In Bootloader I can also get it to find FASTBOOT USB, so it does find something.
However, next step was that I had to root the phone using ADB and TWRP but I cant seem to get that connection working. Both programs finds no devices. So I am not able to actually root the phone.
I also tried RUU but had the same problem. Cant seem to get that connection working, so I can flash/root the phone.
Because of this, I tried to install upgraded versions of Android using an SD card. I can get the phone to read those zip files, but it always ends up with an: "Footer error" or "Verification failed".
I even tried the official HTC Android Marshmallow that you can download, but that came with the same verification error.
The only version that got close was an older version of the software on it. That one came up and said it was an older one, and aborted the installation because of that.
I have tried:
crDroidAndroid-6.0.1-20160826-m8
crDroidAndroid-7.1.2-20180117-m8-v3.8.5
crDroidAndroid-9.0-20190315-m8-v5.2
himauhl-3.10.84-perf-g09631a4
m8qlul-3.10.49-perf-g6f6e344
OTA507
So what am I asking help with? The simple answer is that I wanna install new android software - similar to reinstalling windows. The old phone had Android 5, and the first one Android 6. If I can upgrade to something newer, that would be a bonus, but I am good with "just" getting the phone to work .
So how do I get the phone to accept that zipfile for the android software? How do I get passed that Footer Error/verification error?
Oh and please explain the steps I need to take, for complete a complete noob . Simple steps will be greatly appreciated
*** Software status: Official***
** UNLOCKED ***
** Security Warning ***
M8_UL PVT SHIP S-ON
HBOOT- 3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v 51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
eMMC-boot 2048MB
Dec 17 2015,14:15:48.0
I have done some more testing.
aicp_m8_o-13.1-UNOFFICIAL-20181002
cm-12.1-20150509-UNOFFICIAL-ace
crDroidAndroid-6.0.1-20160826-m8
crDroidAndroid-7.1.2-20180117-m8-v3.8.5
crDroidAndroid-8.1-20180809-m8-v4.6
crDroidAndroid-8.1-20181018-m8-v4.7
crDroidAndroid-9.0-20190315-m8-v5.2
himauhl-3.10.84-perf-g09631a4
m8qlul-3.10.49-perf-g6f6e344
OTA507
And finally the one that gave the best result:
OTA_HIMA_UHL_L51_SENSE70_MR_HTC_Europe_2.10.401.1-1.40.401.8_release_444119
This one came up with a Sideload package error - Status 255. From what I can tell by google, that is an error caused by CM or TWRP. Its suppose to be corrected by deleting some files in TWRP but I dont have TWRP.
So how do I solve this new problem?

Categories

Resources