Related
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
I’ve been helping a buddy get his A500 back to working order, so I thought I’d add the steps taken here which lead to successful replacement of boot loader and ability to flash roms again.
First off Blackthun3r is a genius and you cats should totally donate and thank him if this stuff helps.
The info is a bit spread out so I hope this helps consolidate things. We all owe big ups to jnktechstuff for starting this post here:
http://forum.xda-developers.com/showthread.php?t=1699277 go thank him too.
One thing everyone is right about: You must secure your ID just in case, which is needed to properly reprogram the stock/crappy recovery boot. Two options I saw:
1) From a nandroid backup (inside the clockwork recovery folder or wherever your previous bootloader stored them) there is a uid.txt file.
2) When you run Afterota if it can’t find a uid it will generate a file “AcerIDs.txt”.
Afterota is great too but wouldn’t fix/attached to our A500 in APEX mode, but this feature alone is huge.
For AfterOTA, Thanks and Salute to Gersma:
http://forum.xda-developers.com/showthread.php?t=1675939
Next is just getting the thing to boot.
http://forum.xda-developers.com/showthread.php?t=1699277
Mentioned in “How to unbrick” , as stated they suggest you get 3 files. Here’s what we got :
1) Decrypter (mandatory)
2) 2 ICS roms (you only need one, but he suggests to get both just in case, or even an older Honeycomb if those fail you).
The one that worked for us was ICS 4.0.3: 7.014.01_41.203.01.
Extract the decrypter and use on the rom/zip you downloaded. It will make a separate rom/zip with the words ‘decrypted’ at the end. EXTRACT THIS FILE!
Inside the newly extracted zip file should be 3 files. If you don’t have it or your zip program says it’s corrupted then you don’t need to decrypt it, use the non-encrypted version of the rom pack you just downloaded (i.e. it wasn’t encrypted)!
3 files will look like:
1) Update.zip
2) AMSS.zip
3) Acer_A500_7.014.01_041.203.01_COM_GEN1.txt (or whatever rom you had downloaded)
These 3 files need to be on the root of your external SD micro card (either put it into a reader for pc access or if your system is functional copy it over via USB cable while mounted in the A500). The basic bootloader does nothing but check for an update.zip and apply it. However, it cannot replace itself (saw with a CWM or TWRP) and thus what I think is the ‘rub’ with this device.
After the update.zip applies, boot the system normally. You should have a locked OTA version of ICS with USB Debugging enabled, if not, hit Options, Developer and turn on USB Debugging. If it doesn’t boot, try another rom/decrypt combo. If it boots moved these three files into a sub folder on your SD Card and save for next time you brick it
Next, get the right driver for Windows from Acer site (this is important because it has the ICS USB and the APEX/boot USB driver needed):
http://www.acer.be/ac/nl/BE/content/drivers
You now need to unlock, add SU and Super User. Hit the following link and get Blackthund3r’s Root app (ICS7.1.x for Windows) top of page:
http://forum.tegraowners.com/viewtopic.php?f=30&t=350
When you hit some of this download links be sure to check for things like the skip ad button top right corner, else you’ll download the wrong thing:
Extract and run “ICS Root 2.exe”
1) DO NOT mess with the bundles tabs right now, but ensure all checks minus bottom two are selected and ‘Do it!’
2) You should see that it does confirm for you that it is connected and USB Debugging turned on.
You should now have the device setup to run a proper APEX adjustment, which lets you replace the bootloader and then apply all the little zips and roms your heart desires. Blackthund3r has the last tools we need:
Get APXFlash: http://a500bootloaderflash.tk/#download-links (again watch out for the adfly and click skip add to get to your zips).
APXFlash has all the bundles from proper Blackthund3r repository, the FAQ below may have suggested certain types but that info is kinda old SO just grab a bundle 15, 16 or whatever you are looking for (16 is a great team wiz recovery version combo Skrilax has done, we used that one).
1) Go to Bundle Market and follow the wizard:
2) After downloading the bundle of choice you’ll now be prompted to put in your SBK number from that Acer ID or uid txt file.
3) You should then back up your dump file as it is recommended in the process.
4) Hit blue arrow ‘next’ to see your flash options below, we used the Automatic method, smooth as butter.
5) Follow the prompts for APX mode and click blue once the device is blacked out and the mode has changed on status. This is where that official Acer driver comes in handy.
6) Complete the process as instructed and you’ll be good to go!
Last tool used is:
A500 Manager: http://a500bootloaderflash.tk/#download-links (again watch out for the adfly and click skip add to get to your zips).
This app rocks to help you get into recovery mode (or test your new bootloader) until you get a rom on there that allows you to do it from the power off button or notification tray.
Most of these links and info are at the bottom of Blackthund3r’s FAQ page, which were also super helpful:
http://a500bootloaderflash.tk/
Again this helped my friend and he was thinking several of you could benefit. Even when typing this up I figured some better/quicker ways to maybe get some of the data but this is the thorough steps we took and I hope it helps you! I also had screen caps so once I figure out how to add those, if it'll help or someone needs it will look into that ;p
** DoPa5 v1.0 (AOSP v5.0.2_r1 - Lollipop) is now available for US/UK/AU users **
If you would like to upgrade from the stock ROM, see this post for downloads and installation details
Click to expand...
Click to collapse
DoPa v2.0 is an enhanced version of the stock ROM that features a custom-built kernel. It is based on Hisense's August, 2013 update (build P756.6.02.20) and is intended for US (8gb) versions of this tablet. It does not support the 32gb models sold in the UK and Australia. See Post 2 below for packages to root this tablet and install CWM Touch recovery.
This ROM de-bloats the original, roots it using SuperSU, and adds several useful apps, among them: Apex Launcher and ES File Explorer. It also includes several Xposed Installer modules to tweak your system, including GravityBox and my Phab7 UI switcher. For the hackers amongst us, ADB always runs as root.
The kernel is built from Hisense's source and offers enhancements and bug fixes. Most notably, it provides USB-OTG support so you can connect USB storage devices (e.g. thumb-drives) to your tablet using an OTG cable. It comes in two flavors, a non-overclocked version included in the main package, and a separate overclocked version that can be installed (and uninstalled) independently.
Installation
Having CWM installed is a prerequisite; if you haven't installed it yet, see Post 2. This ROM is intended to function as an update, preserving your apps and data. Unless you want to start from scratch, do NOT wipe or clear anything - the install script will do what's needed.
copy the file(s) to your internal or external SD card
reboot into CWM, then select "install zip"
I recommend you select "toggle signature verification"; enabling this will confirm the file hasn't gotten corrupted (if you get a verification error, stop, then copy the file to a different SD card)
choose the menu entry corresponding to where you put the file(s), then select "sero7pro-bld60220-dopa-v2.0.zip" from the list
after confirming your selection, the update will display what it's doing; you should NOT see any error messages
if you'd like to install the overclocked kernel, you can do so once the main package is in place, or at some later time
reboot
Notes
when you attach a drive using the USB-OTG feature, it is automatically mounted at '/usbdisk'. Be aware there is no easy way to unmount it - you may have to use adb or a terminal app to ensure a clean unmount. This should only be an issue if you write to the disk; if you're only reading, it may be safe to just pull the plug.
the overclocked version of the kernel runs the processor at 1.5ghz rather than the standard 1.3ghz. Using it may result in a significant loss of stability on some systems. You may want to install one of the many apps that let you control the maximum speed to regain stability and reduce power consumption.
much of the app-bloat this ROM tries to eliminate (such as Sams Club or Playstore Magazines) may still be present if you've ever gotten updates for any of these apps. To get rid of them permanently, uninstall them using Settings->Apps->Downloaded. For "system" apps like the Google stuff, select "Uninstall updates", then "OK" when it asks if you want to revert to the factory-installed version (which doesn't exist anymore). The apps will be gone for good.
to enable the many tweaks offered by GravityBox and Phab7, open the Xposed Installer app and enable it via the "Framework" option but don't reboot yet. Back out and choose "Modules", then tap directly on the checkbox to the left of each module's icon (not on the icon or text). Now, reboot to activate their features.
Note: GravityBox's Quick Settings tiles and statusbar mods only work with the Phone or Phablet UIs (i.e. not Tablet UI). To get the full effect from Tablet UI, open Apex Launcher's settings and select "Homescreen settings->Use tablet UI mode"
Geek Alert: with the addition of DriveDroid (not included), this kernel lets your tablet emulate a USB CD drive that can be used to boot your PC. See the app's description for details.
Credits
xboxexpert - for getting things going
randomblame - for many of the patches used in this kernel
Files
new and improved:
sero7pro-bld60220-dopa-v2.0.zip - the DoPa v2.0 ROM with the standard kernel
sero7pro-boot-dopa0oc-v2.0.zip - the overclocked kernel
sero7pro-boot-dopa0-v2.0.zip - the standard kernel (in case you want to reinstall it)
old and tired: (do not use with v2.0)
sero7pro-bld60220-dopa-v1.1.zip - the DoPa v1.1 ROM
sero7pro-usbotg-dopa-v1.1.zip - USB-OTG add-on
sero7pro-macfix-dopa-v1.1.zip - random MAC address fix
sero7pro-sysui-dopa-v1.1.zip - removes screenshot button
miscellaneous:
sero7pro-bld60220-removed.zip - files that were removed from the DoPa ROMS (note: unlike the other files here, this is not a flashable zip. Unzip it, copy the apps you want to your SD card, then install them from there)
stock-v60220-full-update.zip - the complete 6.02.20 update from Hisense - this is the closest you'll get to the original stock ROM
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
XDA:DevDB Information
Sero 7 Pro (US) - DoPa v2.0 Modified Stock ROM, ROM for the Android General
Contributors
dolorespark
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.1.x
Based On: Stock ROM
Version Information
Status: No Longer Updated
Current Stable Version: 2.0
Stable Release Date: 2014-01-22
Created 2015-01-26
Last Updated 2015-01-27
Root/CWM packages
These packages will root and install CWM Touch recovery on the US (8gb) model of the Sero 7 Pro. There are separate versions for Windows and Linux. They have been tested under Win XP, Win 8, and Ubuntu, and should avoid problems encountered with other root/recovery packages.
The packages are modular so that you can run some or all of the functions as-needed. They consist of 4 scripts:
step0-DoItAll - displays some setup info then runs all 3 of the following
step1-adb - enables ADB ("Android Debug Bridge") to locate the tablet
step2-root - roots the tablet and installs the SuperSU app
step3-cwm - installs CWM Touch Recovery v6.0.3.2
Versions of ADB for each OS are included, so no other packages or downloads are needed. Usage should be fairly simple: unzip the package into a convenient directory, doubleclick on step0-DoItAll, then follow the (minimal) instructions. Alternately (and better), open a command prompt/bash shell, change to the directory where you unzipped everything, then run the script(s) from there.
Avoiding Frustration
If you haven't rooted an Android device before, please read the following because there are a few "gotcha"s. If you have but things aren't going as expected, review the following in case you missed/forgot something.
Developer options must be visible in the Settings app. If they aren't, select "About tablet", then tap on "Build number" 7 times. A small popup will tell you that you're now a developer. Back out to the list of settings categories - you should now see "Developer options".
USB debugging must be enabled under "Developer options". Please be sure it is. If it isn't, select it then tap OK when a warning popup appears.
Both Windows and Linux require extra files to be in place before ADB can communicate with your tablet. Click on the button for your OS to see the ugly details.
Windows
Windows requires USB drivers to be installed. Drivers that will work with the Sero7Pro (and possibly any Android device) are included in the package.
After enabling "USB debugging" and connecting your tablet, a wizard may pop up to guide you through the steps. If not, force it to appear by opening Device Manager. Look under "Other devices" where you should see something like "Android phone". Doubleclick on it, then select the "Install driver" button on the window that appears.
When the wizard pops up, tell it you'll select the drivers, then choose the option that tells it where to look. Click the "Browse" button and navigate to the directory where you unzipped the package. Select the usb_driver folder, press "OK", then "Next" - the drivers should install without any problems.
Notes: On Windows XP, the first wizard to pop up may want to install drivers for "MTP" which XP doesn't support. If so, cancel out of that, then wait for the "Andoid Phone" wizard to appear. On later versions of Windows, you may get a popup warning that the drivers aren't signed properly; if so, select "Install driver anyway". On Win 8-64bit, driver installation will fail unless you started the current session with "Driver signature enforcement" disabled.
Linux
Linux (or at least Ubuntu) doesn't allow user programs to access USB devices directly without the appropriate permissions in place. This package includes a file named 99-android.rules which provides those permissions
If you've never provided access to other USB devices, just copy the file to /etc/udev/rules.d. Otherwise, you can either copy it or merge its contents with the .rules file containing your other USB entries.
Note: both the rules.d directory and its contents are owned by root. You will probably have to use the sudo command to gain access. For example, from a bash shell whose current directory is the one where you unzipped the package, you'd enter "sudo cp 99-android.rules /etc/udev/rules.d". Also, be sure the file's permissions match the others in that directory. If not, run "chmod 644 /etc/udev/rules.d/99-android.rules".
Notes
When you're done, open the SuperSU app to enable it. It will ask to update the su binary. After selecting OK, the app will be enabled and will popup warnings whenever an app requests root access for the first time.
The Linux script is actually designed for both Linux and Mac OS X. However, I haven't fully tested it yet so I don't want to make any incorrect claims of support. You may have to correct some file permissions and will almost certainly have to run it from the Terminal app.
Files
sero7pro-root-win-dopa.zip - Windows
sero7pro-root-unix-dopa.zip - Linux
[Obsolete] Remove Screenshot Button / Add Instant UI Switcher
The mod originally described in this posting is now obsolete with the release of the DoPa v2.0 ROM which has both features built in.
If you are running an older version of that ROM, or XBoxExpert's ROM, or even the stock ROM, you can still remove the screenshot button using this CWM-installable package: sero7pro-sysui-dopa-v1.1.zip.
If you'd like to try Phab7, an on-the-fly UI switcher that lets you select Phone, Phablet, or Tablet UI modes, see this thread. Note: you must install the SystemUI mod to switch to Phone UI - without it, SystemUI will force-close when you do.
Good work. Hope to see more devs and more Roms
Really good. I'm using it right now. Keep going with the good work
Good Job! Looking forward to more posts!
Thanks for the nice work and good instructions. I'm using your stock ((build P756.6.02.20) rooted now and plan to try the ROM soon without Link2SD operational to keep all my apps.
Thanks again, I have updated my Sero to this ROM. Everything seems to be working perfectly. I look forward to many updates!
Thank you. Your ROM runs smooth and fast.
Great work man, downloading it now! Thanks!
Antutu result for this ROM
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Installed and working. Thanks.
taba4real said:
12979 is my antutu result for this ROM while my previous stock ROM result was 11948 while 12339 was result of XE ROM. Thank you!
Click to expand...
Click to collapse
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
larryf said:
I'm getting 13861 on this ROM, 11249 on the previous XE ROM.
Ran it twice, results were very close. I did leave all the 'tweeks' in from Xbox's post, not sure if that makes any difference.
Larry
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Why am I getting 10500 on this ROM then?
Does this root and cwm change kernel like xbox's?
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Cooter007 said:
Did you run it with the raw system? What I mean, is did you run it after the ROM settled out and after a few reboots or did you flash and then run the benchmark? It is probably over kill but I like to let the ROM sit for awhile and then do a couple of reboots before I run bench marks. My first score was very close to larryf's score (13,800) the first time I ran it, but after I added live wallpaper, Nova launcher, Xposed, etc. my last score was 11395. I assume any benchmark program would shutdown all non essential programs before running but that may not be the case.
EDIT: Wow, I rebooted right after I type this and ran AnTuTu again and it scored 14,425.
https://www.dropbox.com/s/kmwd7jgjpcw233y/Screenshot_2013-10-07-22-38-57.png
Click to expand...
Click to collapse
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
lordroy said:
I flashed it days ago with this ROM, lots of reboots etc. Not sure what I am doing wrong or why my score is so low.
Click to expand...
Click to collapse
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My HomeScreen ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Cooter007 said:
It may have something to do with my minimal approach to this tablet. I bought this tablet to use in the car. After setting up Nova Launcher, I'm pretty much down to two addition; ODB2 and CoPolit.
My desktop ----- https://www.dropbox.com/s/rsdp9oskbhtg9jp/Screenshot_2013-10-07-23-05-38.png
Click to expand...
Click to collapse
Of course as soon as I mention something, my Sero decides to play nice.
Just got a score of 13861. I didnt change anything, it just decided to score better for some reason.
lordroy said:
Why am I getting 10500 on this ROM then?
Click to expand...
Click to collapse
Sir i used to get this with Power Saving mode instead of Perfromance priority mode....... =):good:
DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2!
This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something moderately more cohesive and understandable. Here's my moderately usable guide!
-----------------------------------------------------------------
VIDEO!
-----------------------------------------------------------------
-----------------------------------------------------------------
Things that work and don't work:
-----------------------------------------------------------------
This section will update periodically as issues arise or fixes arise for said issues.
Note: Things that work: Bluetooth*, all sensors, audio, LTE/SIM/phone stuff, 120hz (you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected])
Things that probably work: N/A
Things that don't work for some reason: SafteyNet with Magisk. All modules that I've used work tho...??! Verizon.
Remember, you can always flash back to stock if something doesn't work properly.
-----------------------------------------------------------------
FIXES!!!
-----------------------------------------------------------------
AUDIO FIX!!! GO TO Phh Treble Settings > Qualcomm features > Use alternate audio policy.
Bluetooth audio stops working with this enabled. Disable it for Bluetooth audio. The audio fix doesn't apply to Bluetooth audio ether way.
BLUETOOTH FIX!!! Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Important notes
-----------------------------------------------------------------
THIS IS ASSUMING YOU HAVE ALREADY UNLOCKED THE BOOTLOADER OF YOUR DEVICE AND HAVE GOTTEN A SERIAL NUMBER OUTPUT FROM CMD AFTER TYPING IN "fastboot devices" AND MAKE SURE YOU HAVE TYPED IN "fastboot flashing unlock" AND "fastboot flashing unlock-critical".
***NOTE: I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES OR ANGRY PARENTS. PLEASE DO NOT COME BACK AT ME SAYING I AM STUPID AND BRICKED YOUR PHONE. YOU DECIDED TO DO THIS. PLEASE PROCEED WITH CAUTION AND DON'T SKIM***
ANOTHER IMPORTANT NOTE: The stock firmware is actually really good for unbricking devices. Razer made it easy to fix your bricked device. So basically, if you can get in to fastboot mode, (which you basically always can do) you can unbrick your device super easily.
AGAIN JUST PLEASE, MAKE SURE TO FOLLOW ALL THESE INSTRUCTIONS CAREFULLY AND DONT SKIM OR ELSE YOU MIGHT BREAK SOMETHING!!!
-----------------------------------------------------------------
Introduction
-----------------------------------------------------------------
This is a quick and easy guide for how to install Android 11 on the Razer Phone 2. I'm kind of a noob here myself but I did this and it worked flawlessly. (also if you do run into any issues PLEASE don't count on me for troubleshooting tips (I'm not that great at that))
-----------------------------------------------------------------
Pre-requisites/Downloads
-----------------------------------------------------------------
Get the factory firmware for your phone. It's a good failsafe in case of a bootloop or a bad case of the phone not booting up. Download it here: P-SMR6-RC001-RZR-201022 (latest build at the time of writing)
Extract this with 7zip or WinRar (or windows. You will need 7zip or WinRar for the rest of this)
First you need the actual GSI. Get the latest version. (Make sure its not a pre-release). system-roar-arm64-ab-vndklite-gapps.img.xz is the version that you should get. The vndklite release will allow you to modify the system partition making it possible to get magisk. Note: If you want magisk, MAKE SURE TO COMPLETELY follow the magisk section of this guide aswell or else magisk will NOT install correctly and will NOT work.
This version also has GApps. It will give you Gmail, the google play store, google play services, etc.
Use 7zip or WinRar to extract this.
Your also gonna need the Trinity Kernel (v2). This gives you TWRP and I'm pretty sure you also need this to have the ability to boot up the phone (I may be wrong but it's required.)
use 7zip or WinRar to extract this.
You will also need this zip file made by arter97 I don't really know what it does but you need it. here is the download: Download.
Don't extract this.
Put all these in a known folder that you can access later.
Alright. Now that we're done with the downloads, time to test to make sure your ready to put this on your phone.
-----------------------------------------------------------------
Making sure your computer is ready
-----------------------------------------------------------------
First things first. Go open your platform tools folder, shift-right click and open a PowerShell, or command prompt window there. Shut down your Razer phone 2 and turn it back on with the power and volume down buttons.
Plug it into your PC and type in
Code:
fastboot devices
you should end up with the serial number of the device. if you don't, follow Razer's instructions on how to install USB drivers and then come back here. Link to PDF.
If you get a serial number, close that and flash stock firmware by going into the aura-p-release-etc. folder, then opening flash_all.bat.
When it finishes and the screen goes black, hold the power and volume down buttons again to get back in to fastboot mode.
open back up the CMD/PowerShell platform tools window thing again.
-----------------------------------------------------------------
Installing/Flashing
-----------------------------------------------------------------
In your CMD or PowerShell window, (while in fastboot mode on the phone) type
Code:
fastboot flash system <file name>
in the <file name> area, just drag and drop the system-roar-arm64-etc.img file into your command line. your command will look a little something like this:
Code:
fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
Wait until it says complete or something similar like done or something and has no errors.
Then, time to flash the kernel. it should just be called boot.img.
We will be typing in:
Code:
fastboot flash boot <file name>
Do the same thing that you did for the last command which is drag and drop the boot.img file for the file name.
Again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select reboot bootloader with your power button on your phone.
Go to recovery mode and swipe where it says to swipe.
Go to the wipe menu and then tap on format data. Type yes and then press enter/ok.
Go back to your computer and open file explorer.
Put the last zip file that I was talking about earlier (the f2fs thing) on the razer phone 2's internal storage. Head back to your phone, and press install.
Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that, go back to the TWRP home screen (with the 8 options)
Go to the reboot menu, then reboot into recovery
Tap on format data and type in "yes" and tap ok. click on "don't install" because you don't need the TWRP app on your phone.
The phone will shut down. Turn it on normally and everything will work!
----------------------------------------------------------------------------------------------------------------------------------
GET THESE THINGS IF YOU WANT 120Hz, GCam, and a SNAZZY RAZER LOGO.
----------------------------------------------------------------------------------------------------------------------------------
To get 120Hz, you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected].
If you want your Razer logo to light up again, use Logo+. here is a download: Logo+ APK
The default camera app sucks. Make sure to get GCam 7.4 from Cyanogen Mods (v8.0 is broken). you can get it here.
Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Magisk
-----------------------------------------------------------------
So this part was pretty long-awaited. It half-passes SafteyNet and modules work! (at least all the modules that I've used.)
Make sure you have the vndklite variant. That is the only way that this will work.
1. Open up an adb/fastboot powershell/cmd/windows terminal window.
2. Type adb root and hit enter.
3. Type adb shell and hit enter.
4. Type mount -o remount,rw / and hit enter.
5. Type mv /bin/resetprop_phh /bin/phh-resetprop and hit enter.
6. Type phh-securize.sh and hit enter.
The phone should reboot after you approve the request (if there is one) and you are now able to install magisk!
MAKE SURE THAT THE SUPERUSER APP IS NOT THERE AFTER RUNNING phh-securize.sh.
Get specifically this version of Magisk. Download the zip file.
Boot into TWRP and tap on mount, and select everything (usb storage doesn't matter in this case. it never mounts either way.)
Transfer over your zip file via file explorer, and go back to your phone.
Tap install, then scroll down until you find the zip file and tap it. Swipe to flash and wait. After it is done, you can reboot!
You should see Magisk manager in your app drawer. Open that. It might ask you to install it, if so, install it. Allow apps from this source then install. Open it up. You should see that Magisk is installed. Update it and turn on Magisk hide.
If it passes SafteyNet, it's a miracle.
-----------------------------------------------------------------
In case of failure
-----------------------------------------------------------------
If it starts bootlooping or is perpetually stuck at the razer logo, powered by android screen, go back into fastboot mode and run the flash_all.bat stock firmware thing. it will unbrick your phone automatically. Really make sure you don't skim if you try it again. If it did work (which it probably did), then have a good time with android 11!
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Reznor7 said:
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Click to expand...
Click to collapse
Just curious, what games have that issue?
Marcos8760 said:
Just curious, what games have that issue?
Click to expand...
Click to collapse
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Reznor7 said:
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Click to expand...
Click to collapse
Thanks for the info. I added that to the top of the thread.
EDIT: Fix at the top of the thread
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
rrusek said:
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
Click to expand...
Click to collapse
I got the Razer logo working flawlessly with logo+. I didn't really see the appeal for Dolby Atmos as all it did was made it louder and made the audio clip more.
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Reznor7 said:
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Click to expand...
Click to collapse
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Marcos8760 said:
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Click to expand...
Click to collapse
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Reznor7 said:
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Click to expand...
Click to collapse
Alright good to know. like the other info I've gathered, ill put that at the top of the thread until further notice.
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Reznor7 said:
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Click to expand...
Click to collapse
Nope, Magisk doesn't work.
Thank you. I got it all set up and mostly working well. I was wondering if you could try Minecraft and let me know if it will let you get to the actual login screen.
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
AgentXGhost said:
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
Click to expand...
Click to collapse
You forgot to extract it with winrar or 7zip. make sure it is a .img file and not a .xz file.
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Thanks very much. It works perfectly.
AgentXGhost said:
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Click to expand...
Click to collapse
oh noes!
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Gurcharan5 said:
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Click to expand...
Click to collapse
Try going to wipe, then format data. That might fix the problem. If not, try everything again.
This one20092011201220132015201720192021Nook v1 Nook Simple TouchNook Simple Touch w/ GlowlightNook GlowlightNook Glowlight PlusNook Glowlight 3Nook Glowlight Plus (7.8 inch)Nook Glowlight 4
The other one
The 2019 Glowlight Plus shares the same name as the 2015 release. To avoid confusion, people began referring to it as the Glowlight 4, a name later used for the 2021 Nook release (surprisedpikachu.jpg). While the 2019 Nook is both confused with the 2015 and 2021 Nooks, it is less common than either. This makes it difficult to find compatible resources and tutorials.
This thread is for collecting the available resources for the 2019 Nook in one place, and eventually building a step-by-step guide for unlocking the potential of the device.
Why the BNRV700?
Three years after its release, it's currently the cheapest option for a reader with a screen size ideal for large format PDFs, such as textbooks. As of writing, the Nook Glowlight Plus (2019) can be found for half (or less) the price of other options with a similar display.
Unfortunately, the Nook ships with poor support for PDFs, sluggish hardware, severely outdated firmware (Android 4.4.2, released 2013) and lacks additional features like expandable storage. Some of these issues can be remedied, meaning the Nook could be a great option for many people, but only if it's safe and convenient to expand its functionality.
If you know of any useful resources or guides, please leave them in the comments below.
Note: This is an early work in progress. As of writing this, I don't have the device yet.
I'm reserving this space to put any resources, or document my experience with rooting or recovering the Nook Glowlight Plus 7.8 2019 (NGP7.8, BNRV700).
Resources
Technical
Hardware overview: TemblastBackup and Recovery
TWRP: GithubNeo Noogie: Temblast, XDA-threadRooting
Magisk Root guide (Glowlight 4): Mobileread-threadCaution: This guide is specifically for the Glowlight 4 (2021) rather than the Glowlight Plus 7.8 (2019) but it might be applicable.RootGLP-3 script (Glowlight 3): XDA-threadCaution: This resource is for the Glowlight 3 (2017) rather than the Glowlight Plus 7.8 (2019), however it has been reported to work.RootGLP-3 script (2019 Glowlight Plus): XDA-threadNote: This is a small modification of the Glowlight 3 (2017) root script for the 2019 Glowlight Plus, from wgznz (Chinese).Firmware
Alternate ROM: XDA-threadSoftware
Installing a launcher:Installing apps:Compatible readers and utilities:Adding wallpapers:Adding a software back button:Physical button remapping:Hardware
Expandable storage mod::
High risk or incompatible resources
Mods
NGP Exposed module with fast refresh: Mobileread-threadSupported: Nook Glowlight Plus (2015), Nook Glowlight 3Notes: Due to the similarities between the NG3 and NGP7.8 (2019), someone might be able to get this to work, but it's untested.
jun127 said:
I think more people would be willing to try it. But, between confusing and inconsistent naming making searches difficult (now even worse with the "Glowlight 4") and a lack of step-by-step guides, it's a minefield for the casual user to modify, and most aren't interested in the sub-standard Nook software.
Click to expand...
Click to collapse
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.
nmyshkin said:
I don't know whether you saw this and then dismissed it or just missed it: https://forum.xda-developers.com/t/gp-g3-gp7-8-twrp-alternative-firmware.4074347/
Seems like that might address most of the issues you have expressed.
Click to expand...
Click to collapse
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
Rough draft / work in progress (proceed at own risk)
Getting started
Download and install ADB
Using Android Studio
1: Download Android Studio
2: Scroll down and click on “SDK Tools Only”
3: Click on “ADB, Fastboot, and Platform Tools” and then click on the “Download” button.
4: After “adb_setup-x86.exe” is downloaded by the installer, run it and install adb inside the android SDK folder.
Using Minimal ADB and Fastboot
1: Download the installer or portable version (See: original XDA thread, latest version 1.4.3, 2018).
2: Install and run
Note: If you use the portable version, commands should be ran from the same directory. To open a console in the current folder on Windows, select the address bar, type cmd and hit enter.
Enable USB debugging through developer options
1: Unplug the nook from the computer and turn the Nook on, register an account with Barnes and Noble and finish setting the device up.
2: Pull down the top menu
3: click "see all settings"
4: Press the down error on the bottom of the menu to go to the second page of settings
5: Press "about"
6: Tap the Nook logo until developer mode is enabled
7: Press "developer option settings"
8: Enable the "usb debugging" option
9: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.Note: When running commands over USB, sometimes it's necessary to temporarily disable mass transfer mode. To do this, go back to the developer options menu and select "disable mass storage".Important: Remember to re-enable mass storage mode if you would like to drag-and-drop files onto your device using Windows file explorer later.
Backup and restoration
The two most popular methods of creating and restoring backups are TWRP and Neo Noogie. If possible, it's best to have a backup from both. However, if you're not comfortable using the command line in Windows, you may choose to use TWRP only. Neo Noogie is a more powerful (complete) backup method, but it's easy to accidentally format your device or write a backup to the wrong Windows drive, either of which could be a nightmare.
TWRP is recovery software that is installed to the device, and provides a menu to backup and restore parts of the device to internal memory. You'll have to copy the recovery files from your device afterwards.
Neo Noogie can either be installed like TWRP or booted with fastboot. When booted into Neo Noogie, the entire flash memory is served to Windows and appears as a raw unformated drive. The internal storage can then be copied with special software. This has the advantage over TWRP in that it can be used to backup every aspect of your device, but you have to be very careful not to accidentally format the drive in Windows, as it could brick your device.
TWRP
Download TWRP
1: Download twrp_quill.img (may, 2020) from https://github.com/Ryogo-Z/nook_ntx_6sl_twrp/releases
2: Move twrp_generic to a folder (such as Documents\Nook)
Install TWRP
3: Power the NOOK BNRV700 off.
4: Hold the U button and then the power button until it starts into fastboot mode.
5: Connect the Nook to a Windows computer with USB, the drivers should be installed automatically.
6: Open the command prompt or Minimal ADB and Fastboot
7: Navigate to the folder you saved the TWRP image in (ex. starting from your user directory, enter "cd Documents\Nook").
8: Enter fastboot flash recovery twrp_generic.img to install TWRP
9: Enter adb reboot recovery (or interrupt startup 5 times) to enter TWRP recovery mode
Create backup with TWRP
Notice: (TWRP will not backup /storage/spsd as well as /data/media, which in practical terms means ...xyz...)
1: (I don't have a Nook anymore as my NST screen isn't working and haven't used TWRP in 10 years. I imagine it's something like boot into recovery/TWRP > Backup > check all the options > run)
2: Plug the Nook into the computer
3: Select USB mass transfer protocol
4: Open the Nook in file explorer and find wherever the recovery was saved to
5: Copy it to a safe place, like documents\nook.
Uninstall TWRP / reinstall stock recovery
The Nook's update file, 'update.zip' contains a copy of the stock recovery which can be reinstalled if you wish to return the Nook to factory defaults. However the stock recovery has fewer recovery features - so it is always safest to keep TWRP installed if you are tinkering with the device.
Rooting
Root Guide for the 2019 Glowlight Plus (using rootGLP)
1: Ensure you've enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2: Connect the Nook to your computer. A popup will appear on your Nook asking to "turn on USB mode to safely move files..." click OK.
Note: This will cause your computer to download the appropriate drivers. After the drivers have been installed your Nook will show up in Windows Explorer and the Device Manager.3: Disconnect the Nook and go back to the developer settings menu (see steps 2.1) and select "disable mass storage".
Note: This will prevent USB mode from interfering as we run the ADB script.3: Download rootGLP.rar
Note: this is the same root script for the Glowlight 3, updated with the correct device name BGRV700. The original can be found in this XDA-thread. For a root guide for the Glowlight 3 using rootGLP, see this XDA-thread. The source is the wgznz forum (Chinese).4: Extract rootGLP
Note: It's best to run the script from a location like C:\rootGLP\ or D:\rootGLP\.5: Run the rootnook.cmd
Note: After the process is complete, you will see superSUfree appear on the screen. You will still need to install an alternate launcher.
Installing apps
Installing a launcher and apps (doesn't require root)
If you haven't installed ADB, you can use the copy of adb.exe in the rootGLP-3\bin\ folder by following the instructions below. After installing a launcher, you should consider installing a file browser (such as ES file explorer) and a better web browser, so that you can download and install apps without connecting to your computer.
1. Make sure you have enabled USB debugging tools from the developer options menu and saved a backup to a secure location
2. Navigate to the rootGLP-3\bin\ folder.
3. Place the launcher .apk inside the bin folder with adb.exe.
4. Click the address bar in Windows Explorer and type "cmd" without quotes and hit enter. A windows CMD terminal will open at the current folder address.
5. type adb install launchername.apk (replace with the name of your .apk file)
Note: kk launcher and text launcher are known to work.6. When you hit the U-shaped home button on your Nook, it will prompt you to select a launcher and ask if you would like to set it as the default. I recommend using "only once" at least until you can ensure you can always get back to the default launcher from whatever Android 4.4.2 compatible launcher you choose.
Installing KOreader and getting pageturn buttons working in KOreader (no root)
1. Download KOreader apk from https://koreader.rocks/
2. make sure your device is connected to adb and authorized with adb devices, if it t says "unauthorized", go to the developer menu (nook home > top right > all settings > page 2 > more > repeatedly tap logo) and tap "allow debugging".
3. install adb install koreader.apk. just hit tab to autocomplete the actual apk name.
4. Create a textfile "event_map.lua" in notepad and copy paste the following keymappings:
Code:
return {
[141] = "RPgBack",
[142] = "RPgFwd",
[140] = "RPgBack",
[139] = "RPgFwd",
}
5. use command adb push event_map.lua /sdcard/KOreader/settings/ to push the event map to the koreader settings.
6. If you had already installed and started KOreader before and just want to fix the keymapping, restart KOreader for the new settings to work (launcher > settings > apps > KOreader > force stop > home button > open KOreader > open book > test buttons > enjoy.
The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?
jun127 said:
It looks like it could be a useful resource, but it seems like a lot of steps and cautions are ommitted. Although I've installed TWRP, rooted, and installed the fastink kernel (among other mods) on my old NST, I would hesitate (especially as a new user) to install alternate firmware without a clear procedure to first backup and revert everything to factory defaults or recover if something goes wrong.
etc.
Click to expand...
Click to collapse
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391
nmyshkin said:
I am not the person to ask, but you are right that the first step is to be sure you can restore the device to stock. I'm one of those eccentrics who still loves and uses and continues to develop little improvements for the original NST/G, so all this fastboot stuff is pretty meaningless to me. I've flashed custom ROMs on Nook Tablets, but that's a totally different operation since back in the day Android was not locked up so tightly.
If you jut want a root guide (but it sounds like you want more than that): https://www.mobileread.com/forums/showpost.php?p=4202391&postcount=391
Click to expand...
Click to collapse
I'd like to put together a simple guide, similar to what I wrote for the original NST about 10 years ago. I think the device needs a roadmap to outline what is currently possible in terms that are easy to follow. The device seems like it has a lot of potential, but it's just not very accessible at the moment.
I watched your video on running the CM on the NST, very interesting stuff and I'm glad to see some people are still keeping the device alive. I had used the original NST as a smartphone for a (short) while, even using it with Google phone and Whatsapp. It was surprisingly functional and, with the right optimizations, the battery could seemingly last forever with light use. Although it otherwise held up well, the rubber front panel and soft-touch back eventually degraded into a gooey mess. Removing the soft-touch coating on the back shell and replacing the rubber on the front with leather made it a more enjoyable reading experience for a while. Unfortunately, very poor app availability on Android 2.1 and the small, relatively low resolution display made it almost unusable for large format PDFs. Ultimately, the screen started failing and although it's still worth fixing, after 10 years it's overdue for an upgrade.
Renate said:
The stock recovery is not a big deal. It's in every update.zip
Just flash it with fastboot.
Why do you want it anyway when either TWRP or NeoNoogie is more powerful?
Click to expand...
Click to collapse
There's some peace of mind in knowing how to return things to exactly where you started. Even if unnecessary, there's always the possibility of some unforeseen issue and having a clear roadmap that you can follow to get back to the very beginning makes a difference in my mind.