I have installed a few ROMS with no problems, however on the last install I noticed programs from another ROM still on the phone. The boot screen (from Jacks, a dog that is now starting to irritate me...) can't be changed. How can I install totally clean?
I would confirm you flashed the right ROM. Normally the boot screen is also replaced with a new ROM. Re-flash and see what happens.
Also, do a hard reset once flashed to new ROM (general recommendation).
Related
I've been flashing new ROMS on an 8525 for a couple of years now, but I'm new to the 8925.
I've been reading a lot, I think I understand the relation between SPL and the ROMs now, but I'm still puzzled.
I keep getting a lot of cruft left behind from prior ROMs and don't know how to get rid of it. for example about three ROMs ago, I flashed the "Mobile Vista" from ansar. Now I still get his Today theme, and there are still a lot of apps installed that read "ansar..."
I've tried removing the battery before flashing, making sure the SPL version is OK with the ROM doing hard resets - nothing seems to let this device start from a "clean slate".
I'm trying to find a ROM I can be happy with, which is why I'm trying so many, but I can't fairly evaluate aon one ROM if I don't know what I've really got installed.
TIA
Walt
I've never heard of anything like that happening Are you sure it is the today theme, or just the boot splash? That would be most likely.
As far as the programs, maybe most of them are from ansar? Which ROM are you using right now?
I just flashed the PDA Corner latest version (15) and it seems to be behaving now. Prior ROMS I tried this morning included Athine, Garmin and Phoenix.
Prior to flashing PDA Corner, I did an "Erase memory" (hard reset from software) and removed the battery for about 10 minutes. Maybe that's what did it. I agree, I've never seen anything like this before, I always thought that flashing the ROM reased everything, but then I started reading about SPL on the Kaiser somehow being more than just a bootloader so I got concerned.
And yes, it was the Today screen including clock, wallpaper, etc. The splash screen on bootup actually did change to the one corresponding to the new ROM.
Thanks.
Walt
When flashing a new ROM, when you get to the "Tap screen to begin" do you perform a Hard Reset?
If not, I suggest you start doing now.
Also, merschle (ex-moderator and Artemis cook) recommended flashing a ROM twice with a Hard Reset in between. I don't do this, but it just might help
Ta
Dave
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Billun said:
Flash a stock HTC rom and then try a modified rom again. It always helped me when i got strange flash problems.
http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
Click to expand...
Click to collapse
I hard reset three times then I flash an OEM ROM, then I hard reset three more times to be sure. I know it's anal, but it works for me.
I don't know how you're flashing try the SD Card method.
It's safer and more reliable.
The SPL & Rom have closer relationship than on your older device.
A sign of have the wrong SPL or needing to change to another SPL is freezing. If you notice your device is freezing or non-responsive, flash the recommended SPL by the chef.
Don't worry any, I was the same when I upgraded from the Wizard...gotta learn all over again.
Newbie flashing here. Followed everything and flashed my first rom yesterday.
Flashed: RUU_Kaiser_HyperDragon_IV_Mega_6.5_WWE_20091006_11-54PM
After trying that one, I then i flashed to another rom.
Flashed: KAISER_WM6.5__3_34_721_V31__B23041_09032009 (not sure which thread i got it from)
But when the phone started up it showed the stupid splash screen from the hyperdragon rom but booted into the new rom (slight problem)
Then i wanted to try another rom this morning and read to flash back to htc rom first. So i just did and i am stil looking at the last rom i flashed. I have hard reset a couple times here and there, and after installing the htc official rom (WTF problem)
Im gonna try loading this next rom now, but i have a feeling i wont see it when it boots, ugh
Not all roms come with splash screens. When you flash a rom that does not come with it's own splash, the splash from the previous rom is retained.
Hard reset, flash the stock ( oem ) rom, the when it says tap here to set up , hard reset again. If you fallowed the right flashing steps ( which you have previously, obviously ) the stock rom should boot up.
Ah, indeed. Thank you for the response. Flashed back to stock rom and all is well. Not so sure i like this flashing stuff.
carhigh said:
Ah, indeed. Thank you for the response. Flashed back to stock rom and all is well. Not so sure i like this flashing stuff.
Click to expand...
Click to collapse
Once you hardspl your phone, it is kind of hard to brick it. A stock flash usually solves everything. Flashing is addictive, it brings out the " gotta have the latest and greatest " in you.
But even after flashing over a hundred times, I still hold my breath everytime I flash. I already bricked one phone way back in the early days of Kaiser flashing when the phones first came out.
Well, Please point me in the direction if this has been asked before but search hates me right now.
But the problem is I've recently flash Timolol's Stock Like Rom, and it's a nice rom but I am missing sense so I realise that Cap's ROM had been updated I flashed and it was successful but put me into a reset loop and so I reflash it again and it froze on the boot screen.
So I had the idea of flasing back to the original ROM (Stock like) and it's working okay, Why can't I flash to Cap's Rom again?
I had it on there before I went to try Tim's Rom...
EDIT: Forgot to mention that after both ROM flashes of Cap's I did do a hard reset
Thanks
I managed to fix it, (not quite sure what was wrong with it though)
I did a hard reset before I flashed and again afterwards
I've noticed other people seem to be having this same problem and there hasn't really been a distinct solution that I can see, so hopefully this question will be helpful in the future and not repeatative.
I've been trying to update to CM7 from CM 6.1.2 on my Evo. I followed instructions from here http://forum.xda-developers.com/showthread.php?t=902051 and downloaded all the recommended software. First I tried to just flash the rom, then the kernal, then the gapps. All seemed well at first, and I got past the Evo 4G screen, but it got stuck booting on the Cyanogen animation (the arrow just keeps going!)
Then I tried to wipe the Davlik-Cache, and rebooted again. I left the phone alone for about 45 minutes, and it still got stuck on the Cyanogen animation.
Finaly, after searching through the forums, I found another post which suggested I do a hard reset then flash the rom, kernal and gaaps then clear the cache and davlik-cache. Still, I'm stuck on the animation. I have a nandroid backup, so I can get back to 6.1.2, but I'd really like to get CM7 working, anything else I should try?
You should't have to do the kernel separately unless you have a specific reason for doing so the ROM comes with a kernel for you. I had a similar problem with my HTC however I was able to get it resolved by installing gapps. Here's what I did -->
Used ROM Manager to go back to working ROM
From working ROM, accessd ROM Manager and chose rebooted into recovery mode
Once in recovery cleared/wiped everything (cache, data, delvik) installed gapps then cm7
Restarted
It did take awhile after restart to get going however once it did it worked marvelously!
Hope this helps and good luck!
Reboot
Similar Problem, Defy CM7 Bootloop
The first time i tried installing CM7 I got a boot-loop. I have tried at least 7 different tutorials all with different variations of flashing this and wiping that yet none yield results. Still stuck at boot-loop.
The most recent thing i have done was used RSD Lite to flash
"JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf"
this got my phone running again, i then pulled off some magic by rooting using a combination of super1click, Z4 and installing superuser myself. after that i copied the files for a bootmenu into my /data/ folder. using CWM Recovery v2.5.1 flashed
"freq_F_US_342_107-850-1700-2100-signed.zip"
to get my 3G running again, and gave up of CM7.
If anyone has anything that could help id appreciate it.
(ps. i've tried many variations of wiping things and re-flashing things)
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.