Well this is my problem. Just got a replacement Inc. rooted install latest radio, S-Off. Now my Nandroids that I had backup on my SD card when I load them my phones goes into a loop. any suggestion why this is happening. Also I use to be able to OC my old Inc. to at least 1500. This one won't go past 1300.
Related
First of all I have an unlocked Telus Desire. This is running HBOOT.83 and was rooted using Unrevoked.
The first rom I tried to install was LeeDroid 1.8 and I got a boot loop and never was able to get it running.
After installing this rom I noticed the phone started freezing at the white screen where it said HTC. I was able to go into recovery and flash Pinky just fine. I then decided I wanted to try the cyanogen mod rom so I flashed that and it was really really buggy for me.
I was able to flash back to Pinky but then I started getting Force Quits everytime I opened the market. I went to reflash the rom and now my phone doesn't boot at all.
EDIT: Now when I boot into the Rom I get a few errors popping up and then it restarts. So I can get into Pinky but it crashes and boot loops.
maybe try installing fake flash, clear all your caches and batt stats, install a basic rom just to get it up and running before you install a custom rom of choice. I have found it isn't as easy to brick this phone as say my old omnia i900 which was windows based. It could be that installing roms without clearing all yr caches is causing the glitches. I'm not an expert and don't claim to be but I always have a clear out before installing a new rom and it works for me.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Thanks for the advice, I will look into Fake Flash as I am not very familiar with that process.
As an update I managed to get into Recovery, and of course I flashed a rom which gave me nothing but a boot loop. Thankfully I was able to mount the SDCard in recovery mode and I am loading on one of the more vanilla sense roms to see if that works.
A lot of custom roms require you to have an ext3 partition on your SD card. This can cause bootloops if you don't have the card partitioned.
I'd also try booting without the SD and see what results you get.
You will all be happy to know the phone is no longer bricked. Recovery mode seems to be working again and I didn't really do anything to do that.
Was using my dad's Desire (I have my own), and thought I would do him a favour by rooting it, so he could backup. I rooted using unrevoked 3.21, and did a backup using ROM Manager. I've heard this is a bad idea, but I never had a problem with my Desire using ROM Manager, and an older version of unrevoked.
Anyway, after the backup, I tried to restart, and it got caught in a boot loop, never getting past the pink circle. (My dad has a t-mobile, HBOOT 0.75, have since upgraded to 0.93 with android 2.2)
My old backup Roms that I did for my desire work fine on his phone, so I have been able to do the above, but I really wanna get his old system back.
I've wiped the cache, done a full wipe, re-rooted, loaded the backup from Rom Manager, and from recovery, and nothing seems to work. The best I can get is looping from the splash screen, but another variation is getting stuck on the pink arrow circle.
So, what is the deal with unrevoked and ROM Manager not working together, when they used to be fine with old versions? Do I have to now backup by recovery alone? But more importantly, is there any way to get my dad's backup back, or is it gone forever?
Please help,
I'm sorry I can't help but here is an advice, never ever use Rom manager. Gives me lots of problems and scared me badly so many times in recovery. Maybe the plain all recovery methods in the clockworkmod would do fine although it has never worked for me. When I use it I still go into boot loops. Try not to use it but maybe that's just for me. Maybe you could try to get the Rom your dad previously used, flash it and on your SD card, there is a folder called clockworkmod, in it there is a folder named backup. From there maybe you could recover your data. I am not sure how but there is always a possibility. Hope that helps!
Thanks for the reply. I've given the phone back to my dad now. He wasn't best pleased about the wipe, but I was able to pull out his contacts from the data.img, which was the most important thing.
Sent from my HTC Desire using XDA App
Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!
I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.
I just got a new replacement Evo and rooted it yesterday. I installed miui 11.19 rom and set it up. I was planning to use a new memory card, so I inserted it and through amon recov, chose wipe partion, but I don't think that's where the problem happened. At the same time, I went to flash a new kernel the invisible one and also wiped cache/dalvik. After I do that, my phone just stays at the white screen upon reboot. I went back into recovery and tried to reflash the same rom but I was getting a weird error "failed... error at line 4". I put in my old memory card, but had the same problem. I had an old rom that was already on the card that somehow happened to work. I wiped all before I did that.
After that flashed successfully, I tried to flash Myn's RLS4, but it gave me a different E: error. Once again I had to flash an old rom. I don't think it is the memory card that is the problem, but maybe... possibly something to do with the way MIUI is installed maybe? Do I need to reformat? But it did it on a fresh memory card as well. Possibly something went wrong in the rooting process?
What do you guys think?
Wish I could help you on this but I am still new to ROOTing and I dont want to say some thing about something I know nothing about, But I can offer a few suggestions. Try to restore your old ROM. See if you still have the same problems and if you DO, Then logic deduction would lead me to think that its the miui ROM... maybe that ROM and your kernel are not compatible?
Did you flash a kernel or theme before you let the Rom load up or is this happening with just the Rom?
Sent from my EVO at the edge of Hell
If its a newer evo, late 003 or 004 version than your unit has the new camera hardware and will require the latest htc kernel. If the rom you are flashing doesn't use the stock kernel then your phone may not boot up properly or hang at the first screen.
Recently was running Synergy Rc1- non god mode, changed to MIUI, wanted to nandroid and lost root.
Was running Synergy RC1-nongodmode
-made a nandroid backup
-wiped / everything 2x
-mounted sd card
-flashed MIUI 1.8.5
Setup MIUI 1.8.5
-logged into market
-re-synced gmail
-rebooted
-downloaded rom manager
-flashed into recovery, to make nandroid
got stuck in boot loops, similar to thread
http://forum.xda-developers.com/showthread.php?t=1208084&page=2
however, after making an attempt to use the latest unrevoked,
my phone will flash the pcimg36 stuff, and I actually CAN get into
clockwork, but i get unable to mount SD card errors, when trying
to flash ANYTHING, however in bootloader, it has no problems
at all, and I know my SD card is good.
So i go into bootloader, to get my stats, and my S-OFF,
is ACTUALLY now S-ON!!
This is an evo thats stood the true test of time, from the day that it came out, until 3 days ago, this beast is in perfect shape.
I used the original 53 (maybe 83?) step root process, far before unrevoked.
And even worse, between hundreds of bootloops, after pulling battery, about 5 times, it actually boots into MIUI 1.8.5, but it ALSO cant mount SD card.
I have also tried several other SD cards, just FYI.
can ANYONE put me in some decent direction?
Normally i got this aced, i have no idea whats going here.
Hboot 0.76.2000
Radio 2.15.00.09.01
EVT2-3 ENG S-ON
Thanks! for the love of god
have tried fastboot stuff to oem qxdm stuff to try to get USB back, and still nothing.
Ive flashed Ruu, and no USB support while in on the phone!
again the fastboot stuff didnt help,
I tried manually flashing a radio through fastboot and get mismatch errors, assuming im trying to flash the wrong radio or something.
please, anyone, help.
im all ears, and have been reading non stop the past 2 days.
anything could help me now.