Starting this thread to document my adventures on rooting via QUADROOTER
https://www.checkpoint.com/downloads/resources/quadRooter-vulnerability-research-report.pdf
(is there a main android->hacking thread? i can only find empty threads mentioning this as news, not as any effort)
Vulnerabilities:
* CVE-2016-2059
* CVE-2016-2504
* CVE-2016-2503
* CVE-2016-5340
feel free to join and point to other developments on the same lines.
I am on a ATT model but not on att network, so I am denied updates... this is what I got:
{
"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"
}
please share yours if on other models, or after receiving updates.
Sent from my STV100-1
I am on the latest MM Beta.
Model: STV100-4
Android Version 6.0.1
Build Number: AAF960
My device seems to be only vulnerable to :
- CVE-2016-5340
Verizon lollipop
Sent from my STV100-2 using Tapatalk
Isn't QuadRooter the program that has been on tech sites regarding viruses/malware?
Dvdxploitr said:
Isn't QuadRooter the program that has been on tech sites regarding viruses/malware?
Click to expand...
Click to collapse
It can be used maliciously because the exploits allow root access. We would just need someone to create an app (& manually disable Android's Verify Apps feature), that would inject SuperUser instead of a malicious app. I guess the next problem to overcome would be the Locked Bootloader, & if the PRIV's extra security settings would even allow the rooted phone to boot.
It wouldn't work because of the BIDE and trusted boot chain.
Sethcreed said:
It wouldn't work because of the BIDE and trusted boot chain.
Click to expand...
Click to collapse
Thanks, I was wondering about that. Oh well, I didn't really think it would be possible with the extra security measures, I was just hoping we could have gotten lucky.
Sethcreed said:
It wouldn't work because of the BIDE and trusted boot chain.
Click to expand...
Click to collapse
can you point me to more info on that please? I'm for now just trying to bootstrap su in the active session.
after i have that i can start to worry about those other pieces to have proper roms/permanent root
Sent from my STV100-1 using XDA-Developers mobile app
When u turn the power on them the boot chain of trust gets power:
1. Primary Bootloader in the SoC, which loads
2. secondary Bootloader. This loads the OS and after that the apps.
All steps are signed by secret key.
Every SoC has an own UID and secret key, which is protected by Fuse technology. These keys using ECC key-2-key Encryption to produce new keys.
Because of the signing process none of the bootloaders can be compromised.
The secondary Bootloader and the OS have non-editable eMMC starting addresses secured by Fuse.
And the SoCs don't have JTAG anymore.
difficult but not impossible...
Hey,
so far that is pretty much the default design for a chain of trust. Nothing special here. But even these system cannot protect against every attack. The problem we are talking about here is always persistence, right. We might be able to takeover the phone, by utilizing an browser exploit or any other type of exploit, but once the device is rebooting all will be gone.
The challenge now is find a way to reinvoke the exploit after boot without doing it by direct manipulation of the system or one of the binaries.
This is certainly possible, but it has to be researched. IPhone jailbreaks are not different, btw.
My idea would be to have a look at all of the system application so see if they use a mechanism like for example Java Reflection or Serialization. Sometimes applications do dirty things like delay load code with a mechanism different from a default invokation. The interesting part here is that once such a mechanism is found you will be likely have to possibility to create a "modified" payload that resides in the "data" part of an application and luckily that cannot be protected by a boot chain of trust.
I have a Blackberry Priv here, and it will be vulnerable ( haven't used it for quite some time... ). When I have some free time, I will give it a try.
Regards,
mitp0sh of [pdx]
Sethcreed said:
When u turn the power on them the boot chain of trust gets power:
1. Primary Bootloader in the SoC, which loads
2. secondary Bootloader. This loads the OS and after that the apps.
All steps are signed by secret key.
Every SoC has an own UID and secret key, which is protected by Fuse technology. These keys using ECC key-2-key Encryption to produce new keys.
Because of the signing process none of the bootloaders can be compromised.
The secondary Bootloader and the OS have non-editable eMMC starting addresses secured by Fuse.
And the SoCs don't have JTAG anymore.
Click to expand...
Click to collapse
It would be so awesome if this would eventually work! I'm getting sick and tired of this annoying BB Bloatware on the Priv (not to mention, not having root access in the first place). I'd love to install CM or any other AOSP ROM for that matter...
I'm happy as long as we can get rid of some of the downloadable bloatware. That way we can have more storage space and ram to use. I'm sure temporary root can help with this.
Sent from my STV100-1 using Tapatalk
Well actually, storage and RAM are not a problem on the Priv, it's got both in spades - unlike all those outdated QWERTY-smartphones I had before (Droid 4, mytouch 4G slide).
Any chance of generating a useful SHA collision in a BB OS reload image? Also wondering if there could be any exploits via BlueTooth or the radio, (did they isolate radio CPU resources from the rest of the system?)
Is there a way to do a root execute after boot, it would seem that the quadrooter exploit would need a booted phone to work either as a malicious exploit or as a way to gain user root. This would bypass the check at boot too. To bad the AutoMagisk will not work but on bootloader unlocked phones.
Its gonna be an achievement, seeing root on a priv
that's the last qwerty android phone (with ok specs for nowaday's standards) on the market and having even a temporary root access to the phone (until the following boot) would be just great!!!
Thinking of getting the Priv. Bootloader will be locked forever and Root seems unlikely. that is bad especially if BlackBerry decides to stop the Android Updates.
Do people here not understand that BlackBerry has always been about security? The whole point of the Priv, and all other BlackBerry handsets is that they can't be 'rooted', exploited or jeopardised in any way, thanks to the years of experience that they have in making secure software platforms.
Pick a non-BlackBerry phone to root, and have some respect.
Related
{
"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"
}
Hi Friend
in contact with the developers VRoot
I request them on Sony 's Android 4.3 also
work with the Boot Loader Lock
This feature was added in the new version of the program
Today I got the opportunity to put this learning
How Root
* First joined the program, or download the source site
*Before installation , make sure your device drivers are installed
*Now install the program normally
*The options on your phone ( Unknown sources & USB debugging ) enabled
*Now connect your phone to the PC and the program Vroot open
(When you connect the phone to connect to internet)
*The program will let you update messages
After a few seconds it takes to install a Application on your phone
Now Root Messaging application will appear on the right
Select it
*Then your phone will reboot
But the program is still work in progress
May take several minutes
After a few seconds, the phone again will reboot
*The appearance of this message, your phone is successfully root
*The application icon should appear on your device menu
*Now your phone can act Czech Root was successful
*to remove the Vroot and install SuperSU
First, go to this link to download the recovery Philz
http://forum.xda-developers.com/showthread.php?t=2649923
* Click on Options install.bat
Then select the first option
question, select the option Allow
*This message displays a successful installation of your recovery
Now turn off your phone
Turning on the phone will see four lights advancing when the blue light show press
Volume up -> Philz
install zip from sdcar and then select the option to install CWM SuperSU
Then reboot the phone
Congratulations work done
Now we have root and recovery
Training Tips
Vroot sent IMEI to some chinese server
I think it is the first Training Root Boot Loader Lock Android 4.3 for Sony
Amir
Moderator Edit: Links removed
I hope some1 can try it fast..and if it works move thread to android devlopment section
Like I said in the news thread this program sents your IMEI and perhaps even your serialnumber.... why would you even use it if it is sents private data to some random server in China...
" Vroot sent IMEI to some chinese server"
Okaaay I honestly don't trust this method with sending IMEI to some chinese server...
mrjraider said:
Like I said in the news thread this program sents your IMEI and perhaps even your serialnumber.... why would you even use it if it is sents private data to some random server in China...
Click to expand...
Click to collapse
Not only China, but also to be sent to all countries
Our distinguished scientist , or a genius that we have very important
SKA67 said:
Not only China, but also to be sent to all countries
Our distinguished scientist , or a genius that we have very important
Click to expand...
Click to collapse
Okay now you've lost me there....
So why even sharing this program when it steals your Imei and Serialnumber from your phone and sents it to multiple places....
Fetching IMEI is a serious concern! However, if a genius can decipher what's the exploit used here...! it seems the program is doing things through ADB??
Training Tips
Vroot sent IMEI to some chinese server
SKA67 said:
Training Tips
Vroot sent IMEI to some chinese server
It is mentioned in the text
Please watch your tone
Someone forced you to make use of this software is no
I use this program for about one year and I never had a problem
Click to expand...
Click to collapse
No but there were two threads with this program and both are closed due to security issues.. And yet again this damn program appears on XDA.... It seems that searching is a bit hard.
Friends
I 've asked the developers vroot about code IMEI
They noted that only promotions and much of the software used
That currently do not use
Sorry but this is closed. As this tool collects IMEI we wouldn't allow discussion and using it here in XDA for the security purpose of our members. The tool may just collect the IMEI for rooting purpose but the matter still not unveiled completely what actually it is. So till then we won't allow Vroot here. Thanks for understanding
SOLVED - Flashed suhide (linked in post 2) leaving this here for anyone else that struggles
Hi all, I'm trying to get Systemless root working with Android 7.0.
In the developer previews it was still passing CTS, as Android Pay was fully working; however now that "full" android 7.0 has been released my device is failing CTS profile match as soon as I flash SuperSU (2.77 or 2.78).
I've even tried the old ways of using the old commands in TWRP terminal
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
I'd like to be able to use Android Pay on 7.0, but still have root functionality for things like Tasker.
Is there any way to get it working currently?
(other than Magisk, I don't want to have to open an app, disable root, use android pay, go back to Magisk, enable root every single time.. Kinda defeats the point of android pay being easy to use)
Have you checked out suhide by Chainfire? I'm still on 6.0.1 but it passes safetynet now. Google has changed the detection so even systemless root fails now. I haven't had s chance to use AP for a purchase though. Others state in this thread that it works.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Sent from my Nexus 6P using XDA Labs
swallowingled said:
Have you checked out suhide by Chainfire? I'm still on 6.0.1 but it passes safetynet now. Google has changed the detection so even systemless root fails now. I haven't had s chance to use AP for a purchase though. Others state in this thread that it works.
http://forum.xda-developers.com/apps/supersu/suhide-t3450396
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
Success! Thank you, I'll give AndroidPay a try and edit this to let you know
pk92 said:
Success! Thank you, I'll give AndroidPay a try and edit this to let you know
Click to expand...
Click to collapse
I'm very curious as well, let us know either way!
It was all working well for a couple of days by now SafetyNet has a "Response payload validation failed"
{
"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"
}
I've been unsuccessful in googling, and AndroidPay is no longer functioning.
pk92 said:
It was all working well for a couple of days by now SafetyNet has a "Response payload validation failed"
I've been unsuccessful in googling, and AndroidPay is no longer functioning.
Click to expand...
Click to collapse
Yeah sadly everyone is getting that now with suhide. Like chainfire said, it'll be a never ending cat and mouse game. Have you tried Magisk by any chance yet? http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I have not but it looks like people have been able to get it to work using that. With it you can unmount root temporarily and supposedly Android Pay works at that point.
DanRyb said:
Yeah sadly everyone is getting that now with suhide. Like chainfire said, it'll be a never ending cat and mouse game. Have you tried Magisk by any chance yet? http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
I have not but it looks like people have been able to get it to work using that. With it you can unmount root temporarily and supposedly Android Pay works at that point.
Click to expand...
Click to collapse
Magisk is really a last resort, I'd rather not have to open the app, unroot, use AP, open magisk, and reroot every time I need to make a payment. It kind of defeats the point of the convenience of Android Pay
pk92 said:
Magisk is really a last resort, I'd rather not have to open the app, unroot, use AP, open magisk, and reroot every time I need to make a payment. It kind of defeats the point of the convenience of Android Pay
Click to expand...
Click to collapse
I hear ya but I think this is going to be the norm. It won't be easy to have root AND Android Pay play nicely side by side. Not when big banks are involved. Google has to do all they can to stop it.
May I ask what you use root for? Only reason is because I too like to use Android Pay but like making a few modifications to my system, namely the Emoji font file, system font file, custom ad-blocking hosts file and an overlay file. I manually make all my changes to /system in TWRP and none of them trip up SafetyNet/Android Pay.
Of course if you're using actual apps that require root, my solution won't work for you.
DanRyb said:
I hear ya but I think this is going to be the norm. It won't be easy to have root AND Android Pay play nicely side by side. Not when big banks are involved. Google has to do all they can to stop it.
May I ask what you use root for? Only reason is because I too like to use Android Pay but like making a few modifications to my system, namely the Emoji font file, system font file, custom ad-blocking hosts file and an overlay file. I manually make all my changes to /system in TWRP and none of them trip up SafetyNet/Android Pay.
Of course if you're using actual apps that require root, my solution won't work for you.
Click to expand...
Click to collapse
+DanRyb would mind telling me how you use TWRP to install say system fonts, etc? While I generally root, I'm enjoying Pay on stock for now, but would like to make a few mods also. Thanks.
jackpollard said:
+DanRyb would mind telling me how you use TWRP to install say system fonts, etc? While I generally root, I'm enjoying Pay on stock for now, but would like to make a few mods also. Thanks.
Click to expand...
Click to collapse
I do it manually through adb command line but you could use a flashable zip too if you find one with the font you like. If making manual changes through adb, just boot into TWRP, go to Mount and make sure you check off /system. Fonts are all in /system/fonts. I replace a bunch of the Roboto*.ttf ones with a font I found like over a year ago. I also replace the emoji font with a custom one of my own which is NotoColorEmoji.ttf.
I'm not sure exactly WHY yet but it seems a custom kernel is needed to respect the changes I made. I attempted last night with just a simple modified boot image that removed the force encryption but all the changes I made in /system I couldn't see once booted. After I installed a custom kernel (I use ElementalX), I was able to make my changes and actually see them. I'm not sure if it has to do with dm-verity or not but I'm still learning as I go. Obviously I can't tweak any of the custom kernel settings using an app (since I don't have root installed) but for me that's OK.
DanRyb said:
I do it manually through adb command ....
Click to expand...
Click to collapse
Thanks for the details, I think I will make a nandriod and play a bit. Again, thanks!
I use root for Tasker, TiBu, AdAway, SDMaid, Nova Launcher (for quicker pull down)
I am on stock 8.0 after the update during a call the phone buzzed and made a loud sound like a siren. After the crash I used it and got message of abnormal restart. I decided to hard reset it. The phone buzzed for about 30 seconds at least and then booted giving me an error uDove to send to HTC. I sent the error and updated all apps to set up.
1. Since then whenever I wake up the phone with the fingerprint or open an app the current window goes white and gets minimised as an app would do. Or as if a pop up goes on and gets closed by an adblock (in desktop).
2. I noticed also lags in performance and battery drain.
All my apps are basic and from play store (major publishers and no games at all) With HTC support I used the phone in Safe mode and no problems where observed. I thought it was htc sense update that was causing the issues however it is not the case. I am lost and do not know what to do. The phone is annoying to use and 4 hard and soft resets did not improve anything.
I ran every check with the HTC utility and nothing significant was reported (all passed ok), During the following hardresets the bootloader gives error
{
"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"
}
coniliakis said:
During the following hardresets the bootloader gives error
Click to expand...
Click to collapse
Looks like partitions map is damaged (hard to read the photo). My educated guess is that you either get a RUU from HTC and let the phone recover everything fresh or unlock boot loader and install custom ROM.
Can you use superuser rights via adb in the HTC recovery mode?
QDT said:
Looks like partitions map is damaged (hard to read the photo). My educated guess is that you either get a RUU from HTC and let the phone recover everything fresh or unlock boot loader and install custom ROM.
Can you use superuser rights via adb in the HTC recovery mode?
Click to expand...
Click to collapse
It reads:
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:can't open /sys/class/power_supply/battery/capacity
handle_cota_install: can't mount /sdcard
E:can't open /sys/class/power_supply/battery/capacity
Could you please tell me what is RUU and how to obtain it? My phone model is this one https://photos.app.goo.gl/tgzt2ebSj1fdt5o29
I can read if I know what I am looking for thank you. HTC has not been very helpful online
coniliakis said:
Could you please tell me what is RUU and how to obtain it? My phone model is this one https://photos.app.goo.gl/tgzt2ebSj1fdt5o29
I can read if I know what I am looking for thank you. HTC has not been very helpful online
Click to expand...
Click to collapse
HTC is sadly ignoring/abandon the U Ultra. Pity.
NVM
RUU is ROM Update Utility - it is an HTC format for update packages. Sadly, Oreo hasn't been made available by HTC.
Since (presuming) you are still under warranty (no unlocked bootloader etc.) I advise to hit the HTC service center and tell them that their OTA went wrong.
Alternatively I could only think of unlocking the bootloader and doing the fix yourself.
Whitch CID do You have? Is it single sim or dual?
I as an update the phone is getting worse the more I use it. I screen blacks out for few seconds and then back to normal. Something like voltage issues. If anyone knows the UK repair service I would appreciate the details. They are not responding e-mails and chat is not helpful at all.
It is bought with UK plug so I assume it is the ones in UK?
Cid
htc__001
wwe
coniliakis said:
Cid
htc__001
wwe
Click to expand...
Click to collapse
So. You have nothing to lose. Try to copy OTA to SD card. Clear Cache and Apply update from SD Card. Maybe it Will help...
https://forum.xda-developers.com/u-...ra-v1-0-0-apr-18th-fast-t3591645/post76405369
deemic said:
So. You have nothing to lose. Try to copy OTA to SD card. Clear Cache and Apply update from SD Card. Maybe it Will help...
https://forum.xda-developers.com/u-...ra-v1-0-0-apr-18th-fast-t3591645/post76405369
Click to expand...
Click to collapse
Edit:
Or downgrade to Nougat, then try with OTA again.
Hello everyone, after buying a new device (huawei) and after 4 visits to the repair center my phone seems to be replaced with another one. unfortunately the battery was changed and it is worse than ever (after a hard reset it says it was last fully charged 223days ago.
I solved the problem by doing a hard reset and not updating the google app. My last reported version (installed by HTC) is 7.17.28.21.arm64 (my device is HTC U ULTRA but same problem). After this everything else runs smoothly etc.
I believe it relates to new features of the app that change completely how it manages the device
• Use voice commands while navigating – even when your device has no connection. Try saying "cancel my navigation" "what's my ETA?" or "what's my next turn?"
• Weak connection? If your search fails, the Google app will deliver you results once you regain connection.
• Troubleshoot connectivity issues with more helpful error cards when your search fails because your device is offline
• New customization options available for cards in your feed
I was having an issue where the Nook wouldn't apply a software update. I figured if I reformatted that would fix it. Well it did. During the initial setup it found and applied the software update OTA. But, after I connect to Wifi, type in my credentials, and click next, I get stuck on this screen:
{
"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 Nook can't get past this. I know it's up to date because it just downloaded an update. I know it was working because earlier today I was reading a book. But now I've hit a wall. I found another topic regarding registering a glowlight 6", but his problem seems to be slightly different. The users in that topic talked about bypassing the registration, but I can't find advice on that for my particular model. The methods I have tried aren't working, so they must be for other model Nooks. And besides, I'd like to have this device working as intended. I don't intend to root it if I don't have to. I've jailbroken my kindles and rooted many android phones over the years, so it's not a big deal if it must be done. But even then, I don't know how I can root it without getting into settings to turn on debugging.
I'll also mention that the device is for the USA region (or ought to be since that's what all the time zone choices are), and so am I.
EDIT: What I failed to mention was that I got the Nook from Savers yesterday (a thrift store) for $5. Well today I talked to Barnes and Noble and the device is blacklisted. Whoever used to own it reported it stolen once upon a time. This deal was too good to be true
Semi-related: The NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/52.0.78_user:user/release-keys release is out.
http://su.barnesandnoble.com/nook/piper/5.2/piper/0.78/update.zip
I'm not sure what great things are in there, but my "glow45patch.zip" is still compatible. (See signature, MergeSmali)
Renate NST said:
Semi-related: The NOOK/ntx_6sl/ntx_6sl:4.4.2/KOT49H/52.0.78_user:user/release-keys release is out.
http://su.barnesandnoble.com/nook/piper/5.2/piper/0.78/update.zip
I'm not sure what great things are in there, but my "glow45patch.zip" is still compatible. (See signature, MergeSmali)
Click to expand...
Click to collapse
Thanks Renate. I'm doing some reading about the Mergesmali utility you made. I think I am competent enough to use it, but I don't see much info about what use it serves me in particular. Can I use the glow45 patch with mergesmali.exe to bypass the initial setup?
TidusWulf said:
Can I use the glow45 patch with mergesmali.exe to bypass the initial setup?
Click to expand...
Click to collapse
No, the point of it is to patch the specific aspects mentioned, sleep images, white background.
The utility of it is that the same patches were written for 4.5 and continue to work for 5.2 (and beyond).
Moreover, you can't modify any system files until your Glow is rooted.
For skipping registration, is this useful? https://forum.xda-developers.com/nook-touch/general/how-to-access-nook-glowlight-3-t4096829
I'm actually no good at exploit rooting because I usually just hook up a UART console instead.
Oh wow, I got to the easter egg. Thanks for that link. I haven't got this far before. So I've got USB debugging turned on. What next? I just want to use this device as an ereader, nothing else. I'm not sure how to bypass registration still yet, and I've read that there's an extra step I have to take to disable telemetry otherwise my battery life will be really bad.
Also, by platform version is 52.0.78 and my nook apk is 5.2.4.27
EDIT: This looks promising, except that it's for the Glow3 and I have the Glow2 https://forum.xda-developers.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331
I was hoping I could avoid rooting, but it looks like I'll have to in order to overcome that boot animation glitch. And also because it seems the only bypass is to install a separate launcher I guess.
There's been a lot of convergence.
Except for a few hardware things (and 6" vs. 7.8") the Glow2, Glow3 & Glow4 are the same.
Just don't install an update.zip for the wrong model!
Renate NST said:
There's been a lot of convergence.
Except for a few hardware things (and 6" vs. 7.8") the Glow2, Glow3 & Glow4 are the same.
Just don't install an update.zip for the wrong model!
Click to expand...
Click to collapse
Thank you for all the great advice. Perhaps then I should first find a way to make a clean backup before I make any big changes like a custom recovery, or disabling apps and jars.
I've made a lot of progress, but now I'm stuck. I used adb push to temporarily run TWRP and made a backup. Then I used adb to install relauncherX. Pressing HOME doesn't prompt me to pick a launcher. I used https://forum.xda-developers.com/showpost.php?p=64191791 to run a script to Root the device. I also disabled the boot animation using this code:
adb shell
su
mount -o remount, rw /system
mv /system/bin/bootanimation /system/bin/bootanimation.bak
reboot
Click to expand...
Click to collapse
I assume root has persisted thru the reboot because in cmd I was as to run ADB SHELL followed by SU and now I have [email protected]_6sl:/ # in my command prompt.
Problem is, Even though I'm rooted and have a custom launcher, I still can't get past the sign in screen. I think if I knew what process it was, I could kill it with adb, but ps isn't giving me any clues, and dumpsys activity is like information overload, and beyond my skillset to decipher. While in adb shell, su, I used kill 3162 (the pid of com.nook.partner) and that didn't help either. It DID however remove the top bar from the screen, where it shows wifi and battery.
EDIT: So, thanks to me actually READING a little more, I followed some info here https://forum.xda-developers.com/nook-touch/general/how-to-access-nook-glowlight-3-t4096829 and managed to disable the activies necessary to bypass registration. I have the RelaunchX launcher now. I'm 90% of the way there! Now I just need an app that can launch ebooks, because the Nook app wants me to sign in, instead of read.
TidusWulf said:
Now I just need an app that can launch ebooks...
Click to expand...
Click to collapse
So, get a reader app.
One that was mentioned recently was AlReader (that's Al as in Albert).
I don't know, I don't use it.
I am using oneplus 6t with twrp and magisk installed.
My root storage is showing full 2.70gb used out of 2.71gb.
I can't even change the bootanimation.
Can anyone please help with solution.
{
"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"
}
Vinitthacker said:
I am using oneplus 6t with twrp and magisk installed.
My root storage is showing full 2.70gb used out of 2.71gb.
I can't even change the bootanimation.
Can anyone please help with solution.
View attachment 5185617
Click to expand...
Click to collapse
You shouldn't change anything in such partitions unless you're a Linux wizard. Or a classic wizard, like Merlin. Why would you even do that if it can be done systemless? There are plenty of ways to change your bootanimation via Magisk. I'm personally using Chainfire's LiveBoot.
Timmmmaaahh said:
You shouldn't change anything in such partitions unless you're a Linux wizard. Or a classic wizard, like Merlin. Why would you even do that if it can be done systemless? There are plenty of ways to change your bootanimation via Magisk. I'm personally using Chainfire's LiveBoot.
Click to expand...
Click to collapse
I am a new to all this. I just wanted to change the boot animation so i did a google search and it showed that replace the bootanimation.zip file from /system/media.
So when i tried doing that, i was getting a storage full error.
How can i do it systemless, can you help?
Vinitthacker said:
I am a new to all this. I just wanted to change the boot animation so i did a google search and it showed that replace the bootanimation.zip file from /system/media.
So when i tried doing that, i was getting a storage full error.
How can i do it systemless, can you help?
Click to expand...
Click to collapse
Well sure but it's pretty straightforward. Before beginning you should note that flashing always contains the risk of data loss (BACKUPS!!) and/or device malfunction, even though the risk is much smaller when you approach things in a systemless manner. But as you have already unlocked and rooted your device, you've pretty much overcome this. System manipulation is usually not as simple as 'just replacing a file' because there's also file permissions to be set, file size limits and plenty of other variables to take into account.
With systemless flashing, it's much easier and safer because the original files are untouched and the correct parameters are set for you. Your system is rerouted to the patched files in the booting process. Take away this process (eg. by flashing Magisk uninstaller) and things are back to normal. Well, most of the time.
A good place to start for custom boot animations (and other goodies) is here: OnePlus 6T Themes, Apps, and Mods
In that section it's safe to say the mods will be compatible with your device. You may also find a thing or two in OnePlus 6T Guides, News, & Discussion.
Some things – like the LiveBoot I've mentioned earlier – will work universally but it's best to do your research before you throw anything at your device. You will find these in the more general sections of XDA.
If you found something you like, just read the instructions in the OP (Original Post) and follow them step by step. Also, if you're smart, read the last few pages too, to make sure it's still a working mod or if deviating instructions should be followed. You don't need to make the mistakes others already made for you. It's mostly just dropping a module in Magisk or installing an app and give it root access. For this MacLaren mod, which replaces the boot animation, fingerprint animation, etc. it's the first method: flash module and reboot. However, last pages reveal that functionality on Android 10 is either erratic or non existent. So best only flash on Pie. I hope this helps you on your way.
Timmmmaaahh said:
Well sure but it's pretty straightforward. Before beginning you should note that flashing always contains the risk of data loss (BACKUPS!!) and/or device malfunction, even though the risk is much smaller when you approach things in a systemless manner. But as you have already unlocked and rooted your device, you've pretty much overcome this. System manipulation is usually not as simple as 'just replacing a file' because there's also file permissions to be set, file size limits and plenty of other variables to take into account.
With systemless flashing, it's much easier and safer because the original files are untouched and the correct parameters are set for you. Your system is rerouted to the patched files in the booting process. Take away this process (eg. by flashing Magisk uninstaller) and things are back to normal. Well, most of the time.
A good place to start for custom boot animations (and other goodies) is here: OnePlus 6T Themes, Apps, and Mods
In that section it's safe to say the mods will be compatible with your device. You may also find a thing or two in OnePlus 6T Guides, News, & Discussion.
Some things – like the LiveBoot I've mentioned earlier – will work universally but it's best to do your research before you throw anything at your device. You will find these in the more general sections of XDA.
If you found something you like, just read the instructions in the OP (Original Post) and follow them step by step. Also, if you're smart, read the last few pages too, to make sure it's still a working mod or if deviating instructions should be followed. You don't need to make the mistakes others already made for you. It's mostly just dropping a module in Magisk or installing an app and give it root access. For this MacLaren mod, which replaces the boot animation, fingerprint animation, etc. it's the first method: flash module and reboot. However, last pages reveal that functionality on Android 10 is either erratic or non existent. So best only flash on Pie. I hope this helps you on your way.
Click to expand...
Click to collapse
Thanks a lot for the help brother