Related
I recently rooted my Nook Simple Touch Glow and when I try to side load apps through dropbox I get an error "Install Blocked; For security reasons you phone is set to block installation of applications not sourced in the Android Market."
I've read up and there should be a check box in the applications menu that allows unknown sources. The trouble is there is no applications menu.
Any idea on how to fix this?
Thanks in advance!
If you have sqlite3 on your desktop or your Nook, you can just do:
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update secure set value=1 where name='install_non_market_apps';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Sqlite
I haven't used Sqlite before. I downloaded it. Do I just run the text you posted in the dos box?
Also, do I need to have the nook attached through usb?
Well, you have to have ADB working however you use ADB.
That's either WiFi or USB.
The quoted code is normally what you enter.
check in dos box that you have sqlite3 command available. Also you need working android debug bridge (adb) working, through wifi or usb, in your case it would probably be through wifi. I do not recommend you to continoe unless you learn something about adb and make it work. (search forum or use google)
the rest is piece of cake. first (adb) command from #2 downloads one database from nook. Another 3 commands opens that database locally, changes the security setings that enables installation of non-market application and quits sqlite3 client.
last command uploads the changed database back to nook.
ADB?
Thanks for getting back to me. Unfortunately, I really don't know what ADB is.
I haven't used any of these tools. Can you give me a little more detail? I'd hate to make a mistake and screw something up.
Thanks again!
Mark
Sqlite
Thanks for the instructions. I was able to turn on the ADB bridge using adbWireless and connect the device.
I'm confused about the command line in SQLite3. I entered everything as listed, but nothing happens. I don't want to copy over the settings.db until I know it has been changed.
What should SQLite say if I have entered in the command properly?
Thanks again
Code:
sqlite3 settings.db
update secure set value=1 where name='install_non_market_apps';
select value from secure where name='install_non_market_apps';
.q
As you can see I have added one 'select' command into sql section. If your database has been updated properly, select command should print new value 1 (before zero).
I have written this command right now, don't have a chance to test it but it should work.. at least it cannot screw up anything.
Sqlite
I'm entering everything as is and either I get
...> with nothing after it
or
Error: near "sqlite3": syntax error.
In either case, the select command does not tell me if it is updated.
Again, sorry for asking so many times. I'm close!!
Sqlite
I figured out what I was doing. I opened the SqLite window separately when it should have all be in the one cmd window.
So what exactly did this do? I keep getting the same error message that it can't install non market apps. Is there a menu setting I should change?
Thanks again
Got it
Just rebooted and now it's working. Thanks!!
A simpler way to do this, assuming you've used something like GlowNooter and is to go into Nook Color Tools and uncheck and recheck the Non-Market Installs. This will allow you to sideload.
I know that this is for second edition but I don't seen a forum for the first edition so this seems to be the closest match. Anyway I am trying to root my Nook Classic (the one with a E-ink display on the top and color touch screen on the bottom). I am following the instructions on nookdevs for rooting the Nook Classic on all hardware and firmware versions (I can't post the link here as I am new but PM me and I can pass it that way if you need). The method is that sometimes when the web browser browses a certain type of website it crashes and sometimes starts adbd and you can connect adb at that point.
I have managed to get adb to connect, pull the init.rc file, make the needed change, but when I try to push the ratc.bin file adb says it goes though but then the second command $ cd /sqlite_stmt_journals (after starting adb shell) says it is not found. So I can't go any further. ratc.bin is what gives root access long enough to push the init.rc back and without being able to run that, well I am up a creek.
Any ideas?
dob43 said:
I know that this is for second edition but I don't seen a forum for the first edition so this seems to be the closest match. Anyway I am trying to root my Nook Classic (the one with a E-ink display on the top and color touch screen on the bottom). I am following the instructions on nookdevs for rooting the Nook Classic on all hardware and firmware versions (I can't post the link here as I am new but PM me and I can pass it that way if you need). The method is that sometimes when the web browser browses a certain type of website it crashes and sometimes starts adbd and you can connect adb at that point.
I have managed to get adb to connect, pull the init.rc file, make the needed change, but when I try to push the ratc.bin file adb says it goes though but then the second command $ cd /sqlite_stmt_journals (after starting adb shell) says it is not found. So I can't go any further. ratc.bin is what gives root access long enough to push the init.rc back and without being able to run that, well I am up a creek.
Any ideas?
Click to expand...
Click to collapse
>> http://www.mobileread.com/forums/forumdisplay.php?f=209
>> http://www.the-ebook.org/forum/viewforum.php?f=44&sid=e250da1c3a4967da22dae8ca2d104ac8
Thanks osowiecki, I did find a thread on Mobile read shortly after I posted this. The other is non-english I am afraid, and sadly I only speak english.
Anyway I did mange to root my nook today. And I am posting here as I hope it will help someone in the future:
Yessssssssssssssss! I finally hacked my Nook Classic (Nook First Edition called by some)! I followed most of the instructions at http://nookdevs.com/Rooting_B&N_revision_1.4_to_1.7_on_any_hardware
I only tweeked in a few places. Here is a general list of what I did:
1. Look at the site above and grab the linked file (ratc.bin). Then go to this thread http://forum.xda-developers.com/showthread.php?t=1474956 and at the top there grab the adb + fasboot + drivers.zip. The reason I used this is because it is much smaller than the full Andriod SDK (which is over 500mb btw) and I figured this would work since it works for Nook Tablets. I didn't install the drivers or anything though. Just used adb.
2. Went with nook browser to http://nookadb.suspended-chord.info/ to crash the browser. If this should ever be down I see on the nookdevs page there is a discussion with the code that is on the crash page so you can put it on any web server and still do this procedure.
3. Once it crashed I went to cmd (comand prompt) and navigated to the folder that had the adb package I downloaded and decompressed earlier. I suggest putting this folder on your desktop for easy use. I gave the command
adb connect yournookip:5555 please note that the nookdevs instructions are not specific in that you NEED the :5555 after the IP. If it doesn't connect, keep crashing the browser by going to that page until it connect.
4. extracted the init.rc file with the command
adb pull /init.rc then edited as per the instructions on nookdevs
5. Now here is where things are different. I tried to push the ratc.bin file and while that seemed to work the commands after it didn't. It would keep saying the file wasn't there. I was cut and pasting the commands direct from the website so I don't think that was the issue. So what I did was grab the bat file at www.mobileread.com/forums/showthread.php?t=121655&page=2 by Jackr and edit it slightly removing the bit about location of adb and placed the bat in the same folder as adb on my desktop and ran it.
6. This actually worked and the bat prompted me to crash the browser again. I kept trying it took a while but as soon as I did it pushed the modifyed init.rc to the nook. The another reason why I think the bat/script is important as my nook totally froze a second after I crashed it. I think that if I was trying to paste that command manually after connecting I would still be trying lol.
7. After reboot I was fully rooted and I installed a bunch of apps from nookdevs using adb. Just make sure the apk (app file) is in the same directory as adb and use the command install nameofapp.apk
8. If you want to use nookmarket app to install files by itself then you need to:
adb connect nookIP:5555
adb shell
then type this after the #
/system/xbin/sqlite3 /data/data/com.android.providers.settings/databases/settings.db "update secure set value=1 where name='install_non_market_apps'"
It will allow nookmarket to install apps on the fly over the net. If you ever want to turn it back off just change the value=1 to value=0 in the above command. Of course you can always use adb, but it can be handy.
Of all the apps I would definitely suggest Nooklibary and wifilocker along with Nooksync. There are several other good nook apps such as trook. Oh I should also mention that Nook Browser still works fine. I think using the batfile/script helped with that situation.
I hope this helps someone who is thinking of taking the plunge (and trying to find out HOW). I wouldn't have bothered if B&N actually continued to update the Nook Classic and add the features that we BEGGED for (and are in NookLibrary). Instead of spending time adding things we didn't like games.
I've tried a thousand times, but always get "failed to copy 'init.rc' to '//init.rc': Permission denied" so RATC must not be working. And I'm on mac, so no bat. Any ideas?
lolbutts said:
I've tried a thousand times, but always get "failed to copy 'init.rc' to '//init.rc': Permission denied" so RATC must not be working. And I'm on mac, so no bat. Any ideas?
Click to expand...
Click to collapse
I would suggest looking at the bat, and creating the equivalent in apple script. If I remember right Mac's still have that option. Another option would be to run say WinXP in emulation (with virtual box for example) and do it that way.
How to root the original Nook tablet (model number: BNRZ100)
dob43 said:
Yessssssssssssssss! I finally hacked my Nook Classic (Nook First Edition called by some)! I followed most of the instructions at http://nookdevs.com/Rooting_B&N_revision_1.4_to_1.7_on_any_hardware
Click to expand...
Click to collapse
Okay, since nookdevs.com has apparently been down for sometime now, I was checking out the mobileread.com link that was shared above and found out the info that I have been searching for to find out how to root the Nook. Be forewarned that I have not tried this yet, but I am about to, and afterwards I will post the results, I am just posting it as sort-of a guide for myself and anyone interested at this point. I will edit this post accordingly once I am successfully rooted.. Please see below for links / details.
Disclaimer: I am not responsible for any damage that is done by you to your Nook, either physically or otherwise. I am just showing you what I have researched and if you choose to follow these directions it is at your own risk.
Which Nook Device Do You Have?
click here to find out:
http://glyde.com/glydecast/how-to/which-nook-do-you-have/
Remember, this is for the first generation only (model number: BNRZ100)
Here is a visual aid that will help you find the SD card that you need to look for once you get the Nook opened up (yes, you will need to open your Nook and access the motherboard):
http://www.wired.com/2009/12/nook-torn-open-hacked-and-rooted/
How to open the Nook up:
https://www.youtube.com/watch?v=GEDqiNiQFHk
Hint: you don't need to take to front panel / bezel off, just the back section because all we need is access to the motherboard to be able to remove the internal SD card, which contains the file that we will be editing.
Finally, the info that you need to root the device (also posted below the link for quick reference, and just in case the link gets broken):
http://www.mobileread.com/forums/showthread.php?t=128210
How to root the Nook, after you figute out how to open it up:
Just you need a microSD Card reader + Linux (any linux ) !
just you should remove the System file MicroSD ( which is inside the Nook )
put it in your PC , change the "init" file with Any txt editor !
just find "service adbd /sbin/adbd" and change the "disable" to "enable" ...
you are done !
Wow I had no idea that Nookdevs went down. Thankfully I did archive all the information on that page. While the method you mentioned is great, and the best, only the earliest nook classic's had removable system SD cards. After the first batch they were soldered chips instead.
With that in mind I am posting what was contained in the link I posted before on NookDevs since it is not available on the internet archive.
------------
This method of rooting is known to work on B&N firmware revisions 1.4-1.7, on all hardware versions. Unlike the other rooting methods, this one involves an element of luck -- it takes advantage of a memory-corrupting bug in the web browser, and its success depends on the current contents of the memory which depends on more variables than we can control. As such, the method requires a little bit of (or more) patience. Warning: After this root is completed, the web browser will be irreversibly damaged.
Contents
1 Preparation
2 Enable adbd on the Nook
3 Pull and modify /init.rc
4 Getting root access
4.1 Keeping root access
5 Your rooted Nook
6 Notes
Preparation
Install Google's Android platform tools from developerdotandroiddotcom. These include many useful utilities, such as the ADB control software.
Open up a terminal to use ADB
Open a command prompt
Navigate to the directory that you installed, then go into the platform-tools subdirectory. This is where the adb executable lives.
Connect your nook to the same WiFi that your computer is on. You need direct (non-firewalled) access to the Nook's IP address to connect via ADB.
Find your Nook's IP address (How to find our your nook's IP address)
Write it down somewhere.
Enable adbd on the Nook
This is the luck portion of the root. adbd is the other half of ADB: ADB runs on your computer, and tries to connect with adbd on the nook. Once connected, you can issue commands, shuffle files, and install applications. Our final goal is to be able to start and stop adbd at will[1].
Open the Nook's web browser and navigate to the web site nookadb.suspended-chord.info. You may want to bookmark the page for a quicker access.
When you load this web page, the browser will crash. (It may automatically reload itself a few times first.) After it crashes, it might enable adbd.
Go back to the command prompt on your computer, and type:
adb connect <nook's IP>
One of two things will happen:
You will get the message unable to connect to <ip address>:5555.
In this case, restart your web browser and load the web page again (from the history or the bookmark). You may have to do this a dozen times or more, so keep at it!
You will get the message connected to <ip address>:5555.
Success!
At this point you have (temporarily) access the nook via ADB, can now enter commands on your PC for the Nook, and can move files back and forth. If you reboot the nook, adbd (the nook companion to ADB) will not be running.
Pull and modify /init.rc
If this isn't your first time through, and you have a modified copy of init.rc, skip this step.
Now that you can connect into the Nook, you will want to pull and edit the /init.rc file. This file is run when the nook turns on, and includes an option to enable adbd (disabled by default). Download the file to your PC with:
adb pull /init.rc
Open this file with Notepad (or a different plain text editor), and find the part the lines:
service adbd /sbin/adbd
disabled
Change 'disabled' to 'enabled' and save the file.
Getting root access
You got the web browser to launch adbd, but you only have the privilege level of the web browser's user - system. To install software and to start adbd when the Nook reboots, you need root access. Rage Against the Cage will give you root access. Next, you'll restart adbd, and push the modified init.rc back to the nook. After that, reboot the nook and you're done!
Download [ratc.zip].
Extract it to the same directory that adb is stored in, then go back to the command prompt:
adb push ratc.bin /sqlite_stmt_journals
adb shell
$ cd /sqlite_stmt_journals
$ /system/bin/chmod 777 ./ratc.bin
$ ./ratc.bin
(several lines of output follow -- don't do anything, a few seconds later adb will disconnect you.)
Keeping root access
If everything went well, you should have root access on the Nook. However, the Nook is now relatively unstable and may stop working at any point, so work quickly!
The nook may crash - just reboot, then restart the process from scratch. (Remember, you don't need to pull init.rc again.)
First, you need to stop your PC's ADB server. It still thinks that it's connected to the nook.
adb kill-server
Second, you need to re-establish the connection with adbd on the nook and then push init.rc file. You can do this by typing these commands[2]:
adb connect <nook IP>
adb push init.rc /
Perform the browser crash procedure again. After each attempt, check if the computer successfully transferred init.rc. If it did, you're done!
If the nook crashes before the transfer completes (so you are not able to connect to your nook), go back to "Enabling adbd on the Nook". You can skip "Pull and modify /init.rc", but do the other steps.
If the adb push gives a permission denied error, redo the "Getting root access", and try again. You may have to do this quite a few times until the whole process succeeds.
Your rooted Nook
Assuming everything worked, you now have a rooted Nook with adbd running on reboot, with root access. You should be able to establish the connection with adbd on the nook without jumping through any other hoops.
What's next? Browse the applications, and install to your heart's content.
Suggestions:
Mynook.ru Launcher A polished replacement launcher. You must replace the launcher to access additional applications with the nook.
Trook A RSS feed reader for the nook, and much more! It can install applications, too. Just go into the nookdevs feed.
NookLibrary A replacement library for the nook. If unifies sideloaded books with Barnes & Noble content, and offers other improvements.
NookMarket A program that allows you to easily install everything on nookdevs. Trook offers more functionality (imho)
Games There are a few games on the applications page.
Notes
↑ There's also a Python script to automate the process: root-nook-eink.tar.xz (Updated Jun 6 , 2011)
↑ You may want to run a script that automatically issues the following commands, reducing the chances of the nook crashing before init.rc has been pushed to it. In this case, extract this [batch file] to the same directory as ADB. Run it by typing:
push.bat
It will prompt you for your nook's IP address, then try connecting. Every few seconds, ADB will complain that it can't connect to the nook. Let's fix that.
------------------------------------------------
The above is from Nookdevs.com and I did not write it I am only posting it here as the site has went down.
I am also posting the html file that is needed to do this (although here it is in txt format). If the the site listed above ever dies you can put this on a website somewhere to use it. And the ratc.bin file needed.
And finally I am adding the apps that make rooting the nook classic worth while. The improved library definitely. Which btw are two parts, the library app and the nooksync which enables you to download from B&N directly. Otherwise you need to use the normal nook library app to download then you can read with the nookdev version. I am not sure which version of the library works best, been a while since I installed it so I included both.
Also wifilocker is great to turn wifi on/off not to mention lock it and keep the nook from going to sleep while you are connected to adb. I definitely suggest installing that as well. The others are handy. Trook can connect to calibre and download books from your desktop. The nook browser is a improved web browser for nook classic, although I never really bothered with it.
Nook notes is good for quick little notes when you don't have any other device handy. Txt reader reads txt files, not the best but it is handy. Personally I just make epubs of anything with calibre. But if you don't want to bother making a epub first, this is handy.
Hope this helps someone!
I downloaded files and rat.bin has malware in it.
I also have hard time understanding the ones that are explained above. Is there any easier way to do it? Does anybody have a good tutorial video or "fool-proof" instruction on this? I have Nook classic wifi version.
I would like to read kindle books on nook as well as the nook books. Is this even possible on this model?
Thanks for the help
kidollt said:
I downloaded files and rat.bin has malware in it.
I also have hard time understanding the ones that are explained above. Is there any easier way to do it? Does anybody have a good tutorial video or "fool-proof" instruction on this? I have Nook classic wifi version.
I would like to read kindle books on nook as well as the nook books. Is this even possible on this model?
Thanks for the help
Click to expand...
Click to collapse
Er of course rat.bin would be flagged as malware, because technically it is. You are hacking a system that is designed not to let you in. But in this case all rat.bin will do is let you in so you can get root of your own device, nothing else. No back doors for anyone else or making your device do odd things.
The problem you are having is not using rat.bin, without that you might as well not try. I also only managed to do it with a BAT file so that it would keep trying to push the init.rc RIGHT AFTER the rat.bin was used. Generally you can't type fast enough to do the push. The window of opportunity is very very small.
This does work but is tricky as the window of opportunity is very small. I tried for hours trying to get it to work, then I used the BAT file to make the push automatic and on the second try it worked. Rooting the Nook Classic is the toughest device to root that B&N made. If you have one of the really early models that has a removable internal SD card then you can pull that, made modifications (install a old version of the ROM, make a modification to init.rc), and reinstall the SD card. I forget the serial numbers of the models that this worked with, but I do know it was the first batch of Nooks B&N made. If you got yours after the first Christmas, then it is likely it doesn't have a internal SD card that you can remove. Later on they soldered them to the board.
As for reading kindle books, no. There isn't a mobi reading app that I have found, let alone kindle books with DRM. The better bet is to use Calibre calibre-ebook.com to convert your kindle books to epub. But they can't be encrypted/DRM. If they are, then you have to remove that. There are scripts for Calibre that can do it for nook and kindle. I use calibre to convert my mobi/kindle books to epub then side load them. Another benefit of rooting a nook classic, you can then browse and download wireless from your calibre library with the took app. Although I never bothered and just did the transfers via USB.
Hi!
I would like to ask for help in this case:
I followed all the instructions here, however for some reasons I wanted to install this app first using the command "adb push Home.apk /system/app" pushing the app found here: Github
Now it turns on/off, shows "Home", batter and time at the top bar, but everything else is black both the Eink screen and the touchscreen as well.
It does not connect to wifi automatically so I can't connect via ADB to switch back to the original Home apk
Please help me, what should I do?
Is 1.7 software not rootable?
I can't get adb to come on, no matter how many browser crashes I do. Even wrote a script for it:
@echo off & setlocal
set IP=192.168.0.119
set loopcount=0
set s
:loop
set /a loopcount=loopcount+1
echo Connecting %loopcount% time...
adb connect %IP% | find /i "connected to" > %s
if errorlevel 1 (
echo Not successful + %ERRORLEVEL% + %s%
goto loop
) else (
echo Successful + %ERRORLEVEL% + %s%
adb shell
goto exitloop
)
:exitloop
pause
Click to expand...
Click to collapse
Is OTA rooting (by redirect on sync.barnesandnoble.com) not possible any longer as well?
Sorry for the late response, for some reason the email telling me there was a post here just arrived TODAY lol.
It should be, I did it with 1.7. The script I have I modded a little from another one I found online here is mine:
Code:
@echo off
echo The website hack seems to work on the round right after it has an instant crash.
echo.
adb kill-server
adb start-server
set /p ip=Enter the IP here.
:CON
cls
echo Crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto INT
echo.
goto CON
:INT
if exist ratc.bin (set f1=1) else (set f1=0)
if exist init.rc (set f2=1) else (set f2=0)
if %f1%==%f2% (if %f1%==1 (goto RTT) else (goto 2fi)) else (goto 2fi)
:2fi
if %f1%==0 (echo "The ratc.bin file is not in the %cd% directory.") else (echo Ratc.bin file present.)
echo.
if %f2%==0 (echo "The init.rc file has not been pulled from the device to the %cd% directory, pulling now.") else (echo Init.rc file present.)
if %f2%==0 adb pull /init.rc
echo.
echo Please add the required files and restart this batch. If init.rc was just pulled, you will need to modify the file.
cmd
:RTT
adb push ratc.bin /sqlite_stmt_journals
adb shell cd /sqlite_stmt_journals
adb shell /system/bin/chmod 0777 /sqlite_stmt_journals/ratc.bin
adb shell /sqlite_stmt_journals/ratc.bin
adb kill-server
adb start-server
goto CO2
:CO2
cls
echo Re-crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto PSH
echo.
goto CO2
:PSH
adb push init.rc /
adb shell reboot
echo.
echo Congrats! The device is now rooted.
echo.
cmd
It is RANDOM on the browser crashes. Sometimes it happens fast, another time it look me a hour or two to get a good crash and root the nook. Also if it doesn't seem to be doing it for a long time, try rebooting the nook (hold down the power until the screen blanks then press the button again to restart it). In my opinion, this is the toughest Nook to root, but definitely worth it. Especially now that B&N ended support some time ago. Also make sure the ADB, this script, and the ratc.bin is in the same folder. I used a folder on the desktop as it made it much easier/faster to get to. Also after you get the init.rc and modded, that should be in the same folder as well.
As for OTA rooting, I have no idea if it will work or not. I never used that method. But if it depended on any sort of connection from B&N, I doubt it will work now since they have abandoned the Nook classic.
If you need any of the nook apps that were on the nook developer site let me know. I downloaded all the apps before the site went down.
dob43 said:
Sorry for the late response, for some reason the email telling me there was a post here just arrived TODAY lol.
It should be, I did it with 1.7. The script I have I modded a little from another one I found online here is mine:
Code:
@echo off
echo The website hack seems to work on the round right after it has an instant crash.
echo.
adb kill-server
adb start-server
set /p ip=Enter the IP here.
:CON
cls
echo Crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto INT
echo.
goto CON
:INT
if exist ratc.bin (set f1=1) else (set f1=0)
if exist init.rc (set f2=1) else (set f2=0)
if %f1%==%f2% (if %f1%==1 (goto RTT) else (goto 2fi)) else (goto 2fi)
:2fi
if %f1%==0 (echo "The ratc.bin file is not in the %cd% directory.") else (echo Ratc.bin file present.)
echo.
if %f2%==0 (echo "The init.rc file has not been pulled from the device to the %cd% directory, pulling now.") else (echo Init.rc file present.)
if %f2%==0 adb pull /init.rc
echo.
echo Please add the required files and restart this batch. If init.rc was just pulled, you will need to modify the file.
cmd
:RTT
adb push ratc.bin /sqlite_stmt_journals
adb shell cd /sqlite_stmt_journals
adb shell /system/bin/chmod 0777 /sqlite_stmt_journals/ratc.bin
adb shell /sqlite_stmt_journals/ratc.bin
adb kill-server
adb start-server
goto CO2
:CO2
cls
echo Re-crash the browser.
echo.
adb connect %ip%
for /f "tokens=2" %%A in ('adb devices') Do (Set dev=%%A)
if %dev%==device goto PSH
echo.
goto CO2
:PSH
adb push init.rc /
adb shell reboot
echo.
echo Congrats! The device is now rooted.
echo.
cmd
It is RANDOM on the browser crashes. Sometimes it happens fast, another time it look me a hour or two to get a good crash and root the nook. Also if it doesn't seem to be doing it for a long time, try rebooting the nook (hold down the power until the screen blanks then press the button again to restart it). In my opinion, this is the toughest Nook to root, but definitely worth it. Especially now that B&N ended support some time ago. Also make sure the ADB, this script, and the ratc.bin is in the same folder. I used a folder on the desktop as it made it much easier/faster to get to. Also after you get the init.rc and modded, that should be in the same folder as well.
As for OTA rooting, I have no idea if it will work or not. I never used that method. But if it depended on any sort of connection from B&N, I doubt it will work now since they have abandoned the Nook classic.
If you need any of the nook apps that were on the nook developer site let me know. I downloaded all the apps before the site went down.
Click to expand...
Click to collapse
Does this still work? I recently dug up my old nook 1st edition, I tried the website and it didn't crash my browser, it just sat there forever loading.. I looked at the site, now it's using TLS 1.3, but old nook 1st edition is stuck with TLS 1.2... I tried for many hours just couldn't "crash" the web browser at all...
I have found a way to remove ads on 5.1.1, it is exactly the same way as 5.0.1 except you NEED root for it to work.
Type in the following commands in a command prompt. Be sure USB debugging is on and it is securely connected to your computer. Although you do type reboot as the last command, the tablet turns off, just press the power button . This was successful on two of my tablets.
Code:
adb shell
su
At this point grant superuser access from the tablet
Code:
pm hide com.amazon.kindle.kso
exit
reboot
In theory this should work from a terminal emulator straight on your tablet but I have not tried it out
EDIT:
I should have explained the process better as some people are getting confused.
1. Make sure you have the correct drivers and USB debugging turned on your tablet.
2. Download this one click tool to gain root access if you have not done so already. Make sure to disable OTA updates from the tool as well (not necessary for removing ads but will be useful in the future).
3. Open a command window on your computer and type the commands above. If you have root you should get a
Code:
#
symbol after typing the su command.
Hello, it's my first post here so I apologize if the question is basic - I went thru all of the steps in other fourms last night and got Google Play to install just fine and even temporarily I appear to get the lock ads to remove but at best that doesn't seem to last past a reboot. After some further reading I found that unfortunately the kindle did a OTA update to 5.1.1 and that explains the reason I've been unable to permanently get rid of those lock ads.
I read your post, but I'm unclear on what I need to do to get root access (I mean without completely rooting the thing) I ran ADB from a windows command line, but I get a "not found" command when i type in SU..here's what it looks like (I'm putting my typing in bold, and the auto generated command line stuf in regular):
========================================
c:\amazon>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127:[email protected]:/ $
=====================================
Since I've only done the automated scrip that is supposed to allow google play and remove ads, I didn't really expect to have root access, but I'm hoping there's some way I can get this to work without trying to fully root the kindle. If I have to go that route I might as well get rid of the entire Kindle OS... I don't actually want to do that, as I use amazon prime so a lot of the default junk that comes with this kindle is useful.
Big-T said:
Hello, it's my first post here so I apologize if the question is basic - I went thru all of the steps in other fourms last night and got Google Play to install just fine and even temporarily I appear to get the lock ads to remove but at best that doesn't seem to last past a reboot. After some further reading I found that unfortunately the kindle did a OTA update to 5.1.1 and that explains the reason I've been unable to permanently get rid of those lock ads.
I read your post, but I'm unclear on what I need to do to get root access (I mean without completely rooting the thing) I ran ADB from a windows command line, but I get a "not found" command when i type in SU..here's what it looks like (I'm putting my typing in bold, and the auto generated command line stuf in regular):
========================================
c:\amazon>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127:[email protected]:/ $
=====================================
Since I've only done the automated scrip that is supposed to allow google play and remove ads, I didn't really expect to have root access, but I'm hoping there's some way I can get this to work without trying to fully root the kindle. If I have to go that route I might as well get rid of the entire Kindle OS... I don't actually want to do that, as I use amazon prime so a lot of the
default junk that comes with this kindle is useful.
Click to expand...
Click to collapse
Yeah it could have been better explained, they meant that process works if your tablet is rooted.
You won't get root commands to work in shell like that if it isn't rooted. Like it says the su file isn't there.
A lot changed yesterday with respect to 5.1.1 and root.
So you could use the temporary root found yesterday to gain access. Should be able to disable it from there. (First two code boxes there show the temp root access and the resulting prompt, the third lets you make it permanent). Though not sure why rooting it is tantamount to removing the entire OS tbh anyway.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Pond-life said:
Yeah it could have been better explained, they meant that process works if your tablet is rooted.
You won't get root commands to work in shell like that if it isn't rooted. Like it says the su file isn't there.
A lot changed yesterday with respect to 5.1.1 and root.
So you could use the temporary root found yesterday to gain access. Should be able to disable it from there. (First two code boxes there show the temp root access and the resulting prompt, the third lets you make it permanent). Though not sure why rooting it is tantamount to removing the entire OS tbh anyway.
http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362
Click to expand...
Click to collapse
Thank you! It appears I finally got the ads cleared permanently although I had a few hiccups along the way. I'm going to try to step-by-step this for anyone else that may have problem like I did (First andriod device, first time messing with one)
1) Got my kindle yesterday and it did an automatic over the air update to 5.1.1 - Found instructions for installing the google play store and removing ads in this excellent thread http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
2) Downloaded "Amazon-Fire-5th-Gen-Install-Play-Store.zip" file from rootjunkysdl.com but had some problems getting my device to recognize correctly. I found the only drivers to work on two seperate computers were from the amazon website https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing#Introduction
3) After I got the drivers to install I ran the "1-Install-Play-Store.bat" file from step #1. The batch file guided me thru everything and the Google Playstore worked just fine. At first I thought I got rid of the lock screen ads as well, but after my first reboot the ads came back.
4) This thread pointed out that with the new 5.1.1 updated you had to have root access enabled. I tried to do so, but the commands weren't working. The problem was, I was missing a critical step that wasn't explicitly stated in the other threads YOU MUST INSTALL THE ROOT_FIRE.ZIP and point your command prompt window to this extracted folder...even though the zip file in step#1 has an adb.exe it's missing other files to get you root acees
http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen
5) After unpacking and running the commands as provided, the ads are gone. I'm attaching a link to a screenshot of my command window so folks can see what they should be typing in:
https://www.dropbox.com/s/icyyzr14limkosu/Capture.JPG?dl=0
Big-T said:
Thank you! It appears I finally got the ads cleared permanently although I had a few hiccups along the way. I'm going to try to step-by-step this for anyone else that may have problem like I did (First andriod device, first time messing with one)
1) Got my kindle yesterday and it did an automatic over the air update to 5.1.1 - Found instructions for installing the google play store and removing ads in this excellent thread http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
2) Downloaded "Amazon-Fire-5th-Gen-Install-Play-Store.zip" file from rootjunkysdl.com but had some problems getting my device to recognize correctly. I found the only drivers to work on two seperate computers were from the amazon website https://developer.amazon.com/public/resources/development-tools/ide-tools/tech-docs/05-setting-up-your-kindle-fire-tablet-for-testing#Introduction
3) After I got the drivers to install I ran the "1-Install-Play-Store.bat" file from step #1. The batch file guided me thru everything and the Google Playstore worked just fine. At first I thought I got rid of the lock screen ads as well, but after my first reboot the ads came back.
4) This thread pointed out that with the new 5.1.1 updated you had to have root access enabled. I tried to do so, but the commands weren't working. The problem was, I was missing a critical step that wasn't explicitly stated in the other threads YOU MUST INSTALL THE ROOT_FIRE.ZIP and point your command prompt window to this extracted folder...even though the zip file in step#1 has an adb.exe it's missing other files to get you root acees
http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen
5) After unpacking and running the commands as provided, the ads are gone. I'm attaching a link to a screenshot of my command window so folks can see what they should be typing in:
https://www.dropbox.com/s/icyyzr14limkosu/Capture.JPG?dl=0
Click to expand...
Click to collapse
Think it might depend when you downloaded the Amazon-Fire-5th-Gen-Install-Play-Store.zip, the zip has been around for some time and he updated it several times last night and somewhat confusingly kept the same name for it and the batch file inside.
The current zip and a few other versions last night has the root riles in the "files" directory that the batch uses them from there. Even then the order of the commands isn't ideal I don't think as the block the ads one comes in the install google play one before the root install which it relies on it.
I think if adb shell pm hide com.amazon.kindle.kso was moved to the blocking 5.1.1 OTA section and updated the same way those OTA hides were to
adb shell su -c "pm disable com.amazon.kindle.kso"
so that section would be
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
adb shell su -c "pm disable com.amazon.kindle.kso"
5? You know everything failed in that pic right?
Pond-life said:
5? You know everything failed in that pic right?
Click to expand...
Click to collapse
Yeah, lol! [laughing with not at] It looks like the commands are failing because he's already in su! Something weird happened at the line:
adb wait-for-device && adb shell
. . . and he went into su (#), so subsequent shell and su fail, but the "pm hide" works! But then the one "exit" takes him out, as though he actually was only in shell. This is really strange.
Worked perfectly! Thanks
I was having issues with the supertool and even another manual entry way of blocking ads, but this seems to have worked.
Thank you!
If you're rooted, why not use an app instead of doing this via adb.
S6 EDGE TMO
dEris said:
If you're rooted, why not use an app instead of doing this via adb.
S6 EDGE TMO
Click to expand...
Click to collapse
Amazon lockscreen ads are not the same as google ads. The lockscreen ads don't go away with ad blockers. That was the first thing I tried after root. Of course, someone could just make an app that runs this script specifically for this device but I find this way pretty simple
phonehunter59 said:
Amazon lockscreen ads are not the same as google ads. The lockscreen ads don't go away with ad blockers. That was the first thing I tried after root. Of course, someone could just make an app that runs this script specifically for this device but I find this way pretty simple
Click to expand...
Click to collapse
You can disable apps with app freezer apps in the play store. Therefore, instead of using adb to disable apps, use an app. App app app lol
S6 EDGE TMO
UPDATE: November 26.
It also works with Tmobile and Verizon (unlocked phone)
Running on latest Pie 9.0 and November update, and magisk beta 17. 3
Original.
you need to root the phone. Or else it does not work.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
@filthysanches did a detailed step by step for newbies down below.
Thanks.
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
beezar said:
I can confirm this method works. Well, instead of editing build.prop directly, I used the Magisk module Tethering Enabler which does the same build.prop modification but will allow it to pass safety net checks, then used the adb command above. Thanks for posting the commands!
Click to expand...
Click to collapse
Do you have a tutorial link for this, I've followed at least 3 of them I've found online and I can't get Magisk modules to install. Says that /system can't be mounted.
eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
does this work the same way using android sdk?
Step 1: open command window
Step 2: type "cd (folder location of the platform-tools sdk)"
step 3: type "settings put global tether_dun_required 0"
step 4 :type "reboot"
I'm going to try this when I get home, just wanted to confirm if this method makes sense.
Step 2.5 type adb devices. If you see your device then step 2.6. type adb shell
Boom! Works now. Thanks ya'll.
I did everything with adb... I think modules with magisk are tricky sometimes
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
uofirob said:
Am I getting the error on startup about something being wrong with my system because I didn't run the settings put global tether_dun_required 0 command? (I only installed the Magisk Module)
Click to expand...
Click to collapse
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!
cedargreen said:
If Magisk is showing installed you are you able to download root explorer from play store. If so then open the system folder in root explorer and then drill down to build.prop. Click on it and choose to open with text editor. Scroll way down to the bottom and on the first empty line put
net.tethering.noprovisioning=true
Save and exit.
Reboot.
Should have native tethering now. ADB shell is not needed. I do this on Verizon. LMK if there are extra steps required for other carriers.
Thanks!!
Click to expand...
Click to collapse
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
uofirob said:
Magisk works, tethering works with the module. Only issue I have is when I startup I get a popup that says "There's an internal problem with your device. Contact your manufacturer for details." but nothing seems to be really wrong with the phone... It still works, makes calls and can tether... so it's just an annoyance. I've seen some mentions of that system error from other phones, and it was because the vendor buildprops doesn't match the system buildprops. I'm wondering if the extra command that was mentioned would fix this. Has anyone else seen this error?
Click to expand...
Click to collapse
Had that too on wife's phone that was rma'd due to constant boot loops. Only thing I have done differently is to delete the net.tethering.noprovisioning=true as well as going into magisk and uninstalling back to normal boot img, prior to taking the Nov OTA. Once that was done I went into twrp and reflashed the magisk zip then redid the build.prop.
My noob understanding of that popup is that something in system has been modified (build.prop?) Causing the notification.
I rma'd before I was able to read about it so couldn't test to see if I could complete uninstall then back to factory then update everything and finally magisk, edit build.prop.
eloko said:
you need to root the phone.
it works on November update 0.25 and 8.0
1. ) buildprop editor add this line
> net.tethering.noprovisioning=true
2.) Open adb shell.
3.) Type following command
>settings put global tether_dun_required 0
>reboot
AND THATS IT.
Click to expand...
Click to collapse
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
I know this is mentioned for Sprint but on stock 025, Nov sec, rooted with Magisk, the above did not work on MetroPCS
access unravel
As a side note, installing a root access "app hider" will reverse the second part of this process breaking connectivity. Not a huge deal but worth noting, as I'm not sure what root access apps will also reverse this.
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
filthysanches said:
For the simple minded such as myself. Unlocking and unblocking wi-fi tethering / Hotspot, tested on Oreo
buildprop editor add this line
Code:
net.tethering.noprovisioning=true
Also BuildProp editor makes this process fairly easy with the permissions
Open adb shell and type
Code:
adb devices
wait for the daemon to successfully start. make sure your device is recognized.
Type
Code:
adb shell
Type
Code:
settings put global tether_dun_required 0
Type
Code:
reboot
Ya'll made this super simple after allot of searching and kind direction
Click to expand...
Click to collapse
Worked perfect. Thank you.
I am looking for non root solution but so far I can't find it
Got it work
https://forum.xda-developers.com/pixel-2-xl/how-to/root-sprint-hotspot-t3738118
Thank you for breaking this down and explaining it. I performed the first part with the buildprop editor using ES File Explorer with root permissions. It still didn't work so I had to wait till I was done with work to perform the second process with ADB and all is working now so happy. I just got my pixel 2XL and wasn't sure if this would work or not.
Thank you so much too whoever solved this.
rockingondrums said:
Has anyone confirmed this works with T-Mobile by checking their tether allowance after testing tethering?
Click to expand...
Click to collapse
did anyone ever confirm this?
Can anyone confirm if this works on pie? Carrier has my tethering disabled.
Hi all, I came across this root tutorial in a post from last year and was hoping to get some feedback on it. Risks involved? Potential for brick or boot loop? The tutorial uses supersu and I'm aware that it may now have security risks. This radio will never be online so it's not a concern. The tutorial was posted in a 8227L thread so it was supposedly done on this model but there wasn't much follow up.
According to AIDA64 my device specs are:
Model: alps 8227L demo
4x ARM Cortex A7 @ 1118mhz
32 bit ARMv7
CPU Revision: r0p3
1GB RAM
16GB ROM
Android Version: 6.0 Marshmallow
Kernel: 3.18.22
API Level 23
Android Security Patch Level: 2017-11-05
Build ID: YT9218_00002_V001
##############TUTORIAL###############
ROOT!
Root has to be done through ADB.
Attention! Incorrect actions can lead to a bootloop (endless loading) of the radio. To fix it, you will need a flashing and, as a result, a complete erase of all data; so, proceed at your own risk!
Requirements: P.C. (I prefer my laptop) and your head unit must be able to connect to the same wifi as the PC (I used my mobile phone's hotspot for wifi and connected my laptop and headunit to it)
Download adb (platform-tools-latest-windows.zip) from here
Download SuperSU apk and SuperSU zip files from here
Extract platform-tools-latest-windows.zip to C:\adb
Extract SR5-SuperSU-v2.82-SR5-20171001224502.zip.
Open the armv7 folder
Select all files in the armv7 folder and right click, Copy
Paste the files into the c:\adb directory
In the same folder, create a notepad file and paste in the following text:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel ubject_r:system_file:s0
now save this file as "rooting.rc"
Open command prompt on your PC as administrator (in windows 10, in the "type here search" type "cmd")
type in "cd c:\adb"
Move over to the headunit and download "What is my IP address" from the google play store.
open up what is my ip address and write down your headunit's ip address (should be something like 192.168.3.4)
Go back to the play store and download "Terminal Emulator for Android"
open Terminal Emulator for Android
Go back to your pc and in the command prompt window, execute the following code:
(my adb worked without additional commands, immediately after opening the emulator)
(any sentences to the right of // means NOTE; so, don’t copy that part)
Code:
adb connect <IP devices>: 5555 // For example adb connect 192.168.3.4/10555
adb shell // Go to Shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,. // In the shell, we switch to superuser mode using the password
remount // Remount so that all further commands are immediately executed from the superuser
adb shell setenforce 0 // Further on the instruction manual from the articles
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc
get back on you headunit,
get the SuperSU apk we downloaded from before and get it installed onto your headunit. (I put mine onto my google drive and downloaded and installed from there)
open it and look for a GRANT command.
Press GRANT to allow superuser access.
NOTE: If you get a request to update the binary file, click reject
go back to your pc. we are going to Reboot your headunit with the reset command
Code:
adb shell reboot
The radio will reboot twice, don't panic.
check with root checker
You should be ROOTED!
EDIT: here is a video:
the text file should contain:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0
nismo2013 said:
the text file should contain:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0
Click to expand...
Click to collapse
it works..no need to find the ip address or use a terminal emulator..you do have to add a extra line of code..
but since your at Android 6, just use KingRoot..much easier
codecxbox said:
but since your at Android 6, just use KingRoot..much easier
Click to expand...
Click to collapse
Thanks for the reply. I used kingroot on an old samsung galaxy s4 I had years ago and it made my device run like garbage. I would prefer the adb method above. In your other comment you sad no ip or terminal emulator is needed. Then you said I do need an extra line of code. Do you mean an extraline of code in order to skip the ip and terminal em? Or the tutorial above needs one more line of code as it is?
nismo2013 said:
Thanks for the reply. I used kingroot on an old samsung galaxy s4 I had years ago and it made my device run like garbage. I would prefer the adb method above. In your other comment you sad no ip or terminal emulator is needed. Then you said I do need an extra line of code. Do you mean an extraline of code in order to skip the ip and terminal em? Or the tutorial above needs one more line of code as it is?
Click to expand...
Click to collapse
you skip the ip add line and the use of the terminal emulator..
you should use these extra lines:
adb push su /vendor/bin
chmod 0677 su /vendor/bin
btw, you have to enable OEM Bootloader unlock at the usb debugging menu..press 4 times the build number and usb debugging will be enabled..after that, connect your cable to your pc, turn off and on your head unit, you should be able to adb devices with a serial number...
I recommend you to do each step copypasting at the adb prompt and pressing enter at each one..as soon you get adb superuser enabled, youre good to go...DONT UPDATE SUPERSU IF IT TELLSVYOU THAT THE BINARY NEEDS TO BE UPDATED!
your build 9816 Im never did that one, but probably you wont need to [email protected], cuz these builds 9*** already have su built in, but there not system wide..test # at adb shell before anything, and then push your su to all partitions..
codecxbox said:
you skip the ip add line and the use of the terminal emulator..
you should use these extra lines:
adb push su /vendor/bin
chmod 0677 su /vendor/bin
btw, you have to enable OEM Bootloader unlock at the usb debugging menu..press 4 times the build number and usb debugging will be enabled..after that, connect your cable to your pc, turn off and on your head unit, you should be able to adb devices with a serial number...
I recommend you to do each step copypasting at the adb prompt and pressing enter at each one..as soon you get adb superuser enabled, youre good to go...DONT UPDATE SUPERSU IF IT TELLSVYOU THAT THE BINARY NEEDS TO BE UPDATED!
Click to expand...
Click to collapse
Thanks for the additional info. I'm still a beginner when it comes to rooting and have never done adb. The reason I wanted to use the network method is the head unit is installed in my car and I only have a desktop pc. I could borrow a laptop but its not readily available. I'd also have to buy a M to M usb cable since the otg usb on the radio is full size.
One of the first things I did was enable developer options and unlock the oem bootloader. But thanks for the heads up! I also read to not undate the super su binary. Random question.. but can magisk manager be installed on top of supersu? On magiskroot.net in the install info it says it can hide supersu root.
Can you please do an edit to the lines I enter into command prompt so I'm sure I get it right? I entered the actual ip address of the head unit. Can you please correct the formatting if it's wrong?I thought I want port 5555 but in the tut above he's using /10555. My current commands are:
Code:
adb connect 192.168.0.3/5555
adb shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount
adb shell setenforce 0
adb push su /system/xbin/su
adb push su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc
*NEXT INSTALL SUPERSU ON HEAD UNIT AND GRANT SUPER USER ACCESS - DO NOT UPDATE BINARY - FOLLOWED BY*
adb shell reboot
First, try to get your firmware, it may be full or update, doesnt matter..just in case your hu bricks..
Second, like I told you, check if superuser is already enabled..
If you only have a desktop pc, download adb lite, and decompress it to c:/adb
Get a usb to usb cable, or cut 2 usb data cables and twist or solder green to green, white to white, red to red and black to black..
I highly reccomend you to download these apks..
busybox.apk from sterikson
CX Explorer.apk or Mixplorer.apk (these you need to obtain system modifications)
Magisk doesnt play well with HU, cuz these android builds contains su watchdogs that turn off any apps that attempt to modify system files..if your goal is to install Viper4Android, then its going to be a battle but it can be done..
I just read that you have the hu installed to your car..in that case you will have to use ADB WIFI, and process everything from your phone..there is a problem, you might need to get a wifi router, cuz these hu units dont do direct wifi..in that case, you need the real ip address of your hu and adb connect hu ip address
If your goal is to install TRWP, its almost impossible..adb fastload doesnt work, its needs access to a keyboard, and as you happen to experience, these units wont recognize a usb keyboard..the way to install TRWP is forcing it through SP Tool, but you need a very specific TRWP image, most likely you never get one..but its not necessary to obtain root, no problem
Kingroot is sounding better by the minute haha. I may just try that and then use a task kill app to stop the ram sucking crap it tries loading into the backgound processes. If kingroot fails to gain access, I hope you don't mind but I'll be back with more questions on the adb wifi process. I already have a wifi router so I'm good there. The tut above does it over wifi and desktop with the files sitting in c:/adb like you said.
A few things I have discovered about this head unit which may apply to other chinese hu.. As I'm sure you know, the bluetooth stack is missing the HID profile and while I was able to pair a gamepad, I couldn't use it. The same went for bluetooth controlled led strips. The work around for a gamepad or keyboard/mouse on these HU is, get a device that is android compatible but uses a 2.4ghz dongle. I plugged it in, drivers loaded and it started working. Check out the Rii RK707 which is an all in one. $23 on gearbest. Gamepad took getting used to but I installed retroarch and the quake 3 arena port and both worked flawlessly with a gamepad. Dead Trigger also worked perfect. I just google searched for the files and then side loaded to the HU. I also put a 3 port usb splitter on the otg and everything works fine together; storage and gamepad.
I also figured out how to gain 8GB free space. If you go to settings, then storage/internal and scroll to other, I saw mine had 8GB of files. I tapped other and then browse and saw 3 folders called amap, amap8 and amapauto or something like that. These are included chinese gps map files. I deleted the folders and my device went up to having 9GB free space and it's been running fine. I was able to install a bunch of games to verify the free space is actually there. I have seen people trying to re-partition their devices and being happy to gain 2GB free. This is the way to do it. The HU also runs less laggy with the extra space.
For external storage like a usb thumbdrive, I think these units claim to supprt 32GB. I can veryify that up to 128GB works fine. I have a 128GB verbatim store n go and keep all of my mp3 and movie files there.
Hope you find some of this helpful.
codecxbox said:
First, try to get your firmware, it may be full or update, doesnt matter..just in case your hu bricks..
Second, like I told you, check if superuser is already enabled..
If you only have a desktop pc, download adb lite, and decompress it to c:/adb
Get a usb to usb cable, or cut 2 usb data cables and twist or solder green to green, white to white, red to red and black to black..
Click to expand...
Click to collapse
Good idea! I have some phone data cables with broken micro usb plugs I can cut and solder together.
How should I check if superuser is enabled? Can I install the supersu apk and try tapping GRANT? I just assumed I didn't have it because AIDA64 came back with "no root" when I ran it.
nismo2013 said:
Kingroot is sounding better by the minute haha. I may just try that and then use a task kill app to stop the ram sucking crap it tries loading into the backgound processes. If kingroot fails to gain access, I hope you don't mind but I'll be back with more questions on the adb wifi process. I already have a wifi router so I'm good there. The tut above does it over wifi and desktop with the files sitting in c:/adb like you said.
A few things I have discovered about this head unit which may apply to other chinese hu.. As I'm sure you know, the bluetooth stack is missing the HID profile and while I was able to pair a gamepad, I couldn't use it. The same went for bluetooth controlled led strips. The work around for a gamepad or keyboard/mouse on these HU is, get a device that is android compatible but uses a 2.4ghz dongle. I plugged it in, drivers loaded and it started working. Check out the Rii RK707 which is an all in one. $23 on gearbest. Gamepad took getting used to but I installed retroarch and the quake 3 arena port and both worked flawlessly with a gamepad. Dead Trigger also worked perfect. I just google searched for the files and then side loaded to the HU. I also put a 3 port usb splitter on the otg and everything works fine together; storage and gamepad.
I also figured out how to gain 8GB free space. If you go to settings, then storage/internal and scroll to other, I saw mine had 8GB of files. I tapped other and then browse and saw 3 folders called amap, amap8 and amapauto or something like that. These are included chinese gps map files. I deleted the folders and my device went up to having 9GB free space and it's been running fine. I was able to install a bunch of games to verify the free space is actually there. I have seen people trying to re-partition their devices and being happy to gain 2GB free. This is the way to do it. The HU also runs less laggy with the extra space.
For external storage like a usb thumbdrive, I think these units claim to supprt 32GB. I can veryify that up to 128GB works fine. I have a 128GB verbatim store n go and keep all of my mp3 and movie files there.
Hope you find some of this helpful.
Click to expand...
Click to collapse
Didnt know about the 2.4 dongle, thanks for the tip! I guess the dongle should translate a usb keyboard, as its supposed to be HID compliant..give it a try!
My HU didnt contain Chinese maps, but there was a load of Baidu crap I deleted, gained some 250mb..Happy with the results!
nismo2013 said:
Good idea! I have some phone data cables with broken micro usb plugs I can cut and solder together.
How should I check if superuser is enabled? Can I install the supersu apk and try tapping GRANT? I just assumed I didn't have it because AIDA64 came back with "no root" when I ran it.
Click to expand...
Click to collapse
SuperSU from Chainfire rides upon su, so if su is not properly working, SuperSu reports that theres no root..
a quick way to know if you could be a superuser is looking at the build.prop at /system..if it says ro.xxxx.userdebug instead of ro.xxxx.user, then chances are that su is installed..but you would need to give permissions to su to modify anything, thats why the chmod command..
get to c:\adb
type adb devices you should see devices and a serial number
type adb shell you should see a $ prompt, means you dont have superuser privileges
if you see a # prompt, then you do have superuser
this is my modified routine:
adb shell
su @#zxcvbnmasdfghjklqwertyuiop1234567890,.
remount
adb shell setenforce 0
adb push su /system/xbin/su
adb push su /system/bin/su
adb push su /vendor/bin/su
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/xbin/su
adb shell chmod 06755 /vendor/bin/su
adb shell /system/bin/su --install
adb push rooting.rc /system/etc/init/rooting.rc
adb shell reboot system
Reading again, you said that BT devices work, like a dongle..but at the fastboot prompt, neither HID or BT drivers get loaded, its like a safe mode boot..only way to emulate that Key Up, Key Down is opening the HU and search for a test point on the board, usually its works as a Key Down
codecxbox said:
Didnt know about the 2.4 dongle, thanks for the tip! I guess the dongle should translate a usb keyboard, as its supposed to be HID compliant..give it a try!
My HU didnt contain Chinese maps, but there was a load of Baidu crap I deleted, gained some 250mb..Happy with the results!
Click to expand...
Click to collapse
The usb keyboard and mouse also worked! I did quite a bit of research on gamepad and keyboard options once I saw 2.4ghz would work and narrowed it down to these 2. The Rii RK707 which is an all in one. It has a led keyboard and mousepad on one side, and flip it over and its a gamepad. Standard LB and RB plus incremental L and R triggers. Works well but the shape takes time to adjust to. https://www.gearbest.com/keyboards/pp_3002324601977019.html
The other which I'm still waiting to arrive is the EasySMX ESM-9110. Visually it's a copy of an xbox one controller but has nice rgby leds in the ABXY buttons. It also has programmable underside buttons like a scuf. Great reviews. https://www.aliexpress.com/item/4000574045231.html
Each are under $30 if you don't mind waiting for shipping from china. Everything else was either cheap junk or over my budget.