Related
I followed all of the instructions on this post:
forum.xda-developers.com/showthread.php?t=442480
No problems at all doing any of it.... BUT I have a G1 that had 1.6. Now it's 1.0. Everything seemed to work fine, but when I try to update with any ROM it does not seem to work... still 1.0.
When I restart it by holding the power and the home button I do not get the menu screen that all tutorials seem to have, I still get the Exclamation mark and have to hit Alt S.
Any suggestions? I have tried loading Cyanogen and 2 different JesusFreak versions. But no changes. ???
EDIT: Ok I just found this ...
to see is you are "rooted" download or use terminal app
At the $ prompt type su <enter>
should return a prompt now of
#
I downloaded the terminal app and it says permission denied when I type in su.
SO I guess it's not rooted...BUT everything I did with the instructions went off without a hitch. Did the telnet instructions with no problems....??? AHHHH!
NEW EDIT! OK I found this video "Rooting the G1 to Amon RA's Recovery " on you tube. Followed the simple instructions, everything worked great. So now I have 1.5.2, booted pressing home and power and got the menu screen for the first time ever. Tried to run an update and that menu screen is gone, I'm back to the exclamation point. And still su does not work in the terminal. And telnet only gives me a connection error now. PLEASE HELP!!!!
Ok I started over did ALL OF THIS:
If you have US-RC30/UK-RC8 or higher, you will first need to downgrade your phone to a previous version. (Skip these steps otherwise)
1. Format your phone's SD card to FAT32 mode:
* Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
* Click the notification, and then click "Mount".
* A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
1. Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
SO, it says I should have root now. I downloaded the terminal, typed in su and it says access denied. ???
Wow. I cant believe that not as single person is willing to help me on a forum about this subject.
So I started over for the 4th time. Again did everything, it all goes smoothly. But still do not have permission when I type in su to a terminal.
I loaded Amon Ra Recovery, then loaded signed killa 1.5.
It worked, I see 1.5, but when I reboot I do not get the menu, I still get the exclamation point..... I only get the menu on the first reboot after loading the Amon Ra Recovery.
PLEASE ANY HELP I'M DYING OVER HERE!!!
fellow g1 er
Theunlocker ddoott coom
For g1 Has two part video about going bqack to early version and then flashing foward to get root
It worked for me.
However you should be aware that their procedure uses something other than dangerecovery which cyanogemod requires. To use froyo 2.2 android.
I found this out AFTERFLASHING FROYO so now oi have to backtrack.
Thunlocker also links to a g1 android version with root whiicch what you flash last from the sd
card using amonra recovery.
I do however haave root. And the unlocker basic root rom worked well until I flash cyanogen mod rc3
But rc3 does still have root on my phone. It just doesn't run well because only danger recovery can partition the nand chip properly apparently and I haven't done that yet.
Furthermore be aware if you install gapps that there are two versions mdpi and hdpi and no one tells you but I think only mdpi works on g1 .
I found out after flashing hdpi myself.
Wish others would help.
We are the blind leading the blind.....
If you find something that gets you cyanogenmod worling with google apps market then please tell me how.
At least if you follow the unlocker videos you will have root.
Get it from their webpwage not you tube because the webpage has the steps written out as well.
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
UPDATED 12/23
---------------------------
1) Added automatic fixing of devicemanager.apk sql databases to prevent OTA root (thanks for the SQL tweak suggestions, Indirect)
2) Added otaban.sh script for those who are already rooted and just want to tweak the sql databases (you will need to put your device back in USB debug mode)
3) Added getroot.sh to just dump the nook back in to rooted/adb mode
INSTRUCTIONS
(Please follow these to the letter; over 500 people have downloaded this script and very few have reported issues)
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
http://goo.gl/vTNpJ
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
On the MAC
Download the nooktablet-mac-root-0.6.zip file from http://goo.gl/qyYDB
Open Terminal, and change in to the directory where the zip file was downloaded. Unzip and cd in to the directory created. EG:
Code:
[B]cd ~/Downloads
unzip nooktablet-mac-root-0.6.zip
cd nooktablet-mac-root-0.6[/B]
Start the rooting script:
Code:
[B]./go.sh[/B]
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly. Also don't connect via a USB Hub.
When the script is finished, it should say "Done. Unplug from USB now"
The Nook will reboot.
You are now rooted and the following is auto-installed for you
1) Go Launcher Ex (Rooted App Launch/Desktop)
2) Market Place (The Android "App Store")
3) Button Savior (adds tiny button on right of screen for nagivation home/back etc)
4) Home Catcher (makes 2 clicks of the Nook N bring up the new Launcher)
5) Nook Color App Menu (allows you to install sideloaded apps to the Nook home screen/Library)
6) Dolphin HD Browser (Replacement web browser)
In addition, some tweaks have been made to prevent OTA updates from working, preserving your root state.
trying this now..
thanks a lot! i spent 2 hours last night trying to get the other method working and it gave me the headache of the gods.
edit: that mediafire link is crawling for me (dl is at like .2kb/s) can anyone mirror it for others who may have similar issues?
Worked beautifully! Where can I send a donation to?
beatlesfan01 said:
Worked beautifully! Where can I send a donation to?
Click to expand...
Click to collapse
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
i can confirm this works guys
yes.. someone please start a thread and aggregate donations for some roms on this bad boy.
t-r-i-c-k said:
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
You are a good man. Thanks again for all of your help and great work. You're an invaluable asset to this community.
Sent from my BNTV250 using Tapatalk
Thanks for the tutorial. It works extremely well!
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
jdubr said:
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
Click to expand...
Click to collapse
Ah, I just looked at the script, I realized now I missed out the mkdir -p ~/.android in it, hence your issue. I will likely fix that and update the script/zip file when I get a minute.
I'm currently considering whether to make the script install busybox at the moment. I don't really need it myself, but I see other people might.
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
t-r-i-c-k said:
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
Click to expand...
Click to collapse
I totally get that. I had just gotten done side-loading tons of stuff and getting my launcher screens setup the way I wanted and then I saw your script and thought about it for a day before breaking down and wiping my NT and starting over.
It was worth it! Thanks again!
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Minor problems encountered
I followed the directions and it mostly worked. First, had the problem with the missing:
[ ! -d ~/.android ] && mkdir ~/.android
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail?
Click to expand...
Click to collapse
Sent from my BNTV250 using Tapatalk
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Click to expand...
Click to collapse
Literally type
unzip nooktkablet-mac-root-0.4.zip
cd nooktablet-mac-root-0.4
mkdir -p ~/.android
./go.sh
Sent from my BNTV250 using Tapatalk
kisstek said:
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
Click to expand...
Click to collapse
Launcher: that's what I meant.
Unplug: if you dont before you reboot it probably wants to media sync
Button savior: installs a tiny button on the right of the screen. Gets you back/home
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Sent from my BNTV250 using Tapatalk
Thanks. I found the little tiny button savior icon while trying out an ssh client. It shows up well on a black background.
And that does make it real easy to get back and forth between Android and Nook. Thanks again for making this easy and the button savior recommendation.
I may have to break down and try the Amazon store now.
t-r-i-c-k said:
Connect the Nook to the MAC. On the nook you should see "USB debugging enabled" in notifications center
On the MAC
Download the nooktablet-mac-root-0.4.zip file
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly.
On the NOOK
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
Click to expand...
Click to collapse
Hey! Noob here. Thanks so much for this! Just have a few questions...is this a permanent fix? I currently have the amazon appstore, but not android, so is this going to be set up the same way (i.e. have to click search and then go launcher to find the apps)?
When I connect to my mac, the usb debugging prompt will come up right away (like the screen for file xfer normally does)?
After unzipping, are those instructions to enter into the mac's terminal command prompt? Sorry, that's where u lost me! Is "cd" short for something? Thanks again for your help. Just want to make sure I do this right the first time. I think swype is the first thing I will install. Hating this keyboard!!!
First, I want to openly thank t-r-i-c-k for this. Even with little to no knowledge of this kind of stuff, after futzing with terminal for a while I got it to work in two tries. Finally, freedom from another lock-in service/device. But I am having a little glitch that I don't understand.
It's intermittent, but now and then I'm getting a crash on the launcher. It happens when trying to adjust settings/preferences. No big deal as it comes right back, and maybe its the app itself. Anyone else facing this?
t-r-i-c-k said:
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Click to expand...
Click to collapse
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
jdubr said:
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
Click to expand...
Click to collapse
ADW seemed slow to me. I just switched to Launcher Ex anf thsts is working nicely. No crashes yes.
Sent from my BNTV250 using Tapatalk
All, I have found a solution to get this P-WAL-107-ELC-02 unlocked and usable!
Original post:
I acquired a used Outcome Health (Contextmedia) Wallboard. There have been other posts previously about unlocking the 10 and 13inch tablets, but the steps and procedures used did not work with this wallboard.
The model number is P-WAL-107-ELC-02, and is similar to the item found here: https:// fccid.io/ 2AI6X-PWALELC
It is running on Android 4.4.4
I can open the "secret" configuration menu built into the app, but all the functions are password protected. I've had no success accessing the default android settings menu either. If you close the app, it launches again immediately, and the status bar seems to be locked down so that it can't be expanded.
EDIT: I've tried using a USB keyboard, and used the settings hotkey but no luck with this either. Using the home button pushes a message at the bottom of the screen "Override Launch." I also tried generic passwords in the various menus, but nothing has worked so far.
Any suggestions or experience with these items is greatly appreciated, thank you!
Click to expand...
Click to collapse
Disclaimer:
This is a collection of the methods that worked successfully in my case. I am assuming anyone using this has an understanding of the use of ADB and shell commands. If not, please do your research to better understand the use of the command line, otherwise you may cause more damage then actual repair. Perform the actions followed at your own risk.
Rebooting into safe mode and removing contextmedia applications:
With the help of information in this thread: https://forum.xda-developers.com/android/help/android-4-4-4-context-media-10-tablet-t3670769 I got it working.
With the wallboard connected to the pc, I restarted the device and repeatedly pressed the power button until it finished booting and it started in safe mode! I was able to open the android settings, uninstall the contextmedia app and the zygote app, access dev options and enable debugging.
Connected to the PC and in debugging mode run the following to remove the synop and the remainder of the contextmedia applications.
adb reboot root //Worked in my case, confirmed root access.
adb shell
[email protected]:/ $ su //Root permissions in shell
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm -r data/data/com.contextmediainc.system.synop
After that, it should let you simply uninstall or disable everything else.
With that removed, you should be able to install any compatible launcher (I used nova launcher at the time of writing this) with the adb install commands.
Flashing TWRP recovery and installing open Gapps:
I finally got a working TWRP recovery using the TWRP_2.8.7.0_RK32.img, using the method show here https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Turns out the manufacture is Rockchip and the series is an rk3288.
Flash your recovery image via adb shell on android
JANUARY 16, 2017
//edit: You need a rooted device for this kind of flashing
Hi, ever wondered about how you can flash a recovery.img via adb shell?
A lot of posts suggest flashing it via fastboot. Well my ****ty Samsung phone is not detected by fastboot. Then there is the option to install a dubious binary file which is called flash_image.. thank u internet!
Well damn I have the recover.img whats so hard to use dd and flash it with a single shell command? For those who don't know much about linux commands here we go;
Enable your USB debugging bridge in switch via adb to the terminal:
./adb shell
Then you should be able to find your recovery partion with:
DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV
that should output something like this:
/dev/block/platform/7824900.sdhci/by-name/recovery
If this is the case you only have to put the recovery.img on your sd-card or the internal storage and you are one command from flashing:
dd of=$DEV if=/external_sd/recovery.img
Thats it! No binaries you have to install. No ****ty fastboot udev rules :S
You can enter into your new recovery system with:
./adb reboot recovery
Click to expand...
Click to collapse
With that, I could flash the gapps from the recovery and now the play store and services are working seamlessly. With the exception of the home and recent buttons not doing anything, this one is completely usable now.
Install SuperSu if you want to maintain permanent root on the device!
Download links:
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Nova Launcher - https://nova-launcher.en.uptodown.com/android
SuperSu - https://supersu.en.uptodown.com/android
Recovery Reboot - https://apkpure.com/recovery-reboot/gt.recovery.reboot
Droid Hardware Info - https://droid-info.en.uptodown.com/android
Open Gapps - Platform: ARM Android: 4.4 Variant:Nano - https://opengapps.org/
No suggestions, but what a cool find. I'm surprised that hospitals use Android smart TVs! Or is it a giant tablet?
Sent from my LM-V350ULM using Tapatalk
jwrezz said:
No suggestions, but what a cool find. I'm surprised that hospitals use Android smart TVs! Or is it a giant tablet?
Sent from my LM-V350ULM using Tapatalk
Click to expand...
Click to collapse
It seems more like a giant tablet. I saved it from the dumpster hoping it could be turned into a nice web surfing machine for the garage.
slaysher62 said:
It seems more like a giant tablet. I saved it from the dumpster hoping it could be turned into a nice web surfing machine for the garage.
Click to expand...
Click to collapse
That would be awesome.
Sent from my LM-V350ULM using Tapatalk
bump
How often do I click the power button when it is booting, to get into safe mode? It just keeps going back to the home screen for me. Also, which USB did you have connected to the PC while doing this?
I am having the same issue
Any further update or progress on this from anyone? This would be perfect for a garage (or wherever) media center.
Any idea where I can find the recovery file? I tried to obtain one via TWRP and no luck.
I was able to install nova laucher and delete the files in data using adb shell. I'm just stuck at the recovery image part.
---------- Post added at 01:11 AM ---------- Previous post was at 12:20 AM ----------
Freak-tab .de website is down. Can someone please send me the image recovery file? Thanks in advance.
slaysher62 said:
bump
Click to expand...
Click to collapse
I'm able to get mine to the Recovery System but I cant run adb shell as I get exec '/system/bin/sh' which is no root. But I can't get into Safe Mode. I have the 32" Wallboard too but mine is ELC-01. What power button combo did you use to get into Safe Mode?
Plug in power and then just mash the power button? When do you stop mashing it?
Mash it as you plug in power and keep mashing?
Plug in power as you hold the power button down?
Stop mashing when it flickers or the screen is white?
Can’t get in to the settings.
ttiimmmmyy said:
How often do I click the power button when it is booting, to get into safe mode? It just keeps going back to the home screen for me. Also, which USB did you have connected to the PC while doing this?
Click to expand...
Click to collapse
Can’t get into settings. Tried the power button variations, with and without mini usb plugged in to the pc.
Wallboard
There are some typos in the original post commands. I wasn't having any luck with the "rm" commands to remove "zygote" and "sysop" apps, so I used the "ls" and "cd" commands to see what the file names were.
Removing the second file should be "[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]" , the third should be "[email protected]:/ # rm -r data/data/com.contextmediainc.system.sysop"
When you type the command "DEV=$(ls /dev/block/platform/*/by-name/recovery); echo $DEV" you'll get an output, type that output into the next command. ex: dd of="output of previous command".
If you just drop the TWRP onto the USB mass storage drive that appears when you connect the tablet, it will be in "/sdcard" folder. The final command will be something like: dd of="output of previous command" if=/sdcard/RK32.img. If you don't have root access it will tell you "permission denied", so make sure you use the command "su" after "adb shell".
Lastly, I accidentally found that when I performed a factory reset via TWRP recovery menu that the Home button started working. It may also work via the settings menu, but I didn't try it that way.
Anyway, hats off to OP for posting this as it gives use to these massive android tablets.
The secret password is cat10dog
Kinda stuck...
Hey Slaysher62. I'm kinda stuck. Was wondering if you could help me out. I have a few of these due to our hospital just not needing them anymore and telling me I could either keep them or throw them away. I've tried for weeks to replicate your success but I feel like I'm missing a few steps. If you could Message me or something that'd be great.
Thanks,
Pinball Wizard
slaysher62 said:
All, I have found a solution to get this P-WAL-107-ELC-02 unlocked and usable!
Original post:
Disclaimer:
This is a collection of the methods that worked successfully in my case. I am assuming anyone using this has an understanding of the use of ADB and shell commands. If not, please do your research to better understand the use of the command line, otherwise you may cause more damage then actual repair. Perform the actions followed at your own risk.
Rebooting into safe mode and removing contextmedia applications:
With the help of information in this thread: https://forum.xda-developers.com/android/help/android-4-4-4-context-media-10-tablet-t3670769 I got it working.
With the wallboard connected to the pc, I restarted the device and repeatedly pressed the power button until it finished booting and it started in safe mode! I was able to open the android settings, uninstall the contextmedia app and the zygote app, access dev options and enable debugging.
Connected to the PC and in debugging mode run the following to remove the synop and the remainder of the contextmedia applications.
adb reboot root //Worked in my case, confirmed root access.
adb shell
[email protected]:/ $ su //Root permissions in shell
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm data/dalvik-cache/[email protected]@[email protected]
[email protected]:/ # rm -r data/data/com.contextmediainc.system.synop
After that, it should let you simply uninstall or disable everything else.
With that removed, you should be able to install any compatible launcher (I used nova launcher at the time of writing this) with the adb install commands.
Flashing TWRP recovery and installing open Gapps:
I finally got a working TWRP recovery using the TWRP_2.8.7.0_RK32.img, using the method show here https://blog.matt.wf/flash-your-recovery-image-via-adb-shell-on-android/
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Turns out the manufacture is Rockchip and the series is an rk3288.
With that, I could flash the gapps from the recovery and now the play store and services are working seamlessly. With the exception of the home and recent buttons not doing anything, this one is completely usable now.
Install SuperSu if you want to maintain permanent root on the device!
Download links:
Generic RK32 with SDcard - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_SDcard.img
Generic RK32 with Unified Storage - http://www.freak-tab.de/abdul_pt/TWRP/Generic/TWRP_2.8.7.0_RK32_DATAMEDIA.img
Nova Launcher - https://nova-launcher.en.uptodown.com/android
SuperSu - https://supersu.en.uptodown.com/android
Recovery Reboot - https://apkpure.com/recovery-reboot/gt.recovery.reboot
Droid Hardware Info - https://droid-info.en.uptodown.com/android
Open Gapps - Platform: ARM Android: 4.4 Variant:Nano - https://opengapps.org/
Click to expand...
Click to collapse
Help with recovery
Recently acquired 3 of these 32-inch screens at first I wasn't able to get into safe mode but I deleted everything off the sd card and restarted the screen after that spamming the power button worked and I was able to get the app uninstalled and Nova launcher installed but what I'm having an issue with is getting TWRP to install also I noticed mine isn't a RK3288 its a RK3188
I've tried to flash all the TWRP RK3188 recoveries I could find but none of them work just puts the screen into a boot loop until removing power and restarting
any update from android 4.4
was anyone able to get any operating system installed on this besides andriod4.4? trying to decide if I am going to just use the screen and install a new mini board to install android 10 or chrome os
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
to get to the secret menu . power on "tablet", wait till the program is running . you will see a logo close to the bottom right hand corner. keep pressing it until the menu pops up. to get into the actual settings I can't remember what it was called but I should be something like device admin or such on the right hand sign. click it. it will ask for password ( cat10dog ) from there you should be able to follow the instructions above
Uit232b-u03
Thought I'd chime in; I have one of these wallboards, model # UIT232B-U03, nominally equipped with an RK3188. Here's what I've found:
Misc. Device Info
RIL Ver: KitKat ril-rk29-dataonly v3.3.00
Build No.: Z05-outform-32-B4.21-20160324
Build Fingerprint: rockchip/rk3188/rk3188:4.4.4/KTU8Q/eng.root.20151208.162319.eng/test-keys
Board / Chipset: rk30sdk / RK30board
As you might notice from the Build Fingerprint, this model appears to be running an engineering build of Outcome/ContextMedia's KitKat ROM; this screen was pulled from a working clinic, but USB debugging was already enabled and connecting via adb shell automatically dumps you into a root shell. There's nothing more you need to do to gain that access.
The device info (courtesy of Droid Info) references three different RK chips in a few places: RIL Ver. (rk29); board & chipset (rk30); and everywhere else (rk3188, specifically). I don't know what to make of that. Maybe something to do with it being an engineer build? Could be an engineering sample board, too -- I need to check for that info.
Personalization
As mentioned, it looks like this unit (and maybe other UIT2xx-xxx revisions) appears to come pre-rooted with USB debugging already enabled. There's no need to authorize any given machine on the tablet when connecting over ADB for the first time, either. If you still want/need to access the system settings, three-finger-tap on the application logo in the bottom-right of the screen (tapping multiple times will just cause a credits list to pop up). The password to leave the application for the Android system settings is cat10dog, as has been noted elsewhere.
Before I loaded anything new, I went ahead and factory reset it to see what it looked like. Upon doing so, the only system application was Zygote -- it looks like it's a modified version which is serving as the "launcher" for this tablet, and which forcibly reloads the application whenever it is closed for whatever reason. From factory reset, it will launch into a first-time setup screen, where it looks like you can configure the application and get connected to wifi/ethernet and download the remaining system apps (this is my impression; I didn't go through with it, but I imagine the application will want to verify a license or something). Uninstalling the modified Zygote seems to not kill the first-time setup screen (makes sense -- it's meant to stay resident and likely has everything it needs loaded into RAM at the time), but you can install Nova Launcher 5.3 (last version to support KitKat 4.4.4) and then Zygote fully disappears and you won't get bothered about setup anymore. (I have no idea what happens if you remove Zygote and then don't install a launcher. You can probably still connect over ADB, but I've never seen a launcher-less Android.) Other apps can be installed at this time, too.
As noted elsewhere, the Home and Recents soft buttons still do not work. I'm not 100% sure, but I think that's something stuffed in the ROM itself and may not be configurable (maybe through the commandline?). But, you can just use the Back button to go back to the home page at any point.
I have not had any success installing TWRP: It turns out, despite the chip being labeled in all ways as an RK3188, it is in fact a lower-specced RK3188T (1.4Ghz top speed). Every version of TWRP for the RK3188 I've tried has resulted either in a bootloop (unplug from power and plug back in to return to system), or a black screen, or the TWRP splash screen but which never progresses beyond that step. (This reminds me, I need to check on the black screen instances to see if the recovery executable is running at all, and what happens when I try to manually start it.)
On the off-chance anyone has a TWRP build for the RK3188T for me to try, I'd definitely appreciate it! Or indeed any ARMv7-based build, if I'm just going to be blindly loading recoveries to see what happens. (If anyone has any advice for debugging the recovery loading process, I'm rather a noob at this and could use any information about where to look for logging info, or to make it output a log at all if it doesn't by default.)
OH, and uh... if anyone has a stock version of the recovery partition, could you send it to me? I didn't back it up before writing over it...
Other than not getting to install TWRP and get all experimental with ROMs, it is usable in its current state as an old-but-servicable, pre-rooted-for-your-convenience-no-supersu-required, massive Android tablet. Too bad Pocket Camp requires Android 5 since a few builds ago...
Edits for grammar, spelling, extra info.
theugly_bear said:
was anyone able to get any operating system installed on this besides andriod4.4? trying to decide if I am going to just use the screen and install a new mini board to install android 10 or chrome os
---------- Post added at 07:41 PM ---------- Previous post was at 07:36 PM ----------
to get to the secret menu . power on "tablet", wait till the program is running . you will see a logo close to the bottom right hand corner. keep pressing it until the menu pops up. to get into the actual settings I can't remember what it was called but I should be something like device admin or such on the right hand sign. click it. it will ask for password ( cat10dog ) from there you should be able to follow the instructions above
Click to expand...
Click to collapse
device configuration and also just to clarify what he meant was tap on that flower looking logo repeatedly until you get the secret device configuration then on top right corner theres 3 lines select network settings and it should ask for a password which is cat10dog
And now I'm stuck
If anyone could give me direction/etc to get past where I'm at, I'd appreciate it.
I bought one of these bad boys from an auction and thankfully found this post and started the task of customizing it. I got to the point to where I deleted the apps listed, all through adb reboot recovery (used Generic RK32 with SDcard).
However, on reboot, it didn't go into recovery and had the Context Health splash to a nature backdrop and an Error: Wallboard not installed message. USB debug wasn't persistent, and trying everything that worked previously, I can't seem to get into Safe Mode, and I haven't found any other ways to get into Settings.
I did find the "reset" hole on back, which otherwise functions as a hardware 'Volume Up', but have yet to find any [Boot to Recover] methods involving only Volume Up and Power that work.
Any ideas of things to try?
Thank you
Update 1: Still no luck overall, but somewhat of progress, I hope: Plugging in the DC automatically boots up everything. If I hold down the hardware volume up/reset while adding power AND have USB plugged in, I get a listing in Device Manager; however, the screen stays black. Otherwise, as far as getting my PC to notice it, this is the only means to do it. There is no connection when powered on normally, rather I plug in USB before or after providing power. Also, spamming the power button while booting in order to get into Safe Mode had worked initially. Now doing it causing a freeze on the second or third splash screen refresh.
So I have recently acquired a bunch (50+) of these 32" screens. They were pre-rooted as @dwkindig had mentioned. I was able to remove all of the Context media apps and unlock the functionality as a basic android tablet pretty quickly. Threw Nova launcher on it and they work great. Has anyone had success in getting anything above Android 4.4 on these? I have a ton and can pull any files that would be of help to do some digging here, so please let me know. I would love to at least get Lollipop on these so that Android Webview could be upgraded and I could use the Wallpanel app for dashboard use on these. Any suggestions or help I can offer?
First time posting and I wanted to say thank you to all the excellent talent here on XDA! None of this would have been done without the work of so many people.
I have a Moto G Play (2021) (XT2093-4) that I recently purchased (Best Buy - $159 US/Carrier Unlocked) and I wanted to document my adventure in to rooting, making '/system' RW, and fixing the missing LED notification light (hint: I used the charging light) (hint^2: It's not required to make '/system' RW in order to fix the LED notification light - I just wanted more control over my phone).
First, "OEM unlocking" was greyed out for me, but became available after several days of having the phone online with a SIM card.
I followed the instructions here to unlock the bootloader and root with Magisk (Non-TWRP). Along with these instructions.
Once bootloader is unlocked, you will need the 'boot.img' file from your stock firmware. I used the "Rescue and Smart Assistant" utility to grab a copy of the stock firmware (GUAMNA_RETAIL_QZAS30.Q4_39_35_9_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml) and extracted the "boot.img" file for the next steps.
Continue installing Magisk (Filenames may be different! Don't just copy and paste.):
Code:
adb install Magisk-v23.0.apk
adb push boot.img /sdcard/Download
(Follow the instruction on your phone to patch 'boot.img' in Magisk)
adb pull /sdcard/Download/magisk_patched-23000_aKKMt.img
adb reboot bootloader
fastboot flash boot_a magisk_patched-23000_aKKMt.img
fastboot flash boot_b magisk_patched-23000_aKKMt.img
You should now have a working, rooted Moto G Play. You can just stop here and have fun with your phone, but I noticed that even with root, the system partition was not RW.
I followed these instructions to make '/system' writable (Note: you will need the 'sysrw_repair.zip' that's included in the bundle and a Linux system):
Code:
adb push systemrw_1.32_flashable.zip /data/local/tmp/
adb shell
su
cd /data/local/tmp/
unzip systemrw_1.32_flashable.zip
cd systemrw_1.32/
chmod +x systemrw.sh
./systemrw.sh in=`ls -l /dev/block/by-name/super | awk '{print $NF}'` out=/data/local/tmp/systemrw_1.32/img/super_original.bin size=50
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
(On another Linux terminal)
Code:
cd /path/to/unzipped/sysrw_repair/dir/
chmod +x sysrw_repair.sh
./sysrw_repair.sh
This results in a new folder (img) with a rather large bin file (super_original.bin).
(Back on the phone adb)
Code:
exit # Exit root
exit # Exit adb
adb reboot bootloader
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
You should be able to login and have a writable '/system':
Code:
adb shell
su
mount -o rw,remount /
No errors should appear.
Last, I like having an LED indicator that tells me that I have an SMS/MMS notification waiting. Motorola thought it would be wise to eliminate that feature altogether instead of having the option to enable it. So, I forced it back on using a startup script that dumps the notifications and greps for some key words. And, if it finds something, it "breaths" the charging LED. The script loops until the notification is gone, then keeps checking for new notifications every 30 seconds. (Note: the "/data/adb/service.d/" directory is used by Magisk like an INIT service):
(Still root on the phones adb)
Code:
cd /data/adb/service.d/
cat <<EOF > ledfix.sh
#!/bin/sh
while true; do
if dumpsys notification | egrep NotificationRecord | egrep sms > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) == 0 ]]
then
echo 1 > /sys/class/leds/charging/breath
sleep 2
continue
else
sleep 2
continue
fi
elif egrep 'Charging' /sys/class/power_supply/battery/status > /dev/null
then
if [[ $(cat /sys/class/leds/charging/breath) -ne 0 && $(cat /sys/class/leds/charging/brightness) -ne 0 ]]
then
echo 0 > /sys/class/leds/charging/breath
echo 255 > /sys/class/leds/charging/brightness
elif [[ $(cat /sys/class/leds/charging/breath) == 0 && $(cat /sys/class/leds/charging/brightness) == 0 ]]
then
echo 255 > /sys/class/leds/charging/brightness
else
continue
fi
else
echo 0 > /sys/class/leds/charging/breath
echo 0 > /sys/class/leds/charging/brightness
fi
sleep 30
done
EOF
chown 0.0 ledfix.sh
chmod 0755 ledfix.sh
reboot
Now, the charging light will fade off and on about every 2 seconds if there's an SMS/MMS notification waiting. And will check for notifications every 30 seconds. I'm sure someone can come up with a better way of doing this, but this was a nice quick-and-dirty way to get what I wanted.
Hope this helps!
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
PROFSLM said:
I created an account to say thank you for this, I have already done a good portion, having unlocked the bootloader, the problem is the Rescue Smart Assistant, it won't let me log in, it keeps telling me it can't connect, and the GUI is different because of an update, there is no download button inside the program, only a greyed out rescue button. How did you manage to make the backup Boot.img? Maybe you are using a different OS, and/or version of the program (Not the app, that is already auto-installed), I'm using Windows 10, are you on Linux? I might just need to try from Linux, maybe in a VM.
I was trying to do this before I found this post, and have already installed ADB, the SDK, fastboot, and Motorola Drivers, I just need a way to get the Boot.img, and to patch it, also figure out how to flash it. The last android I rooted with a custom rom was the HTC EVO 4G with Oreo/Jellybean, so I'm a little rusty, but am able to understand technical jargon.
If anyone could help, that would be awesome. I've reinstalled different versions of Rescue Smart Assistant as well, they always upgrade on boot, same problem. I've added exceptions to my firewall and everything.
UPDATE: Was about to post this when I had updated from android 10 to 11 and decided to try logging in again a little closer to my router, to see if the connection was timing out, I think that was the cause, as I can now sign in, and the GUI seems correct from the first appearance. I don't see why I should have any trouble following the rest of the guide, but feel I should share my trials and frustrations anyways, for anyone else experiencing the same,
Thanks again.
Click to expand...
Click to collapse
You can also get the firmware from
Lolinet Mirrors
https://t.me/MotoUpdatesTracker
Search for Firmware by codename, software channel, Software Version, and build #
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
mario0318 said:
So I wasn't going crazy when I could swear a LED notification light in the upper right side above the screen blinked once whenever I rebooted the phone?
Why would Motorola include such a thing and not utilize it for more than merely a boot up indicator? Like I dont even get to see it come on while charging, it literally only blinks once during boot and that's it.
Click to expand...
Click to collapse
I know!
I don't know what triggers that light to come on. I even waited until the battery was at 6% and the light still never came on.
So, I updated the script above to make the light go full brightness if the battery is charging. The order matters, so if a notification comes in while charging, it'll "breath" the LED. Also, if the battery is full, then the light will turn off. Kind of telling you that it's time to unplug.
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
jorduino said:
I followed these steps and my touch screen stopped working. I had previously installed twrp already on it while trying to learn how to root it, and when i boot into fastboot it goed through twrp, i also used the boot.img file from lolinet, not sure which of these caused the issue. Interestingly though, the touch screen does work whilst in twrp. any suggestions on how to fix or what would be causing it? Phone does work with usb mouse over OTG
Click to expand...
Click to collapse
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
mario0318 said:
Are you absolutely sure you used the correct boot.img from an image version exactly matching your phone variant version?
Click to expand...
Click to collapse
Im not completely sure how to get the right file, but I think the first time it was the wrong one, but then when i got what i thought was the right one, it just didn't work at all and I had to recovery flash it. I had just updated so maybe the correct image wasn't available yet. Im going to try again though
Oh! Hello @latentspork. Thanks for your interest in my SystemRW project. I just came across this thread randomly...
I'm happy you got my script to work on your Motorola device by using the included sysrw_repair script
Please feel free to send me your log files from script folder. Thanks. It's useful for further development of the script
latentspork said:
The phone doesn't have enough space to complete 'lpmake' on the device and will end with an "Error 73" code. Running the "sysrw_repair_v1.32" tool on a Linux machine was a workaround because it pulls the '*.img" files to your local machine then combines them in to a single '.bin' file. But, before I did that, and because it's really annoying, I made some room to stop the phone from complaining about a lack of space:
Click to expand...
Click to collapse
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Yes that's true the included sysrw_repair script (Linux only) pulls the image files from the phone to your computer and attempts to run the same lpmake command with the same arguments that just failed with error 73 on the phone itself and now all of a sudden it just works in Linux. Go figure.
latentspork said:
(Still on the phone's adb)
Code:
rm ./img/super_original.bin
Click to expand...
Click to collapse
Why would you delete the super_original.bin ? That's your stock read-only super image which by default is automatically dumped by script for backup purposes in case you ever get a bootloop.
And if you launch the script by specifying a custom input value (in=x) like in your example above then you won't even have a super_original.bin file to begin with because script will skip the whole dumping of original super image process.
latentspork said:
This results in a new folder (img) with a rather large bin file (super_original.bin).
Click to expand...
Click to collapse
I think you mean super_fixed.bin
latentspork said:
Now it's time to flash the fixed bin file to the "super" partition:
Code:
cd /path/to/unzipped/sysrw_repair/dir/
fastboot flash super ./img/super_original.bin
fastboot reboot
Click to expand...
Click to collapse
Here in your instructions you are manually flashing the wrong file. Shouldn't you be flashing super_fixed.bin to your super partition?
Usually I only flash the super_original.bin to get back out of a bootloop...
latentspork said:
Now, on the Linux machine, I unzipped 'sysrw_repair_v1.32_proper.zip' then commented out line 39 (where it calls the "flash()" function) of the script (sysrw_repair.sh) because I wanted to flash the "super" partition myself.
Click to expand...
Click to collapse
See that's why I included that automatic flash() function in the repair script. Then you don't have to worry about manually flashing the wrong file to your super partition
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
@lebigmac
I really appreciate the reply and the tool! It did work really well on my model (XT2093-4).
That's not 100% accurate. Lpmake error 73 means CAN'T_CREATE and has nothing to do with error 70 (insufficient space).
To this day I still don't know exactly what causes error 73 on some devices (mostly Motorola and others) but it looks like some kind of kernel panic. If anyone knows how to avoid this error 73 in Android please let me know! Thanks!
Click to expand...
Click to collapse
I only assumed that "Error 73" was caused by insufficient space, because the phone really did run out of space. I noticed that the phone was out of space because I got a home screen notification warning, asking me to free up space. I confirmed it with a "df -h" at the shell. Apparently, the OS takes up almost 15GB. When you add the ".img" files, there's only about 5GB left. There wasn't enough room to complete the ".bin" file. Maybe I could have used an SD card or something.
You're probably correct in that "Error 70" is the correct error for that, but on my phone, I never saw that error. I did notice that the tool was still trying to write data as the phone ran out of space, then it would throw the "Error 73". Maybe it didn't register the lack of space, or just an oddity with my model? No idea.
Why would you delete the super_original.bin ?
Click to expand...
Click to collapse
This is the file that was created when I initially ran the "./systemrw.sh" command on the phone. The result of running the command on the phone were several ".img" files and a very large "super_original.bin", but it was incomplete because the command threw an "Error 73". I was following your instructions, and I noticed that the output name of the file was "original" instead of "fixed". I probably could of outputted it to a new name to reduce confusion, but I didn't really care too much about the name as long as I had a working file.
I think you mean super_fixed.bin
...
Shouldn't you be flashing super_fixed.bin...
Click to expand...
Click to collapse
Normally, yes. But the Linux script also outputted the filename "super_original.bin". Again, as long as it worked, I was okay with it. The commands I used above were the exact commands that I ran at the time. I copied them from the terminal consoles I was using. So I don't know why it wasn't outputting the correct filename (again, I was following your instructions and was a little confused that the names came out differently - I just figured I was doing something wrong like not use the proper output command or something).
Then you don't have to worry about manually flashing the wrong file to your super partition...
Click to expand...
Click to collapse
I was really just being cautious because my previous phone broke and I didn't have a fallback.
But, at no point were there two bin files (original and fixed), so there wasn't much confusion. Where I originally had just ".img" files before running the script, I now had a single ".bin" file. I knew that was the file I needed.
But again, thank you for all the hard work on this tool! I was reading that it's worked on lots of different model phones, and it's always good to see the open source community doing things that help all kinds of people.
For moto notification for this phone at least use https://play.google.com/store/apps/details?id=br.com.itsmeton.motoledreborn or moto led reborn from the play store it just works
Hi, sorry. This can be removed. I put it in place because I was having issues with the xda app. For whatever reason, every time I tried to share this particular post, it would share a link for the post which I used originally, rather than the current post. I knew that if I commented I could get back here easily on my PC.
So what is the place holder for