• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Sprint] How To UpGrade To JellyBean

No roms yet, but there are people that are working hard toward this goal. btw Are you rooted and trying to get the update?
 
We have officially rooted the Jelly Bean Victory so as soon as I get the sys dump I will be on my way to making a JB stock ROM for those who havent recieved the OTA :D
 
Good.Is That How I Get Android Version 4.1. On The Samsung Galaxy Victory Because The Jelly Bean Rom Or Is It A Kernel To Update To That Version?
 
Yeah it works on every device I have ever had, its a kernel and baseband update, I have built an OC kernel from the SRC, the release of that SRC means an update in the OTA
 
You can download the 4.1.1 update.zip from the below link (replace the xx with tt). Copy it to your SD Card. Turn phone off. Boot the phone into recovery (hold power + volume up) and apply the update.zip from the SD card. You do not need to be rooted to do this. This will update the phone to Jelly Bean 4.1.1.

hxxp://allphonefirmwares.blogspot.com/2013/01/samsung-sph-l300-galaxy-victory-4g-lte.html
 
Oh I see what these are, they are OTAs that can only be flashed via stock recovery, don't even try to flash via CWM cause it won't work, I will make a CWM version later today :rolleyes:
 
Every body who's posted on this thread will get a shout out. Sharing the love.

Sent from my PG86100 using Tapatalk 2
 
lambolos said:
Did the jelly bean file come out yet? And why i don't have a 4g icon on my phone yet?
6
Click to expand...

I am working on converting a CWM backup of JB stock to a flashable zip. This will probably take a day or two if its even possible. I have the files but they're all hashed (sha256?). This is exactly why I hate CWM6 and think people should just stick to TWRP or CWM5. :D
 
rbheromax said:
I am working on converting a CWM backup of JB stock to a flashable zip. This will probably take a day or two if its even possible. I have the files but they're all hashed (sha256?). This is exactly why I hate CWM6 and think people should just stick to TWRP or CWM5. :D
Click to expand...

Sorry for bumping but what is the progress on this? And can it be done for Virgin Mobile?
 
Yesterday my phone downloaded the OTA update and stored it in /cache with a long file name full of hexadecimal. I made a CWM backup and then attempted to let the OTA installer run. Unfortunately it complained about the unsigned zip file and when I decided to back out to inspect it further, the OTA updater now believed that it had completed. Hacking logs in /cache/recovery didn't help.

I did an adb pull of the downloaded file so I could inspect it and put it in a better place for updating from CWM's recovery interface (/sdcard). It failed on checking signatures of the bloatware apps I had removed previously (but also backed up with TitaniumBackup). I restored the apps and renamed the .apks in /system/app to match what updater-script expected to find. Then the update failed on these items:

assert(getprop("ro.product.device") == "goghspr" ||
getprop("ro.build.product") == "goghspr");
assert(getprop("ro.secure")=="1");​

I removed those lines as I knew it was the right device and because CWM wasn't providing the desired result on "ro.secure". At this point I noticed that updater-script also wanted to replace the recovery image, so I removed these lines, to avoid losing CWM:

delete("/system/recovery-from-boot.p",
"/system/etc/install-recovery.sh");
ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/system");
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");​

The update ran successfully. I think that CWM complained that root access had been lost, but I missed the prompt when I brushed against the camera button and clicked "no" instead of "yes" to fix permissions. This is the offending line in updater-script:

set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
​

I booted CWM (power+volume up), started adb shell, and fixed the setuid permission on /system/xbin/su.

I took this as a good time to downgrade Superuser.apk and /system/xbin/su to a version that works promptly - LBE Privacy Guard had been timing out on starting its active protection service because Superuser was taking too long to respond.

Now JB is running successfully. Did another Titanium backup, another CWM backup and copied the files safely elsewhere. Now to remove bloat again. . . .
 
What was the update version? I got MC1 but I can't find some of the lines you mentioned. Also did You get an error about assert(apply_patch_check("/system/SW_Configuration.xml", "70c14cf4f075ae395683eb364fb0f134b14f6bf5", "066fca423ad3d8237ee999ab0c43afa8da212d46")); ?
 
normal19 said:
What was the update version? I got MC1 but I can't find some of the lines you mentioned. Also did You get an error about assert(apply_patch_check("/system/SW_Configuration.xml", "70c14cf4f075ae395683eb364fb0f134b14f6bf5", "066fca423ad3d8237ee999ab0c43afa8da212d46")); ?
Click to expand...

I received MC1. I don't recall seeing an error about /system/SW_Configuration.xml. Does the file exist in your phone? I was unsuccessful in matching up the signatures with anything I knew to check - more for me to learn as I go.

A few days in, something is more battery hungry than with ICS. Not sure yet what it is, but it could be something with the Clock app. I've removed most of my alarms and all my world clock cities, along with locking down with LBE Privacy Guard what Clock can do. We'll see.
 
I've done almost everything but can't get my rooted victory to install jellybean. I have clockworkmod and I have the update.zip file on my internal and SD card but every time I try to flash it I get a status 7 error message saying failed.
 
I dont believe you can flash OTAs with CWM. I would say, flash stock recovery, run update from Settings app, let it update, then relash CWM if needed
 
You must log in or register to reply here.
Back
Top Bottom