/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/status
/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/capacity
/sys/class/leds/green/brightness
/sys/class/leds/red/brightness
I need someone to verify if these directories/files exist on the MT2-L03 variant. I plan to add LED charging support to the TWRP recovery. I don't have the device on me at the moment so please let me know. If they are there then please open each file on your device with a text editor of some sort while the device is not plugged up. Take note on what they say, then plug your device up and take note on what they change too. This information would be greatly appreciated. If the directories to do not exist then please seek to find the ones which are equivalent. I'm at work so can't do this myself at the moment. The LED support will basically show your LED light up if charging your device while in TWRP. No light would mean you aren't charging obviously while the red light means charging and the green light means charge is full. Would be a nice cosmetic feature to add as well as comfort in knowing your device is actually charging when plugged up by the LED light as seen in your daily Rom too. @xordos, maybe you can assist me here.
Modding.MyMind said:
/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/status
/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/capacity
/sys/class/leds/green/brightness
/sys/class/leds/red/brightness
I need someone to verify if these directories/files exist on the MT2-L03 variant. I plan to add LED charging support to the TWRP recovery. I don't have the device on me at the moment so please let me know. If they are there then please open each file on your device with a text editor of some sort while the device is not plugged up. Take note on what they say, then plug your device up and take note on what they change too. This information would be greatly appreciated. If the directories to do not exist then please seek to find the ones which are equivalent. I'm at work so can't do this myself at the moment. The LED support will basically show your LED light up if charging your device while in TWRP. No light would mean you aren't charging obviously while the red light means charging and the green light means charge is full. Would be a nice cosmetic feature to add as well as comfort in knowing your device is actually charging when plugged up by the LED light as seen in your daily Rom too. @xordos, maybe you can assist me here.
Click to expand...
Click to collapse
/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/status & /sys/devices/platform/bq_bci_battery.1/power_supply/Battery/capacity do not exist. I don't see any other similar looking folders in /sys/devices/platform/ so far. Will update if I do.
/sys/class/leds/green/brightness & /sys/class/leds/red/brightness do exist. Both files just say "0" (Zero) when not plugged in, and "255" while plugged in.
ScoobSTi said:
/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/status & /sys/devices/platform/bq_bci_battery.1/power_supply/Battery/capacity do not exist. I don't see any other similar looking folders in /sys/devices/platform/ so far. Will update if I do.
/sys/class/leds/green/brightness & /sys/class/leds/red/brightness do exist. Both files just say "0" (Zero) when not plugged in, and "255" while plugged in.
Click to expand...
Click to collapse
Thanks, worse case I will have to get the information when I get off of work later on this evening. Thanks man for letting me know on the other two. Will have this patched up before today is over with and send a pull request to Dees_Troy so it will be implemented in all future releases. I already added LED support to my primary device and I was so fond over it's cosmetic view and the comfort of knowing that my device is actually plugged up; I decided I would do the same for this phone as well. I also plan to add this to my Wifes TWRP on her HTC EVO Design 4g.
ScoobSTi said:
/sys/devices/platform/bq_bci_battery.1/power_supply/Battery/status & /sys/devices/platform/bq_bci_battery.1/power_supply/Battery/capacity do not exist. I don't see any other similar looking folders in /sys/devices/platform/ so far. Will update if I do.
/sys/class/leds/green/brightness & /sys/class/leds/red/brightness do exist. Both files just say "0" (Zero) when not plugged in, and "255" while plugged in.
Click to expand...
Click to collapse
@ScoobSTi, when you get the chance, can you run the following command to see where those two files actually are located at on the device. I believe they are symlinked given the paths I mentioned previously and would prefer to have their absolute paths without symlinks.
busybox readlink -f /sys/class/leds/red/brightness
busybox readlink -f /sys/class/leds/green/brightness
Copy and paste here what each command returns with.
Modding.MyMind said:
@ScoobSTi, when you get the chance, can you run the following command to see where those two files actually are located at on the device. I believe they are symlinked given the paths I mentioned previously and would prefer to have their absolute paths without symlinks.
busybox readlink -f /sys/class/leds/red/brightness
busybox readlink -f /sys/class/leds/green/brightness
Copy and paste here what each command returns with.
Click to expand...
Click to collapse
"busybox readlink -f /sys/class/leds/red/brightness" = /sys/devices/leds-qpnp-f5d1b800/leds/red/brightness
"busybox readlink -f /sys/class/leds/green/brightness" = /sys/devices/leds-qpnp-f5d1b600/leds/green/brightness
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OK, @ScoobSTi, just need one more verification.
readlink -f /sys/class/power_supply/battery/status
results?
Once I have this I can complete the update to the device tree.
Modding.MyMind said:
OK, @ScoobSTi, just need one more verification.
readlink -f /sys/class/power_supply/battery/status
results?
Once I have this I can complete the update to the device tree.
Click to expand...
Click to collapse
Result: /sys/devices/qpnp-charger-f5d1b000/power_supply/battery/status
ScoobSTi said:
Result: /sys/devices/qpnp-charger-f5d1b000/power_supply/battery/status
Click to expand...
Click to collapse
Building now. Thanks for your assistance bro. Greatly appreciated.
Modding.MyMind said:
Building now. Thanks for your assistance bro. Greatly appreciated.
Click to expand...
Click to collapse
It's nothing lol, just simple stuff. Thank you for working on this phone!
ScoobSTi said:
It's nothing lol, just simple stuff. Thank you for working on this phone!
Click to expand...
Click to collapse
@xordos, @superbass311, Need a quick test to confirm that the LED light works while in TWRP Recovery before I send a pull request to Dees_Troy for future builds.
Unzip the attachment, flash the recovery.img to the recovery partition. Boot up in TWRP.
1. Confirm that the LED light on the device is not on while device is not plugged in to any electrical sources.
2. Confirm that the LED light on the device is on while the device is plugged in to any electrical sources.
2a. Red light means battery is charging but is not full
2b. Green light means it is "charging" but the battery is full
ATTACHMENT REMOVED BY ME
I can until tonight. But will do. driving...
not working here
more info:
reverted to stock recovery
reboot
confirm stock
fastboot flash recovery.img
reboot
confirm twrp
no led lights plugged or unplugged
Just remembered I never flashed TWRP (still), so I can't help with this, at least not yet.
Sent from my MT2L03 using XDA Free mobile app
Iguanadon said:
not working here
more info:
reverted to stock recovery
reboot
confirm stock
fastboot flash recovery.img
reboot
confirm twrp
no led lights plugged or unplugged
Click to expand...
Click to collapse
Thanks, will take a look at the C file to see what modification is needed.
ROUND 2!
@Iguanadon, if you are up for it, I made a fix and applied a change to the init.rc file. Should work now. Check attachment below to download. Same instructions as before.
Attachment removed by me
followed my same procedure with same results. sorry to say still no led. i'm up for more tests if needed.
Iguanadon said:
followed my same procedure with same results. sorry to say still no led. i'm up for more tests if needed.
Click to expand...
Click to collapse
Well that is disappointing :-/. Only thing left is to make sure I didn't overlook any files. C file us good to go. Binary must not be getting called properly while in TWRP.
Iguanadon said:
followed my same procedure with same results. sorry to say still no led. i'm up for more tests if needed.
Click to expand...
Click to collapse
Using the build I made, can you boot up in to TWRP then go to "advanced" and select "copy log to sdcard". Then boot back in to your system, open up the recovery.log file and copy paste it all here for me so I can see if anything is out of the ordinary.
sent pm not sure how to do spoiler
Iguanadon said:
sent pm not sure how to do spoiler
Click to expand...
Click to collapse
init.svc.chargeled=running (this is what I was looking for).
The binary is working like it is suppose to so this is good news. It means that the paths being used to find the leds on the device is not completely accurate so I got to take a deeper look in to the phone. Thanks man for your help.
Related
####NO LONGER SUPPORTED####
Links have been updated to the last release and are working
###############################
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The NookBuntu Dev Team
devastatorx | penkia | lincore | munday | luciferii
CREDITS: munday for his initial work on this project, penkia for the wifi and touchscreen fixes. The guys who pulled off the vnc trick to get us thinking about how to make this a full fledged linux tablet. All the great developers for the nook and every other device.
*DISCLAIMER*
I'm not responsible, blah blah blah...if you are trying this...your warranty cherry was popped long ago
Q & A - This area will be updated as questions arise
Q: Why the skip from alpha 0.1 to beta 0.3?
A: Alot of testing and fixes were implemented behind the scenes. These images were not released due to usability issues. We wanted this release to be one that could serve as a daily build. And this comes relatively close.
Q: Will this mess up my current configuration?
A: If your current configuration runs from the eMMC, then no. It runs solely from the uSD card. As long as you don't mount your eMMC inside NookBuntu and start messing around with it, it should be fine.
Q: Is this awesome?
A: Yes, it is so awesome that if I were to speak anymore than a few lines about it's awesomeness, computers would become self aware, sheep would begin counting people, and pong would turn into tetris...
Q: Will this run from the internal memory?
A: This is being planned for a future release and currently only runs from the SD card. DO NOT FLASH IT TO THE eMMC!!!
A NOTE ABOUT DONATIONS - Please read
No we do not ask for donations or accept them. We do this because we are as passionate as anyone in this communtiy about the tech we use.
If you would like to donate, please instead consider donating to the following charity
The National Breast Cancer Foundation - https://www.nationalbreastcancer.org/donate/
My sister was recently diagnosed with stage 3 breast cancer. I ask that if you do wish to donate, please do so in her honor. If you wish to make a donation in her honor please pm me for details (name and whatnot). Thank you!
################################
NookBuntu Beta 0.3
################################
Screens
Working
Boot into NookBuntu when the device is powered on (no adb necessary!)
Network manager - this is still being worked on, use the method listed in the instructions below
Touch screen
On screen keyboard auto slide out on text input area focus
Audio
Not Working
Home button
Volume buttons
Multi-touch
Bluetooth
Hardware acceleration
Accelerometer
Charging
Installation instructions
DOWNLOADS
NookBuntu Beta 0.3 - Download
md5: bfe2206fbfd7f402cd1c95c61b13dc83
NookBuntu Boot Partition - Download
md5: 316f8d6d44cb3d2c4a13f01da63c302e
We will need to make a bootable SD card for this. As of right now I have an 8gb card and will be uploading a burnable image soon...but for now this method will work.
Download this script and save it somewhere you have easy access to.
Download: SDMAKER
Ok so you have all the files right? Right?? ...right
Let's get that SD card prep'd for our NookBuntu installation.
1) Open up a terminal and cd to where you saved the file sdmaker.sh
2) Insert your soon to be nookbuntu sd card into your pc and find out where your sd card is mounted i.e. /dev/mmcblk0 or wherever. REMEMBER what it was (for me it is /dev/mmcblk0)
3) Type the following command hitting enter after each line
Code:
sudo chmod +x sdmaker.sh
sudo ./sdmaker.sh /dev/yoursdcard
4) Let this command run and finish out, it is formatting your sd card to correctly have a boot and filesystem partitions
5) Once this has finished you should have two new partitions show up, either mounted already at /media/boot and /media/Angstrom or should be able to mount the new partitions in your file manager. If they aren't mounted go ahead and mount them.
Let's regather. You have two folders open on your desktop, one titled "boot" and the other titled "Angstrom". Are you with me? Good.
6) Untar/7zip/Unzip whatever...decompress the file nookbuntu-0.3beta.tgz anywhere you would like.
7) cd to the directory where you extracted the files. There should be a folder titled "system" Go ahead and cd into that directory.
8) Now we need to copy all of the contents to the Angstrom partition on your SD card
Code:
sudo cp -r * /media/Angstrom
This will take awhile, get something to drink.
9) After that has finished lets copy over the boot partition. Go to where you downloaded the file "nookbuntu-boot.7z" and extract it. Now CD to nookbuntu-boot. Are you with me? Let's copy those files over!
Code:
sudo cp -r * /media/boot
10) After that has finished we need to setup your wifi so it will work. So let's edit the one of the files we just put on your sdcard (use whatever text editor you would like:
Code:
sudo gedit /media/Angstrom/etc/wifi/w2.conf
In your text editor you will have something like this:
Code:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="WiFiNetworkName"
scan_ssid=1
key_mgmt=WPA-PSK
psk="yourWPAkey"
}
We need to change a few things to be able to connect to your home wifi.
Change the following:
Code:
ssid="WifiNetworkName"
to
ssid="YourSSID"
Obviously replace "YourSSID" with whatever your actual SSID is.
Chances are you are using WPA encryption...well if you aren't...you should be. Assuming you are we need to set up so we can send the key to the router when we connect.
See this line?
Code:
psk="yourWPAkey"
Change "yourWPAkey" to...you guessed it....your WPA password
Save the changes and exit.
11) Unmount the sdcard from your computer
Code:
sudo umount /media/boot
sudo umount /media/Angstrom
12) Take the Sd card and put it in your nook while it is powered off.
13) Power on your nook and give it a few mins...voila! NookBuntu should have loaded!
These next steps are for getting wifi up and running you can do this from an ADB shell or from the terminal inside NookBuntu or make it into a script for future use.
Enter these commands (hitting enter after each line unless otherwise noted)
Code:
killall wpasupplicant
ifconfig tiwlan0 up
killall connmand
wpa_supplicant -Dwext -i tiwlan0 -c /etc/wifi/w2.conf & dhclient
You should shortly be associated to your home network!
Enjoy NookBuntu! Make sure to thank all the great devs who have a hand in this project!
-devastatorx
Change log
Beta 0.3
Network Manager (semi working at the moment, should be fixed in next release) - penkia
Audio Working - devastatorx
On screen keyboard when focusing on a text input area - penkia
Boot into X when the device is powered on - Lincore
New base image - devastatorx & penkia
**reserved too
Wow, going to bed tonight, but I am definitely trying this tomorrow, I hope this is inevitably usable on the nook color, that steps up it's usability as a tablet.
Just a suggestion for the Mods, we should have a second forum for ubuntu on the Nook, that way it doesn't clutter up the android development and then it can expand and be organized for developers of linux vs android, might draw some more interest into this!
Honestly can't wait to try this though, good work
Holy ****, it finally happened. Downloading now!
It's gonna be a loooong day at work today of not doing any work and messin' with my nook!
Thanks for this!
Racks
I'm going to wait a bit before giving this a shot, but seriously, thanks! I'm excited about the possibilities. Do you think our hardware will be prohibitive to using this in the long-run? I know it's really early, so if that's a silly question, feel free to disregard it.
junkrobot said:
I'm going to wait a bit before giving this a shot, but seriously, thanks! I'm excited about the possibilities. Do you think our hardware will be prohibitive to using this in the long-run? I know it's really early, so if that's a silly question, feel free to disregard it.
Click to expand...
Click to collapse
At this stage it is difficult to say as not everything is working (no hardware acceleration, sound, etc)
As of right now the device runs pretty smoothly for what it is and is more responsive than it was when using the vnc method. I will be working more on the build this weekend and hope to establish a development team to keep things moving forward with consistant fixes and updates.
With a good, dedicated development team we should make some exciting progress in the near future.
Sent from my PC36100 using XDA App
I think it'll be good to note what's not working on the initial post, that way if a dev wants to help, at least they know what to look for and try to solve
racks11479 said:
It's gonna be a loooong day at work today of not doing any work and messin' with my nook!
Thanks for this!
Racks
Click to expand...
Click to collapse
I thought I was the only playing with my nook at work, now I don't feel so bad. haha.
@devastatorx, you are the man!!! Thanks so much, I can't wait to try this out.
So this is actually an Angstrom distro?
bassrebel said:
I think it'll be good to note what's not working on the initial post, that way if a dev wants to help, at least they know what to look for and try to solve
Click to expand...
Click to collapse
I will update the OP. I just wrote it last night at about. 12:30am and then let the file upload over night and hit post on my way out the door this morning. So it was a little rushed.
Sent from my PC36100 using XDA App
starkruzr said:
So this is actually an Angstrom distro?
Click to expand...
Click to collapse
Negative. This is a ububtu installation. The script just names that partition "Angstrom".
Sent from my PC36100 using XDA App
Ubuntu 10 or 11? Unity would be most worthwhile for our devices . And bugger all, I guess I'm going to have to pick a new microSD.
Ubuntu 10. As of right now there are some path issues so I am unable to get the unity-2d gui to load. Will have this fixed in the next release.
Sent from my PC36100 using XDA App
Ophbalance said:
Ubuntu 10 or 11? Unity would be most worthwhile for our devices . And bugger all, I guess I'm going to have to pick a new microSD.
Click to expand...
Click to collapse
Unity would be rather nice. Especially if we can get GPU acceleration working.
Perhaps this is a silly question, but... have you given any thought to packaging updates in some form that doesn't require downloading the entire distribution again? Yes, I can see there being issues if you don't apply them sequentially if it comes out in a zip of some kind... but it'd save you/us a ton of bandwidth. Maybe if it's all in SVN or GIT?
I'm stuck here:
Code:
sudo cp -r * /media/boot
It says "/media/boot" is no directory
MAD PROPS keep up the good work this is what android is all about might have to buy another nook color one to install in the car and one to use every where else .
Arbelzapf said:
I'm stuck here:
Code:
sudo cp -r * /media/boot
It says "/media/boot" is no directory
Click to expand...
Click to collapse
What OS are you using? The drive may be mounted elsewhere and my instructions are based off of the drives first partition being mounted at "/media/boot" and the second partition mounted at "/media/Angstrom". If this is not where the partitions are mounted then adjust the instructions for where you have them mounted or remount the device's partitions to these folders.
This should help...but I'm not saying this to be a jerk or anything...this is an Alpha and is in no way intended for daily use. Only those comfortable in Linux, and feeling adventurous should give this a go. Future releases (beta and onward) should be stable enough and easy enough to install for daily use.
To address the updates question:
I may implement a kind of crude package system after I get to a stable enough release to call it a beta. Such packages will include the modified system files and an install script to set the new update up. But like I said, that probably won't be until beta.
Hey all, I thought I would put together a quick guide on how to port modules built for other devices. Since we share the same CPU as the One X and many other phones it's possible some of the mods for them are compatible with our phones too. In this case I was wanting to give coolbho3000's overclock module a try to see if it would work.
Please keep in mind that this will not always work and it's still better to try and use a module built specifically for your setup. Using a module that's not made for your device can cause all kinds of issues and seriously affect system stability. Always make sure you read the original instructions to make sure you understand how it works and how it's intended to be used.
Neither me, XDA or the module's author are responsible for anything that happens to your device. You and you alone are responsible for your actions.
First thing you'll want to do is try to load it as is, it probably won't work but it'll at least give you a place to start. In this case I'm using the overclock module from the One X so I used:
Code:
adb push krait_oc.ko /data/local/krait_oc.ko
adb shell
su
insmod /data/local/krait_oc.ko
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it is successful it won't say anything, but there you can see it failed as expected. In order to find out why it failed we'll need to run dmesg and look for where it tried to load it.
Code:
dmesg | grep "krait_oc"
There we can see module_layout is where the issue is. What we can do now is pull one of the already installed modules off of the device and use it as a reference, in this case I used lcd.ko since it has an easy name to type. Grab your two modules and using linux run modprobe to find a value for module_layout. (If you only have Windows available skip to next step)
Code:
modprobe --dump-modversions lcd.ko
Now that we know what to look for open up the module in a hex edit and search for "module_layout." Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Change those four bytes to match and then save the module under a new name so it is not confused with the original.
Once you save the edited module its time to push it to the device again and try once more.
And success! Sometimes you'll also need to edit the module to accept the current kernel version you are using, but the process should be similar as to what's here.
So, uhhhh . . . you gonna share that modded kernel?
utnick said:
So, uhhhh . . . you gonna share that modded kernel?
Click to expand...
Click to collapse
Kernel is still the same, this is just for the modules
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Got overclock working fine. Great thanks Haus
Can anyone make a zip? Pretty please.
You can't make a zip. you have to mod the ko file yourself and launch it yourself.
utnick said:
*sigh* I wish I knew what that meant. Can I ask to you to explain it to me please? And does this mean you have the ability to port the kernel to OC an EVO LTE?
Click to expand...
Click to collapse
Think of modules as sort of like an add-on for kernels, except that they're saved as part of the ROM instead of on boot. I used the one-x overclock module here, but since it's not made for the evo it may not be completely stable. Plus there are other changes that need to be made to the thermal profiles according to his original post.
Ideally coolbho3000 will be willing to create one for us and officially support it. I've already reached out to him about it so hopefully we'll hear something back soon.
Hey I know quadrants don't mean much but do you think you could get us a screenshot of our phones scores when overclocked?
Thanks for the guide by the way I will definitely try this when I have time...
Red.
So glad you're here haus :thumbup:
Sent from my EVO using xda premium
it there a way to remove a module, and replace a new edited ported *.ko?
all of this is done in recovery?
if trying to replace a module should just get to modding the kernel itself?
Great guide, I've been looking for something like this. So could I use this method to get USB hosting working? I know the one x (AT&T), has a custom kernel that supports it.
XDA University is Coming! Can't wait to learn more...
Immediately before it you will see the value that needs to be changed, but, keep in mind that it is little endian so the bytes are read backwards. In the view of lcd.ko on the right you can see the value we previously got of '37 19 bc d3' is saved as 'd3 bc 19 37'.
Click to expand...
Click to collapse
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
exSD said:
That's not little endian and reading backwards is not little endian when the original is not big endian. Little/big endians are in terms of byte size orders.
Good tutorial.
Click to expand...
Click to collapse
Thank you, but "byte size orders?"
xHausx said:
Thank you, but "byte size orders?"
Click to expand...
Click to collapse
Byte value order. Hex value.
thanks a lot
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
hackerse7en said:
thanks a lot for your tutorial, and congrats,
i tried your tutorial and i cant modprob on linux, i atached the screenshot of what happenz,
i try "modprobe --dump-modversions usbhid.ko" and i receive a blank line with nothing, i tried with other modules and it do the same, but for the one who was extracted from my phones modules folder, it works,
and i also have a daught, i search for "module_layout" only or any other values?
Click to expand...
Click to collapse
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
xHausx said:
Make sure you have spaces between your arguments. It also depends on what value it's telling you is incorrect, it may be different depending on which one you're trying to use.
Click to expand...
Click to collapse
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
hackerse7en said:
i already did that i think itś something wrong with the module because i put them i the same directory and the exact same commands and it just dont work, i atached some screenshots and the modules.
thanks for helping me
Click to expand...
Click to collapse
i just cant undestand, if someone can help me.
Hi everyone
My phone screen is completely smashed but it appears that the phone can still turn on. I've connected it to the laptop and it seems to connect (installing driver, etc) but it doesnt come up on windows explorer. Presumably because the phone is encrypt + PIN locked. I tried tapping randomly on the phone screen but my guess is that it is not registering but even if it is it would be impossible to get the right decryption code in.
1. Is there a way to display the screen output either on TV / Monitor / Computer ?
2. Even better can I get the display replicated on the laptop with a USB connection and navigate through that
I suspect the answer to all of this is no and I just have accept the photos are gone. Any ideas are welcome.
Thanks for reading
yeancheant said:
Hi everyone
My phone screen is completely smashed but it appears that the phone can still turn on. I've connected it to the laptop and it seems to connect (installing driver, etc) but it doesnt come up on windows explorer. Presumably because the phone is encrypt + PIN locked. I tried tapping randomly on the phone screen but my guess is that it is not registering but even if it is it would be impossible to get the right decryption code in.
1. Is there a way to display the screen output either on TV / Monitor / Computer ?
2. Even better can I get the display replicated on the laptop with a USB connection and navigate through that
I suspect the answer to all of this is no and I just have accept the photos are gone. Any ideas are welcome.
Thanks for reading
Click to expand...
Click to collapse
Mini hdmi. If your screen is unresponsive though there isn't much point.
Sent from Jelly Fuelled SGS2
Screen is smashed pretty bad though - don't think it is going to work. Will the mini hdmi work without the phone turn on pass the decryption password stage. Thanks for your help
yeancheant said:
Screen is smashed pretty bad though - don't think it is going to work. Will the mini hdmi work without the phone turn on pass the decryption password stage. Thanks for your help
Click to expand...
Click to collapse
Really unsure. I use cm10 so tv out is unsupported but the mini hdmi cables can be picked up on ebay pretty cheap.
Sent from Jelly Fuelled SGS2
theres not much you can do if you got a pin or screen security.did you enable usb debugging?
Do full wipe try to look into pictures of recovery.
Send form Galaxy S2. Using XDA Premium
If you had USB debugging enabled, then you can easily use ADB to copy out your files
Paulius7 : what do you mean by full wipe - I can't see anything on the screen at the moment
Jokesy: The phone is probably stuck at the password to decrypt in which case I suspect adb wouldn't work. I haven't used that before but might give it a go
Thanks for all the suggestions
yeancheant said:
Paulius7 : what do you mean by full wipe - I can't see anything on the screen at the moment
Jokesy: The phone is probably stuck at the password to decrypt in which case I suspect adb wouldn't work. I haven't used that before but might give it a go
Thanks for all the suggestions
Click to expand...
Click to collapse
Did you have USB debugging enabled?
We can still access adb via CWM recovery
I said. You can look into pictures if you can reach CWM(recovery mode)
Full wipe-Is Clean everything but not pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Paulius7 : The screen is smashed - so I can't really get into CWM - unless I do it blindly and then guess the number of clicks to eventually do full wipe. But I don't understand how full wipe can help "Do full wipe try to look into pictures of recovery. "
Jokesy: I installed resurrection remix - don't know if USB debug is enabled by default. Either way I'm going to download the android sdk and give it ago and see .
yeancheant said:
Paulius7 : The screen is smashed - so I can't really get into CWM - unless I do it blindly and then guess the number of clicks to eventually do full wipe. But I don't understand how full wipe can help "Do full wipe try to look into pictures of recovery. "
Jokesy: I installed resurrection remix - don't know if USB debug is enabled by default. Either way I'm going to download the android sdk and give it ago and see .
Click to expand...
Click to collapse
ICS or Jelly bean?
also its ICS
Somehow my previous entry didn't stick.
So .. the good news is usb debug is on. Downloaded android sdk and java. I'm new at this and this is what happened
adb devices - found the phone
adb shell - got in with root
ls /sdcard/ - empty! presumably due to the encryption or PIN
tried it on the new replacement S3
ls /sdcard/ - all the files came out
any ideas ? I appreciate your help Jokesy and we have seen progress although I accept that the chance of reaching our end point still remains low
yeancheant said:
Somehow my previous entry didn't stick.
So .. the good news is usb debug is on. Downloaded android sdk and java. I'm new at this and this is what happened
adb devices - found the phone
adb shell - got in with root
ls /sdcard/ - empty! presumably due to the encryption or PIN
tried it on the new replacement S3
ls /sdcard/ - all the files came out
any ideas ? I appreciate your help Jokesy and we have seen progress although I accept that the chance of reaching our end point still remains low
Click to expand...
Click to collapse
no that's because /sdcard is not mounted.
follow this tutorial
Boot to recovery, then follow these steps:
1. Connect your device to your pc
2. Open command prompt from Adb folder. (hold shift key, then right click on a blank space, select open command window here)
3. #check if your device is connected via adb by typing in the command window:
adb devices
4. adb shell
5. mount sdcard
6. ## check the directories of the sdcard just to be sure by typing:
ls /sdcard
7. exit
8. adb pull /sdcard \mysdcard
wait for the process to finish
Check you C: drive for a folder named "mysdcard". all the files and folders in your internal storage will be there.
If you face any errors, let me know
Good luck
doesn't seem to work
tried mount sdcard and mount /sdcard and mount /sdcard/
it says mount:can't read 'etc/fstab': No such file or directory
yeancheant said:
doesn't seem to work
tried mount sdcard and mount /sdcard and mount /sdcard/
it says mount:can't read 'etc/fstab': No such file or directory
Click to expand...
Click to collapse
what kernel were you running before your screen broke?
default resurrection remix during the installation - i think its siyah
yeancheant said:
default resurrection remix during the installation - i think its siyah
Click to expand...
Click to collapse
were you using adb from recovery?
probably not earlier. i've tried again - blindly getting into recovery - and i think i did as windows then say installing adb driver - but now when you do "ls" there is no sdcard. tried mount sdcard and the same error message
To start off, credit goes to @GioBozza, @CappyT, @pioccd, @TotemFallico, @SimoIanni. They made this mod. All I did was port it to the V20.
ORIGINAL THREAD (go drop a "Thanks"): https://forum.xda-developers.com/nexus-6p/development/wakeblock-blocking-drain-late-t3526313
Next, some caveats:
Neither I nor the users mentioned above take any responsibility for anything that goes wrong with you installing this.
I have personally tested this on the H918 on the 10k firmware. I see no reason for it not to work on other variants, BUT MAKE BACKUPS!!!
This mod is unofficial, and will remain so, meaning I may not be able to update it for every release, whether that be a new Android version for the V20, or a new mod version.
This is for STOCK ONLY.
This mod requires ROOT.
Again, MAKE BACKUPS!!!!!!!!!
Instructions (READ THROUGH THEM FIRST):
Backup `/system/framework/services.jar` and `/system/framework/oat/arm64/services.odex` (The latter is only relevant for ODEXed ROMs).
Download and install the app from the linked thread.
Download the `services.jar` file attached or linked in this post.
Copy it to your device somewhere safe (such as `/sdcard/`).
Use either the command line or a root file explorer to copy the downloaded JAR to `/system/framework/`, overwriting the current one. (YOU MADE A BACKUP, RIGHT?)
Make sure its permissions are set to 0644 (rw-r--r--).
Use either the command line or a root file explorer to delete the `services.odex` file that you made a backup of I'm sure C_C.
Reboot.
(If you have TWRP 3.1.1-1, you'll have to keep the backups on your device somewhere, since it doesn't support MTP right now!)
If all went well, your phone will boot successfully and you'll have some pretty fine control over your wakelocks. If not, restore your backups using the TWRP file manager and try again.
If you have any questions about the installation process, ask here. Otherwise, ask on the linked thread.
Nice job!
Good job everyone!
Sent from my LG-US996 using Tapatalk
Excellent work! Been hoping this would get unoffiical support.
Edit: Damn, doesn't seem to boot on NotSoStock for the H918. I wonder if Tilde changed something in services.jar
@Zacharee1 nice find.
What are you using to compare before and after results of the mod?
Using the link you posted and github I've added the the mod to my rom all seems well but not sure which app will measure this best?
Also is there an app or something you are using to control which wakelock you want to block?
I tried the playstore version, but says device not supported...
Either way it doesn't seem to have any negative effects so far so I guess I'll just wait for a few days to see if there are any noticeable improvements...
Thanks for your work and contributions to this community!
Hopefully you'll still be using this device by time I finally go public with oZoP! Hopefully soon, but can't really say how much longer. Still many, many hours
stangdriver44 said:
@Zacharee1 nice find.
What are you using to compare before and after results of the mod?
Using the link you posted and github I've added the the mod to my rom all seems well but not sure which app will measure this best?
Also is there an app or something you are using to control which wakelock you want to block?
I tried the playstore version, but says device not supported...
Either way it doesn't seem to have any negative effects so far so I guess I'll just wait for a few days to see if there are any noticeable improvements...
Thanks for your work and contributions to this community!
Hopefully you'll still be using this device by time I finally go public with oZoP! Hopefully soon, but can't really say how much longer. Still many, many hours
Click to expand...
Click to collapse
I'm using Wakelock Detector Free to see which wakelocks are still happening. Some of them can't be blocked without causing systwm_server to continually crash, so you have to be careful.
The core kid is unsupported on this phone, not the app. If you swipe to the wakelocks tab, you should see a bunch.
I'm going to be on this phone for at least 2 years, so no worries there.
Aaren11 said:
Excellent work! Been hoping this would get unoffiical support.
Edit: Damn, doesn't seem to boot on NotSoStock for the H918. I wonder if Tilde changed something in services.jar
Click to expand...
Click to collapse
Did you set the permissions correctly?
d
stangdriver44 said:
@Zacharee1 nice find.
What are you using to compare before and after results of the mod?
Using the link you posted and github I've added the the mod to my rom all seems well but not sure which app will measure this best?
Also is there an app or something you are using to control which wakelock you want to block?
I tried the playstore version, but says device not supported...
Either way it doesn't seem to have any negative effects so far so I guess I'll just wait for a few days to see if there are any noticeable improvements...
Thanks for your work and contributions to this community!
Hopefully you'll still be using this device by time I finally go public with oZoP! Hopefully soon, but can't really say how much longer. Still many, many hours
Click to expand...
Click to collapse
Hi, the playstore app says "Unsupported" because it checks for official build of WakeBlock, now I am on DU wich is Unofficially supported and my home screen looks like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If yours looks like this too you can proceed blocking wakelocks. Please refeer to this thread to see which wakelocks to block(remember that the WakeBlock app asks for the block time in milliseconds so you need to add 3 zeros to the guide's times)
SimoIanni said:
d
Hi, the playstore app says "Unsupported" because it checks for official build of WakeBlock, now I am on DU wich is Unofficially supported and my home screen looks like this
If yours looks like this too you can proceed blocking wakelocks. Please refeer to this thread to see which wakelocks to block(remember that the WakeBlock app asks for the block time in milliseconds so you need to add 3 zeros to the guide's times)
Click to expand...
Click to collapse
He changed some classpaths, so the service didn't bind. It's all working now.
Zacharee1 said:
Did you set the permissions correctly?
Click to expand...
Click to collapse
Yep. Chmod 0644
Aaren11 said:
Yep. Chmod 0644
Click to expand...
Click to collapse
Strange. If you send me the working jar, it probably won't be hard to edit, since NSS is deodexed.
SimoIanni said:
d
Hi, the playstore app says "Unsupported" because it checks for official build of WakeBlock, now I am on DU wich is Unofficially supported and my home screen looks like this
If yours looks like this too you can proceed blocking wakelocks. Please refeer to this thread to see which wakelocks to block(remember that the WakeBlock app asks for the block time in milliseconds so you need to add 3 zeros to the guide's times)
Click to expand...
Click to collapse
OP is correct... It was am error on myside and have since fixed and been blocking away those dang wakelocks!
Haven't really ever used anything that gve me control like this to pick and choose which ones! Very nice, now the problem is figuring out which ones to block! Haha
I have started lite with mainly just gms.core and will go from there.
Thank you for your work and thanks OP for bringing this here!
Awesome thank you!
Sent from my LG-H918 using XDA-Developers Legacy app
Quick update:
Don't use WakeBlock to block WifiOffDelayIfNotUsed. Your phone will reboot when connected to WiFi, disconnected from power, and put to sleep. This wakelock has been causing me some headaches, so here's an experimental JAR that just disables the wakelock altogether. Test it using the same instructions as in the OP (it does boot; I tested that far), and report any weird behavior. I won't be able to fix anything that happens because of this, but it'll be good for others to have that information.
If this goes well, I think I'll try packaging this into an AROMA installer. I've always wanted to try making one of those.
Aaren11 said:
Yep. Chmod 0644
Click to expand...
Click to collapse
Alright. I reuploaded the services.jar. Try it now.
Zacharee1 said:
Alright. I reuploaded the services.jar. Try it now.
Click to expand...
Click to collapse
Thank you! Sorry I was unable to reply yesterday. I'll give it a try
Edit: No luck unfortunately, still fails to boot. I've attached the services.jar from NSS 6.5
Just tried this on stock H910 and it couldn't get past the ATT logo. I replaced the .jar file and changed the permissions to 0644. Did I need to delete the .odex file in the .jar?
Will this work on G5?
Looks very interesting - out of curiosity has anyone had the dreaded "anx_wlock" kernel wakelock/battery drain on the V20 and managed to fix it with this?
Thanks. Works great on WETA 5.0.7 H918
I can confirm that this process works on Update v5.2.6.8. Any other version beyond that your mileage may vary. "ADB debugging" and "Apps from Unknown Sources" should be enabled. I would like to thank the following members because without their resources this walkthrough wouldn't have been possible: @diplomatic for the exploit, @el7145 for leaving a cookie crumb trail of clues within his comments in this thread which I had to follow like the yellow brick road in order to repeat his success, @rbox for the custom recovery and pre-rooted image, and @AFTVnews.com because if it hadn't been for your article I probably would've never gotten my AFTV device rooted in time before the 5.2.6.9 OTA update. Oh, I almost forgot... and thanks @Chainfire for SuperSU . And also @teamfresno for the advice.
ACHIEVING TEMPORARY ROOT PERMISSIONS
1. Download and install ADB on your PC.
2. Download "mtk-su_r4.zip" and extract "arm64" folder in ADB install directory (C:\adb).
3. Run command below:
Code:
adb connect 192.168.0.XX
(IP address of your Fire TV device)
4. Transfer mtk-su to your /data/local/tmp folder:
Code:
adb push C:/adb/arm64/mtk-su /data/local/tmp/
5. Open an adb shell:
Code:
adb shell
6. Change to your tmp directory:
Code:
cd /data/local/tmp
7. Add executable permissions to the binary:
Code:
chmod 755 mtk-su
8. Run the exploit:
Code:
./mtk-su
NOTE – The following line should display:
New UID/GID: 0/e
9. Ensure that mtk-su succeeded in setting selinux to permissive by typing the following command:
Code:
getenforce
INSTALLING TWRP & SLOANE
1. Download rbox's TWRP custom recovery and the latest pre-rooted ROM from your PC and copy it to the root of a USB stick [or microSD card].
2. Connect the USB stick [or microSD] to your AFTV2.
3. Change to USB Storage directory:
Code:
cd /storage/usbotg/
NOTE – If recovery is on microSD
Code:
cd /storage/sdcard1
4. Run the zip file. This will automatically run SU:
Code:
sh /storage/usbotg/firetv2_recovery_v7.zip
If recovery is on microSD
Code:
sh /storage/sdcard1/firetv2_recovery_v7.zip
NOTE – It should print out a following lines:
Extracting unzip...
Remounting /system read-write...
Extracting...
Remounting /system read-only...
5. Reboot to Recovery:
Ctrl+C (closes out previously ran script)
Code:
adb reboot recovery
6. Your AFTV2 should reboot to a black screen displaying the Amazon logo, followed by a prompt stating that the device will automatically restart, but if not to unplug then re-plug the power source. It will not automatically restart, but DO NOT unplug the device yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7. If you copied the recovery and ROM onto a USB stick then you will need to disconnect it from the AFTV2, and connect a USB hub with at least 2 ports to the AFTV2, and connect both a USB keyboard and the USB stick to the hub at this time. If you copied the recovery and ROM onto a microSD then connect a keyboard to the empty USB port at this time.
8. Now unplug then re-plug the power source and you will be presented with the TWRP splash screen.
9. At the boot menu, press the RIGHT arrow key on the USB keyboard to boot into TWRP recovery.
NOTE – whatever you do DON'T let your AFTV2 idle for too long on the initial recovery boot menu screen or it will time out thus restarting, requiring you to repeat the prior steps.
10. Use the arrow keys to select the "Install" in TWRP.
11. "Select Storage", and choose the location where you stored the pre-rooted ROM.
12. Select "Swipe to Confirm Flash" to start the installation.
13. Select "Reboot System" once the file has finished installing in order to restart the AFTV2.
For those feeling a little adventurous/ambitious then feel free to follow this guide created by @g422 as he discuses where to go from here by delving into other avenues to truly tap into the power of your AFTV2 such as what's "Xposed" and the benefits it offers for rooting your device, and also how to backup your current Fire OS install using TWRP.
Also shouts out to @PhoenixMark who created a guide for Mac users based on my write-up as how to enable root here.
This will work if we have a bricked device stuck on the Amazon logo?
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!
Sent from my SM-G9650 using Tapatalk
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
JUSTINMARMER said:
This will work if we have a bricked device stuck on the Amazon logo?
Click to expand...
Click to collapse
Idk. I think we're pretty much in the same boat now: https://forum.xda-developers.com/showpost.php?p=79063299&postcount=197
Delete... duplicate comment
b0ricuaguerrero said:
Thanks for this! can't wait till I get home and finish the process with your guide. Other guides had my head spinning. Achieved temp root but no mention of pushing super su.
Click to expand...
Click to collapse
Not a problem. Just giving back where I can
b0ricuaguerrero said:
Worked like a charm on my fire tv 2, but I did notice voice control seems to be broken after achieving permanent root.
Anyone else experienced this????
Click to expand...
Click to collapse
I don't use voice activation, voice assistants, etc. as a preference. I'm just paranoid like that
huffmybrd said:
Oh wow, looks like that exploit spread like wildfire!!
Wonder if anybody will see if this works for the firestickv2 (I don't trust myself to crack the case of mine open lol)
Click to expand...
Click to collapse
It's worth looking into. Since I currently own one as well I'll see a/b performing these same instructions and post my findings at some point in time.
salsoul said:
worked flawlessly on Amazon fire tv 2, the only thing i would say about the instruction for me was that usbotg was not recognised I only had sdcard0 (int storage) sdcard1 (sd card) apart from that great job thank you
ps there was an update waiting to install from amazon which i blocked, perhaps they are patching already
Click to expand...
Click to collapse
I tried both ways, with the microSD and USB so I know it works if you followed what was stated in the instructions to the T... I know that when I attempted the USB option the first time, I had forgot to plug the USB stick in which made it show up as USB (0) which is only logical explanation I can think of for what happened to you.
Krog18 said:
Thank you for putting this guide together! Also thanks to @rbox for twrp and the rom!Finally got root on my Fire TV 2!View attachment 4718781
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Not a problem, glad I could help
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
n8wwd said:
This is fantastic work!!!
Do you know if root can be 'hidden' to Netflix app won't block it's use?
Click to expand...
Click to collapse
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
True. Nothing like having a 'brick on a rope' so to speak. That's not a 'deal breaker' as I subscribe to IPTV services that out performs it anyway. Do you know if Hulu does the same as Netflix? The missus may take exception if it killed that...
---------- Post added at 12:22 AM ---------- Previous post was at 12:20 AM ----------
I guess the main reason I'd want root access is to take all of the preloaded apps off for room, as well as have the ability to use the external storage within apps.
---------- Post added at 12:48 AM ---------- Previous post was at 12:22 AM ----------
well...I answered my own question..seems Hulu doesn't like it either...*sigh* Time to search for a box that can hide root so my wife won't blow a gasket....
Wait, we can't use Netflix if we are rooted? Yikes.
I've had no trouble with Netflix yet since I rooted this yesterday, but of course ymmv.
Sent from my SM-G9650 using Tapatalk
---------- Post added at 08:36 AM ---------- Previous post was at 07:44 AM ----------
urbanman2004 said:
Thanks, and unfortunately, no. SuperSU is the component that enables root which can be detected by apps that disengage user functionality when they discover root is enabled. I attempted to install Magisk v18.1 to counteract this side effect, but failed miserably w/ the end result to the point that my AFTV2 does a constant boot loop as recounted here. Magisk would be the only option I'm aware of to make root 'hidden', but it's not worth it at the cost of turning your device into a boot looping paper weight.
Click to expand...
Click to collapse
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Krog18 said:
Damn, sorry to hear that. I imagine what happened is the result of magisk patching the kernel on a locked bootloader. I hope you're able to get it fixed. Good luck to you!
Sent from my SM-G9650 using Tapatalk
Click to expand...
Click to collapse
Thanks. You never know, somebody smart enough might actually come up with a tool capable of relieving my device from its eternal boot loop hell