Hi all,
I received notification to upgrade to Jelly bean but the process fail.
I am on 4.0.4 stock + root franko kernel (but flashed back to stock) + busybox.
I have a feeling it is busybox that prevents the OTA.
Is this right? How can i uninstall/restore system so that OTA works?
FYI: I have too many data settings on my phone, don't want to wipe everything. So my understanding is that custom roms are not for me.
Thx in advance...
Sent from my Galaxy Nexus using xda premium
Up... please help me :fingers-crossed:
4.0.4 Stock Radio & Recovery?
3rdstring said:
4.0.4 Stock Radio & Recovery?
Click to expand...
Click to collapse
Radio is stock.
Recovery is CMW, but tried after flashing back stock recovery, no luck. Also tried to upgrade manually with the downloaded upgrade file using CWM ; i get status 7 error...
Right, no more feedbacks, I guess I will have to wipe everything out. painful, but I guess I have no other choice.
So my understanding is that the thing to do is to flash full 4.0.4 stock image. Is there any chance I can do that without loosing everything that is on my phone?
what is it I have to wipe, clear and so on?
Last, if i go down that route, I might as well consider a custom ROM: important question, when a custom rom evolves (update, new version...) will I also have to wipe everything and start again with a 'factory reset' phone ?
Thanks
benjieb said:
So my understanding is that the thing to do is to flash full 4.0.4 stock image. Is there any chance I can do that without loosing everything that is on my phone?
what is it I have to wipe, clear and so on?
Last, if i go down that route, I might as well consider a custom ROM: important question, when a custom rom evolves (update, new version...) will I also have to wipe everything and start again with a 'factory reset' phone ?
Thanks
Click to expand...
Click to collapse
To go back to the stock ROM, unfortunately you will lose everything.
EDIT: Using the conventional method but as efrant has stated below, you can do it without losing all your data.
When a new version of a custom ROM comes out, you can just 'dirty' flash it without a factory reset but sometimes you might get errors/bugs popping up though generally it's fine.
Flash the imm76i system image and boot images only. The apply the update in cwm. It should work without wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Flash the imm76i system image and boot images only. The apply the update in cwm. It should work without wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks for that ; also found this POST... patch in progress!!!! Hoping that having installed / uninstalled busybox wil not have left damages behind.
thanks all here + monkeyboy451
Related
This is a full flashable build of 4.0.4 AOSP I compiled myself.
There are absolutely no tweaks of any kind, this is full stock.
Download
You can download it here: https://faramir.eriador.org/r/full-maguro-ota-en.4.0.4.zip
Installation
It can be installed with CWM.
Wipe
You should not need to wipe (except maybe cache). That said if you have weird issues, like accounts not syncing, try wiping.
I installed it over CM9 without wiping, but your mileage may vary.
If you come from pre 4.0.3 ROMs, please wipe.
Google Apps
gapps are not installed, so you will have to flash them too. You can use my mirror at https://faramir.eriador.org/r/gapps-ics-20120317-signed.zip
Please prefer the version of google apps you were already using, otherwise you will more than probably need a wipe.
Root
Note that this is stock, hence there is no superuser, you will have to install superuser and su by hand like on a stock rom.
Here is a mirror for it: https://faramir.eriador.org/r/su_ICS_GN.zip
Kernels
It should be compatible with all 4.0.3 custom kernels although I only tested FuguMod (http://forum.xda-developers.com/showthread.php?t=1438417)
RECOVERY WARNING
This is full stock, which means if you keep the original kernel, it will reflash stock recovery at first boot.
nikademus said:
Hello,
I just compiled 4.0.4 AOSP
You can download it here: https://faramir.eriador.org/r/full-maguro-ota-en.4.0.4.zip
It can be installed with CWM.
You should not need to wipe (except cache).
gapps are not installed, so you will have to flash them too.
Note that this is stock, hence there is no superuser.
It should be compatible with all 4.0.3 custom kernels although I only tested FuguMod.
Click to expand...
Click to collapse
So is it completely stock i.e stock kernel etc? basicly just an ota but not an ota if you get me?
p.s first haha
leelaa said:
So is it completely stock i.e stock kernel etc? basicly just an ota but not an ota if you get me?
Click to expand...
Click to collapse
Yes, it's fully stock, the google way
Real OTA image from google is not available yet, so this is what looks like it the most.
It's mainly for those who want to have real 4.0.4 now without waiting and without losing CWM or making a wipe.
Thanks thats what i want, good job
nikademus said:
Yes, it's fully stock, the google way
Real OTA image from google is not available yet, so this is what looks like it the most.
It's mainly for those who want to have real 4.0.4 now without waiting and without losing CWM or making a wipe.
Click to expand...
Click to collapse
how about losing CWM after making a full wipe
how can i go back to restoring a nandroid backup mate?
thx for help
i only have 3e recovery with the belly-up android...
I just flashed this and lost CWM and have no Gapps.. my Signal bars stay grey and don't turn cyan (blue) even though I know.I'm in an area I get perfect service.
Sorry can't see any changes. Same sh#@% defrent day.
klone96 said:
I just flashed this and lost CWM and have no Gapps.. my Signal bars stay grey and don't turn cyan (blue) even though I know.I'm in an area I get perfect service.
Click to expand...
Click to collapse
As I posted in the OP, you need to flash gapps. It's forbidden to distribute them (at least included in a ROM).
klone96 said:
I just flashed this and lost CWM and have no Gapps.. my Signal bars stay grey and don't turn cyan (blue) even though I know.I'm in an area I get perfect service.
Click to expand...
Click to collapse
How did you flash the ROM?
I also flashed it together with Gapps, su and FuguMod R200.
I didn't loose recovery and also I can connect without any issues on Wifi and mobile data.
zurchpet said:
How did you flash the ROM?
I also flashed it together with Gapps, su and FuguMod R200.
I didn't loose recovery and also I can connect without any issues on Wifi and mobile data.
Click to expand...
Click to collapse
he probably wiped full like me and also forgot to download SU (from the other thread), gapps and optional kernel
zurchpet said:
How did you flash the ROM?
I also flashed it together with Gapps, su and FuguMod R200.
I didn't loose recovery and also I can connect without any issues on Wifi and mobile data.
Click to expand...
Click to collapse
I flashed in cwm and flashed the gapps but I guess it didn't take bcuz I don't see them I'm no where near a laptop so I'm guessing I'm screwed untill I root/flash recovery??
I have put links to gapps and su in the OP
Soo.. is it best to just wait for another stock rom with a kernel that has a recovery... or just flash this?
This rom will not overwrite existing recovery partition.
Sent from my Full AOSP on Maguro using Tapatalk
YoungAceAtlanta said:
Soo.. is it best to just wait for another stock rom with a kernel that has a recovery... or just flash this?
Click to expand...
Click to collapse
You can flash FuguMod before booting, it will not wipe your recovery.
The problem is within the init.rc:
Code:
service flash_recovery /system/etc/install-recovery.sh
class main
oneshot
This is stock behavior.
Hey guys can I flash this over the AOKP Mod I have installed? If so, how?
I do not find meaningful replace the stock ... what's the point? Then, after a day or puts the CM9 o another aopk ..... mistake?
sago62 said:
I do not find meaningful replace the stock ... what's the point? Then, after a day or puts the CM9 o another aopk ..... mistake?
Click to expand...
Click to collapse
I will probably stay on that ROM and not flash any AOKP or so. It has all I need.
Joshaldo said:
Hey guys can I flash this over the AOKP Mod I have installed? If so, how?
Click to expand...
Click to collapse
I have flashed it over CM9 nightly without any wipe needed.
sago62 said:
I do not find meaningful replace the stock ... what's the point? Then, after a day or puts the CM9 o another aopk ..... mistake?
Click to expand...
Click to collapse
please talk english to us! thanks!
Hello everyone.
I am fairly new to Galaxy Nexus (but not new to Android ROM flashing). How do I install JellyBelly? Currently I am rooted with BL unlocked. Please answer the following questions:
- Do I need CWM for JellyBelly?
- Do I need to wipe/factory reset (I am on yakju 4.0.4)
- Exactly when do I flash "JellyFix"? Right after I flash the ROM?
- Does the ROM has any issues (i.e battery life, volume, hw problems etc.)
- Do you advise to install this ROM, or instead wait for the official Google's OTA?
Now I could have easily found answers to this in the original thread, but the search functionality is unavailable for me and I am not in the mood of going through 100s of pages. I would really appreciate it if someone answers these questions for me.
You do need CWM
You would have to wipe data & cache
So far I have not encountered any bugs, everything runs completely smooth. (Project Butter )
I saw you flash now, I promise you will not regret it.
Sent from my Galaxy Nexus using xda premium
Poster above me practically answered everything. Except that, most roms now, you don't need to flash "JellyFix" or whatever, because their roms have been updated to include the fix internally, so you just flash the rom and you're good. But for the sake of completeness, yes, you would flash the fix for whatever problem after you flash the rom.
http://forum.xda-developers.com/showpost.php?p=28105262&postcount=296
is my data lost after updating to jelly bean?
MOST2K2 said:
is my data lost after updating to jelly bean?
Click to expand...
Click to collapse
You're gonna be wiping your device to install a ROM (CDMA or GSM phones) or wiping your device to flash an image (GSM phones). Either way you lose it all.
If you want to keep your data use titanium backup.
MOST2K2 said:
is my data lost after updating to jelly bean?
Click to expand...
Click to collapse
Not the stuff on your sdcard. As for your app data, you can easily use Titanium Backup to back it up before hand, and restore it after.
I flashed the T999UVDLI6 package to my phone but cannot seem to Root now. I have tried everything that used to work and Superuser will not take. has anyone else flashed and succeeded in rooting?
Here is how I got here:
I tried to update using CWM and it failed
I reflashed STOCK T999UVALH2 and then updated using Android Recovery and the full update worked
I have tried flashing via Odin 3.04 like always and the CWM mod will NOT take- all I ever get is the Android Recovery
Interestingly, if I try to flash Superuser from SD card using Android system recovery it gives me an :E:signature verification failed" message.
Any thoughts?
You must be fully stock and also have stock recovery... When I did it I used mobile Odin to keep root, and but you can use ota root keeper
Sent from my SGH-T999 using xda premium
ktetreault14 said:
You must be fully stock and also have stock recovery... When I did it I used mobile Odin to keep root, and but you can use ota root keeper
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So because I had CWM recovery it failed?
Yea
Sent from my SGH-T999 using xda premium
Rooting after upgrade
Fonz said:
I flashed the T999UVDLI6 package to my phone but cannot seem to Root now. I have tried everything that used to work and Superuser will not take. has anyone else flashed and succeeded in rooting?
Here is how I got here:
I tried to update using CWM and it failed
I reflashed STOCK T999UVALH2 and then updated using Android Recovery and the full update worked
I have tried flashing via Odin 3.04 like always and the CWM mod will NOT take- all I ever get is the Android Recovery
Interestingly, if I try to flash Superuser from SD card using Android system recovery it gives me an :E:signature verification failed" message.
Any thoughts?
Click to expand...
Click to collapse
I've flashed and succeeded in rooting, I did the same method as you described. Except I'm using Odin 1.85 not Odin 3.04 :cyclops:
Also, did you try doing a full wipe? I didn't see that in any of your steps. Might want to try that if you haven't already.
Wipe-o-rama
fishguts said:
I've flashed and succeeded in rooting, I did the same method as you described. Except I'm using Odin 1.85 not Odin 3.04 :cyclops:
Also, did you try doing a full wipe? I didn't see that in any of your steps. Might want to try that if you haven't already.
Click to expand...
Click to collapse
Yes- I wiped everything possible (data/factory reset, cache partition, and Dalvik Cache) and Odin would not load it which is why I ended up using the Stock Loader. I will have another crack at it
Hmmm
Fonz said:
Yes- I wiped everything possible (data/factory reset, cache partition, and Dalvik Cache) and Odin would not load it which is why I ended up using the Stock Loader. I will have another crack at it
Click to expand...
Click to collapse
Okay, I retraced my steps and everything still works fine for me...so I did some things to break my phone a bit to see how this can fail, and came out with a few results.
Using Odin, uncheck the "Auto Reboot" option, I think this ROM will reflash to stock upon reboot unless disabled, it's a "feature" found in the Galaxy Tab 2 also. CWM 6.0 will take care of that, as they ask you to disable that "feature" upon reboot from CWM. Now, in order to get there, you need to go directly from Odin mode to recovery. So here's what I did exactly to get the results that you are asking for:
Using Team Win Recovery Project (TWRP Recovery), I wiped dalvik, cache, system, data, and factory reset, and then I opened Odin, unchecked "Auto Reboot" option, flashed T999UVALH2 back to stock, rebooted into android recovery, factory reset, reboot back into android recovery, flashed T999UVDLI6, and then rebooted into android recovery, did a factory reset, and rebooted into Odin mode, where I kept that same box unchecked, and flashed TWRP recovery. After it flashed, I unplugged my cable, and rebooted directly into the custom recovery where I flashed SU. Booted my phone and I have root access with JB. Now, if you don't want to use TWRP as your recovery, then you should use the latest version of CWM.
I was typing this as I was doing it, so I know for sure this works. At least, for my phone it does. Good luck and I hope this helps!
Awesome. Thanks for taking the time to troubleshoot for me. I will try today and report back
Sent from my SGH-T999 using Tapatalk 2
Please clarify
I am fully stock and using stock recovery and I am getting an error regarding :E:signature not being valid when I try to flash. I have applied OTAs that my phone received in the past. Dose this mean I need to revert back to the default firmware image also or is there a different issue? Thanks
I've been flashing OTA leaks with CWM. Both ICS and JB. I don't lose CWM recovery. This process is a lot easier than some people think. I have never needed stock recovery to update to the OTA leaks.
1) Stop using CWM v5. Its time to upgrade to v6.
2) Get T999UVALH2 on your phone. Whether you have UVALEM and use the official OTA update to UVALH2, or do a full install of it. You need UVALH2. I personally still had a UVALEM nandroid, so I restored then factory reset. Then backed up the clean install. Then I ran the OTA through the phone settings > About phone > Software updates. Now I had UVALH2. Guess what? Nandroided that, too.
Also, make sure you flash the UVLH2 modem if using another version.
3) If needed, get CWM on there through Odin. Or if you got a prerooted version, get CWM on there through other means.
4) Download the OTA update here: http://www.sammobile.com/firmware/?page=3&model=SGH-T999&pcode=TMB&os=1&type=1#firmware
5) Flash update with CWM. Upon exit, it will ask you about recovery and root.
Now you have the new leak, CWM recovery, and root.
CWM 6 did the trick. Still rooted and running JB
Sent from my SGH-T999 using Tapatalk 2
Well here we go. I rooted my Evo back in the day, and decided to give it a shot on my sprint GS III. Don't go as well as I thought. Using the Odin method, and following all instructions carefully, I finished and my phone booted, in attempt to download busy box, I found that even tho the superuser app is present, it claims no root. This bothers me, and I've decided not to go through the root. There is now a system update present, (ota) and i want to install it, but the presence of superuser scares me.. Should I just update? My android version is 4. 1.1
HAM_MAN87 said:
Well here we go. I rooted my Evo back in the day, and decided to give it a shot on my sprint GS III. Don't go as well as I thought. Using the Odin method, and following all instructions carefully, I finished and my phone booted, in attempt to download busy box, I found that even tho the superuser app is present, it claims no root. This bothers me, and I've decided not to go through the root. There is now a system update present, (ota) and i want to install it, but the presence of superuser scares me.. Should I just update? My android version is 4. 1.1
Click to expand...
Click to collapse
So you probably have the custom recovery still installed on your phone (CWM) correct? If so, that is what will prevent the update from going through from 4.1.1 to 4.1.2. The update is looking for the stock recovery.
tkepk181 said:
So you probably have the custom recovery still installed on your phone (CWM) correct? If so, that is what will prevent the update from going through from 4.1.1 to 4.1.2. The update is looking for the stock recovery.
Click to expand...
Click to collapse
Yes I do. I forget which version tho. So what are you recommendations?
HAM_MAN87 said:
Yes I do. I forget which version tho. So what are you recommendations?
Click to expand...
Click to collapse
Since you have a custom recovery, I'd recommend just flashing the stock rooted ROM by Freeza. It should be exactly what you're looking for: rooted, stock system with no extras and nothing removed.
First flash MB1 baseband in recovery (called "MB1 Firmware/modem/baseband update" on Freeza's page)
Then (while in recovery) perform a factory reset, wipe davik and cache, and flash the Rom (your choice n Odex vs. Deodex).
You'll be rooted with stock. No more nagging updates (for MB1, at least).
Hope this helps!
topherk said:
Since you have a custom recovery, I'd recommend just flashing the stock rooted ROM by Freeza. It should be exactly what you're looking for: rooted, stock system with no extras and nothing removed.
First flash MB1 baseband in recovery (called "MB1 Firmware/modem/baseband update" on Freeza's page)
Then (while in recovery) perform a factory reset, wipe davik and cache, and flash the Rom (your choice n Odex vs. Deodex).
You'll be rooted with stock. No more nagging updates (for MB1, at least).
Hope this helps!
Click to expand...
Click to collapse
Thanks! I'll probably end up doing this. Although, it raises some concerns, because I tried to flash Cyanogenmod, and clockwork mod completely froze when I attempted it, and wiped my phone. Guess it's worth a shot? Also, I would like to be able to un–root if the need arises.
HAM_MAN87 said:
Thanks! I'll probably end up doing this. Although, it raises some concerns, because I tried to flash Cyanogenmod, and clockwork mod completely froze when I attempted it, and wiped my phone. Guess it's worth a shot? Also, I would like to be able to un–root if the need arises.
Click to expand...
Click to collapse
You could try using the toolkit by mskip. There is an option in there for restoring to stock rom/firmware/recovery. Just read the directions carefully and thoroughly. Mskip is also pretty good at responding to questions in regard to the toolkit.
I could try that as well, I'll have to talk to my friend because I don't have a computer. Thanks! You guys have been a huge help.
Sent from my Galaxy S III using xda app-developers app
I am running stock. No ROM but I am rooted, and I use Franco kernel and xposed framework, what will happen to those mods? Im afraid of brick, should I uninstall all of those including root first before updating to L... When it comes out? Please I need answers, I had soft brick before and I don't want it again.
BrickMeNot said:
I am running stock. No ROM but I am rooted, and I use Franco kernel and xposed framework, what will happen to those mods? Im afraid of brick, should I uninstall all of those including root first before updating to L... When it comes out? Please I need answers, I had soft brick before and I don't want it again.
Click to expand...
Click to collapse
You should only have to wipe, yes you will loose the mods, but they will probably be updated. You will just have to wait a month or 2.
WeRSpecialPeople said:
You should only have to wipe, yes you will loose the mods, but they will probably be updated. You will just have to wait a month or 2.
Click to expand...
Click to collapse
Wipe everything right? Like factory reset or twrp? Will I have to reinstall root/Franco?
Franco will need to create a new kernel, the old one won't work after a version update. Xposed will work if you manually flash the update; if you want ota you'll need to disable it first and revert to stock recovery.
Sent from my Nexus 7 using XDA Free mobile app
You'd have to try really hard to brick a Nexus device. What's so scary about a soft brick? Learn how to use fastboot and adb and there's absolutely nothing to be scared of.
Actually I was going from cwm to twrp and I didn't know the wipe buttons would get rid our my OS altogether..? my dumb mistake.
But I was saved by nexus 7 toolkit
Sent from my Nexus 7 using XDA Free mobile app
Yea don't worry about bricking. You will be able to restore thru nexus toolkit as long as your bootloader is unlocked. I wiped the os off my nexus 4 as well.
I just took the plunge and xposed isn't working nor is my showbox.
Android L is really cool and I can live without xposed, but showbox not working is a big hit. I just got it all setup too. Works good. No real problems.
I flashed back to stock and wiped, then upped to L
How do you flash back? Can I just flash a custom 4.4.4 ROM or do I need flash stock?
player911 said:
How do you flash back? Can I just flash a custom 4.4.4 ROM or do I need flash stock?
Click to expand...
Click to collapse
Just like you would any other ROM in recovery or fastboot. If you want stock, flash stock. If you want a custom ROM, flash a custom ROM.
player911 said:
How do you flash back? Can I just flash a custom 4.4.4 ROM or do I need flash stock?
Click to expand...
Click to collapse
Multiple choices. If you made a backup/nandroid before flashing L you should be able to restore your backup without any issues, For one thing the bootloader didn't change. You can fastboot flash the system and boot images after extracting them from the factory image then wipe cache and dalvik. Flash the whole factory image either with or without modifying the flash_all.bat (open the flash_all.bat in notepad and remove the -w which will prevent the storage from being wiped). Or... flash a custom or stock ROM. Piece of cake!
Good to know. I'm trying to hang on but we'll see