I'm very frustrated with my player, I rooted it last year and flashed Pacrom venturi 2013-11-05 JB and sultan kernel, cwm 6.0.4.4, it wasn't easy it took me like 6 hours with lots of problems but at the end it was done. Now I tried to update it to KK and I've been trying for days. The first rom I tried was Pacrom venturi 20140407 with cwm 6.0.4.4 and I think sultan kernel and I had no problems except the wifi didn't work so I didn't backup and tried to flash it again but it didn't work because status 0 and status 7 and I tried several times to no vail so I downloaded one by one all the nightlys from April some of March, some from January, the one that used to work in from november, so I tried 4.4 - 4.3- 4.2.2 - 4.2 -4.1, pacrom, slimkat, cm, beanstalk, sultan kernel, Mercurius v5, Mercurius reborn, CM kernel, KKernel, CWM 6.0.4.4, 6.0.4.3, 5.0.2.7 and non worked. I've tried flashing it like 200 times of those, maybe like 5 times was successful but as soon I flash the kernel and then restart the screen its black nothing appears, I tried the build from july and the keyboard keep on crashing, so this is some of the thing that I've experienced
Most builds won't install because errors 0 and 7
"some symlinks failed status 7"
assert failed status 7
error status 4 installation aborted
E: Error in /sdcard/"name of rom".zip (status 0)
there're more that I didn't keep track of
I re-downloaded the roms twice to make sure it wasn't because a corrupt zip
If I successfully flash a rom, once I flash the kernel and fails, I can't re-flash the same built because errors start appearing
sometimes I get different versions of CWM depending of the rom.
presently I flashed CM 10.2 20131105 venturi, android 4.3.1 and gapps from july 2013 built-in kernel version 3.0.1.101-G70UEKI8 but the capacitive buttons don't work so I tried these kernels: Mercurius_kernel_usa_v5fixed, KKernel_R2.1_usa, Sultan-kernel-Venturi-r5-USA, Mercurius_Reborn_RC1_usa, pac-cm-USKernel-Mar-03, cm-10.2-USA-Kernel-REV5 but once I restart,the screen is black so I have to do a restore to just before the flashing of the kernel but can't use it like this.
Any sugestion? Any other kernels? I'm about to give up.
I'm on stock and love my YP-G70, everything just works and I can customize it as I like. Except for the times I load too many widgets I have no problems. I see NO reason to change to ROMs with less functionallity and lots of problems. 2.3 is THE most stable and most used version of Android. If it ain't broke don't fix it. Mine "looks" like the S4 and works like it too, why would I change? KISS
tapia818 said:
I'm very frustrated with my player, I rooted it last year and flashed Pacrom venturi 2013-11-05 JB and sultan kernel, cwm 6.0.4.4, it wasn't easy it took me like 6 hours with lots of problems but at the end it was done. Now I tried to update it to KK and I've been trying for days. The first rom I tried was Pacrom venturi 20140407 with cwm 6.0.4.4 and I think sultan kernel and I had no problems except the wifi didn't work so I didn't backup and tried to flash it again but it didn't work because status 0 and status 7 and I tried several times to no vail so I downloaded one by one all the nightlys from April some of March, some from January, the one that used to work in from november, so I tried 4.4 - 4.3- 4.2.2 - 4.2 -4.1, pacrom, slimkat, cm, beanstalk, sultan kernel, Mercurius v5, Mercurius reborn, CM kernel, KKernel, CWM 6.0.4.4, 6.0.4.3, 5.0.2.7 and non worked. I've tried flashing it like 200 times of those, maybe like 5 times was successful but as soon I flash the kernel and then restart the screen its black nothing appears, I tried the build from july and the keyboard keep on crashing, so this is some of the thing that I've experienced
Most builds won't install because errors 0 and 7
"some symlinks failed status 7"
assert failed status 7
error status 4 installation aborted
E: Error in /sdcard/"name of rom".zip (status 0)
there're more that I didn't keep track of
I re-downloaded the roms twice to make sure it wasn't because a corrupt zip
If I successfully flash a rom, once I flash the kernel and fails, I can't re-flash the same built because errors start appearing
sometimes I get different versions of CWM depending of the rom.
presently I flashed CM 10.2 20131105 venturi, android 4.3.1 and gapps from july 2013 built-in kernel version 3.0.1.101-G70UEKI8 but the capacitive buttons don't work so I tried these kernels: Mercurius_kernel_usa_v5fixed, KKernel_R2.1_usa, Sultan-kernel-Venturi-r5-USA, Mercurius_Reborn_RC1_usa, pac-cm-USKernel-Mar-03, cm-10.2-USA-Kernel-REV5 but once I restart,the screen is black so I have to do a restore to just before the flashing of the kernel but can't use it like this.
Any sugestion? Any other kernels? I'm about to give up.
Click to expand...
Click to collapse
check in the zip file if you have 4/3 files (file_contents boot animation meta-inf system
if yes go check if the 4 files are in the directory / home / beggining folder in the zip if no then extract it then select all 4 files and then send to zip
captpete1 said:
I'm on stock and love my YP-G70, everything just works and I can customize it as I like. Except for the times I load too many widgets I have no problems. I see NO reason to change to ROMs with less functionallity and lots of problems. 2.3 is THE most stable and most used version of Android. If it ain't broke don't fix it. Mine "looks" like the S4 and works like it too, why would I change? KISS
Click to expand...
Click to collapse
I agree, GB is a very stable version, but I own a phone with JB installed and sometimes I don't want waste my phone battery so I use the galaxy but when it had GB, it was a downgrade for me, it was slow and could not install chrome which it's a must for me and with other roms looks and runs great ( when it used to).
It has everithing
sabirchowdhury said:
check in the zip file if you have 4/3 files (file_contents boot animation meta-inf system
if yes go check if the 4 files are in the directory / home / beggining folder in the zip if no then extract it then select all 4 files and then send to zip
Click to expand...
Click to collapse
I tried to re-zip one build and when I tried to flashed it status 4 came up.
Right now I was able to flash pac_venturi-nightly-20140410.zip with gapps 2014-01-05 and its working but I think that I'm using the wrong kernel for the US version because when I restart my YP-G70 stays in the Pacrom logo or galaxy S Cyanogen (mod) like frozen.
Do anyone know of a rom and kernel for the us version of KK? or the kernel for this build that I flashed and seems working because I backed up and can restore it to before flashing the kernel thank you.
tapia818 said:
I tried to re-zip one build and when I tried to flashed it status 4 came up.
Right now I was able to flash pac_venturi-nightly-20140410.zip with gapps 2014-01-05 and its working but I think that I'm using the wrong kernel for the US version because when I restart my YP-G70 stays in the Pacrom logo or galaxy S Cyanogen (mod) like frozen.
Do anyone know of a rom and kernel for the us version of KK? or the kernel for this build that I flashed and seems working because I backed up and can restore it to before flashing the kernel thank you.
Click to expand...
Click to collapse
have you tried
http://forum.xda-developers.com/showthread.php?t=2568478
Related
Hey guys,
I (was) on jokers CM9 (before recent update). I backed up and then attempted to install the new version... So here's the problem, I can't install Gapps PERIOD. It failed for jokers CM9, as well as MIUI v4. I'm not new to installing ROMs, I know I did all the wipes properly etc and fixed permissions just in case. I have tried the last 3 releases of Gapps as well. The ROM is good, boots fine and all (MIUI and CM9) but no Gapps in any situation. The only time I've been able to get it to stick is using the Options Chooser MIUI Installer, worked great. Ive downloaded the files mutiple times with no problems... no idea what I could be missing! Anyone else had this problem/fix?
did you update your CWM recovery to 6.0.x.x? That's what i did before flashing jokers CM10 alpha build and it wouldn't let me install GAPPS either. I just reverted back to an earlier version and it worked fine.
R2DeeTard said:
did you update your CWM recovery to 6.0.x.x? That's what i did before flashing jokers CM10 alpha build and it wouldn't let me install GAPPS either. I just reverted back to an earlier version and it worked fine.
Click to expand...
Click to collapse
Yes! I actually did right before I started flashing the new stuff... thanks!
Still having trouble ... downgraded back to 5.x. (joker v3). Now it seems like data/cache arent wiping. When trying to flash clean, after doing all wipes I still end up with the same install.
fabe0334 said:
Still having trouble ... downgraded back to 5.x. (joker v3). Now it seems like data/cache arent wiping. When trying to flash clean, after doing all wipes I still end up with the same install.
Click to expand...
Click to collapse
I use photon3 recovery. Works great. Be sure to flash twice if gapps don't show up. If still nothing then you must have a bad download of gapps.
If this works let me know.
Sent from my SGH-I777 using XDA
[Q] What kind of "loop" do i have? Happens with AOKP devil and glitch ICS and CM10
First I know the phone is not bricked. I can and have repeatedly ODINed to stock EH03, remembering to atlas and repartition as per droidstyle's guide. The problems begin when I go through the rest of the guide section 4, to get and ICS AOKP rom running. (This is staging for my question to be complete. Question at bottom.)
For whatever reason the phone was stuck to only boot into (red) recovery. I had the AOKP rom MS6-devil before and I think flashed another different devil kernel over that. The phone has been completely stable for months now. I tried data wipe/reset and wipe cache, and dalvik too. It still only rebooted to red recovery (sorry don't recall the exact version). This is when i decided to ODIN and start fresh.
Maybe some side questions. Is it ok to flash different devil kernels on the devil kernel rom? I assume yes but I just needed to run through my check list. When I ODINed back to stock did that automatically restore the phone to a stock kernel as well?
So the phone ODINs fine every time and ODINing cmw4 for CW7 and GB bootloaders too. (BTW when i flashed ICS rom several month back i dont think the guild had anything about ODINing bootloaders. Is this new?). 3 finger works and I'm in blue recovery 4, i wipe data and dalvik (I've done this more than 5 times some i also tried a cache wipe with same results).
What kind of boot loop is this?
I flash the ICS rom zip that i want and it starts but the status bar on the phone make a small amount of progress then goes black, reboots to the flash the Samsung logo then goes to some splash screen that shows Icy Glitch Kernel V14 if i try the AOKP M6 official, or a splash screen of Devil Kernel if i flash AOKP M6-devil or even with CM10 i see the splash screen of cyanogenmod. If i let the phone sit on the screens for a long while all i see is a continual booting to these splash screens.
I have mucked something up with the kernel and i thought ODIN would reset that each time. If I can know what kind of boot loop i face i can go to find the right threads or make a post in the right place to get this resolved.
Actually it's normal for that to happen, after you start the install it should reboot the phone to an updated recovery and continue the installation from there. At least that's what it did for me when coming from stock. How long did you wait? Are you getting any errors? If you're still using the stock sd card that could be your problem right there. Also, I highly recommend trying a JB rom, ICS is pretty stale at this point. AOKP just released JB Milestone 1
Good tips. I didn't know that's what it should look like. I was flashing for many hours and waited 20-30 minutes. The only happenings on screen were the splash screens flashing occasionally as if the phone were looping. Im guessing now that's normal in the flashing process. I've flashed the same roms before months ago and probably the process on screen I just forgot. Ill try again later when I have time and try some jb action and report back.
When going from stock to ics are you first flashing ths build 2? There are many versions of devil available some are built for ics and aome for jb only. It's important to know which one you are dashing cause the jb devil kernels have a specific partition layout needed to get jb to run on the fascinate. I could be wrong but anything higher than 1.5.xx is jb specific.
The devil rode a unicorn named jelly bean
forsakenone said:
When going from stock to ics are you first flashing ths build 2?
The devil rode a unicorn named jelly bean
Click to expand...
Click to collapse
You know I think that is it. I just blanked on doing that. I have build 1 and 2, b/c sometimes one works and one doesn't. I think I used 1 this time, but the first time I flashed ics i used build 2. Any way thanks. I am checkin out jb now too. cm10 is working great.
You didn't miss the step (to flash Build2 between EH03 & AOKP/CM10), the step was missing (temporarily) from the guide because some have found it to be unnecessary. I had the same bootloop as you when I didn't go through Build2 on the way to AOKP. Seems like the phone attempts to boot normally rather than into recovery to finish the installation of AOKP/CM10, and can't because it is midway through the installation. So did you state you had the problem when flashing CM10 as well? That's interesting, since some can skip going through Build2 and some can't. I thought maybe AOKP required it and CM10 did not... still trying to figure out what is different between phones that require it and those that don't.
Yeah I had it happen on cm10 too. I tried again but only flashed cm10 and no strange looping like I described. But I didn't flash any build before cm10.
Ok, since I am not allowed to post in the dev section, might as well ask here.
I was trying to flash the Carbon (unofficial) rom for Xperia 2011 devices http://forum.xda-developers.com/showthread.php?t=2337174. At that time I was running on CM10 & nAa 3.4.45 kernel, my phone is Sony Ericsson Live (build .587).
First, I had the "Status 7 error" while installing, after removing the the first three lines of update-script , that fixed it for others, but not for me. The installation still failed but this time no status shown.
I removed the boot.img from the zip file as suggested & also changed the updater-script provided by another dev in the thread, no dice.
I reverted to stock for now....but I'm curious as to know what I did wrong. Carbon rom & another rom (Cyanogenmod Timespace) are two roms I cann't seem to flash. But others seem to be doing fine.
You can try installing the rom without wiping system, then you won't get the status 7 error and you don't have to delete the lines
If that's not working open the zip again, delete the three lines using notepad++ (or scite on linux), save it and repack the zip using 7zip with the default settings
Hmmm...."status 7 error" doesn't mean that the installing the ROMs is a failure...since the ROMs are made for Mango, did you flash the dev files for LWW after you have flash the ROMs???? flash dev files is important for your LWW...without it then you phone will get bootloop....
iPusak Gaoq™ said:
Hmmm...."status 7 error" doesn't mean that the installing the ROMs is a failure...since the ROMs are made for Mango, did you flash the dev files for LWW after you have flash the ROMs???? flash dev files is important for your LWW...without it then you phone will get bootloop....
Click to expand...
Click to collapse
Well, I couldn't flash the rom, not even once. Every time I tried there was an error, like I said, I was able to get rid of the status 7 error using the script another guy provided, but the installation was a failure nonetheless. Only this time, there was no reason shown. It just said, installation aborted.
mihahn said:
You can try installing the rom without wiping system, then you won't get the status 7 error and you don't have to delete the lines
If that's not working open the zip again, delete the three lines using notepad++ (or scite on linux), save it and repack the zip using 7zip with the default settings
Click to expand...
Click to collapse
Already did that, but still cannot install. But yes, it didn't show "Status 7" that time.
alvi.mahmud said:
Well, I couldn't flash the rom, not even once. Every time I tried there was an error, like I said, I was able to get rid of the status 7 error using the script another guy provided, but the installation was a failure nonetheless. Only this time, there was no reason shown. It just said, installation aborted.
Click to expand...
Click to collapse
Hmmm...you misunderstand my point....even if the "status 7 error" came up, doesn't mean that you fail to install the ROMs...some ROMs has "status 7 error" came up while installing but still the ROMs install is successful...
try installing the ROMs without modified the scripts then flash the dev files after it...don't boot between both flashing....if your phone will got bootloop then make sure you use the right kernel for the ROMs....
like Mihahn said, if wipe system give you error the flash is without full wipe...
iPusak Gaoq™ said:
Hmmm...you misunderstand my point....even if the "status 7 error" came up, doesn't mean that you fail to install the ROMs...some ROMs has "status 7 error" came up while installing but still the ROMs install is successful...
try installing the ROMs without modified the scripts then flash the dev files after it...don't boot between both flashing....if your phone will got bootloop then make sure you use the right kernel for the ROMs....
like Mihahn said, if wipe system give you error the flash is without full wipe...
Click to expand...
Click to collapse
mmm....stuck in bootloop yet again. This is getting tiresome. Well, let's see what can be done.
Another thing, I had CWM 5 installed, but the nAa kernel had a CWM 6 (I think), so during bootloop....at times they just toss me from one version of the mod to other. Does what I said made any sense?!!
Ok, got it to work! (I don't know what I did though). But my internet is down. I have this same problem in all CM build roms, is this a problem in general?
alvi.mahmud said:
Ok, got it to work! (I don't know what I did though). But my internet is down. I have this same problem in all CM build roms, is this a problem in general?
Click to expand...
Click to collapse
Hmmm...what do you mean "my internet is down"??? 2G+3G internet or wifi??? both work fine on my phone....if 2G+3G then download the setting from your services provider the proper setting....some APN setting in CM build is outdated...
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
Hello all...
First of all, I'm not very experienced at flashing roms.. HOWEVER, I've flashed several roms across multiple phones over the years and have yet to brick a phone.. so I am fairly familiar with recoveries, etc... But I've run into a "wall" and don't know what to do.... hopefully someone can shine some light to my issue.
My TMobile S5 is currently running Twisted Lollipop (v7?).. but I want to switch now to a CM based rom. I had PREVIOUSLY used a CM based rom (a nightly) dated back from June before I switched to Twisted. My phone is rooted.. and I am using TWRP recovery. However, NOW if I do a full on wipe... and try to flash a rom (so far only the latest nightlies).. it seems to do some partitioning stuff.. and then stops saying COMPLETE... I never get the typical "install" text you see when installing a rom in recovery.. If when it's finished.. when I click REBOOT.. TWRP asks me if I want to.. and warns NO OS is installed..
I was able to load a backup of a CM 12.1 based build from a June nightly I had.... but I get the same thing if I go thru the CM updater. I honestly haven't tried to flash anything else..
Am I missing or overlooking something.. I'm on the DOB1 firmware.
Thanks
aenielida