For the past couple months I've been trying to update my galaxy nexus from 4.0.2 to jelly bean through an update distributed on the network however whenever I begin the installation process I'm shown a black screen with Google in white. This screen persists until the phone runs out of battery power despite the fact that the installation is only supposed to take a couple minutes at most. Is there a way to fix this problem or another way to install jelly bean without needing to connect my phone to my desktop?
bumping for some info
Vynath said:
bumping for some info
Click to expand...
Click to collapse
Have you rooted your phone and unlocked the bootloader? I would check out this video by DroidModderX on HOW TO Install Jelly Bean 4.1 on Galaxy Nexus (Verizon, GSM, or Sprint), make sure to follow the instructions for the GSM version since your on Bell which uses GSM. Hope this helps .
Hello xda-developers!
Well here is my situation. I just got my Samsung Galaxy Tab 2 10.1 about 1 week ago (Southern California, USA) and the first thing I did was root the device so that I could enable all features and do things like install linux/busybox.
Okay so just the other day i was looking at my notifications and it said that there was a software update. I figured that this was probably samsung's official jelly bean and i was excited to update so I downloaded the software it was around 330MB's. After the download it asked me if i wanted to install now or install later and i choose now and afterwards the device rebooted and it booted into CMW-Recovery and i got this error.
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Now i heard that i am getting this error because this "software update" is not "officially" signed by Samsung. I don't know if that is true or not...
So i have a couple of questions...
One, is this update for jelly bean?
Two, how can i go about updating to jelly bean?
Three. is my rooted status blocking this update?
Four, is it possible to root the device after the jelly bean update?
If anyone can assist me with this error that I am getting I would really really appreciate it. I am not sure where to go from here.
sammobile.com/firmware/?page=3&model=GT-P5113&pcode=0&os=1&type=3#firmware
do you guys think that software update i was seeing was jelly bean?
I thank you all for your time and assistance.
-droidshadow
droidshadow said:
Hello xda-developers!
Well here is my situation. I just got my Samsung Galaxy Tab 2 10.1 about 1 week ago (Southern California, USA) and the first thing I did was root the device so that I could enable all features and do things like install linux/busybox.
Okay so just the other day i was looking at my notifications and it said that there was a software update. I figured that this was probably samsung's official jelly bean and i was excited to update so I downloaded the software it was around 330MB's. After the download it asked me if i wanted to install now or install later and i choose now and afterwards the device rebooted and it booted into CMW-Recovery and i got this error.
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Now i heard that i am getting this error because this "software update" is not "officially" signed by Samsung. I don't know if that is true or not...
So i have a couple of questions...
One, is this update for jelly bean?
Two, how can i go about updating to jelly bean?
Three. is my rooted status blocking this update?
Four, is it possible to root the device after the jelly bean update?
If anyone can assist me with this error that I am getting I would really really appreciate it. I am not sure where to go from here.
sammobile.com/firmware/?page=3&model=GT-P5113&pcode=0&os=1&type=3#firmware
do you guys think that software update i was seeing was jelly bean?
I thank you all for your time and assistance.
-droidshadow
Click to expand...
Click to collapse
First, wrong section. This is for the first gen Galaxy Tab, you have the second gen.
Second, good chance the OTA didn't flash because of the custom stuff, there is asserts to stop flashing if something is missing.
Third, find your appropriate section and post there, you might get a more definitive answer for your device.
You may have already heard of the impending JB update for your stock S2, that is, if you're the "stock guy". But don't you ever feel you want new Android earlier? Are you considering to "prison break" your Android? Get to the polls and share your thoughts.
PS: The jelly bean update has only surfaced on few carriers/regions. This post refers to jb update via Kies or OTA.
^^ "prison break" = modify(mainly rooting/flashing)
The jelly bean update is out its xxls8 have a look around open your eyes you may find it http://forum.xda-developers.com/showthread.php?t=2113489 also this isn't an ipone you don't jail break/ prison break you root and I'm fairly sure that you can just install the stock jelly bean ROM from stock recovery without root
What's the point of this thread
Never ever without root!
Terrible. Totally useless thread. Please don't do this ever again.
Sent from the Matrix
New to the site, watched the video and followed instructions and couldn't find a thread close to what I wish to do per sey.
So here is what I am trying to do.
Last October I had the Armageddon 4.2.1 ROM put on my S2 GT19100 and its been ok but I have a few problems with it like video recording and such and I have been waiting for the official 4.2.1 update to come out in the UK and it seems it has.
So I am not really all that savvy with rooting and such but I'd like to put the official 4.2.1 Firmware on my phone now and I could do with some comprehensive instructions on how to do so as in step by step.
Some help would REALLY be appreciated.
Thanks.
i think you are waiting for 4.1.2. 4.2.1 update is never announced for S2 by samsung!!!!!:silly:
if you want 4.2.1 go here CM10.1
but you have to do all that root business... or download Spain official 4.1.2 firmware from sammobile.com
4.1.2 and 4.2.1 both are different versions of Jelly Bean.
or the other unofficial (leaked version) - i think was Arg version of 4.1.2
RandomPHD said:
New to the site, watched the video and followed instructions and couldn't find a thread close to what I wish to do per sey.
So here is what I am trying to do.
Last October I had the Armageddon 4.2.1 ROM put on my S2 GT19100 and its been ok but I have a few problems with it like video recording and such and I have been waiting for the official 4.2.1 update to come out in the UK and it seems it has.
So I am not really all that savvy with rooting and such but I'd like to put the official 4.2.1 Firmware on my phone now and I could do with some comprehensive instructions on how to do so as in step by step.
Some help would REALLY be appreciated.
Thanks.
Click to expand...
Click to collapse
you can try SuperNexus rom for 4.2.1. instructions are in the OP of that thread.
if you want JB 4.1.2 based rom, try NeatROM lite 4.2
I recently tried to downgrade my Galaxy S3 from Jelly Bean 4.1.2 to ICS 4.04 using Odin and a ROM file downloaded from Sammobile.
The installation was succesful and after doing a factory reset and clearing cache the phone booted up ok. It connected to my network provider for several seconds and then disconnected.
After several attempts at this process using different files, I noticed that the IMEI of my phone was no longer correct. At this point I thought I had bricked my phone by somehow corrupting the IMEI.
In an attempt to put it right, I reloaded Jelly Bean 4.1.2 and my phone now works fine again. Please can someone advise what I am doing wrong with this process and why the IMEI gets corrupted as this is obviously why the network rejects my phone when I install ICS.
If you would look here: http://forum.xda-developers.com/galaxy-s3/general/ref-galaxy-s3-modem-radio-collection-t1740061 you will found this link for ICS ROMs: https://www.wuala.com/UpInTheAir/SGS3/Modems/I9300/ICS/?key=n0KVwtIMZPE8 . From here, select CWM folder if you want to flash the modem via recovery, or the Odin one if you want to flash it with Odin. Choone one of the file, download it, and then flash it via the method you want.
QuickQuestion: Why would you wanna use ICS when it has been released 4.3 for our device, and 4.4 it is said to be released in the following weeks (Hope so! ). If you want, you can answer, if not, it'ss not a big problem
Thanks for the reply. Is this the reason my IMEI is corrupted when I flash a PDA from Sammobile? I am new to using Odin etc and followed the instructions on the website.
There are some features I liked in ICS that were removed in Jelly Bean, such as direct access to words in the custom dictionary and the 3 x 4 keypad that was removed in 4.3. I already downgraded from 4.3 to 4.1.2 but wanted to try ICS 4.04. So far I can install it but cannot get a network connection for more than a few seconds.
#EDIT: After further research this problem appears to be an issue with the phone's EFS data. I have now used EFS Professional to back up this important area. What I don't know is can I restore this backed up EFS data to correct the problem I'm having when I downgrade Jelly Bean 4.1.2 to ICS 4.04?
andyb1712 said:
Thanks for the reply. Is this the reason my IMEI is corrupted when I flash a PDA from Sammobile? I am new to using Odin etc and followed the instructions on the website.
There are some features I liked in ICS that were removed in Jelly Bean, such as direct access to words in the custom dictionary and the 3 x 4 keypad that was removed in 4.3. I already downgraded from 4.3 to 4.1.2 but wanted to try ICS 4.04. So far I can install it but cannot get a network connection for more than a few seconds.
#EDIT: After further research this problem appears to be an issue with the phone's EFS data. I have now used EFS Professional to back up this important area. What I don't know is can I restore this backed up EFS data to correct the problem I'm having when I downgrade Jelly Bean 4.1.2 to ICS 4.04?
Click to expand...
Click to collapse
If you have a 16GB s3, u might want to keep JB, 16GB ICS S3 has the possibility for sudden death. But, i too am considering going back to ICS, Jellybean is a joke, it lags way more than ICS does. Trying to force the system to constantly render at 60FPS is hardware demanding and was probably a temporary approach. Its unfortunate that ICS ROMS are no longer available for download. Also, i doubt kitkat would be released for our phone.
My S3 is 16Gb and was originally shipped with Jelly Bean. I watched a Youtube video comparing ICS and Jelly Bean and ICS was faster responding in virtually every test, despite the guy doing it being pro Jelly Bean.
I don't know much about the 'sudden death' problem with ICS on 16Gb models but from what little I've read, I thought this was more of a hardware issue due to defective memory chips and/or main boards?
My S3 updated to Jelly Bean 4.3 last December and I wasn't happy because they had removed the 3x4 Samsung keypad that I like to use. I tried a number of different keypads from Play Store but in the end decided to downgrade to 4.1.2, which went without a hitch.
My attempts to do the same with ICS 4.04 did not go so well and I'm still not sure why the IMEI was corrupted or even more surprising, that it was corrected when I re flashed 4.1.2
andyb1712 said:
My S3 is 16Gb and was originally shipped with Jelly Bean. I watched a Youtube video comparing ICS and Jelly Bean and ICS was faster responding in virtually every test, despite the guy doing it being pro Jelly Bean.
I don't know much about the 'sudden death' problem with ICS on 16Gb models but from what little I've read, I thought this was more of a hardware issue due to defective memory chips and/or main boards?
My S3 updated to Jelly Bean 4.3 last December and I wasn't happy because they had removed the 3x4 Samsung keypad that I like to use. I tried a number of different keypads from Play Store but in the end decided to downgrade to 4.1.2, which went without a hitch.
My attempts to do the same with ICS 4.04 did not go so well and I'm still not sure why the IMEI was corrupted or even more surprising, that it was corrected when I re flashed 4.1.2
Click to expand...
Click to collapse
Not sure exactly how the sudden death works, i just know it affects 16GB s3 variants. I know the video you are referring to, i watched the exact same one. I think most people got caught up in the hype of JB and forgot how good ICS was.
Havoc-X said:
Not sure exactly how the sudden death works, i just know it affects 16GB s3 variants. I know the video you are referring to, i watched the exact same one. I think most people got caught up in the hype of JB and forgot how good ICS was.
Click to expand...
Click to collapse
The Youtube video made me laugh as it was supposed to encourage you to want the Jelly Bean upgrade, when all it did was make me want to run ICS even more! I tried a friend's Galaxy S2 with ICS the other day and it was smoother and faster responding than my S3.
I hope to have another go at getting it working but also I am concerned I probably came close to bricking my handset last time because I do not know enough about the process. This wouldn't be good as I still have another year on my network contract to go.
Do post here if you succeed in downgrading to 4.0.4 as I am also looking for it but it's not working
And best of luck
Unless you have a backup of your efs folder, from before firmware EMG4 then you cannot downgrade.
EFS format was changed at EMG4 to v2, earlier roms are incompatible with v2 and later roms incompatible with v1 so IMEI will be corrupt.
Sent from my GT-I9300 using Tapatalk
Thanks for the info.
My S3 was shipped with EMG4, so unfortunately I don't have any efs data that I can use with earlier ICS firmwares. I was trying in vain to load BLG8 but it just resulted in a corrupted IMEI and no network.
Unless there is some way of converting saved v2 efs data to the earlier format, then I will have to stick with the Android version I have.
Why are you not trying 4.3 or custom rom mate? My god if your phone is giving u problem u should try to tame it. Very smooth, the nb6 firmware. Or at least let yourself try a custom rom for instance temasek.
Sent from my GT-I9300 using XDA Premium 4 mobile app
I have tried the Official Samsung 4.3 release but didn't like that they removed the 3x4 Samsung Keypad, which I prefer to use. I've tried custom firmwares on my old phone (Galaxy Ace) but never had much success with installing them or getting things to work properly after.
My S3 is still under contract for another year and my skills in this area of modifying are beginner level at best, so I plan to do a lot more reading on here and a lot less messing around with the phone firmware until I know more about it.
andyb1712 said:
I have tried the Official Samsung 4.3 release but didn't like that they removed the 3x4 Samsung Keypad, which I prefer to use. I've tried custom firmwares on my old phone (Galaxy Ace) but never had much success with installing them or getting things to work properly after.
My S3 is still under contract for another year and my skills in this area of modifying are beginner level at best, so I plan to do a lot more reading on here and a lot less messing around with the phone firmware until I know more about it.
Click to expand...
Click to collapse
Your phone lag is because of Samsung bloatwares, get rid of it and you would be fine. Temporarily suggestions would be hang on 4.12 and try greenify. U don't need root but root would give you he best out of it. Look up cf autoroot and begin your journey.
:thumbup:
Sent from my GT-I9300 using XDA Premium 4 mobile app