Basically, I have s-off and the official clockwork mod recovery installed. However, the same problems occurred with paul's version of custom recovery.
When flashing, I always go through the process of erasing all the partitions via mounts and storage, then i erase davlik cache and battery stats.
Then I install the ROM by the zip install.
And with kernels, I just install (not aware of any other steps that are needed)
But this is where I come unstuck. I am currently on RaiderX303's Cyanogen port. But I can't get any other roms to work. The same with kernels. Basically, flashing always completes with no errors, but then it crashes/stops at the second spash. So on core droid, it crashes on the android with a green circle going round it.
Anyone got any idea why this might be happening? Couldnt find any reference to it from anyone else.
Anyone got any idea?
tried getting clockworkmod from rom manager? the earlier version has a bootloop issue
I have the same problem with the Core Droid Rom, I believe its the kernal it has,some devices don't like it. The phone don't like the overclock, Infact not many do work on my device.
Sent from my Desire HD
rorydaredkign said:
Basically, I have s-off and the official clockwork mod recovery installed. However, the same problems occurred with paul's version of custom recovery.
When flashing, I always go through the process of erasing all the partitions via mounts and storage, then i erase davlik cache and battery stats.
Then I install the ROM by the zip install.
And with kernels, I just install (not aware of any other steps that are needed)
But this is where I come unstuck. I am currently on RaiderX303's Cyanogen port. But I can't get any other roms to work. The same with kernels. Basically, flashing always completes with no errors, but then it crashes/stops at the second spash. So on core droid, it crashes on the android with a green circle going round it.
Anyone got any idea why this might be happening? Couldnt find any reference to it from anyone else.
Click to expand...
Click to collapse
When you say erasing the partitions , do you mean wiping?, I personally would try installing ROM Manager from the market and letting that install the rom from SD, select wipe and backup before flashing and see if that helps at all, Can you flash the CM RC-1?
I can flash that and also the leeDroid and hd Rom. Just don't like the core Droid and buzz kernals
Sent from my Desire HD
yep I am installing by wiping, but on the last install I used rom manager and still the same problem. Just like vimto, I think it may be the Buzz kernel, so I will try a different kernel and see.
rorydaredkign said:
yep I am installing by wiping, but on the last install I used rom manager and still the same problem. Just like vimto, I think it may be the Buzz kernel, so I will try a different kernel and see.
Click to expand...
Click to collapse
There are some strange issues, camera not working for some of us on raiderx303's ROM, which seem to point to possible hardware variation I wonder if this is a symptom of the same issue?, CoreHD uses buzz kernel as default doesn't it?
But didnt you say you had issues with the MCR? that is based on stock rom so am surprised at that
Yep, I was thinking the same. Maybe EU/US difference. I think the Kaiser has about 4 versions didnt it?
Related
Hey guys,
Had my Nexus for just over a year now, direct from google. i've been flashing roms and kernels for about 6 months, however since upgrading recovery to CWM 3.0 i've had nothing but problems.
Ive downgraded CWM to 2.5 and even switched to Amon RA 2.2.1, still having issues flashing.
Mainly themes, but alot of roms are refuses to flash too. leaving me stuck on the nexus X splash screen when switching on.
i've just flashed to cm6.1 and tried to flash an old theme i used to use, and even that failed. and im completely stumped.
I can only imagine that when flashing CWM through rom manager, it changed some other system files perhaps? Im not going to even pretend i can hold more than my own, hence this post, im stumped. does anybody know what may/could of happened? and what i can do to fix it?
Thanks in advance
http://forum.xda-developers.com/forumdisplay.php?f=603
when you wipe you do a complete wipe, /system, cache and all?
edit:
try and flash the zip from temasek signature.
http://forum.xda-developers.com/member.php?u=2332422
Try reflash the fastboot region on your phone
Sent from my Nexus One using XDA App
so i went to install the newest infected rom with sense 3.0 and was very excited about it. repartitioned my card with RA, wiped, and installed and got boot loops upon sense startup. tried a dozen combinations of superwiping, cache/dalvik wipe, double flashing, fix uid, etc but no luck.
i then decided to try the BOS kingdom rom and get the same problem, boot loops as soon as sense loads. maybe i wasnt destined to install sense 3.0 roms.
ok, so i decide to try KingsROM shift4g blakk rom. its a sense 2.x rom so it should be ok, right? nope! boot loops as soon as sense loads up.
at this point, i suspect its my sd card. i use a 1gb without any repartitioning and try KingsROM again. still same problem. the only roms i can actually get flashed are the latest Fresh and Warm 2.2.
i think the problem may be my phone and not the sd card or rom.
details:
003 with nova panel, S-OFF with unrevoked forever
HBOOT 2.10.0001
RADIO 2.15.00.11.19
i have tried RA 2.3 and CW 2.5.0.7 (the newer version doesnt support some sort of scripting so i use an older version). i also superwipe 2-3x before EVERY flash and sometimes wipe cache/dalvik AFTER a flash.
does anyone have any suggestions on what i should do or try? any input is appreciated and i thank you all in advance.
Those roms all use the same kernel, try flashing the rom then netarchys latest kernel, youll lose cam but I can almost guarantee it will boot.
Sent from my PC36100 using Tapatalk
RileyGrant said:
Those roms all use the same kernel, try flashing the rom then netarchys latest kernel, youll lose cam but I can almost guarantee it will boot.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
wow that certainly stinks since i use the camera a lot. i will definitely try it for the sake of trying. i wonder why it wouldnt be able to handle a kernel especially if its a stock htc one iirc.
superwiped 3x, flashed rom, flashed netarchy kernel, then did cache/dalvik wipe with same results =(
http://www.stupidgifs.com/images/full/75.gif
any other suggestions?
nevermind, I failed to properly read the post.
jesuspgt said:
nevermind, I failed to properly read the post.
Click to expand...
Click to collapse
it happens. it means you need more coffee
Where can I find the download link for the new gb.
Dinc
I'm not sure what you're asking for. Honeycomb 3.0 (which is not available for the Incredible) or Gingerbread with Sense 3.0?
Sent from my awesome sauce Incredible uisng Miui
I think gingerbread with sense 3.0. Sorry.
Dinc
There are several roms with what you are looking for in the development forum.
Oh ok. And do these install the same way. I'm still using the old clockwork recovery.
Dinc
Yes they should install like normal. Check the OP's for the ROM though. All require hboot .92 and CWM 3.0.0.x.
I recommend giving JoelZ's kingdm rewind 3d a go. very smooth
Yeah I'm still using the old cwm and I have never messed with cwm3 so how do I install the new newest cwm.
Dinc
You can use rom manager or you can flash the recovery manually in hboot. Files at www.dougpiston.com
RE: Multiple wipes
http://www.cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.
I only wipe everything once, flash vr superwipe, then flash rom. Works fine on all.
sent from whatever damn rom im using this hour!
k_nivesout said:
Not trying to start a big debate, just pointing out that wiping multiple times isn't doing anything but adding more time to your flashing process. Hopefully this helps.
Click to expand...
Click to collapse
You obviously need to wipe three times and then flash the ROM twice. And reboot about 4 times. One each is not enough. Pull your battery a couple of times as well.
Is installing the new cwm the same as flashing a radio.
Dinc
If you take the time to read what I linked, it explains everything. When you're telling your recovery to wipe, it is a routine run within code. Doing a secondary wipe or even a third is just running the same exact command again. Logically, why would CWM run the same exact command differently, necessitating multiple wipes to get the same result?
There's no "randomness" built into the recovery that would result in the command not being run, or run differently, when you select it.
Its not like a physical action, where the more you wipe, the "cleaner" it gets. Again, it is a routine run within code, and it is not variable or random.
If there was any perceived benefit to the wiping procedure that you mentioned, I'm willing to bet that its due to wiping the /system and /boot partitions, which isn't done when you wipe data/factory reset and wipe cache in the main menu. This is something that should be, and usually is, included in the rom's updater script, but may be forgotten by the dev. Some people have mentioned that recovery version 3.0.0.8 does not work well with AMOLED incredibles. I can't speak for that myself, but in the event that there is a problem, the resolution would be using the 3.0.0.7 recovery, not wiping multiple times.
And I don't think you're correct in assuming that "all the devs" recommend the multiple wipe approach, I think you'll see that plenty do not, including the cyanogen dev who wrote the article I linked to (BTW, he is the one that got CM7 on the Droid X, a phone with a locked bootloader, so I'm assuming he might know what he's talking about.)
That is all..
snapper915 said:
Is installing the new cwm the same as flashing a radio.
Dinc
Click to expand...
Click to collapse
They are totally different, CWM is a recovery, radios are well, radios. They are flashed the same way though (in bootloader).
Awesome. Thanks. I don't have to rename any thing.
Dinc
cvbcbcmv said:
you mean like PB31IMG.zip? No, nothing like that.
Click to expand...
Click to collapse
Sweet. Thanks for everyone's help.
Dinc
folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Verdeee said:
folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Click to expand...
Click to collapse
You're not flashing your Rom correctly. I told you this in Thor's forum (at least the exact post was there also, so I suspect it's you, if it's not you, then accept my apologies ).
The reason it keeps telling you that a certain Rom/kernel is installed, is because it seems like you're just flashing one over the top of another without cleaning anything out. This is why your cpu overheats. You've got a corrupted OS.
Also, a Kernel image is not a Rom. And there are 2 types of kernels. 1 for a stock rom, and 1 for a cooked rom. You shouldn't mix the 2 or you may get problems depending on the rom. Another reason why your cpu overheats.
Do this. Put your SD in your PC's card reader, and format it to Fat32. Reason, is that I have absolutely no idea what you have on your sd. Update.zips, Kernels, Roms, etc.
Copy your VillainRom or Revolver Rom or Taboonay Rom (or whatever rom you want to use) to your SD, then put it back in your 500.
When you flash a new rom, you boot to CWM.
Wipe User Data
Wipe Cache Partition
Goto Advanced and Wipe Delvik
I like to do each a couple of times, just to be sure.
Then go back to the previous menu, and select "Install zip from sd"
Choose your rom and install it.
All three of the above roms come with a cooked kernel so you shouldn't have to mess with kernels.
Also, if you wish to install a different cooked kernel, you only need to wipe Delvik before installing.
Also, Install the rom first and let it run for awhile before installing a kernel. Never do both at the same time.
And the final rule, if you used a backup program like Titanium Backup or any of the others, Never Ever backup and restore system files to a different rom.
But, if you want to put it back to stock, the I suppose you can use the acer recovery tool to flash a stock acer rom and flash the stock recovery image. For more info, see this thread;
http://forum.xda-developers.com/showthread.php?t=1155664
Hi all,
first of all sorry for posting here and not in the EliteMod Thread. But i have to post 10 times and then ........
After flashing the new kernel i´m missing a lot of apps?!?!?!
No matter how i flash (wipe data/dalvik or wipe nothing) the apps are missing. I use dataswap (64mb) if necessary.
The apps i miss are Titianium Backup, Terminal, Gentle Alarm and so on.
I dont know why this is happens. Until now every new kernel or Elitemod Rom was fine.
I normally flash via 4ext recovery, but same via RomManager.
Any tipps or help??
BTW: I really love the work from Nikr. His EliteMod Rom and tweaks are really the best i´ve seen so long.
thx for help and keep flashing :fingers-crossed:
If you did a full wipe and installed a fresh new Rom then course you're going to be missing apps until you re-install them. Or at the very least install the titanium backup app then running a restore for the apps.
Though with a kernel-only flash (i.e.: that new one the other day) you shouldn't be wiping data/etc to flash it.
Maybe a little more details on your problem?
Hi,
thx for the quick respond.
I downloaded kernel zip and put it on the sdcard. After that boot into recovery and choose install zip from sdcard.
Thats was the normal way for kernels. But if i do this now i miss a lot of apps.
I tried to wipe only dalvik and flash, same result. I tried to wipe dalvik/data and flash, same result.
Only changes till the last rom flash i did, was to pull down the LCD destiny from 240 to 210 via Rom Toolbox.
It wouldn´t be such a big deal, but the apps i miss i also couldn´t find in the market. If i search for Titanium Backup nothing appears. Same for Gentle Alarm and so on.
I flash Roms for over 1 year now, but something like that never happend
the change in dpi will affect some apps as "not avalaible" as the are only able to work with certain densities. maybe change this and see what happens
Sent from my HTC Vision using xda premium
Today was a new Kernel Version released and everything is fine now.
Looks like there was a kernel problem with apps on stored on the sd card.
thx for help anyway