Hello there,
I just installed MIUI_Au ICS on my rooted HTC Desire, and am now trying to get rid of my S-On.
My OS is Ubuntu 11.10, 64bits.
My phone details are as follow:
- Bravo PVT1 Ship S-On
- Hboot 0.80.0000
- MicroP-031d
- Radio 5.17.05.23
I tried running Revolutionnary, but it does not support Hboot 0.80 ; I tried to go back to Unrevoked, but it does not work properly on a 64bits OS.
What should I do?
Are all hboot seen on Alpharev S-Off'd, even the one labelled "Stock"?
Bonus question: is my radio up-to-date?
Radio is ok, you need to run alpharev not unrevoked to get s-off, see instructions on alpharev.nl
Sent from my HTC Desire using XDA Premium App
Thanks. So nandroid backup, install the "Stock hboot" from Alpharev with fastboot, wipe, nandroid restore → should be good?
Miles Prower said:
Thanks. So nandroid backup, install the "Stock hboot" from Alpharev with fastboot, wipe, nandroid restore → should be good?
Click to expand...
Click to collapse
Nandroid yes then you need to run alpharev.iso to unlock nand (get rid of protection) then you will be able to flash custom hboot, recovery etc... Without it all flashing will fail... Read instruction about s-off on custom roms first...
Edit: best thing will be to revert to rooted stock Rom then run alpharev utility
Sent from my HTC Desire using XDA Premium App
Do I really need the Linux LiveCD? I'm already running Linux after all.
Well, I'm worried.
I did a nandroid backup first, then fired up unetbootin to make a bootable Alpharev USB drive and reboot my computer.
Stages 1 and 2 went supposedly fine, but my computer is now sitting there doing absolutely nothing on Stage 3.
During Stages 1 and 2, the terminal spit a few worrying messages but the process still went on automatically, without me taking action; those messages are :
- Unable to enumerate USB device on port 1
- USB 2-1: device descriptor read/64, error -71
Stage 3 currently looks like this:
Step 3 of 3 is starting. During this step, you will receive instructions and progress on-screen. This is normal. DO NOT TURN OFF YOUR PHONE DURING THIS STEP, HBOOT is beeing flashed during this stage, and turning it off WILL *BRICK* your phone!
Waiting for flashing to complete...
- USB 2-1: device descriptor read/64, error -71
- USB 2-1: device descriptor read/64, error -71
- USB 2-1: device descriptor read/64, error -71
- USB 2-1: device descriptor read/64, error -71
- USB 2-1: device descriptor read/64, error -71
- USB 2-1: device descriptor read/64, error -71
- Unable to enumerate USB device on port 1
Phone is stuck on this screen:
AlphaRev SPLBOOT version 2.0
----------------------------------
Normal NAND detected. Non-PVT4.
It has been about 15 minutes and nothing is happening. Any advice? Think I can power everything off safely (it seems to me the Stage 3 process did not start at all, but I could be mistaken), or anything else to do?
Did you go to rooted stock rom as I told in previous post?
Sent from my HTC Desire using XDA Premium App
I'm afraid not. The rom is still MIUI Au ICS, rooted.
I'm getting "device not accepting address XX, error -71" where XX is a number ranging from 55 to 90 now.
According to http://paulphilippov.com/articles/how_to_fix_device_not_accepting_address_error it seems to be some kind of hardware failure / power failure on the PC side.
Any script? Like data2sd or data2whatever?
Sent from my HTC Desire using XDA Premium App
I used to have A2SD+ on a previous MIUI install (based on Gingerbread), but not with this rom.
However, it seems there's some kind of unified mass storage space since the "internal unused space" seen by the device was of approx 700Mo (I do have a 1Gb Ext3 secondary partition on the card). I did not manually install any kind of script myself.
____
Found this:
http://www.miui-au.com/faq/a2sd/
"MIUI-Au is built around A2SD+ and you Should have an ext3 partiton on your SD Card before installing MIUI-Au.
MIUI China, and many other ROM chefs, use Darktremor A2SD (we’ll call it DT-A2SD). DT is stable, reliable and very full featured with a command line interface that can be used to change many settings. In early 2011 DT stopped moving the Dalvik cache to the SD Card automatically and it had to be done using the command line interface (a2sd cachesd command). We at MIU-Au were not happy with this and some other aspects of DT so we built our own A2SD, which we call PC-A2SD. Features of PC-A2SD are: Invisible, automatic, no command line interface and nothing for the user to do. Automatically puts Dalvik cache on SD Card. Automatically handles slow to mount SD Cards and will also allow the ROM to run without an SD card. In real world use we believe it is no slower than DT, and provides 40Mb – 80Mb more internal phone storage by moving the Dalvik cache out of the phone and onto the SD Card.
If you are using MIUI-Au and have your SD card partitioned correctly with an ext3 partition, A2SD+ is Invisible and Automatic. You do not have to do anything to make it work."
If it DOES fake the NAND on the SD card, switching off the phone and rebooting WITHOUT the µSD card might allow me to still access my current Recovery (Clockmodwork)? This seems quite like playing russian roulette to me.
Thanks to Zanzibar on #alpharev for poiting out this FAQ : http://alpharev.nl/instructions.txt
"No output other than 'Normal/New NAND detected.' -> Nothing was flashed.
- Pull the battery, there's no risk."
I just did, and everything went well. Restoring my Nandroid backup now from the Clockmodwork Recovery.
I'll flash a stock rooted HTC rom and try again properly.
Thank you for the help and support.
Thanks. I'm at work on the phone, my resources are limited, goodluck with stock rom
Sent from my HTC Desire using XDA Premium App
Hello Miles,
I've got exactly the same device than you with same hboot version, and I'm currently trying to find a way to s-off it.
I did a lot of research on the web but I can't seem to figure out how I can actually get rid of the s-on.
Did you manage to eventually s-off your desire, and if yes, can you tell me how ?
Thank you !
bightf said:
Hello Miles,
I've got exactly the same device than you with same hboot version, and I'm currently trying to find a way to s-off it.
I did a lot of research on the web but I can't seem to figure out how I can actually get rid of the s-on.
Did you manage to eventually s-off your desire, and if yes, can you tell me how ?
Thank you !
Click to expand...
Click to collapse
alpharev.nl
Is it really compatible with HBOOT 0.80.0000 ? I thought it was not. Maybe I got confused with the Revolutionary method (aka Alpharev X).
I'll give it a try, thanks !
Yes, I was 80.
Sent from my HTC Desire using Tapatalk
Ok,
I've finally found a way to s-off my desire !
All I had to do before the whole process was to flash with an official HTC RUU (2.29.405.4), so it updated the hboot from 0.80.0000 to 0.93.0001.
After that, I could use revolutionary 0.4pre4 which support this hboot version and let it do the magic.
Installed 4ext touch recovery, Runnymede AIO, and everything's now just fine !
All you needed was rooted stock custom rom and alpharev.
Yes I know and I tried that, but for some reason it didn't work and gave me an "unary operator expected" error during the final step of the process.
I've googled that error and found different causes and solutions, but I didn't want to spend too much time on it, so I took the "easy way".
Anyway, now it works and I'm very happy
fair enough
Related
Hi trusty XDA-peoples... I've been on the modaco forums the past 12 hours and have had no luck. I have a bung Desire after following the Apps2SD update (the goldcare and root went 100% fine). I used the old method and have just tried Paul's new method. The result is the same (I've tried it in 3 different Linux distros, it still says "device not found"). I'm only getting this 'device not found' AFTER I applied the A2SD zip update on the modaco forum (first page on the root instructs).
http://i40.tinypic.com/6t22w6.jpg
If anyone can help, that'd be much appreciated. The phone was on the red-triangle when this error occurs, and I've also tried it on the "different screens" (which doesn't make sense but I tried them anyway - on hboot screen and fastload screen) - still "device not found"...
Please Help.
Thanks guys.
You try starting over from the very beginning?
And, I think you might be right about A2SD breaking root.
eViL D: said:
You try starting over from the very beginning?
And, I think you might be right about A2SD breaking root.
Click to expand...
Click to collapse
I have gone all the way back. I have no problems flashing TestRUU (the "new method" also works) but when ADB tries to load the Recovery on to my phone, "device not found" (yep I'm SU all my commands so I don't think it's a permissions problem). It just won't see my phone in the mode where the red-triangle is up. It's just dead.
Anyone think replacing TestRUU with Rootedupdate.zip and then flashing that way will work? Or will that completely brick it?
Ok, was gonna suggest
./adb-linux kill-server
sudo ./adb-linux start-server
sudo ./recovery-linux.sh
try a different port?
eViL D: said:
Ok, was gonna suggest
./adb-linux kill-server
sudo ./adb-linux start-server
sudo ./recovery-linux.sh
try a different port?
Click to expand...
Click to collapse
Tried 3 different machines, 2 Ubuntu builds and Paul's TinyCore new-method. USB ports appear to work OK (since it flashes TestRUU fine on the USB cable/ports!)
I've tried testing all the adb settings (adb reboot/root/usb etc.) but all come up "device not found". Grr. It appears Apps2SD broke the Recovery mode on my Desire? How is that even possible?
Ok, so what is the last thing you have done that worked?
almost crapped my pants....
Got this error just now.
error: device not found
error: device not found
[email protected]:~/android/tools/pushfiles$ error: device not found
unplugged the usb and plugged back in and reran the command and it worked.
are you using a hub?
eViL D: said:
Ok, so what is the last thing you have done that worked?
Click to expand...
Click to collapse
Last night, ROM updated with Paul's Root. No problems. Then I ran through the recovery-linux.sh and got green recovery screen on desire. Installed A2SD.zip from my 4gb Goldcard. Reboot. Fine.
Then turn off phone, removed 4gb goldcard and inserted 8gb normal card. Rebooted with recovery-linux.sh and got recovery screen on Desire. Partitioned 8gb card into 512mb and 7.5gb partitions. converted from ext2 -> ext3, reboot.
That's where it's broken. Boot- Loop at "quietly brilliant". Rebooted a few more times, and same. Removed 8gb and inserted 4gb goldcard. Same looping problem.
Then tried to reflash Pauls' rooted ROM - but can't get into the recovery screen anymore. And this was the first time I saw in Terminal "device not found". Ever since then it's been 'device not found'
Tried to reinstall TestRUU from windows, failed. Couldn't see the phone.
After a few hours, did a clear-storage from bootloader., this time (i think i had 8gb card in) the phone loaded with no looping. But the ROM is broken. Cannot detect SIM and cannot detect SD Cards (goldcard is no go either). Only thing that works is WiFi at the moment.
Downloaded Pauls' r3 new method and reflashed. First process worked fine, everything flashed (i got a strange error that I posted on modaco about: "FAILURE hboot 90 pre-release? please flush <something else>". The error was on r2 and Paul looked into and updated something and posted r3. I flashed via r3 and still got the same error! But some other system files continued to flash (not sure what Paul fixed, but he did something). So I thought it was all good. step1.sh seem to go fine, but when i get to step2.sh - BAM! "device not found". Back to square one.
eViL D: said:
almost crapped my pants....
Got this error just now.
error: device not found
error: device not found
[email protected]:~/android/tools/pushfiles$ error: device not found
unplugged the usb and plugged back in and reran the command and it worked.
are you using a hub?
Click to expand...
Click to collapse
no hub, straight into usb port (even at the back of usb motherboard connection)
i'll try again
nothing :|
united we stand...
Hi biliskner!
Fear not - I'm sure we'll get your phone sorted - I have *exactly* the same problem, and it went wrong at the same place... usb works fine, but adb refuses to work, regardless what PC I use. Aaand, the same problems with sim card/sd card in the phone - I'm so glad (sorry!) that I've found someone else with the same issue!
Spent quite a long time in IRC with Paul and SGT somebody from MoDaCo trying a few things - they're both confident we'll get it fixed, just not quite sure how yet!
Seb
Any way you can test the usb/cable with something else?
sebm said:
Hi biliskner!
Fear not - I'm sure we'll get your phone sorted - I have *exactly* the same problem, and it went wrong at the same place... usb works fine, but adb refuses to work, regardless what PC I use. Aaand, the same problems with sim card/sd card in the phone - I'm so glad (sorry!) that I've found someone else with the same issue!
Spent quite a long time in IRC with Paul and SGT somebody from MoDaCo trying a few things - they're both confident we'll get it fixed, just not quite sure how yet!
Seb
Click to expand...
Click to collapse
Cool - there's someone else in the modaco forum, kingoffail, also having the exact same problem. We can't get into recovery mode. And the current ROM on it is totally useless :| (is the current ROM on it like a pre-build / testing ROM? No SD detect or SIM detect? Sounds like a bloody iPad!). I don't want an HTC (or any) iPad -.-
eViL D: said:
Any way you can test the usb/cable with something else?
Click to expand...
Click to collapse
I just reloaded it on my laptop with Ubuntu (the SDK tools -> recovery-linux.sh method). Same deal as last night. Tried 3 USB ports and different usb cable (not the original HTC cable). And ... "device not found".
I'm just about to try and flash a generic rom to it now, see if that fixes it.
also eViL D: yes - I'm confident the usb cables works absolutely fine as everything else works; just adb doesn't.
Seb
Well, you could fastboot the system image and boot image from the test ruu.
That sounds promising - how do you flash the /system bit?
sebm said:
I'm just about to try and flash a generic rom to it now, see if that fixes it.
also eViL D: yes - I'm confident the usb cables works absolutely fine as everything else works; just adb doesn't.
Seb
Click to expand...
Click to collapse
I understand. Just trying to get low level things first.
If I delete Paul's "TestRUU" and rename his "rootupdate.zip" to "TestRUU" and hack it that way, you think the step1.sh will flash it OK? (makes the step1.sh think it's flashing TestRUU but in fact it is flashing the rootupdated.zip rom which the might solve the problem?)
I don't understand why Paul has flashed a TestRUU before loading Recovery and then flash rootupdate.zip from the SDCard - why not just flash rootupdate.zip from Linux at step 1 and bypass TestRUU and trying to push Recovery from Linux into Desire's SDCard? Is that where the exploit is?
OK, we have some progress - I'm in the process of flashing RUU-MoDaCo-Bravo-1.15.405.4-release (I extract the zip from that archive, and am flashing with fastboot now) - something is happening at least!
Seb
Hi, Apologies if this is in the wrong section.
I hope someone can help. I am trying to root my HTC Desire using the latest Unrevoked software.
I have followed all instructions, (removed htc sync, installed the usb driver). I have run the software and it did it's thing and says root is done. I can see the Superuser app in my apps. I installed titanium backup which requested Root access fine. I granted it, but titanium backup came back saying it couldn't get root access.
I have run the unrevoked software a few times and it doesn't seem to fail, or throw any errors at all.
This is the process:
Plug phone into computer (Windows 7 ultimate).
Run unrevoked sw.
It pushes the recovery image.
Reboots a few times.
Says it is getting root.
Says "Triumph" etc. Finished with Done.
Final reboot goes to normal phone fully booted.
Still cant get root.
If I boot into the boot menu I see the following information:
Bravo PVT1 SHIP S-ON
HBOOT 0.93.0001
Microp 0.31d
Touch Panel SYNT0101
Radio 5.09.05.30_2
If I select recovery menu I can see the Clockworkmod recovery menu is displayed.
I have an unbranded Desire running the HTC OTA 2.2 Froyo update.
Android Version 2.2
Baseband: 32.44.00.32U_5.09.05.30_2
Build number: 2.10.405.2 CL226611 Release keys
SW number: 2.10.405.2
Am I missing a step somewhere or should it just work, one button press?
Any help would be appreciated.
Thanks.
I did mine on Windows 7 ultimate x86 so it is possible on that OS
¿Have you select "Charge Only" and "Remember this" when you have plugged the USB cable?
¿Are you sure your phone had USB Debugging turned on by having gone to Menu>>Settings>>Applications>>Development and checking USB debugging?
pr0orz1337 said:
Have you set "USB debug on" and "only charge" mode?
Click to expand...
Click to collapse
Yep. I have followed all the instructions. The process runs fine it just doesn't seem to work, or im doing something wrong. Is there anything I need to do in the recovery menu?
I was unable to root my phone using Windows 7 64bit. When I used a computer with a 32bit operating system, I had No problems.
Sent from my HTC Desire using XDA App
I installed titanium backup which requested Root access fine. I granted it, but titanium backup came back saying it couldn't get root access.
Click to expand...
Click to collapse
That's a bug in Titanium, i had it 2 or 3 times, too.
Check that "Apps from other sources" thing (don't know the exact name in the english rom), restart your phone and run titanium again.
Xeno87 said:
That's a bug in Titanium, i had it 2 or 3 times, too.
Check that "Apps from other sources" thing (don't know the exact name in the english rom), restart your phone and run titanium again.
Click to expand...
Click to collapse
Well I've managed to get it working. I had to install the busy box application. Not sure what it does but titanium backup now works.
Thank you for your help.
Hi, I have searched and found a couple of posts but none of them really shows the same problem I have - so sorry if this is obsolete or maybe I missed something.
[Info Desire]
Screen= AMOLED
HBOOT= 0.93.0001
Radio=5.17.05.23
SDCard 32 gb class 2 1 gig EXT3
The thing is here is the full story what happened.
I had an old Leeroid Rom on my Desire and I was quite happy with it - but recently the synchronization with my accounts like facebook, google calendar, gmail did not work anymore - so I thought ok Let's get a new Rom as my Leeroid was about 6 months old.
So I looked around and found to my surprise Sense 3.0 Roms - i thought great and tried them.
First I tried [ROM] Aurora v03 [Sense 3.0|Android 2.3.5|Stock|CM7/r2|Smooth & stable][Sep23] (Problem I had but didn't know I had no EXT4) So I had little to no Space for apps
Then I tried [ROM][Cool3D Sense 3.0][19 Sep]Cool3D AceS v3 |Android 2.3.5|FAST|STABLE|STOCK|CM7/r2
I also flashed the Latest Radio (see above) but now the Problem really started: The phone got slow and laggy responded slow or not at all rebooted...
So I thought ok I will go back to a Rom I know - the newest Leeroid.
When trying to flash Leeroid (I wiped Data and ext3) I noticed that I took rater long to get into the recovery menu - actually i just selected recovery and then went to bed - at the next morning the recovery menu had been loaded. so i Flashed the leeroid rom. Rebooted and apart from the htc logo nothing happened (I waited for over 2 hours)
Now if I try to load up the recovery menu i get the following:
sd checking...
loading...[PB99DIAG.zip]
Several Minutes later
No Image!
loading...[PB99DIAG.nbh]
about 10 minutes later...
No Image or wrong Image!
Loading...[PB99IMG.zip]
anpother 10 minutes later...
No Image!
Loading...[PB99IMG.nbh]
Then it seems it goes back to the menu (i don't know it is unresponsive but it might just load the recovery menu i guess)
Another thing i want to add is - I tried to S-off my Desire with the Noob Method described here
Everything went smoothly until step three when the computer awaits the reboot of the desire ("follow the steps on the screen of the desire") the computer gave me like 4 errors but the desire booted up (but no directions to do anything)
I also resized the EXT3 partition with easus partition manager (that might have been a problem?)
Now here are my questions:
Can I somehow repair my desire or is it a goner?
If I can repair it - how?
I did read about the whole Goldcard thing here but keep in mind that I can not boot my desire...and as it looks right now not the recovery mode either...
I humbly ask for your assistance - and thank you for your time.
Hmmm I would try a few things
1) Remove SD card, any better?
2) I'd probably skip any attempts to repair and take straight back to stock with RUU (you need a gold card if you havent got the correct RUU starting with 2.x) you can make a goldxcard in any old card reader usually.
Well I removed the microSD and apparently this changes things... It is booting to a screen which says android... so far...
however I will create a goldcard now....
Well I tried my 2 Gb microSD on2 Computers with 4 different cardreaders could not get the CID... now i am formatting my 32gb - maybe it'll work with that one...
Desire can boot as it or not ?
The desire "kind of" boots if i switch it on (without the mircosd) i first get the htc logo and then a blinking android writing - i left it sitting on my table to continue booting but when i returned the battery drained.. this is all i can say...
Here is a video of what it does, so you get a better idea (you can see that even though i tried to get into bootloader it does not go to bootloader now...) Video
EDIT:
I can get into bootloader and recovery - created a goldcard but can not flash the RUU... Error 170 says my device is not connected even though it is and activated fastboot...
I thought I got it finally so far to Flash the RUU but then i get the following error:
ERROR [131]: USER-ID-ERROR
Gold card is not working.
Do you know what your original software version was? What carrier are you? Which ruu are you using now?
Just to make sure I am supposed to post the CID on the website not the reversed one...? just so i don't make a mistake...
I am terribly sorry but I do not know what my original software version was. My Carrier is O2 (i bought it in April/May last year when the Desire was available in Germany)
Would a Nand Backup help? (If so would it be saved on the sd card and where?) Maybe I have one...
The CID you get is reversed I believe
I get 2... one reversed and one so to say normal...
I think you use the reversed one. Try both
Thx I will try again
Ok so apparently you do have to use the reversed CID... now what... reroot? then trying s-off again then gparted then flash new rom?
So now you RUU'd?
If so maybe run it for a little while (few hours maybe) do reboots, check performance, install some apps etc etc. Then maybe yes, re-root.
Yes i RUU'd Thanks for your help
I will have it running for a while and do a couple of reboots, updates of apps maybe install an app or two etc but may I ask why i should not go ahead with rooting right away?
Hello,
Firstly I rooted my HTC wildfire 2.2.1 to cyanogenmod7.Then I tried to unroot and install stock rom RUU_Buzz_hTC_Asia_TW_1.18.709.2_Radio_13.45.55.24_3.35.15.31_release_132351_signed
As I Powered on phone,it booted normally but my phone's touchscreen was frozen. I even can't unlock the system's lock pattern!! Also If i get calls on my phone i even can't drag to answer the call!! I searched for solution but after bothering google i found that i must enabled the USB DEBUGGING to reinstall the stock rom....I even can't answer the call due to touchscreen got frozen,how i enable the USB DEBUGGIN........I hope there is solution for it.....please help to sort out this kinda problem!!
Waiting for better solution
When i Hboot i found this on my phone
buzz pvt ship s-off
hboot-6.01.1002
mircop-0622
touch panel-syneky_01
radio-3.35.15.31
Boot into the recovery.
Go into Mounts and storage
Select Mount USB storage
Copy over one of the "safe" RUU .zip files.
http://forum.xda-developers.com/showthread.php?t=854117
Flash it.
The touchscreen should work now.
On some RUUs the touchscreen doesn't work.
OR
Reflash CM7
Download a different RUU (in .exe format, like the one you flashed)
Try installing that one.
nejc121 said:
Boot into the recovery.
Go into Mounts and storage
Select Mount USB storage
Copy over one of the "safe" RUU .zip files.
http://forum.xda-developers.com/showthread.php?t=854117
Flash it.
The touchscreen should work now.
On some RUUs the touchscreen doesn't work.
OR
Reflash CM7
Download a different RUU (in .exe format, like the one you flashed)
Try installing that one.
Click to expand...
Click to collapse
hi
I got the problem in my htc wildifre buzz while rooting!!
Firstly I rooted Htc wildfire buzz 2.2.1 to CM7!! But i din't like the look of CM7 then I tried to revert back to my previous version of phone so i tried to install RUU_Buzz_hTC_Asia_TW_1.18.709.2_C_Radio_13.45.55.24_3.35.15.31_release_141439_signed on the phone!! However I installed it but as I powered on the phone then it starts normally till "'HTC"' appear after that i can't unlock the phone and can't enter into phone!! In other word touchscreen got frozen so i can't unlock!! If i get calls i can't even answer using any method!!
Then i bothered the google to search for solution then i get solution that i must enabled usb debugging!! I even can't unlock the phone and enter how could i enabled usb debugging!!
Then i found solution in xda developers
http://forum.xda-developers.com/showthread.php?t=1468840
http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
I read the methods and perform same things in phone as mentioned in above thread but i couldn't succeed!! Whenever I tried to update i found
Finding update package
Openinng update package
Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
So whether my phone is bricked or not can anyone tell me please!! How to fix these problem!! As i entered into HBOOT mode my phone shows following info
buzz pvt ship s-off
hboot-6.01.1002
mircop-0622
touch panel-syneky_01
radio-3.35.15.31
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