Related
I've noticed that not all roms put what spl we should have, so is it safe to assume that 1.33.2005 good for the rom?
The rom I'm looking at is http://forum.xda-developers.com/showthread.php?t=574526
Yes! Tried it myself
I think it's good for all roms, actually it might even be a prerequisite for all hero roms except micro hero.
Not 100 % sure of the latter though.
I just tried flashing the hero rom and it flashed just fine but after it got passed the mt3g splash it just repeated the hero and htc splash, I'm back on cyanogen, any ideas on how to get it working?
Did you wipe before you flashed? Also, the first boot can take a few minutes.
If it's neither lack of wipe or lack of patience I have no idea
It's lack of patience lol. I'll try flashing it again and wait this time.
Okay, well it's not lack of patience unless waiting 1 hour isn't long enough. Any body else have some ideas to get this working?
Kaptur mentioned it, but did you wipe before applying the update.zip ?
Yes I did.
Then I recommend you try another ROM, maybe evil D:'s sense/nano sense as apparently thats quick/stable.
it has to be a bad download or you need to wipe a couple more times I've wiped and it still did a boot loop before so try wiping at least3 times and /or try a new rom
I flashed 2 different heros after that, 1 of them i got the splash loop and evil's worked.
I usually find if a wipe then flash doesnt work, I just repeat the same procedure i.e pull battery, wipe and reflash then boot does the trick.
If all else fails repartition card and then flash, and if that doesnt work, i guess that rom isnt for you.
Im having this problem with nano sense.
I always wipe completely and recreate all partitions if im running a hero rom
Wouldn't recreating the partitions get rid of my apps? If not, I might try that.
Hi Peeps,
I have searched in vain for a guide to changing from cm 4.2.15.1 to super d stable, but I cant seem to find one.
can someone advise me what to do so I dont brick my phone, and is it really worth moving to super d I hear its faster.
I am running cyanogen 4.2.15.1 H&E red I have the ra-dream 1.5.2 recovery, I have ext2 partition on sd card and I have a PVT board
Also I am worried about the ext2 partition because I have heard you have to remove it first and there is a certain way to do it??
Thanks in Advance
I was able to flash SuperD over Cyanogen without wiping or repartitioning. This is with an sdcard partitioned the usual way, fat32 and ext2.
The only issue I ran into was the battery meter - had to remove /data/system/batterystats.bin. Not sure of the exact procedure, so I did that from the recovery console and then booted up with a full charge.
Works great and really is a lot faster.
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
nmw407 said:
I would always wipe when moving from one rom to another. You never know what's could be hanging around.
I go thru this same process every time and never had problems:
1. Nandroid or Bart backup
2. Copy backup from SDcard to PC just in case SD card gets corrupted somehow
3. Wipe
4. Install new rom
5. Fix apk mismatch
6. Reboot
7. Check to see if Gapps are working, namely market, talk, sync, and of course google voice
Click to expand...
Click to collapse
5. When you say "fix apk mismatch"....what do you mean?
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
shuboy00 said:
5. When you say "fix apk mismatch"....what do you mean?
Click to expand...
Click to collapse
It's an option in Amon_RA's recovery
shuboy00 said:
7. I did the same thing (went from Cyanogen to SuperD) and I can boot into SuperD fine, but it won't connect to T-mobile's network and I am missing the Market. Any help?
Click to expand...
Click to collapse
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
mejorguille said:
It's an option in Amon_RA's recovery
Wipe, Flash the DRC83_Base_Defrangled, the flash SuperD. Since both are legal, they need to pull the google apps from the base. And you would probably be fine without a wipe from SuperD to CM since they are similar donut builds. Wipes are recommended if you go from eclair to donut (and donut to eclair, elcair to sense, sense to dount.....). Cyanogen fixed it so you don't need to wipe as in the olden days...
Click to expand...
Click to collapse
I see. So I am already running the DRC83_Base_Defrangled. Here is what I am doing:
I am currently running Cyanogen 4.1.99. My build number is DRC83. But my model number says "Android Dev Phone 1" <-- could that be why I don't have the Market in my roms?
So anyways this is what I do from Cyanogen 4.1.99: I backup, wipe, flash the DRC83, flash SuperD, then flash the 26I radio. Like I mentioned, rom boots up fine, just no market and no network access. Am I doing something wrong?
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download this. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
mejorguille said:
You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
b0ricuaguerrero said:
i believe he said that he is running latest cyan rom. try backing up your fat32 partition and reformat, that should do the trick
Click to expand...
Click to collapse
I was referring to the poster above my post
mejorguille said:
Absolutely no reason to flash the radio. The only thing that I can think of is that you have a bad download? Download <removed>. Go to recovery, backup, flash the base, flash the rom. That should be all you have to do. Also, try CM 4.2.15.1 if SuperD isn't working for you. You are using a version of cyanogen about 4 months old and there have been 20 something releases since.
Click to expand...
Click to collapse
K. Did what you said. Downloaded the base you provided. Flashed. Then flashed the SuperD rom. Booted up. First I see is "!Sorry - The process com.google.process.gapps has stopped unexpectedly. Please try again." Still no network and still no Market. Urgh. Frustrating!!
Also, I tried CM 4.2.15.1 after the SuperD didn't work and it hung on the G1 screen. IDK why 4.1.99 works but not 4.2.15.1.
i guess it didnt hung, you just have to wait a bit longer.
Ive got the following on the HBOOT screen
GLACIER PVT ENG S-OFF
HBOOT=0.85.2007 (PD1510000)
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010, 12:44:14
Clockwork v3.0.0.6 (using this method http://forum.xda-dev...ad.php?t=944681 )
Okay so with that for reference, I'd like to find out why I can't flash CM7 without the blue Andy bootloop. I understand that a fresh install takes time to load, I gave it 30mins before a battery pull, I then returned the battery, hit the top power button and let that sit for another 20. Before I flashed the ROM (through recovery) I made the following wipes in this order; wipe data/factory reset and then wipe cache partition. I've flashed other ROMs that have flashed without issue (Ice Glacier 1.1.6 themed and Royal MIUI) but, lets face it CM owns. Any help would be appreciated. Thank you for reading this.
DHSdrone said:
Lets face it CM owns.
Click to expand...
Click to collapse
No, Sense owns.
With that out of the way, the only thing I can think of is a corrupt download. Try re-downloading the zip to your PC and copying it to your SD. My other thought was a bad recovery, but since you've successfully flashed other ROMs, that doesn't seem likely.
you didn't wipe dalvik in advanced, do that and bootloop will stop...
darinmc said:
you didn't wipe dalvik in advanced, do that and bootloop will stop...
Click to expand...
Click to collapse
Little known fact, if you wipe data, you already wiped dalvik.
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Mmmhmm, the only thing it could be is bad download or some other mysterious gremlin lol
Sent from my HTC Glacier using XDA Premium App
option94 said:
Little known fact, if you wipe data, you already wiped dalvik.
Click to expand...
Click to collapse
Well then I retract my statement...
when you say bad or corrupted download I assume your talking about the recovery. I thought the same as well, Ive tried both versions of what was posted as the correct, best, and or easiest method of clockworkmod recovery. Im not sure if both versions were in fact the same recovery.img but they both worked for the roms Ive flashed except for cm (nightly 29, cm7-rc2, rc3,and rc4). The fact tjat I cant get this to work, only makes me want it more.
DHSdrone said:
when you say bad or corrupted download I assume your talking about the recovery.
Click to expand...
Click to collapse
No, I mean the CM7 download. The actual ZIP file that you flash.
As far as recovery versions, only 3.0.0.5 and 3.0.0.6 can flash CM7.
Ive tried flashing several different versions of cm7, starting with rc-2 through rom manager. When that gave me my first boot loop I went back to the method I was more familiar with. With trying the different versions I don't see how they were all currupt or broken downloads. I haven't tried any of the cm froyo roms yet.
As far as my earlier statement of "cm owns" I mean no disrespect of any of the other rom developers (including those that did work properly the first time). Ive just came from the G1 and cm is the only rom I ran. Sense may be the best way to go, it's not something Ive given much consideration or time.
I have had the same issue except mine seems to be all 2.3 (Gingerbread) based roms, they all go to bootloop. I have no problem however flashing any of the 2.2 based roms. I also have cwm 3.0.0.6
I had the same issue everytime with different nightly releases. After wiping everything and formatting boot and system still would do it. I found if you wipe then install cm7 only the phone boots fine then reboot setup wifi if your using it the go back into recovery install gapps and it works fine.
Sent from Teh retardarded duc using XDA Premium App
Im unable to get a full boot. After reading several similar sorties I've always turned off all wireless radios. Will post a logcat later today.
Ok so was able to get mine to Boot completely Finally!!! I am somewhat of anoob so sorry if it seems confusing.
1.From recovery wipe data/ factory
2. Wipe cache
3.Advanced > wipe dalvik
4.Mounts>format boot
5.Mounts>format system
6.Advanced> partion SD card (I believe I used 256) No swap partition(dont know if it matters)
7.Mount USB and transfer cm7 and Gapps
8.Flashed cm7 only not apps.
9.Reboot phone (should boot all the way up)
10.Go back to recovery and flash Gapps
11.Reboot phone
My phone booted up very quickly. I hope this helps anyone else out there with the same issue
no more loop da loops
After searching google, and then to various forums, and finally giving up and posting to 2 separate forums, Ive come to say THANK YOU !!! You are all evil geniuses of the highest degree and I bask in your greatness. Ive been overlooking one thing, that is the "if things go bad, try the sd-card format" well I did and it worked. Now that the derp has left my head, and the panic has subsided I can see now that my problem was in fact like many others, and the answers were right in front of me. Again thanks for being patient and coming together as a community to help me out.
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
ok my evo has been messing up alot lately. it all started with the front camera like 2 weeks ago the front camera does not work at all and certain roms will not boot. i flashed roms almost every week and always superwiped and everything. i am using Amon RA 3.11 right now i am running MetrogenMod (CM7). Yesterday my phone was in a bootloop that would only boot at the splash screen and reboot over and over again. It became a "usb brick" and it wouldnt detect the sd in recovery but i was able to fix it using adb in fastboot with this guide. flashed the rom all over and now its working except for the ffc. i think some of the files in the internal memory are corrupted but i have not been able to find anything to fix it. i have flashed many roms, RUU, updated radios. i am running out of ideas. Can anyone help me?
my phone:
s-off
revolutionary
Hboot 6.16.1002
radio: 2.15.00.0808
HW: 004
by the way the roms i can run are: Radiance(sense 3.5), Energy (sense3.5) MIUI ICS, CM7.1, CM7.2 rc1, Metrogenmod, stock, 4korners,
this roms only boot up for 3 minutes and then reboot over and over every 3 minutes (yes they boot correctly but as i am trying to set it up it reboots): MIUI GB, rainy day, TN shooter rom for evo 4g
Try doing a fresh install with re formatting your sd card as well. Use Amon Ra to format sd and upgrade to ext 3.
Of course back up what you want on sd, but remember, not all data transfers from one version of android to another well. i.e. app data from gb won't function well on ICS and the opposite too.
Though ultimately, it could be a hardware failure. In which case take out to Sprint and get it replaced... That is about all you can do at that point.
Sent from my PC36100 using xda premium
imheroldman said:
Try doing a fresh install with re formatting your sd card as well. Use Amon Ra to format sd and upgrade to ext 3.
Of course back up what you want on sd, but remember, not all data transfers from one version of android to another well. i.e. app data from gb won't function well on ICS and the opposite too.
Though ultimately, it could be a hardware failure. In which case take out to Sprint and get it replaced... That is about all you can do at that point.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
well i already did that many times, i wipe everything 3 times manually, format the sd card, partitioned it, and all that but it still has that problem. since i dont have sprint (im flashed to metropcs) i will just look for another evo