So, I'd been using MIUI for some time, and as we all know it has low in call volume when we receive a call and now this problem persists even after switching back to stock ROM ( spice 318B A01 ).
Thats really weird because it was a fresh install of .nb0 and not a nand backup. And I made sure to format /system as well as /data and /cache.
This thing is really bugging me
Any of you guys facing the same problems?
desperate for a fix *sigh*
peace.
whyzee said:
So, I'd been using MIUI for some time, and as we all know it has low in call volume when we receive a call and now this problem persists even after switching back to stock ROM ( spice 318B A01 ).
Thats really weird because it was a fresh install of .nb0 and not a nand backup. And I made sure to format /system as well as /data and /cache.
This thing is really bugging me
Any of you guys facing the same problems?
desperate for a fix *sigh*
peace.
Click to expand...
Click to collapse
hi
31B has a lot of bugs like the screen lag and all try the 31D take it from below link im sure ur wont have any problem i have flashed all the roms provided here and have gone back to the same never had any problems at all
link : http://www.mediafire.com/?28bhxqedlru2ii1
not sure if i have renamed it to firmware.nb0 if not rename it and place it on the root of ur SD and flash via stock recovery this one is good u wont have any problem to my knowledge
whyzee said:
his problem persists even after switching back to stock ROM
Click to expand...
Click to collapse
I had the same problem
Multiple flash with CWM I did not solve the problem
The problem was solved when I flash with SUT L3.
kugga said:
I had the same problem
Multiple flash with CWM I did not solve the problem
The problem was solved when I flash with SUT L3.
Click to expand...
Click to collapse
sure will try that too..
turns out I had a faulty SD card
haree said:
hi
31B has a lot of bugs like the screen lag and all try the 31D take it from below link im sure ur wont have any problem i have flashed all the roms provided here and have gone back to the same never had any problems at all
link : http://www.mediafire.com/?28bhxqedlru2ii1
not sure if i have renamed it to firmware.nb0 if not rename it and place it on the root of ur SD and flash via stock recovery this one is good u wont have any problem to my knowledge
Click to expand...
Click to collapse
Is this Cherry version cause there is a 5019 version on their site??
whyzee said:
Is this Cherry version cause there is a 5019 version on their site??
Click to expand...
Click to collapse
its spice CSL
From my SpiceMi410 via XDA Premium
Related
So I installed the new clockwork recovery to install CM7, which I decided against until it's stable
But now everytime I boot to recovery there is like insane vibration!? Like seriously it would be a solid 5 on the Richter Scale
Is there anyway to prevent this? I know other people had this problem as well but the CM7 thread was developing too quickly for me to find a response.
Hope someone can help!
I'm having the same issues as well
however i went ahead and run the backup
completed it
Haven't flashed to any custom roms though
Getting exactly the same thing on my LG O2X, too. Very strange. I think I'm just going to let it buzz and flash a new ROM... :-o
issue still persists with latest version of CWM recovery -- very annoying to say the least.
I'm surprised a solution hasn't been posted yet...?
I'm also getting this constant vibration with CWM Recovery.
I have change Baseband, CWM & ROM many times, yet still it always constantly vibrates in CWM Recovery.
My LG 2X is a "made in Korea" model, if that make a difference.
There must be a fix ?!?!
It has been said many many times, no solution possible or known. You'll have to do with it. Nobody knows where it comes from, very few people have this.
I've solved the vibration issue on my O2X. After tried several version of CWM finally I've found this version '4.0.0.5-modaco-2x-clockworkmod' has no vibration issue.
Here it is: http://www.mediafire.com/?tvgghy52k6myjd4
Thank you for solving this.
mewtwo68d said:
I've solved the vibration issue on my O2X. After tried several version of CWM finally I've found this version '4.0.0.5-modaco-2x-clockworkmod' has no vibration issue.
Here it is: http://www.mediafire.com/?tvgghy52k6myjd4
Click to expand...
Click to collapse
i have the same issue.
is this zip safe to use? we install it from cwm recovery menu?
does anybody with the same issue test it?
freemannnn said:
i have the same issue.
is this zip safe to use? we install it from cwm recovery menu?
does anybody with the same issue test it?
Click to expand...
Click to collapse
No, unzip the file and you'll find 'install-clockworkmod-windows.bat' file, connect your phone and run the .bat file
mewtwo68d said:
No, unzip the file and you'll find 'install-clockworkmod-windows.bat' file, connect your phone and run the .bat file
Click to expand...
Click to collapse
i have already installed some a version of cwm. (5.0.2.2) i think
is this a problem? or it will overwrite it?
freemannnn said:
i have already installed some a version of cwm. (5.0.2.2) i think
is this a problem? or it will overwrite it?
Click to expand...
Click to collapse
No problem for me, i've installed cwm 5.0.2.7 on my phone before i install 4.0.0.5-modaco-2x-clockworkmod. No need to re-flash your phone.
Got it installed ok.
I can't do a CWM managed backup, errors with...
Can't mount /system!
hesian said:
Got it installed ok.
I can't do a CWM managed backup, errors with...
Can't mount /system!
Click to expand...
Click to collapse
Thats what i am talking about.
Is it tested that everything works like before;
Sent from my Optimus 2X using Tapatalk
can anyone help me to install it?
For those who like stock rom with 2.3 update .. this update is for u nd from now onwrds its not using uc kernels its jst the basic official rom with root access and blot ware removed
its pre rooted and very well tested and also its a backup file of clockwork mod recovery
there is no fancy thing don its official spice csl 2.3.4 version ... by installing this update may also solve ur warranty issue (becoz did for me) and since here in our country India the service attendant dont mind seeing super use.apk installed on the system since its now available on market so there is no worry u can take this phone to the service center anytime by flashing this recovery file ...
only work after flashing this rom and taking to the service center is to flash back the stock recovery image bt keep in mind my words AFTER FLASHING
How to do it
first u need clockwork mod recovery
then
all u need is to jst download the .zip file
extract it to ur pc
plug in ur phone to usb
mount sd card
look for the folder named as clockworkmod open it
look for folder named as backup
go into it and copy paste here the extracted files
now jst go to the recovery mod and then simply restore the backup and then after restoring is complete jst do a full data wipe full format the disk and i read somewhere that someone asked for document to go or something similar named app which came with the stock rom .. so its now there too i didnt removed it
link Stock 2.3.4 Pre rooted
reserve for future
also suggestions are welcome
To install these updates all u need is to jst put these files to root of ur sd card and then u need to flash it through recovery menu
PLZZ NOTE THAT THIS IS A UNTESTED VERSION SO BEWARE WHILE TRYING
i can not try it myself as my phone is out for service for 7 days if no one tried i will do it on my own when i get it replaced
I am downloading it now. soon i will tell more about it to you guys.
i hope will not brick my device.
kshitij_bhatt said:
reserve for future
also suggestions are welcome
To install these updates all u need is to jst put these files to root of ur sd card and then u need to flash it through recovery menu
PLZZ NOTE THAT THIS IS A UNTESTED VERSION SO BEWARE WHILE TRYING
i can not try it myself as my phone is out for service for 7 days if no one tried i will do it on my own when i get it replaced
Click to expand...
Click to collapse
hi
assuming u mean flash it via CWM or do u mean stock recovery
i have flashed this rom. after that i started the phone, the first problem i got is the lock screen is not allowed me to go in, what ever you i do. then i reast all my data but then also it is not working, so i returned back to rc2
^hey thanx for trying... i too was supposing that lock screen might not work .. did u noticed any changes with the icons ..??
and @haree by flashing via recovery means via recovery .. this might should work with both cwm and stock rom
kshitij_bhatt said:
^hey thanx for trying... i too was supposing that lock screen might not work .. did u noticed any changes with the icons ..??
and @haree by flashing via recovery means via recovery .. this might should work with both cwm and stock rom
Click to expand...
Click to collapse
Currently, we can not flash/install any update.zip using stock recovery. As I have mentioned before in some thread, for our device update zip signed using all available (test) keys returns error for signature verification in stock recovery.
okk i didn't read that anywhere bt i thought signed ziped could be flashed through stock rom and as for now don't flash this rom becoz lock screen is stucked new one will use that same old stock one
yashwantsingh said:
i have flashed this rom. after that i started the phone, the first problem i got is the lock screen is not allowed me to go in, what ever you i do. then i reast all my data but then also it is not working, so i returned back to rc2
Click to expand...
Click to collapse
The reason behind this (I guess) is that our devices have a lot many hidden settings and apk in /cda partition (/dev/block/mmcblk0p9) and many of the apps from /system/app are symlinked (shortcut) to that partition.
Lockscreen settings are also stored there, which tells device which app to open when a particular gesture detected.
And while creating custom ROM we do not mount this partition or may be their communication does not retain. I have never tried mounting /cda/ in any custom ROM that I have cooked myself. (I forgot ), but I used to delete such links.
This is a list of apk that I used to remove, (using Spice Mi410 as base ROM)
AndroidNeroSync-release.apk
bbm_msger_v2_0_r20.apk
ChsHandWritePack.apk
ChsPack.apk
DownloadFlashPlayer.apk
dxtg-foxconn-vwr-pdf_3.001.868.apk
dy_bbstore_my&id_r6.apk
dy_CSLFunClub_my&id_v1_8_r9.apk
FaceBook_hdpi.apk
FacebookSync_Home3_hdpi.apk
FacebookSync_Home3_hdpi.odex
FacebookWidget_Home2_GB_hdpi.apk
FihScreenLock_GB_hdpi.apk
FlickrSync_Home3_hdpi.apk
FlickrSync_Home3_hdpi.odex
FoxconnDLNA_Phone.apk
IndonesianPack.apk
MalaysianPack.apk
MapKing0908.apk
Muvee_Editor_Eclair_1.1.2_Commtiva.apk
TouchPal.apk (You will need to add another keyboard after removing this.)
UI-Android2.0-SCSL-1.2.2.7.apk
ya i too didnt mounted that ... i didnt even noticed that those blot wares are in cda portion... haaww all my work got wasted lol hmm lets do some more work we have plenty of time lol
ok for next update i will consider it too ...
i did deleted these . files from the system/app for this rom
\/
AndroidNeroSync-release.apk
bbm_msger_v2_0_r20.apk
ChsHandWritePack.apk
ChsPack.apk
DownloadFlashPlayer.apk
dxtg-foxconn-vwr-pdf_3.001.868.apk
dy_bbstore_my&id_r6.apk
dy_CSLFunClub_my&id_v1_8_r9.apk
FaceBook_hdpi.apk
MapKing0908.apk
Muvee_Editor_Eclair_1.1.2_Commtiva.apk
TouchPal.apk (ADDED Gingerbread keybord insteed)
now i searching over for mounting /cda and remove blot wares from there
Napstar said:
The reason behind this (I guess) is that our devices have a lot many hidden settings and apk in /cda partition (/dev/block/mmcblk0p9) and many of the apps from /system/app are symlinked (shortcut) to that partition.
Lockscreen settings are also stored there, which tells device which app to open when a particular gesture detected.
And while creating custom ROM we do not mount this partition or may be their communication does not retain. I have never tried mounting /cda/ in any custom ROM that I have cooked myself. (I forgot ), but I used to delete such links.
This is a list of apk that I used to remove, (using Spice Mi410 as base ROM)
AndroidNeroSync-release.apk
bbm_msger_v2_0_r20.apk
ChsHandWritePack.apk
ChsPack.apk
DownloadFlashPlayer.apk
dxtg-foxconn-vwr-pdf_3.001.868.apk
dy_bbstore_my&id_r6.apk
dy_CSLFunClub_my&id_v1_8_r9.apk
FaceBook_hdpi.apk
FacebookSync_Home3_hdpi.apk
FacebookSync_Home3_hdpi.odex
FacebookWidget_Home2_GB_hdpi.apk
FihScreenLock_GB_hdpi.apk
FlickrSync_Home3_hdpi.apk
FlickrSync_Home3_hdpi.odex
FoxconnDLNA_Phone.apk
IndonesianPack.apk
MalaysianPack.apk
MapKing0908.apk
Muvee_Editor_Eclair_1.1.2_Commtiva.apk
TouchPal.apk (You will need to add another keyboard after removing this.)
UI-Android2.0-SCSL-1.2.2.7.apk
Click to expand...
Click to collapse
hi
sorry if this is off topic but i have rooted my 2.3.4 have removed most of the above is it ok to remove this too : FoxconnDLNA_Phone.apk
kshitij_bhatt said:
^hey thanx for trying... i too was supposing that lock screen might not work .. did u noticed any changes with the icons ..??
and @haree by flashing via recovery means via recovery .. this might should work with both cwm and stock rom
Click to expand...
Click to collapse
i only see change in lock icon
haree said:
hi
sorry if this is off topic but i have rooted my 2.3.4 have removed most of the above is it ok to remove this too : FoxconnDLNA_Phone.apk
Click to expand...
Click to collapse
Yes
This apk (I guess) helps in media sharing over wifi to any other computer/device.
So should not affect the normal functionality.
Napstar said:
Currently, we can not flash/install any update.zip using stock recovery. As I have mentioned before in some thread, for our device update zip signed using all available (test) keys returns error for signature verification in stock recovery.
Click to expand...
Click to collapse
actually i have the releasekey for FIH device, but i can't share that.
and i think Clockworkmod is more cool than stock recovery..
Sent from my FIH-FB0
tj_style said:
actually i have the releasekey for FIH device, but i can't share that.
and i think Clockworkmod is more cool than stock recovery..
Sent from my FIH-FB0
Click to expand...
Click to collapse
okk no problem bt seriously ur work with miui and cyanogen mod dude hats offf...
update the link its working now
okk here is a very quick bug fix... the stock lock screen had not been removed from this update so as for now if u update over any rc update or other custom rom you might not be able to unlock (Except by doing an invisible slide lol)
so dont update it over rc updates or cm or miui this is ment to be updated over stock rom ... rc updates support will be added in very next update...
bt will not support over cm and miui as i dont know much about these roms
Any reviews/screenshots for this ROM yet?
whyzee said:
Any reviews/screenshots for this ROM yet?
Click to expand...
Click to collapse
not yet becoz usb not working sorry and its not stable too...
Please remove set CPU app or ask permission from the Dev or it will be considered as warez
Swyped from my MI 410 using XDA App
mysteriousboy87 said:
Please remove set CPU app or ask permission from the Dev or it will be considered as warez
Swyped from my MI 410 using XDA App
Click to expand...
Click to collapse
thanx and yaa its a warez sorry i was unaware of the fact at that time bt its now removed
Installed the CM7 rom as usual but
my imei was changed to 000000000000000 and can not make calls and send sms
(Although not show signal, you can
access the internet). In the system
does not contain the efs folder and
had not backed up. Is there a
solution?
not want to change, I know it's
illegal, I "only" repair the original. Yes,
I googled before posting, but found
nothing satisfactory. thank you and sorry for my bad english.
that was a bug of the rom which was fixed
try flashing the firmware through odin
thanks for the reply. Had already
restored the 2.3.6 rom by odin and
several others with cwm and not
solved.
then its a big problem
dheeraj (dhlalit11) said:
then its a big problem
Click to expand...
Click to collapse
+1
I guess its a hardware problem.. something wrong with the motherboard.. if flashing stock ROM or custom ROM didn't solve it then i guess you have to take it to the SC..
Google gave me this: http://forum.xda-developers.com/showthread.php?t=1264021
- Via xda premium
a.cid said:
Google gave me this: http://forum.xda-developers.com/showthread.php?t=1264021
- Via xda premium
Click to expand...
Click to collapse
had tried this method but the efs
folder (And their archives) do not exist
in the system, unfortunately ...
I've been exploring the system files and view the log Custom recovery found the problem. Recovery was an error during the flash unfortunately could not solve the problem (yet) but anyway it was good to know where the error happened. Any help will be important, since that time my phone is just an MP3 player lol
Once again thank you and sorry for my english
Happened with me once and i think a trip to one of the samsung care center won't hurt much
Just be sure not to tell the people there that you flashed the cm7 custom rom on the device.
thousandecibels said:
Happened with me once and i think a trip to one of the samsung care center won't hurt much
Just be sure not to tell the people there that you flashed the cm7 custom rom on the device.
Click to expand...
Click to collapse
OK, thanks for the reply. I will try
a downgrade to Froyo in any
carrier to recover the efs and if it
fails it'll follow your advice. Thank
you very much
hi everybody i'm new in ur forum.
Hy guys.
I have a problem with my camera, samsung galaxy mini. i can't use it.
When i open the camera apps, suddenly appear
"Camera failed"
"ErrorMessageHandler.handleMessege(-1)"
Is there someone who can help me??
thank you
What rom are you using?Have you changed something abou camera?
Asbusto said:
What rom are you using?Have you changed something abou camera?
Click to expand...
Click to collapse
i use original rom...i don't change anything about camera...
Did this problem occur from the first time you bought your device?
Asbusto said:
Did this problem occur from the first time you bought your device?
Click to expand...
Click to collapse
no...he Was working well before...
What have you done just before that error occurs?e.g.:tweaks,mods...
if you don't know what's the problem i suggest you to wipe all from recovery (if you want you can use titanium to backup apps and restore them) or to make a clean install with odin
Faced this error long time ago it doesn't help even if you flash stock through Odin even the people at the service centre don't know how to fix this
Fortunately I got it fixed
Here what u do
Root sgm
Install cwm
Install cmx
Wipe
Install touchwizcm
Use for a day you will notice that sometimes it works and sometimes there is error
Now when camera works quickly install latest firmware through Odin and you are done.
Sent from my GT-S5570 using Tapatalk 2
So , I have tried every version of TWRP I can find Including PHILZ , and none of them will open zips to flash everything fails,Also my nandroid backups fail to flash as well after i do a factory reset........ md5s are fine.. Ive also made sure they aren't ZIP.ZIP.. Ive done a fairly extensive search to no avail.Has anyone come across this problem? .. frustrating... Im on the hk firmware S-off rooted
In twrp settings did you make sure that Theme testing isn't on.. Even So on that screen press default settings tab and reset twrp flashing settings... Just in case you have a sticky setting..
ya tried that too .. unfortunately it didn't work..... i don't think its a TWRP only problem because PHILZ wont work either .. the recovery just wont open any zips
heliguide62 said:
ya tried that too .. unfortunately it didn't work..... i don't think its a TWRP only problem because PHILZ wont work either .. the recovery just wont open any zips
Click to expand...
Click to collapse
Did you find a solution?
Nope still stuck.. got any ideas?
heliguide62 said:
Nope still stuck.. got any ideas?
Click to expand...
Click to collapse
A while back on a different device i had the same issue. I relocked the bootloader, and then went through the whole process of unlocking again (at htc-dev) reflashed the recovery did fastboot erase cache and reinstalled SU. was kind of a hassle but it worked. Worth a shot maybe.
Sent from my 831C using XDA Premium 4 mobile app
actually makes a certain amount of sense .. it might be a bootloader problem ,.. I think im going to ruu.. start over and if that doesnt work i will definitely give that a shot... THANKS!!!...
heliguide62 said:
actually makes a certain amount of sense .. it might be a bootloader problem ,.. I think im going to ruu.. start over and if that doesnt work i will definitely give that a shot... THANKS!!!...
Click to expand...
Click to collapse
Your welcome, i didnt go as far as an RUU, Just relocked the bootloader and did the unlock process over. but if you want to go all the way back i dont see any harm in it. Glad i was able to help man
Sent from my 831C using XDA Premium 4 mobile app
Or you can delete your TWRP folder from sdcard and reflash recovery...that has helped me before
Also what are you trying to flash somethings are not meant to be flashed in recovery some are fast boot/bootloader flash setups
heliguide62 said:
So , I have tried every version of TWRP I can find Including PHILZ , and none of them will open zips to flash everything fails,Also my nandroid backups fail to flash as well after i do a factory reset........ md5s are fine.. Ive also made sure they aren't ZIP.ZIP.. Ive done a fairly extensive search to no avail.Has anyone come across this problem? .. frustrating... Im on the hk firmware S-off rooted
Click to expand...
Click to collapse
any solution figured out yet for this??
im having the same issue here. i wasnt able to flash zips either.. . thought it was solved but i tried restoring a backup recently and came to find this issue again..
did u get it figured out if so please share your solution. thanks
here is a link to the thread i started about this issue maybe something in it can help u out if ur still searching. http://forum.xda-developers.com/showthread.php?t=2754466
try putting the zip on the internal storage card instead of the external storage card. seems to be working for me but not sure bout backups tho.
Original T said:
try putting the zip on the internal storage card instead of the external storage card. seems to be working for me but not sure bout backups tho.
Click to expand...
Click to collapse
Yeah that is because by default the m8 has external sdcard r/w protection I believe. So yeah moving it could work