Related
when i try to restore my nandroid it says error flashing boot image please help
That happened to me once. I think the actual file was corrupt because I was able to restore from a different nandroid. Do you have any others saved that you can try?
I don't remember that exact error message (I actually think it might have been different), but a very similar (or identical) error can occur of on backup/restore you have a low battery, low disk space or have renamed the directories.
What recovery are you using?
Do you have other backupsyou can try?
Are you trying to restore a clockwork backup with ra, or an ra backup with clockwork?
Sent from my blah blah blah blah
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
rcbarr said:
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
Click to expand...
Click to collapse
Wait, what?
It's not like you have a choice to do one or the other, nand and titanium do totally different things. You should always do a nand backup before flashing anything, regardless if you use tb...unless I misunderstood what you're saying...
Sent from my blah blah blah blah
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
DaKlown said:
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
Click to expand...
Click to collapse
OP didn't give as much detail as you - good example of how details help.
You can only restore backups you made with the same version of hrboot. You can't restore a .79 backup while running .76 (which I'm pretty sure is what you downgraded to in order to load cm6).
Now I need to find flashable zips of both hboots so I can switch between cm6 and sense. I so miss my 4g lol. Thanks for your help!
I upgraded hboot to .79 and still got the same error. Funny thing is that my cm6 loaded fine and my hboot is still reading .79 anyone have any clue as to why sense wont load and why cm6 loaded on a different hboot?
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
potna said:
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
Click to expand...
Click to collapse
You are doing exactly what I am trying to do, and ran into the same trouble.
Seems like having to run unrevoked again is unnecessary. There must be a way to switch the boot loader without it ? Did you ever find a quicker way?
I feel pretty comfortable messing with this stuff, even though I am new to the EVO. That said, I really do not want to brick it doing something stupid. Messing with these boot loaders does scare me a bit.
potna said:
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
Click to expand...
Click to collapse
I'm having the same problem, but I don't have the luxury of either Sense or Cyanogen working--I'm just permanently stuck inside the ClockworkMod Recovery and can't get back to a nandroid restore point I've verified in the past as working.
Is there something I can do to remove the pc36img.zip file? How?!
I have amon_ra and I ran into this issue a while back too. You most likely got this error due to your battery level being too low. Turn your phone off, charge the battery for a while and try again.
http://forum.xda-developers.com/showthread.php?t=705026&highlight=%5Brecovery%5D
Near the top of his post it states your battery must be atleast 30%, in red text.
Sent from my HTC Evo 4g
Hey all
So i searched and saw people with slightly similar issues, but not the same as mine.
I was hoping anybody could help.
I was having small issues with the rom i was running (CM) and decided to wipe all and go back to a nandroid i had of a previous ROM (Myn 2.2).
I wiped all through recovery and tried to load the Nandroid. It got stuck at the white HTC Evo 4g load screen.
I pulled battery. Went into recovery. Reloaded a seperate Nandroid backup (one that i had restored before with no issues) and had the same issue.
I then went back into recovery, wiped all, and did a fresh install of the Myn rom zip on my SD card (one that i had loaded before and knew was okay). Once again...stuck at the white loading screen.
So here i am. Recovery works, but i absolutely cannot get any ROM's or Nandroid backups to work after restoring/installing. Constantly stuck at the white screen.
Any ideas? I've flashed my phone a million times and this is the first time this is happening.
Thanks in advance everyone.
okay, quick follow up.
I reflashed CM6 and am able to load ONLY CM.
Seems really weird to me. Any ideas why I am unable to get back to other ROMs? I did recently update to the most recent Radio...that's the only physical change to my phone that i made that i can think of.
Thanks again. At least i have a working phone.
I had this issue, RLS4 is based on the 3.30 release. I had to downgrade my NV, PRI, Radio and WiMax to get it running.
You can grab all of these here:
http://forum.xda-developers.com/showthread.php?t=715485
EDIT: Make sure you flash one zip at a time here. I'm not certain if it's okay to do them all at the same time, but I generally hear that can cause issues. It'll ask you to reboot after each one. If you use Amon RA, it'll just reboot into recovery again, not sure about Clockwork.
I was also surprised that my nandroid backups of Myn's from before I flashed 3.70 software update didn't work/revert my software back to 3.30.
sidepart said:
I had this issue, RLS4 is based on the 3.30 release. I had to downgrade my NV, PRI, Radio and WiMax to get it running.
You can grab all of these here:
http://forum.xda-developers.com/showthread.php?t=715485
Click to expand...
Click to collapse
Cool, i'll try this and report back.
Any idea which ones i should specifically downgrade to?
thanks
bweisholtz said:
Cool, i'll try this and report back.
Any idea which ones i should specifically downgrade to?
thanks
Click to expand...
Click to collapse
I downloaded these ones and flashed them in this order. Each time I'd try to install the ROM after flashing. I didn't successfully flash until after the NV. If I was a good troubleshooter, I would've tried to narrow it down here. Sorry, I'm not sure if it's necessary to downgrade one or all.
EVO_WiMAX_26023_R01
EVO_Radio_2.15.00.09.01
EVO_PRI_1.77_003
EVO_NV_1.77_003
I didn't mess with HBOOT, I was able to install the ROM after I flashed the NV.
I have a same problem
stuck on the white screen, triyed to run the pc36img.zip and its says no image
then I went to recovery it only allows me to run a zip file...What can run as zip
file to get this to load my rom and I dot have nanroid either...
Any help/advise is apprciated!!
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
I struggled with my phone for three days trying to flash roms recently. At one point I went to an older version of CWM 3.0.0.5 and it worked once, but then it stopped flashing again.
Tried Amon_Ra and didnt have any luck either due to signatures or something. Went back to CWM 3.0.0.8 and havent had any problems since. CWM must be messing up every once in a while or something.
Good Luck
Sorrows said:
Hey guys, I was wondering if you all could help me with an issue I've been having lately.
For some reason, I can't flash any ROMs. When I do, it hangs and hangs and hangs on the Splash Screen. It hasn't always been this way, everything worked just fine until last month I flashed MIUI. It worked, but after I decided I didn't like it, I couldn't flash any new ROM, and none of my backups worked until I wiped data and what not.
I've reformated my SD card, and I still can't flash any new ROMs. Help?
I'm kind of worried that if I decide to flash the stock 2.3 update when it comes, I'll brick my phone.
Click to expand...
Click to collapse
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
MojoRisin011 said:
I've had the same problem then someone suggested I flash a temporary 2.x clockworkmod to whipe bc clockworkmod 3.x has reported issues of not wiping completely.
Here's the zip I used, flashing will temporarily give 2.5.1.2. When you reboot, it will be back to whatever you had before. Also try repeatedly wiping data, cache, dalvik 3x or more. Hope this helps
http://forum.xda-developers.com/attachment.php?attachmentid=549325&d=1300835217
Click to expand...
Click to collapse
And that could cause it to hang on the Splash Screen?
Sorrows said:
And that could cause it to hang on the Splash Screen?
Click to expand...
Click to collapse
I'm just speaking from personal experience.. it can't hurt.
Is your hboot version .92?
Sent from my ADR6300 using XDA App
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Sorrows said:
INCREDIBLEC XD SHIP S-OFF
HBOOT-0.92.0000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
And it could hurt actually, because it is incredibly difficult for my phone to restore even.
Also, I can't flash the alternate recovery for some reason. Every time I try, it says there was an error.
Click to expand...
Click to collapse
You know.. its interesting that you mention this..
I have been following the CM7 nightlies for a while, and got fed up at one point and just stuck with one of there nightlies. Well... I noticed I couldn't flash ANYTHING at one point. Couldn't upgrade the kernel, radio, ROM... it would all cause it to hang up at the boot screen. I had to get EVERYTHING back to exactly how it was and then restore the most recent image I had created. It's the only thing that will work on my phone as of now. I wonder what happened, I feel like the phone lost its writing ability or something..
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Hypcrsy said:
I had a similar problem a while back. I had a 2GB laying around as a spare, made sure it was formatted on my comp FAT32 and then put whatever ROM I wanted on it and tried it from there. It stopped the looping issues I was having. So I saved all my stuff from my daily SD card (16GB) and formatted that and put it back in the Inc and I haven't had a problem since. Maybe try a new SD?
Click to expand...
Click to collapse
Your right, I think I'm going to try another SD card... or back this one up and format it...
But the weird thing is I can flash tweaks to the ROM, but I can't change kernels, ROM, radio.... without it getting stuck on the splash screen...
But I'm gonna go ahead and try another SD, because I had another SD that messed up on me, and it gave me similar issues. I just haven't had any problems with this one... so yeah.
If that doesn't work, you might try doing an RUU completely back to stock. then try flashing a new ROM.
Good luck!
Recently was running Synergy Rc1- non god mode, changed to MIUI, wanted to nandroid and lost root.
Was running Synergy RC1-nongodmode
-made a nandroid backup
-wiped / everything 2x
-mounted sd card
-flashed MIUI 1.8.5
Setup MIUI 1.8.5
-logged into market
-re-synced gmail
-rebooted
-downloaded rom manager
-flashed into recovery, to make nandroid
got stuck in boot loops, similar to thread
http://forum.xda-developers.com/showthread.php?t=1208084&page=2
however, after making an attempt to use the latest unrevoked,
my phone will flash the pcimg36 stuff, and I actually CAN get into
clockwork, but i get unable to mount SD card errors, when trying
to flash ANYTHING, however in bootloader, it has no problems
at all, and I know my SD card is good.
So i go into bootloader, to get my stats, and my S-OFF,
is ACTUALLY now S-ON!!
This is an evo thats stood the true test of time, from the day that it came out, until 3 days ago, this beast is in perfect shape.
I used the original 53 (maybe 83?) step root process, far before unrevoked.
And even worse, between hundreds of bootloops, after pulling battery, about 5 times, it actually boots into MIUI 1.8.5, but it ALSO cant mount SD card.
I have also tried several other SD cards, just FYI.
can ANYONE put me in some decent direction?
Normally i got this aced, i have no idea whats going here.
Hboot 0.76.2000
Radio 2.15.00.09.01
EVT2-3 ENG S-ON
Thanks! for the love of god
have tried fastboot stuff to oem qxdm stuff to try to get USB back, and still nothing.
Ive flashed Ruu, and no USB support while in on the phone!
again the fastboot stuff didnt help,
I tried manually flashing a radio through fastboot and get mismatch errors, assuming im trying to flash the wrong radio or something.
please, anyone, help.
im all ears, and have been reading non stop the past 2 days.
anything could help me now.
Hi,
I spent more than half the day reading about a problem I am having and just getting acquainted with the terminology and I'm a little burnt out. Here is my problem:
Dropped my phone in water while it was on. Immediately disassembled, flushed out with tap water, then force flushed with alcohol. Board dried out nicely, but had to replace screen & LCD because I cracked it while trying to pry it apart to get the water out. Replaced screen, reassembled phone.
Now it works partly, and I am thinking the OS is somehow corrupted because it is behaving weird. I need a way to re-install the OS without doing a “factory reset”, is that possible. Is that what the factory reset does, like re-installing a fresh copy of windows on a screwed up machine?
Quirks:
1) errors:
a) Process com.android.phone is not responding
b) Application Settings (in process com.android.settings) is not responding
c) The application Sprint Connections Optimizer (process com.smithmirco.mnd) has stopped unexpectedly. Please try again.
2) High current draw, phone now gets warm, drains the battery in 2 hours. new battery.
3) Bluetooth and Wifi won't turn on (widgets or in setting), but “Sprint Retail Diagnostics” says that they are ON.
4) All else works fine on phone!
Previously the phone was switched over from Sprint to a local carrier Mobi PCS (Hawaii). He used a program called Flash To Talk Android Studio when switching the phone over. Phone was not rooted. Everything was working perfectly before, never had an issue.
Anyone know how to repair the OS?
Here is all the info I was able to collect:
EVO 4G Model: PC36100
MEID: xxx
IMSI: xxx
Hardware Ver: 0003
WiFi MAC: unavailable
Bluetooth Adress: unavailable
4G MAC: unavailable
HBOOT: 2.18.0001
Android ver: 2.3.5
BaseBand ver: 2.15.00.12.19
Kernel ver: 2.6.35.10-g94d0005
[email protected] #1
Mon Mar 12 19:29:30 CST 2012
Build #: 5.07.651.1 CL356670 release-keys
Software #: 5.07.651.1 710RD
Browser: WebKit/533.1
PRI ver: 2.33_003
PRL ver: 10602
When entering HBOOT, this would flash on the screen momentarily and dissapear:
SD Checking.
Loading PC36DIAG.zip
No Image!
Loading PC36DIAG.nbh
No Image or wrong image!
Loading PC36IMG.zip
No Image!
Loading PC36IMG.nbh
No Image or wrong image!
THANKS!!!!!!!!!!!!!!!!
The hboot messages are standard. Once hboot starts its going to look for a pc36img.zip in the root of your SD card. It hasn't found one. That's fine. Not an error.
Are you rooted? What recovery are you using? If amonra, I would try fixing permissions, clearing cache/dalvik then rebooting.
fitz420 said:
The hboot messages are standard. Once hboot starts its going to look for a pc36img.zip in the root of your SD card. It hasn't found one. That's fine. Not an error.
Are you rooted? What recovery are you using? If amonra, I would try fixing permissions, clearing cache/dalvik then rebooting.
Click to expand...
Click to collapse
I have read that " try fixing permissions, clearing cache/dalvik then rebooting" in other threads, but I am not rooted. My main concern is no more OTA update support if i root it, but i guess i could install those manually?
So is my best shot root the device and do the above?
No custom recovery, the phone is basically stock except for the change over to Mobi PCS from Sprint. BTW- does that mean that the phone has a custom ROM now?
Thanks for the swift response!!!
No not really. If the phone was flashed to a different carrier, then it just has new info as to how to contact towers an such. That has nothing to do with the rom itself.
If your current rom is hosed, then you have nothing to lose by rooting and installing something else. If you like stock, there's lots of stock rooted roms here.
Start at the rooting process and go from there
Sent from my PC36100 using Tapatalk 2
cbucz24 said:
No not really. If the phone was flashed to a different carrier, then it just has new info as to how to contact towers an such. That has nothing to do with the rom itself.
If your current rom is hosed, then you have nothing to lose by rooting and installing something else. If you like stock, there's lots of stock rooted roms here.
Start at the rooting process and go from there
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
That's pretty much what I was going to say.
fitz420 said:
That's pretty much what I was going to say.
Click to expand...
Click to collapse
Thanks guys, appreciated.
My main reason for not wanting to go with another ROM was that I would need to re-flash the Mobi-PCS info in there and he would charge me another $35. I'll talk to the guy and see if he can work with me.
Where is a good place to see all the ROMs in action? Youtube?
Oh, and can I install a new kernel without changing the ROM? I am thinking the kernel is corrupt because it controls the hardware, and my Wifi and Bluetooth don't work, and I get excessive current draw. I am really curious to find out if fixing the software will fix the hardware issues. I'll let you know how it plays out.
jivenene said:
Thanks guys, appreciated.
My main reason for not wanting to go with another ROM was that I would need to re-flash the Mobi-PCS info in there and he would charge me another $35. I'll talk to the guy and see if he can work with me.
Where is a good place to see all the ROMs in action? Youtube?
Oh, and can I install a new kernel without changing the ROM? I am thinking the kernel is corrupt because it controls the hardware, and my Wifi and Bluetooth don't work, and I get excessive current draw. I am really curious to find out if fixing the software will fix the hardware issues. I'll let you know how it plays out.
Click to expand...
Click to collapse
Trying to root the phone, but ran into a little roadblock.
Was following the procedure at HTCDev.com to unlock the bootloader, and when i entered this:
fastboot oem get_identifier_token
I got this error:
(bootloader) [ERR] Command error !!!
OKAY [0.009s]
finished. total time: 0.010s
I verified the phone said "FASTBOOT USB". Had all the drivers installed, the 3 files in c:\android.com, etc..
suggestions?
jivenene said:
Trying to root the phone, but ran into a little roadblock.
Was following the procedure at HTCDev.com to unlock the bootloader, and when i entered this:
fastboot oem get_identifier_token
I got this error:
(bootloader) [ERR] Command error !!!
OKAY [0.009s]
finished. total time: 0.010s
I verified the phone said "FASTBOOT USB". Had all the drivers installed, the 3 files in c:\android.com, etc..
suggestions?
Click to expand...
Click to collapse
Another question. I am not familiar with this terminology so really wouldn't know what to search for, but can i copy the setting that made this Sprint phone into a Mobi PCS phone? If i have to do a factory restore or change ROMs on this phone, i want to be able to flash the Mobi PCS setting back in by myself w/o having to go back to the dealer, is that possible?
thanks!!!
The stars have aligned tonight. I removed crap from my SD card and went from 1.4GB to 2.54GB free, I repeated the same steps as last night, and now it works. I copied the Identifier Token, all is well!
Thanks for the hand holding. I am sure I'll need some more along the way.
jivenene said:
The stars have aligned tonight. I removed crap from my SD card and went from 1.4GB to 2.54GB free, I repeated the same steps as last night, and now it works. I copied the Identifier Token, all is well!
Thanks for the hand holding. I am sure I'll need some more along the way.
Click to expand...
Click to collapse
So here are my results.
I followed a guide by ocnbrz on AndroidForums.com (Awesome BTW), and ended up going with the MikG 3.1 ROM and Anthrax Kernel.
Long story short, same issues with the phone:
Slow boot, quick battery drain, no wifi/bluetooth, no spk/mic.
I am so very bummed, I guess that means I have hardware damage, unless anybody has any last ditch suggestions for going deeper into kernel/hardware issues.
One curiosity, after doing all those cache and Dalvik wipes, and bootloader unlock (which i thought wiped the phone), I still have alot of old background pics on the phone. I think its because they are stored on SD card?
BUT, why are my Mobi PCS settings still in the phone? it connects to Mobi PCS network, i just have no sound, but i do have 3G. I would think that doing all that to the phone, new ROM and Kernel, all the previous configs would be erased. Why are they still there?
Jive
The carrier you got flashed to is in a completely separate partition on the phone. When you flash a rom, it doesn't touch the other part.
As for why other things aren't working, its hard to say...it does sound like actual hardware damage. Sorry for your luck.
Just out of curiosity, which recovery did you choose?
when you wipe and installed the custom rom, I assume you wiped everything? A bad flash can cause all kinds of errors and quirks.
I always use the 3x wipe, then also wipe my sdext too since I'm also using that.
AOKP anything
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
Also, if the guy who flashed it told you installing a custom rom would break it, he lied and he's trying to get more money.
In future ventures to the cell phone place, you may want to choose a different dealer.
AOKP anything
cbucz24 said:
The carrier you got flashed to is in a completely separate partition on the phone. When you flash a rom, it doesn't touch the other part.
As for why other things aren't working, its hard to say...it does sound like actual hardware damage. Sorry for your luck.
Just out of curiosity, which recovery did you choose?
when you wipe and installed the custom rom, I assume you wiped everything? A bad flash can cause all kinds of errors and quirks.
I always use the 3x wipe, then also wipe my sdext too since I'm also using that.
AOKP anything
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
Also, if the guy who flashed it told you installing a custom rom would break it, he lied and he's trying to get more money.
In future ventures to the cell phone place, you may want to choose a different dealer.
AOKP anything
Click to expand...
Click to collapse
Interesting... The Mobi guy actually said "there are 4 settings to change to Mobi from Sprint, sometimes when you flash a ROM, 2 of those settings get changed, sometimes they don't and the phone will still work" I don't know any better so I believed him.
Before flashing the ROM, I did a wipe with Amon Ra 2.3, cache, Dalik Cache, and Data. Then used "vr superwipe" as recommended. Before installing the Kernel, just wiped cache and Dalvik cache.
The phone was misbehaving before and after I did all the changes from stock software. I wanted to see if changing the ROM and Kernel would fix the issues i was having, but alas, no.
Now the question is, do I get another EVO 4G or something else? I love my EVO, plus I just got a new batt. and car charger, and now I have spare parts in the old phone that doesn't work 100%.
what to do....
The only thing that may change when flashing a rom is what number you dial do voicemail. Other than that, all other info is on different partitions. By flashing a rom, you can't break your carrier flash unless it wasn't right to begin with.
OK, just for giggles try smelkus recovery. Its the MOST recommended recovery. Use the superwipe x3. It formats everything.
Secondly, a large percent of roms are using a sdext partition. Format to at least ext3.
Then try a simple rom. Find a rooted stock.
If it still doesn't work, then you will probably need another one. There's a guy in the Q&A section with 2 of them asking questions about selling his. Might wanna look into it.
Sorry I couldn't be more help.
I'll take AOKP anything
cbucz24 said:
The only thing that may change when flashing a rom is what number you dial do voicemail. Other than that, all other info is on different partitions. By flashing a rom, you can't break your carrier flash unless it wasn't right to begin with.
OK, just for giggles try smelkus recovery. Its the MOST recommended recovery. Use the superwipe x3. It formats everything.
Secondly, a large percent of roms are using a sdext partition. Format to at least ext3.
Then try a simple rom. Find a rooted stock.
If it still doesn't work, then you will probably need another one. There's a guy in the Q&A section with 2 of them asking questions about selling his. Might wanna look into it.
Sorry I couldn't be more help.
I'll take AOKP anything
Click to expand...
Click to collapse
Thanks for the suggestions.
I got the smelkus recovery working, did the superwipe, then flashed the Nitrous ROM and Kernel, but still stuck in Hboot screen.
My last attempt will be to unroot with a RUU file. If that doesn't work, I know some hardware is screwed and I give up.
I'm getting a EVO 3D off eBay, so I'm excited for my new phone. The 4G was phenominal, and the 3D is gonna be even better! can't wait!