[Q] Flashing problems. - General Questions and Answers

Hello everybody.
I've scoured these forums for a few days now, in hope that I can resolve this very frustrating problem but, alas, I've failed in my mission and have had to resort to picking your brains. (sorry about that!)
I'm running Cyanogen mod 7 on my T-Mobile G2 GSM and so far the ROM has worked brilliantly. The only reason I'd like to change is because of the poor GPS. I've tried a patch and the command fix but both of them didn't work for me.
Anyway... When I boot into Clockwork mod recovery (and wipe all the necessary files) and try to load my new ROM, I'm presented with an error message similar to this:
------------------------------------
finding update package...
opening update package...
E:error in / [ROM NAME & LOCATION]
Install Aborted
------------------------------------
I've tried downloading the rom several times via different websites, tried different ROMs all together, followed every bit of advice I could muster on here, and even purchased a new memory card... Just in case.
It's really frustrating though because I have to use recovery to get Cyanogen back (I need it to tether or I have no internet at home!) and that takes so long each time.
As you can probably imagine, it's really frustrating .
Any help would be massively appreciated!
Thanks again,
Bacoon.

Bacoon said:
finding update package...
opening update package...
E:error in / [ROM NAME & LOCATION]
Install Aborted
Click to expand...
Click to collapse
on sdcard /mnt/sdcard/clockworkmod folder there is a log take a look at it
I think you have to flash a corresponding CWM by fastboot utility

Thank you for getting back to me!
There are 2 that I can see. Should i go for Recovery.log or Report.log?
It's also giving me lots of options to view it... Should I use html viewer? It seems like the only thing that'd work.
Cheers!
EDIT:
I used the HTML viewer on "Report.log" and it came up with a HUUUGE list. Anything in particular I should be looking for, mate?

Bacoon said:
Thank you for getting back to me!
There are 2 that I can see. Should i go for Recovery.log or Report.log?
It's also giving me lots of options to view it... Should I use html viewer? It seems like the only thing that'd work.
Cheers!
Click to expand...
Click to collapse
report.log is generated from cwm recovery menu to report them errors
It says open ROM Manager to repport the issue
recovery.log in a general log to describe CWM activity
I think easy way is to change to a CWM that will allow you to flash that ROM
(I can't tell you exactly because I don't have links)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
to see/edit files use notepad or better Notepad++ that's a decent editor/viewer best Notepad replacement
I don't know give me a link to that log or better think to change CWM recovery...

alsnxpl Ancient
try CM 10.1
---------- Post added at 03:34 AM ---------- Previous post was at 03:29 AM ----------
Android_Number17 said:
try CM 10.1
Click to expand...
Click to collapse
By Mardon

Related

[ROM] CyanogenMod 6 For Vega (unofficial)

I have created the vendor files for the advnet vega based apon the cyanogen ones for the Gtab, and compiled CM6 for the vega. This is not supported by cyanogen's team yet as the vega isnt officialy supported by them yet so please take that into mind (dont ask for support on the cyanonen irc ect u probably wont get it) but feel free to ask support on this thred.
Nither me or the CyanogenMod team take no responsability for any damage caused bu this rom. by flashing it means u understand this risks and accept the risks.
What doesnt work :-
- Camera
- Rotation can be funny (if it works at all)
[UPDATE]
- Black Screen Of death can occur when rebooting (looking into this ASAP) so be prepared to restore
What works :-
- Every thing else (i think)
[INSTALL]
1) get the .zip file from the bottion of the post
2) copy it to SD card
3) reboot into recovery
4) MAKE NANDROID BACKUP
5) flash zip from recovery (you will get a boot write error thats normal)
6) reboot
7) DONE
[DOWNLOAD]
http://db.tt/UmV1dYK
[CREDITS]
CyanogenMod Team for there src
Bekit for the Gtab vendor this is based on
Anyone else i have forgotten
[MY VENDOR]
If anyone else wants to try and improve on this please feel free.
https://github.com/BuzzBumbleBee/android_device_vega/tree/froyo
(Please note at the current time the boot.img that the compile creates will not work on the vega to u will have to make one by extracting the original ramdisk from the boot.img)
thanks mate been tring with cyanogenmod for gtablet..gonna try now. THis bad boy vega need some action
got error message:
assert failed: package_extract_file("boot.img" ,"/temp/boot.img")
E:Error in /sdcard/CM-6.2.0-Vega.zip
(status 7)
Installation aborted.
edit: fixed.
I successfully installed, I put the original boot.img from vega into the zip, taking it for a spin now. Thanks Apache14.
I sold my Vega because of the screen imo wasnt great and the wi-fi issue.
Would have loved to have tried this rom though.
Good work !!!
Thanks to apache14 and everyone involved
How do we get market onto the tab. thanks in advance
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Apache14 said:
Dunno about market any CM6 compatable gapps will work ..... also the adding boot.img isnt needed as there is no need to flash the boot.img (the stock advent one works pritty well for now)
Click to expand...
Click to collapse
thx mate, misread the first post
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
arad85 said:
Anyone working on fixing the black screen of death on cold boot a lot of people are getting with clockwork? I know there are enough people who don't have CW installed because of this that anything that depends on it will have a more limited appeal.
Click to expand...
Click to collapse
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Follow the instruction paul gave on modaco.
Download the Recovery image and flash utility and extract to desktop
open terminal
adb devices to make sure your device is connected
cd to the directory of file you just extract
then type
adb push recovery.img /data/local/
adb push flash_image /data/local/
adb shell chmod 4755 /data/local/flash_image
adb shell /data/local/flash_image recovery /data/local/recovery.img
thats done.
If you on mcr 6, the vega reboot recovery is already installed if not download from the market.
cheers
alphaola said:
I have installed clockwork a couple of times and no black screen of death. Its straight forward.
Click to expand...
Click to collapse
Yes, it's very straightforward. I've done it a few times too and followed the instructions. I still get the bsod as do a number of others. Without CM installed, no bsod...
Try power cycling your Vega back-to-back using the power button. I bet you'll get it to bsod reasonably quickly.
BSOD
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Apache14 said:
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
Brilliant - thanks
Apache14 said:
Some people have reported black screen of death when rebooting with the power menu. so be careful and be prepared to restore (or flash stock boot,img again)
I am looking into this error now and hope to have a fix pritty soon
Click to expand...
Click to collapse
arad85 said:
Brilliant - thanks
Click to expand...
Click to collapse
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Note: Do not unzip the cyanogengenmod, just use winrar to open it and copy those files into it then close it
alphaola said:
i fixed it. Copy boot.img,system.img and ramdisk.img from vega into the cyanogenmod zip,then flash, it also boot into recovery using rom manager.
Click to expand...
Click to collapse
Sorry, being particularly thick today. How do I get hold of the three .img files?
arad85 said:
Sorry, being particularly thick today. How do I get hold of the three .img files?
Click to expand...
Click to collapse
download the advent vega system file from advent vega website,zip it using winrar.
alphaola said:
download the advent vega system file from advent vega website,zip it using winrar.
Click to expand...
Click to collapse
<facepalm>
arad85 said:
<facepalm>
Click to expand...
Click to collapse
no stress man. Its quite smooth and fast, love the animation as well
alphaola said:
no stress man. Its quite smooth and fast, love the animation as well
Click to expand...
Click to collapse
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
To get the market and apps
Download http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip, then flash using rom manager. then once you reboot you should get all your apps and market. enjoy
arad85 said:
So I did all this, and now have a device that is....
... exactly the same as before but with CWR installed (even says it's MoDaCo ROM). The flashing process took only a few seconds and no boot write error. Am I missing something here?
EDIT: hang on... just realised the zip file was wrong!!
Click to expand...
Click to collapse
ahahha mate,it works.
Download button savior to make navigation easy
Hello all
Really looking forward to a stable version with an idiot proof install for folks like me.
Great work
Rgds
Lok

Sensation Root Problem at Step 3 TRIED OVER 30 TIMES Many of ways

I can be contacted here: [email protected]
Anyone able to help with Root ? I picked up a link in a HTC thread on Whirlpool
http://forum.xda-developers.com/show....php?t=1192300
got as far as S Off (Security Off), Updated Clockwork Recovery mod- v4.0.1.4, Now I am stuck on To permanently root your Sensation part 3. When trying to update: When I go to flash clock work/Revolutionary it says: (bad) Can't open Install aborted, though that said some users are having this error and the root is still successful according to XDA however for me I got Root check off the Market and it returns a failed result on Basic and some times a pass on Advanced but some times not. Busybox,Super user,Titanium back up are all saying I'm not rooted to don't have Root permissions.
Have a look at the link below it contains 4 photos of my sensations screen as I went through the process it will no doubt give you a better idea of my problem. It's a link to my blog BTW. Any help would be greatly appreciated. I am not a member of XDA so thought I would try my luck here before having to create yet another account somewhere Thank You.
Best look at the photos from bottom to top as they uploaded back to front, order of process is bottom to top.
http://mathewmurrayharrison.blogspot...sensation.html
Phenomenal MATT writes...
Anyone able to help with Root ? I picked up a link in a HTC thread on Whirlpool
So did you download this http://forum.xda-developers.com/atta...8&d=1311991644 file and flashed it via recovery?
I have S-OFF and I flashed that file I have full root. I then used ROM Manager to flash clockworkmod (CWM) because ROM Manager doesn't see the recovery that came with the S-OFF.
I just backed up my Telstra ROM. It just finished a minute ago.
Yes I did flash that via Recovery inc. the old su-2.3.6.1-ef-signed.zip AND the new su-2.3.6.3-efgh-signed.zip.version I've tried the other couple of suggested methods on that link I posted and nothing seems to be working. Sadly can't see were I have gone wrong.
Here is a link to another two photos with the error message I am getting.
http://mathewmurrayharrison.blogspot...blog-post.html
Phenomenal MATT writes...
Yes I did flash that via Recovery inc. the old su-2.3.6.1-ef-signed.zip
Did you install ROM Manager? I installed ROM Manager and used that to flash CWM and all is working fine here.
EDIT:
My bad. You did say you can't get full root. Don't really know why it won't work for you. Mine worked first go.
Phenomenal MATT
Yeah I have Rom manager but I can't do anything with it everything returns an error.
Phenomenal MATT writes...
Yeah I have Rom manager but I can't do anything with it everything returns an error.
I just figured that out, my bad. I understand that rooting doesn't stick.
Phenomenal MATT
Sounds like you were one of the lucky ones cause if you read the comments after the steps many people are have minor issues. I'm ashamed to say I've being at it all day VERY FRUSTRATING !!!
Yes I put the ZIP file into 'The Root' of the SD card (Main section of SD Card) and yes in recovery I can see that zip file but when I click open it says:
Can't open /sdcrd/su2.3.6.3-efgh-signed.zip
(bad)
Installation aborted.
I've tried over 30 times same thing every single time. HEADACHES !!! lol
Sooo looking forward to a solution. I might have to creat a XDA account and post it in the questions section there, looks as though questions are getting answered pretty quick (Good support) ...WITH ALL THAT SAID IF ANYONE HERE CAN HELP I WOULD BE MOST GRATEFUL.
Phenomenal MATT writes...
Can't open /sdcrd/su2.3.6.3-efgh-signed.zip
(bad)
Installation aborted.
You've probably already tried this, but if not, have you downloaded the su zip again? could it be corrupt?
EDIT: I am really new to Android. Got my phone the day it came to Telstra. You are probably better off on the XDA forums.
Phenomenal MATT
I signed up for XDA but they expect you to make 10 posts elsewhere on their forum before allowing you to comment on the Sensation Dev. one (The comments under the instructions in this link:
http://forum.xda-developers.com/show....php?t=1192300
Yeah I downloaded it on PC, Mac, Mac with Boot camp, Zipped, un Zipped and even tried the old Zip file it says to try in trouble shouting section then followed buy the new Zip file.
Awwwww Well Patients a vertue ... Hopefully it's all worth it.
Seems like the guy already gave you your answer. Just download the zip again. You probably have a corrupted download. And make sure that signature verification is off in recovery. Should work.
I've downloaded over 30 times on 3 different computers + straight to Sensation as a hard Disk tried Zipped, unzipped you name it... PC - Mac Normal sd card, Micro SD card... & Also like to add Sign. verify is off too tried it on and off, I a award the file needs to be zipped and that needs to be off just trying everything here pulling my hair out.
Do You go CWM > Advance . backup ur Rom ?
I'm using rev. And I go to backup and restore click on back up after its complete 10 minutes later I go and try to get the zipped file but it fails every time.
Sent from my HTC Sensation Z710a using XDA App
Finally got it to work. I had to download it from the net with my phone to download folder as opposed to with a pc then moving it to main root folder on SD card. Question is now what ? I want to over clock but I want to keep sense. Do all Roms remove sense ? Leedroid ? What else is recommended now I'm rooted. Btw thanks again everyone for your help.
Sent from my HTC Sensation Z710a using XDA App
Thanks Matt
Thanks for posting this, Phenomenal Matt. I had the EXACT same problem that you posted about. Copying the su zip file to my phone's sdcard while the phone was mounted as a drive did not work at all. I had to download the su zip file on my phone before Clockwork Recovery was able to successfully install it and give me root.

[Q] Status 7 error when flashing a new ROM in TWRP

So, I do have the newest TWRP installed, but I get a "Status 7" error message anytime I want to flash a new Jelly Bean rom. I'm on AOKP 4.2.1 right now. Can anyone help me?
Here is the error message:
Code:
--Installing: /sdcard/aokp_tf300t)_unofficial_20120625_2002_build-40.zip
Finding Update package...
Opening Update package...
Installing update...
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf30
0t"
E:Error in /sdcard/aokp_tf300t_unnoficial_20120625_2002_build-40.zip
(Status 7)
Installation aborted.
Frank11 said:
So, I do have the newest TWRP installed, but I get a "Status 7" error message anytime I want to flash a new Jelly Bean rom. I'm on AOKP 4.2.1 right now. Can anyone help me?
Here is the error message:
Code:
--Installing: /sdcard/aokp_tf300t)_unofficial_20120625_2002_build-40.zip
Finding Update package...
Opening Update package...
Installing update...
[B][COLOR=Red]assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf30
0t"[/COLOR][/B]
E:Error in /sdcard/aokp_tf300t_unnoficial_20120625_2002_build-40.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Your problem shown in red. updater-script tested your build.prop for tf300t and did not find that. If your unit is tf300t then edit updater-script and remove the assert lines.
Inside the zip you will find /META-INF/com/google/android/updater-script. Edit with notepad or notepad++; not word, wordpad, or other. Save rezip and flash.
tobdaryl said:
Your problem shown in red. updater-script tested your build.prop for tf300t and did not find that. If your unit is tf300t then edit updater-script and remove the assert lines.
Inside the zip you will find /META-INF/com/google/android/updater-script. Edit with notepad or notepad++; not word, wordpad, or other. Save rezip and flash.
Click to expand...
Click to collapse
Okay, thanks, so I deleted that first line...But the update still failes, yet a I don't get an Error Code anymore.
Frank11 said:
Okay, thanks, so I deleted that first line...But the update still failes, yet a I don't get an Error Code anymore.
Click to expand...
Click to collapse
Sorry for the long delay! Search is still down here on XDA.
I'll have to ask questions I would have searched for.
The rom you are trying to flash is 20120625. That is very old and I can't remember any JB aokp roms on XDA during that time. I didn't catch the date earlier because the assert error was staring at me.
Is this from XDA? Give me some info about the rom or better yet a link. I feel that is an ICS rom with a date that old. Maybe that is not actually a date but appears so. With a link to the rom I might be able to find your current issue.
Note: your recovery you are flashing with should be twrp 2.4.1.0 JB.
XDA search is alive again.
This is an ICS rom. Choose a JB rom and try again I think you will have success.
Good Luck!
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
mikep2323 said:
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
Click to expand...
Click to collapse
Did you do your editing with notepad or notepad ++?
Error 6 is usually files that were edited with wordpad or word. It can also be an editing error such as not completely removing the line or partially deleting or editing a line that is still included.
Note: Wasn't blsckbean 6 ICS?
mikep2323 said:
Any update I'm having same problem.I'm trying to flash blackbean 6 and getting same error,I deleted the stuff posted above and now I get status 6 error.I have jb bootloader and I can flash all other jb romsroms and blackbean 7,but not 6.
Click to expand...
Click to collapse
Not sure but was blackbean 6 an ics rom? I've not looked to see for myself but I have ran 7 and it's great!
Sent from my SAMSUNG-SGH-I747 using xda premium
I unziped it on tablet and edited it with a text editor from tablet then reziped it.If it was a ics one that would make sense but on goo site it says blackbean 6 jbl so I assumed that the jbl meant jellybean boot loader.I also opened the bb7 zip and in that script updater it doesnt have the few lines with the build prop stuff,so after I deleted the first few lines in the bb6 zip it looked exactly like bb7 script updater.I don't think I left any of the lines there.After I edited the stuff I went down to the next line and pressed back button to move the rest of the lines up.If the jbl doesn't mean jellybean loader and it was for icecream sandwhich then I would assume that's why it isn't working.Thanks for writing back.Ive tried almost all the roms for tf300t and like that one the most but without ability to move my game data to microsd card I can't use it.I guess ill have to wait till they can figure out how to make directory bind workwork with jb 4.2.
I also just looked it up and bb6 is for jb bootloader.
mikep2323 said:
I unziped it on tablet and edited it with a text editor from tablet then reziped it.If it was a ics one that would make sense but on goo site it says blackbean 6 jbl so I assumed that the jbl meant jellybean boot loader.I also opened the bb7 zip and in that script updater it doesnt have the few lines with the build prop stuff,so after I deleted the first few lines in the bb6 zip it looked exactly like bb7 script updater.I don't think I left any of the lines there.After I edited the stuff I went down to the next line and pressed back button to move the rest of the lines up.If the jbl doesn't mean jellybean loader and it was for icecream sandwhich then I would assume that's why it isn't working.Thanks for writing back.Ive tried almost all the roms for tf300t and like that one the most but without ability to move my game data to microsd card I can't use it.I guess ill have to wait till they can figure out how to make directory bind workwork with jb 4.2.
I also just looked it up and bb6 is for jb bootloader.
Click to expand...
Click to collapse
I'm downloading it now, when finished I'll see what I can do and give you an update.
tobdaryl said:
I'm downloading it now, when finished I'll see what I can do and give you an update.
Click to expand...
Click to collapse
Thanks I would appreciate the help,I've searched for endless hours and everything always points back to editing those lines..If you need anymore info let me know.I've also tried to download diffrent times.Bb7 flashes fine and hydro and clean rom and blue rom but bb6 wont.I even flashed bb7 then tried to flash bb6,same error as frank got.I also made sure my build prop said tf300t for the errors.I've tried many combonations and wipes.I'm on blue rom now if that matter
mikep2323 said:
Thanks I would appreciate the help,I've searched for endless hours and everything always points back to editing those lines..If you need anymore info let me know.I've also tried to download diffrent times.Bb7 flashes fine and hydro and clean rom and blue rom but bb6 wont.I even flashed bb7 then tried to flash bb6,same error as frank got.I also made sure my build prop said tf300t for the errors.I've tried many combonations and wipes.I'm on blue rom now if that matter
Click to expand...
Click to collapse
OK. Sorry for the delay, I've been recovering my tablet. I edited the updater-script, flashed BB6. Stuck on bootanimation, flashed again, stuck on bootanimation, restored my previous backup, stuck on bootanimation. Flashed stock rom back to a working tablet.
I can't suggest you install the rom but I have uploaded updater-script.
For the future I also edit on the tablet. I suggest jota free on the playstore, it does not add extra characters that cause errors. Example most editors end a line with both linefeed and carriage return which will not work for these files.
Good Luck!
Thanks for getting back to me,I will probably try this at some point,if it didn't work on your tablet then maybe it wont work on mine as well.I do have a few backups and all my apps on titanium back up so maybe ill give it a try.Maybe I just might have to wait till they make directory bind work with jb 4.2 to flash Bb7.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
mikep2323 said:
Thanks for getting back to me,I will probably try this at some point,if it didn't work on your tablet then maybe it wont work on mine as well.I do have a few backups and all my apps on titanium back up so maybe ill give it a try.Maybe I just might have to wait till they make directory bind work with jb 4.2 to flash Bb7.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You're welcome. Sorry my results weren't better.
tobdaryl said:
OK. Sorry for the delay, I've been recovering my tablet. I edited the updater-script, flashed BB6. Stuck on bootanimation, flashed again, stuck on bootanimation, restored my previous backup, stuck on bootanimation. Flashed stock rom back to a working tablet.
I can't suggest you install the rom but I have uploaded updater-script.
For the future I also edit on the tablet. I suggest jota free on the playstore, it does not add extra characters that cause errors. Example most editors end a line with both linefeed and carriage return which will not work for these files.
Good Luck!
Click to expand...
Click to collapse
Can you upload an updater-script for Gingerbread MT6575 models ? Also the link is not working.

[Q&A] [FIX] Low Mic Call

Q&A for [FIX] Low Mic Call
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FIX] Low Mic Call. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hi
Can you specify what the changes made by your fix are?
This fix solved my bad quality calls! Thank you.
no luck...
I flashed it... No luck..sounds still muffled...
Even worst than before... Anyone knows how to roll back it
I myself listened the voice from other phone and it sucks...the volume is low and muffled..it needs to be taken on high priority... I attend too many business calls n the main function doesn't works properly..
Also you should make a YouTube video with step by step instruction...
I had no trouble with flashing by twrp. I think the call quality is better now.
Fine!
Did it flash correctly?
Im wondering, did it flash correctly? According to the dialog there was an error first but it said successfull? Pls help. Thx
Perfect
The script is good and does the job, I had to put the build.prop file and the zip file on the root of the sdcard otherwise it wouldn't flash.
Nope
Fix does nor work. Build.prop does not change at all. Tried in /sdcard/ and /sdcard/0 without succes (although the installer claims succes, build.prop does not change). Still have the issue that during call the other end cannot hear me unless I am on speaker.
I'm having the same issue
- Noise
- The other side unable to hear me.
- tested using google voice search/voice recording software unable to detect any voice.
- using Speakephone and Headset are ok.
what have changed
The issue start to happen after I install OxygenOS. I've change to CM12.1 the issue remain.
I've follow the fix on this thread and confirm the result on build.prop, not working for me.
i read somewhere that I need to edit .XML, i have rooted the phone but everytime i save the .xml it says access denied. I really hoping this issue can be solve soon, it start irritate me.
Error in flashing the lowmicfix
Hello, sorry if this is a noob question. I tried the LowMicFix, placing the two files included into the .rar file in the Downloads folder. I then rebooted the phone into recovery, clicked Apply Update, selected the zip file and I get this message:
HTML:
Finding update package..
opening update package..
verifying update package…
E: footer is wrong
E: signature is wrong
installation aborted.
Have I done something wrong? I really want to fix this problem.
Thank you in advance!
Works like a charm...
Works like a charm
You saved me, I thought my mobile gets screwed
And now works like new
Thanks again
ludester said:
Any fix for the OPO not able to handle recording anything with bass without distorting and making the audio horrible.
Click to expand...
Click to collapse
bobmarsh72 said:
Also would like to know if anybody knows a fix?
Click to expand...
Click to collapse
Unfortunately It's a known issue that's taking ages to being solved by CM/OPO team.
https://jira.cyanogenmod.org/browse/BACON-64
How do I make the change?
I Downloaded the files and put them on my phone in the Internal Storage folder and I rebooted the device, is that all?
What exactly does this mod do? Increase the mic volume or use another mic or something else?
Yet to fix
I bought my OPO a couple of months ago and had no problems with it till the last weak when people started to complain that they just don`t hear me. I never dropped it, never damaged it.
I`m really keen to fix it. I applied all the possible fix instructions (both root editing the system files anf patches) but to luck. I wiped my OPO completely a number of times. I flashed various versions of both CM and OxygenOS.
Is there a chance that it might be fixed with the coming updates?
Hi,
Does not work for me.
It recognize the zip file when i load it from recovery it start the process but it gives me an error and wtire the following:
" Finding update package...
Opening update package...
Veryifing update package...
E:footer is wrong
E: signature verification failed
Installation aborted"
i am with cm12
What can i do?
Trinit! said:
Hello, sorry if this is a noob question. I tried the LowMicFix, placing the two files included into the .rar file in the Downloads folder. I then rebooted the phone into recovery, clicked Apply Update, selected the zip file and I get this message:
HTML:
Finding update package..
opening update package..
verifying update package…
E: footer is wrong
E: signature is wrong
installation aborted.
Have I done something wrong? I really want to fix this problem.
Thank you in advance!
Click to expand...
Click to collapse
You will need to be rooted and flash with a custom recovery.
---------- Post added at 06:23 PM ---------- Previous post was at 06:08 PM ----------
Dandin69 said:
Hi,
Does not work for me.
It recognize the zip file when i load it from recovery it start the process but it gives me an error and wtire the following:
" Finding update package...
Opening update package...
Veryifing update package...
E:footer is wrong
E: signature verification failed
Installation aborted"
i am with cm12
What can i do?
Click to expand...
Click to collapse
-Unlock bootloader (will wipe all data )
-Flash custom recovery (twrp etc)
-Root device
-Then you can flash these files using your custom recovery. IT SOLVED my issue of low mic.
I'm running the latest CM12.1 Snapshot, YOG4PAO236-bacon, and my call quality has been fine on various ROMs until this one. The mic appears to be quite low and everyone I've talked to can barely hear me. Does anyone know if this fix will help this particular problem? I cannot seem to find many answers for this specific ROM release.
EDIT: Manually made the changes and the mic is perfect.
Finally I found a solution...
TheHawk1337 said:
Fix does nor work. Build.prop does not change at all. Tried in /sdcard/ and /sdcard/0 without succes (although the installer claims succes, build.prop does not change). Still have the issue that during call the other end cannot hear me unless I am on speaker.
Click to expand...
Click to collapse
After a few months that I needed to use the speaker for calls or bluetooth headset, and tens of times trying all the fixes that I could find on the World Wild Web (the Internet) even trying at least 15 other roms for my oneplus one.
Finally I found a solution...
15 usd on eBay for a module of the main speaker and 20 minutes for replacing the module
According to YouTube video of disassemble
And my one is like new...
Yeah Baby, Yeah....
QA Bot said:
Q&A for [FIX] Low Mic Call
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FIX] Low Mic Call. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Click to expand...
Click to collapse
Hello,
with this fix my headphone mic is now good. However with my mic from the phone LG G2 802 I have now lots of echo. So I got with this fix a echo problem. How to solve it?
Regards,
Martin

Rom size errors

After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You would have a better chance of finding a working solution if you go to the M8 forum.
I'll bet @xunholyx can get you straight, he's pretty experienced with the M8 I think.
siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
xunholyx said:
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
Click to expand...
Click to collapse
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
siepod said:
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
Click to expand...
Click to collapse
Download this splash.zip, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Next, download this RUU onto your PC to update to Lollipop. Hook up your phone and double click on the download, then follow the prompts. You'll probably get a "fail hboot pre-update" (or something like that). The first run updates the hboot with old firmware. Just run the RUU a second time without disconnecting, and the conversion back to Sense will be complete.
xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
You are an absolute star, thank you. Will give this a bash when I get home from football later today, and let you know how I get on or if I have any problems. Great written instructions though, thanks!
xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
siepod said:
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
Click to expand...
Click to collapse
I'm not sure.
Try the splash.zip download and instructions from here. It should be the same file, but trying another download and flashing from your PC might work better for you.
xunholyx said:
I'm not sure.
Try the splash.zip download and instructions . It should be the same file, but trying another download and flashing from your PC might work better for you.
Click to expand...
Click to collapse
Brilliant, tried those and it worked a treat. Then installed using the RUU you gave me, and as promised I was greeted with a full back to stock Sense version, and have been able to install the ROM I wanted. Thanks once again for all your help, truly appreciated!
I'm guessing it was the CID that was causing the error, if anybody has the same problem in the future and ends up on this thread. I'm guessing if I'd have changed the CID your method with the HBOOT would probably have worked too (as out of curiosity I tried the HBOOT method with your file and it then worked).
Thanks again, great to know there are people out there willing to try and help each other. :highfive:

Categories

Resources