Database Users

Gingerbread over-the-air update problem

I woke up this morning and my over the air update was ready to install. I clicked install, and it went to reboot. When it was loading the package my screen went to the Android guy and the caution symbol.
When I got to work I took the battery out and rebooted the phone. My phone is rooted and I have a recovery app installed so I chose to reboot with 2.2. Everything is working like normal again now.
I assume the update file did not download fully since my phone was just on 3G all night.
My Question is: Will the update automatically push to my phone again, since I already started downloading the file? Or will I have to do a manual update?

it didnt install cuz u are rooted

To be able to receive the OTA without manually installing it, your phone needs to be STOCK. Since you are rooted, you have the option to go back to stock via odin or you can install GB manually with root. Either way, once GB is installed you will lose root.. so be prepared to root again if you choose.

marschmellau said:
To be able to receive the OTA without manually installing it, your phone needs to be STOCK. Since you are rooted, you have the option to go back to stock via odin or you can install GB manually with root. Either way, once GB is installed you will lose root.. so be prepared to root again if you choose.
Click to expand...
Click to collapse
Not true u can receive the OTA if yor on a custom rom,
Im on bonsai 4.0.1 and i keep getting that damn pop up!!!
But dont bother with it cause u can't install it as im rooted, however u still will be prompted with it..

Thanks guys. Manually updating at work right now.

is there a link on here for a manual update
been reading these boards for a while and have seen a update (i think from qbking77) for gingerbread but...it seems that with this official upgrade there may be a different procedure
i am hearing two versions of how to update..one saying for a rooted phone and one stating it must be unrooted
any help? my phone is rooted running Drock clean kernal ec05 and baseband S7000.5ec05

rstaffer89 said:
been reading these boards for a while and have seen a update (i think from qbking77) for gingerbread but...it seems that with this official upgrade there may be a different procedure
i am hearing two versions of how to update..one saying for a rooted phone and one stating it must be unrooted
any help? my phone is rooted running Drock clean kernal ec05 and baseband S7000.5ec05
Click to expand...
Click to collapse
Nope. Always the same...must be completely stock to get the OTA or flash the update.zip. And as usual 10 minutes after OTA started there are prerooted GB ROMs you can flash if you don't want to go back to stock.
Sent from my SPH-D700 using XDA App

marschmellau said:
To be able to receive the OTA without manually installing it, your phone needs to be STOCK. Since you are rooted, you have the option to go back to stock via odin or you can install GB manually with root. Either way, once GB is installed you will lose root.. so be prepared to root again if you choose.
Click to expand...
Click to collapse
I have a stock Epic with stock ROM except that I used the one click (simple) rooting method to root it.
How can I Install the GB update now? I don't want to flash my phone and go back to ODIN (I haven't flashed a phone before, even though I have done so to the Nook color).
Is it possible to manually apply the update to my rooted phone? Will that work or will my phone be bricked?
I am ok with rooting the phone again after the update. I am hoping they have a simple rooting method for GB as they did with froyo. Thanks!

so i am running the same sfr 1.2 with genocide i believe and the update keeps showing up if i flash a gingerbread rom with this go away or is there a way to get the notification to go away?? actually my wifes phone and it is driving her nuts!! lol

Phone won't boot :(

My galaxy 3 (apollo) came with 2.1, so I thought I would update to 2.2. I downloaded JPU from hotfile, the one that uses sampro.pl as password. Had odin set up with .ops, one package, nothing else checked. It flashes it and restarts a few times, then gets to the samsung logo which flashes, then it just freezes.
I have tried wiping the cache and factory reset. I tried JPS too (which I knew worked on my other phone - but that I upgraded from 2.2 to 2.2) but nothing seems to work.
Have I done something wrong?

I would suggest to flash your mobile once again
by following the instructions in the below link.
http://forum.xda-developewjrs.com/showthread.php?t=1372414
I hope it helps.

Somehow I got it working, I flashed Cyanogenmod and it worked, then wiped all including dalvik cache with cwm, still didn't work when I flashed froyo. So I removed sbl.bin and boot.bin from the .tar, tried and still nothing, then wiped data and cache one last time and on reboot it started up!
I had wiped the data and cache tens of times before and after flashing before, so it was either removing the bootloader or wiping the dalvik cache that made a difference. Only took all day to update my phone!

Try to get some different source for froyo....

I'm Glad you got it working again! next time you need stock firmware, use the one available in this forum by searching "stock jpu" the dev has removed the bootloaders and therefore it is much safer, and yeh as you've discovered, when it doubt, wipe the dalvik!

Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)

mike_1983 said:
Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)
Click to expand...
Click to collapse
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...

J.Purungrit said:
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...
Click to expand...
Click to collapse
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster

mike_1983 said:
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster
Click to expand...
Click to collapse
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.

I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice

Smonic said:
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.
Click to expand...
Click to collapse
Ah I didnt know the Galaxy 5 had been out longer. The camera didn't work when I used the latest CM7 for the Galaxy 3, when it took a picture it looked like a commodore loading screen But I didn't check gallery thinking about it, perhaps they came out alright

prabhuthelegend said:
I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice
Click to expand...
Click to collapse
I rooted the phone with SuperOneClick, I think it worked! Anyway I gave the phone to my brother now and hes just interested in a working phone, not messing about with roms! I may get the phone again when it comes down in price again (you can get them refurbished in brand new condition here in UK)
Thanks!

Running Rooted 3.2.1 to ICS? Do I unroot?

I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks

tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Same question here
Sent from my A500 using XDA

3d0rr said:
Same question here
Sent from my A500 using XDA
Click to expand...
Click to collapse
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.

Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?

tu3218 said:
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
Click to expand...
Click to collapse
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA

3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yeah I think so as well. I flashed stock via the Acer recovery tool but I get nothing when I boot into recovery except what I stated above. I'm not sure if that's right or not.
Sent from my Galaxy Nexus using XDA

I was happily running timmydean's rooted 3.2.1 based on the leaked OTA. The ICS upgrade came through and installed just fine. No loss of data and the programs I tried all worked. I was on stock 4.0.4 unrooted.
However, I'm now borked. I rebooted into recovery (Power, Vol -) to see about rooting via the backdoor I'd installed. I had thor's 1.7 Touch CWM recovery installed. I got some weird message that recovery was broken. (Don't recall the exact msg.)
After that, it hung on the "android" screen. Soft-bricked.
So I did a factory reset (Power, vol+, rock screen switch) and ended up back on 3.2.1. Now, the Settings > About > Check update results in the "Network coverage is currently poor. Please move to a location with better coverage to continue." message.
My WiFi is fine, speedtest.net reports a 20 Mbps download. All other apps function well. I'm pulling a DCHP address from my router.
I'm fairly sure this is a badly-worded error message from Acer and actually refers to server overload or some other issue on their end.
Also, installing the latest Acer Iconia Update preps the system for ICS. At one point, installing it allowed the update to proceed, but not to ICS. Uninstalling/reinstalling that update seemed to jog the system at one time.
So I tried wiping data/cache/dalvik and went back to stock 3.2. Same error message when updating. Wiped again and went back to stock 3.0.1. Same error message.
So I'm stuck and am going to give it a few days to see if Acer can sort out their upgrade path. If not, I will probably load CM9 or Thor's ICS ROM. (I do have a Nandroid, so I can get back to where I was pre-ICS.)
All in all, I'm very disappointed in Acer for borking my tablet.
________
Update: So now a day later, the "poor coverage" message was replaced by an "update available". Installed A500_7.014.03_com_gen1, after reboot, another update A500_7.014.15_com_gen1 installed. I am now on stock 3.2.1.
System update shows "Your device is up to date".
Will see what tomorrow brings, but this is certainly frustrating.

thorne75 said:
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
********************************************
Could you guys running the backdoor and still rooted please try this:
1) Try and capture the build no. of the update
2) See if the update will download BUT do not install yet
3) Go to /cache/fota/ and find the zip -
4) copy it to yr external sd
5) post back the build no.
thanks!!!
Procedure for manual install:
1/ rename the file as : update.zip
2/ place the file on the micro sd card
3/ turn off the tablet
4/ press the down volume key and the power button at the same time untill the tablets turns on
5/ the iconia will start the upgrade process by itself.
OR just redownload the update and it install
*********************************************
I had trouble when i reverted to stock in the weekend
and it was a bit of a process to get the OTA's to 3.2.1.
I did manage to hold "full root" but had to revert a couple of times
by putting stock recovery back and using backdoor .
I accidentally factory reset and everything went a bit pear shaped from there...oops!!
Im still waiting for the OTA ICS - getting network coverage error -one good thing
is my partners tab is only 5 days old and still pure factory,
her tab shows same error so at least we know its not root/backdoor problem
So yeah if u gonna take the OTA best to get rid of the backdoor unless you wanna play guinea pig for us all>>>>
dunno why we aint found one of those yet
I dont think you can cause too much of a problem where a "hard reset" pwr/vol -/rotation lock/ combo wont fix...you can then root from there.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:

dibb_nz said:
********************************************
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
Click to expand...
Click to collapse
Dibb_nz, I was stock gen 2. I don't wanna take OTA until be sure it's safe. Unless now I know that a hard factory reset may save my tab if something happen.
Can you tell us where did you read that post about 'gens'? I still a little confuse about that
Sent from my A500 using XDA

BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA

3d0rr said:
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
Click to expand...
Click to collapse
oh sounds promising, although I just read another post from someone across the ditch in OZ he reckoned acer said they were working on a patch for the problems theyre havin with the first update...who knows
now m8, sorry to confuse you, that wasnt my intention, but i try to make sure that i;m not suggesting things which may end with you or others borkin or brickin yr tab. Ive spent the last few days reading thousands of posts (just like everyone else) thankfully we are fortunate in being able to learn from the mistakes of others I know a bit more about ics than i did 3 days ago let me tell you, lol.
i just finished helpin out a fellow "timmy-ite" stuck with no way of getting in to apx mode to get un-borked...well didnt really help just a sounding board more than anything
he got himself up and running, used the apx tool in my sig, unlocked the bootloader, rooted, flashed custom recovery did a nand and is now running flexreaper - with the tools and knowledge he gained he now has the choice to go back to HC to get the OTA or not....he's one happy camper!!!
Have a read have a read thru the threadhere. ask him a question or two if you want - but dont get too hung up "maybe doing something wrong" you won't be the only person ever to experience that uhh-ohh sinking feeling when you know you shouldnt have just done whatever it was that u just did
Theres always someone round here who will help - usually cos they done the same silly lthings themselves - why ya think i'm always posting

what is the backdoor program you guys talk about?

tu3218 said:
what is the backdoor program you guys talk about?
Click to expand...
Click to collapse
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.

jpinsl said:
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
Click to expand...
Click to collapse
timmyDean How to root stock 3.2.1
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Click to expand...
Click to collapse
beat me to it
its a completely stock gen2 rooted and cwm - you can use to unbrick, or go back to stock. only for HC bootloaders though.....

This worked to me
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method.
1) Go to play market and install Acer Recovery Installer.
2) Open Acer Recovery and verify with recovery do you have. In my case it was CWM recovery by thor2002ro 1.5
3) Install stock recovery. Make a backup of your old recovery when ask.
4) Factory reset: in my case, I made a backup of all my data and used Titanium to backup some apps. Then I harded reset my tab by turning it off and the combo pwd + vol(+) then lock-unlock switch 3 times until I saw "eraing user data" in the top-left corner.
5) turn on the tab and go to google play. Search for acer and install Update enhancement.
6) Go to settings-> about-> system update and aply the OTA update.
You will lost root, but everything should work fine.
To gain root access again, you can follow this thread -> http://forum.xda-developers.com/showthread.php?t=1546593
Now I have rooted stock ICS and I'm so happy

Hey great write up, will try this as soon as I'm off work. Anyway to confirm stock recovery is installed? Because I have done what you said(just the flash stock recovery part) an when I boot into recovery I just get a triangle an exclamation point. Not sure if thats right or not. But I will definitely give this a go since you were running exactly what I'm running now.
Sent from my Galaxy Nexus using XDA

3d0rr said:
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method...
...To gain root access again, you can follow this thread - ...xda-developers.com/showthread...
Now I have rooted stock ICS and I'm so happy
Click to expand...
Click to collapse
yay for 3d0rr you finally took the plunge congrats!!!!!
@tu3218
That download link is no longer available
instead download blackthund3r's one-click-root,
google "ICS Root for Windows"
At step 3 - After you have backed up -
Copy the uid.txt file from the backup folder - this holds your cpu id -
you're probably gonna need it at sum stage

I followed your instructions and it went perfect!!! Rocking ics now. Thanks for the help. First thing I notice, soooo much faster an full of butter.
Sent from my Galaxy Nexus using XDA

[GUIDE] On ICS LPY ROM [DO's & DONT)

From the Moderator... Please read my Caution in post #27-thanks
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Edit: Shorty66 just posted he bricked his note by doing factory reset from within the os. So far he's the only one at the moment. But numerous members reported bricking their device using CWM recovery & stock recovery. Just to be safe, use the os factory reset rather than recovery. Me myself have used the os factory reset at least 6-7 times as we speak without any issue for the time being.

Nice guide, perhaps you could also add the steps to safely go to a 'safe' kernel/rom if one is already using LPY?
Sent from my GT-N7000 using xda premium

+1
Would also like to know the go back to b/cm9 etc steps
Sent from my GT-N7000 using xda premium

Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there to get to any custom roms or rooted gb.

Ashren81 said:
Entropy covered that earlier. But whatever u do if u're on LPY, avoid wiping under CWM or stock recovery. Get any safe GB cf-root kernel and wipe/reset/flash from there. And dont restore nandroid backup from any leaked ics or LPY kernel. As to stock LPY device, u can just flash back to any stock gb and from there get to any custom roms or rooted gb.
Click to expand...
Click to collapse
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2

MamaSaidWhat? said:
So just to be clear, as I am currently on rooted LPY ROM + kernel, the safest thing would be to flash CF-Root GB kernel whilst still on LPY? How would this be done? Because obviously CWM functions aren't safe, and flashing a GB kernel (through Mobile Odin) on a ICS build would cause a brick also?
I really hate LPY and I want to get on to CM9 just to be safe, but I'm having trouble figuring a safe way to do so any help would be greatly appreciated.
Sent from my White Galaxy Note using Tapatalk 2
Click to expand...
Click to collapse
flash using pc odin or heimdall. get to recovery and flash/wipe or install gb backup from there. but i advise u to get back to stock gb to get a clean start and move from there.

Ashren81 said:
First, before flashing the ICS LPY Rom, go back to any STOCK GB according to your liking.
Second, do a full wipe/dalvik/data WHILE YOU'RE ON STOCK GB. Restart/Reboot and start flashing the official ICS LPY Rom on ur device.
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Lastly, you'll be greeted with a new device setup wizard and all the premium apps will be installed. It'll take sometime for the premium app to initialize. You'll think u're stuck at the boot screen (samsung logo), but no. Just wait, it could last a good 3 to 4 min before u see the device setup wizard.
For the time being, to avoid bricking, it is not advisable to root or install CWM for this particular release. Some kernel code might have changed making it problematic for CWMR to live side by side.
And if you do decide to root and get CWMR on ur device, DONT WIPE/FACTORY RESET thru stock recovery or CWMR. It is known to mess up ur eMMC. Just DONT.
Hope it helps.
Click to expand...
Click to collapse
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex

sehooo said:
i agree with u but rooting using this way is safe for all stock changer
http://forum.xda-developers.com/showthread.php?t=1647148
i did that for 3 notes here
and u can change the the default twlancher for the lpy as its laggy with any other launcher
now its all ok for lpy ( ICS + CLEAN+ SMOOTH +ROOT )
i prefer go launcher ex
Click to expand...
Click to collapse
apex launcher FTW!

nice guide!

Ashren81 said:
Third, since this is not a wipe rom, DONT DO IT. Once booted, RESTORE FACTORY SETTING and WIPE using the ICS OS menu. Not thru RECOVERY or CWMR. As long as u wipe/reset thru the os menu, u should be fine.
Click to expand...
Click to collapse
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
The post I referenced: http://forum.xda-developers.com/showthread.php?p=26086599#post26086599

k1ng617 said:
I question the validity of this, because was a reported issue using the settings factory reset too. As far as I know, settings/factory reset still uses recovery to wipe data. Might want to double check that and update your post accordingly.
Click to expand...
Click to collapse
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.

Ashren81 said:
Yeah shorty66 just said he bricked his note using the os factory reset menu. So now we have all method bugged. But I still recommend doing a factory reset from within the os on first boot to clear things out. U wont get the premium apps installed on the first boot if u're coming from any other previous rom because LPY is not a wipe rom. U wont even get the device setup wizard on the first boot. When u do the factory reset, it'll get the premium apps to install upon boot and u get the chance to set the device up using the welcome wizard. I see most people who bricked their device went straight to the recovery and do a wipe from there. Just dont do that, never.
Click to expand...
Click to collapse
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.

hgberry said:
This is how i go back to GB from ics
From lpy go to recovery, flash abyss 4.2 redpilltouch, reboot recovery, so now i'm on GB kernel recovery, wipe data, cache, dalvik. DON'T BOOT SYSTEM. Restore any nandroid GB backup, after that reboot system.
Hope it help.
Click to expand...
Click to collapse
yes that should be the way like i've post earlier. just use the safe-kernel of ur choice. but dont restore nandroid backup from any previous ics, nandroid from previous gb is fine. nice to see ur note safely back on gb. /thumbsup

I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium

Goodm7sn said:
I don't understand what's all this fuss about really...
I flashed lpy thru mobile Odin (coming from gingerbread) with root option checked, and all went smooth! No pc was used at all! I was even at University when I did that!
Then 2 days later, I factory reset using stock recovery... And all went fine! I was even in a friend's car!
So what's up with all the bricking all over the forum?!!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It happen randomly due to I/O bug on the kernel. While wiping big chunk of data off the partition, it'll glitch. Maybe after a wipe, 10th wipe, 11th wipe, 50 wipe etc. Maybe ur upcoming wipe will be ur last wipe, u might never know. Wiping thru CWM and stock recovery is known to produce the bricking effect. Only 1 person reported bricking thru the os factory reset.

I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???

djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
hardware conflict with newly kernel source is possible. different chip revision on different batch of notes produced could also lead to the issue. but if that is to be ruled out not to be the case, then its either samsung released a broken/buggy kernel for public usage or they make changes to the kernel source to react to CWM and the rooting community. just like how apple kept changing their baseband kernel every now and then to block jailbreaking on idevices.
to me its more like a buggy kernel. no wonder they kept pushing and delaying the ics release. ever thought of that?

djtiny said:
I have to agree I don't understand how these bricks are happening. I have gone from Darky LC1 to LPY and then flashed Chainfire LPY kernel through mobile odin. I then got bored and flashed ICS stunner 26.1 through CWM. I have then gone back to CWM whilst on Stunner and Flashed Abyss Note Kernel 4.2. Then on the top of that I have flashed Alba V2 repack of LPY after a wipe/data from CWM and still no brick. I understand the risks involved but like I said not bricked yet.
Does anyone think that there maybe a different eMMC chip on some of these notes that have shipped which have bricked. Wounder if there is anyway to tell anyone looked into this. Just a thought as it might not be the software but the chip on certain devices ???
Click to expand...
Click to collapse
You might just be in the lucky position to have a phone which doesn't have the error.
But somebody also suggested that it makes a difference what you have fleshaed before the LPY rom...
I did not have anything else than stock GB befor the official update, but perhaps there is a way to flash a specific rom before going to LPY to be safe.
Do you still know your flash history?

Hi Shorty66,
Sorry to hear about your note. I can remember being on Darky LC1 base rom full root. I downloaded the LPY.tar file flashed this via mobile odin to flash LPY via mobile odin and wiped data/cache from that program. When this was completed I had full root with the premium suit installed. Battery life was naff so I booted into CWM did full wipe along with cache davlik and flashed Stunner 26.1 rom then when this was fully booted I flashed the kernel extracted from. 19 stunner rom via mobile odin. Then when Alba releashed V2 full repack this was flashed via Red Pill 4.2 as I have this on my SD card because of the brick issues. After this was flashed I rebooted into redpill and proceeded with Flashing the Alba V2 full repack zip. This has fully booted with full root and no brick. So I dont quiet understand why my device has never bricked as im a flashaholic I tell you my mrs I always on to me about it.
Sent from my GT-N7000 using xda premium

Yeah I can understand a buggy kernel but why release it as a proper update. I cannot see them delaying it just to add the premium suit. The note and S2 share the same hardware so the building of the rom should have taken the same amount of development time apart from adding the spen into the framework. The emmc chip if im not mistaken is what the rom and the free memory is on for the internal part of storage feel free to correct me. Im just spit balling ideas here but the way the partition are read on ICS is different as somebody developed a way to bind it like on gingerbread roms. What if the way that ics roms are made screws up and when another rom is flashed when wiping takes place it just erases all the partition info on the chip and this causes the brick. If that makes any sense and when it comes to write the info that seems to start bit sticks and there is no partition information of chip info to write to which is why it just hangs.
Sent from my GT-N7000 using xda premium

[Q] soft bricked ls980

so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.

omega52390 said:
so i got my g2 back from lg after getting the screen repaired. and of course they set it back to stock. now i expected this and made a backup of cyanogenmod thinking i could just root put on a recovery and reflash the backup and be done super quick.
well i had a hell of a time getting the recovery on but its on there now running newest philz however after I flashed my backup i got stuck in a boot loop. luckily i also kept a copy of the original download of the rom. i checked the md5 and its good however even after doing a clean wipe and install of the base rom i still get stuck in a boot loop. this has been a huge headache and i have no idea what i did wrong.
Click to expand...
Click to collapse
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?

XxZombiePikachu said:
is the one you flashed from here http://download.cyanogenmod.org/?device=ls980 and also did you flash gapps after flashing rom?
Click to expand...
Click to collapse
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
edit hang on ive got a 10.2 nightly and jb gapps i might have something here will report shortly... nvm i think... it locks up saying "using legacy property environment for update-binary...please upgrade to latest binary"

omega52390 said:
yes it is the 03-08 snapshot... no i did not flash gapps... and i can't get an up-to-date one on there either because i can't figure out how to get the thing to mount to my computer while in recovery
still scratching my head on why i don't have KK gapps though...
Click to expand...
Click to collapse
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup

XxZombiePikachu said:
well naturally after flashing cm you have to flash a gapps also did you make a nandroid backup
Click to expand...
Click to collapse
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.

omega52390 said:
but cm should still at least boot w/o gapps i've done that with this phone before (when i first got it) and of course i didn't do a nandroid because thats the smart thing to do T_T i was running low on space and figured this was going to be so easy but of course murphy's law got the better of me.
Click to expand...
Click to collapse
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm

XxZombiePikachu said:
well unless you have adb access to push a zip to your device then that means another trip back to stock(I know what it means to be out of space which is why I actually have an otg with pendrives as my backup) and after that you might want to try one of the latest nightly's and if it still bootloops then there just might be something broken in the builds, you would have to get support from someone who uses the same device/cm
Click to expand...
Click to collapse
thats the thing i've only ever had trouble with adb coudl never wrap my head around it let alone get it to work

w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD

omega52390 said:
w00h0000 i figured it out after a bunch of reading and failing i figured out that my problem was the ZVA radio had reasserted itself however the fix others were talking about wasnt' working then i remember i had a stock rom backed up in twrp so i tried sideloading twrp (btw i got adb working XD) and boom still nothing then after a bunch of stressing i tried installing a zv8 radio and boom back into a stock rom and i am now reinstalling cm at least now if it fails I have a fall back XD
Click to expand...
Click to collapse
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
I completely forgot about the zva radio(I had helped someone in the past with a similar issue) and that's great news you by adb working that will make things easier since it gives you more options to fall back on, awaiting to see if you managed to get cm running
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
for some reason cm is still failing to load im going to try installing cm then putting on furnace kernel
edit i remember and succeeded in recreating my secret recipe. first i have an old twrp and 10.2 unofficial nightly thats where i am now. next ill put on a new CWM philz and try putting my CM backup on

another update i finally got my cm 11 backup running however it appears there is damage to the install from back when i made the backup do you know of anyway of repairing an install w/o having to do a reset? really the only noticable problem right now is that i can't use any live wallpapers :/