So, I flashed my frist rom back in April. I tried out the Energy Rom. Last night I tried out the Core Cell Evo Rom. This Rom started to give me trouble so I flashed to the current energy rom. I'm still new to this, so I think I may have made some kind of mistake that I'm not aware of.
I noticed that when I flashed to the new energy rom, the splash screen for the cell rom came up. Now whenever I try to change the date and time on my phone, it kinda locks up. I think it still functions, but because the screen is frozen I can't see what to press so I end up doing a restart. Does anyone know how I can remove all the remnants of the cell rom? I thought when you flash a new rom, it's supposded to completely get rid of the old rom?
First run TASK29, then flash preffered ROM, after that do HARD RESET, and then it must be OK
Some ROMs include a new splash screen, and some don't. The EnergyROM series doesn't include a splash screen, so that's why you can still see the Core splash screen.
You can find utilities to replace this if you search for "splash screen".
Task29 won't affect this (i.e. it doesn't touch the splash screen, nor the radio either), but it does a good job at wiping the ROM area itself.
If the problem still happens after a task29 and a flash (i.e. the lockups), then you should post about this in the thread relevant to the ROM you're running.
Thanks for the info guys. I'm at work but I'll try out the task29 thing when I get home. I didn't post this in the energy rom thread because I didn't want to seem like I was directing my problem at that rom until I had a good idea of what was going on. If the problems still persist, then that's where my next post will be.
You can always reflash a stock ROM. That will give you the original spash screen back and then you can flash the custom ROM again.
Well, it wasn't the splash screen that I was worried about. Seeing the splash screen made me think that the core cell rom was conflicting with the energy rom. After hearing what steviewevie had to say on the subject, I know otherwise. I'll also install a custom splash screen later now that I know that can be done to.
You can go here for the steps to change the splash screen its actually pretty easy and fun.
http://forum.xda-developers.com/showthread.php?t=576703
Ok, I ran Task29 and I've installed the stock rom. Do I need to do another HardSPL before I can flash a new rom?
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
creglenn said:
No you only need to perform the hardspl once which you have already done so from now on when changing roms just make sure to task 29 then flash new rom and thats it
Click to expand...
Click to collapse
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
sigma20xx said:
Oh? I didn't use the stock rom that was put up on this site. I actually downloaded the Tilt 2 rom from the HTC site. So I thought that would have made some kind of difference.
Click to expand...
Click to collapse
HardSPL was designed to stay on the phone, even if you flash stock ROMs. You have to specifically run the relocker utility (from the HardSPL thread) if you want to go back to the stock SPL (e.g. for warranty return).
MOD Note
I'm moving your thread to General. This has nothing to do with ROM development. Custom ROM usage yes, but not Development.
Russ741
Related
Recently acquired a used 8525 and have been checking out tons of custom ROMS but today my phone locked up and wouldn't do anything. I am flashed to 2.10 HardSPL and was running the stock "like" 6.5 ROM on the front page of the Hermes forum. Phone would start up but locked up at the first HTC splash screen. I tried resetting and removing the battery but it would hang at the same spot. I flashed to a different ROM and everything seems OK. The 6.5ROM ran fine for a few days when it was installed. Is it possible to damage the internal memory by flashing and reflashing constantly or is the issue more than likely a software problem?
You need to flash the at&t stripped rom between those custom roms. That will "straighten out" any odd memory issues like what your experiencing.
And I'm guessing it would take several thousand (or more) rewrites of the memory to mess it up. Probably similar to compact flash, or a thumb drive. Maybe one of the more knowledgeable ones around here know.
Thanks for the info. Do I simple flash the stripped AT&T rom from the bootloader and then do the same for the custom rom afterwards?
Yup! And it seems just flashing the at&t stripped rom seems to be fine, no need to let it go through setup and all of that. I generally wait for it to get to the "tap here" screen, then go into boot loader and reflash.
I'm having the same issue one my 8525.
I can't do ANYTHING because my phone is stuck saying smart mobility.
And, a black screen.
How do I....
Do I simple flash the stripped AT&T rom from the bootloader and then do the same for the custom rom afterwards?
I've downloaded your stripped AT&T room... now what? I dont know about bootloader
Ok. It looks like I finally have SOMETHING other than that screen.
I just did a hard reset.
Is there anything I should do BEFORE this happens again?
Install Hard SPL V7 if you get to the today screen... Go to here - http://forum.xda-developers.com/showthread.php?t=296722
page 116, post 1160 to use the sd card method...
This should make it easier to recover your Hermes if something goes wrong.
Cheers...
SD card MUST be 2Gb or less and formatted FAT32. Check your spelling - hermimg.nbh...
I'm fully functioning now... I have installed HARD SPL before.. do I re do it?
Or, what?
all is working normal now
Nah, once it's there, there is no need to redo it. It will stick between flashings.
I've seen people say to flash a stock ROM before flashing a cooked one - why? Surely all the data from the last ROM is overwritten by the cooked ROM anyway, isn't it?
iridium21 said:
I've seen people say to flash a stock ROM before flashing a cooked one - why? Surely all the data from the last ROM is overwritten by the cooked ROM anyway, isn't it?
Click to expand...
Click to collapse
I'm not sure about the TP2 but on the hermes it was always recommended for going from an extended storage rom to a normal rom. Might have just carried over since then.
Doesn't make a difference, its a myth. The flash chip gets rewritten.
petard said:
Doesn't make a difference, its a myth. The flash chip gets rewritten.[/QUOTE
If custom ROM without radio You should flash stock ROM first(if you would like to have it)
Click to expand...
Click to collapse
petard said:
Doesn't make a difference, its a myth. The flash chip gets rewritten.
Click to expand...
Click to collapse
Not a myth, at least to some devices like the diamond, HD and the HD2 where members who decide to skip this step are finding themselves with very unstable devices that often turn off or restart on there own.
Flashing a stock rom or using the mtty tool erasers any artifacts that can be left behind when flashing cooked roms.
Flashing Procedures I use:
• flash stock rom or mtty tool found in sig.
• flash cooked rom
• hard reset twice
Never had any issues from automatic resetting of any kind!
ive been flashing since the wizard, and probably after 20 phones ive never flashed stock rom first. i actually stop hard resetting to.
intruda119 said:
ive been flashing since the wizard, and probably after 20 phones ive never flashed stock rom first. i actually stop hard resetting to.
Click to expand...
Click to collapse
As mentioned, some devices are more prone to it perhaps. There are a lot of threads that speak to members dealing with device resetting and other glitches and the remedy recommended is always the same.
For me, it's just habit now....
Only do this as a last ditch effort. Say u flash a custom rom, hard reset as u should, then configure the rom. But u seem to be getting odd screen freezes and problems that only u seem to get and not anyone else for that particular rom. U go into the thread of the rom asking and everyone says its just u. Well at this point u would flash stock rom, hard reset, flash same custom rom, hard reset, now the custom rom works perfect! Why? How th hell should i know? I just know what works!
I think that flashing a whole stock ROM each time is a bit over the top. If you want to be on the safe side, then do a hard reset on your old ROM, then flash the new ROM, then hard reset again. That should do as much as flashing the stock ROM would do.
I think main the benefit is because the CustomRUU doesn't perform a Hard Reset after flashing, where as the Stock RUU does.
Some people prefer to do a "task 29" nand format. Unless you've been flashing dodgy ROMs that go outside of where they are meant to then I think you'll be OK.
JM2c's
Dave
DaveShaw is the man so take his advice.
I have flashed over 40 ROMs (all from XDA or HTC) on my TP2 and I never flash back to stock. I have had no issues. I also did the same with my Tilt1.
Hello all,
I've just heard of HTC not providing warranty to devices with altered Roms.
Considering this is true, has the Touch Diamond 2 a reset button to place the original factory Rom before sending the device to the manufacturer?
I'm planning on buying one, this is why i'm asking.
Thank you,
-Moving Thread-
1) this does not belong in the android development
2) the reset button reboots the phone.
Rebooting the phone will only restart whatever ROM is on the device. You can use a key combo to force a ROM reflash that will return your phone to its original configuration. There is also a program called Clear Storage on these phones that will do the same thing.
Miami_Son said:
Rebooting the phone will only restart whatever ROM is on the device. You can use a key combo to force a ROM reflash that will return your phone to its original configuration. There is also a program called Clear Storage on these phones that will do the same thing.
Click to expand...
Click to collapse
Wrong.... using the "key combination" will NOT reflash back your original rom.. all that does is hard reset the phone to the original settings of the custom rom you put on the phone.
If you have done any reading about flashing roms you'll see its a 2 parter. The first is the Hard SPL and the second is flashing the custom rom itself. If you plan on sending a phone back in for warranty purposes and have a custom rom on then you need to do two things. Flash back to the stock rom which you can download in the roms section and then you need to respl your phone to whatever version of spl your phone had. I believe there are three different ones to choose from.
That way when you send it in they cant tell that you had a custom rom on and that you dinked with the phone in any way.
So in short.... doing a hard reset will NOT just go back to your original rom.
Do some reading in the rom section, specifically the Hardspl thread and within the first page everything is explained in details on how to hardspl the phone and REspl the phone back.
good luck
Didn't mean to get your dander up, but if you reread my post I said nothing about it reflashing to the stock ROM. I said it will reflash to the original configuration, meaning whatever ROM is currently on the device will be reset and lose any customizations or add-ons. A soft reset will not accomplish this. Sorry I wasn't more specific.
Oh no worries Miami... Keep in mind the guy has 1 post... He could have been around for ages and know all about flashing roms and what not but its pretty easy to assume he doesn't know much about it with only one post. If I was confused by what you said I can only imagine what he thought. "oh once I flash a custom rom I just have to do a hard reset and it goes back to the way it was when I got it"
Just covering the bases here right
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Have you use amo-ra?
Sent from my evil evo!!
rsjc741 said:
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Click to expand...
Click to collapse
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
klquicksall said:
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
Click to expand...
Click to collapse
Thanks
I should face-palm myself. I just read the sticked post and I'm going to try some of his suggestions. He pointed out why cyanogenmod wouldn't work.
My whole consept of the framework went out of the window, and now I think of it more like a standard linux distro, in terms of kernel->ROM relationship.
I don't think I need to have a custom kernel for the Gingerbread beta-4, but i'll look it up just in case... Though I don't have a clear idea on how to flash that.
And to the person 2 above, im using Cyanclockwork. For whatever reason, I like its design verse RA recovery. I might try RA recovery just to see if it works better, as everyone has said it does.
I think i needed to clear all my caches and then load the ROM.
So I did a wipe of everything (data, darvik, cache) and trying to install the GB ROM. My boot screen is *still* looping. Do I need to get another kernel? Is it like flashing a ROM? Where are they at? I didn't see any in the software section...
I'm relatively new to this ROM flashing business and, before I flash my first custom ROM, I have three quick questions that I would be very grateful if one of you more advanced developers could answer.
1. Is it possible to return to the stock ROM (or on the DInc, HTC Sense) without unrooting, or would I have to unroot and reroot?
2. What is the possibility of bricking my phone? I have seen a lot of warnings about bricking, but what is the actual probability that this will happen?
3. By using Titanium Backup, how much am I actually backing up and how much will I have to do myself to re-customize my phone?
Thank you.
1) Yes, by backing prior to your first flash you can always revert back to your backup. You could also download a stock rom and flash to that as another method of returning to stock.
2) Bricking and reading information on flashing have an inverse relationship a.k.a the more you read the less likely you brick and the less you read the more likely you brick. If you use that thing called google you will almost certainly not brick your device.
3) Not sure I can answer this one as I don't use titanium for anything. To get my phone back to the point I had it after each flash I only need to spend about 5 mins tweaking CPU, voltage and placing my clock widget where I want it. Google handles apps and contacts so that isn't a problem. You can backup your messages and what not with numerous programs. Customization can become endless i.e. themes, display tweaks etc but I don't really know how far into that you have gone.
You can follow my step-by-step tutorial, found here-Rooting Droid Incredible- for a very easy way to root.
Backup stock rom first. Don't be like me.
Where's ma rosie at?
I flashed the Optimized Shift ROM, and everything worked very well. However, I do have one more question - a patch for the ROM was posted today, and how do I install that? Do I just flash it like a normal ROM, or do I do something else?
The dev (newtoroot) should have said whether it was something you could flash over or do a full wipe (like before first installing a rom). You just flash the updated version like you did initially.
Whenever I try to restore to my backup of stock Sense/Froyo, my phone gets stuck on the white "HTC Incredible" screen, and I have to take out the battery and reboot into Optimized Sense. Because of this, it appears I may be stuck in a custom ROM. Is there anything I can do?
teentech said:
Whenever I try to restore to my backup of stock Sense/Froyo, my phone gets stuck on the white "HTC Incredible" screen, and I have to take out the battery and reboot into Optimized Sense. Because of this, it appears I may be stuck in a custom ROM. Is there anything I can do?
Click to expand...
Click to collapse
Make sure you do a full wipe, the same thing you'd do before flashing a new ROM, and then restore the backup.
RMarkwald said:
Make sure you do a full wipe, the same thing you'd do before flashing a new ROM, and then restore the backup.
Click to expand...
Click to collapse
Thank you. Unfortunately, I just tried that, and it once again wouldn't boot up. Is there anything else I can do?