[Q] htc evo wifi error - EVO 4G Q&A, Help & Troubleshooting

As title says,
Htc evo
0003
Android version 2.2
Baseband 2.15.00.11.19
Kernal 2.6.32.15 netrchy-toastmod -4.1.9.1
Rom myns warm twopointtwo rls5
Was running android 2.3
With miui rom 1.7.8
With shell 3d
Woke up this morning, went to turn on wifi and nothing happened.
Went to homescreen, pressed menu , settings, wirless, wifi , checked the box
It tried to turn on for ten seconds or so and then said error right under the wifi box.
Made me go
Went to rom manager, loaded last back up (clear dalvik and cache)
No dice..
Flashed new miui rom
Then cm7
Then older miui
Then older cm7....
Then warm....
Flashed 2 dif kernals to fix the problem,
Still, no dice...
Checked xda, android forums, google, craigslist...
I give up
Any help would be greatly appreciated
Just relized bluetooth no worky either

Maybe it's time to try a 100% clean wipe and re-flash.
Give Synergy a shot, because it's awesome (link below) and while you're at it, format and partition your SD card. This will ensure a very clean wipe of the SD (make sure you back up important files onto your computer, like your nandroid backups or CM backups). Wipe the usual cache/dalvik and everything else 3 or 4 times, and then load the ROM up. See if it fixes it.
Synergy: http://forum.xda-developers.com/showthread.php?t=1144447
Formatting/partitioning procedure: http://forum.xda-developers.com/showthread.php?t=1158993

Sell it. Get an HTC HD2.

just did 2 100% clean wiped, i manually wiped everything...
cache
davlik
data
then again manually in recovery settings
flashed said synergy rom,
which by the way is slow,
running an older version of android...
and old sense..
anyhoo, still,, when i check the box for wifi, it tries, then says error..
just tried timat kernal with miui rom<--by far best romm m
next is stock rom and stock kernal, which i cant find :/ go figure

eyeisdasteve said:
Sell it. Get an HTC HD2.
Click to expand...
Click to collapse
post whoreing my thread steve?

Do you have an old nand backup you could restore to? That might be worth a shot.
Both of those issues happened to me once when I used an incompatible kernel with one of my roms, but as soon as I did a nand backup, I was fine.

bradleyw801 said:
Do you have an old nand backup you could restore to? That might be worth a shot.
Both of those issues happened to me once when I used an incompatible kernel with one of my roms, but as soon as I did a nand backup, I was fine.
Click to expand...
Click to collapse
i don't , wish i did...
im stuck...
just put it all to stock and cracked a beer , your move evo

Related

Cm6 & Shadowrom Bootloop after install?

For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972

Weird problem with newly rooted Evo

I just got a new replacement Evo and rooted it yesterday. I installed miui 11.19 rom and set it up. I was planning to use a new memory card, so I inserted it and through amon recov, chose wipe partion, but I don't think that's where the problem happened. At the same time, I went to flash a new kernel the invisible one and also wiped cache/dalvik. After I do that, my phone just stays at the white screen upon reboot. I went back into recovery and tried to reflash the same rom but I was getting a weird error "failed... error at line 4". I put in my old memory card, but had the same problem. I had an old rom that was already on the card that somehow happened to work. I wiped all before I did that.
After that flashed successfully, I tried to flash Myn's RLS4, but it gave me a different E: error. Once again I had to flash an old rom. I don't think it is the memory card that is the problem, but maybe... possibly something to do with the way MIUI is installed maybe? Do I need to reformat? But it did it on a fresh memory card as well. Possibly something went wrong in the rooting process?
What do you guys think?
Wish I could help you on this but I am still new to ROOTing and I dont want to say some thing about something I know nothing about, But I can offer a few suggestions. Try to restore your old ROM. See if you still have the same problems and if you DO, Then logic deduction would lead me to think that its the miui ROM... maybe that ROM and your kernel are not compatible?
Did you flash a kernel or theme before you let the Rom load up or is this happening with just the Rom?
Sent from my EVO at the edge of Hell
If its a newer evo, late 003 or 004 version than your unit has the new camera hardware and will require the latest htc kernel. If the rom you are flashing doesn't use the stock kernel then your phone may not boot up properly or hang at the first screen.

[Q] irc, myn's rls5, toastmod kernal.....wth is wrong

Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
(irc help would be awesome still since I now have some help with main issue- I enter all the correct info into the app but it shows nothin. I've tried several to no avail. I appreciate the help) second I've ran into more pretentious ppl in these forums for Android then others no offense to the good guys but just my exp. It was brash to say that in this post tho. Thank you guys again for the ones willing.
That's because even the biggest idiot can work an iphone.
Jataadroid said:
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
Click to expand...
Click to collapse
Jataadroid said:
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Click to expand...
Click to collapse
Patience dude. I didn't catch it, but what exact kernel are you using, net has a lot of em, the one in the OP of myn's thread you mean? What recovery(and version of that recovery, some versions of clockwork floating around that have some bugs i think) did you use to flash the rom? what radio version and pri version do you currently have installed? Which ROM were you coming from, and did you do a full wipe(data, cache, davlik cache) before flashing it? I have never experienced anything like you are describing whilst using Myn's, his ROMs have been solid. Give a little more info and surely we can help you get running smoothly again.
thanks for the reply heres the details...myn's rls5, net toast havs more, ra_superson
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Looks like we're running nearly the same setup, minus my ra_supersonic 2.2.1 recovery. I have attempted the stock kernel furnished in the Rom zip but since it didn't offer overclock I switched to net havs more smartass. I do the dalvik and cache wipe each time.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
Not trying to be a smart ass but do you realize that by insulting us will not get you any help? Rhetorical question
From reading what you jus stated the obvious problem is you did not do a FULL WIPE as you should do when flashing between roms.
Also next time please be patient as those like myself who browse through this section to help impatient ppl like your self, do actually have a life outside of xda. Its been a big snow storm in the southeast so most like myself included are outside enjoying the snow!
DO A FULL WIPE THEN REPORT BACK!
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
gotta do a full wipe if you are switching between roms
Sent from my PC36100 using XDA App
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Ok. Well crap.... thanks guys since that is apparently my only option.
OneStepAhead said:
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The kernel was included in the op and I've seen tags with same setup as mine.
Jataadroid said:
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
Click to expand...
Click to collapse
Sorry you feel that way but since i have had the hero, on every thread about a rom says wipe all! This must be a joke for someone as rude as yourself to come on here and disrespect those who are trying to help.
Next time you decide to flash a rom remember to do a full wipe because inside the data partition is files for the particular rom, if you dont wipe, the new files will just over lay but not delete the old one. This will cause conflicting issues within the files as the phone tries to do both at the same time.
Screen tearing and the "jigglies" as I like to call it have always come from kernels - in my experience. And just because someone might have the same set up as you, the way it affects your phone ccan be quite different as you are running different apps, different settings, etc.
First thing I would do if I were you is to freeze any kernel govenor you are using - no setcpu, no secreen off profile, no set on boot, no os monitor govenor, no nothing like that. You don't want want any of that going on when you flash a new rom or kernel.
I know you don't want to do a full data wipe so let's see if we cna get you going without that. I used to HATE doing data wipes, I don't mind so much now because I've learned that trobule shooting can frequently take longer than just doing a data wipe.
I would say #1 make sure you are using AMON RA. Power button-reboot-recovery. Wipe cache at least twice, wipe dalvik at least twice. Now JUST flash the rom (you've already said your radios are updated so you wont have a problem with this). Let the phone boot up and give it time to settle in. You wont have any screan tearing. Now you're running a completely stock Myn's rls5 rom. Check some stuff out, make sure your basic settings are good, make sure your 4g is not scanning, etc.
Make a nandroid of this and keep it.
Now start making changes if you'd like. Flash a different font, flash a different kernel, etc. But leave all the governors OFF until you have a kernel that you KNOW will run ok on your phone. For example - I can run 2 of ziggy's kernels but the others don't work for me. I can run a few of net's kernels, but many don't work for me.
So my basic suggestion is to make sure you get a stable, stock Myn's rls5 on your phone before you mod it. If you can't get that, then yes - you might want to wipe data. Doing a batch backup in Titanium is really easy and it makes restoring very easy as well. It's our own customizing that is time consuming because we are all probably very picky (and proud!) of our beautiful phones.
Thanks for the helpful info from ALL that posted. I understand the risk of the non entire wipe, nandroid is safe of original stock Rom but not of new one. After tinkering with setcpu I've gotten more consistent stability. I know I will reflash with an entire data wipe here soon to see results. Running ra_supersonic 2.2.1 recovery.
I've made list of check point when I test some new Roms and kernels. I have some more question on backing up user info from backed up apps but Im sure ill find it on here.
Now that my system is stable for the time being, some one mind help me setup irc? And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it. Ra_supersonic 2.2.1 recovery i like also.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
You're welcome. I am late at getting back to this post, but yea. Definitely. As everyone else has suggested, you have to do a full wipe when changing ROMS. Only time you could get away with just wiping davlik cache and cache is when upgrading the same rom ( like from rls 3 to rls 4, and rls to rls 5), but even then, it doesn't always work. Full wipe is always recommended. I would also recommend downloading your apps one at a time from the market, and adding your mods one at a time, make sure everything is stable after each flash. Good luck.
QUOTE And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it QUOTE
If your phone is the newer hardware (late 003 or 004), you can only use the stock kernel, or a kernel based off stock for the camera to work. That would be htc #15. I believe Net's 4.3 kernels are based off of that. I am also pretty sure that Net explains that in his kernel thread in the development section.
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
r.storm85 said:
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Click to expand...
Click to collapse
This isn't true, the problem is ALWAYS the kernel. I'm running myn rls5 and mikfroyo 4.3 with an SBC #15 v7 kernel (i'll edit post and add the link) and I have had zero issues except I can't download MMS messages on 4g on mikfroyo.
Jataadroid said:
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Click to expand...
Click to collapse
Okay, this process will 100% work. It's the one I've been using since my lowly mytouch slide oh so many months ago.
*before you do this, make sure you have backups of your nandroid and your rsa keys. I'll edit post and give you links on how to back up your rsa keys*
RSA Key back-up: http://forum.xda-developers.com/showthread.php?t=887900 ...since you're rooted you can go straight to the part where it says "if you're rooted do this.."
1. First you need to fix the sd card. Create a folder on your computer desktop and call it "my sd card". Plug your phone into the computer and select "disk drive". Next you're going to copy EVERYTHING from the sd card and place it in the folder on the desktop (and dude I mean everything! AS IS, DON'T CHANGE ANY NAMES). Then, you're going to unhook your phone, go to settings>sd and phone storage. Then you're going to format your sd card. Yes, do it, but make sure you have EVERYTHING backed up first. After that's done, plug your phone back in, select disk drive and copy everything from your "my sd card" folder on your computer and put it back onto your sd card.
*phew*
Okay now that the sd problem is fixed, here's how you fix the rest. You see, when you upgrade your PRI to 1.90 and your radio, etc etc you gotta update the kernel to a version that's 1.90 supported. I'll edit post and post a link to where you can find one OR you can just use the kernel that's included with myn's rom because it WILL WORK. *edit* the kernel I'm using has been taken down because of the witch hunt against SBC kernels. So for now, just stick with stock. It works just fine.
Anyway.
Steps to getting myn working perfectly.
*before starting, re-download myn rls5 in case the screen flickering was caused by a corrupted download*
1. Download Titanium Back-up from the market. Back up all the apps you want to keep (basically, anything you downloaded from the market as you'll get facebook, sense widgets, etc back). You can do this while you re-download the rom.
2. Make a nandroid back-up in case something goes seriously wrong. A rom that flickers your screen is better than a brick.
3. Once that back-up is done, reboot into recovery. Once there, you're going to WIPE EVERYTHING. Full data, cache and dalvik wipe. Yes, do it. There is no other option.
3. Flash myn's rom. Let it go all the way through. Do NOT flash a new kernel until you've found one that's 3.70 compatible and works with PRI 1.90. Myn rls5 is designed to work with the newest updates (which means a #15 kernel, like the one that came stock).
4. Reboot. If the screen is still flickering, then at this point it's a hardware problem. Flash back to stock, unroot and go get a new one. If it works fine, re-download titanium back-up from the market and restore all your apps. From there it's just putting your widgets back on your home screen.
From here, you can search the forums for a kernel that works with the newest updates. If you read them, they'll tell you what they're compatible with. Remember do NOT use an AOSP kernel with a SENSE rom, that's just spells IDIOCY. Until you find a kernel that works, stick with the one that came with the rom because everyone knows that one works.
I hope this helps. As for the IRC chat, not all the experts are on all the time. If no one is online that can help when you get one, try getting a few hours earlier or a few hours later.

[Q] Can't boot Myn's RLS5...

I'm coming from CM 6.1.2 and have done everything correctly to a freaking T. Has anyone had any problems getting stuck at the Splash screen and getting passed it? I can flash any other Sense ROM just fine but Myn's always gets hung at the Splash screen no matter what radios, kernels, PRIs, etc... Getting frustrated. I spent like six hours yesterday trying to get it to boot.
What recovery are you using? and do you have the newest update from Sprint (radio, prl)
Newest RA... I have every new radio, PRI, NV, Wimax...
Did you wipe everything more than once before flashing the Rom?
I wiped everything via Amon's built in options and Calk's format all .zip.
Did you have any problems updating with Calk's format all .zip?
As long as I'm flashing something other that RLS5 it works great.
Re- download Myn's Rom again. I know it sounds crazy but the download must be corrupted.
Done that, too... It flashed fine on my friends newly rooted EVO. I know that download wasn't bad because we used the same one. Thinking about running an RUU and starting over.
The best one will be the Sprint lover ROM as pcm36img.
I'd have to use that since I run Linux... don't know of an RUU that works on Ubuntu.
okay. report back if it work for you.
DO you know of a root method I won't need to hook my phone up to my computer with? I kinda don't have my cable with me at the office.
rom is already rooted.you can download it to you're phone, weather you are on wifi or 3g/4g.
And are you rooted?
No... if I run a RUU I won't be rooted anymore.
Nope! You will not loose root!.try it out, thank me later
I don't see what harm it could cause... I'm DLing the one you posted in that other thread.
Report back.
Make sure that the file is a pcm36 img.zip and that its in you're sd card.
evolishesh said:
Make sure that the file is a pcm36 img.zip and that its in you're sd card.
Click to expand...
Click to collapse
My phone recognizes it and starts to load it then stops... is there another one?

[Q] Error flashing MikG?

So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....
So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.
I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?
Gonna try and flash my old Deck 1.3d rom and post back with results
Naturesretard said:
So I was having issues with MikG and my settings.... Reinstalled aosp system apps by accident over sense system apps and it kept popping up with error messages....
So I wiped everything and reflashed MikG 3.xx and it boots up... But all I see is the wallpaper and status bar. I see no clock/apps, and am never prompted with entering my google info and whatnot.
I also deleted the ROM and put it on again thinking it might be corrupt but I still get this problem. Wtf just happened? Did I just brick my phone?
Gonna try and flash my old Deck 1.3d rom and post back with results
Click to expand...
Click to collapse
did you factory reset wipe?
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.
Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
Naturesretard said:
I factory reset from within amon ra and wiped each thing individually as well. Flashed the full wipe version of MikG 3.11 and it proceeded to wipe everything again. Everything installs fine, but when it boots, it just shows the MikG walpaper, and the notification bar. No apps, no clock, no new user "welcome to android" prompt either. All I can do is turn the screen on and off.... I have to pull the battery to turn the phone off.
Putting my Deck 1.3d nandroid on my sd card as I type and am going to flash in just a minute to test and see if I can even boot anything...
Click to expand...
Click to collapse
You sure you got the FULL WIPE version? If you flashed the UPDATE version you will get these exact same problem.
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....
But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
Just restored my Deck 1.3d and its booting as I type. Will post back with details.
Naturesretard said:
I got both.... originally thinking it was an update TO the ROM itself. (idk why lol) Decided to keep it for if I ever have to reflash the main rom due to a user error....
But no, I made sure I was flashing the full wipe version. You think I should redownload again and try it out? I had the file saved on my friends laptop and hadn't touch it since I put it on my SD card so.... figured I could just delete the one on my SD card and retransfer
Click to expand...
Click to collapse
I'd do a complete wipe on everything and start from scratch. I just got a new SDcard and formatted it and did a fresh install of MikG 3.11 and it runs like no other.
Back up your SDcard to a PC and format and start fresh. I noticed a HUGE difference in function and performance although it sucked loading almost 10gigs of music back on.....lol
you think it might be an error on the sd card like a bad sector?
Just booted back into Decks.... Although the backup of my sd:ext didn't take apparently and it's stock Decks.... Kinda odd; No apps or anything. Or is that supposed to happen? Same wallpaper though....
Gonna try and reflash MikG and if it still doesnt work I'll follow your method. Would rather not as I did that a few months ago when I partitioned my SD card for a2sd lol...
Will post back with results
Redownloaded and flashed MikG full wipe. Its good now. Thanks to you anyway.

Categories

Resources