Develop Bugs

[Q] I need some help!

This past week, I have tried both Myu Warm Treats for Android and Baked Snack roms. I have been using CyanogenMod ever since I rooted my phone, and I love it. I just wanted to try out a couple of other roms I kept hearing about. Anyways, everytime I flash a new rom, I keep getting these error messages saying that the "process-android-media" or something has encountered an error. I keep getting that and another error like it saying that the mms process has unexpectedly closed. This has happened on both of the roms I've tried and nothing I have tried will fix it. When I flash recovery back to Cyanogen, it's perfectly fine. What should I do?

The most likely problem is forgetting to wipe everything in recovery before flashing a new rom. Wipe userdata and cache and Dalvik cache. Then everything should work fine.
btw, it's really best if you put questions in the Q&A section. I fear a flame war will emerge from this thread.

How are you trying to flash the ROM? It should be done with Amon RA or Clockwork (or ROM Manager if you're using Clockwork), so no processes should be ending while you're flashing.
Also, this belongs in Q&A Forum, not Development.

Yeah, I just thought the ROM Manager would take care of wiping all the data and what-not. And sorry for not following whatever "protocols" you guys have for these types of things. It's maddening when you can't figure out a problem like this on your own. I just wanted to find some help as quickly as possible.

[Q] HELP!!!!

Hi, hope im posting in the right section.
i have had my desire since it came out , rooted it straight away , flashed loads of diffrent roms (from here) but now all of a sudden my desire has started crashing all the time and when i say all the time i mean about every 15 mins. I take the battrey out, boot use it for a min then when i next go to use it it wont do anything and i have to take the battrey out again and boot.
i have tried lots of diffrent roms it still does the same, i have even tried to run backups from rom manager and still the same. i have run antivirus still the same.
any ideas
thanks

It sounds like a kernel issue (too much undervoling or overclocking maybe, and some ROMs might not contain a kernel image), but first of all it would help us if you told us what ROM you're actually using right now.

Try to flash your sd rom.
If you use a2sd..partition again.
Full wipe again and flash you favorite rom.
If the problem still percist....Flash an official rom better old one 2.1 for no change to newer boot. Test the device if still freeze.
If everything ok, root again your phone ...partition again sd and then flash your favorite rom.

I've been having the same problem mate. Just flashed back to stock 2.1 and all seems fine now. Will reroot later this week and see what happens!
Sent from my HTC Desire using XDA App

Moved to Q&A.
Please do not post question threads in Development.
Post What Where:
General - general technical discussion items, news, anything else that does not fit into the other fora categories.
Q&A (Questions and Answers) - all questions, irrespective of type, get posted in here whether they be theme related, accessory related, technical, etc.
Accessories - any items to do with components and/or accessories relating to your device.
Rom Development - only meant for very advanced technical discussion directly related to ROM development activity and the delivery of actual ROMs and ROM components ONLY. Nothing else goes in here.
Themes & Apps - anything to do directly with the development of themes and/or applications. Nothing else goes in here.

Right sorry for the late reply the misses made me paint the kitchen before the new floor was put in.
well tried everything so then tried flashing back to stock but it carnt find bootloader (using magic mem card)
any more idea's?
ps im using aurxtsense 8.0
i was thinking it was something to do with clocking as well.
mine seams to have calmed down now, it still couldn't find bootloader though when i tried to flash a stock ruu.
i formated my memory card and re-flashed aurxtsense 8.0 and it hasn't crashed since.
haven't tried doing anything since because i aint got time to sit and sort it out at the mo if something goes wrong again

Not sure what the means but you should be able to flash the ruu from HTC or if your phone is branded then one from the network. There's a like to them all in the dev section.
Can tell u though that I flashed back to stock and had no problems. Bit since rooting again its back. Even wiped my SD card and recreate the partitions. Doesn't seem as frequent this time though. I went straight to a hd Rom. It never used to happen on older custom roms and do think its something to do with the volting & clocking.
Sent from my HTC Desire using XDA App

[Q] Looping Boot Image

Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?

Have you use amo-ra?
Sent from my evil evo!!

rsjc741 said:
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Click to expand...
Click to collapse
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1

klquicksall said:
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
Click to expand...
Click to collapse
Thanks
I should face-palm myself. I just read the sticked post and I'm going to try some of his suggestions. He pointed out why cyanogenmod wouldn't work.
My whole consept of the framework went out of the window, and now I think of it more like a standard linux distro, in terms of kernel->ROM relationship.
I don't think I need to have a custom kernel for the Gingerbread beta-4, but i'll look it up just in case... Though I don't have a clear idea on how to flash that.
And to the person 2 above, im using Cyanclockwork. For whatever reason, I like its design verse RA recovery. I might try RA recovery just to see if it works better, as everyone has said it does.
I think i needed to clear all my caches and then load the ROM.

So I did a wipe of everything (data, darvik, cache) and trying to install the GB ROM. My boot screen is *still* looping. Do I need to get another kernel? Is it like flashing a ROM? Where are they at? I didn't see any in the software section...

Boot Loops, forever.

So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!

Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App

i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...

Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App

I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.

You can also try wiping /system and /boot.

*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.

All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.

SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility

no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)

wow... what a bummer. thanks for the help anyway, it's much appreciated.

sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium

I'll try it again to verify the code, I'm pretty sure it was "170"

sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had

sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468

This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App

=D
Sent from sweet snacks off tapatalk.

[Solved] MiuiV4 CDMA will not boot

All right this problem has now been solved! Thank goes to khamsakamal48 for posting the solution for the problem. The problem is solved by replacing the updater-script with the one that is used in the GSM version the of Rom. Then Using the latest 4ext recovery, wipe everything and install. Thank you to everyone that have participated in trying to get this solved. This might also work with other recoveries, but has not yet been confirmed.
Updater-Script: http://db.tt/sUfk5p8E
Latest 4ext recovery: http://db.tt/sP5o7HhJ

only thing i could think of is try a different recovery .I haven't had any trouble at all booting miui an i use cwm touch version.

Alright I'll have to give it a try. Was trying to avoid that but oh well. Thanks!
Sent from my Incredible 2

so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.

kylesag21 said:
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
Click to expand...
Click to collapse
Can you give us a little more background on your phone setup? Have you flashed roms successfully before or is this a first time? Are you s-off?

Sorry bout that. I am S-off and I am able to flash all of the other roms available. But when it comes to this one it just won't flash.
Sent from my Incredible 2 using Tapatalk 2

I have been having this same problem. I am going to try to go through everything I have done to see if I can get more info.
I had MIUI V4 (2.9.29 CDMA) running shortly after rooting this phone (maybe 1 week ago). I installed it from the latest TWRP, so that isn't our problem. I loved it and everything was great. I am unsure what radio I was on at the time, and I think that may be where my problems came in.
I successfully installed ViperINC 1.0.0 after doing a factory reset, wiping cache, dalvik from my WORKING MIUI V4. It booted and I played with it for a few hours, but wanted to go back to MIUI. At this point I was on the firmware from nitsuj17's thread. When I tried to factory reset and install MIUI clean again I started having the same trouble as OP. Since then I have tried every radio I could get my hands on, and may have even been a bit sloppy about what firmware I flashed (the only one I'm unsure of is CondemnedSoul's Return to stock as I am unsure what all it included other than radio and stock rom). After a lot of different attempts, I used CondemnedSoul's PG32IMG and went back to stock where I had everything working fine (for stock). I got an OTA update, but wasn't satisfied so I kept trying different radios from the pinned post on the Development thread (really only .0312 and .0320 as well as the first leaked firmware I linked from nitsuj17). So far nothing has worked to get me any further than the OP unless I just use a different rom. Had this rom never worked I would just talk to the developer, but as I had it working before and no idea what changed I'm at a loss.
I don't have enough posts to get something on the Development forum, but if anyone here can help, I'd really appreciate it.

I've been scouring these forums looking for someone who has made progress on this issue. I'm going to make a list here of posts by people having similar problems, if not the exact same. I have yet to see anyone successfully address them.
One of a few people on the MIUI V4 thread who have had the same issue. I had this rom running at one point, though, so I'm not sure what change caused it to stop. I definitely get further with the TWRP recovery (freezes on "android" splash screen) than the 4ext recovery (reboots to recovery).
I don't believe the JB issues are directly related, but similar problems.
Similar to the Jellybean issue above. More similar to my own situation since I also only started having trouble after flashing ViperINC, but I have formatted, wiped and reverted (even to S-ON and unroot Froyo) so much that I can't see how it would have changed anything that I have not removed. This thread has 3+ people with the same sort of issues. Last report one of them installed ViperINC with all defaults and let it run for a few minutes then wiped and re-installed CM10 with success. I may try this, only with MIUI. I have no idea what settings would be slipping through.

And the cdma miui is one of the only roms that boots for me. Running it now. I think Zelmo is right, there's something sticking around with that Aroma script. I've flashed aosp roms over sense roms and vice versa without even wiping and never had issues like these. I've basically wiped this thing with steel wool and always the same thing. It's gone atleast 15 mins with it's bootloop/freezing max cpu process. It ain't gonna boot! I was up until 2am last night ****ing with it. I'm done.

I'm nearly there. Had I never been able to run MIUI, I would probably have dumped it by now, but it's like an itch I can't reach at this point. There is just something there that I can't see or imagine that is hanging in through every wipe I can find. I just formatted my SD card and did a bunch of wipes (I know that has been tried) and I'm going to try VenomINC with all defaults like Zelmo88 had some success with. If I don't have any luck getting to MIUI from there I'll probably go back to my dinc or buy a new phone soon. This one was really an experiment anyway.
Will follow up if I can figure out anything else.

khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.

stoicwood said:
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
Click to expand...
Click to collapse
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.

grunt9800 said:
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
Click to expand...
Click to collapse
I think most of us first noticed these problems around the time we flashed Viper, but I have nuked this thing so hard from so many different directions since the last time I ran Viper that I can't imagine anything surviving. Still, a little too coincidental.
Running the GSM version didn't last long, either. I played around with trying to get it to use my sim, but as soon as I changed some of my network settings it went into a bootloop tailspin and somewhere along the way corrupted my /system. That took a little work to get around, so now I'm back to aeroevan's CM10 which runs OK... other than what doesn't.

Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app

[SOLVED]
khamsakamal48 said:
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly first try! Now running CDMA version without problem. I don't know why it works, but it works. Everyone thank khamsakamal48!

I'm not seeing a meta-inf folder. Is there another place it could be?
Sent from my vivow using xda premium

I believe it is in meta-inf>com>google>android
Updater-script should be located there.
Sent from my HTC Incredible 2 using Tapatalk 2

Nope, no meta-inf. Back to Google
Sent from my vivow using xda premium

Are you using 7zip to open up the zip file?
Sent from my HTC Incredible 2 using Tapatalk 2

I'm too embarrassed to tell you what I was trying got it now, thanks again
Sent from my vivow using xda premium