Database Develop

[ROM][CWM] Honeycomb 3.1 - Touchwiz UX - WIFI - DEODEXED (Updated 7/22/2011)

Pretty basic release. This is a deodexed version of the touchwiz wifi update.zip available in this thread: http://forum.xda-developers.com/showthread.php?t=1167250
I have not changed anything else in this ROM (though I am now working on a more streamlined touchwiz ROM using this deodexed version)
So no, this ROM is not meant to improve performance or fix any bugs from the stock touchwiz update. A deodexed ROM simply makes it possible/easier for devs to create patches that can address these issues, make themes, etc.
Warning: I am not responsibile for any damage you do to your device from flashing this update. Please be careful and follow the instructions below, and use at your own risk!
md5: 5a6a04a24f7f799b1b122d9e445110b2
Uploaded 7/22/2011: http://www.multiupload.com/WTU98VP2D5
-Fixed WiFi issue (thanks to DocRambone for the fix)
-Fixed /system not being wiped properly during update
Installing:
Download and place somewhere on your /sdcard directory
Boot into CWM
Wipe Dalvik Cache
Wipe /data and /cache (you can skip this if you had flashed the r4-7/19/2011 previously)
Install this zip from sdcard
---
Rooting:
Flash su_busybox_misc-sam_tab_10.1-051511.zip using CWM / Rom Manager: http://droidbasement.com/galaxy/tools/su_busybox_misc-sam_tab_10.1-051511.zip
---
Before reporting any bugs please make sure you have followed these directions. If you are getting a boot loop you most likely missed one of the steps above.
If you are getting the "service temporarily unavailable message" you need to sign into your google account, it should go away after you do that
Have fun themeing and modding!
~Shev
Thanks to:
pershoot - for the update.zip and the rooting zip
mughalgxt - for finding and sharing the stock touchwiz update

Does this mean i am the first...
To try this.....HMMMMM - let me sleep over it.
Oh - what the heck!

is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!

Interesting....very interesting. Might have to give this a look-see...

rvrugg90 said:
is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!
Click to expand...
Click to collapse
No, this update will make it possible to create and use modified versions of the apps + framework resources contained within the touchwiz ROM (i.e create themes, etc)

Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?

Nice work here.

xSunny said:
Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?
Click to expand...
Click to collapse
Are you talking about the special tilt / pan control? Just tested that, still doesnt work, but it may be possible now to patch the problem if someone can find it (in the deodexed resources).

Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom

Yeah i still didnt go back to stock 3g im just hoping somebody can find it in this deoxed rom but lets see

Can you pleaseeeee hook me up with the 3g touchwiz .zip??? IV looked everywhere! My tab is sooo slow with the wifi version but the 3g version, even with errors, was smoking fast! Thanks!
je2345 said:
Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom
Click to expand...
Click to collapse
Sent from the best phone on the planet (SGS2) running the best ROM on the planet (Cognition S2)!

Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz

roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
I don't think it really matters when you flash root bro. Make sure you are using pershoots tools pack though.

roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
The linked root zip is optional, you don't have to flash right after, you can flash it whenever (but dont use any of the other rooting zips available for this tab, the linked one is the only compatible version). Your bootloop is probably caused by not wiping /data+/cache or the davlik cache. Follow the instructions in first post.

daddymatt said:
Can you pleaseeeee hook me up with the 3g touchwiz .zip???
Click to expand...
Click to collapse
Enjoy.
http://www.megaupload.com/?d=XBAH8X7P

Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...

nakedninja42 said:
Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...
Click to expand...
Click to collapse
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.

are you sure thats the 3G version? I went to download it and my pc sees it as exactly the same as the new wifi version... thank you sooo much for it either way! good looking out!!!

SellswordShev said:
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.
Click to expand...
Click to collapse
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?

nakedninja42 said:
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?
Click to expand...
Click to collapse
No if its not working in CWM it wont work if you do it through ROM manager. Redownload and verify the md5 hash from the original post. Boot into CWM recovery, wipe everything mentioned and retry.

[Q] Liberty Rom w/ 5.7.xxx

Hey guys,
This is my first post and first rom on my D3. I have, however flashed my D1 multiple times. So I have an idea about what i'm doing, but i'm not 100%. Anyhow, I was running 5.7 since it got released OTA. Was extremely happy with the fixes that came out in that ver. Started searching around and ended up flashing Liberty3 2.0 a few weeks ago. I noticed the battery drained somewhat fast when idling. So I did some searching and installed the speedy v7 script. Even got the "it works!" file when i looked in root browser. I also made sure to wipe data, reboot multiple times, wipe battery states and click my heels 3 times.
Battery life probably improved a bit, I still dont think its as good as stock 5.7. It is probably acceptable, but I am used to charging my phone before I go to sleep. Having around 90% battery life when i wake up, and being able to run on that one charge for almost 24 hours. This may be attributed to the surprisingly good sleep policies in the stock blur battery manager. I would love to have those built in to liberty. But I think that some of it also has to do that when I flashed liberty, my version dropped to 5.6.890.
Now after reading the entire thread for Liberty3 2.0, I see that people say to "apply hascode's patch" for 5.7. The thing is, no one links it. Did some poking around and are they talking about the second link from the bottom of this page:
hash-of-codes.blogspot.com/p/android-downloads (please add .html, i am new)
If so, do i just drop it on the SD card, boot in to safestrap and apply the zip?
Sorry this is long-winded. I just wanted to explain the extent that I have gone through before asking a question.

dtr3030 said:
If so, do i just drop it on the SD card, boot in to safestrap and apply the zip?
Sorry this is long-winded. I just wanted to explain the extent that I have gone through before asking a question.
Click to expand...
Click to collapse
Yeah, just install the rom and patch, both from clockwork recovery (cwr/safestrap). That patch is for his cm7 build I believe but I would still give it a shot if I was you, worst that happens is you have to restore a backup w/cwr and it might be what you need.

Haha again no link. It's a mystery patch!

it's there. i'm a noob and cant post links. thats why i said "someone please add .html"
but here it is again:
hash-of-codes.blogspot.com/p/android-downloads . h t m l
i looked again right now and the bottom two look like rooted stock roms. the one just above that labeled "Users of OTA 5.7.894 apply this patch (after applying main .zip) md5sum 46c140b55469ab557cd053e992142223" might be what i'm after. i'm still on 5.6 tho.

hashcodes patch will work for liberty if youre installing it on 5.7.894. Yes it is for CM7, but it works for CM9/Liberty and probably all AOSP roms. I havent tried it with a blurrred rom. http://hash-of-codes.blogspot.com/p/android-downloads.html is the link (lol)

MrJudylicious said:
hashcodes patch will work for liberty if youre installing it on 5.7.894. Yes it is for CM7, but it works for CM9/Liberty and probably all AOSP roms. I havent tried it with a blurrred rom. http://hash-of-codes.blogspot.com/p/android-downloads.html is the link (lol)
Click to expand...
Click to collapse
What does it do btw?

I'm trying to figure out how to push my system to 5.7 while running liberty. Somehow I went from stock 5.7 to liberty 5.6. I still have the verizon system update on my sd card cuz I had debloated before and needed to manually update. It was 50mb I think. I don't think that will update libery tho, will it?
I assume the hashcode patch is his own system tweaks and fixes.

Thanks for sharing this. BTW, do you know how I would go to 5.7 when I already have Liberty3 2.0 running over 5.6? I have no idea how this whole bootstrap thing works... More complicated than HTC and Samsung where you'd only get bootloader and recovery...
I'm using SafeStrap 1.6 and I'd like to not delete any settings I currently have. If that is possible...

what you should do is return to stock blur 5.6.890 (i prefer to sbf but ive received a lot of flack for it). Once on stock, root, install OTA rootkeeper from market, download the 5.7.894, install via stock recovery. Restore root from OTArootkeeper, install safestrap 1.06, install recovery from within the app, restart, hit menu during boot menu, make a backup, toggle safe system, format /system (under mounts and storage), install liberty, install hashcodes 5.7.894 patch!!!, factory reset clear data/cache, boot it up.
Obviously you would lose every settting you have. the idea behind safestrap is to leave your stock system untouched, and its about as surefire as it gets.

[Q] Upgrading to latest ICS leaks from stock, safestrap or not??

Hey guys.. My System Version is listed as being 6.13.215.XT894.Verizon.en.us. (This phone is about a week or 2 old for me) I have installed safetsrap recovery just to see how it works etc and have successfully installed the Eclipse port on the non-safe system. Now that I am done having fun with that, I would like to upgrade my system to newer leaked versions. My question is this: Should I uninstall safestrap before attempting to flash any of the leaked updates? How should I go about removing safestrap the "best" way? Also could someone please enlighten me with the correct "order" of these releases? EG: 6.11.200, 6.11.202, 206 etc. I guess I'm confused bc my system version starts with 6.13 instead of 6.11. Any help much appreciated!

I'm in the same boat as you, safestrap w/eclipse setup and I think I want to just switch to ICS 211
Pretty sure there are 2 methods, one with fastboot, and one with safestrap.
Fastboot method (droidforums.net/forum/droid-4-roms/212634-simplified-211-update-guide.html) definitely requires you to uninstall safestrap, but I think that automatically happens when you flash w/stock 219.
Safestrap method (droidforums.net/forum/search.php?searchid=4780372) allows you to just use a 211 ICS rom. But, I'm not sure if you already have to have done the fastboot ICS, I think you may have to fastboot ICS then install safestrap and safestrap into 211 ICS from 206 or 208 ICS.... Anyways, that's about where I am right now, trying to figure out if I safestrap to a 211 ICS rom from my current stock 219 GB, will it brick my phone. :/
---------- Post added at 12:46 PM ---------- Previous post was at 12:38 PM ----------
Oh also (droidforums.net/forum/droid-news/212864-another-ics-leak-here-droid-4-maybe-closer-ota.html) says that "212 ICS should be leaked soon". You may want to just hold tight, lots of new leaks means that something big (and easy to install for noobs like me ) may be coming soon .

The adventure continues...
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!

Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.

The Optimizer said:
Thanks for the quick response man... I'm glad to see I'm not the only one in this situation! I've been "creeping" on this board for 2 years now, (which I can't believe how fast that time went by) and thought it was about time that I start posting etc... you know what I mean, I see that was your 4th post so, that makes 2 situations where we are in the same boat! Thanks for the links brother I have actually read those, but need to checkup on them again... ALSO, my system downloaded an update the other day, (OTA) and was automatically going to install it (I clicked on download, thinking it would just download and wait for me to do the install manually like i have been used to in the past...) So, I tried to interrupt the download by throwing my phone into airplane mode really quick and then forcing a shutdown. Next time I turned on my phone I end up seeing the "Green Android with a triangle" screen, and a progress meter.. and I KNOW what that means. Something was flashed automatically by the phone. I got nervous, but my phone booted up perfectly, and I still had root, along with safestrap intact. I'm still a bit confused by what might've happened, but am relieved that my phone is still working perfectly... strangeness. I'll update this thread w any more info I can find. Thanks again!
Click to expand...
Click to collapse
Yup, same here, I'm just taking as much info in right now as possible. I think our options are eclipse, stock 219 with frozen apps, or ICS. Oh if you use stock at all, I'd recommend upgrading to 219, I think that was a major update, my battery life has just about doubled... then again I only had my phone for about a week before upgrading, and about 3 weeks total now.
kwyrt said:
Time out guys! First off, you cannot flash the ICS leaks in safestrap. The leaks are updates, not full ROMs. Second, you cannot flash a ROM based off the ICS leaks in safestrap unless you update you stock system to an ICS leak first. Well, you probably could, but it wouldn't boot. If you are on GB .215 you will need to update to .219 first. If you are on GB .219, and have not installed safestrap, you should be able to flash the an ICS leak via stock recovery without fastbooting. If you have installed safestrap, I believe you have to fastboot using the .219 file since safestrap changes something in the build.prop that will cause the leak update to fail.
Click to expand...
Click to collapse
Thanks for clarifying that ^^, kwyrt, I've read some of your other posts they are always quite informative!

Glad I could help! There are a LOT of nice, helpful people in these forums. Just keep asking questions! Doing some of this stuff can be nerve wracking even if you know what your doing. I actually, finally, got up the nerve to jump on the ICS leak train last night. If you decide to take the leap, I highly recommend using jsnweitzel's Droid 4 Utility located here: http://forum.xda-developers.com/showthread.php?t=1714596. Made the process much easier than it has any right to be.

Android 4.0.4 flash Success! =)
So I decided to take the leap last night... first thing I did was every way of factory resetting I know how to do hehe. (Privacy, factory reset under settings, then a data and dalvik clear in recovery) Downloaded the GB219 file, put it on my SD, fired up the Droid 4 Utility (thanks to everyone who contributed!) and had no problems at all upgrading. I wasn't worried about root so I skipped the OTA rootkeeper process. Next I needed to get to an ICS build. Again, I used the Droid 4 utility.... only difference being that we had to flash the boot.img file first.. (ICSFIX.img). On my first go, I successfully flashed the new boot.img (ICSFIX), but then got a sig verification error when trying to flash the OTA zip. ****. Soft brick at 2AM... heh. at least I still had plenty of time. Re-DL the OTA file, copied it over again and repeated the entire procedure, this time with success. Really Glad I decided to upgrade! Thanks guys!

[Q] [SOLVED] Odd Behavior After OTA update..

So here's what happened on my note..
I was running the XXLRQ rom rooted with CF-root kernel and then this OTA update popped up on my phone 2days ago (approx 5MB).. Since I just woke up that time and I don't know what hit me (stupid me) I continued with the update even if I'm aware that running OTAs on a rooted phone can give you problems.. And boy I GAVE ME ONE HELL OF A PROBLEM!
When the phone rebooted, it just shows the "galaxy note GT-N7000" screen and totally blank after that..
1. Did battery pull after 5mins and attempt to boot to recovery - no respone, still black screen after the "galaxy note GT-N7000" screen.
2. Was able to boot to download mode and flashed stock prerooted gingerbread Dr. Ketan's thread and i know that file is working fine since its on my computer for 1month already and ive flashed that copy 100% fine - flashed ok via pc odin, rebooted but still same behavior.. cant get into recovery also to do a full wipe.
3. Flashed my XXLRQ rom copy on my computer - phone booted up fine with all my info in it then I got the SIM-Lock and no root (since the CFroot kernel was overwritten perhaps?)
4. Was able to root it and since I just want a clean phone again, tried reflashing the Prerooted Gingerbread again via Mobile ODIN v2.30 (this has never failed me ever since) but the problem reappeared! - cant get into recovery either..
5. So I was left with no choice but to flash that XXLRQ again via PC ODIN and root with PhilZ's stock kernel that i just found out 2days ago since its very new.. - EVERYTHING went fine with no glitches or hiccups and was able to wipe everything clean (data/cache/dalvik).
6. Tried flashing Prerooted Gingerbread again.. Mobile odin passed but problem reappeared.. Same case with PC odin..
7. Reflashed XXLRQ again from MOBILE ODIN this time and added PhilZ's kernel and everything went fine..
7. Ran the EMMC Brickbug Check to make sure my phone is still in pristine condition and it PASSED the test.
So here's my question:
1. Any ideas what happened there? what was that update from the XXLRQ rom?
2. Moving back to gingerbread using PC ODIN should wipe everything fresh when it comes to the aspect of bootloader/kernels but not the data which should be wiped clean by wiping from recovery right?? so why is the problem persistent..
Now I'm not confident enough to flash this phone again because it might have a problem lying deep inside that cant be fixed by wipes...

Anything
but most likely cache or dalvik cache/unclean update procedures. Either cf stuff or ics stuff could also conflicted.
Gb flash was probably nonwipe rom, so stuff from ics rom/cf kernel conflicting with gb stuff. A factory reset in gb, which is safe, ICS not, could have solved that. Update back to ics was probably a fluke, unless the conflicting stuff was overwritten with the ics rom/modified kernel.
Clean procedures safely executed are always best to prevent this. This includes original components unmoddified for otas and kies update ability.
Off topic tip: efs backup, cause that seriously go wrong with updating.
Sent from my GT-N7000 using Tapatalk 2

Recently there were some minor updates from LRQ streamlined to the phone itself (which has LRQs installed already), these minor revisions (some says) increased the performances of the phone itself.
1. Yes that small update was for the LRQ rom itself... minor updates I should say. The cause on why your phone almost got toasted was and is still unclear to me though. It could be perhaps your phone was never toasted.. You should have perhaps waited more than 5 minutes before.. I'm sure it would have booted up still. But I guess the fact of the matter is,, you panicked after that (after seeing the Note's Logo for 5 minutes only)... He'll I've seen and even experienced my phone to boot up (after flashing a custom rom) around 10 minutes tops... but I did not get fidgety or panicky about it... I guess you may have just push the panic button all too soon bud... You could have waited perhaps even like 8 mins to really verify if it already stucked on the boot logo thing...
2. Going back to Stock GB does not WIPE your phone clean.. you have to initiate really a manual wipe once your in stock GB.. WIPE data/partition, dalvik cache... that is to me the surefire way to wipe clean all the cluttered remnants of the previous ROM you've used before.

It was the Update of N7000XXLRT

nokiamodeln91 said:
It was the Update of N7000XXLRT
Click to expand...
Click to collapse
what makes you say it's the XXLRT when the OP explicitly said he has XXLRQ already on his phone, when an OTA update popup on his screen.
your post is kinda misleading and confusing...:

capitansid said:
So here's my question:
1. Any ideas what happened there? what was that update from the XXLRQ rom?
Click to expand...
Click to collapse
letters_to_cleo said:
what makes you say it's the XXLRT when the OP explicitly said he has XXLRQ already on his phone, when an OTA update popup on his screen.
your post is kinda misleading and confusing...:
Click to expand...
Click to collapse
Yes the OP was on LRQ and he got an OTA of 5MB which i meant was the update for LRT
Country/Carrier Date Final PDA Size
Germany 7 Sep 2012 N7000XXLRT 5.7 MB

baz77 said:
Anything
but most likely cache or dalvik cache/unclean update procedures. Either cf stuff or ics stuff could also conflicted.
Gb flash was probably nonwipe rom, so stuff from ics rom/cf kernel conflicting with gb stuff. A factory reset in gb, which is safe, ICS not, could have solved that. Update back to ics was probably a fluke, unless the conflicting stuff was overwritten with the ics rom/modified kernel.
Clean procedures safely executed are always best to prevent this. This includes original components unmoddified for otas and kies update ability.
Off topic tip: efs backup, cause that seriously go wrong with updating.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ahh yes, I have the EFS backup already and its copied everywhere.. LOL
letters_to_cleo said:
Recently there were some minor updates from LRQ streamlined to the phone itself (which has LRQs installed already), these minor revisions (some says) increased the performances of the phone itself.
1. Yes that small update was for the LRQ rom itself... minor updates I should say. The cause on why your phone almost got toasted was and is still unclear to me though. It could be perhaps your phone was never toasted.. You should have perhaps waited more than 5 minutes before.. I'm sure it would have booted up still. But I guess the fact of the matter is,, you panicked after that (after seeing the Note's Logo for 5 minutes only)... He'll I've seen and even experienced my phone to boot up (after flashing a custom rom) around 10 minutes tops... but I did not get fidgety or panicky about it... I guess you may have just push the panic button all too soon bud... You could have waited perhaps even like 8 mins to really verify if it already stucked on the boot logo thing...
2. Going back to Stock GB does not WIPE your phone clean.. you have to initiate really a manual wipe once your in stock GB.. WIPE data/partition, dalvik cache... that is to me the surefire way to wipe clean all the cluttered remnants of the previous ROM you've used before.
Click to expand...
Click to collapse
1. Hmmmm maybe you are right about waiting longer than 5mins.. But i cant say i panicked.. because I just thought that its only a 5mb update so it should not take long to reboot.. I just thought that theres a problem because it did not bother showing up the boot animation so it means it cant pass the proper boot up sequence to proceed with the android update.. (feel free to correct me.. its just my own understanding )
2. Yes I am aware that flashing back to GB cant wipe the data/cache/dalvik but it should wipe out the kernel and any other problems that would keep it from booting into recovery.. but it didnt.. flashing back to GB should give me the stock GB recovery and i should be able to boot to recovery but i failed..
nokiamodeln91 said:
Yes the OP was on LRQ and he got an OTA of 5MB which i meant was the update for LRT
Country/Carrier Date Final PDA Size
Germany 7 Sep 2012 N7000XXLRT 5.7 MB
Click to expand...
Click to collapse
Lesson learned.. Never do OTA updates EVER! :silly:
Thanks for the response guys! But i still have that question in the back of my mind.. What really happened on that update...? My strong guess is that CF root kernel did not like the update since its meant for an LRQ rom not for an LRT..
Edit:
How do I Edit the thread title to add [solved] to it???
Cant see any button that would help.. LOL

to update on OTA u need to be unrooted on stock kernel. then the ota seems to work finr
Sent from my GT-N7000 using xda premium
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
capitansid said:
How do I Edit the thread title to add [solved] to it???
Cant see any button that would help.. LOL
Click to expand...
Click to collapse
edit the first post
Sent from my GT-N7000 using xda premium

@captain sid....
it's better to stop getting OTA updates from now on... Kapish? do what you gotta do... if you wanna update your phone... two ways.. KIES or PC Odin. that's all.

nokiamodeln91 said:
to update on OTA u need to be unrooted on stock kernel. then the ota seems to work finr
Sent from my GT-N7000 using xda premium
---------- Post added at 01:51 PM ---------- Previous post was at 01:50 PM ----------
edit the first post
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
letters_to_cleo said:
@captain sid....
it's better to stop getting OTA updates from now on... Kapish? do what you gotta do... if you wanna update your phone... two ways.. KIES or PC Odin. that's all.
Click to expand...
Click to collapse
Yeah.. Learned that the hard way.. :highfive:

OTA Beta Updates

Hi,
One of my friends told me not to do OTAs beta updates because it could bootloop my phone.
Last update I flashed the zip and all worked perfectly fine, but I had to re-root my phone and re-uninstall annoying stock apps with titanium backup.
Now I have a question :
Is it really risked to do the update with an OTA download ?
I really don't want to re-root my phone and do all the other stuff that comes with it.
I guess there is a way to do a safe update which keeps my data with the OTA but I need a confirmation about that.
Thanks !
(Original post [here] but probably faster answers on this forum, I guess ?)

I think it is ok with official updates. I have not any issue. Just i have not rooted or etc. All stock

gioyocho said:
I think it is ok with official updates. I have not any issue. Just i have not rooted or etc. All stock
Click to expand...
Click to collapse
Thanks, but I would like to have the advice of somebody with approximatively the same setup as mine, I mean at least with a rooted op3t
If you have all stock, then I can't tell if doing the OTA update will re-stock my phone too

I always have stock phones, because early time when i tried root, unlock btl, install twrp, change rom... sometimes there were wrong things, examle booting only logo and phone make a stone looks like, also custom roms has some bugs and on stock i am sure that everything works good. I do not understan why people starting root, change roms or etc. Use stock always and everything will be ok

gioyocho said:
I always have stock phones, because early time when i tried root, unlock btl, install twrp, change rom... sometimes there were wrong things, examle booting only logo and phone make a stone looks like, also custom roms has some bugs and on stock i am sure that everything works good. I do not understan why people starting root, change roms or etc. Use stock always and everything will be ok
Click to expand...
Click to collapse
U better off using an iPhone
To answer OP, yes you can struck in bootloop.
Remember it's beta version and not stable release.