A little(big?) tip for flashing Kingdom Sense 3.0 ROM - Droid Incredible General

I'm new and honestly I prowl these boards to learn as much as I can so,
forgive me if this post is out of place BUT
I was having a hell of a time getting Kingdom Sense 3.0 ROM to behave and I was waiting 20+ minutes...nothing was happening.
It dawned on me to maybe try setting aside a recovery image and the rom on my desktop then format the SD card(fat 32 of course) and low and behold
Sense was up and running within 5-6 minutes of boot!!
I have since has a few problems with the lock screen hiding from me but nothing
too bad, if I can only figure out how to get the usb to work!
It may work for those who are having a problem with it...give it a shot

Wait so you were waiting for the ROM to install or you were waiting for it to boot up the first time?

Related

Changing Boot screen?....

Hey guys. i have probably what everyone will call a stupid question, but ive looked everywhere and still have not gotten a solid answer.
Basically, the first ROM i loaded was a version of CELL Series that had a costum slate grey boot screen. i liked it, but im addicted to ROM flashing and started putting other ROMs on. bad thing, is that no matter what rom i flash, the CELL series screen is the first thing i see when turning on my phone. ive run task 29 and loaded Energy GTX at the moment, but that same boot image comes up and i have no clue how to change it....
is there something im doing wrong that can be fixed?
DaemonAshra said:
Hey guys. i have probably what everyone will call a stupid question, but ive looked everywhere and still have not gotten a solid answer.
Basically, the first ROM i loaded was a version of CELL Series that had a costum slate grey boot screen. i liked it, but im addicted to ROM flashing and started putting other ROMs on. bad thing, is that no matter what rom i flash, the CELL series screen is the first thing i see when turning on my phone. ive run task 29 and loaded Energy GTX at the moment, but that same boot image comes up and i have no clue how to change it....
is there something im doing wrong that can be fixed?
Click to expand...
Click to collapse
When you flash a new rom did you do a hard reset after that?
if so, idk BUT create your own boot screen.... http://forum.xda-developers.com/showthread.php?t=684301
Not all roms include custom boot screens ...
I know the Energy does not , at least not the "first" boot screen ...
DaemonAshra said:
....
Basically, the first ROM i loaded was a version of CELL Series that had a costum slate grey boot screen. ... but that same boot image comes up and i have no clue how to change it....
Click to expand...
Click to collapse
Here's a ready made 1st boot screen you can flash via microSD for exactly this situation, made via pakistaniprince's post above. I've also included the stock pink tmobile screen if you want to go back. If you do make your own, please post in that thread so we can have a ready made collection. Just put the leoimg.nbh from the zip into your FAT32 microSD and go into bootloader, it's that simple. takes less than 30 seconds.
http://forum.xda-developers.com/showthread.php?t=709548
thanks everyone for the great advice! i will a new one when i get home. and i might even create my own. it sound like a fun project. i will post what i make when i finish it

[Q] SOD no matter what build

Well before everyone attacks me with "try searching on forums" responses, i have done that already. So here is my problem. no matter what build i use i will occassionally get sod and have to remove the battery to power it back on. the button lights turn on like its going to power on but no matter how long i wait it wont come out of sleep.
I have all display settings turned off in windows mobile before i boot into android, and i have auto like turned off in both windows and android. I have auto rotate turned off, and screen time out set to 30 min, which actually fixed my problem for a while. it always seems to happen that something happens that i have to power off my phone, and as soon as i do that is when it starts acting up and i get sod. it takes a few tries of taking out the battery for the phone to stop getting sod but after a few days it seems to come back.
I have even tried reformatting my sd card and still had the problem. i have the stock 16 gig sd card it came with. i havent flashed anything on the phone because i dont want to risk screwing up, so you guys are my last resort because i have tried everything.
Time to try different sd card.
In both windows and android, Auto light is off and you manually set the display backlight?
Have you tried the hyperdroid 1.7 version??
Vaizard84 said:
i havent flashed anything on the phone because i dont want to risk screwing up, so you guys are my last resort because i have tried everything.
Click to expand...
Click to collapse
Im pretty sure this is ur problem. Lots of things go wrong with stock.
its not as hard as it seems. just follow the intructions for ur specific hd2.
(look in the usa hd2 forums) if ur a usa hd2 user. IM SURE ITS A STICKY.
IF U WANT TRY THE OFFICIAL UPDATE FROM T-MOBILE!
i have heard good things about it
Unfortunately you have no choice but to flash the HSPL, a custom rom, and a radio. these are easy. ive flashed my phone countless times. I've also flashed other peoples HD2's countless times. Even when the phone was in the middle of flashing and the power went out at my house it did not brick the phone.
If you want to run android as a daily driver (like I do) my best advice is to flash the following.
HSPL (duh lol) http://forum.xda-developers.com/showpost.php?p=6891358&postcount=1893
Radio version 2.12.50 http://www.megaupload.com/?d=9GU2FF3X
WinMo rom http://forum.xda-developers.com/showthread.php?t=734238
(click on the first 'ChuckyDroidRom' picture under downloads in the first post.
You will use this utility to flash the 3.
http://forum.xda-developers.com/showthread.php?t=575524
when/if you download the 3 items, create a folder on your desktop. Name it something simple. Then inside that folder create 3 folders. name them HSPL, Radio, WinMo Rom. extract the downloaded items to their respective folders.
with the customRUU utility. extract the file to each of the folders.
Then,
Flash the HSPL first, the radio second, then the winmo rom.
when finished with those use the format sd card app in windows mobile to format your sd card (the program is set to format to android specs)
then copy whatever android build you want to the sd card.
Enjoy!
if you have any questions you may feel free to PM me. I will be home all day and would not mind helping you.
wow that is a lot easier than i thought well so far its working really nice, i havent got any sod yet, keeping my fingers crossed lol. thanks everyone for the help!
Vaizard84 said:
wow that is a lot easier than i thought well so far its working really nice, i havent got any sod yet, keeping my fingers crossed lol. thanks everyone for the help!
Click to expand...
Click to collapse
Yeah I promise you it was your radio/rom version. I had the EXACT same problem and nothing fixed it until I flashed and updated my radio. sometimes you just have to bit the bullet and dive deep!
cheers on your fixed phone, and knock on wood for no more SOD!
If you do experience SOD again. I recommend a faster SD card. I was having issues with any build I was using. Up to date flashed radio and lite WM rom, my only cure was faster SD card. I went from the stock 16GB C2, to an 8GB C6 (17.99 from Amazon), and I have not experienced SOD anymore. I have issues where sometimes the screen will not come back on right away, and I have to wait a few seconds, but it never sleeps on me anymore.

[Q] android wont go past htc screen

my android build wont go past the htc screen i have re formatted the sd card would i have to flash another win mo rom
i hate when people act like they dont want to help lol
It's not that noone wants to help. We see this question posted at least a dozen times a day and it's just obvious you've not searched. The first boot of Android (any build) takes a long time, up to half an hour depending on various things. Leave it, if it doesn't work after that long, then post back.
i left it go for 3 hours lol...i even went back to stock and went thru the whole flash process
Ok then write down your entire process to get an android build to the point where it's just sitting there on the HTC screen.
ok i flashed the hspl then radio then winmo rom (energy) then i downloaded the biffmod rom extracted the rom placed it all in the android folder went to the file explorer clrcad then haret and it jus sits there... it was working 1 rom ago and that malfunctioned so much i had 2 leave it and now no android build works
I am having the same problem, I have let the device cook for over an hour and drain the hell out of my battery and still no go? It all started with SkinnyEVO v1.7, and yes, I did try changing the kernel to no avail, then the other day I was going to give the Bluetopia build a whirl, same result. I have no problems booting SkinnyEVO v1.5 or Sense rEVOlution v2.3. These two work amazingly well on my device.
Does anyone have any ideas as to why certain builds have this problem and other builds do not? I am suspecting it is a kernel issue but I may be wrong in my suspicions. Please enlighten me if so.
Thanks ..... HTR
yea im tryna figure out myself
I had the same problem when I got my HD2...formatted sdcard with HD2. After this I got no more problems.

[Q] LOOSING!!.. to my htc tattoo

HI GUYS!
After hours of searching for my problem.. I finally gave up.. ending on LOOSING!!! hehehe...
Here's what happen...
I decided to update my CyanogenMod 7.0.0-RC1.7002 2.3.3 into 7004. I don't like to use ROM manager so I use the old trick.. home+power key to go to recovery. Clearing data,cache,system....
But it seems that i get STATUS 7 error. After reading on I decided to update clockwork mod from 6.0.0.5 to 6.0.0.6.
Updating it in the recovery.. Its says update complete for clockwork.. I decided to reboot clockwork so i can try to update my rom again..
Now I can't boot into clockwork recovery.. BOOM! LOOSING.. =(
Reading on different threads.. my eyes really hurts now and forgot about my laundry.. sun is down T_T NO LUCK FOR ME..
Here's what I can and can't do right now
-I can only boot to HBOOT
- can fastboot usb but can't detect my memory card
- when i do up+power, I get 3 vibrates but blank screen..
- in the endless TATTOO spash screen.. I can hook it to computer but cannot detect the device.. it says error at some point.
-when i hit home in hboot.. it goes to endless TATTOO splash screen but no recovery appear.
-when i go to simlock FAT32 int OK.255 not key-card!!!! shown.
I hope I can recover my phone as I suspected it is bricked.. omg will i be... LOOSING??!!
Please help genius.. thank you very much!
rommanager is buggy and boot loop occurs. gapp also the cause.
redo it. wait for splash screen blue circle.. it will work
no luck,... i waited for 15 minutes on tattoo logo.. and i think that is enough if i would see the blue spash screen.. T_T but i didn't..
any other ideas? genius persons of xda =)
I had a lot of this TATTOO screen bootloops when trying to update custom roms in the past, and the most of the times I could connect with adb.
If you can, I think you can flash the recovery image again via adb.
If you can't, try to flash the stock rom from windows. There is a sticky that have info about this(because theres a problem to use the correct drivers, needed to be my htc both on normal boot and on hboot).
http://forum.xda-developers.com/showthread.php?t=646663
Another thing you can try is to take the rom.zip from your pc' s temp dir(run RUU utility and without to close it, search in temp dir for rom.zip), rename it to CLICIMG.zip, put it to sd card(via a card reader if cannot recognized by usb) and flash the rom from hboot(the stock rom).
take a look
http://forum.xda-developers.com/showthread.php?t=989762
thanks dancer_69.. but I was just about to do the rom.zip procedure but boogeyCZ says it needs the goldcard and I have none.
>.<
I successfully created it last year but my laptop crashed and needs a full wipe.. I did not backup my goldcard (failure)
Is it possible to do the rom.zip procedure without the goldcard?
using the stock rom puts me back to the original rom (1.6). Doing this requires me to root my phone again am i right?
I think that if the rom is the same with the rom that the device had from factory, the goldcard isn't nessecary(it works for me several times).
And yes, you're right, you need to do the rooting proccess from the begining as the phone will return to factory state
well i am in cyanogen mod 7 7002.. if I roll back to stock rom which is 1.6.. i can't do it is that what you mean?
Also, if I do this, what could possibly go wrong??
I have the stock rom now I am just waiting for genius replies from you and to all xda developers.. I think It's really not my fault as I did just the instructions of the developers in updating to 7004... Its just really hard when something goes wrong like what happened to me...
I am also thinking on going to HTC service center here in my country.. but the problem is the one year warranty covers only manufacture defect and manipulating the software of the phone will void the warranty. (I am just hoping they won't ask me what happen to it >.<)
I just want to do the best of my ability to fix it. So please help me get through it.. Thank you very much..
If the checks don't pass, the rom will not installed.
But if you have your stock rom, I think that it will flash without problems(I've done this 3 times on my device and without a goldcard). I think that the goldcard needed to be able to flash any Tattoo's official rom from hboot.
PROBLEM SOLVED!!
What I did is I went in htc service center in my country. (main office). They re-program my phone and after 15 minutes.. it's alive!! =)
But now I am having doubts in rooting my phone again. I think it is much better if I leave the phone in its true version of android.
-It is much faster and stable (when I am in CyanogenMod 7, it is laggy, occassional errors, unstable even with working camera now, it is still buggy as others said). I am more on speed and snappyness of the phone and for me a rooted HTC tattoo (gingerbread) slows the phone down. I am not saying rooting is bad, but for a phone that has low specs, maybe I will just upgrade my phone with a 1ghz processor and root it with cyanogenmod 7 and we will have a happy ending on it. =)
But it is a +100 to the developers, that at least I learned a lot in the world of android. Please keep up the good work and thank you very much genius people of xda developers, I can now say.... WINNING!!!!
PROBLEM SOLVED!!
What I did is I went in htc service center in my country. (main office). They re-program my phone and after 15 minutes.. it's alive!! =)
But now I am having doubts in rooting my phone again. I think it is much better if I leave the phone in its true version of android.
-It is much faster and stable (when I am in CyanogenMod 7, it is laggy, occassional errors, unstable even with working camera now, it is still buggy as others said). I am more on speed and snappyness of the phone and for me a rooted HTC tattoo (gingerbread) slows the phone down. I am not saying rooting is bad, but for a phone that has low specs, maybe I will just upgrade my phone with a 1ghz processor and root it with cyanogenmod 7 and we will have a happy ending on it. =)
But it is a +100 to the developers, that at least I learned a lot in the world of android. Please keep up the good work and thank you very much genius people of xda developers, I can now say.... WINNING!!!!
I don't think that you have right about this.
I've used stock rom and custom roms in parallel in the past, and the custom roms win(even before camera and fm radio work). And the device is much faster with custom froyo and gb roms than the stock one. Plus the battery drains in a lot longer time(for me with stock rom battery needed every day charge, but with the last versions of froyo and gingerbread roms 2 days the minimum). Plus a lot more apps work with our tattoo.
JORGEtattoo said:
PROBLEM SOLVED!!
What I did is I went in htc service center in my country. (main office). They re-program my phone and after 15 minutes.. it's alive!! =)
But now I am having doubts in rooting my phone again. I think it is much better if I leave the phone in its true version of android.
-It is much faster and stable (when I am in CyanogenMod 7, it is laggy, occassional errors, unstable even with working camera now, it is still buggy as others said). I am more on speed and snappyness of the phone and for me a rooted HTC tattoo (gingerbread) slows the phone down. I am not saying rooting is bad, but for a phone that has low specs, maybe I will just upgrade my phone with a 1ghz processor and root it with cyanogenmod 7 and we will have a happy ending on it. =)
But it is a +100 to the developers, that at least I learned a lot in the world of android. Please keep up the good work and thank you very much genius people of xda developers, I can now say.... WINNING!!!!
Click to expand...
Click to collapse
I use one click recovery and then use rommanager, easy
Well we all have our perspective.. but thanks anyways. I will have a break on rooting, as soon as the cyanogenmod 7 is on stable situation.. i will try again.
You are righr, more apps is available when you root.. well i now feel the importance of rooting.
After much consideration... i rooted my tattoo again using CyanogenMod 7.0.0-RC2.2 (7007) 2.3.3 Gingerbread.
Very pleased with the speed of the os now.. thank you very much kalim.
I use one click recovery but there is a memory error.. but it booted nicely.. its just that i cannot hook mass storage via recovery.. don't know why., I just use a memory card reader to transfer the rom. I don't want to use rom manager anymore, I am more or less traumatized on what happen.. hehe...
Again.. thanks! If you don't know how to root your HTC tattoo guys.. it is time for you to learn... =) very happy

[Q] Kernels

ive tried many lovely roms on my dream, but all but one have horrific battery life, the one exception is gingeryoshi 1.1 with the new farmatito kernel, so i figured i could just install it to my preferred rom and id be away, however it seems not so simple as all that
first i tried installing it to the cos-ds image i was running at the time, it simply killed that stone dead, wouldnt boot past the boot anim. so i decided to test it on my current fave rom, beatmod 2.2, i did and it booted and seemed to run fast and reasonably problem free until it came to installing an apk i had on my sd card, where i found that it wouldnt read the card at all, it said no card inserted and on pulling and reinserting it displays damaged SD card and often causes many force closes on other running processes, so what is it that i need to change to get it working, it seems close enough that itll just need some tweaks so if someone could point me in the right direction id be grateful, just a "read this, this and this" and some links is plenty (the info may well be on here already but digging it out can be a nightmare and i havent got that far on my own yet, its a BIG forum)
so what exactly are you trying to figure out? how to fix your sd card or how to get the kernel working? your sd card may have actually just died because believe it or not those things dont last as long as you think.. thore more times you copy things on and off them the quicker they die.. but as far as the kernel problem im not sure exactly how it all works i usually get the recommended kernel for rom... usually on the post with the rom link
no the sd card is fine, its any sd card when used in beatmod with that kernel, so getting the kernel working, what i want is a rom thats a little faster than the somewhat sluggish gingeryoshi but is compatible with the farmatito kernel which solves my short battery woes
ive actually even tried cos-ds and used their recommended farmatito kernel but even then it still leaves me stuck at the g1 boot screen. infact as yet beatmod is the only rom i have got to boot at all with a different kernel than the one that comes with the rom. im not sure if its something that im doing or possibly that the g1 is on its way out, its just refused to use the backup i made before testing the greenromproject rom (which also didnt boot, again stuck at the g1 screen) as the md5 check failed and what with it being picky about which backups it will and which it wont boot anyway im beginning to suspect there may be more to it than a software complaint
and now that ive finished typing i look over at my phone to still see that big g1 glaring at me, none of my current backups now work ah well try a fresh install i guess

Categories

Resources