Develop Bugs

[Q] Who provides a professional service to upgrade my Kaiser

Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry

I don't think there is a company that provides such a service especially if we take in to account that kaiser/tilt is a 3 year old device and the android port is not official. There are plenty of topics in the forum describing how to replace winmo with Android. You don't have to be a hacker to run Android on your phone. Just read the stickies and you wil be able to flash ityourself in no time

There are phone dealers out there (in the USA anyway), that will do this for a fee on the Kaiser, but trust me, with what has gone into the development of this, almost anyone can do it. Save yourself the money and try it yourself. The worst I've heard about is a mis-flashed phone needing some master reset.

The question is who?
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.

Henrykjr said:
I live here in the Orlando area and have called a number of cel phone companies.
I was treated like King Gidorah Three Headed Space Monster. They didn't have a clue this could be done.
Click to expand...
Click to collapse
Listen HenrykJR there are about dozens of android builds on this forum + many different versions of two kernels, not all of those will work correctly for you. You might experience different issues with one setup but the other will work correctly for you. So even if there was a company that could flash it for you, you might end up with an unstable device. Also how could a company gain knowledge on flashing android builds to a phone that was originally shipped with windows mobile??? You seem to be looking for Nessy....in woods.
Your best bet now is to find someone in the forums to help you flash your device....maybe even use skype to show you how to do it. It really isn't that hard.

Hehe, i don´t think you´ll find a Company that will do it for you. Maybe you find some guys that do it for Money (me to ). But if you spend a little time with reading through this forum you could do it yourself and save the money.
Preparing:
1.) You need a SD card (mandatory for android on Kaiser). And you need a Google Mail Account for syncing your contacts etc. and access the android market.
2.) You have to "unlock" your Phone (with HSPL/HardSPL). Only after that you are able to flash things (Cusom WinMo ROMs, Radio, Android) to your Kaiser. So read through this guide and follow step 1-4.
3.) Now you have an unlocked phone an you should be able to flash everything. And the first thing you flash should be the latest "radio". The "radio" for Kaiser is similar to the BIOS for your PC. Like the subsystem and responsible for GSM chipset etc... So look & read in this Radio-Thread, download the latest Radio (it is 1.71.09.01) an follow the guide "Flashing Radio from microSD"
4.) Now your Phone is up-to-date and ready for flashing Android (or WinMo custom roms). YOU NEVER HAVE TO DO THE STEPS 1-3 AGAIN! Your Phone is now completely prepared!
Flashing Android:
For Android on Kaiser you always need 2 Parts. The Kernel (this part initialize the hardware so its similar to "driver" on PC) and the Built (the Android OS itself). But Both should work together so you´ll may find in some kernel suggestions in Built-threads because not ever kernel work with every built. For your beginning i whould suggest you some things:
First the kernel:
DZO is the most popular (the father of android on Kaiser) Kernel-Developer for Kaiser. So go to his repository and download "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh". Because Vouge and kaiser have almost the same hardware we all could use this kernel. But everyone have to modify this kernel to make phone related optimizations. You can do thy by hand (not recommended for you) or with a tool called "Atools". This tool is writthen in "Python" so mac and linux user could use it too. But you need to install Python. But that is all described in the Atools thread. Read through it and follow the guide.
Modifing Kernel:
We will only modify the madatory things. Not more at the moment...
So run Atools, klick on the "folder" Button and load the "voguimg-240x320-2.6.32-froyo-09-10-10_23.nbh".
Device: "Kaiser" should be checked
Resolution: 240x320 should be checked (native resolution of Kaiser display). Everything else will give blurry optic.
Version: "Froyo" should be checked, because we will flash a Froyo built (thats android 2.2). If you want to flash an older built like a Donut one (1.6) you have to modify & flash your kernel again.
Panel Type: Try "auto" or "1" first. But if you have a fuzzy screen or artifacts you have to try out which paneltype fits best for your device. HTC has built in 3 different displays in the Kaiser and the only way to find out which one is builtin is trial & error.
Keymap: Depends on which hardware keyboard layout you have. Here in Germeny i have to use "qwertz".
We leave the other options as they are an klick on the "Disk" button to save our modificated kernel now. it save it as "KAISIMG.nbh".
Now we need the Built:
I suggest "Fat Free Froyo" at the moment. Fast, stable, an looks good. So go to this thread and download "ODEX DOWNLOAD RLS5 ALL LANG-ODEX" on the bottom of the post.
then unzip/unrar this file...
Flashing your first Android:
1.) You should have a fat32 formatted SD card
2.) put the Kernel (the modified KAISIMG.nbh) to the root of SD card
3.) Create a folder named "andboot" on SD card
4.) Put the unzipped file (androidinstall.tar or .tgz) in the folder "andboot"
5.) Remove SIMcard and any cables from phone and put the SD card in your phone. Battery should be 50% carged or more...
6.) go to bootloader-mode (press and hold camera button and powerbutton). the KAISIMG should be loaded and it will show you "press powerbutton to update" or something similar. Do that... Now a progressbar will appear. When it is at 100% wait a few seconds an then pull the battery. Wait 10 seconds an insert it again. Voila! You flashed your first android kernel!
7.) Now we have to install android itself. So Power on the phone. In the moment when you see small white text on black background you have to press and hold the d-pad button. This one in the middle. Now you get in the install menu.
8.) Leave the options "System on nand" and "DATA on nand" as it is. Navigate to "install system" an press dpad. It ask "format system" and "format data". Both "YES". after this procedure you enter the menu again. navigate to "quit".
9.) Yeah! The first Bootup of Android! The first bootup takes longer as the following ones because now the system prepares for bootup and do a lot of optimisations. Even if you enter the lockscreen you should give it 10 minutes time to finish this optimization process in backround.
10.) Finish! You have flashed your first android completely! Now you can play around and make your settings. Remember: You have to sign in to your google account befor you can access the market or syncronize your contacts etc.!
Sounds more complicated as it is. Try it!
And if you´ll dig in deeper in this stuff you have to read here! Especially the Stickies/Refs/Tutorials! We´ve all done that!
have fun!

Henrykjr said:
Hey all,
I own an unlocked ATT Tilt 1 (Kaiser 8925). It is currently running windows mobile which is extremely slow. I have read all over the internet that you can put the Android 2.2 OS on this phone and have seen youtube videos on this topic also.
Ideally I need to be able to buy apps from the android marketplace.
Since I'm not a phone hacker I'd like to find a professional cel phone service company that can do this for me.
I searched extensively on Google and can't seem to find one. So who can do this and what is the normal charge for something like this.
Just trying make my old phone useful in wifi mode.
Any advice would be great.
Regards Henry
Click to expand...
Click to collapse
Brother, You can do it yourself, I can assure you. Regarding any ambiguity, you can contact me through PM. (I can guide you complete on voice over skype / msn). Its a TIDEOUS job but EASY to do since there is no MEANS OF BRICKING your kaiser (unless you flash something else than what u have do to install android).
I am here to help you in this community. And you can do this thing yourself.
Your device is At&t Tilt. The bad thing about installing android is getting a RIGHT kernel that suits your LCD type and enables wifi in the android build u install. (maybe in 1st try, maybe takes almost 10 tries like it happened for me)

UK 1.2.0 Glow ONLY TFU Software Upgrade

After much debate I have decided to make my work public as a lot of people seem to want these features!
THIS IS AN ALPHA SOFTWARE! EXPECT BUGS!
THEREFORE IF YOU INSTALL, ITS YOUR CHOICE. I TAKE NO RESPONSIBILITY IF THINGS GO DOWN THE PAN!
To get this working well, I need you guys! The testers - the community!
TFU ROM UPGRADE PACK ALPHA 3
What is it?
This software pack will supply your STOCK UK nook with software 1.2.0 with the following features:
ROOT
BUSYBOX
ADB
A clean nook friendly interface
A custom kernel (Thanks guevor http://forum.xda-developers.com/showthread.php?t=1906507)
Multitouch
Browser, Email, PDF, News Feed, Lots of tools
A custom built video mod to improve multitouch speed, refresh rates, delay and general display performance
MORE (but I cant remember)
Follow this guide to backup your nook and find out everything you need to know about the process. Please do this BEFORE any other tinkering! Make sure you know what you are doing!
http://forum.xda-developers.com/showthread.php?t=1961835
How to Install
Make a CWM SD card:
http://forum.xda-developers.com/showthread.php?t=1360994
Flash my zip:
http://dl.dropbox.com/u/13673492/TFU_ALPHA3.zip
Reboot:
You now have everything you need to get started!
BUGS:
Cant install apps unless you use ADB or drop them into /data/app and install.
If some of the preinstalled apps don't work follow this procedure:
-Open nook color tools and disable/enable allow non-market apps.
-Use file explorer to browse to /data/app and click on and install the broken app.
If you need help with ADB or want a different way to root check out my other post here!
http://forum.xda-developers.com/showthread.php?t=1961835
If you find a bug let me know please!

RESERVED

Hi Loney,
Installed just now and all seems well so far - well done!
John

I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.

Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks

stelph said:
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
Click to expand...
Click to collapse
You are spot on. I didn't want to cause problems for people. Is your firmware 1.2.0? its firmware differences which are most likely to cause a problem. If you have a good backup, give it a go. If it works great. If not, you could try sending me your framework.jar file and I can try and find out what the differences are. Good luck!

roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks for posting this. Very useful for people who aren't familiar with the nook. I will mention your name and this post when I update my guide with this information.

Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.

roustabout said:
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
Click to expand...
Click to collapse
This is great news. Everyone will benefit from some constancy across all devices.

Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!

stelph said:
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
Click to expand...
Click to collapse
In my next update you will be able to customise the launcher as you like. The fact that you cant is a bug that can be fixed by clearing the launcher data using the included titanium backup program.

Since i'm back from the hell of the "bricked nook", now i can come back to test your mod with more understanding.
It seems that if we change the language to all but english, the installation of the mod is doomed to a blank launcher. (that was the case for registering the nook i have to do it in english).
I reflash my nook after setting it in english and that correctly installs everything (not Opera but that's easy to recover it).
may be a note for foreigners who try to install this mod is to be aware of keeping the nook in shakespeare's mother tongue.
would you mind integrating in your future version the manga reader "perfect viewer"? fastmode.apk is also a request but now i understand that is not so easy.
thanks for your contribution. :highfive:

I'll report my experience using this technique. A few days ago, I purchased a US Nook Simple Touch (non-glow) which came with software v.1.0. I made a backup using the method referenced in the OP. I then upgraded to software v.1.2 via the manual (USB mode) method shown at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/ . I made another backup. I verified both backups using the SD card method as suggested by roustabout. Everything looked good.
I followed the OP instructions and was successful in installing TFU_ALPHA3.zip with CWM.
Upon reboot of the NST, I saw a dialog chooser asking me to select either the standard Nook software or Launcher7. I first tried Launcher7 and was greeted with a large gray "n" background. Nothing else. The only button that had functionality was the "n" button which brought up the "home" menu at the bottom of the screen. This got me back to the standard Nook software. So at least the reader still worked.
I rebooted and tried Launcher7 again, just to be sure. Still nothing but the large gray "n" background. No apps.
I restored my v.1.2 backup without any problems, and am now back to a "stock" NST. All good.
So while the TFU_ALPHA3.zip installation proceeded without incident, I didn't see any apps that I could run from Launcher7. I guess I'll have to try a different technique.

it seems like the same problem i said in my previous topic. did you set your language to anything but english?
i had the launcher7 without anything loaded. I had to set the language in english then reinstall the TFUAlpha3 to make it work correctly.
hope it helps.

jjinkou2 said:
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
Click to expand...
Click to collapse
I have the US version of the NST. I couldn't find any way to change the language in the settings.

fastmode is working but we have to set it manually. i read this here http://forum.xda-developers.com/showthread.php?t=1241419, and i tested it.
Code:
adb shell
# cd /sys/class/graphics/fb0/
# echo -n 1 > fmode
# echo -n 0 > pgflip_refresh
since no-refresh and fastmode are autoexclusive i set pgflip_refresh to 0.
values are lost when the nook reboots.

New version coming soon. Lets start a list of requests guys. And if anyone has tested custom graphics settings, what works for you?

Loney,
Things that aren't working for me:
* Launcher 7 settings can't be altered (changes don't "save")
* apk installs are hitty-missy. Sometimes moving an apk into /data/apps and rebooting will work, other times I need to install it again by clicking on it in a file explorer.
* Fast mode app does nothing (but we knew that...)
Other than that, all is cool. I have also installed the patched .jars from the "mod manager" thread and they work alongside your changes.
Well done for your efforts on our behalf. Shout if you want anything specific testing - I'm confident that I can recover from "bricking"!
John

loney01843 said:
New version coming soon. Lets start a list of requests guys.
Click to expand...
Click to collapse
I haven't tried this yet, but when I do I would imagine access to google markets would be needed.

A follow-up on my experience which may (or may not) help getting this to work with the US NST (non-glow). Yesterday, I decided to give GlowNooter (http://forum.xda-developers.com/showthread.php?t=1675706) a try. Suspecting that it wouldn't work out-of-the-box, I deleted /system/framework/framework.jar from the glownooter.zip file. Installation of the .zip succeeded, and I was able to run ADW Launcher. I added my account to YouTube, attempted to sync in GMail, rebooted, and installed the PART-2-END.zip. Then I tried to open up Market, but kept getting connection errors. I also tried the Browser app, but was unable to enter text into Google's search page. So I guess there is stuff in glownooter's framework.jar file that is needed for everything to work. I didn't try too much more.
Anyway, I reverted to the stock NST 1.2 software for now. But I am happy to help with testing new firmware since I'm pretty confident about restoring to stock software.

[REF} All in One guide for NOOBS with Videos! "WORK IN PROGRESS"

If you just switched from iPhone or BB or this is ur first android. Read this thoroughly and see ur questions get eliminated by this guide. if you find this helpful then show your appreciation and hit that thnx button.
As of now this thread is under construction, I have not seen any noob helper all in one thread & i have always had one for the phone I have. So here it goes for Note 2. Feel free to give me suggestion but keep in mind that I only do this on my free time so this might take while to finish.
I don't take any credit I Googled everything. I do take credit of modifying some stuff in word.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.

Credit for this Post goes to TRusselo!!!!
Here is how to do Advance research/help your self + Mods!​
{
"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"
}

Here is how to Root Your Note 2 Mac & Windows!​
Root Note 2 on Windows without Tripping Flash counter!!!
Step 1: Download the files Here and unzip them.
Step 2: Do this Only if you want CWM. Connect your phone to computer and copy over CWM recovery.img to your internal sd card. Make sure you do not put that in any folder.
Step 3: Put your phone into down load mod. First Turn off your phone. Then Press Volume down, Power and home button. You will see following screen.
Step 5: Then Press Volume Up and you will see following screen.
Step 3: Open up Odin folder and run Odin3 v1.85 and unselect F. Rest Time.
Step 6: Connect your Note 2 to computer. Once you connect your phone you will see yellow box on upper left corner on Odin.
Step 7: Now Press PDA and browse for the location of the downloaded files. And Select root files that you downloaded and open it.
Step 8: Press Start.
Step 9: Phone will reboot once its done flashing. And you will get Pass on upper left corner.
Step 10: Now download any of the app that requires root permission(titanium back up) and make sure you have root.
Option One: Install CWM Recovery Hard way!
Step 1: Go to your phone and enable usb debugging under setting>developer's option.
Step 2: Connect your phone to your windows computer and open up command prompt.
Step 3: Type adb on your command prompt then you will see all the commands that adb offers.
Step 4: Type adb shell then type su after that type dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Step 5: You will see following in your command prompt.
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
13992+0 records in
13992+0 records out
7163904 bytes transferred in 1.672 secs (4284631 bytes/sec)
Step 6: Now Just type " reboot recovery " in command prompt.
Step 7: You now have rooted At&t Note 2 with CWM installed.
Option 2: Flash TWRP Easy Way!
1) Download Goo Manager from Play Store.
2) Open the app & press Menu button. (Make sure to give superuser permission)
3) Press "Install OpenRecoveryScript"
4) Recovery will be downloaded & installed.
5) Once You see message saying Recovery Installed, press boot into recovery.
6) Done you have custom Recovery.

Here is How to Unroot Your Note 2.

fourth for all in one links.

fifth for video reviews.

sixth for themes.

seventh for how to use xda
This order may get changed.

eight for how to flash themes.

Last one

appdroid said:
Last one make sure to hit thnx guys.
Click to expand...
Click to collapse
Getting my Note 2 in a week and I'm new to Android.
If you root can you delete the At&t bloat apps? Or do you have to do something else to get that?
Also is there some option to disable 4G and just go on 3G?
Thanks

used all my thanks!! great write up!!! you always provide us with great information!!!

fxbreaker said:
Getting my Note 2 in a week and I'm new to Android.
If you root can you delete the At&t bloat apps? Or do you have to do something else to get that?
Also is there some option to disable 4G and just go on 3G?
Thanks
Click to expand...
Click to collapse
Rooting will allow you to completely remove an app. You can disable(removes from app drawer and totally deactivates the app) without rooting by doing the following:
Go to setting/applications manager
Select desired app
Will give option to 'disable'
Select disable and the app will no longer run or be visible.
If the option shows 'disable updates' select that then go back and select the app again and it will then let you disable the app.
This method leaves the file on your phone so it doesn't free up any space but it will free up some memory as you will no longer have this 'bloat' running.
Sent from the Millennium Falcon

I Don't know why someone would rate this thread down???

appdroid said:
I Don't know why someone would rate this thread down???
Click to expand...
Click to collapse
Maybe cause every other word you type is "hit my thnx button", "dont forget to hit my thnx button", "I love getting my thnx meter up!"........just a thought.
Maybe folks are confused. Are you trying to ramp up your thanks numbers? Or are you truly trying to help the community. If its the latter you wouldnt or shouldn't care what your thanks meter says.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

For me the best way to get pumped up to do this kind of work is getting thnx. Just little reward that i look forward to when i am done writing all this. It keeps me going. & Its not like I am asking for $$ u know its shows appreciation. May be ppl are getting me wrong, but i love getting thnx specially after long nite of writing.
& question about helping out community? Well in my mind there is no doubt. But i can't speck for others as everyone has there opinion. I been quite for long time on xda, just got note and thought i would do something again that would help my fellow members but i don't think its working out.
cdshepherd said:
Maybe cause every other word you type is "hit my thnx button", "dont forget to hit my thnx button", "I love getting my thnx meter up!"........just a thought.
Maybe folks are confused. Are you trying to ramp up your thanks numbers? Or are you truly trying to help the community. If its the latter you wouldnt or shouldn't care what your thanks meter says.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse

appdroid said:
For me the best way to get pumped up to do this kind of work is getting thnx. Just little reward that i look forward to when i am done writing all this. It keeps me going. & Its not like I am asking for $$ u know its shows appreciation. May be ppl are getting me wrong, but i love getting thnx specially after long nite of writing.
& question about helping out community? Well in my mind there is no doubt. But i can't speck for others as everyone has there opinion. I been quite for long time on xda, just got note and thought i would do something again that would help my fellow members but i don't think its working out.
Click to expand...
Click to collapse
To be honest I dont see a problem with your noob guide. Dont misinterpret my reply:thumbup:. If people find your post helpful they will thank you. Regardless if you ask for it not. :beer:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

I appreciate the work done in this thread. and all he is asking for is a thanks in exchange for hours and days of research sounds good to me .goodjob op keep it up
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Gonna take ur words for it cd since i have known u from skyrocket days lol. Ya will stop asking. & do what i do best finish this guide.:silly:
cdshepherd said:
To be honest I dont see a problem with your noob guide. Dont misinterpret my reply:thumbup:. If people find your post helpful they will thank you. Regardless if you ask for it not. :beer:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse

appdroid said:
Gonna take ur words for it cd since i have known u from skyrocket days lol. Ya will stop asking. & do what i do best finish this guide.:silly:
Click to expand...
Click to collapse
Ahhhh the skyrocket days. Life was soo simple
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Samsung Galaxy S7 Active Root! (SUCCESS)

I have an AT&T Galaxy S7 Active - US Model - SM-G891A
I haven't seen any credible sources with a root for this device. From what I can tell, it is identical to the Qualcomm version of the Galaxy S7(non-edge) with one exception; The S7 Active has the "Active button".
Since almost every Qualcomm variant of the Galaxy S7 has been rooted, is there a chance that the S7 active is rootable? or is there already a root?
Let me know if you need any other information or if you would like a test dummy.
UPDATE: Successful Root Of the Galaxy S7 Active (Qualcomm)
PLEASE USE THE POLL TO LET US KNOW WHAT VERSION OF FIRMWARE YOU END UP ROOTING. IF YOU FAIL, PLEASE PROVIDE US WITH AS MUCH INFORMATION, ABOUT YOUR EXPERIENCE, THAT YOU CAN. THIS WAY WE CAN DO OUR BEST TO HELP YOU AND CONTINUE IMPROVING THIS ROOT.
ROOT - CLICK BELOW
Original Tutorial Credit(HERE)
Updated for Galaxy S7 Active (by NotSoMiniGun)
Make sure you have downloaded these files:
• SuperSU v2.74 (updated) SuperSU v2.76
• Modified ODIN
• Unlock boot.tar
• Fastboot
• Samsung Official USB Drivers v1.5.40
Make sure you meet these requirements:
• Firmware PG7, PH2, PI2, PK2, PL1(6.x.x only)
• NO NOUGAT SUPPORT YET (1/30/2017)
• >60% Battery charge
Additional suggestions and warnings:
• Make sure you know both your Samsung account info and your Google account info. You will need these, for Factory Reset Protection, if something goes wrong and you need to wipe your phone.
• I, also, recommend rooting a clean/wiped/reset phone. This rules out quite a few things that could cause failures or strange behavior during or after the rooting process.
• You WILL lose some speed and battery life. This is not an optimized root. If you are comfortable with that fact, then go ahead. You’ve been warned. Do not complain about it on this thread.
• Install the Samsung drivers even if your computer already seems to have them. Right click and run the .exe as administrator. REBOOT after install. This rules out another potential point of failure.
• MAKE SURE YOU ONLY HAVE YOUR PHONE PLUGGED IN. Make sure there are as few USB devices, as possible, plugged into your computer during the rooting process.
• DISABLE YOUR ANTI-VIRUS
Step 1:
Read EVERYTHING above. Twice.
Step 2:
Open Settings->About Device and scroll down to “Build Number”. Tap it repeatedly until it says you have activated “Developer Mode”.
Step 3:
Open Settings->Developer Options and turn ON both “USB Debugging” and “OEM Unlock”.
Step 4:
Turn phone OFF. Once off, hold (Volume Down, Center Home, and Power) until you see a blue warning screen.
Step 5:
Press Volume Up and plug your phone into your computer. You should have blue screen that says “Downloading”.
Step 6:
All of the files should be downloaded to your computer and be sitting in your “Downloads” folder. Un-zip the ODIN-modified.zip, right click the ODIN .exe, and run as administrator.
IF YOU DON’T SEE A BLUE BOX AT THE TOP LEFT OF ODIN THEN DO THESE STEPS AGAIN:
1. Run the Samsung USB Drivers .exe again.
2. Reboot your computer.
3. Make sure your data cable isn’t damaged and is plugged in all the way.
Step 7.
Select AP and choose the ENG Boot file ending in .tar. Then click “Start”. The blue box should eventually turn green and say “PASS”.
IF YOU GET STUCK IN A BOOT LOOP:
“If your phone ends up in a bootloop (which most likely will), you will need to do a factory reset. To do this, hold down Volume Down, Center Home, and Power buttons together until your phone resets then quickly switch the Volume Down to Up key while holding the rest of the buttons down until you see “Recovery booting” at the top-left of the screen. If you mess up, don’t worry you can keep trying until you get it right. Once in stock recovery, choose “Wipe data/factory reset” then “yes” to do a factory reset. THIS WILL ERASE EVERYTHING ON YOUR PHONE! Reboot and after 5-10 minutes, you should be welcomed by a welcome screen, go ahead and login.”
Step 8:
Go through the set-up screens until you can repeat Steps 2 & 3.
Step 9:
Unzip fastboot.zip to its own directory. Unzip the contents of SuperSU and copy them to the fastboot folder.
Step 10:
Shift-RightClick in the white space below the files in the fastboot folder. Click “Open Command Window Here”.
Step 11:
Type the following in the Command Prompt:
Code:
adb devices
Code:
root.bat
Watch your phone for any messages and make sure to tap OK. If it freezes, unplug your phone, plug it back in, and restart from Step 10.
Step 12:
Install BusyBox from the app store. Open the app and make sure it installs to “/system/xbin”. DO NOT INSTALL IT ANYWHERE ELSE. THIS WILL CAUSE PROBLEMS AND REQUIRE A FLASH AND RE-ROOT.
Step 13:
You are now successfully rooted. Read the rest of this post carefully to fix the following items:
WiFi password reset
SecurityLogAgent
General Lag and other issues.
TO UNROOT - CLICK BELOW
Link to Instructions Provided By (jembot)
WARNING:
DO NOT uninstall "SecurityLogAgent", DO freeze it using Titanium Backup. Uninstalling it seems to cause instability and random system crashes.
DO NOT attempt to update SuperSU BINARY UPDATE:You can update to v2.76 from v2.74 with the provided file (updating the app is also ok) after root. Other attempts to update will break WiFi, Cellular Data, Access to the Play Store, and will require a reflash in ODIN to regain functionality.
If you do accidentally do this, just reflash to PI2 firmware and check for OTA updates, or use the update packages, to bring your device back to PL1 Firmware. It will lag a lot, so be patient.
FIRMARE AND PACKAGE DOWNLOAD LINKS
PI2 Firmware Download Password: G891AUCS2API2_FULL_FSFD (Cost me $10 lol)
PG7 Firmware Download
PG7 to PH1 Update
PH1 to PI2 Update
PI2 to PK2 Update
PK2 to PL1 Update
PI2 to PL4 Update
PK2 to PL4 Update
PL1 to PL4 Update
SuperSU v2.74
SuperSU v2.76
Modified ODIN
Unlock boot.tar for PL1 or earlier (credit activefan01)
Original boot.tar for PL4 (use if updating to nougat)
imsservice.apk (use to remove VoLTE and RCS icons)
Fastboot (bundle used in the rooting tutorial)
Samsung Official USB Drivers v1.5.40
Other Issues and Solutions:
If you get and MD5 error:
Your download for the tar file was probably incomplete or corrupt. To fix, re-download and make sure it downloads completely before trying again.
If ODIN does not recognize the file or doesn't display it in the browser:
The file should end in a .tar extension, not a .MD5 extension. Use THIS tutorial to show file extensions in windows(if you can't see them), and make sure the file ends in .tar
If you still experience significant lag or battery usage:
1. Try any of the suggested CPU governor apps on this thread.
2. I, personally, noticed the biggest improvement with Device Control [root] from the play store
3. Enable - Power Efficient Workqueue
Enable - LCD power reduce
Core Limits - 1593 MAX - 307 MIN and Lock Frequencies
Governor - Interactive and Lock Governor UPDATE: "PERFORMANCE" seems to work significantly better at removing lag and, surprisingly, saving battery
Enable - Automatic FStrimming
Enable - Core Control and MSM-Thermal
Enable - Reapply on boot with a 15 second delay
4. Under developer options, consider setting all of the animation speeds to 0
5. As always, you are responsible for any damage to your device or data
For those of you who want Xposed:
1. Install Flashfire from the Play Store
2. Put these 2 files on your phone FRAMEWORK and APK
3. Use Flashfire to flash the zip to your phone.
4. Install the APK and Reboot.
5. Enjoy
6. Avoid these modules or risk bricking your phone:
- Gravitybox - Confirmed
- Xblasttools - Confirmed
For those of you who want to Tether/Hotspot:
1. Install XTether in Xposed
2. Activate and Reboot
3. The native hotspot/tether options will now work in settings
4. Enjoy more.
If you have issues with AT&T keeping you from setting up your phone:
1. Make sure you connect to WiFi on first step of the Samsung setup
2. Do the normal setup until you get to the AT&T Setup portion
3. Let the setup "scan" for connections on WiFi
4. Dismiss the warning about limited WiFi and turn the WiFi OFF
5. Proceed with the rest of the setup by hitting NEXT or SKIP when available
6. You should now be able to use your phone and should be able to setup all AT&T related software separately.
To fix WiFi password reset issue:
1. Install BuildProp from the Play Store
2. Change the value of ro.securestorage.support=false
3. Save, reboot, enter WIFI password for the last time!
How to remove the VoLTE and RCS(hurricane looking thing) icons: (tested by FtaWolf)
1. Install a file explorer like FX
2. Set Read/Write access to System Partition, use the 3 dot menu in the top right
3. (be careful not to touch anything else, I soft-bricked my phone twice on accident)
3. Navigate to /system/priv-app/imsservice
4. Rename file imsservice.apk to imsservice.apk.bak, tap and hold to rename
5. Copy THIS file into the same folder
6. Then set permission to 644, again, tap and hold to change permissions
7. Reboot and you should be good to go.
How to add HotSpot and MobileData toggles or remove unwanted toggles (credit slimshouki)
1. Install CSC Feature Expert from the PlayStore
2. Scroll down until you find "Config Def Quick Setting Item" (Do not search for it, you wont find it)
3. Add " ,WiFiHotspot,MobileData"
4. (OPTIONAL) Delete any toggles you don't want. Make you there is a single comma between all values
5. Open Settings->Personal->Backup and Reset->Reset Settings
6. After it reboots you should see the toggles.
COMPATIBILITY STATUS:
Galaxy S7 & S7 Edge Qualcomm Variant Root: Confirmed Successful On: PG7, PH2, PI2, PK2, PL1 || Fails On: PL4, Android 7.0 Update
Poot Debug APK Qualcomm Root: Incompatible
Dirty Cow Exploit: Temp/Partial Root
TO DO:
Determine Root Method/Source (activefan01, perhaps you can weigh in)
Custom Recovery (if possible)
Optimize Current Root Method (currently takes a decent toll on battery life)
7.0.0+ Root (currenty only works on pre-nougat systems)

If no one has any answers on the availability of a functioning root for the Samsung Galaxy S7 Active, can some one tell me why the Active series of phones seem to be actively ignored? Is there an extreme difference in hardware? Is it difficult for devs to get their hands on the device? Is there not enough interest?

The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.

br0adband said:
The basic gist with the Active line is: nobody really cares in terms of development because they're just not popular devices in terms of sales. They're better devices, in my opinion, but that doesn't mean much to anyone else obviously.
Root would be nice to muck around with I suppose, be able to do some more things, run some root-required apps and so on but, I can live without it so far.
The fact that there is no working firmware available from AT&T or Samsung anywhere could have something to do with it as well perhaps. I've been looking for a pure stock image just in case I have issues but so far it's just non-existent and probably always will be unavailable.
The Active models are great devices, just not popular to the majority of buyers unfortunately and that immediately translates into not being popular with developers or the community in general. I'm getting 2.5 days of battery life per charge with at least 7 hours of SOT with this one I have now so I'm a happy camper without any complaints.
Click to expand...
Click to collapse
I'm only getting 4hrs of sot..... Hmm

I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.

I am also searching for root. I got some link in google search, but they are not working. I bought this unlocked device in India. While it works fine with old network, but it does not work with new network which are purely 4g and use voice over LTE for calls.
Sent from my SAMSUNG-SM-G891A using Tapatalk
---------- Post added at 02:13 PM ---------- Previous post was at 02:12 PM ----------
I need to put Indian CSC on this phone.
Sent from my SAMSUNG-SM-G891A using Tapatalk

br0adband said:
I don't use cellular except when I'm out and about, I use about 40-45% brightness or less (auto brightness when out and about), I have roughly 155 packages disabled with Package Disabler Pro, that's about it.
With a 4000 mAh battery, the GS7A better last as long as mine is lasting or something is absolutely wrong I'd say - it's not that hard to get this kind of battery life and usage but as always YMMV.
Click to expand...
Click to collapse
Would you be willing to compile a list of all the packages you disabled? Maybe then I can get better battery life.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Here's the list as XML and it's attached as well for import to Package Disabler Pro:
Code:
<importExportSetting>
<disabledPackages class="java.util.ArrayList">
<string>com.mobeam.barcodeService</string>
<string>com.monotype.android.font.rosemary</string>
<string>com.matchboxmobile.wisp</string>
<string>com.sec.android.widgetapp.samsungapps</string>
<string>com.samsung.android.app.galaxyfinder</string>
<string>com.sec.android.app.chromecustomizations</string>
<string>com.samsung.android.app.aodservice</string>
<string>com.samsung.svoice.sync</string>
<string>com.drivemode</string>
<string>com.sec.android.app.clipvideo</string>
<string>com.sec.android.devicehelp</string>
<string>com.android.wallpapercropper</string>
<string>com.sec.android.app.wfdbroker</string>
<string>com.att.android.digitallocker</string>
<string>com.samsung.android.app.withtv</string>
<string>com.sec.android.app.safetyassurance</string>
<string>org.simalliance.openmobileapi.service</string>
<string>com.samsung.android.easysetup</string>
<string>com.android.externalstorage</string>
<string>com.sec.android.easyonehand</string>
<string>com.sec.factory</string>
<string>com.cequint.ecid</string>
<string>com.directv.dvrscheduler</string>
<string>com.samsung.android.qconnect</string>
<string>com.amazon.mShop.android.install</string>
<string>com.sec.android.app.tourviewer</string>
<string>com.sec.android.Kies</string>
<string>com.samsung.faceservice</string>
<string>com.monotype.android.font.foundation</string>
<string>com.sec.android.widgetapp.easymodecontactswidget</string>
<string>com.samsung.android.email.provider</string>
<string>com.samsung.android.firmware.tsp</string>
<string>com.google.android.configupdater</string>
<string>com.sec.android.app.billing</string>
<string>com.sec.android.app.minimode.res</string>
<string>com.samsung.android.game.gamehome</string>
<string>com.samsung.android.slinkcloud</string>
<string>com.dti.att</string>
<string>com.dsi.ant.service.socket</string>
<string>com.sec.android.AutoPreconfig</string>
<string>com.sec.android.app.soundalive</string>
<string>com.samsung.android.securitylogagent</string>
<string>com.android.carrierconfig</string>
<string>com.samsung.android.app.watchmanager</string>
<string>com.samsung.android.app.assistantmenu</string>
<string>com.locationlabs.cni.att</string>
<string>com.samsung.SMT</string>
<string>com.samsung.aab</string>
<string>com.samsung.vvm</string>
<string>com.sec.android.ofviewer</string>
<string>com.samsung.hs20provider</string>
<string>net.aetherpal.device</string>
<string>com.sec.att.usagemanager3</string>
<string>com.dsi.ant.sample.acquirechannels</string>
<string>com.samsung.android.smartface</string>
<string>com.android.mms</string>
<string>com.android.backupconfirm</string>
<string>com.sec.android.app.SecSetupWizard</string>
<string>com.hancom.office.editor.hidden</string>
<string>com.sec.bcservice</string>
<string>com.android.calendar</string>
<string>com.samsung.android.providers.context</string>
<string>com.sec.android.preloadinstaller</string>
<string>com.sec.android.uibcvirtualsoftkey</string>
<string>com.samsung.android.sdk.professionalaudio.utility.jammonitor</string>
<string>com.android.sharedstoragebackup</string>
<string>com.yellowpages.android.ypmobile</string>
<string>com.samsung.android.app.colorblind</string>
<string>com.android.printspooler</string>
<string>com.android.dreams.basic</string>
<string>com.att.myWireless</string>
<string>com.sec.android.app.dictionary</string>
<string>com.samsung.android.app.talkback</string>
<string>com.samsung.android.game.gametools</string>
<string>com.asurion.android.mobilerecovery.att</string>
<string>com.sec.smartcard.manager</string>
<string>com.sec.allsharecastplayer</string>
<string>com.samsung.app.slowmotion</string>
<string>com.samsung.android.smartcallprovider</string>
<string>com.directv.promo.shade</string>
<string>com.dsi.ant.plugins.antplus</string>
<string>com.samsung.android.personalpage.service</string>
<string>com.samsung.advp.imssettings</string>
<string>com.samsung.android.app.advsounddetector</string>
<string>com.sec.android.app.clockpackage</string>
<string>com.samsung.android.app.mirrorlink</string>
<string>com.samsung.android.sm</string>
<string>com.sec.android.widgetapp.locationwidget</string>
<string>com.google.android.apps.walletnfcrel</string>
<string>com.samsung.android.controltv</string>
<string>com.samsung.mdl.radio</string>
<string>com.sec.spp.push</string>
<string>com.dsi.ant.server</string>
<string>com.samsung.android.gamepad.service</string>
<string>com.samsung.android.allshare.service.fileshare</string>
<string>com.synchronoss.dcs.att.r2g</string>
<string>com.sec.android.mimage.photoretouching</string>
<string>com.samsung.android.universalswitch</string>
<string>com.samsung.helphub</string>
<string>com.sec.android.app.sns3</string>
<string>flipboard.boxer.app</string>
<string>com.google.android.feedback</string>
<string>com.google.android.apps.photos</string>
<string>com.android.managedprovisioning</string>
<string>com.sec.android.providers.tasks</string>
<string>com.ubercab</string>
<string>com.monotype.android.font.chococooky</string>
<string>com.android.dreams.phototable</string>
<string>com.samsung.safetyinformation</string>
<string>com.facebook.katana</string>
<string>com.samsung.app.highlightplayer</string>
<string>com.sec.android.app.vepreload</string>
<string>com.android.providers.partnerbookmarks</string>
<string>com.cleanmaster.sdk</string>
<string>com.samsung.android.keyguardwallpaperupdator</string>
<string>com.android.wallpaper.livepicker</string>
<string>com.samsung.android.beaconmanager</string>
<string>com.amazon.mShop.android</string>
<string>com.samsung.android.app.FileShareClient</string>
<string>com.facebook.system</string>
<string>com.sec.android.soagent</string>
<string>com.samsung.android.fmm</string>
<string>com.samsung.android.mdm</string>
<string>com.smlds</string>
<string>com.ws.dm</string>
<string>com.samsung.knox.appsupdateagent</string>
<string>com.samsung.android.spayfw</string>
<string>com.samsung.app.newtrim</string>
<string>com.samsung.android.spay</string>
<string>com.sec.hearingadjust</string>
<string>com.samsung.android.dlp.service</string>
<string>com.samsung.android.bbc.bbcagent</string>
<string>com.samsung.android.voicewakeup</string>
<string>com.sec.android.splitsound</string>
<string>com.wssnps</string>
<string>com.samsung.android.app.watchmanagerstub</string>
<string>com.policydm</string>
<string>com.samsung.android.app.FileShareServer</string>
<string>com.enhance.gameservice</string>
<string>com.americanexpress.plenti</string>
<string>com.sec.svoice.lang.es_US</string>
<string>com.lookout</string>
<string>com.samsung.android.sm.provider</string>
<string>com.monotype.android.font.cooljazz</string>
<string>com.android.bluetoothmidiservice</string>
<string>com.facebook.appmanager</string>
<string>com.samsung.voiceserviceplatform</string>
<string>com.samsung.aasaservice</string>
<string>com.samsung.android.allshare.service.mediashare</string>
<string>com.sec.android.app.mt</string>
<string>com.sec.knox.switcher</string>
<string>com.qualcomm.atfwd</string>
<string>com.sec.android.app.magnifier</string>
<string>com.samsung.android.video</string>
<string>com.amazon.kindle</string>
</disabledPackages>
</importExportSetting>

Thank you. I'm going to mess around with it later.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Here first run with sot with S7 Active.
{
"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"
}
Sent from my SAMSUNG-SM-G891A using Tapatalk

FtaWolf said:
Here first run with sot with S7 Active.
Click to expand...
Click to collapse
That's awesome, really it is, but what does that have to do with this thread and rooting it?

br0adband said:
That's awesome, really it is, but what does that have to do with this thread and rooting it?
Click to expand...
Click to collapse
Not thing. What did disabled package pro have do with thread. You didn't ? It.
Sent from my SAMSUNG-SM-G891A using Tapatalk

Back On Track
While I agree the S7 Active is a fantastic phone with fairly substantial battery life, those merits should be discussed in another thread such as HERE. The main goals of this thread are:
1. Determine if there is an available Root for the Samsung Galaxy S7 Active
2. Determine if any current exploits, for other models, could be modified to Root the S7 Active
- The Galaxy S7 (snapdragon model) Root
- Dirty Cow
- etc.
3. To offer help or a reward to anyone willing to make progress on this topic.
I personally am wiling to donate $50+ to anyone able to provide a legitimate root (or to a charity of their choice).
Please let me know if there is an official way of presenting a bounty or if there is any other way I can help progress this project.

I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system

-snip-

Poot
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?

NotSoMiniGun said:
Is there any evidence that the POOT generic Qualcomm root would work on the Galaxy S7 active?
Click to expand...
Click to collapse
Most likely not as that is an old method. You could try the method mentioned a few posts up.
Sent from my SAMSUNG-SM-G891A using Tapatalk

first of all, I apologize for my "English", I had to use google translator.
I am edu present, I'm from Argentina, and was looking for information on how to root the s7 active, no luck, but I found information that perhaps more experienced people can help them find a solution ....
Qualcomm Quadrooter Exploit
QuadRooter Android sounds like another serious security exploit. Which one can allow a malicious app Apparently to gain root access based on Qualcomm Android phones and tablets, enabling the app to do pretty much what Then it pleases. , According to Check Point, the research group discovered That QuadRooter, up to 900 million Android devices Qualcomm Could be AFFECTED. This exploit targets the drivers Qualcomm Which is why it is specific to this hardware. As of the 1st Augusts security update Google has patched 3 of the 4 will patch vulnerabilities and the last one in the September 1st update. To keep your device safe from bugs it is always in Original bests to stay on top of your security updates. One of the best ways to protect your phone from malicious software is to download apps only from trusted sources or google play.
If you want to check and see if your device can possible be vulnerable to this threat Then you can download and run QuadRooter Scanner by check point. Personally I am hoping That a developer can figure out this exploit and use it to get many android users root access. I am sure someone can create a app gets root then a INJECTS That SuperSU and their binary into the device. If you are hoping for the same I recommend not updating to new security patches and give the developers some time to get root access devices.
I would not be surprise to see this QuadRooter vulnerability Implemented into Kingroot app some time soon, as it would make there app on Android devices unstoppable. What do you think about this bug please comment below and let me know.
This information I found in rootjunky.
I hope you can serve something
---------- Post added at 01:58 AM ---------- Previous post was at 01:45 AM ----------
rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
how did it go?

I tried it but not got success.

rahuldixit2010 said:
I fully agree with "Notsominigun". This phone is fantastic in all aspects, but root is very essential in some scenario to utilize its potential, especially those who are using unlocked phone in other network and country. Some features are not working which can be enabled easily by rooting and taking full control of the phone.
I have searched for "Dirty Cow" and found it can be used to root any android device with following steps:
http://androiding.how/dirty-cow-root-android/ ; I will try it once get a Linux system
Click to expand...
Click to collapse
That's awesome! Now, who is familiar with Linux... can dump boot.img and kernel.img from the phone...
I found that it's here:
cd dev/block/platform/soc/624000.usfshc/by-name/
dd if=/dev/block/sda6 of=/sdcard/efs.img
dd if=/dev/block/sdd10 of=/sdcard/aboot.img
dd if=/dev/block/sda13 of=/sdcard/fota.img
dd if=/dev/block/sda16 of=/sdcard/modem.img
dd if=/dev/block/sda17 of=/sdcard/boot.img
dd if=/dev/block/sda18 of=/sdcard/recovery.img
I don't know, will these comands work in linux?

[NST/G] Update FW 1.2.2 UK (unofficial)

If anyone has an old UK device at the bottom of a drawer somewhere which they recollect has a non-English language dictionary from B&N on it, please contact me before trying this.
Spoiler: How I did it
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
The most important discovery was that the "UK ROM" was still there in the US FW 1.2.2 update. That is to say, if you copied over the splash screens from the UK 1.2.1 update and the Oxford dictionary, you had nearly everything that was different between the two. Except it didn't work. It looked different on boot, but was still the US version (you can tell by looking at Settings which are different in the two versions).
Eventually I took at look at the update script in the B&N zip and saw that it was checking build.prop before doing anything else. I compared that file on the UK 1.2.1 and US 1.2.2 zips and found the major difference was in localization. In two entries "GB" was used instead of "US". Was it that simple?
Yes!
Ah...but it refused to register. In fact, it refused to authenticate, so it never got to asking about your account. The final discovery was the result of a completely idle-brained attempt (because I was out of ideas). I had rooted an instance after skipping OOBE. In the launcher app drawer I saw the familiar junk, including DeviceRegistrator (anyone who has rooted an NST knows this app with the smiley-face icon). I've always thought it was just cyber-detritus, an early version or mock-up left by B&N developers. They were not very tidy, after all. But maybe intents of the app are used in the current registration process. Who knows? Anyway, I tapped on the icon and proceeded to successfully authenticate the device. That got my attention! Then I tried to register with my existing B&N account and password. BINGO! I could see my device on the B&N website under my account and I was able to "buy" a free book using the Shop app (you need a credit card on file with B&N to get even a free book).
So it works for me, in the US.
Because of the changes I made to the original US 1.2.2 update zip, the internal signature is broken, so it cannot be used as an auto-update zip. Hence the need for CWM.
To avoid the necessity to root (for those who would rather not), I removed the broken Lancher.apk in /system/app and replaced it with a simple launcher in the Gingerbread style that is able to run as a system app. So when the device gets to displaying "home", it asks how you want to do that. Initially, the Launcher app is selected so that you have access to an app drawer and the DeviceRegistrator app. After registration, a reboot will present the "home" option choice again. This time the "always" box can be ticked and the B&N "Home" app selected. The Launcher.apk will never be heard from again. Those who go on to root can remove it from /system/app if they wish.
Outstanding issue to be explored: dictionaries. There seems to be a capability for adding different language dictionaries. The User Guide refers to this also. I have not been successful in doing this and don't know whether there ever were any other dictionaries. Since this was not a US option, I'm guessing that the only hard-coded URLs for the dictionary downloads are to non-existent UK servers. I still haven't tracked down where those URLs are. The Nook app for Android is reputed to have the same capability, but when I installed it on one of my rooted tablets, it only had an English dictionary. The format of this db file seemed to be exactly the same as the Oxford dictionary on the UK ROM. I got a Spanish book from B&N and tried to look up a word from there. This gives an option to download a dictionary (as the user guide says) but the result just sends you to the Settings where the only dictionary visible is the default English. So maybe you have to be in another country? Anyway, I could not get the NST to recognize the English dictionary offloaded from the Nook app, despite the apparent structure similarity with the Oxford already onboard. Perhaps there is a database somewhere that would keep track of the dictionaries on the device if the download function were still working. I have not found it. Or, perhaps additional "downloaded" dictionaries have a special place to be (Edit: YES! They go into /data/media/B&N Downloads/Dictionary). Someone with a long memory who has experience with the UK ROM but is not primarily an English speaker might hold the key.
Spoiler: Q&A
--Is this the same thing as the Region Changer?
No. The region changer procedure gives you a device running US firmware (although it looks like B&N still knows it's a UK device based on the serial number and their own records--or they might be identifying its point of origin by the internet connection). This update zip will give you a true UK ROM: the different splash screens, the different settings options (including language) and the ability to enter letters with diacritical marks from the keyboard. It also features the Oxford dictionary. However, it will contact US B&N servers, not the non-existent UK ones.
--Do I need to have an existing B&N account?
I think so. The back door we are using to authenticate and register the device does not have an option for creating a new account.
--Should I deregister my device before doing this?
If you did a region change and are currently running registered US FW 1.2.2, I would recommend deregistering the device before converting to the UK ROM, just to avoid potential conflicts. You can use the same account to register the new ROM. If you have B&N content, it might even show up since it's the same account (mine did).
--Can I purchase books from B&N using the Shop app?
Maybe. I was able to "buy" a free book from B&N and have it appear on my device (note: to purchase even a free book you need to have a credit card on file for your B&N account). But, I am in the US. The B&N Terms of Service says that you have to use (or have on file) a credit card with a US address. There appear to be workarounds like purchasing a US-based cash card, etc. Seems like a lot of extra effort, but apparently some people have done it.
--I live in the US but this sounds interesting. Can I try it too?
Well, I did! The ROM is interesting in a number of ways. It really is a Western European variant, not just UK. German, English, French, Italian and Spanish are the available languages. If your primary language is not English but instead one of these, this might be an attraction. However, there is at least one unexpected consequence. Some external servers will be absolutely convinced you are outside the US. I found this out by trial-and-error when I could not get my Today's Comics app to work. When I changed the region to English (US), it began to work, so I guess the content was region-blocked. I jiggered the Settings app of the UK ROM slightly so it would display the English(US) option.
--I see "Chinese" among the languages! Can my NST display Chinese?
Well, no. Unfortunately the only way to get English(US) to display is to display all of the "development" languages. I tried to suppress "Chinese" but had no luck. There are Chinese characters in DroidSansFallback but the strings for the B&N system were never fully translated (maybe not at all). There is a lot that is translated (appears to be Taiwanese Chinese), probably left from the original phone ROM they used to make the NST OS. However, if you select Chinese any apps you may have installed that are correctly localized for Chinese will display appropriately.
How to do it
Note: I did this on a deregistered device. It does not matter whether your device is currently US FW 1.2.2 or a UK FW 1.2.1.
1. Prepare a CWM card (if you don't already have one, use one of the two sdcard versions). If you've never done this sort of thing before it's probably easiest to download the zip for the Nook Region Changer and follow the instructions there for making the sdcard (steps 1-3). You don't need the two update zips that are on the card, but it's still CWM. If you already have a Region Changer card, you can use it as-is.
2. Download a copy of my 1.2.2 UK update zip. Copy the update zip to the CWM card (the card should be in the card-reader slot of your PC, not in the Nook)
3. Power down your Nook.
4. Insert the CWM card into your Nook and power up. You'll see the logo and maybe the opening menu.
CWM is a little wobbly on the NST. Sometimes it seems to get stuck on a white screen after the logo. If that happens to you, press the lower right hardware button. That generally wakes it up.
Navigating in CWM involves using the upper left hardware button (go back to the previous menu), the two right hardware buttons (go up and down a menu) and the "n" button (do what is highlighted).
5. Move down to "backup and restore". Press "n".
{
"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"
}
6. The menu should show "backup" at the top. Press "n". This will backup your current configuration onto the sdcard.
7. At the conclusion of the backup you should be returned to the top of the menu.
8. Move down (or one step "up") to "advanced". Press "n".
9. Move down one step to "wipe dalvik cache". Press "n".
Then move way down (or a little up) to "yes". Press "n".
Here you may run into another CWM issue. At least for me, CWM has a tendency to freeze after any kind of wipe. If that happens to you, don't panic. If the buttons don't seem to be responsive, press and hold the power button. If the device does not reboot back into CWM, release the power button and press and hold again. Eventually the device will reboot, taking you to the top of the menu again.
10. From the top of the menu move down to "wipe data/factory reset". This option is just like the previous one, including the potential freeze. Do it.
11. From the top of the menu, move down to "install zip from sdcard". Press "n".
12. The top of the next menu says "choose zip from sdcard". Press "n".
13. Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
14. After the update is complete you need to return to the top of the menu where it says "reboot now" (if you are not already there). At that point, remove the CWM card from the device and press "n" to reboot.
15. Your Nook will boot into the UK ROM setup. You'll see the familiar multi-lingual splash screen, the marching dots, and finally come to a Language choice screen.
Select whichever language you prefer. You can change this later from Settings.
16. The next screen is the "Welcome" screen.
You are now going to execute a "skip OOBE". Since registration fails in the usual setup wizard, we will have to go in the back door, so to speak. At the "Welcome" screen, press and hold the upper right hardware button and swipe your finger across the top of the screen from left to right. You should see a "Factory" button appear in the upper left corner of the screen. Tap it.
17. Now you are on the Factory screen.
Again, press and hold the upper right hardware button and tap the screen in the lower right corner. You should see a "Skip OOBE" button appear on the screen. Tap it.
18. OK, so now you are faced with a choice which I have added to the ROM in order to finesse the registration issue without needing to root the device. There should be two options listed on the screen: Home (the B&N home screen) and Launcher (I added this). For now tap on "Home". The B&N home screen loads up with the infinite spinner in the lower half (no registration, no wi-fi, no data).
19. Press the "n" button and select "Settings". Set up a wi-fi connection and set the time zone and time display format. Leave wi-fi on. Use the power button to shut the device off.
20. Power up your Nook. When it has passed the marching dots it will ask you again whether you want "Home" or "Launcher". This time, choose "Launcher".
A simple Android launcher screen is displayed. All you care about is the app drawer, that little square of tiny squares in the center of the bottom of the screen. Tap it.
21. There is a bunch of stuff (mostly junk) in the app drawer. Resist the impulse to fool around there. Keep your eyes on the prize! Locate the DeviceRegistrator app (stupid smiley-face icon). Tap it. Check to be sure your wi-fi is on.
22. You need to do two things here.
First, register (authenticate) the device itself. That's the first button on the left in the first row. Tap that. If all is going well (and your wi-fi is on) you should get a confirmation alert. After that, type in your username (email) and password for your B&N account. There is no option here to create an account, so you need to have one already established for this to work. After you've typed in the information, tap on "Register User". You should get a confirmation alert. You can now turn off wi-fi. Press the "n" button and select "Settings". Check Device Info>About your NOOK. If everything went according to plan you should see that it is registered.
23. Shut down the Nook. Power up one more time. After the marching dots you are again faced with the choice of "Home" or "Launcher". Before you make your selection, tap on the little (empty) checkbox. This will make your next move permanent. Now tap on "Home".
You'll never hear from "Launcher" again. It will just languish in /system/app with all the other unused apps and your Nook is now registered and good to go!
If you want to root and further customize your Nook, select one of the updated NookManager packages. I strongly recommend using NookManager to make a backup of your device before rooting. The CWM backup you made at the beginning of this process is not a complete nandroid backup and you'd be better off with one before you make any more changes. If you are not interested in rooting, you may want to make another backup with the CWM card at this point and then put it away somewhere safe. Just in case.

I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!

ashh87 said:
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
Click to expand...
Click to collapse
Thanks a lot for the feedback. Now we know it was not just a one-time fluke for me. I'm glad it worked for you as well.

Also worked for me. After registering I used NookManager to root it, then installed the latuk kernel from this post with CWM and it's now UK 1.2.2 and external keyboard supporting. That's all I was looking for. Another thumbs up for the repeatability of your method. Thanks for the detailed instructions.
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?

markeq said:
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
Click to expand...
Click to collapse
Let's say--hypothetically, of course--that you did that. There are two ways around it.
1. If you rooted with the "traditional" or "stealth" versions of NookManager, you have ES File Explorer. You can use it to access the App Manager and remove the defaults from the "Launcher" (or "Home", or whatever). After doing this, a reboot will present you with the choices again. Screenshots for a likely sequence below.
2. A more general quick-and-dirty method that will work in any situation: install yet another launcher app. When you reboot, the activity picker will see a new option and give you your choices again. When you've got it right, just uninstall the additional launcher (which you never have to run for this method to work). Here's a link to another simple and relatively useless launcher that will fit the bill.

nmyshkin said:
Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
Click to expand...
Click to collapse
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
any ideas on what i could try different to get working ? otherwise im stuck on a de-registered 1.2.1uk so my only option might be to nuke all b&n and go custom ereader route (which is probably fine tbh)

A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?

Renate said:
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Click to expand...
Click to collapse
yeah it looks normal on my computer (im running popos although i cant see how that would change anything)

Well, you can always do it semi-manually, at least you'll get feedback.
Extract META-INF\com\google\android\update-binary
Go to TWRP and use ADB to push both the (original) zip and the (extracted) update-binary somewhere useful.
Use ADB (you do have a rooted prompt?)
Code:
# chmod 755 update-binary
# ./update-binary 2 1 whatever.zip
You'll get text out of this and maybe figure out what the problem is.

cyberboy666 said:
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
Click to expand...
Click to collapse
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, just in case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1

nmyshkin said:
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, jus tin case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
Click to expand...
Click to collapse
omg thanks ! yes i think issue was with CWM card - i flashed a new one from the link you gave and now it is working
and also thanks for the advice @Renate - i want to get set up/learn to send ADB anyway so this is helpful

Hmm, well, I didn't know that.
OTOH, you would have seen that you couldn't find an update-binary in that zip.

nmyshkin said:
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
Click to expand...
Click to collapse
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)

jewelie said:
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
Click to expand...
Click to collapse
I'm glad it worked for you. That's my reward
Unless your glowlight is not turning off completely, I can't think of any other factor on a stock system that would drain the battery fast, barring some unknown hardware issue.
Hopefully this sorts it out.

On top of the running an unregistered device, I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing. Other possibilities that have been suggested to me are corrupt books, and maybe having the WiFi off.
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Device is now on sleep with wifi off and no books after the fresh start. I also hacked the cover I was using to make sure it wasn't touching the screens or buttons. It's at 79% now, let's see what the percentage goes to over the next few days...
EDIT: BTW The reason I know it's not the battery itself is because I disassembled it and tested the battery through a few 0.5A charge & discharge cycles and gave it a week to see if there was any significant self discharge - madly, it still has almost the full 1500mAh capacity - impressive for a device that's been going for 10yrs now!

jewelie said:
I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing.
Click to expand...
Click to collapse
I think this has been debunked in the distant past although I can't put my finger on the particular post.
jewelie said:
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Click to expand...
Click to collapse
That part is interesting and the initial result is not surprising. Unfortunately CWM cannot do a thorough wipe unlike, say, TWRP. A factory re-image is the most thorough cleaning I'm aware of, followed by the deregister/erase, then with CWM bringing up the rear. The reason I didn't include a factory re-image at the beginning of the process is that I wanted to keep it simple and not scare away those averse to anything approaching root. The 8-failed-boot-attempts method for a factory re-image is tremendously tedious and involves close timing and dexterity. OTOH, a NookManager card can initiate the process with the push of one hardware button. But that means making yet another card and flirting with the whole root thing (not necessary to root just to do the factory re-image).
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.

@nmyshkin Thank you so much for the detailed guide.
I followed all the steps without any issue. I even got the freezing bug after clearing the Dalvik cache. But followed your steps, pressed on the power button twice and it restarted.
I used a 2Gb memory card and used the sd_2gb_clockwork-rc2.zip and I've written the image with WinImage 8.50.

nmyshkin said:
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
Click to expand...
Click to collapse
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?

jewelie said:
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
Click to expand...
Click to collapse
I'd say so, especially if you've been doing any reading at all.

nmyshkin said:
I'd say so, especially if you've been doing any reading at all.
Click to expand...
Click to collapse
Update: It's over a month later, battery is still on 26%. Touch wood, it's fixed. THANK YOU!