Related
Hi - posted this elsewhere but really need help.
First off - I think I made a serious of noob mistakes that have resulted in my problem. I desperately want to be able to recover my phone, so please be nice.
I have a rooted incredible with the leaked 2.05 OTA radio update and have been running Cyanogenmod 6 rc3 and then 6.0. This morning I tried updating to 6.0.1 but for some reason it didn't update. It kept rebooting to 6.0 and telling me I needed to update again.
I decided to just unroot the phone and go back to stock to take advantage of the stock 2.2 update. I put the earlier 2.1 stock file on my SD card and pressed power and volume down to boot into recovery. The phone then started to update to the older version, but ultimately wouldn't do it, telling me this was an older version.
I realized this was because of the leaked radio update I had. Until I can fix that, I want to just reboot back into CM6, but I can't. The only way to turn the phone on and off is to pull the battery, but the phone won't boot, it just goes into recovery -- and I can't use the volume or power buttons at all to select menu items. So I have to pull the battery again...
So I'm stuck there. Any ideas how to at least fix so I can use CM6 again?
I should also mention that I recently replaced the digitizer, which was cracked, and almost everything works, except now I can't use the trackball
lvjy said:
Hi - posted this elsewhere but really need help.
First off - I think I made a serious of noob mistakes that have resulted in my problem. I desperately want to be able to recover my phone, so please be nice.
I have a rooted incredible with the leaked 2.05 OTA radio update and have been running Cyanogenmod 6 rc3 and then 6.0. This morning I tried updating to 6.0.1 but for some reason it didn't update. It kept rebooting to 6.0 and telling me I needed to update again.
I decided to just unroot the phone and go back to stock to take advantage of the stock 2.2 update. I put the earlier 2.1 stock file on my SD card and pressed power and volume down to boot into recovery. The phone then started to update to the older version, but ultimately wouldn't do it, telling me this was an older version.
I realized this was because of the leaked radio update I had. Until I can fix that, I want to just reboot back into CM6, but I can't. The only way to turn the phone on and off is to pull the battery, but the phone won't boot, it just goes into recovery -- and I can't use the volume or power buttons at all to select menu items. So I have to pull the battery again...
So I'm stuck there. Any ideas how to at least fix so I can use CM6 again?
I should also mention that I recently replaced the digitizer, which was cracked, and almost everything works, except now I can't use the trackball
Click to expand...
Click to collapse
Is soff?
Sent from my Incredible using XDA App
tcberg2010 said:
Is soff?
If it is u could run the new ruin from hboot. This will give u stock 2.2 and stock recovery. But you'll be able to flash clockworkmod again.
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
tcberg2010 said:
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Nope, s-on.
Is there a way to make it s-off in this state? I'd be happy to just get it into stock 2.2. Thanks.
I'm pretty new to this rooting for Android, I recently got my Incredible.. I used unrevoked to root my incredible. I did it normally like USB debugging and all that. Soon as it started to root it, the phone rebooted itself like it was supposed too, got to the HTC Incredible screen (the first screen on the boot up) and black screen and white bars on the sides. Now I got this phone like November 27th.. and I'm pretty postive my screen is an SLCD? And that seems to be what the problem is with the black screen white bars.. Thing is, of course the black screen white bars stayed there, so I pulled the battery out and put it pack in. It loaded up normally and it seemed to be rooted fine. It had the Superuser (ninja). And everything was normal. I downloaded ROM Manager and then downloaded the Flash ClockWorkMod Recovery, and then I clicked on Cynagen Mod and went down to Google apps. Downloaded it, installed it, then it asked to reboot. ALL OF WHAT I JUST DID, (followed from The Start to Finish Guide to Rooting Your Android Phone, I con't post links yet) .. So as it rebooted it got the HTC Incredible screen (the first screen on the boot up) and it did the black screen white bars. I removed the battery either twice or three times.. And still nothing, I THEN FOLLWED THIS Incredibleforum dot com (I rooted and now I only see a black screen with white bars in recovery.) and went to the Hboot menu and went down to recovery and selected it. It rebooted and still black screen white bars at the HTC Incredible screen. I then tried his other method and went to download that file and went to unrevoked and did the custom recovery and put recovery in the file and plugged my phone in. ( He actually said to like check USB debugging, which I couldnt actually do because I couldnt get to my menu..) So then after plugging it in and showing the orange light for charging. It did nothing other then charge. I turned it on ( I'm pretty sure, it might have turned on by itself) and it worked. It got the menu screen. And everything was the same. ROM Manager was still there, same with superuser. And the 3 game apps that I downloaded before I rebooted for Google Apps. I haven't found Google Apps, I'm not really sure where Google Apps would be anyways.. But what I'm getting at here is, What actually happened????? Why those white bars?? And will this happen everytime I have to reboot? If someone could just give me their best answer or an explanation It would really help. I'm new to this stuff.. But I'm getting nervous with this black screen thing white bars.. and I'm debating wether to just unroot..(how easy is unrooting?).. But my phone is fine now, I haven't tried like downloading anything but everything seems to be working fine.. Where could I find Google Apps? And which ROM? Cynagen Mod Or Bugless Beast.. Please Help
You have an slcd screen. Your recovery is for smiled. Use unrevocks recovery for slcd screens. As I have read you need that one for recovery to work properly. I don't have an slcd so I don't know to much about that end
Just cruise the forums there is tons of info out there.
Sent from CM Nightly 11-20 using Tapatalk.
I had similar issues, and poster above is correct... I was able to flash a modified clockwork recovery to get it working with slcd...but I'm halfway afraid to try any ROM Manager abilities due to the different recovery :>
Just flash the modified Clockwork- very simple and works perfectly. I have the zip if you want it.
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
mcolib8 said:
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
Click to expand...
Click to collapse
http://www.megaupload.com/?d=7O9ZPP2T
You don't need to uninstall anything from your phone obviously, but I'd uninstall any unrEVOKed stuff from your computer before you do the new version. Recovery is basically the tool that lets you modify the phone. You go there to do nandroid backups and restores, and to flash zips. Let me know if you need instructions on how to apply the fix.
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
mcolib8 said:
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
Click to expand...
Click to collapse
1. Mount your phone as disk drive (I'm assuming you know how to do that, if not, lemme know)
2. Move the file to the root of your sd card (not in any folders) and make sure you don't re-name it at all.
3. Disconnect your phone, wait for the card to format, and then yank your battery.
4. Put the battery back in, hold Volume Down+Power.
5. You'll see your bootloader and it will find the file automatically, let it install it.
6. Once it's done, yank your battery again and repeat Step 4.
7. This time, choose not to install it, and instead choose Recovery- should load up Clockwork just fine. Easiest way to access Clockwork in the future is thru ROM Manager- there's an option to boot into recovery.
PS. might wanna check your clockwork version first thru ROM Manager- my version is 2.5.0.5 and I'm not sure if Koush has included the SLCD fix in any of the newer versions, so I'd make sure you have that version before doing this.
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Edit... responded too late. Thanks for the advice!
Sent from my ADR6300 using XDA App
ithuwakaga said:
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm guessing you didn't read to the end of the thread before you posted
iBowToAndroid said:
I'm guessing you didn't read to the end of the thread before you posted
Click to expand...
Click to collapse
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
ithuwakaga said:
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
iBowToAndroid said:
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
Click to expand...
Click to collapse
Thank you!
Sent from my ADR6300 using XDA App
Hiya,
Firstly, yes, I did a search. Here's my problem.
I used unrevoked and rooted my phone, so I could remove bloatware, tether etc. I then installed the hydra kernel to OC to 1.113 (stock volt), and this worked fine too. Couple weeks passed, everything's dandy, and today I decided to give Cyanogenmod 6.1 a try. So I get that up and running and decide that I like the Sense UI better, so I go into the ROM Manager app and tried to restore a backup that I made before installing the ROM. So the phone restarted, and then displayed the HTC Incredible logo and it stayed there.
I waited 30 minutes, pulled the battery, tried to boot. Same thing.
I held down vol down and went into HBOOT, and selected recovery. I get the black screen with vertical white lines on the sides. Waited thirty minutes, no change.
I then tried to reset factory settings through main HBOOT menu. Got the black screen with white stripes again.
So, it appears I bricked my phone. My theory is that the space on my SD card was too low and when I did the backup not all the information was saved, and when the phone tried to reset it pooped out, on account of the fact that the restore data was incomplete.
Thoughts? I do have the Best Buy warranty on this thing, so I'm wondering how that could offer some sort of solution (although I am pretty sure they will not like the fact that it has been rooted..). So in summary: Halp!!
Thanks yall.
IHateMayonnaise
Hater of Mayonnaise,
Have you ever been inside the recovery, working? I'm guessing no. The screen you described is an older clockwork recovery on an incompatible LCD screen. Try one of the newer recoveries. 2.5.1.2 should work work, as well as BAMod, and I believe Doug piston has one up. Rename the file to the proper PB31IMG.zip format and load from HBOOT. After that, look for your backup or install a new ROM.
You're not bricked till the phone doesn't turn on.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Hater of Mayonnaise,
Have you ever been inside the recovery, working? I'm guessing no. The screen you described is an older clockwork recovery on an incompatible LCD screen. Try one of the newer recoveries. 2.5.1.2 should work work, as well as BAMod, and I believe Doug piston has one up. Rename the file to the proper PB31IMG.zip format and load from HBOOT. After that, look for your backup or install a new ROM.
You're not bricked till the phone doesn't turn on.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yes I've been in it many times. When I first tried (while rooting my phone) I had the same thing happen, but I got the newer recovery or something (I forget what I did) and it went away. Why would this problem come back?
Maybe koush didn't fix the new one, so when you upgraded it broke. Go back to the older one that did work and all is dandy.
Sent from my ADR6300 using XDA App
yep it worked thanks!
lost android process
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Just fyi. Bricked is completely dead. Not stuck at a boot screen.
Sent from my Sprint Galaxy Tab
+1 on this bricked is thrown around far too much
shoman24v said:
Just fyi. Bricked is completely dead. Not stuck at a boot screen.
Sent from my Sprint Galaxy Tab
Click to expand...
Click to collapse
Sent from my Incredible using XDA App
uwintoday said:
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Click to expand...
Click to collapse
Which ROM?
Sent from my ADR6300 using XDA App
uwintoday said:
my phone gives the message android .process.acore has stopped unexpectedly.
cant get anything to work.
Click to expand...
Click to collapse
When does this happen? It started happening to me after I flashed data throttle zip on OMGB v6. only when I toggle 3G though.
Sent from my Htc Incredible using XDA App
android .process.acore
[ROM] SkyRaider Vanilla 3.0.1 RC3 ran this for a few days. did a back up and installed Incredible Gingerbread[Android 2.3 ran this for around twenty minutes. no back up done and tryed to install The Ultimate Droid 2.5.0. Thats when the problem started.
my phone has the andorid in the middle of the screen and says touch to continue. gives this error android .process.acore when android is touched. can only dial 911.
Since you didn't do a backup, make sure you do a complete wipe. If necessary, do a RUU and try again.
Sent from my ADR6300 using XDA App
android .process.acore
I dont see a complete wipe option.
I only have hboot options.
uwintoday said:
I dont see a complete wipe option.
I only have hboot options.
Click to expand...
Click to collapse
Factory reset, or something similar. Can't remember exactly. If not there, try fastboot.
Sent from my ADR6300 using Tapatalk
the ruu updates says loading PB31IMG.zip no image wrong image
Try going into the phone from safe mode. It might help you figure out if its the rom or an app on the rom.
Sent from my ADR6300 using Tapatalk
uwintoday said:
the ruu updates says loading PB31IMG.zip no image wrong image
Click to expand...
Click to collapse
Which means either your sd card is not FAT32, or you named it wrong.
Sent from my ADR6300 using Tapatalk
Or the file may have been corrupted during download. See if the md5 checksum matches that posted on the download site.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15
This is driving me crazy. No phone for days.
Ok i formated the sd card to fat32 via my computer sd slot. downloaded radio to computer from here
radios/2.15.00.07.28/ copy PB31IMG.zip to sd card via computer. with s off i did this , power off phone. Hold DOWN volume and press power. to accesses the hboot screen. hboot updateed PB31IMG.zip. yeah.
when i rebooted it goes into this endless loop of the red eye and the word droid.
Please advise.
Thanks
It isn't the radio you need to flash. An RUU is a stock rom as delivered by HTC. Try one of these.
http://shipped-roms.com/shipped/Incredible/
Sounds like you may need to reflash recovery too.
Edit: On second thought, you're recovery is probably ok. I was getting your problem confused with the original poster's problem.
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.11.15
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
melodicjunkie said:
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
Click to expand...
Click to collapse
thats internal feature of Hboot... it looks for pc10img.zip on sd card.... not at all an error....
and it can be useful in a situation where you mess up your recovery and rom ... you would be able to save your phone via that ....
also its used to go back to stock rom and unroot when needed
+1 for hispeedword. Best possible answer right there - that's exactly what's going on. Use ROM Manager to reboot straight to recovery from now on and it will skip HBOOT so you don't have to wait through all of that. CM and most other roms also allow that option when you hold down the power button.
Now, you said "shortly after rooting and flashing" - what exactly did you flash? You do know baconbits is ONLY meant to be used with the stock rom right? The exact one that you rooted and that came on your phone. If you flash ANY other rom - even a 'stock rooted rom' then you run into tons of errors when flashing baconbits.
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
TheMod'sPolice said:
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah I was being stupid, I didn't even know at the time when my phone messed up that it was from me flashing baconbits...until I did a back up, than flashed a different rom and reflashed baconbits, lmao..
so your saying to use baconbits if you rooted but didn't flash custom roms, than it works fine?
I'm thinking of switching to a sense rom, I don't even know why.. what are the pros/cons of sense? Thanks.
Assuming you've already answered your question up there, sense roms usually consume more battery life because of the plethora of constantly active widgets. However, if you're VERY social or buisiness, Id recommend it. The battery drain only cuts down on a few hours, depending on your usage, cpu governers and radio, and for that, you get a lot of functionality from the rom. Plus the new elegant blues ported theme for sense roms is just gorgeous. I also like the whole manual link to facebook in the contacts. Still hoping for a port for that xP try it out.
Sent from my HTC Vision using XDA Premium App
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Check k2buckleys post out HERE n report back.
hgelpke said:
This afternoon I received my replacement phone from Asurion and like and good Android user, I attempted to root it with the Universal root method that had worked really well on my old phone. For some reason, the root did not work and I attempted to restore the phone to stock using the PC36IMG for 3.70 to go along with the 2.10 hboot. Everything seemed to have gone fine until the phone booted up. After a few minutes, it froze and rebooted itself. On top of that, when it does boot it recognizes neither the sdcard nor usb.
I can get into the bootloader and seem to have access to the sdcard from there but any attempts I've made to adb into it have come up with a "no device found" error.
If I attempt to go into recovery, it reboots then goes to the screen with the evo with the red exclamation point on it.
I have no idea what could be the problem or even where to go to try to fix it. I've tried searching the forums but anything I can find about reboots usually has to do with custom roms and any solutions to the other problems seem to revolve around being to adb into the phone while its booted up which does not work due to the lack of usb.
Click to expand...
Click to collapse
When you enter recovery, and get the red triangle screen, adb should recognize the phone from there. Also, if you set the phone into 'fastboot' mode, from the bootloader, does fastboot see the device?(fastboot devices) As blake directed you to another post of mine, you see one of the questions is if you are S on or S off. Whats the result there?
also, not sure if some of this may help or not, because you're phone is freezing up, but see this thread in regards to SD card and USB not being recognized.
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
hgelpke said:
Whatever the issue is, Z4root also causes the phone to freeze/reboot almost immediately as I run it. I think the problem is that some files got flashed during the attempted root that are still lingering a causing the issues. By all accounts the phone is restored to stock in that it reads the PC36IMG file just fine and restores everything that needs to be restored. It even says that recovery is restored. The problem is that recovery is not restored at all.
I'm quite baffled by it. If I can't fix it, I was hoping to bring it into Sprint for an exchange since it does show s-on and appears to be completely stock. My concern is that it is in asurion replacement and if they send it off, are they going to discover something when it gets back to them, I don't want to get hit with a large sum of $$$.
Click to expand...
Click to collapse
If your phone is S on, you have nothing to worry about. Just don't send it in with a bunch of "root related" stuff on your SD card, and you'll be fine. How did you get s on?
Sent from my PC36100 using XDA App
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
hgelpke said:
I reflashed the RUU to get the phone back to stock. And by all accounts, it worked. Except that it didnt.
Click to expand...
Click to collapse
So running the RUU seemed successful, but it still didn't work? But it did turn you back to S on? Had you used Unrevoked before?
Sent from my PC36100 using XDA App
I did the autoroot found here:
http://forum.xda-developers.com/showthread.php?t=838448
If I'm not mistaken, it uses some of or all of unrevoked, but I'm not sure.
I have not used the files from the unrevoked website though.
Can you attach the autorootlog.txt file to a post for me to take a look at? If you got a refurb phone it may have had something still messed up by the previous owner.
Sent from my PC36100 using XDA Premium App
I'll get the log file when I get home from work. Hopefully there is something telling in there. It didn't really dawn on me that the phone could have been rooted by a previous owner, thereby doing something to my attempt.
It's pretty rare anymore but definitely not unheard of. When the new hardware came out there were a ton of people bricking them by forcing their hboot to downgrade or trying to root with the old unrevoked. And, you could definitely tell with some of the refurbs.
From my personal experiences with asurion, along with those of quite a few people I've talked to, they don't really fix the refurbs as much as just get them back to a useable state so they can be pawned off on someone. The minute you try to root or flash an upgrade/ota it is going to start acting up again.
Sent from my PC36100 using XDA Premium App
Since I'm getting another Asurion phone, what can I do to avoid it in the future?
Depends on what is wrong with it. Although, if it boots to the bootloader then odds are it is fixable.
Sent from my PC36100 using XDA Premium App
Xhausx, I want you on whatever subforum is my hone forum. when this man speaks, . ... listen.
Sent from my PC36100 using XDA App