Related
Last summer I rooted my color Nook using Auto Nooter 2.1. I plan to give this Nook to a family member and I am struggling to return this to it's factory settings. I have read and watch the instructions provided by The uNlockr-How to Restore the Nook to it's Factory settings. I get as far as flashing the SD card, however that's where things take a left turn. The file names on the downloads they describe are not in the current downloads I can find. I have downloaded and flashed the img file for 4gb_clockwork-0.7.tar.gz. When I look for the actual Nook restore files every discussion thread leads me to here: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148 I've downloaded the large 200+MB file, extracted it... however none of the file names match the instruction per unlockr or the video:
Where am I going wrong? I have spent nearly 4 hours trying to navigate this Chinese maze? I'm sure that I have overlooked something but at this point I can't see it.
Any help to get me to this final destination I would greatly appreciate. I have a deadline of Monday afternoon to get this root righted.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1461172
HB
wheresgrant said:
Last summer I rooted my color Nook using Auto Nooter 2.1. I plan to give this Nook to a family member and I am struggling to return this to it's factory settings. I have read and watch the instructions provided by The uNlockr-How to Restore the Nook to it's Factory settings. I get as far as flashing the SD card, however that's where things take a left turn. The file names on the downloads they describe are not in the current downloads I can find. I have downloaded and flashed the img file for 4gb_clockwork-0.7.tar.gz. When I look for the actual Nook restore files every discussion thread leads me to here: http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148 I've downloaded the large 200+MB file, extracted it... however none of the file names match the instruction per unlockr or the video:
Where am I going wrong? I have spent nearly 4 hours trying to navigate this Chinese maze? I'm sure that I have overlooked something but at this point I can't see it.
Any help to get me to this final destination I would greatly appreciate. I have a deadline of Monday afternoon to get this root righted.
Click to expand...
Click to collapse
First off... the files you download from the thread above are CWM installable.... don't extract them... place the one you want to use on uSD and flash it... After you flash it... the Power + n boot will return to factory with 1.4.1 update installed.
Dizzy... Sincere thanks. Am I to assume that I should select the file romrestore.zip ? again all of the directions I've followed none have mentioned the use of this particular file. To make matters worse I downloaded a zip of nook-complete-restore-1.0.1.zip and the file is completely corrupted. I can't find a 1.4.1 version of the complete restore on available servers.
OK... my guess is that it not the correct file. I move the romrestore.zip to the nook power+ Nboot. reformatted system & data... fine. Installed romrestore.zip. "assert failed E:Error in sdcard/romrestore.zip. Installation aborted. Can someone give guidance on the correct file to install and where to find it?
You do not need the romrestore.zip.... just flash the file you downloaded from post 148 in the other thread... then if you reboot into stock recovery with power + n it will do the reset factory data.
The romrestore.zip file you are referring to was written to replace cwm recovery files with 1.0 stock recovery files... this is done with the 1.4.1 files I put together with that versions files.
Dizzy,
I appreciate you being patient with me but something is getting lost in the translation. Is this used in conjunction with the 4gb_clockwork-0.7img? I've used that to flash the SD card first. Then I've moved the entire 202MB nookcolor_1_4_1.zip to the SD card. Upon Power +nboot I come back to the same menu of options asking me whether I want to apply sdcard/update.zip. Each time the installation fails.
I fear I am mixing processes and files that don't belong together. Can you please just give me the simple steps (or point to them... post 148 doesn't explain what to do with those files). I'm batting 0 for 12 right now.
You sure are making this hard. If you will read the thread I linked in post#2 you will see just how easy it is.
It will take you back to whatever that Nook shipped with. Mine goes back to v1.3, my BIL's goes back to 1.0.0. Upgrades from there should happen automagically.
Your right. I was making this harder than what it was. I did take your advice and I tried the 3-finger reboot method. Eventually I was able to boot to the factory rom... but here is the kicker... the nook must be plugged into it's power supply (not running on it's battery) to hard reboot. Again, Google is both thy enemy and thy friend. I understand hacking doesn't come with a manual and these forums exist for the benefit of the community, by the community, but I've found so many incomplete instructions, bad file links, corrupted files... well I'm not really sure anyone can say they have the firmest handle on this procedure.
It's done though... and for the advice given here I'm grateful.
wheresgrant said:
Your right. I was making this harder than what it was. I did take your advice and I tried the 3-finger reboot method. Eventually I was able to boot to the factory rom... but here is the kicker... the nook must be plugged into it's power supply (not running on it's battery) to hard reboot. Again, Google is both thy enemy and thy friend. I understand hacking doesn't come with a manual and these forums exist for the benefit of the community, by the community, but I've found so many incomplete instructions, bad file links, corrupted files... well I'm not really sure anyone can say they have the firmest handle on this procedure.
It's done though... and for the advice given here I'm grateful.
Click to expand...
Click to collapse
Glad it helped.
And for the record I have done this to 2 different Nooks more than one time and never had it plugged into the charger. It IS important to make sure you have a full battery before doing these things.
The good news is that it worked!
HB
Grant... to answer your question... yes the files to flash 1.4.1 from CWM would be flashed from CWM (your clockwork imaged uSD)... you would just put the file on the uSD and boot it in the nook... install zip from card... select the file and let it flash... when its done flashin... power on holding n... allow it to do its thing and you'd be at factory 1.4.1.
The benefit of this method was you didn't have to flash to original and update... but since 1.4.2 has come out it would have to update anyway.
Harrybub... when I do the three finger way, my nook brings up ClockworkMod Recovery v3.2.0.1
I need to reset factory settings, but this came up two times that I was successful with the 8 interrupted boot.
The third time, I just chose the (wipe data/factory reset) in Clockword Mod recovery. Now it just boots up into recovery
Help?
gryphon101 said:
Harrybub... when I do the three finger way, my nook brings up ClockworkMod Recovery v3.2.0.1
I need to reset factory settings, but this came up two times that I was successful with the 8 interrupted boot.
The third time, I just chose the (wipe data/factory reset) in Clockword Mod recovery. Now it just boots up into recovery
Help?
Click to expand...
Click to collapse
See the post right above your's.
I just started over, found I had a corrupted cwm, maybe... Also had Rom zip and GAPPs zip on the same card. Redid everything using cwm image on one card, then zips on a separate card. That did it!
gryphon101 said:
I just started over, found I had a corrupted cwm, maybe... Also had Rom zip and GAPPs zip on the same card. Redid everything using cwm image on one card, then zips on a separate card. That did it!
Click to expand...
Click to collapse
Just an FYI... having both zips on the card is not an issue... common practice is to have them both, along with other zips on the CWM bootable uSD... you just have to make sure of what zip you are installing from uSD.
Ok, please I hope you can help. New to rooting, I rooted my s5, and was working fine for days, then I got the error and yellow triangle "system software not authorized by Verizon" I downloaded one md5 firmware I found and flashed it using odin, after was done had the same error though. I was on version 4.4.2. (don't know if that matters) I cannot find any other "stock" firmware online to try that are md5 that I can use with odin. I can find all these custom roms in zip format but don't know how to flash to odin when they are in the zip format and not tar or md5. Right now im just bricked and cant do anything and trying to learn how to fix all this.
Links to all files you need to download and full instructions on how to Odin back to stock can be found here ==>
http://forum.xda-developers.com/showthread.php?t=2784880
To properly root your device follow these instructions here ==>
http://forum.xda-developers.com/showthread.php?t=2784860
You can not just flash a ROM to your phone like with older phones, due to the locked bootloader. You have to install Safestrap and install the ROM there. You will find all you need to do that along with a link to a Youtube video explaining it all here ==>
http://forum.xda-developers.com/showthread.php?t=2793891
ok, I did just like the guide says and applied the tar file. it goes through the whole process but when it reboots it still says "secure fail:modem" in the left hand corner and "system software not authorized by Verizon wireless has been found on your phone please turn off and got to nearest wireless store for help". Im lost....
do I have to download and flash all those files? the nk2,n12, ne9, ncg??? what is the difference? hope someone can help...been working on this for hours and there doesn't seem to be a lot of information on my issue
tr889 said:
do I have to download and flash all those files? the nk2,n12, ne9, ncg??? what is the difference? hope someone can help...been working on this for hours and there doesn't seem to be a lot of information on my issue
Click to expand...
Click to collapse
Stick with my instructions to reset and the instructions to root. I have all the files and instructions you need for root linked in the how to root section in the OP.
I did it word for word, and after boot it still comes up to the system software not authorized by Verizon screen. Don't know how to proceed?
any help would be greatly appreciated because at this point im out 450 dollars.
Took it too Verizon and they said there is nothing they can do but give 178 dollar gift card...anyone here have any other ideas? Followed the rooting guide here, updates were turned off, don't know what went wrong
tr889 said:
Took it too Verizon and they said there is nothing they can do but give 178 dollar gift card...anyone here have any other ideas? Followed the rooting guide here, updates were turned off, don't know what went wrong
Click to expand...
Click to collapse
Did you re-partition using the pit file when trying to go back to stock? This doesn't make any sense. To the best of my knowledge, even tripping knox won't result in this ...
Yeah I did. Don't know what to do...I seem to be the only one that has had this issue. My question is, what did I do to wrong to make this happen? How do I prevent it when I get a new phone? It seemed to happen after tethering using x tether on xposed? Is there an issue with xtether ?
No there's no issue there. I run it and have Odined back to stock a couple of times and re-installed it.
Work backwards. Un-install all xposed modules. Un-install SuperSU, towel root and everything else you have added. Do a factory data reset and then try to Odin back to stock maybe? Take it all the way back to NGC
You don't use any kernel tars, just the full factory image tar
First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie
Odin stock and start over.
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie
please delete, sorry
Charlie
You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.
not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie
I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?
doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie
With Barnes & Noble now selling the Galaxy Tab S2 710 (32gb) for $299 in the U.S. (and an extra 10% off if you're a B&N member), I picked one up yesterday and immediately came here to research rooting and set up. What I found were a lot of guides written a while ago, and a lot of confusing (at least to me) information. So I thought I would consolidate, in one place, in a new thread, what I eventually did, on the assumption that there might be a lot of new Tab S2 owners in the coming weeks. Obviously, you undertake these steps at your own risk, and YMMV. Also, hopefully equally obviously, none of the fantastic tools here are original with me -- credit goes to all those, like chainfire, ashyrx, wanam, engine95 and many more who have built and/or developed them.
1. If your Tab comes with anything but 5.1.1 XXU2BPB1, feel free to take the OTA update. In the US, it's the most current build as of 4.30.16 and you will still be able to root.
2. If you don't already have it, download Odin 3.10.7. You can find it here: http://forum.xda-developers.com/showthread.php?t=2711451
When you run Odin in Windows, probably better to run it in administrator mode (right click on the icon), although I haven't always found that to be necessary.
3. Flash a Custom Recovery using the PDA tab of Odin. Put your Tab into Download mode by turning it off, then pressing and holding the Home, Power and Volume Down buttons all at the same time. When the download screen comes up, press the Volume Up button to continue. Now you're ready to attach your Tab to your PC. Load TWRP 3.0.2-1 from Ashyx's thread here: http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686 into Odin. Follow his instructions carefully -- once the custom recovery flashes, you have to manually reboot into the new recovery (so untick the auto-reboot option in Odin) or else your new custom recovery gets overwritten and you go back to your stock recovery.
4. Backup your Stock Rom -- While you're still in TWRP (or if you've already rebooted, go back to it), it would make sense to do a full backup of your stock ROM. That way you can restore your Tab to its original state if you ever need or want to.
5. Root -- Here's where I found the most confusion on these forums. You can do a systemless root -- i.e., keeping a stock, SE Enforcing, kernel (as opposed to flashing a permissive kernel and always getting the red SE Noneforcing Kernel message on a reboot and/or needing to use CF-Auto-Root). All you need to do is install Super SU 2.71 (BETA). Get the zip from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and put it on your Tab. Then flash using the "Install" choice within your TWRP recovery. Reboot -- and when TWRP asks you whether you want to install SuperSU because you're not rooted -- you have to say "NO" (OK, that's counterintuitive, but chainfire's instructions are clear).
5. Debloat -- That's beyond this thread's scope, but I recommend Titanium Backup from the Play Store. If you want to get rid of the "Nook" logo on reboot, flash the zip file from post #2 of Engine95's thread (using TWRP) found here: http://forum.xda-developers.com/tab-s2/development/rom-neked-nook-oj1-5-1-1-710-t3317823
6. SD Card Fix -- if you find your third party apps can't write to your SD Card, the attachment below describes how to fix it. If this type of editing scares you (make a backup first!), the Play Store app SD Card Fix supposedly still works with Lollipop and you can try that.
7. Netflix Fix -- for some reason, Netflix doesn't like root on the Nook Tab. The fix for this is as simple as renaming the file "system/lib/liboemcrypto.so" (using a root explorer of your choice) as "system/lib/liboemcrypto.so.bak"
8. Xposed -- I happen to like Xposed and don't find it messes up anything, while giving you a ton of customization options. Installation is a two-step process. First, find the correct version of wanam's Xposed zip from here: http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960, and flash it using TWRP. For Lollipop on the S2, I used his SDK 22-arm version (SDK 23 is for Marshmallow). Don't worry if the reboot takes a long time -- that's normal. Then, once rebooted, simply install wanam's Xposed apk (XposedInstaller_3.0_Alpha4) that's available in the same thread.
That's it. I hope this saves some of you a lot of my trial and error, and, if it does, please press the "thanks" button.
EDIT -- Here's a #9 I just discovered --- Microsoft Office apps, although pre-installed on the device, will not open once you're rooted (or maybe it's just flashing TWRP that does it). Moreover, if you uninstall and try a re-install from the Play Store, if you're like me, you'll get a device not compatible message. My solution was to sideload the apks (e.g., Word, Excel and Powerpoint) from my Note 4, but I suspect you could also change your device ID within your build.prop file (backup first!) and get a similar result.
ANOTHER EDIT (5.2.16) -- #10 -- I can't get Google Play Movies to work at all on my T710 after rooting. Tried renaming libemcrypto.so without luck. Tried editing boot.prop to disguise myself as a Nexus 10. Tried the Xposed module Root Cloak. All no good. Any suggestions welcome!
Thanks! I just got a new nook and have started to come into these forums and also noticed the old and randomly updated threads. I appreciate the clear instructions. Are there any roms right now that you are recommending?
rawdikrik said:
Thanks! I just got a new nook and have started to come into these forums and also noticed the old and randomly updated threads. I appreciate the clear instructions. Are there any roms right now that you are recommending?
Click to expand...
Click to collapse
Sorry, I'm trying to stick with stock. Engine95's rom seems to have some happy users though....
how do you manual reboot to recovery mode after download mode? i have tried the (pwr+vol up+home) but it does not work at all.. once i reboot normally the TWRP which i flashed cannot get installed at all. I need HELP!
Okay, so I have a Samsung Galaxy S 5, specifically the SM-G900H.
I rooted it some months ago and yesterday wanted to use the Screen Mirroring, so I found that you could get that function back by adding a line to the build.prop file.
Did that using this build.prop editor in F-droid.
It worked, but it also gave me a 2048 resolution and tablet layout (odd, I just added the key "wlan.wfd.hdcp" with the value "disable"), since I saw it stated that it had made a backup I chose to use the "restore" option and then boot. I'm not sure if it restored the wrong file or what but now after the first splash screen I get a black screen.
I went into Recovery Mode (Home+Power+VolumeUp) and tried to do adb from there but I only see the phone as "Host" and adb gives me an "error: closed" message whenever I try to do anything else than adb devices. If I try this without going into recovery mode I see the device as "offline".
So giving up hope to do this smartly by fixing the build.prop I tried a data wipe from recovery mode, the error persists but now I get stuck hearing the second splash screen's sound over and over again.
If I start ODIN mode I can see the device and flash (?) the auto-root found here without problem.
So, what do you recommend I do at this point? is there any way to edit the build.prop file with either ODIN or recovery mode's adb sideload?.
Or should I just flash a new ROM? I downloaded Cyanogenmod but I'd rather keep using stock for now. Where can I find the latest stock rom?.
Sorry if this has been solved elsewhere, I've looked and tried a bunch of them... there's a lot of noise out there.
update (making progress)
In case anybody wants to chime in (or this helps anyone else in the future)
I think I made some progress but the phone is not functional yet.
I flashed the TWRP found here:
http://forum.xda-developers.com/galaxy-s5/development/rom-kian-rom-bog6-t3187812
and went into recovery mode with that.
I did a backup, although I'm not certain what it backed up and where because neither the free space it needed nor the used space I had match up very much with that... a bit worried.
Then I mounted the /system and saw that there was no build.prop but only the build.prop.bak so I renamed that to build.prop and now I can see the second splash screen and don't hear it (I think this is because I might have had the volume down before) and it gets stuck there.
But hey, now I can edit the build.prop and maybe backup my files (mostly the chat logs and pictures) into the SD card. Will see what happens... I'll try to remember to come back and update.
build.prop.bak is the original it backed up when you edited it, it saves a new copy
Just rename to build.prop and reboot
*Detection* said:
build.prop.bak is the original it backed up when you edited it, it saves a new copy
Just rename to build.prop and reboot
Click to expand...
Click to collapse
hmmm Detection I did that at some point and it didn't seem to work, but it could have been that I didn't wait long enough.
After several more changes it worked (although my phone is still in tablet mode and I lost all my personal data).