Related
I've been a lurker since I got my eris back when root was a dream. Now I have quite a few things floating around my work dirs that aren't on xda or are wanted, so I figured I would start releasing some of my better/more polished things. So here is my first:
cbackup v0.4
Based upon craft_backup v0.5.3: showthread.php?t=628743 (sorry no links)
Backup and restore apps/data just like craft_backup
Changes/Features of cbackup:
- Change names to cbackup and crestore because I got tired of typing out "craft_backup" and "craft_restore"
- Move backup dir to /sdcard/backups/cbackup/*
- For cbackup, allow a choice for destination in backup dir (defaults to cb<date>)
- For cbackup, automatically move backup dir to timestamped location instead of overwriting it
- For crestore, display menu of all cbackup dirs along with original craft_backup dir if it exists. This menu has the latest last, numbered first with number 1 being the default.
- Works with roms that don't have the busybox symlinks installed
Changelog:
v0.3
- First public release
v0.4
- Fix problem when missing bb symlinks
Disclaimer: I am not responsible for damage caused by this app. I take no credit for the good work done on craft_backup, I just wanted something it didn't do so I hacked it up to suit my needs. Eventually it became nice enough to share. I will not support it, unless there is something wrong with my added code (which is possible, since the listing code is complex). Refer to the original app's thread for almost all problems.
nXuaJunYYc
Testing it now.
EDIT: WORKS PERFECTLY- 5 STARS.
Crestore- not found.... help?
I assume you're running "crestore" and not "Crestore" nor "Crestore-". Can you post the output of:
echo "$PATH"
from adb shell?
If that's fine, I think I know what may be wrong, but try that first
edit:
I'll be uploading a new version in a minute that I think will fix your problems, but if it doesn't, if you could also try the following it would be helpful:
# which crestore
# which sed
# echo abc | sed -es/a/d/
# ls -l /system/bin/crestore
# ls -l /system/bin/cbackup
# /system/bin/crestore
So I got it to find it, but it says not found for everything. Also comes up in Italian no matter what, but no biggie.
or use the eris master app, which can do most of that right now. the good thing is that its in a gui interface. jamezelle and i will be adding additional features later for the backup / restore apps as well. and one thing that we will have shortly is the ability to restore market update links for apps installed outside of the market.
@ECLIPS3:
Sorry, I'm a command line guy and I'm a linux guy. I really don't want to install wine and mono on my poor little linux netbook just to run your app and then navigate a gui. Plus these scripts run entirely on the phone, so you should be able to run them anywhere with only your phone (maybe even using terminal on the phone...haven't tested that yet). And before we start a war, I'm not saying that there is anything with wrong with your app, and I'm sure it has/will help a lot of people who want the easy gui, but it wasn't for me, and I thought other people may feel the same way. There's no reason both apps can't exist. I also appreciate you letting people know in this thread so the less cli-oriented people know their options.
@Erisftw:
That is really strange if it's continuing to not give you a choice for language. Are you sure you flashed the latest one that I uploaded (cbackup-v0.4-signed.zip)? And that you made your backup either using v0.4 or using v0.3 on a phone with busybox properly installed. If so could you copy and paste the first ~20 lines of output from crestore, and let me know if you are on windows or linux?
dont worry, not trying to start a flame war at all. i love diversity and competition as it creates better programs to arise, that ultimately are better for the end user. theres plenty of room for everyone here. i love CLI as well, but not a lot of people do. arent you glad this is a free world to have competition?
Changed to 4, restored. fine, but it has old rosie, and when you click on the app, it says app no longer installed.
Hello everyone,
I'm writing an android application that needs to swap between 2G/3G networks.
I wasn't able to find any suitable function in the SDK documentation.
I tried "digging" into the android code to see how other activities (such as Settings.ACTION_WIRELESS_SETTINGS, the Phone Information technician code [*#*#4636#*#*]) implement it and came across com.android.internal.telephony.Phone which is in charge of the switching.
I guess the device has to be rooted to perform this (and of course, my application needs root privileges), however, I can't change the android code on the device.
So, my question is: How do I access com.android.internal.telephony.Phone from my application without changing the android code?
Many thanks,
Omri.
Anyone has an idea?
Thank you
CDMA or GSM?
And a lot of the telephony is private.
Sent from my iPhone with the bigger GeeBees.
I have good news: I got it working and I wanted to share on how.
I had a few problems on the way, but I faced them all.
First of all, being able to access com.android.internal.* from the SDK (with ADT) wasn't that comfortable before I ran into this guide, which lets you include all the hidden & internal APIs in your android.jar library and override the access rules limiting you not to access them in ADT.
After that was done, I thought I'm done, but I was wrong.
To switch from 2G to 3G you need to invoke setPreferredNetworkType() method on the Phone object (com.android.internal.telephony).
To get the Phone object, you'll need to invoke the getDefaultPhone() method on PhoneFactory (com.android.internal.telephony).
But, of course, nothing will be simple, this method only runs when your manifest inclues android:sharedUserId="android.uid.system" (aka, your process runs as system user).
Your process won't be able to run with the android.uid.system UID without your package being signed with the platform certificate.
To sign your package with the platform certificate, you need signapk.jar, platform certificate (platform.x509.pem) and platform key (platform.pk8).
Because I'm using CyanogenMod I was able to put my hands on the platform cert&key pair without recompiling android. (available here)
Once you have these, the rest is pretty simple:
Sign your APK with signapk.jar:
Code:
java -jar signapk.jar platform.x509.pem platform.pk8 Application.apk Application-signed.apk
Because this is a system package, you won't be able to install it with "adb install Application.apk", we'll have to use a different method.
Upload your APK to the /system/app folder (don't forget to mount /system for read-write before you do that):
Code:
adb push Application-signed.apk /system/app/Application.apk
The next thing to do is launch your activity:
Code:
adb shell am start -a android.intent.action.MAIN -n com.your.package/.YourActivity
That's it!
You got it working!
Good luck to whoever runs into this post
Cheers,
Omri.
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
this is awesome!
cb22 said:
Hi everyone,
If you have any questions relating to Arch on the TF300, please post them here and not in the dev thread
I'll do my best (as well as others, I'm sure) to answer them, but bear in mind that you should have some basic Linux knowledge before flashing!
Click to expand...
Click to collapse
I can't thank you enough for this, it's been fantastic so far! I only have a few questions, as I am extremely new to arch linux...as in this is the first time I've used anything aside from debian in the linux world.
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Despite all of that, this has breathed new life into my tablet, you're doing fantastic work and I hope you only continue to make it more amazing!
fankuan19 said:
To start, how would we go about changing DE's? I've downloaded a couple, but i get errors every time i try to start one saying that another window manager is already running. With ubuntu one just logged out and chose from the log in screen, but there doesn't appear to be a log out process for this, i get a black screen every time i do. Other than that, are there any general programs/settings/tweaks that you would suggest applying? While this is very nice, it still seems to be missing some basic functions, such as putting the screen to sleep and having a set system time.
Click to expand...
Click to collapse
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
whoops
timothyb89 said:
Take a look at the .xinitrc file in the home directory. It's a hidden file so you may need to "show hidden" or give an editor the full path (/home/user/.xinitrc)
The file runs the following by default:
Code:
exec startxfce4 --with-ck-launch
You can change everything after `exec` to the script for a different DE, such as `startkde`. If you don't know the command, there should be a list of session templates in /usr/share/xsessions/. Inside each .desktop file there's an "Exec=" line, everything after that is the command to sub in.
My crappy bash skills threw together a quick command to get a list of installed xsessions:
Code:
grep "Exec=" /usr/share/xsessions/*.desktop | sed -E 's/^Exec=(.+)$/\1/'
The output on the default rootfs will just be "startxfce4". If you have KDE another line should output "startkde", and so on. Put the command in your .xinitrc (making sure to replace the current one) and then reboot as there's no proper way to log out.
Click to expand...
Click to collapse
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
fankuan19 said:
First of all, thanks for the help! Unfortunately, I appear to have done something incorrectly, as the Linux partition will no longer boot. That code didn't return anything but a ">", although as I type this i realize I may have needed to be root...haha, regardless, I tried to edit the .xinitrc file with "exec /bin/usr/startlxde", which is what was after "exec=" in the xsessions directory, nothing happened after waiting quite a while after boot.
I suppose I'll have to reflash the entire partition, considering i can't access the filesystems to change it back. Ah, the wonders of linux!
Click to expand...
Click to collapse
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Razorbacktrack5535 said:
Sorry if I repeat my question,but how can i activate the keyboard without using a pc with linux ?
Click to expand...
Click to collapse
Without using a PC... Hmm, that could be tricky. If you're in Android, and you add this line to the top of /data/linux/home/user/.xinitrc
Code:
maliit-server &
(before the exec line)
It should give you the virtual keyboard when you restart into Linux.
cb22 said:
You should be able to gain access easily via Recovery. Just adb shell in, mount /dev/mmcblk0p8 /mnt and look in /mnt/linux - that's your root file system...
Click to expand...
Click to collapse
I was actually able to just use the terminal emulator in android to navigate back to the .xinitrc file, turns out i wasn't supposed to leave the "--with-yadda-yadda" bit, so i got lxde working...and as it turns out, i don't like it nearly as much as the DE you included, so i'll be switching back to that!
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
koiulpoi said:
First off: thank you SO much for your hard work at this! My tab has never browsed the web this well. It's better than the desktop I'm sitting next to. Arch is amazing!
Just a few questions. Do we have basic tab controls yet? I'm looking for, specifically:
Brightness Control
Enable/Disable Touchpad
Volume Control
Sleep/Suspend/Hibernate
Especially that last one! As far as I can tell, if I'm not going to use the tab for more than a couple minutes, it's apparently best to shut it down or reboot back into Android so it can "sleep". Or plug it in. I know we're rough around the edges yet, but is this stuff in, or no?
Click to expand...
Click to collapse
I don't think sleep/suspend/hibernate is implemented at all quite yet. The backlight seems to turn off completely when the screen times out though so you can fake having a low power mode, though obviously true sleep would be nice.
As for volume control, use pavucontrol. You may need to install it with `pacman -S pavucontrol`.
For brightness ... there's no good way to do this as far as I can tell. XFCE has a brightness control applet you can add to the bottom panel but it doesn't seem to work, and most of the usual packages (e.g. xbacklight, etc) don't detect the backlight device. Oddly enough I gave e17 a try and its builtin brightness applet worked fine, I wonder what they do differently ...
At any rate you can control it manually: the file /sys/class/backlight/pwm-backlight/brightness has a 0-255 value which controls the screen brightness. Note that you need to run the echo command as root
Code:
# echo "1" > /sys/class/backlight/pwm-backlight/brightness # minimum brightness
# echo "255" > /sys/class/backlight/pwm-backlight/brightness # maximum brightness
# echo "0" > /sys/class/backlight/pwm-backlight/brightness # completely turns off backlight. use with care
Setting it to zero makes it next to impossible to see the screen. I ended up having to ssh into the device (or reboot) to get it back.
I modified the file through a PC and It works ! Thanks, no problems with wifi
Sleep / Suspend isn't implemented yet.
But, I did a bit of testing, and the TF should last for about ~40 hours with the screen off, and the processor in the Low Power mode (which it does automatically. Obviously, it's still wasteful compared to proper suspend, but it's not too bad.
Really liking this so far, other than managing to break wifi once, which I fixed by doing a quick re(install I guess is the proper term). Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Thanks for all your work cb22, and thanks for taking my advice and switching file hosts
This may be a dumb question
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Shingaling said:
But I can't for the life of me find out how to flash the hybridkernel.blob, I've already done every other thing, but i'm lost as to what to do there. Can I get a bit of guidance please?
:Nevermind: Silly me forgot to go to fastboot, I was trying to do it with adb, for any others though, reboot to fastboot on your tf300t and then run go to the location of fastboot on your pc and hold shift and right click and select open comand line here. Then move the hybridkernel.blob to the same location as the fastboot and run fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
Disregard, didn't see the edit until after you posted essentially the same thing I did.
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
koiulpoi said:
So, does Adobe Flash support work at all in Chromium? I haven't gotten it to recognize the plugin at all. Any way to get this working, or is it just gonna keep bugging me to install it?
Click to expand...
Click to collapse
I don't think it works at all, I've tried every permutation sudo pacman -S flash-plugin that I could think of and I've gotten notwhere.
They is no flash for ARM for pure Linux.
Wysyłane z mojego ASUS Transformer Pad TF300T za pomocą Tapatalk 2
Itege said:
Any chance of a future release having SLiM or something setup out of the box(I'd do it but looking at some of the guides, we are missing some files(?) :s) either that or is there a way to autologin a new user other than the default one named user?
(edit for more info) I've tried following a guide I found on the arch wiki which had me modify [email protected], but it didn't boot so I had to edit it back to the default.
Click to expand...
Click to collapse
In theory you should be able to install a proper display manager without too many issues:
Code:
# pacman -S lightdm lightdm-gtk-greeter
# systemctl enable lightdm
...though when I tried this the DM would never actually be run. I was able to run it manually over SSH without issues (both lightdm and slim worked, more or less). I'm in the process of investigating why it isn't run at startup like it should be, whatever the issue is doesn't seem to be related to the display manager itself.
I have an issue with wifi.
1: The WLAN do not find any Network with Channel 12 or 13.. I think I must change the region in germany, but where?
2. The WLAN do not connect, they search for an network adress and after 30seconds they ask for wlan key again.. the key is correct and my router shows the connection.. but archlinux means the key is wrong.. testet with router und smartphone wlan hotspot..
3. 3G not connecting, i have create a profile for BASE Germany, but they do not connect.
UPDATE:
for 2: Sometimes they connect and I can surf. But the ping are more then 600ms.. After few seconds the connection lost, sometimes they connect again, sometimes say ask for wlan key again.
Maybe you can help me. Sorry for my bad english.
Yours Sincelery
Robert
Could any of you guys find out if you have a process running in "interruptible" state named "kinteractive_lo"?
You can check that using "top" in CLI or installing gnome-system-monitor. I guess the standard xfce task manager works as well.
It's driving me nuts and I believe is one of the reasons why I have to hard-reboot my tablet, since invoking reboot with --force works perfectly.
Thanks in advance!
Hello everyone,
Could you show me how to access my Nook Glowlight 3 without registration ?
Current firmware: 50.0.117
Thank you!
Well, I usually bypass the registration by popping the thing open, hooking up a 3.3V UART interface and getting a root console.
I've never really looked into if there were secret hand signals to bypass the registration.
So I looked at the disassembled code to see what was there.
All the OOBE (Out-of-box-experience) stuff is in /system/priv-app/bnereader.apk
The welcome screen is com.nook.app.oobe.o.WelcomeIntroActivity
This calls com.nook.viewutils.KeyHeldHelper to see if a particular button is held down
and also com.nook.viewutils.MultiClickListener to see if you tap three times.
I held the button and tapped three times and I got com.nook.app.util.DiagnosticActivity (as in the screen grab).
(You can also get here if you had a shell with)
Code:
# am start -n bn.ereader/com.nook.app.util.DiagnosticActivity
The problem? The key you have to hold down while tapping is the volume up key.
What? You don't have a volume up key?
The way I held down the volume key was with a USB keyboard, but that can only be done when you're rooted.
You could also pipe raw events to the input system if you were rooted.
I'm certainly interested in someone contradicting me, but this seems like a dead end.
Ok, I'm going to contradict myself.
As I said, the Welcome Intro screen needs the volume up key and a triple tap.
There is also the com.nook.app.oobe.RegisterUserLogin screen
This can be bypassed by holding the Lower Left and the Upper Right and giving a triple tap.
Obviously, this would only work on the Glow3 which has buttons.
Unfortunately, the Glow2 has the exact same code.
I can't seem to get this one to work on an (already rooted) Glow3.
If you have a Glow3 try the LL/UR/triple tap.
Yes, this should work on the Glow3 if you are at a page with email/password/etc.
I can't get there because I'm intercepted by the WiFi page.
It's not working
Hello
I have Nook Glowlight 3, I tried the LL/UR/triple tap many times on login screen. but it don't work
Thank you!
Renate NST said:
Ok, I'm going to contradict myself.
As I said, the Welcome Intro screen needs the volume up key and a triple tap.
There is also the com.nook.app.oobe.RegisterUserLogin screen
This can be bypassed by holding the Lower Left and the Upper Right and giving a triple tap.
Obviously, this would only work on the Glow3 which has buttons.
Unfortunately, the Glow2 has the exact same code.
I can't seem to get this one to work on an (already rooted) Glow3.
If you have a Glow3 try the LL/UR/triple tap.
Yes, this should work on the Glow3 if you are at a page with email/password/etc.
I can't get there because I'm intercepted by the WiFi page.
Click to expand...
Click to collapse
dnt83 said:
I tried the LL/UR/triple tap many times on login screen. but it don't work
Click to expand...
Click to collapse
You know, there are more secret touches and broken code all over.
I found another one, but I can't seem to get this to work either.
It's on this screen. There are four touch spots.
The bottom two when pressed and held should show a version number at the top center of the screen.
The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.
I'm working on it, but you can try too.
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Renate NST said:
You know, there are more secret touches and broken code all over.
I found another one, but I can't seem to get this to work either.
It's on this screen. There are four touch spots.
The bottom two when pressed and held should show a version number at the top center of the screen.
The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.
I'm working on it, but you can try too.
Click to expand...
Click to collapse
Thank you very much for your support
The bottom two it showed version.
I tried the top two it no work
dnt83 said:
I tried the top two it no work
Click to expand...
Click to collapse
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Yes, it worked
Thank you very much!
Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Hello
Could you show me next step to root it?
Thank you!
Renate NST said:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
Click to expand...
Click to collapse
Hello
I rooted and can work in adb shell, could you show me how to skip oobe?
Thank you!
dnt83 said:
how to skip oobe?
Click to expand...
Click to collapse
You need to install a launcher so that you have something "Home" to run.
Also:
Code:
# pm disable com.nook.partner/.oobe.WelcomeScreenActivity
Renate NST said:
You need to install a launcher so that you have something "Home" to run.
Also:
Code:
# pm disable com.nook.partner/.oobe.WelcomeScreenActivity
Click to expand...
Click to collapse
Yes, Thank you
I already installed custom firmware
Thank you very much for your support!
And if anybody is wondering, this works on all 5.0 Nooks, Glow2, Glow3, Glow4
Hi, I just picked up a new Nook Glowlight Plus (the 2019 7.8" model) and am trying to get started using it without the compulsory registration. My understanding from the start of this thread is that I should be able to root it, install an alternate launcher, disable the oobe.WelcomeScreenActivity, and I'm off to the races.
I have gotten as far being able to see the device with adb and connect to it, but I can't root it. adb seems to be working as normal (e.g., I can "adb shell" in as I would expect) but any attempts to push files with "adb push" fail. After attempting adb push, the device disconnects from adb and can no longer be seen until I physically unplug and re-plug it. Interestingly, adb push of a directory _does_ create the directory structure on the Nook -- just not any of the actual files...
Any help debugging this is appreciated...
A log of what I'm seeing is here:
https pastebin.com / ti4qB6Xr
(Sorry, I can't post direct links yet, and didn't want to spam the thread with a wall of text...)
Thanks!
---------- Post added at 02:58 AM ---------- Previous post was at 02:52 AM ----------
I should also mention that if I start to go through the on-device Welcome screen (choose timezone, choose wifi network and enter password), before actually getting to the login screen, I'm prompted to allow it to download a firmware update. I did not allow the update, in case a) the update changes something that would make rooting or installing a new launcher more difficult, and b) I don't want to miss the opportunity to note the download link and fetch an extra copy of the update in case it's useful later.
But if the download link is already known to the community, and if the update is unlikely to change anything that rooting/launchers depend on, I would also try letting it download, and then going to the login screen and trying the lower-left+upper-right+triple-tap bypass mentioned earlier in the thread.
Please let me know if I should try this.
Thanks.
So "adb push" is still not working, but I was able to root the device with shell chicanery. I tarred/gzipped the exploit payload, base64 encoded it, and used a shell loop to transfer it a line at a time:
Code:
c=1
cat nookrooter.tgz | base64 -e | while read line
do
echo "$c" >&2 ; c=$(expr $c + 1)
echo "$line" | adb shell 'busybox head -1 | busybox tee -a /data/local/tmp/nookrooter.tgz.b64 > /dev/null'
done
At ~64k base64-encoded lines, it took a bit over an hour to transfer. After base64-decoding, checking the md5 on both sides, and untarring in the right spot, it rooted just fine:
Code:
frappe/home/chris/nook/root-glp/rootGLP-3-13998# adb shell id -u
uid=0(root) gid=0(root)
That said, I'd still love to get some guidance on this device from folks who are familiar with it. Any idea why adb push might consistently fail? Is my basic understanding of how this whole process works is correct? Does it matters if I allow the device to complete the OTA firmware update before going farther?
My intent for the device is to use it as a standalone e-reader. I don't want to ever connect it to a network, nor to run any apps on it other than an e-reader. Public domain e-book content will be converted to EPUB (or, occassionally, CBZ or PDF) with Calibre (specifically the ebook-convert CLI) and copied via USB. I don't need to use "shelves" or whatever the Nook paradigm is for organization, nor will I "manage" the device with Calibre; "management" as such will be strictly copying individual files into a flat directory structure from the shell. I'm not too fussy about fonts, and don't need (or want) much more than the ability to click on a book and page-up/page-down through its contents.
I'm an experienced C/Unix developer, but have never used Android before.
Any help and pointers are much appreciated.
Thanks!
CrisCraigMorgan said:
But if the download link is already known to the community...
Click to expand...
Click to collapse
Yes, the manifest of the updates is discussed here: https://forum.xda-developers.com/nook-touch/general/software-updates-wifi-t4136097
CrisCraigMorgan said:
So "adb push" is still not working...
Click to expand...
Click to collapse
Strange. Why didn't you try adb install on the apk?
Maybe the adb on your host is broken. Try this.
adb push something
Did it fail?
adb devices, is it "gone"?
lsusb, really?
adb kill-server
adb devices, is it "back"?
Renate NST said:
Yes, the manifest of the updates is discussed here: https://forum.xda-developers.com/nook-touch/general/software-updates-wifi-t4136097
Click to expand...
Click to collapse
Thanks!
Renate NST said:
Strange. Why didn't you try adb install on the apk?
Click to expand...
Click to collapse
I'll try installing some apk that way. But in the case of the root payload, there are other files in addition to the one APK.
Renate NST said:
Maybe the adb on your host is broken. Try this.
adb push something
Did it fail?
Click to expand...
Click to collapse
Yup, I tried experimenting with other files, smaller files, individual files rather than directories -- all files failed (though, as noted, directories were created in the case of trying to push a local source directory).
Renate NST said:
adb devices, is it "gone"?
lsusb, really?
adb kill-server
adb devices, is it "back"?
Click to expand...
Click to collapse
I can run some more experiments later. The pastebin log above shows what I saw: immediately after any attempt to use "adb push", "adb devices" showed no devices. I didn't check usbconfig (FreeBSD here, not Linux, but that shouldn't matter), but there were no kernel messages about the device detaching (until I physically pulled the USB cable), so I suspect that the device would still have shown as attached.
Thanks!
So having rooted my Nook, I went ahead and installed the l2.apk launcher posted here https://forum.xda-developers.com/nook-touch/general/normal-launcher-nook-t3966911; disabled com.nook.partner/.oobe.WelcomeScreenActivity; renamed the bootanimation file; and rebooted.
When the device rebooted, it just displayed a message that said, "Unfortunately, com.nook.partner has stopped" and nothing else. Re-enabling com.nook.partner/.oobe.WelcomeScreenActivity restored it to its original boot-up behaviour.
So I think I must be missing something basic about the boot process, or rooting generally.
Should it be sufficient to just have another launcher installed? Do I have to do something particular to invoke it during the boot process?
Should I install TWRP? Alternate firmware, as described here: https://forum.xda-developers.com/nook-touch/general/gp-g3-gp7-8-twrp-alternative-firmware-t4074347 ?
Another question I have is about keeping root access across reboots. I can unpack the exploit in rootGLP-3.zip (from https://forum.xda-developers.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331) and run it to gain root; but when I reboot the device, I lose root again until I re-run the exploit. I tried setting /system/bin/busybox suid root, but then "busybox su" returns "unknown user root" -- I'm guessing because it's calling getpwuid(), but there's no /etc/passwd so the call fails. Could I just create /etc/passwd to define root? I also tried copying the "su" binary in the exploit dir into /system/chris/bin/ and setting it suid root, but this also fails (with no output). I could just write the three-line version of su that calls
Code:
setuid(0); exec("/system/bin/sh")
, but I have no idea how to compile code for this thing. Anything I'm missing here?
Thanks.
I played around a bit more with adb push. Still consistently failing, but restarting the local adb server does at least re-establish connectivity without unplugging/re-plugging the device. Definitely sounds like a problem with my local adb install rather than the device. Considering that I have a(n admittedly super-janky) method to transfer files, I don't feel a strong need to debug it right now.
Code:
frappe/home/chris/nook-13599# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
frappe/home/chris/nook-13600# adb devices -l
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:19
frappe/home/chris/nook-13601# adb push ReLaunchX_2.1.5-app-debug.apk /data/local/tmp/
adb: error: failed to copy 'ReLaunchX_2.1.5-app-debug.apk' to '/data/local/tmp/ReLaunchX_2.1.5-app-debug.apk': couldn't read from device
ReLaunchX_2.1.5-app-debug.apk: 0 files...ped. 7.6 MB/s (131056 bytes in 0.016s)
frappe/home/chris/nook-13602# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)
frappe/home/chris/nook-13603# adb devices -l
List of devices attached
frappe/home/chris/nook-13604# adb kill-server
frappe/home/chris/nook-13605# adb devices -l
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:1
frappe/home/chris/nook-13606# adb shell
[email protected]_6sl:/ # id
uid=0(root) gid=0(root)
[email protected]_6sl:/ # ^D
CrisCraigMorgan said:
Anything I'm missing here?
Click to expand...
Click to collapse
There's all sorts of "rooting" stuff here, but I just prefer a simple replacement of adbd in the ramdisk with one that doesn't switch to user "shell".
I don't want/need/like the chainfire stuff hanging around.
Sorry, I've lost track of where everything here is as I've never used any exploit method.
As for your launcher stuff, did you check logcat to see if there is any obvious reason why partner.apk is dying?
Code:
adb logcat
Have you tried:
Code:
adb shell am start -n com.android.launcher/com.android.launcher2.Launcher
Was the Launcher even installed correctly?
Code:
adb shell pm list packages -f launcher
I tried all rooting methods for fire hd 8 7th gen but didnt succeed... the apply update in the recovery is also not there... can anyone help me?
im new...
Darklord071 said:
I tried all rooting methods for fire hd 8 7th gen but didnt succeed... the apply update in the recovery is also not there... can anyone help me?
im new...
Click to expand...
Click to collapse
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Letitride said:
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Click to expand...
Click to collapse
Thanks for the welcome.. i tried using linux and windows... the fire tab is running fire os 5.6.6.0..
i know adb commands..and i disabled ads using fire toolkit.
and i use debian linux.
Thanks in advance!!
Letitride said:
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Click to expand...
Click to collapse
btw do u have the drivers for 32bit arch linux?
thx
Darklord071 said:
btw do u have the drivers for 32bit arch linux?
thx
Click to expand...
Click to collapse
Fire OS 5.6.6.0 is the newest one and my understanding is that version/release is a PITA as the "exploit" to unlock & inject the Fastboot mod is a problem .... sorry about that, maybe another XDA'er familiar with that can help walk you thru on their efforts & success (or not) i.e. whether they managed to roll it back.
I used LMDE-4 Cinnamon 64bit (d/l via Linux Mint) and it works fine on my good old Dell 380 desktop on USB stick ... don't believe one can get anything done if I stay on Windows 10 Pro. Copy or download all the possible files you need to the USB/thumb drive ahead or while connected in LInux ... go slow & a nice cup of coffee is always good to watch & sip. If you have even older hardware (just retired my 15 years old Dell Optiplex 620 MT which has been a home server) - LMDE-3 Cinnaman 32 or 64 bits (LTS) should do. Sorry, I don't have a link to any 32 bits ... just go search for it while connected.
If and when you managed to modify the HD8 and get back into Bootloader & Recovery, do not restart the device until you are certain that TWRP is up & running (whether you install & run Magisk or not, doesn't matter) Then, sideload & flash either LIneage 12 OS or the "stock" HD8 rom in this XDA thread/link - https://forum.xda-developers.com/hd...rmware-amazon-fire-hd-8-2017-douglas-t3972921
Even if you cannot do some/all of the above, the latest V8.2 Toolbox itself is pretty good - ads blocked & OTA stopped/disabled, able to install Google Apps & Play Store, etc. and Nova Laucher (I recommend & use it myself on the FD8) ... it is more responsive than Lineage (being in "beta" status) - install some apps & run it, let it update & settle down for a day or two.
Be sure to read & follow all the steps, disable WiFi & turn on Developer's Mode, enabled USB debug, etc. - then resume & do the setup after using the Toolbox.
Not bad for a $60 device that's 3+ years old, I got Youtube Vance running, Adaway installed & FB/Messenger/IG "Lite" working - use it to watch videos on a 64 GB mSD card offline, and check email & run news app ... when not using it as a security cam monitor linked to our Xiaomi & Wyze wifi cams.
Just don't feel like trading up for a $10 Amazon gift card & get the newest HD8 with 20% discount - if and it's on sale on 2020 Prime Day, I might just grab another one to play.
What do you wish, hope & expect the HD8 to do by rooting it ??
Letitride said:
Fire OS 5.6.6.0 is the newest one and my understanding is that version/release is a PITA as the "exploit" to unlock & inject the Fastboot mod is a problem .... sorry about that, maybe another XDA'er familiar with that can help walk you thru on their efforts & success (or not) i.e. whether they managed to roll it back.
I used LMDE-4 Cinnamon 64bit (d/l via Linux Mint) and it works fine on my good old Dell 380 desktop on USB stick ... don't believe one can get anything done if I stay on Windows 10 Pro. Copy or download all the possible files you need to the USB/thumb drive ahead or while connected in LInux ... go slow & a nice cup of coffee is always good to watch & sip. If you have even older hardware (just retired my 15 years old Dell Optiplex 620 MT which has been a home server) - LMDE-3 Cinnaman 32 or 64 bits (LTS) should do. Sorry, I don't have a link to any 32 bits ... just go search for it while connected.
If and when you managed to modify the HD8 and get back into Bootloader & Recovery, do not restart the device until you are certain that TWRP is up & running (whether you install & run Magisk or not, doesn't matter) Then, sideload & flash either LIneage 12 OS or the "stock" HD8 rom in this XDA thread/link - https://forum.xda-developers.com/hd...rmware-amazon-fire-hd-8-2017-douglas-t3972921
Even if you cannot do some/all of the above, the latest V8.2 Toolbox itself is pretty good - ads blocked & OTA stopped/disabled, able to install Google Apps & Play Store, etc. and Nova Laucher (I recommend & use it myself on the FD8) ... it is more responsive than Lineage (being in "beta" status) - install some apps & run it, let it update & settle down for a day or two.
Be sure to read & follow all the steps, disable WiFi & turn on Developer's Mode, enabled USB debug, etc. - then resume & do the setup after using the Toolbox.
Not bad for a $60 device that's 3+ years old, I got Youtube Vance running, Adaway installed & FB/Messenger/IG "Lite" working - use it to watch videos on a 64 GB mSD card offline, and check email & run news app ... when not using it as a security cam monitor linked to our Xiaomi & Wyze wifi cams.
Just don't feel like trading up for a $10 Amazon gift card & get the newest HD8 with 20% discount - if and it's on sale on 2020 Prime Day, I might just grab another one to play.
What do you wish, hope & expect the HD8 to do by rooting it ??
Click to expand...
Click to collapse
I wanna install custom roms to get a better experience... Thanks a lot ??.
Darklord071 said:
I wanna install custom roms to get a better experience... Thanks a lot .
Click to expand...
Click to collapse
There isn't much custom rom development going on with a years old Fire HD tablet, unless you are prepared to work on LOS's V12 beta (newest release) - which I tried briefly, which I am hoping to go back to when status is "stable". I am perfectly happy to go back to use the tablet as an always-on mini monitor for our home security cams.
Have you managed to root yours yet ??
Just FYI and as a sideload, I've been watching prices for the newest HD8 2020 (Gen 10) priced at $89.99 - with Prime Day around the corner. Well, I hit the Enter key today upon getting an alert that it's on sale at QVC for $59.99 with free standard shipping. Wiki codes & whatever - able to use a "New" code to get an additional $15 off, hence - ordered it, just a click over $50 shipped, taxes included - AND, it's bundled with a coupon for free case redemption (that's anywhere from $15 to $25) and other goodies. I should get mine by next weekend - going to have fun with the Toolbars Kit & see how far I can run with it, and see if the smart XDA'ers will find a way to root it - got another inexpensive tablet to play & watch YouTube Vanced, etc.
This post was a Mistake
Letitride said:
There isn't much custom rom development going on with a years old Fire HD tablet, unless you are prepared to work on LOS's V12 beta (newest release) - which I tried briefly, which I am hoping to go back to when status is "stable". I am perfectly happy to go back to use the tablet as an always-on mini monitor for our home security cams.
Have you managed to root yours yet ??
Just FYI and as a sideload, I've been watching prices for the newest HD8 2020 (Gen 10) priced at $89.99 - with Prime Day around the corner. Well, I hit the Enter key today upon getting an alert that it's on sale at QVC for $59.99 with free standard shipping. Wiki codes & whatever - able to use a "New" code to get an additional $15 off, hence - ordered it, just a click over $50 shipped, taxes included - AND, it's bundled with a coupon for free case redemption (that's anywhere from $15 to $25) and other goodies. I should get mine by next weekend - going to have fun with the Toolbars Kit & see how far I can run with it, and see if the smart XDA'ers will find a way to root it - got another inexpensive tablet to play & watch YouTube Vanced, etc.
Click to expand...
Click to collapse
I haven't rooted mine yet... I used the raspberry pi before??.. so I am gonna use a laptop soon... I'm only 14 yrs old???. I wanna also be a software developer when I grow up.. and my laptop is in the us and can't be delivered to me cuz of the pandemic.... Thanks a lot and I posted this question in reddit and some nice guy gave me the link for directions.. these are the instructions posted by a fellow xda'er..
Yesterday i managed to root updated FireOS and install Lineage 12.1, so, here's my story
Version 5.6.6.0 build 654620620,
on Linux KDE Neon.
Installed python3, PySerial, adb, fastboot dos2unix as described in this and other posts.
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Downloaded the following attachments from the first post : amonet-douglas-v1.2.zip and brick-douglas.zip
Extract both files to the same folder
Enable Developer options and enable ADB (inside debugging options) on Amazon tablet
Plug in the tablet (has to be turned on)
Now comes the commands execution part. So, open the terminal in Linux (lines that start with // are comments and should not be run from command line - if you copy paste)
Code:
sudo systemctl stop ModemManager && sudo systemctl disable ModemManager
Code:
adb devices
// there should be an item listed
// to be sure, you can unplug and run it again, if it's empty,
// ou know tablet can connect, so plug in the tablet back
Code:
adb reboot bootloader
// reboots the tablet and awaits commands
Code:
sudo ./brick.sh
// type YES, hit enter
// it will take a couple of minutes (around 3-5min in my case)
// watch the tablet for success message, it should be displayed there if everything works
// but also, watch your terminal...if it gives you error message similiar to:
// ==> [I][U]failed with error message that it can't write somewhere[/U][/I]
// you have to try with brick-9820 script
Code:
sudo ./brick-9820.sh
// it will take a couple of minutes, similar to above step
NOTE : after either of the above commands (which one succeeds) POWER OFF THE TABLET and DO NOT try to turn it back on. It should stay powered off!!
Code:
sudo ./bootrom-step.sh
// this will take some time (in my case around 5-10 minutes)
// will give you message similar to "awaiting device connection" and nothing else...
// although nothing seems to happen, just wait a bit and watch the terminal, it will soon start displaying the process
// it should then reboot the tablet, but in my case, that did not happen, so i had to do it manually...
// NOTE that althought tablet seems to be "off", it isn't, so press power btn and hold for 5 sec to turn it off
// after that click and hold volume up button (when in portrait mode it is the right one, the one closest to power btn)
// and immediately after that press and hold the power btn until amazon logo shows itself
// it should then show in bottom left corner HACKED FASTBOOT after a few seconds
Code:
sudo fastboot devices
// there should be a device listed
// if not, you should run (in the extracted directory that you are in):
./bin/fastboot devices
// if sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot
Code:
sudo ./fastboot-step.sh
// takes a couple of minutes (1-3 min in my case)
// reboots the device
after that you should be in TWRP
NOTE when in TWRP:
DO NOT RESTART tablet before the following
(or amazon fire os will overwrite TWRP and you will be reset to factory default with fireOS, losing everything you've done and starting from scratch...
when it happened to me, the brick-9820.sh didn't work anymore and had to use brick.sh script)
-allow modifications
-format data,system,cache partitions, go to wipe->advanced wipe-> repair/format (something like that), select each of the 3 partitions aformentioned and format to ext4
-if you've done it correctly, there should not be any red warnings
-after that go to wipe, select all partitions and wipe them (just to be sure)
-tablet should be connected and TWRP should be left on
on PC
-download Lineage 12.1 ROM from https://forum.xda-developers.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
-download opengapps from https://opengapps.org/
- put them inside amonet-douglas-v1.2 folder where you've extracted the prior ZIP files (just to be clear, you can put them anywhere, but i like to keep it all inside the working directory)
-go to terminal
Code:
adb push lineage-12.1-20200614-UNOFFICIAL-douglas.zip /sdcard
adb push open_gapps-arm64-5.1-nano-20200624.zip /sdcard
now the files are on the tablet
- in TWRP go to INSTALL, go to /sdcard folder if not in it
- first install Lineage ROM from zip
- then install GApps from zip
hope it works!
I'm glad i've finally rooted it, thank you all for the great content here!
Darklord071 said:
I haven't rooted mine yet... I used the raspberry pi before.. so I am gonna use a laptop soon... I'm only 14 yrs old. I wanna also be a software developer when I grow up.. and my laptop is in the us and can't be delivered to me cuz of the pandemic.... Thanks a lot and I posted this question in reddit and some nice guy gave me the link for directions.. these are the instructions posted by a fellow xda'er..
Yesterday i managed to root updated FireOS and install Lineage 12.1, so, here's my story
Version 5.6.6.0 build 654620620,
on Linux KDE Neon.
Installed python3, PySerial, adb, fastboot dos2unix as described in this and other posts.
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Downloaded the following attachments from the first post : amonet-douglas-v1.2.zip and brick-douglas.zip
Extract both files to the same folder
Enable Developer options and enable ADB (inside debugging options) on Amazon tablet
Plug in the tablet (has to be turned on)
Now comes the commands execution part. So, open the terminal in Linux (lines that start with // are comments and should not be run from command line - if you copy paste)
Code:
sudo systemctl stop ModemManager && sudo systemctl disable ModemManager
Code:
adb devices
// there should be an item listed
// to be sure, you can unplug and run it again, if it's empty,
// ou know tablet can connect, so plug in the tablet back
Code:
adb reboot bootloader
// reboots the tablet and awaits commands
Code:
sudo ./brick.sh
// type YES, hit enter
// it will take a couple of minutes (around 3-5min in my case)
// watch the tablet for success message, it should be displayed there if everything works
// but also, watch your terminal...if it gives you error message similiar to:
// ==> [I][U]failed with error message that it can't write somewhere[/U][/I]
// you have to try with brick-9820 script
Code:
sudo ./brick-9820.sh
// it will take a couple of minutes, similar to above step
NOTE : after either of the above commands (which one succeeds) POWER OFF THE TABLET and DO NOT try to turn it back on. It should stay powered off!!
Code:
sudo ./bootrom-step.sh
// this will take some time (in my case around 5-10 minutes)
// will give you message similar to "awaiting device connection" and nothing else...
// although nothing seems to happen, just wait a bit and watch the terminal, it will soon start displaying the process
// it should then reboot the tablet, but in my case, that did not happen, so i had to do it manually...
// NOTE that althought tablet seems to be "off", it isn't, so press power btn and hold for 5 sec to turn it off
// after that click and hold volume up button (when in portrait mode it is the right one, the one closest to power btn)
// and immediately after that press and hold the power btn until amazon logo shows itself
// it should then show in bottom left corner HACKED FASTBOOT after a few seconds
Code:
sudo fastboot devices
// there should be a device listed
// if not, you should run (in the extracted directory that you are in):
./bin/fastboot devices
// if sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot
Code:
sudo ./fastboot-step.sh
// takes a couple of minutes (1-3 min in my case)
// reboots the device
after that you should be in TWRP
NOTE when in TWRP:
DO NOT RESTART tablet before the following
(or amazon fire os will overwrite TWRP and you will be reset to factory default with fireOS, losing everything you've done and starting from scratch...
when it happened to me, the brick-9820.sh didn't work anymore and had to use brick.sh script)
-allow modifications
-format data,system,cache partitions, go to wipe->advanced wipe-> repair/format (something like that), select each of the 3 partitions aformentioned and format to ext4
-if you've done it correctly, there should not be any red warnings
-after that go to wipe, select all partitions and wipe them (just to be sure)
-tablet should be connected and TWRP should be left on
on PC
-download Lineage 12.1 ROM from https://forum.xda-developers.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
-download opengapps from https://opengapps.org/
- put them inside amonet-douglas-v1.2 folder where you've extracted the prior ZIP files (just to be clear, you can put them anywhere, but i like to keep it all inside the working directory)
-go to terminal
Code:
adb push lineage-12.1-20200614-UNOFFICIAL-douglas.zip /sdcard
adb push open_gapps-arm64-5.1-nano-20200624.zip /sdcard
now the files are on the tablet
- in TWRP go to INSTALL, go to /sdcard folder if not in it
- first install Lineage ROM from zip
- then install GApps from zip
hope it works!
I'm glad i've finally rooted it, thank you all for the great content here!
Click to expand...
Click to collapse
Dude! Thank you so much for sharing this, I've spent hours looking for a solution and I'll certainly give this a go when I next get the opportunity. Literally I exhausted all my efforts to the point where I posted a question a couple of days ago (https://forum.xda-developers.com/showpost.php?p=83638279&postcount=584). Fingers crossed your very helpful reply will help me see an end to this painful process!
lmao
andyboot said:
Dude! Thank you so much for sharing this, I've spent hours looking for a solution and I'll certainly give this a go when I next get the opportunity. Literally I exhausted all my efforts to the point where I posted a question a couple of days ago (https://forum.xda-developers.com/showpost.php?p=83638279&postcount=584). Fingers crossed your very helpful reply will help me see an end to this painful process!
Click to expand...
Click to collapse
LMAO. No problem
btw it worked for other ppl so, it will definitely work for you!
Darklord071 said:
LMAO. No problem
btw it worked for other ppl so, it will definitely work for you!
Click to expand...
Click to collapse
Quick update, worked like a charm! Thanks once again!
WORKED!!
andyboot said:
Quick update, worked like a charm! Thanks once again!
Click to expand...
Click to collapse
tried it yesterday.. IT WORKED!!!
Just wanted to add another confirmation that these steps worked. Its hard finding the correct info for such an old device and so much out of date guides, but this worked like a charm.
thetakerfan said:
Just wanted to add another confirmation that these steps worked. Its hard finding the correct info for such an old device and so much out of date guides, but this worked like a charm.
Click to expand...
Click to collapse
Hit the thanks button if you want to!
Thanks Darklord071. Worked like a charm.
I guess LineageOS 12.1 is the best we can get huh? it's showing Android 5.1.1.
Some apps are not compatible with those old Android versions. Oh well.