Not allowed to do any posts in the Android Revolution HD (ARHD) forum yet http://forum.xda-developers.com/showthread.php?t=1925402 so I'll share my experience here.
It seems like people sometimes have various issues after a Note II N7100 upgrade to AHRD rom 4.3 20.0 (or 20.1) , from earlier 4.1.2 versions like 19.0 and after reading all posts of this upgrade of various tips, fixes and install steps, I felt it was time to try the upgrade myself. It turned out to be successful without any issues with root working as well as everything else with a "butter" smooth experience since 2 weeks back..
These are the steps I followed.
- There was some importance regarding a specific bootloader that was recommended to flash first and also a custom recovery.
I was in version AHRD 19.0 on bootloader LJ3 but MJ5 was recommended most often. So MJ5 was flashed with Odin v3.09
- Next a custom recovery was mentioned and it seemed that most people were successful with TWRP 2.6.3.1
So I flashed TWRP 2.6.3.1 with Odin v3.09.
- Then the AHRD 20.1 rom was transferred to EXT SD card on the phone.
- Next, a wipe of data was done in TWRP
- Then the rom AHRD 20.1 rom was flashed after following the AROMA install procedure.
- After successfull boot, all my apps were installed from my Titanium backups.
Good you shared this with people who having trouble... but some may ask if you were able to update the SuperSU... then reboot and see if you still have root?
TWRP or Philz touch recovery (6.1.28) seem to work good (less problems).
Someone else also posted success like this:
1. Flash latest Philz touch recovery (6.1.28).
2. wipe everything (pick option flash new rom).
3. flash ARHD 20.1.
4. Reboot and set up everything like usual.
5. Update supersu and everything else/ restore titanium backup
Good luck to all.
cyberboob said:
Good you shared this with people who having trouble... but some may ask if you were able to update the SuperSU... then reboot and see if you still have root?
TWRP or Philz touch recovery (6.1.28) seem to work good (less problems).
Someone else also posted success like this:
1. Flash latest Philz touch recovery (6.1.28).
2. wipe everything (pick option flash new rom).
3. flash ARHD 20.1.
4. Reboot and set up everything like usual.
5. Update supersu and everything else/ restore titanium backup
Good luck to all.
Click to expand...
Click to collapse
Yes, root remains after SuperSU update and reboot !
Related
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Info:
Computer OS: Windows 7 Ultimate (64-bit)
Firmware Version: PDA:LH1 /PHONE:LH1 / CSC:LH1 (TMB) - (Ver. 12.07.20.02) (current)
Binary: Samsung Offical (Kernal 3.08 ICS)
Build Number: IMM76D.UVLH1
ROM: Stock T-mobile Android 4.0.4 (before i flashed cyanogenmod9)
Baseband Version: T989UVLH1
Brand: Samsung
Model: SGH-T989 (hercules)
Type: Galaxy S2 X
Carrier: T-Mobile, USA
Country Code: 1 (USA)
Access Point: epc.tmobile.com
Odin3: v3.07
Clockwork Recovery: v5.0.2.7
Root: tmobilegalaxys2rootICS -> CWM-SuperSU-v0.87 (updated can't view newer version right now)
Cyanogenmod9: cm-9.1.0-hercules
Google Apps: gapps-ics-20120317-signed
spikeguy4 said:
What happened: Samsung Galaxy S2 tmobile SGH-T989 (more info at the bottom)
Ok so I installed the usb drivers through kies and got the latest firmware from kies. Installed Odin 3.07. Backed up my stuff. Flashed recovery-cmw-hercules using Odin. Then I rooted my phone using tmobilegalaxys2rootICS (flashing with CWM recovery) and installed CWM-SuperSU v0.87. Updated root and CWM on the next boot using SuperSU app and Rom Manager to the current version (non touch for CWM). I then got cyanogenmod9.1.0-hercules (stable) and gapps-ics-20120317-signed. I wiped the internal SD card and external SD card. Went into recovery manager. Did a factory reset, cache wipe, dalvik wipe, battery stat wipe. Flashed cyanogen9, flashed gapps, fixed permissions and rebooted. Now i'm stuck in a bootloop just looking at the start up screen of cyanogenmod. I have access to the recovery menu and the odin screen so i'm not bricked as far as i know, just bootloop'd. I read somewhere of a super wipe by JDT or someone along those lines but i can't find those scrips to flash them. Any help would be great. Thanks!
Click to expand...
Click to collapse
Hey! As of I know, you are not using a TOUCH recovery. Sad to say but a lot of ROMs will only work on TOUCH recovery, because they changed something in the Cache wiping that ain't screwing up with device or something (as I understood digging up a little bit).
Here is my advice, go with this for now:
MIRROR
It's v13.1 of Sk8er's recovery. Though I want to tell you, if you try to hardboot into it (what I mean is: hold +/- volume and plug in USB) it probably won't work since it doesn't work for me for a weird reason (I'm on v13.0 so I couldn't say for v13.1).
In EXTRAS you got the cache.wipe and the super.wipe of TDJ.
And another thing I think you should know about this device is HOW TO FLASH CORRECTLY.
Here is the way:
Make a backup (optional)
SUPER WIPE (using TDJ tools)
Factory Reset (wipes data/cache/.....)
Install your rom (without GApps)
Reboot phone.
Wait for let's say 10 minutes (optional as well I don't do it but it's recommended... Just reboot, and when you see no bootloop, go back to recovery for next)
Wipe cache/dalvik (without using TDJ but only from recovery touch)
Install gapps.
Reboot.
if you just update your rom, like going from a nightly to another nightly, no need to follow this. Just wipe cache and dalvik using recovery touch, and you are good going.
Cheers!
I'll try it!
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
spikeguy4 said:
Thanks switchfoot! I'll try this today. I'll grab the cache wipe and super wipe as well as upgrade to touch-cwm however i'm a little worried when you say skaters mod made you unable to hard boot, seems risky as that's your last resort if you brick the device (as far as i know). Thank you so much for the steps on flashing, I read so many different ways I was very confused on the proper procedure. I have class today so I probably won't report back till later today but i'll let you know what happens!
Click to expand...
Click to collapse
My friend here is a flawless recovery with 0 issues if you are worried about the one above TWRP 2.2. Also stay on one site for everything and may I suggest xda only. Do not venture off not that the other sites are issues just that you will confuse yourself although rootzwiki is just as good.
There is plenty of How To's here in xda that you do not need to be confused, confusion comes when you start asking others there opinions and take bits and pieces from all of them... Good luck and feel free to pm me if you need any further help... Just please read up before you do anything
These are the exact instructions from CM on how to install their rom: did you follow these instructions
Installing
How to INSTALL from another ROM (DO NOT SKIP ANY STEPS!):
Be sure to back up your current ROM!
Update your radio to the above recommended version if you have not already done so. (See the list below)
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON NON-TOUCH CWM RECOVERY: Install darkside-wipe-cache-only.zip (which fixes bootloop due to bad /cache format)
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
Awesome!
Wow that's exactly what i was looking for! Thank you! I just flashed a stock rom to go back to the start. I'll begin the process over again following these steps. The only issue is that the radio update section in the guild no longer exists. Is it ok to go on without the radio update? Or will this cause issues? If so is there a mirror for them?
SOLVED!
OK! I'm all set now. I had to use the full wipe as well as the cache wipe after install and the bootloop was resolved. The bigger headache was when kies failed at updating the firmware so i had to do an emergency firmware flash. Any way i have clockwork, root with SuperSU, cyanogenmod9.1.0, and the latest google apps! Plus its backed up now! YAY! Now i just have to configure it to how i like and we'll be in business! Thanks for all your help guys! I really appericate it!
Last thing
I still need the radio update since the file no longer exists in your link. Everything is good but I don't have any wifi calling or features of that order. Which are important in keeping my usages down and getting coverage in my house and otherwise bad areas. Where do I get this and would I just install it via CWM? Thanks again!
Hey guys, I was playing around on my phone, and I downloaded something off of 4shared (just a game) and it crashed and made my phone freeze. I then held my power button and waited for it to boot but now im stuck in a bootloop with the stock telus rom... is there anything I can do that wont wipe everything on my phone? Oh and I can get into both CWM recovery and download mode.
I gave it some more time to startup and it pretty much factory reseted my phone. I get that thing to setup my phone after startup. Everytime I turn my phone off it goes back to this screen and my phone restarts. If I surf through the files of my phone, it shows I still have everything but It doesnt show any of my apps or anything.
Hey guys/gals,
I recently bought a Koodo Galaxy s2x. After a few weeks I looked online and saw that there were some JB Roms for my phone. I couldn't resist and tried to flash one after rooting. I didn't have many problems with it, but there were some glitches that started to bug me, so I decided to see about going back to stock (I should have done this first I know). So then after hours(many) of searching, the best I could find was a T-Mobile stock Rom I decided to try and flash it (both times via odin). I also read somewhere that I should use darkside superwipe to clear my cache, so I tried that, but ever since that CWM stopped working on my phone. anytime I tried to do any back up or anything it just froze, and I had to hard boot. Finally I just tried flashing T-Mobile stock ICS, and Odin said "Failed". I decided to just unplug my phone, as I thought I already screwed it up, but after rebooting, the T-mobile Rom worked. I don't understand why it works fine if the Flash Failed. Now, I can no longer connect to kies (I'm hoping official JB will be shipped soon!), and I am wondering if I can somehow return to a stock Koodo Rom, and if it will connect to Kies again, as it previously had. I have looked a lot and have not found anything that I fully understand. I'm not overly experienced, which is why I should not have flashed to begin with. This is the closest thread I have found to help me, but I don't fully understand what all I need to do:
"Haven't seen anyone shared this yet.
Here's the KOODO ICS 4.0.4 stock ROM I used CWM to flash to stock after I tried the custom ROM.
h t t p s : / / sourceforge.net/projects/koo...d.zip/download
I also flashed DARKSIDE.SUPER.WIDE before I flashed this or you can used CWM Recovery 6.0.1.2 to wipe system and cache."
Is it possible for me to get back to stock phone? and still connect to Kies? and then possibly upgrade to JB through Kies if Hercules ends up receiving it?
Thanks for any help you can give me. Here is all my current phone info incase this helps:
Model:
SGH-T989
Android Version:
4.0.3
Baseband version:
T989DTLLG2
Kernel version:
3.0.8-perf-T989UVLE1 -CL508451
[email protected] #1
SMP PREEMPT Sun May 6 15:07:07 KST 2012
Build number:
IML74K.UVLE1
Thanks.
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: https://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
arcsine said:
If your ultimate goal is to get Jellybean on your phone, check the development section of this subforum. There are numerous stable and wonderful JB roms (AOKP Milestone 6, Liquid Smooth, CM10).
To get back to your stock ROM, download it from here: h t t p s ://sourceforge.net/projects/koo...d.zip/download
Then, go into recovery (NOT odin), and flash the rom.
Click to expand...
Click to collapse
That link doesn't work, it says cannot find page. Also, my phone is currently not rooted, does it have to be rooted to flash from recovery? if not what do I do to flash from recovery? I know how to get into recovery, but after that do I use 'apply update from external storage'? Do I have to wipe the cache first?
Thanks.
PS: I just want to be able to get back to stock for now. At least until I learn more about flashing Roms. There is still lots for me to learn, like kernels, radios, Nightly's for official Roms, or even how to properly flash a rom without feeling lost. If I know a way to get back to stock comfortably, It will give me more reason to try some other Roms (once I learn how).
Here is a working link to the stock Koodo ROM: http://sourceforge.net/projects/koodostock/files/KOODO_SGH-T989D_Stock_Signed.zip/download
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted: http://galaxys2root.com/t-mobile-galaxy-s2/how-to-root-icsgb-on-t-mobile-galaxy-s2-sgh-t989/. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
arcsine said:
Here is a working link to the stock Koodo ROM:
Are you running a custom ROM right now or your stock ROM? If you're running a custom ROM, it should come with root privileges. If you are running the stock ROM, you can just back it up instead of needing to download the zip from sourceforge. This guide will help you get rooted:. After rooting, get into recovery mode (if you can't get the button combinations to work, there is an app. called quick boot which reboots you into recovery/bootloader/etc). If you don't have a recovery or it's corrupt, download ROM manager from google play, and choose the 'install clockwork recovery'. Reboot to recovery to make sure it works, then uninstall rom manager (it's been known to cause bugs if you use it for other things - and I'd recommend other recoveries such as TWRP but it's a bit more advanced). From your recovery's screen, there should be a backup option. Make a complete backup and name it something appropriate. To flash a ROM, download it and put it on your storage drive. Reboot to recovery, and go to wipe. Wipe your data (factory reset), and system (only really need to wipe data in most cases, but be safe). To flash the custom ROM now (or flash the default ROM I just linked), there should be an option to 'install zip from sd card' or something similar. Choose that, browse to your ROM and install it. After installing, go to wipe and wipe your cache+dalvik cache, then reboot. There are several beginner guides sticked in the development forum, along with explanation of terms like radio/kernel/nightly/etc.
Click to expand...
Click to collapse
Thanks a ton... Worked perfectly! I'm hoping it will connect to Kies once again.. I'll let you know if it works.
Unfortunately, I still can't connect to Kies.. It just sits at the Loading status (for like 10-15 mins). But At least I don't have all of the T-mobile apps and stuff anymore!
Reposting as this was posted in wrong section:
Hi
I have been trying to upgrade from CM 10.1 (build 03212013 ) to Paranoid Android 4.4, since I see the new version has BLN support (I'd stuck with the old CM for so long due to this).
Anyways upon trying this I discovered I had to (always ran clear cache, and ran the T989 script super -wipe)
- update my modem to the latest t-mobile - upgraded to the latest which is needed - UVMC6
- was trying to install with CWM 5.8.x - but it would just 'hang' at "installing ZIP" further research indicates I need to upgrade CWM
- Upgraded to CWM 6.0.4.3 per more searching, tried erase flash, just hangs - further research indicates this CWM has a known issue
- used ODIN to goto TWRP 2.7 - flashed, and booted, tried numerous times hangs at "teamwin' screen when trying to boot into recovery
Ended up giving up and Odin flashing back CWM 5.8.1.3 and loading my old CM 10.1 build again
Anyone have any hints why this is so difficult for me?
Need some help if possible please!
thanks
Jonathan
Found work around
Just want to update
I managed to find a work around of sorts. I needed to restore my phone back to CWM 5, and to do that I needed to use ODIN to flash it.
After flashing CWM5 back to the phone, I was able to restore previous ROM (CM mod 10.x), and boot up. After that I used the rommanager to re-install CWM 6.0.4.3, and reboot the phone into recovery.
When in recovery I went to mountand storage, and formatted , /cache, /system and /data. After doing that I choose to install ZIP from SDcard, and selected the Parandoid Android 4.4.x I was trying before. This completed, and installed without any error messages.
Hopefully this helps someone else out.
Thanks,
Jonathan
Hey all, haven't been keeping up on roms and updates for a while... I've been running JellyBomb rom since the first week the phone came out and had all the .zip's of MC2 / MA7 / MA5 / LK8 / LJC / LJ1 modems to run in TWRP. I got the zip for MK4 / NE2 yesterday and loaded the MK4 after a backup for safety, just looking to see if I'm safe to try the NE2 modem.
http://forum.xda-developers.com/showthread.php?t=2139889
I'm also seeing all the 4.4.4 rom's and I have a few questions, goomanager looks to be out of date these days and I'm still on TWRP V.2.5.0.1, I see on their site they are up to 2.8 (although I only see .zip for 2.7) for the Note 2 and still suggest to use goomanager. Can I just grab the .zip and load in TWRP recovery? I've got a fresh backup, so would I be able to go back to this backup from the 4.4.4 roms? Is it as easy as latest version of TWRP then wipe phone and load a 4.4.4 rom, or am I missing steps?
Thanks for any help:good:
kraftwerksfit said:
Hey all, haven't been keeping up on roms and updates for a while... I've been running JellyBomb rom since the first week the phone came out and had all the .zip's of MC2 / MA7 / MA5 / LK8 / LJC / LJ1 modems to run in TWRP. I got the zip for MK4 / NE2 yesterday and loaded the MK4 after a backup for safety, just looking to see if I'm safe to try the NE2 modem.
http://forum.xda-developers.com/showthread.php?t=2139889
I'm also seeing all the 4.4.4 rom's and I have a few questions, goomanager looks to be out of date these days and I'm still on TWRP V.2.5.0.1, I see on their site they are up to 2.8 (although I only see .zip for 2.7) for the Note 2 and still suggest to use goomanager. Can I just grab the .zip and load in TWRP recovery? I've got a fresh backup, so would I be able to go back to this backup from the 4.4.4 roms? Is it as easy as latest version of TWRP then wipe phone and load a 4.4.4 rom, or am I missing steps?
Thanks for any help:good:
Click to expand...
Click to collapse
It's safe to flash any modem for any rom including the NE2 modem. The 2.8 version of TWRP is linked in the thread here in development section. @jlmancuso posted a fixed version of 2.8 towards the last couple of pages in the thread so search for it because it's NOT on the site. It works fine but you can safely use Phil's recovery 6.07.9 or the newest version from his website (linked from the thread here in development) if you have any doubts or issues using it. Also be aware of the bootloader issue which causes the phone to not charge when powered off. If you have this problem on a MK4 or NE2 based TW rom then you will need to update your bootloader. This has been covered in the Community ROM thread. @jlmancuso posted a flashable bootloader in his thread on one of the last few pages. That pretty much sums it up.
FYI. Concerning nandroid backups, you must create and restore the backup from the same recovery. It is highly recommended to use Phil's recovery 6.07.9 or newest version for backups because TWRP backups are not cross compatible. So if you haven't done so already, use Phil's for your nandroid backup and go over the backup settings to include/exclude the items you want to include or exclude in your backup.
tx_dbs_tx said:
It's safe to flash any modem for any rom including the NE2 modem. The 2.8 version of TWRP is linked in the thread here in development section. @jlmancuso posted a fixed version of 2.8 towards the last couple of pages in the thread so search for it because it's NOT on the site. It works fine but you can safely use Phil's recovery 6.07.9 or the newest version from his website (linked from the thread here in development) if you have any doubts or issues using it. Also be aware of the bootloader issue which causes the phone to not charge when powered off. If you have this problem on a MK4 or NE2 based TW rom then you will need to update your bootloader. This has been covered in the Community ROM thread. @jlmancuso posted a flashable bootloader in his thread on one of the last few pages. That pretty much sums it up.
FYI. Concerning nandroid backups, you must create and restore the backup from the same recovery. It is highly recommended to use Phil's recovery 6.07.9 or newest version for backups because TWRP backups are not cross compatible. So if you haven't done so already, use Phil's for your nandroid backup and go over the backup settings to include/exclude the items you want to include or exclude in your backup.
Click to expand...
Click to collapse
Awesome thanks!
looks like I've got a bunch of reading to do then... everything has changed. I grabbed Philz touch 6.48.4-l900.zip, looks to be the latest/last update. I'll look into that flashable bootloader next.
I may just stay with jellybomb as the phone just works so well. After I do a fresh backup with Philz recovery can I go to a 4.4.4 rom and back to the backup of older 4.1.2 jellybomb rom? Anyway, thanks for the info and pointing me in the right direction! I'll read up and report back if need be.
kraftwerksfit said:
Awesome thanks!
looks like I've got a bunch of reading to do then... everything has changed. I grabbed Philz touch 6.48.4-l900.zip, looks to be the latest/last update. I'll look into that flashable bootloader next.
I may just stay with jellybomb as the phone just works so well. After I do a fresh backup with Philz recovery can I go to a 4.4.4 rom and back to the backup of older 4.1.2 jellybomb rom? Anyway, thanks for the info and pointing me in the right direction! I'll read up and report back if need be.
Click to expand...
Click to collapse
Yes you can flash back to an older pre 4.4 TW rom or any AOSP rom. Just stick with Phil's recovery because it's compatible with both TW and AOSP. I like the ui of TWRP better but reliability is a priority and Phil's does it all best. Good luck.
If you have ever taken the MK4 (4.3) or NE2 (4.4) OTA then your bootloader should be fine. If you've never taken the MK4 or NE2 OTA then you will most likely have the no charge issue when powered off (phone will reboot instead of charging when you plug in the charger while powered off). so you will have two choices: find and flash the bootloader that @jlmancuso posted in his Community ROM thread OR flash a stock unrooted rom with flash count reset and take all the OTA's until you are up to NE2 KK 4.4... then odin flash Phil's recovery (same version as mentioned above but its a md5.tar file) and make sure you uncheck the reboot device option in Odin and immediately pull the battery once it finishes flashing. Then reboot straight to recovery and immediately go into Phil's settings and select the re-root phone option. From that point you will be stock 4.4 unrooted WITH KNOX.. Next you will need to download and install SuperSU from the Google Play Store then immediately open SuperSU and let it remove KNOX from your phone (unless you want it). Then you can reboot to recovery and flash whatever rom you want.
tx_dbs_tx said:
Yes you can flash back to an older pre 4.4 TW rom or any AOSP rom. Just stick with Phil's recovery because it's compatible with both TW and AOSP. I like the ui of TWRP better but reliability is a priority and Phil's does it all best. Good luck.
If you have ever taken the MK4 (4.3) or NE2 (4.4) OTA then your bootloader should be fine. If you've never taken the MK4 or NE2 OTA then you will most likely have the no charge issue when powered off (phone will reboot instead of charging when you plug in the charger while powered off). so you will have two choices: find and flash the bootloader that @jlmancuso posted in his Community ROM thread OR flash a stock unrooted rom with flash count reset and take all the OTA's until you are up to NE2 KK 4.4... then odin flash Phil's recovery (same version as mentioned above but its a md5.tar file) and make sure you uncheck the reboot device option in Odin and immediately pull the battery once it finishes flashing. Then reboot straight to recovery and immediately go into Phil's settings and select the re-root phone option. From that point you will be stock 4.4 unrooted WITH KNOX.. Next you will need to download and install SuperSU from the Google Play Store then immediately open SuperSU and let it remove KNOX from your phone (unless you want it). Then you can reboot to recovery and flash whatever rom you want.
Click to expand...
Click to collapse
Yeah no over the air updates on my phone and I found that fix/thread on the community ROM encase I do run into that issue. I did swap over to that latest/last version of Philz Recovery and all is well, also ran a fresh backup, also with you on the UI but like you said as long as it works.
Let me ask you this, after I update the bootloader to NE2 that bootlader will still work with my backup of 4.1.2?
So does the procedure go - load 4.4.4 ROM/wipe and factory data reset in recovery > update bootloader in recovery > done?
Looking at the 4.4.4 Dirty Unicorns or the 4.4.4 Liquidsmooth , just want it to run solid.
Again thanks for the help/info!
tx_dbs_tx said:
so you will have two choices: find and flash the bootloader that @jlmancuso posted in his Community ROM thread OR flash a stock unrooted rom with flash count reset and take all the OTA's until you are up to NE2 KK 4.4... then odin flash Phil's recovery (same version as mentioned above but its a md5.tar file) and make sure you uncheck the reboot device option in Odin and immediately pull the battery once it finishes flashing. Then reboot straight to recovery and immediately go into Phil's settings and select the re-root phone option. From that point you will be stock 4.4 unrooted WITH KNOX.. Next you will need to download and install SuperSU from the Google Play Store then immediately open SuperSU and let it remove KNOX from your phone (unless you want it). Then you can reboot to recovery and flash whatever rom you want.
Click to expand...
Click to collapse
Is that right? or did you mean I'd be stock 4.4 rooted with KNOX? If I remember you can't run SuperSU unrooted, right?
So far I grabbed these zip's:
gapps-kk-20140606-signed.zip
NE2-screen-mirroring-fix.zip
tw-4.4.2-power-off-charge-fix.zip
Is that NE2 screen mirroring fix needed most of the time too?
I ran a titanium backup, I pulled the titanium backup and full backup using Phil'z recovery to my computer. I'd like to clear internal and external without loosing root as internal data is cluttered/full, is their a procedure to do that or do I need to do a factory data reset then reroot?
Thanks tx_dbs_tx:good:
Hey guys so i've had a rooted note 2014 for awhile now and want to get into custom roms. I'm on stock 4.4.2 and i'm trying to flash liquidsmooth but have a couple of questions. So on the installation guide it says
"First time installing LiquidSmooth to your Samsung Samsung Note 10.1 (2014), or coming from another ROM:
- Make sure you're running latest Recovery
- Copy GApps zip, SuperUser zip and Liquid ZIP to your internal SDCard
- Boot into Recovery
- Flash Liquid zip from internal SDCard
- Flash GApps zip from internal SDCard
- Reboot
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!"
It seems simple enough but how do I know if i'm running the latest recovery? Also is there any other things I need to do or know before I attempt this?
Dachank said:
Hey guys so i've had a rooted note 2014 for awhile now and want to get into custom roms. I'm on stock 4.4.2 and i'm trying to flash liquidsmooth but have a couple of questions. So on the installation guide it says
"First time installing LiquidSmooth to your Samsung Samsung Note 10.1 (2014), or coming from another ROM:
- Make sure you're running latest Recovery
- Copy GApps zip, SuperUser zip and Liquid ZIP to your internal SDCard
- Boot into Recovery
- Flash Liquid zip from internal SDCard
- Flash GApps zip from internal SDCard
- Reboot
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!"
It seems simple enough but how do I know if i'm running the latest recovery? Also is there any other things I need to do or know before I attempt this?
Click to expand...
Click to collapse
Hi. Did you flash TWRP? I rooted then used flashify to install TWRP 2.8.5.0. I have had success using TWRP 2.8.5.0 but for some people issues this version and the have to use 2.6.3.1.
LiquidSmooth maintainer for d2usc/vzw & p600
Orion116 said:
Hi. Did you flash TWRP? I rooted then used flashify to install TWRP 2.8.5.0. I have had success using TWRP 2.8.5.0 but for some people issues this version and the have to use 2.6.3.1.
LiquidSmooth maintainer for d2usc/vzw & p600
Click to expand...
Click to collapse
I actually just went ahead and put 2.8.6.0 on there with odin and flashed your rom and it worked out alright. Do you happen to know what problems people were having with 2.8.5.0? Great ROM btw
Dachank said:
I actually just went ahead and put 2.8.6.0 on there with odin and flashed your rom and it worked out alright. Do you happen to know what problems people were having with 2.8.5.0? Great ROM btw
Click to expand...
Click to collapse
Wiping data and cache mainly. And thank you.
LiquidSmooth maintainer for d2usc/vzw & p600