Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Root with NRT (Video by Rootjunky)
More videos here: http://www.wugfresh.com/videos/
Ah,.. So nice to see this. Thank you!
Sent from my Nexus 9 using XDA Free mobile app
Cool
btw twrp is out.
tyvar1 said:
Cool
btw twrp is out.
Click to expand...
Click to collapse
Yes, it will auto update on first run and it will know twrp is out. Full root support. And everything.
Sent from my Nexus 5 using Tapatalk
WugFresh said:
Yes, it will auto update on first run and it will know twrp is out. Full root support. And everything.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I usually flash my recovery the old fashioned way lvia fastboot like I did yesterday with the first version of TWRP but I decided to flash the newer version of TRWP with the Tooolkit. I was unencrypted prior to using the Toolkit and when it did the modified boot.img my device rebooted and encrypted itself. I assume I can just restore my backup from yesterday to go back to unencrypted.
nrage23 said:
I usually flash my recovery the old fashioned way lvia fastboot like I did yesterday with the first version of TWRP but I decided to flash the newer version of TRWP with the Tooolkit. I was unencrypted prior to using the Toolkit and when it did the modified boot.img my device rebooted and encrypted itself. I assume I can just restore my backup from yesterday to go back to unencrypted.
Click to expand...
Click to collapse
This makes no sense. Yes to your question. But how did you come to that conclusion? Can you add me on Google hangouts chat.
Sent from my Nexus 5 using Tapatalk
WugFresh said:
This makes no sense. Yes to your question. But how did you come to that conclusion? Can you add me on Google hangouts chat.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Started a hangouts chat
Tnx for this tool.
I did something wrong(fix permission) in twrp and i got boot-looped.
then i thought it would be smart o delete everything on the device...(not my brightest moment)
used the tool to flash stock + unroot.
Worked fine but:
When finishing it couldn't connect to the network when it was setting up.
I resolved this by rebooting.
Then when i put my backup back from Google play the navigation bar was missing and the notification tray was missing too.
I resolved that by doing a factory reset.
tnx again.
berendspruijt said:
Tnx for this tool.
I did something wrong(fix permission) in twrp and i got boot-looped.
then i thought it would be smart o delete everything on the device...(not my brightest moment)
used the tool to flash stock + unroot.
Worked fine but:
When finishing it couldn't connect to the network when it was setting up.
I resolved this by rebooting.
Then when i put my backup back from Google play the navigation bar was missing and the notification tray was missing too.
I resolved that by doing a factory reset.
tnx again.
Click to expand...
Click to collapse
Thats a lot of rando weirdness, you may want to flash stock again. Glad to hear its helped you.
{{ WugFresh }}
nrage23 said:
Started a hangouts chat
Click to expand...
Click to collapse
Determined to be kernel related. I am looking into whats involved with unencrypted N9 devices now though, and will see what I find out.
{{ WugFresh }}
Added the new LRX21R to the kit, just hit update and you will see it in the pull down list.
{{ WugFresh }}
berendspruijt said:
Tnx for this tool.
I did something wrong(fix permission) in twrp and i got boot-looped.
then i thought it would be smart o delete everything on the device...(not my brightest moment)
used the tool to flash stock + unroot.
Worked fine but:
When finishing it couldn't connect to the network when it was setting up.
I resolved this by rebooting.
Then when i put my backup back from Google play the navigation bar was missing and the notification tray was missing too.
I resolved that by doing a factory reset.
tnx again.
Click to expand...
Click to collapse
Should never need to fix permissions. If needs permissions fixed it means have bad deved rom or dirty flashed over different rom base. This breaks the uids and is just a bad way to fix things. Will bite you again sooner or later.
prdog1 said:
Should never need to fix permissions. If needs permissions fixed it means have bad deved rom or dirty flashed over different rom base. This breaks the uids and is just a bad way to fix things. Will bite you again sooner or later.
Click to expand...
Click to collapse
jep i was being stupid...
I wanted to flash the new update LRX21R manually.
so i got a zip file from the ota thread.
tried to flash it in twrp
but it failed.
so i tried fixing permissions.
why i chose that option i dont know.
i should have read up on that function before using it.
Tested the tool today to Flash 5.0 (LRX21R).
The flash stock(with option not to wipe enabled) command failed to update my Nexus 9! Problem more likely with the factory image.
Had to manually flash each image and there was no option for vendor image in the advance tools.
Successfully Flashed TWRP, but root didn't work as this method doesn't install SU binaries.
Had to use chainfire's root method instead.
The toolkit hadn't been updated to Include LRX21R when I was using it.
berendspruijt said:
jep i was being stupid...
I wanted to flash the new update LRX21R manually.
so i got a zip file from the ota thread.
tried to flash it in twrp
but it failed.
so i tried fixing permissions.
why i chose that option i dont know.
i should have read up on that function before using it.
Click to expand...
Click to collapse
It's a fix for a bad rom flash with apps that FC. It just a work around, flash is still bad. I used it in testing years ago just to see what broke. Should never be used. I have flashed tens of thousands of times and have never needed. Update won't flash if you are rooted or have anymodded files. It is only for pure stock. Have to flash back to stock unrooted to flash it. Might as well just flash the new full image.
corkiejp said:
Tested the tool today to Flash 5.0 (LRX21R).
The flash stock(with option not to wipe enabled) command failed to update my Nexus 9! Problem more likely with the factory image.
Had to manually flash each image and there was no option for vendor image in the advance tools.
Successfully Flashed TWRP, but root didn't work as this method doesn't install SU binaries.
Had to use chainfire's root method instead.
The toolkit hadn't been updated to Include LRX21R when I was using it.
Click to expand...
Click to collapse
Just an FYI for future use, the option "Force Flash Mode" does just that. It extracts the package further and flashes the images individually.
And yes, google seemed to mess these packs up a bit where that is necessary.
Root will work now on that build now that its listed. And when Chainfire releases the kernel autopatcher zip, Any Build mode will work on Lollipop, so you won't have to wait on me adding builds - although I am pretty quick!
{{ WugFresh }}
Sent from my Nexus 5 using Tapatalk
WugFresh said:
Just an FYI for future use, the option "Force Flash Mode" does just that. It extracts the package further and flashes the images individually.
{{ WugFresh }}
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the Tip on using "Force Flash Mode" from the settings.
What about vendor.img, still not available in the advance mode.
corkiejp said:
Thanks for the Tip on using "Force Flash Mode" from the settings.
What about vendor.img, still not available in the advance mode.
Click to expand...
Click to collapse
oh snap. I forgot to add that. It takes care of it in the flashstock.bat and force flash, but it deff needs a button in adv utils. Will add in v1.9.9 which may be ready later tonight, or tmrw the latest.
sad face for having to rearrange buttons now! Lol.
{{ WugFresh }}
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!
You are the MAN! I was having a helluva time rooting my N9 until this beauty came along. Even an idiot like me can root with this great tool. Thanks again!
With that in mind, I have a couple of questions...
1. I did not flash a custom recovery when I rooted. Can I still get OTA updates?
2. Can I flash TWRP at a later date using the tool?
Once again, mucho thanks.
Related
I have created this thread for all you SG-NOTEII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-NOTEII device?
Don't panic just ask here and I or WE THE SG-NOTEII COMMUNITY will gladly help!
In case of Emergency!
Hey, I just installed the T889UVALL4 update, which fixes the Exynos exploit. I had my phone rooted before the update but then I had to UNroot it to even install or to see the update. So I wanted to know if I can still root with the same method as I did before using Odin and install CWM recovery with out bricking my device.
Unless there's a new root.
Sent from my SGH-T889 using xda app-developers app
No your safe to re-root. Same method.
Sent from my HTC One S using Tapatalk 2
Thanks. Came from iOS. Still new to the Android Eco System as far as Rooting/ Roms/Hacks/ etc. Didn't have to waste a thread :thumbup:
Sent from my SGH-T889 using xda app-developers app
this thread is................... awesome?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was notified there was an update available. I was rooted using CF auto root and after unrooting Super SU, I cannot get the update. It just says checking for updates... I try connecting to Kies but that wont connect. I am a noob in need of an expert. Right when I was starting to think I had a grasp of Android, I'm stuck. I'm on stock everything 4.1.1 and T889UVALK8
HELP!!
MarDog said:
I was notified there was an update available. I was rooted using CF auto root and after unrooting Super SU, I cannot get the update. It just says checking for updates... I try connecting to Kies but that wont connect. I am a noob in need of an expert. Right when I was starting to think I had a grasp of Android, I'm stuck. I'm on stock everything 4.1.1 and T889UVALK8
HELP!!
Click to expand...
Click to collapse
You Should Download and Flash A Custom Recovery For Your Note 2, Like CWM Or TWRP Through Odin. Then You Should Be Able To Flash A Newer Radio Or ROM.
Are You Looking For An OTA Update From Tmo?
MarDog said:
I was notified there was an update available. I was rooted using CF auto root and after unrooting Super SU, I cannot get the update. It just says checking for updates... I try connecting to Kies but that wont connect. I am a noob in need of an expert. Right when I was starting to think I had a grasp of Android, I'm stuck. I'm on stock everything 4.1.1 and T889UVALK8
HELP!!
Click to expand...
Click to collapse
update : Kies worked finally somehow. Not sure why it wasn't working the 10 other times I tried. Problem solved!
MarDog said:
update : Kies worked finally somehow. Not sure why it wasn't working the 10 other times I tried. Problem solved!
Click to expand...
Click to collapse
Probably Wasn't Properly Connecting To Kies. Glad It's Ok Now.
I'm sure this is a stupid question, but why can't I roam over to ATT? I have a Tmo value plan (post-paid unlimited) and when I'm in my companies datacenter, my Tmo connection is very poor- to the point where I miss calls and texts sometimes don't come through. I try manually choosing ATT from the provider list but it reports "not registered".
Am I doing something wrong? I should be able to roam over to ATT, right??
phdeez said:
I'm sure this is a stupid question, but why can't I roam over to ATT? I have a Tmo value plan (post-paid unlimited) and when I'm in my companies datacenter, my Tmo connection is very poor- to the point where I miss calls and texts sometimes don't come through. I try manually choosing ATT from the provider list but it reports "not registered".
Am I doing something wrong? I should be able to roam over to ATT, right??
Click to expand...
Click to collapse
Settings-More Settings-Mobile Settings-Data Roaming (check).
Sent from my SGH-T889 using xda premium
This is weird... i flashed CWM using ODIN and everything was fine... flashed a few roms and made backups just fine! This morning i went to flash the new MYROM- revolution and i boot in to CWM and press the "wipe data/factory reset" option and it would RESTART the recovery! i went to restore my current settings and it fell in to a boot loop. i flashed the CWM again via TOOLBOX/ODIN and still the same!!! i restored my original rom ( factory with root) and it booted but now i'm nervous to try anything im using the 6.0.2.7 version (the one that comes with the ROM manager app ). has anyone run into this kind of trouble??? any help would be appreciated!!!
jeibosquez said:
This is weird... i flashed CWM using ODIN and everything was fine... flashed a few roms and made backups just fine! This morning i went to flash the new MYROM- revolution and i boot in to CWM and press the "wipe data/factory reset" option and it would RESTART the recovery! i went to restore my current settings and it fell in to a boot loop. i flashed the CWM again via TOOLBOX/ODIN and still the same!!! i restored my original rom ( factory with root) and it booted but now i'm nervous to try anything im using the 6.0.2.7 version (the one that comes with the ROM manager app ). has anyone run into this kind of trouble??? any help would be appreciated!!!
Click to expand...
Click to collapse
Change your recovery to TWRP. Forget that "old" CWM....Too many problems with it.
premiatul said:
Change your recovery to TWRP. Forget that "old" CWM....Too many problems with it.
Click to expand...
Click to collapse
+1000000
Sent from my HTC One S using Tapatalk 2
premiatul said:
Change your recovery to TWRP. Forget that "old" CWM....Too many problems with it.
Click to expand...
Click to collapse
Belive me I tried to install TWRP and it wont get pass the team win "splash screen"... I've tried it more than once to no avail....
jeibosquez said:
Belive me I tried to install TWRP and it wont get pass the team win "splash screen"... I've tried it more than once to no avail....
Click to expand...
Click to collapse
Did you try to install it with GALAXY NOTE2 TOOLKIT?
http://forum.xda-developers.com/showthread.php?t=1957720
Never had any problems with that, so give it a go....
Quasi-bricked GN2 ... help please.
Hello -
I'm rooted and I was trying to install a different system font using Font Installer * Root * .
I followed the apps instructions and wound up with a bunch of Korean instead of where I thought the new font should be.
I then tried to re-boot and got stuck at the Samsung screen.
I have since tried to wipe / factory reset and flash the stock rom to no avail.
I have a Nandroid backup I created with Galaxy Note 2 Tool Kit but I don't know hot to re-install it.
Everything stops at the Samsung screen.
Help!
Thanks.
UPDATE: It's official -- I'm bricked. After hours of searching these fora it appears I need a Samsung signed stock 4.1.2 rom as I'm getting the "E:Signature verification failed" error and teshxx's ROM doesn't appear to be signed (is that correct?)
I'm stuck with the stock recovery and I really can't see any way out.
HELP please!
whatllitbenext said:
Hello -
I'm rooted and I was trying to install a different system font using Font Installer * Root * .
I followed the apps instructions and wound up with a bunch of Korean instead of where I thought the new font should be.
I then tried to re-boot and got stuck at the Samsung screen.
I have since tried to wipe / factory reset and flash the stock rom to no avail.
I have a Nandroid backup I created with Galaxy Note 2 Tool Kit but I don't know hot to re-install it.
Everything stops at the Samsung screen.
Help!
Thanks.
UPDATE: It's official -- I'm bricked. After hours of searching these fora it appears I need a Samsung signed stock 4.1.2 rom as I'm getting the "E:Signature verification failed" error and teshxx's ROM doesn't appear to be signed (is that correct?)
I'm stuck with the stock recovery and I really can't see any way out.
HELP please!
Click to expand...
Click to collapse
You are correct I hope you have insurance on your phone.
Sent from my HTC One S using Tapatalk 2
Question
If I have a tmobile note2 unlocked to use on AT&T and want to root and install Roms will it break the unlock? Where I have to have it unlocked again? I have searched everywhere and can't seem to find an answer except on really old phones.
Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.
BraveRobot said:
Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.
Click to expand...
Click to collapse
Be Brave, little Robot.
From what you've described, you're not out of luck here. I seriously doubt you've hard-bricked your phone. In order for me to help you, I need you to verify the following:
You can get into your Recovery (either CWM or TWRP).
You can get into download mode.
If these two are true, you're in luck. Below, I've copied a post I made yesterday helping someone else through a similar situation. Some things may be a bit different, but for the most part, it'll help you through you stuff.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Ok, now that we've identified what's wrong with your phone, we can now help solve it!
Solution/Fixes
Are you able to get into a custom Recovery? If not, you need to use Odin and follow The Rooting Guide to get back to a custom recovery (I recommend TWRP, but CWM is just as good).
Next, you want to download a Rom and put it on your device. I'd recommend (just for now), to get Freeza's stock TW Rom.
Now, before you try to flash this Rom, you'll have to wipe. In order to get rid of the FCs, you'll have to at least wipe System. I'd recommend a full wipe of your Internal SD Card (after backing up anything you want to save), but it's not technically necessary. Afterwards, you can wipe data and cache/dalvik cache.
Then you can flash your Rom. It seems like you know how to do this, but in case you don't, I have previously posted directions over here.
Hope this helps!
Click to expand...
Click to collapse
Be Brave, little Robot.
Click to expand...
Click to collapse
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
I've always given my instructions in TWRP, but the options/settings should be very similar in CWM. In the quoted post below, there are instructions on how to flash a new Rom.
For your situation, I'd recommend wiping system in step 4 below:
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
I'm going home from work for the night. I'll try to keep up with the thread, but if you have any questions, look over at this thread, I think Miguelcoo1 asked just about every question that can be asked, haha (he's a good guy, I'm just giving him a hard time).
In CWM recovery it says wipe data/factory reset. Is that what I want?
BraveRobot said:
In CWM recovery it says wipe data/factory reset. Is that what I want?
Click to expand...
Click to collapse
Is there an advanced option? Factory rest only wipes Data and Cache, if I recall correctly.
Here are my options:
- reboot system now
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
In advanced, here are my options:
- reboot recovery
- wipe dalvik cache
- wipe battery stats
- report error
- key test
- show log
- fix permissions
- go back
By the way, I have to wait 5 minutes between posts because my account is new. (How do I get rid of that?)
BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
Here's the guide for CWM
Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app
topherk said:
Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Alright. I don't mean to sound ungrateful, but this is all very new to me. How do I flash the new CWM onto my phone?
g_money said:
Here's the guide for CWM
Click to expand...
Click to collapse
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).
topherk said:
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).
Click to expand...
Click to collapse
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?
BraveRobot said:
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?
Click to expand...
Click to collapse
If you go into recovery/backup and restore/restore, do you have any backups listed?
g_money said:
If you go into recovery/backup and restore/restore, do you have any backups listed?
Click to expand...
Click to collapse
It says "No files found."
So I guess I didn't back anything up?
Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.
BraveRobot said:
Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.
Click to expand...
Click to collapse
Yes the instructions topherk gave you where to wipe and flash freezas stock rom. He gave you the links. Make sure you have the rom on your sd card ready to flash.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Ok, that worked. Thanks guys! Everything seems to be back working again.
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.
No I think your ok. At some point you restored one bad data or something. The only thing you should ever restore are apps you downloaded from the play store. Never restore any system apps. And samsung apps (bloat) you don't want to delete you just want to freeze.
Transmitted with a portable device using Xparent Blue Tapatalk 2
BraveRobot said:
Ok, that worked. Thanks guys! Everything seems to be back working again.
Click to expand...
Click to collapse
Good to hear
BraveRobot said:
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Click to expand...
Click to collapse
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
BraveRobot said:
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.
Click to expand...
Click to collapse
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?
g_money said:
Good to hear
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?
Click to expand...
Click to collapse
Yeah, I guess I'll keep it rooted, but I'm going to give things a few days rest after that scare. I need my phone! Maybe I'll come back and mess with it more later.
[HOW-TO] How to flash a factory image
________________________________________
How to flash a stock ROM build available on Google's developer site.
Unlocked bootloader is needed. I am assuming you are unlocked, rooted, and probably running a custom rom.
A. Install the drivers
I am not installing or helping anyone install anything on their PCs.
You can find that all over XDA. Please search. (or just click here. Be sure to thank owenbeals for putting this stuff in one place)
B. Backup your data ***Warning***
1) Backup all your personal data (e.g., photos, music, etc.)
**This will delete all data on your device. So Heed this warning.
This will unroot you.
This will unroot you.
Hi, no root. Unrooted. You. Did I mention your data will be erased?
Download the Attached file (at the bottom)
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
I created a folder called Nexus on the root of my c Drive
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. *Note you will need 7zip, in order to open zipped files
**Thanks to Efrant for the attached file. I stole it from his Help thread for the nexus4.
3) Download the version of Android you want from here. Make sure you are using a Razor image which is for the Nexus 7.
Edit *Want to keep your Data Intact?
Proceed with this step if you want to keep your data intact. With your favorite text editor, right click the flash-all.bat file and select edit. Remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15j.zip, it should now read fastboot update image-razor-jss15j.zip.
The -w option instructs fastboot to wipe data. Once removed it will skip deleting your data.
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip. Do not use any other unzipping program
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file).
7) Reboot your device into bootloader mode (by turning it off. Once off, hold volume down, and press and hold power). Once On and in fastboot plug it into the PC.
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located (see step 1 for where your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and select Open Command Prompt.
Make sure your computer recognizes your device by typing:
Code:
fastboot devices
at the prompt.
If it doesn’t see any devices. Guess what, you need to go back to step A.
Else;
At the prompt type
Code:
flash-all.bat
and hit enter.
Once done welcome back to stock.
You are not rooted. But you are still unlocked. If you want it locked;
At a command prompt type
Code:
Fastboot oem lock
hit enter.
Done.
It works, but should it go to the General area?
Thanks for this!!! New to Droid in general, Nexus my 1st, so easy step by step flash back to stock, appreciate it!!!
opticaldh said:
It works, but should it go to the General area?
Click to expand...
Click to collapse
Maybe. I just figured its an answer to a question. Lol.
matafact said:
Thanks for this!!! New to Droid in general, Nexus my 1st, so easy step by step flash back to stock, appreciate it!!!
Click to expand...
Click to collapse
Check out Wugfresh's Nexus Root Tool.
It can do it all..... :thumbup:
danvee said:
Check out Wugfresh's Nexus Root Tool.
It can do it all..... :thumbup:
Click to expand...
Click to collapse
Tools are not for New users. Terrible thing to suggest.
If you just need to get a job done, not an education in how it gets done (or all of the behind the scenes processes involved), sometimes a single, simple tool is the answer. :thumbup:
It's an option that should not be ignored or disparaged just because 'you learn nothing by using it'.
danvee said:
Check out Wugfresh's Nexus Root Tool.
It can do it all..... :thumbup:
Click to expand...
Click to collapse
tweaked said:
Tools are not for New users. Terrible thing to suggest.
Click to expand...
Click to collapse
New to Droid, but long time BB user, tweaked and played with, helped Hybrid developers beat test etc, so not a complete 'noob".. Had already unlocked and rooted, saw Wug's tool, so d-loaded and tried it... Wug's Toolkit worked great, was fairly str8tfrward, except couldn't get the "Nandroid Backup" to work or backup anything... But long time geek, got my 1st computer in 1981 or so TRS80II, so do understand the concepts...
matafact said:
New to Droid, but long time BB user, tweaked and played with, helped Hybrid developers beat test etc, so not a complete 'noob".. Had already unlocked and rooted, saw Wug's tool, so d-loaded and tried it... Wug's Toolkit worked great, was fairly str8tfrward, except couldn't get the "Nandroid Backup" to work or backup anything... But long time geek, got my 1st computer in 1981 or so TRS80II, so do understand the concepts...
Click to expand...
Click to collapse
:good:
Question! I have TWRP installed, will this remove that and all my recovery images? Should I make my nandroid backups on my PC before doing this?
Thanks! :good:
TheAltruistic said:
Question! I have TWRP installed, will this remove that and all my recovery images? Should I make my nandroid backups on my PC before doing this?
Click to expand...
Click to collapse
You should make backups and move them to PC if you care about the data.
This will replace almost everything.
Bootloader is replaced
Then boot/kernel, recovery, system are replaced
Finally cache and userdata are erased and replaced.
Since /sdcard is now "virtual" and sits in userdata, it will get wiped out also.
sfhub said:
You should make backups and move them to PC if you care about the data.
This will replace almost everything.
Bootloader is replaced
Then boot/kernel, recovery, system are replaced
Finally cache and userdata are erased and replaced.
Since /sdcard is now "virtual" and sits in userdata, it will get wiped out also.
Click to expand...
Click to collapse
^What he said. It wipes everything. You will be stock out of the box with the exception of the unlocked bootloader.
When you flash the stock image, what build number do you get- JWR66N (only first OTA) or JSS15J (second OTA)? I'm one of those Best Buyers that can't get the second OTA to install.
xene97 said:
When you flash the stock image, what build number do you get- JWR66N (only first OTA) or JSS15J (second OTA)? I'm one of those Best Buyers that can't get the second OTA to install.
Click to expand...
Click to collapse
The stock image from Google is JSS15J
Its we are the only one with jss image on Google every other device has jwr
Sent 4rm my Paranoid Nexus 4.3 LTE...
chiikko561 said:
Its we are the only one with jss image on Google every other device has jwr
Click to expand...
Click to collapse
The tablet shipped with JWR66N and OTA updated to JSS15J
The factory restore for JWR66N hasn't been provided provided, only JSS15J.
sfhub said:
The tablet shipped with JWR66N and OTA updated to JSS15J
The factory restore for JWR66N hasn't been provided provided, only JSS15J.
Click to expand...
Click to collapse
I know thats why or device is having all the problems plus n4 owners who use custom Roms based off jss
Sent 4rm my Paranoid Nexus 4.3 LTE...
chiikko561 said:
I know thats why or device is having all the problems plus n4 owners who use custom Roms based off jss
Click to expand...
Click to collapse
Have the same random reboot and gps problems in JWR66N.
danvee said:
If you just need to get a job done, not an education in how it gets done (or all of the behind the scenes processes involved), sometimes a single, simple tool is the answer. :thumbup:
It's an option that should not be ignored or disparaged just because 'you learn nothing by using it'.
Click to expand...
Click to collapse
You are correct that the option should not be discarded, whereas to use a tool at the beginning I also see as dangerous as you should first know exactly what you are doing before rooting, flashing anything.
Thanks for this very informative how to! Maybe you can add the tool option and make it a one-stop thread .
Sent from my Nexus 7 (2013)
sfhub said:
Have the same random reboot and gps problems in JWR66N.
Click to expand...
Click to collapse
I would rather deal with that then deadlocks screen freezes and unusable
Sent 4rm my Paranoid Nexus 4.3 LTE...
I'm on a rooted Nexus 7 2013 wifi only with twrp recovery installed. I'm currently running stock android 4.3 and wish to update to 4.4.2. I had originally held off updating but now want to do so. Here's what happened.
1. I first went to Settings /about phone /System update and tried to update. That failed repeatedly even though I have unmodified stock rom. (now even download fails though earlier it has downloaded successfully and the file is somewhere on the tablet).
2. So I next went to
http://forum.xda-developers.com/showthread.php?t=2380113
And downloaded the ota update zip file (JSS15R to kot49h). Then went to my Twrp 2.6.3.0 recovery screen and tried flashing the zip file from there. It failed. I didn't wipe anything first because I didn't want to lose my data.
So I'm stuck. Can I update without losing my data?
Thanks
Jeff
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
and normaly you can ota update without wipe your data, but i dont want to assure that.
dusu84 said:
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
and normaly you can ota update without wipe your data, but i dont want to assure that.
Click to expand...
Click to collapse
Thanks for offering to help.
I'm running supersu 1.91. I went into its settings and found it had "survival mode" selected, so I unselected it. Then booted into twrp screen and tried to flash the downloaded ota zip file again. No luck. Here's the fail screen image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apparently some twrp versions have trouble flashing. I would like to update twrp but don't know how. No update button and can't find anything on the twrp website about updating.
because of the unexpected content in app_process... have you maybe running xposed framework?
then flash xposed_disabler zip first.
dusu84 said:
because of the unexpected content in app_process... have you maybe running xposed framework?
then flash xposed_disabler zip first.
Click to expand...
Click to collapse
Aha! You're a genius! I think we're getting somewhere now. Yes, I have Xposed, GravityBox, and XPrivacy installed and running.
Should I uninstall them?
Where do I find xposed_disabler zip?
I'll start searching for xposed_disabler but would appreciate any pointers.
Also, this may have nothing to do with this, but when I searched for key loggers I got this message (I ignored} :
you should see the xposed disabler recovery zip in your recovery on sdcard. this zip should be copied to your sd card when you install xposed framework. when the zip isnt there you can also download this in the original xposed thread. (im not allowed to share links because im new at xda).
because the message by search for key loggers... i dont know. sorry.
Anderson2 said:
And downloaded the ota update zip file (JSS15R to kot49h). Then went to my Twrp 2.6.3.0 recovery screen and tried flashing the zip file from there. It failed. I didn't wipe anything first because I didn't want to lose my data.
So I'm stuck. Can I update without losing my data?
Thanks
Jeff
Click to expand...
Click to collapse
Jeff, your best bet really is to just flash back to stock, then just flash recovery and root in one step using the Nexus 7 Toolbox. This whole process will take you about 15 minutes and you will have a solid foundation.
The first reaction of many people to a suggestion like that is "what about my data?" My answer is to think carefully about what data would actually be affected by wiping your device. If you have things set up normally on Android there is very little that won't be put back on your device after going through the initial setup again. All your apps will reinstall from Google Play, contacts and email will sync, settings will sync... Even your WiFi settings. Wallpapers will sync, and pictures and videos will sync if you have one or more of the various accounts set up that do that. The only things missing will be things that you downloaded from the web and any sideloaded apps. That probably isn't more than a handful of apps and/or PDF documents... And only if they are stored on internal memory vs. Virtual SD card. If you have any stragglers, you can use Titanium Backup for ROOT, but I don't even find that necessary.
Just make sure you have your Google account sync set to on, and whatever other apps you use sync for like SkyDrive, DropBox, and any other things that get their names from two capitalized words mashed together.
Mike
Sent from my Nexus 7 using Tapatalk
Ah, but I am one of those who avoid syncing and trusting Google with my data.
Anderson2 said:
Where do I find xposed_disabler zip?
Click to expand...
Click to collapse
hey, have you find the xposed disabler recovery zip and whether have you flashed it?
is the ota update now working?
greets
EDIT: the xposed disabler recovery zip must be directly on your sd card... not in a specifically folder.
dusu84 said:
hey, have you find the xposed disabler recovery zip and whether have you flashed it?
is the ota update now working?
greets
EDIT: the xposed disabler recovery zip must be directly on your sd card... not in a specifically folder.
Click to expand...
Click to collapse
Not, I didn't find the xposed disabler recovery zip. At least not from a site I can trust. I searched my Nexus 7 contents and didn't find a xposed disabler recovery zip.
What I did do was uninstall Xposed, rebooted, and now Settings /about phone /system update did download the 4.4.2 system update - but didn't keep the file (at least not in the cache folder) because "verification failed". So I'm back where I was.
I also have Avast Mobile Security installed and it has a stealth anti-theft component that protects itself from tampering. I wonder if it might be blocking things. I might temporarily uninstall Avast to see.
One more thought: the Nexus 7 apparently has a way of booting into "safe mode". I don't know how to get into it, but perhaps the Android update might succeed when in safe mode.
This is really a pain! I can't believe I'm the only one facing this problem.
Anderson2 said:
Not, I didn't find the xposed disabler recovery zip. At least not from a site I can trust. I searched my Nexus 7 contents and didn't find a xposed disabler recovery zip.
What I did do was uninstall Xposed, rebooted, and now Settings /about phone /system update did download the 4.4.2 system update - but didn't keep the file (at least not in the cache folder) because "verification failed". So I'm back where I was.
I also have Avast Mobile Security installed and it has a stealth anti-theft component that protects itself from tampering. I wonder if it might be blocking things. I might temporarily uninstall Avast to see.
One more thought: the Nexus 7 apparently has a way of booting into "safe mode". I don't know how to get into it, but perhaps the Android update might succeed when in safe mode.
This is really a pain! I can't believe I'm the only one facing this problem.
Click to expand...
Click to collapse
ok strange...
btw. what the xposed disabler recovery zip does is copying /system/bin/app_process.orig back to /system/bin/app_process ... and in system/bin/app_process you have the unexpected contents according to your image what you have posted.
the xposed disabler recovery zip can you download from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314045&d=1381353218
but the problem with the app_process should done with uninstall xposed i think. after you uninstalled xposed, have you try to flash the ota zip again?
you come into safe mode by holding "shut down" after you press on/off button.
dusu84 said:
ok strange...
btw. what the xposed disabler recovery zip does is copying /system/bin/app_process.orig back to /system/bin/app_process ... and in system/bin/app_process you have the unexpected contents according to your image what you have posted.
the xposed disabler recovery zip can you download from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314045&d=1381353218
but the problem with the app_process should done with uninstall xposed i think. after you uninstalled xposed, have you try to flash the ota zip again?
you come into safe mode by holding "shut down" after you press on/off button.
Click to expand...
Click to collapse
Thanks for hanging with me.
It gets stranger still. Safe mode method doesn't work for me. When the power off popup comes on, if I short press or long press, it doesn't bring up the safe mode option.
I uninstalled Xposed and rebooted. Then I went back to my Twrp recovery screen and tried to reflash the ota zip again. It failed again but with an interesting error message about debuggerd contents.
And in case I'm missing something here is my tablet information.
Anderson2 said:
Thanks for hanging with me.
It gets stranger still. Safe mode method doesn't work for me. When the power off popup comes on, if I short press or long press, it doesn't bring up the safe mode option.
I uninstalled Xposed and rebooted. Then I went back to my Twrp recovery screen and tried to reflash the ota zip again. It failed again but with an interesting error message about debuggerd contents.
Click to expand...
Click to collapse
im sure we will make it
i hope this can solved the debuggerd problem: http://forum.xda-developers.com/attachment.php?attachmentid=2307599&d=1381111112
download it and flash it with twrp. perhaps a reeboot into recovery. then try to flash the ota update zip again.
dusu84 said:
im sure we will make it
i hope this can solved the debuggerd problem: http://forum.xda-developers.com/attachment.php?attachmentid=2307599&d=1381111112
download it and flash it with twrp. perhaps a reeboot into recovery. then try to flash the ota update zip again.
Click to expand...
Click to collapse
Here's what I did that finally worked. (sort of cheated)
1. Made a nandroid backup of the current state.
2. I had previously restored to an earlier nandroid and then tried to update again various ways. No success.
3. Finally, I restored a nandroid I made when I first rooted right after I bought the tablet. From this state the tablet updated itself automatically to 4.4.2!
My next task is to check my data to see if it went back to that early days. If so, maybe I can restore just data from the recent nandroid. Otherwise, I'll just work around it.
So far data and apps appear OK. How lucky can I be? Shows the advantage of making an early nandroid when tablet is still new.
(big sigh of relief)
Anderson2 said:
Here's what I did that finally worked. (sort of cheated)
1. Made a nandroid backup of the current state.
2. I had previously restored to an earlier nandroid and then tried to update again various ways. No success.
3. Finally, I restored a nandroid I made when I first rooted right after I bought the tablet. From this state the tablet updated itself automatically to 4.4.2!
My next task is to check my data to see if it went back to that early days. If so, maybe I can restore just data from the recent nandroid. Otherwise, I'll just work around it.
Click to expand...
Click to collapse
Anderson2 said:
So far data and apps appear OK. How lucky can I be? Shows the advantage of making an early nandroid when tablet is still new.
(big sigh of relief)
Click to expand...
Click to collapse
perfect its solved :good:
still have a nice day with your kitkat nexus!
Thank you.
One problem remains. I tried to do a new nandroid and discovered that when I went to the recovery screen instead of twrp, all it showed was open Android with red exclamation and something about "no command".
I think it deleted my Twrp, (or my Twrp was not compatible with kitkat). I don't recall how to reinstate twrp. Will try to find out. Rom Toolbox tells me there is no available recovery for my device, which must be wrong.
EDIT reinstalled twrp using goo manager. So I'm good!
I didn't read through this whole thread so excuse my response if you already found your answer.. I think if you have twrp flashed then the ota is going to fail every time. Reflash the stock recovery and run the ota update.
Sent from my Nexus 7 using Tapatalk
If I were in your shoes, I would just flash the factory KitKat ROM. You can download it here: https://developers.google.com/android/nexus/images
If you edit flash-all.bat (windows) or flash-all.sh (Linux) you can flash it without wiping your data. I would not bother though, I would let it while my data and restore it through synching or through Titanium Backup
Sent from my Nexus 7 using XDA Premium HD app
I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya
Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.
Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.
absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!
absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)
Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app