Related
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
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
What does it do?
Sent from my CM10.3 Galaxy S3.
This fix includes one missing binary which some specific cameras require in order to be able to be used.
If you don´t have any trouble starting the camera app, using the camera, you don´t need to flash this zip Even if everything works fine and you do install this fix, it wouldn´t harm your system
habylab said:
What does it do?
Sent from my CM10.3 Galaxy S3.
Click to expand...
Click to collapse
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
g.ott said:
just flashed it, doesn`t work for me unfortunately. :crying: :crying: :crying:
i have this problem you told of since a very long time and i really can't get rid of it. makes me fckn sick. i could cry on and on.
what else is possible to do? every litte hint is very much appreciated.
Click to expand...
Click to collapse
If that fix not help you can maybe make a camera fw upgrade.
[tapatalk]printed, scanned and faxed...[/tapatalk]
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Gorgtech said:
There are more binaries available, the one I included is a more common one. Samsung uses 2 different cameras ( Sony or Samsung ).
Does your camera work 100% with a Stock ROM ? If so, have a closer look in /data/cfw and show me what you find inside ( eg. SlimISP_xx.bin ).
Flash a Stock Firmware, make sure to copy the file and add it here as a zip file. By installing custom ROMs, your cfw folder will be empty most the time if these files are not added by the ROM itself.
Click to expand...
Click to collapse
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
g.ott said:
hi guys,
thx a lot for your words. here is what i've done:
i just flashed a stock rom and the camera works. then i installed cf root and root explorer but /data/cfw is an empty folder. so i can`t copy anything here.
with the custom rom and the cam not working i had a file like SlimlSp00.bin (or something similar) in this particular folder but not now.
what to do now or did i misunderstand something?
Click to expand...
Click to collapse
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Gorgtech said:
Just out of curiosity, did you try to remove this file ? Maybe your camera tries to load this binary though it´s not suitable for your model. You can try to create a different folder and first copy the found bin ( just to have a spare copy ), remove SlimlSpxxx out of your data/cfw folder.
Wipe your Dalvik Cache and restart the ROM
Click to expand...
Click to collapse
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
g.ott said:
this idea didn't come up of course
but i just tested it. i already had my custom rom backup restored. i moved the SlimlSP_BH.bin to my ext sd, so that /data/cfw was empty, rebooted to recovery, wiped dalvik and it doesn't worked. second try i wiped cache and dalvik and it also doesn`t work.
Click to expand...
Click to collapse
alright, i for sure will give you every information you need.
under "phone/cam fw ver check" i see
rear camera
cam fw ver: GDF
phone fw ver: GDFI02
front camera
cam&phone fw ver: S5K6A3
"Phone/Cam FW Write" isn't available in that form. options with "write" are only "phone to cam fw write (rear)" (but this is greyed out so i can't touch it) and "fw write count".
Gorgtech said:
If your camera doesn´t work with this binary, you may need another one..and there are lots of them to try but you have to chose one which is suitable for a Sony or a Samsung camera Well, there is a easier way out if you try to upgrade your camera firmware.
Before we proceed, I need some details first, which type of camera you have in order to pick up a suitable binary.
1) Dial *#34971539#
2) pick up this option: "Phone/Cam FW Check"
3) Show me what you see
4) Chose this option: "Phone/Cam FW Write"
A short explanation :
GDxxx = Sony
ZFxxx = Samsung
Click to expand...
Click to collapse
hi gorgtech, are you still here?
I´m still here but I´m not quite sure how to help you out. There is another way to enforce an upgrade of your Firmware but I´m not sure if this would work out for everyone.
I´ll see what I can do later and prepare a zip file for you
g.ott said:
hi gorgtech, are you still here?
Click to expand...
Click to collapse
Gorgtech said:
I want to offer you a little fix for those of you who actually experience this problem. On some Samsung based ROMs, some people complain about not working cameras, no matter how often they tried to install a ROM after several wipes. This error may occur in case your camera uses a different firmware.
Most people however won´t experience this error.
I´ve created a little Fix which is actually very easy to apply as a flashable zip. It was intended to be used with my Samsung Galaxy S3 ROM, it may also work with every other Samsung based ROM
Here is the link: Camera Fix for Samsung based ROMs
Simply install this file through your custom recovery
Just in case this patch should not work for everyone, leave me a comment and I´ll see what I can do :angel:
Click to expand...
Click to collapse
about time someone done this! thanks! i thought i corrupted the drivers, but thats for the fix!
Dude, brilliant, this works on KitKat roms also, I have spread the word and linked your thread to the benefit of all.
Thank you
Sent from my GT-I9300
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
ayoubij said:
does this really work? can someone add it to aosp code then? @XpLoDWilD @CarbonDev
Click to expand...
Click to collapse
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
metalgearhathaway said:
Well it works perfectly for me, but @Moster2 says the md5 checksum is identical to the files already in place, but it works. I'm both happy but mildly confused! If you get the issue it's obviously with trying! You only need to flash the rom to remove it, so it's of no concern to try
Sent from my GT-I9300
Click to expand...
Click to collapse
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
metalgearhathaway said:
I'm wrong, this method went wayward for me in the end :banghead:
Sent from my GT-I9300
Click to expand...
Click to collapse
Damn!
Sent from my Linaro SM'd CM11 Galaxy S3, with Archi's kernel. A proud Googy Beta tester.
Well done. Works perfectly.
I tried just about everything I could find regarding fixing the camera in my S3, including manually replacing the Camera2.apk and this is the first fix I tried that actually works. Thanks for putting the time and effort in to solve this annoying problem.
Unable to install MIUI v5 by sijav.
I am LB with 4.2.2(ROOTED) and XZDUALRECOVERY
I am getting boot-loop.
Followed the instructions perfectly as per said.
NOT A NEWBIE!
Same to me…my phone(c5502) also unable to flash the rom…following all the instruction and even redownload the file also no luck…(ps:my xperia arc s or xperia v just one flash than done)but still u can try the MIUI apps called "Miui Express",just feel like using miui rom.This apps include launcher, contact, message, phone, lockscreen even themes too~
Sent from my C5502 using XDA Premium 4 mobile app
Joncat24 said:
Same to me…my phone(c5502) also unable to flash the rom…following all the instruction and even redownload the file also no luck…(ps:my xperia arc s or xperia v just one flash than done)but still u can try the MIUI apps called "Miui Express",just feel like using miui rom.This apps include launcher, contact, message, phone, lockscreen even themes too~
Sent from my C5502 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for reply. Can you post on sijav's thread? I am not able to post there because I joined here recently!
Daedroza said:
Thanks for reply. Can you post on sijav's thread? I am not able to post there because I joined here recently!
Click to expand...
Click to collapse
what?
you're getting bootloop? @Daedroza and @Joncat24 what version did you flashed?
I have got feedback that this works, I also my self flashed with every possible options!
ALSO did you come from 4.2.2? if not wait I'm making a package ftf for you guys to flash and it will works
instruction in main thread updated.
sijav said:
what?
you're getting bootloop? @Daedroza and @Joncat24 what version did you flashed?
I have got feedback that this works, I also my self flashed with every possible options!
ALSO did you come from 4.2.2? if not wait I'm making a package ftf for you guys to flash and it will works
instruction in main thread updated.
Click to expand...
Click to collapse
Yup...downgrade to 4.2.2, root and also install recovery.Both 4.6.6 and 4.5.23...i'm even go to ur Miui forum to redownload the file but still same get bootloop wont boot...4.5.23 english and multi language also tried...if I select full wipe (in aroma),install till 40% than black out...(bootloop).The new 4.6.6, successfull install (if I select full wipe in aroma option, it happen same as 4.5.23)but the rom can't get root permission...showing system ui fc and the network operators showing wrong networking...if I reselect the network operators it show correct operators but the name just won't show the correct one that I had selected...
Ps:both before installing the rom i'm already full wipe the phone by myself coz if I select full wipe in aroma option it will cause bootloop...
Sent from my C5502 using XDA Premium 4 mobile app
sijav said:
what?
you're getting bootloop? @Daedroza and @Joncat24 what version did you flashed?
I have got feedback that this works, I also my self flashed with every possible options!
ALSO did you come from 4.2.2? if not wait I'm making a package ftf for you guys to flash and it will works
instruction in main thread updated.
Click to expand...
Click to collapse
Thanks for reply sijav.
I used 4.2.2 customised INDIA as base rom. I installed root then recovery. I flashed your 4.6.6 MIUI file. Did clean wipe in Aroma installer also. After the process ended the phone booted with sony logo then MIUI logo and then restarted again(bootloop)
***I will try this again in next 24 hours And will post the results here. Thanks for your work
Sent from my C5502 using XDA Free mobile app
If I'm not mistaken, if you're on locked bootloader you should first format system through recovery then install miui rom, it was the same way in locked Arc S
Sent from my C5502 using XDA Free mobile app
@sijav also if you are uploading your own 4.2.2 ftf can you please upload it on google drive?
It would be a great relief if you could upload all your further builds on google drive and share it here. Gives more 2mb/s speed so we could tell you instantaneously the build is flawless or not.
Sent from my C5502 using XDA Free mobile app
Daedroza said:
@sijav also if you are uploading your own 4.2.2 ftf can you please upload it on google drive?
It would be a great relief if you could upload all your further builds on google drive and share it here. Gives more 2mb/s speed so we could tell you instantaneously the build is flawless or not.
Sent from my C5502 using XDA Free mobile app
Click to expand...
Click to collapse
hi, @Joncat24 this is really strange! both things, network wrong? I'm not sure! everything is working here, system ui fc? you don't have root access? can you give me logcat? else I can't do anything because everything is working with me and I'm not sure about your problems so please give me logcat.
System will format on aroma before installing so you no need to do that!
alright here's my theory: I'm assuming that you all have tried with philz touch recovery, maybe the philz touch recovery is not good! (as you can't flash latest cm with it!!) please use ClockWorkMod (the vanilla recovery) from NDR Utils app and give me the results. it should work after that!
oh and forget everything about 4.2.2! I can't get access to my old 4.2.2 ftf file anymore! sorry I can't upload anything... and about uploading in google drive, well google drive has banned my whole account many times because many users have downloaded huge files. So I'm trying not to put anything on google drive. also my upload speed is less than 14 kbps so I'm not just posting things on net without testing it with every aspect myself! (As I hate to spend more than 1 day to upload it again) so even if you tell me that my build is broken even if I fixed it it makes me 2 days in avarage to upload both eng and multi rom into servers.
sijav said:
hi, @Joncat24 this is really strange! both things, network wrong? I'm not sure! everything is working here, system ui fc? you don't have root access? can you give me logcat? else I can't do anything because everything is working with me and I'm not sure about your problems so please give me logcat.
System will format on aroma before installing so you no need to do that!
alright here's my theory: I'm assuming that you all have tried with philz touch recovery, maybe the philz touch recovery is not good! (as you can't flash latest cm with it!!) please use ClockWorkMod (the vanilla recovery) from NDR Utils app and give me the results. it should work after that!
oh and forget everything about 4.2.2! I can't get access to my old 4.2.2 ftf file anymore! sorry I can't upload anything... and about uploading in google drive, well google drive has banned my whole account many times because many users have downloaded huge files. So I'm trying not to put anything on google drive. also my upload speed is less than 14 kbps so I'm not just posting things on net without testing it with every aspect myself! (As I hate to spend more than 1 day to upload it again) so even if you tell me that my build is broken even if I fixed it it makes me 2 days in avarage to upload both eng and multi rom into servers.
Click to expand...
Click to collapse
No problem. Going to try this with Vanilla CWM. If any one wants Google Drive FTF links I shall upload it for them.
Will post the result in three hours thanks sijav.
BTW which version of recovery? 6.0.4.5 right?
Result.
Result :
Flashed fresh 4.2.2 Customized India FTF. Installed SuperSU ROOT. Flashed XZDUALRECOVERY. Selected 6.0.48 CWM-Based recovery as told.
Selected the zip to be flashed. Selected Full Wipe in AROMA!
Installation started > Stopped at 1% > Device restarted and stopped at SONY LOGO.
I am on locked boot loader and I think that's what the problem is!
- NEW
Used PhilzTouch Recovery > INSTALL Complete.
I clean wiped then clicked on INSTALL NEW ROM, which again clean data, cache. Seems to work with one bug "ALL CHECK POINTS REACHED". It is not going from my Notifications menu!
Daedroza said:
Result :
Flashed fresh 4.2.2 Customized India FTF. Installed SuperSU ROOT. Flashed XZDUALRECOVERY. Selected 6.0.48 CWM-Based recovery as told.
Selected the zip to be flashed. Selected Full Wipe in AROMA!
Installation started > Stopped at 1% > Device restarted and stopped at SONY LOGO.
I am on locked boot loader and I think that's what the problem is!
Click to expand...
Click to collapse
EXACT same results. I fear though that if i unlock my bootloader and MIUI fails again, PCC won't be able to rescue me with firmware repair! :crying:
C5502 with root (TowelRoot method), XZdualRecovery, stock 4.3 (waiting to go back down to 4.2.2 INDIA release again). Any hints on how to fix this? Am really interested in trying MIUI, but if Xperia ZL roms work perfectly, then i'd like to try one of those...if there's one as interesting as MIUI
Did you try to format system partition?
Adiyel said:
EXACT same results. I fear though that if i unlock my bootloader and MIUI fails again, PCC won't be able to rescue me with firmware repair! :crying:
C5502 with root (TowelRoot method), XZdualRecovery, stock 4.3 (waiting to go back down to 4.2.2 INDIA release again). Any hints on how to fix this? Am really interested in trying MIUI, but if Xperia ZL roms work perfectly, then i'd like to try one of those...if there's one as interesting as MIUI
Click to expand...
Click to collapse
Yes. Use PhilZ, don't select Everything Wipe in Aroma and try installing.
If possible try installing twice! mine worked at second instance!
PROBLEM IS WITH RECOVERY AND NOT MIUI!
Daedroza said:
Yes. Use PhilZ, don't select Everything Wipe in Aroma and try installing.
If possible try installing twice! mine worked at second instance!
PROBLEM IS WITH RECOVERY AND NOT MIUI!
Click to expand...
Click to collapse
damn! you were right,
formating data partition seems not a good idea in philz recovery!!
I'm gonna remove wipe in aroma and let users do it for next release OR find a way to remove things from data manually
thanks a lot for letting me know about this one.
have fun guys
Finally
sijav said:
hi, @Joncat24 this is really strange! both things, network wrong? I'm not sure! everything is working here, system ui fc? you don't have root access? can you give me logcat? else I can't do anything because everything is working with me and I'm not sure about your problems so please give me logcat.
System will format on aroma before installing so you no need to do that!
alright here's my theory: I'm assuming that you all have tried with philz touch recovery, maybe the philz touch recovery is not good! (as you can't flash latest cm with it!!) please use ClockWorkMod (the vanilla recovery) from NDR Utils app and give me the results.
Click to expand...
Click to collapse
YES!!! Finally...finally i had successful to flash Miui on my Xperia ZR!!:good:Actually i was already want to give up...but lucky i did give up... I just try not to use Philz Touch recovery...it works!! U are right...is the recovery problem...but my Xperia V was successful install the rom by using Philz Touch recovery...thats strange... I just use ClockWorkMod to flash and before flash the rom, i just wipe cacheand format system and it works...even i had mentioned before that all the problem all gone~~ :good::laugh: thanks~
Q&A for [ROM][UB][4.4.4][Z]GZR Validus 6.2 ROM official builds {Linaro+Sabermod}
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 [ROM][UB][4.4.4][Z]GZR Validus 6.2 ROM official builds {Linaro+Sabermod}. 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!
One of the greatest rom here in XZ.. but i have a problem while holding the notification on the notification area. It keeps FC.. can you fix the problem pls?
RainFreecs said:
One of the greatest rom here in XZ.. but i have a problem while holding the notification on the notification area. It keeps FC.. can you fix the problem pls?
Click to expand...
Click to collapse
well, u have to understand all devs works like crazy since lollipop is out, so i will provide updates but will be as all others; really busy...will see on next update what i can do.
i can't install the gapps, says "E:/ cannot load volume/misc
Does Stereo Sound Mod working ?
geekeys49 said:
i can't install the gapps, says "E:/ cannot load volume/misc
Click to expand...
Click to collapse
Because cm recovery is broken, for ALL DEVICES...u should have read that in threads, its mentionned everywhere.
U can flash from sideload, or else u fastboot flash a KK kernel, u flash what u need to, and u fastboot flash back lp kernel.
Guys i can't install twrp recovery
fastboot error
FAILED (remote: Command not allowed)
anyone know how to install this?
adipPL said:
Guys i can't install twrp recovery
fastboot error
FAILED (remote: Command not allowed)
anyone know how to install this?
Click to expand...
Click to collapse
wrong thread...ask this in appropriate forum.
did u installed fastboot drivers?
u installing from device or pc?
hey guys is it really needed to flash a recovery to the fotakernel or can I also just flash kk kernel when I wan't to flash something ? btw I'm not really in a hurry to try this rom so maybe I should just wait for this problem to be fixed so that the recovery is working well without having to flash a recovery to the fota kernel?
mic009 said:
hey guys is it really needed to flash a recovery to the fotakernel or can I also just flash kk kernel when I wan't to flash something ? btw I'm not really in a hurry to try this rom so maybe I should just wait for this problem to be fixed so that the recovery is working well without having to flash a recovery to the fota kernel?
Click to expand...
Click to collapse
its not mandatory no...u can fastboot flash KK boot.img from cm or whatever rom; then u flash needed stuff, then u fastboot flash included kernel in order to get a working rom
Alx31TLse said:
its not mandatory no...u can fastboot flash KK boot.img from cm or whatever rom; then u flash needed stuff, then u fastboot flash included kernel in order to get a working rom
Click to expand...
Click to collapse
Okay thanks, I will flash the rom soon but this problem with the recoveries will be fixed eventually right? I'm not asking for a ETA or something because I understand that it's difficult to fix it and that it's not a small problem cause something vital is broken ofcourse.
mic009 said:
Okay thanks, I will flash the rom soon but this problem with the recoveries will be fixed eventually right? I'm not asking for a ETA or something because I understand that it's difficult to fix it and that it's not a small problem cause something vital is broken ofcourse.
Click to expand...
Click to collapse
its cm recovery tho, i can't tell...but we (some z devs) working on twrp, to make it boot as it was before....
Alx31TLse said:
its cm recovery tho, i can't tell...but we (some z devs) working on twrp, to make it boot as it was before....
Click to expand...
Click to collapse
Okay good to hear, yesterday I also flashed this rom btw it's super smooth and a amazing rom:good: but the only thing I have a problem with right now is the random reboots that occur. So maybe I should provide a log to you, only I don't really know how to do that because I never had to provide logs haha. the reboots occur at times when I turn my wifi on or off or other moments but it could also be something else I really don't know actually why it happens sometimes and the other moments everything is as it should be so......
mic009 said:
Okay good to hear, yesterday I also flashed this rom btw it's super smooth and a amazing rom:good: but the only thing I have a problem with right now is the random reboots that occur. So maybe I should provide a log to you, only I don't really know how to do that because I never had to provide logs haha. the reboots occur at times when I turn my wifi on or off or other moments but it could also be something else I really don't know actually why it happens sometimes and the other moments everything is as it should be so......
Click to expand...
Click to collapse
since nobody reported that, that means its becuz of your apps or your data restore
clean flash the rom, and don't restore any apps or settings, if no random reboot for 12 hours minimum; then its becuz of you, not me :angel:
Alx31TLse said:
since nobody reported that, that means its becuz of your apps or your data restore
clean flash the rom, and don't restore any apps or settings, if no random reboot for 12 hours minimum; then its becuz of you, not me :angel:
Click to expand...
Click to collapse
Thank you for your help and advice btw I shall look into it myself and try to fix it, so far it didn't occur again so I think I'm good for now. Really great rom so far, the best lollipop rom i've tryed till date! it's very smooth and nice overall.:good:
Hello everybody,
I have got a little problem.
The device has lost the recovery.Wenn the device is booting to it,the screen flickers but it isn't displayed anything,the green lamp lights. The recovery is Philz touch,respectivly it was.
Anybody any idea?
Thanks
hansmerz said:
Hello everybody,
I have got a little problem.
The device has lost the recovery.Wenn the device is booting to it,the screen flickers but it isn't displayed anything,the green lamp lights. The recovery is Philz touch,respectivly it was.
Anybody any idea?
Thanks
Click to expand...
Click to collapse
stop being a noob and become a newbie bro! by reading in threads or using search button...philz , dual or whatever from stock roms won't work on my roms.
u must fastboot flash a cm11 kernel and make your wipes+ rom and gapps flashing from there. cm recovery is broken for eveyone.
and on cm/aocp roms, recovery in included in kernel so if u flash my rom and the kernel is included in zip pacjage, for sure u gonna loose recovery!
Nice work.
Just flashed this ROM and no bugs at all till now.
Hey there!
I flashed the v7. it starts fine , but after a few mins i get the "system ui" has crashed :/
Being fixed...wait for next build
Hello!
Could someone port the latest TWRP to our Xperia V, please please please? ))
The latest 2.8.5 FOTAKernel Image for mint is working almost perfectly on our tsubasa, the only issue is it does not allow to flash serious zips, like ROM zips, because of the device check (it says I have mint and the flashable zip is only for tsubasa ). So could someone modify this device check to tsubasa somehow? And after that I guess it would good to go, since the 2 device, mint and tsubasa is almost the same in everything. :fingers-crossed:
Best regards,
Zalan
banciii said:
Hello!
Could someone port the latest TWRP to our Xperia V, please please please? ))
The latest 2.8.5 FOTAKernel Image for mint is working almost perfectly on our tsubasa, the only issue is it does not allow to flash serious zips, like ROM zips, because of the device check (it says I have mint and the flashable zip is only for tsubasa ). So could someone modify this device check to tsubasa somehow? And after that I guess it would good to go, since the 2 device, mint and tsubasa is almost the same in everything. :fingers-crossed:
Best regards,
Zalan
Click to expand...
Click to collapse
You might try the attached one.
I've unpacked the image and modified the default.prop file.. replaced every occurence of "mint" by "tsubasa"
However, I haven't tested it yet.
By the way, this is no flashable zip.. I had to compress the file because of XDA's file size limitation for .img files.
banciii said:
Hello!
Could someone port the latest TWRP to our Xperia V, please please please? ))
The latest 2.8.5 FOTAKernel Image for mint is working almost perfectly on our tsubasa, the only issue is it does not allow to flash serious zips, like ROM zips, because of the device check (it says I have mint and the flashable zip is only for tsubasa ). So could someone modify this device check to tsubasa somehow? And after that I guess it would good to go, since the 2 device, mint and tsubasa is almost the same in everything. :fingers-crossed:
Best regards,
Zalan
Click to expand...
Click to collapse
It has nothing to do with "serious zips". Read this if you like.
WhiteNeo said:
You might try the attached one.
I've unpacked the image and modified the default.prop file.. replaced every occurence of "mint" by "tsubasa"
However, I haven't tested it yet.
By the way, this is no flashable zip.. I had to compress the file because of XDA's file size limitation for .img files.
Click to expand...
Click to collapse
Thanks again, almost. With your img I can flash CM zip again, but gapps buggy. It installs without error, but after boot, every single google apps force close and can't use the ROM. Can't figure it out why, I made full clean install. Other features looks fine so far. But huge thanks for the try anyway.
banciii said:
Thanks again, almost. With your img I can flash CM zip again, but gapps buggy. It installs without error, but after boot, every single google apps force close and can't use the ROM. Can't figure it out why, I made full clean install. Other features looks fine so far. But huge thanks for the try anyway.
Click to expand...
Click to collapse
Wanna send a logcat of the fc? ^^
Maybe it's an issue with a recovery binary or something..
WhiteNeo said:
Wanna send a logcat of the fc? ^^
Maybe it's an issue with a recovery binary or something..
Click to expand...
Click to collapse
Ohh, did not think u would take care of it beside your other tons of work thanks, will try tomorrow ))
banciii said:
Ohh, did not think u would take care of it beside your other tons of work thanks, will try tomorrow ))
Click to expand...
Click to collapse
If it's easy to fix I'll try it. But I can't promise anything.
WhiteNeo said:
If it's easy to fix I'll try it. But I can't promise anything.
Click to expand...
Click to collapse
Just tried the backup-restore option with every partitions (dalvik, cache, system, data, secure). Dunno what exactly, but something is very buggy. I don't get any error during the backup, but after the restore, my phone does not start. When I choose system reboot after the restore I only get black blank screen after the sony kernel logo, then I get a reboot after about half minute and back into the recovery automatically.
So after that, I tried the install which I mentioned earlier. I wiped everything again and installed only 0214 nightly CM12 build. Booted, worked fine. Then installed the latest stock (PA) gapps, reboot and the gapps force closes started. Here is the logcat, but I guess it's not that case anymore since the buggy backup/restore function.
https://www.dropbox.com/s/b5lgn60s2l5xp8b/twrp-gapps.txt