yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] Renate:
You know, there are more secret touches and broken code all over.

I found another one, but I can't seem to get this to work either.

It's on this screen. There are four touch spots.

The bottom two when pressed and held should show a version number at the top center of the screen.

The top two, in some pattern (that I'm still looking at) should respond with the Easter Egg which gets you to the Diagnostic.

I'm working on it, but you can try too.

Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
[Nook Touch General] dnt83:
Thank you very much for your support

The bottom two it showed version.

I tried the top two it no work
[Nook Touch General] Renate:
Ok, the top two spots, tap: L-R-L-R-L-R-L-R-L-R and you'll get to the Easter Egg.
[Nook Touch General] dnt83:
Yes, it worked

Thank you very much!
[Nook Touch General] dnt83:
Hello

Could you show me next step to root it?

Thank you!
[Nook Touch General] dnt83:
Hello

I rooted and can work in adb shell, could you show me how to skip oobe?

Thank you!
[Nook Touch General] Renate:
You need to install a launcher so that you have something "Home" to run.

Also:

# pm disable com.nook.partner/.oobe.WelcomeScreenActivity
[Nook Touch General] dnt83:
Yes, Thank you

I already installed custom firmware

Thank you very much for your support!
[Nook Touch General] Renate:
And if anybody is wondering, this works on all 5.0 Nooks, Glow2, Glow3, Glow4
[Nook Touch General] CrisCraigMorgan:
Hi, I just picked up a new Nook Glowlight Plus (the 2019 7.8" model) and am trying to get started using it without the compulsory registration. My understanding from the start of this thread is that I should be able to root it, install an alternate launcher, disable the oobe.WelcomeScreenActivity, and I'm off to the races.

I have gotten as far being able to see the device with adb and connect to it, but I can't root it. adb seems to be working as normal (e.g., I can "adb shell" in as I would expect) but any attempts to push files with "adb push" fail. After attempting adb push, the device disconnects from adb and can no longer be seen until I physically unplug and re-plug it. Interestingly, adb push of a directory _does_ create the directory structure on the Nook -- just not any of the actual files...

Any help debugging this is appreciated...

A log of what I'm seeing is here:

https pastebin.com / ti4qB6Xr

(Sorry, I can't post direct links yet, and didn't want to spam the thread with a wall of text...)

Thanks!

---------- Post added at 02:58 AM ---------- Previous post was at 02:52 AM ----------

I should also mention that if I start to go through the on-device Welcome screen (choose timezone, choose wifi network and enter password), before actually getting to the login screen, I'm prompted to allow it to download a firmware update. I did not allow the update, in case a) the update changes something that would make rooting or installing a new launcher more difficult, and b) I don't want to miss the opportunity to note the download link and fetch an extra copy of the update in case it's useful later.

But if the download link is already known to the community, and if the update is unlikely to change anything that rooting/launchers depend on, I would also try letting it download, and then going to the login screen and trying the lower-left+upper-right+triple-tap bypass mentioned earlier in the thread.

Please let me know if I should try this.

Thanks.
[Nook Touch General] CrisCraigMorgan:
So "adb push" is still not working, but I was able to root the device with shell chicanery. I tarred/gzipped the exploit payload, base64 encoded it, and used a shell loop to transfer it a line at a time:

c=1
cat nookrooter.tgz | base64 -e | while read line
do
echo "$c" >&2 ; c=$(expr $c + 1)
echo "$line" | adb shell 'busybox head -1 | busybox tee -a /data/local/tmp/nookrooter.tgz.b64 > /dev/null'
done

At ~64k base64-encoded lines, it took a bit over an hour to transfer. After base64-decoding, checking the md5 on both sides, and untarring in the right spot, it rooted just fine:

frappe/home/chris/nook/root-glp/rootGLP-3-13998# adb shell id -u
uid=0(root) gid=0(root)

That said, I'd still love to get some guidance on this device from folks who are familiar with it. Any idea why adb push might consistently fail? Is my basic understanding of how this whole process works is correct? Does it matters if I allow the device to complete the OTA firmware update before going farther?

My intent for the device is to use it as a standalone e-reader. I don't want to ever connect it to a network, nor to run any apps on it other than an e-reader. Public domain e-book content will be converted to EPUB (or, occassionally, CBZ or PDF) with Calibre (specifically the ebook-convert CLI) and copied via USB. I don't need to use "shelves" or whatever the Nook paradigm is for organization, nor will I "manage" the device with Calibre; "management" as such will be strictly copying individual files into a flat directory structure from the shell. I'm not too fussy about fonts, and don't need (or want) much more than the ability to click on a book and page-up/page-down through its contents.

I'm an experienced C/Unix developer, but have never used Android before.

Any help and pointers are much appreciated.

Thanks!
[Nook Touch General] Renate:
Yes, the manifest of the updates is discussed here: https://xdaforums.com/nook-touch/general/software-updates-wifi-t4136097

Strange. Why didn't you try adb install on the apk?

Maybe the adb on your host is broken. Try this.

adb push something

Did it fail?

adb devices, is it "gone"?

lsusb, really?

adb kill-server

adb devices, is it "back"?
[Nook Touch General] CrisCraigMorgan:
Thanks!

I'll try installing some apk that way. But in the case of the root payload, there are other files in addition to the one APK.

Yup, I tried experimenting with other files, smaller files, individual files rather than directories -- all files failed (though, as noted, directories were created in the case of trying to push a local source directory).

I can run some more experiments later. The pastebin log above shows what I saw: immediately after any attempt to use "adb push", "adb devices" showed no devices. I didn't check usbconfig (FreeBSD here, not Linux, but that shouldn't matter), but there were no kernel messages about the device detaching (until I physically pulled the USB cable), so I suspect that the device would still have shown as attached.

Thanks!
[Nook Touch General] CrisCraigMorgan:
So having rooted my Nook, I went ahead and installed the l2.apk launcher posted here https://xdaforums.com/nook-touch/general/normal-launcher-nook-t3966911; disabled com.nook.partner/.oobe.WelcomeScreenActivity; renamed the bootanimation file; and rebooted.

When the device rebooted, it just displayed a message that said, "Unfortunately, com.nook.partner has stopped" and nothing else. Re-enabling com.nook.partner/.oobe.WelcomeScreenActivity restored it to its original boot-up behaviour.

So I think I must be missing something basic about the boot process, or rooting generally.

Should it be sufficient to just have another launcher installed? Do I have to do something particular to invoke it during the boot process?

Should I install TWRP? Alternate firmware, as described here: https://xdaforums.com/nook-touch/general/gp-g3-gp7-8-twrp-alternative-firmware-t4074347 ?

Another question I have is about keeping root access across reboots. I can unpack the exploit in rootGLP-3.zip (from https://xdaforums.com/nook-touch/general/how-to-root-set-nook-glowlight-3-t3802331) and run it to gain root; but when I reboot the device, I lose root again until I re-run the exploit. I tried setting /system/bin/busybox suid root, but then "busybox su" returns "unknown user root" -- I'm guessing because it's calling getpwuid(), but there's no /etc/passwd so the call fails. Could I just create /etc/passwd to define root? I also tried copying the "su" binary in the exploit dir into /system/chris/bin/ and setting it suid root, but this also fails (with no output). I could just write the three-line version of su that calls

setuid(0); exec("/system/bin/sh")

, but I have no idea how to compile code for this thing. Anything I'm missing here?

Thanks.
[Nook Touch General] CrisCraigMorgan:
I played around a bit more with adb push. Still consistently failing, but restarting the local adb server does at least re-establish connectivity without unplugging/re-plugging the device. Definitely sounds like a problem with my local adb install rather than the device. Considering that I have a(n admittedly super-janky) method to transfer files, I don't feel a strong need to debug it right now.

frappe/home/chris/nook-13599# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

frappe/home/chris/nook-13600# adb devices -l
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:19

frappe/home/chris/nook-13601# adb push ReLaunchX_2.1.5-app-debug.apk /data/local/tmp/
adb: error: failed to copy 'ReLaunchX_2.1.5-app-debug.apk' to '/data/local/tmp/ReLaunchX_2.1.5-app-debug.apk': couldn't read from device
ReLaunchX_2.1.5-app-debug.apk: 0 files...ped. 7.6 MB/s (131056 bytes in 0.016s)

frappe/home/chris/nook-13602# usbconfig | grep 1.6
ugen1.6: <BarnesAndNoble BNRV700> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA)

frappe/home/chris/nook-13603# adb devices -l
List of devices attached

frappe/home/chris/nook-13604# adb kill-server

frappe/home/chris/nook-13605# adb devices -l
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
MY_SERIAL_NUMBER device usb:1:6 transport_id:1

frappe/home/chris/nook-13606# adb shell
root@ntx_6sl:/ # id
uid=0(root) gid=0(root)
root@ntx_6sl:/ # ^D
[Nook Touch General] Renate:
There's all sorts of "rooting" stuff here, but I just prefer a simple replacement of adbd in the ramdisk with one that doesn't switch to user "shell".

I don't want/need/like the chainfire stuff hanging around.

Sorry, I've lost track of where everything here is as I've never used any exploit method.

As for your launcher stuff, did you check logcat to see if there is any obvious reason why partner.apk is dying?

adb logcat

Have you tried:

adb shell am start -n com.android.launcher/com.android.launcher2.Launcher

Was the Launcher even installed correctly?

adb shell pm list packages -f launcher
[Nook Touch General] Renate:
Also:

# pm disable com.nook.partner/.FacadeLauncherActivity
# pm disable com.nook.partner/.OobeLauncherActivity
[Nook Touch General] CrisCraigMorgan:
Thanks Renate NST! "adb logcat" lead me to com.nook.partner/.OobeLauncherActivity:

E/AndroidRuntime( 2856): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.nook.partner/com.nook.partner.OobeLauncherActivity}: android.content.ActivityNotFoundExceptio
n: Unable to find explicit activity class {com.nook.partner/com.nook.partner.oobe.WelcomeScreenActivity}; have you declared this activity in your AndroidManifest.xml?

Once I disabled that, I got prompted for what launcher to use and could run the L2 launcher as expected. w00t!

So from this point, I expect that I can install any random e-reader app and do my thing.

I still do have a couple more questions though... :)

When I plug in the Nook, I see it presents a couple of block devices to the host computer. But these don't have filesystems on them, and indeed can't be read or written:

da2 at umass-sim2 bus 2 scbus5 target 0 lun 0
da2: <Linux File-CD Gadget 0000> Removable Direct Access SCSI-2 device
da2: 40.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
da2: quirks=0x2<NO_6_BYTE>

da3 at umass-sim2 bus 2 scbus5 target 0 lun 1
da3: <Linux File-CD Gadget 0000> Removable Direct Access SCSI-2 device
da3: 40.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
da3: quirks=0x2<NO_6_BYTE>

frappe/home/chris-105647: su
Last login: Mon Jul 27 17:51:20 2020 from localhost
FreeBSD 12.1-STABLE (JKERN12) #0 r361820M: Fri Jun 5 20:58:36 PDT 2020

Welcome to FreeBSD!

frappe/root-14109# dd if=/dev/da2 of=/dev/null
dd: /dev/da2: Device not configured
0+0 records in
0+0 records out
0 bytes transferred in 0.000078 secs (0 bytes/sec)

frappe/root-14110# dd if=/dev/da3 of=/dev/null
dd: /dev/da3: Device not configured
0+0 records in
0+0 records out
0 bytes transferred in 0.000079 secs (0 bytes/sec)

How can I get it to export the user-data part of the filesystem (/sdcard/?) so I can copy content from the host?

Also, I enabled MTP file transfers in settings, but it doesn't seem to be working: attempts to connect with gphoto2 return, "Error: No camera found."

Also, specifically trying to run the Nook app, it refuses to do anything if the wifi is turned off. Anyone know if there's a way around this?

Thanks!
[Nook Touch General] Renate:
Yeah, that's what the "mass_storage" USB gadget does.

If there is nothing assigned to it, it will be empty.

This would usually be in init.E60QQ0.usb.rc (but you don't want to do this since UMS is stupid).

write /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file /dev/block/mmcblk0

The function of the USB gadget is controlled by stuff in init.E60QQ0.usb.rc which is controlled by persist.sys.usb.config

You probably had it set to mass_storage,adb

There is no adb only config unless you rewrite that file.

Which is what I do.
[Nook Touch General] CrisCraigMorgan:
So you recommend I not use USB mass storage at all with the device? If so, what is the preferred way to transfer data? MTP?

Just to be sure I understand, this would cause the Nook's /dev/block/mmcblk0 to get exported as lun0 from the device (which I would see as /dev/da2 or whatever on the host computer)? How does the Nook share raw block-level access to the device with the host computer? Does it unmount any filesystems on /dev/block/mmcblk0 before sharing the device? Or does it somehow try to allow both itself and the host computer simultaneous raw write access to the block device? (I hope not, because that sounds like madness...?)

Finally, any idea why MTP doesn't seem to be working?

Thanks again for all your help. When I picked up this device, I didn't figure that it was going to end up being a crash-course on Android development... So thanks. :)
[Nook Touch General] CrisCraigMorgan:
I think I solved both my mtp and my adb push/adb install issues.

mtp wasn't working because my automounter was clever enough to detect the Nook and mount it with fusefs/mtpfs. So this appears to work.

And adb looks like possibly an mdns library conflict.

So, both local to my host computer, and nothing to do with the Android device.
[Nook Touch General] Renate:
UMS is morally bankrupt because it's basically like ripping out your hard drive and handing it to a stranger.

Also the foreign system needs to understand the file system, which doesn't work for Windows.

The mount of /dev/block/mmcblk0 is useful in recoveries to allow a full raw backup.

I use only ADB and my Windows utility adbsync.exe (in signature) to keep my Android devices up to date.
[Nook Touch General] Renate:
Hmm, something is failing badly.

Why don't you hook up your hardware USB protocol analyzer and see what's really going on.

What? :eek: You don't have one?

Is dmesg showing any errors?

Don't you have another system to try?

The problem with MTP & PTP is they are designed to limit access.
[LG V30 Questions & Answers] mpicasso:
See attached - fresh download/install of Havoc 2.9 and Gapps; changed fingerprint to: PQ3B.190801.002

Cannot write to SD card using Google Files or Root Explorer. Any suggestions on what to try or even how to obtain more information would be appreciated. Card worked when on Los but not since being on Havoc. Point - card HAS worked on Pie ROMs before.

Edit: somehow, I had a screenshot taken while using TWRP, yesterday, and stored on SD card. Card is good...just cannot figure how to access for write (add/delete).
[LG V30 Questions & Answers] Cubicle:
I've been having this problem too:

H932 (Tmobile V30)

Rooted stock Oreo

ES File Explorer

I've only been having this problem the past 1-2 months. No OS updates. I have done some application (app) updates through Google Play. Root is working, can get into Terminal Emulator, run "su" command, my firewall works, Magisk & Xposed all report no problems., & all my modules & extensions work fine.

Hopefully someone has an idea.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] sourav24071999:
Noice ?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] SakthivelNadar:
Reserved for device related changelogs!

Atom_2.6.3_lavender-10.0-20200507:

initial build changelogs:

- Enable display burn-in-protection in Ambient Display

- enable pm.sleep_mode

- rootdir: let the kernel set the swappiness

- overlay: add rssnr overlay

- spoof taimen instead of flame

- rootdir: fstab: setup 1GB ZRAM

- device: add SystemUI to PRODUCT_DEXPREOPT_SPEED_APPS

- more render tweaks

- Dexpreopt everything

- adjust statusbar padding in framework

- overlay: make the UI smoother

- vendor_prop: Enable FIFO scheduling for UI and render threa…

- prop: Disable VSync for CPU rendered apps

- audio: Tweak in-call audio

- media: Enabled 1080p video playback on YouTube
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] KackBarton:
Any screenshot?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Rotblaag:
wrong reply please disregard
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] KackBarton:
Thanks my friend, now i'm starting a download and try.
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] Jctatis:
any screenshoots?

should i use orange or twrp?
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] SakthivelNadar:
any recovery, im pushing new update in few days, it will have more fixes :) so stay tuned!
[Xiaomi Redmi Note 7 ROMs, Kernels, Recoveries, & O] javedgh:
Nice rom
[Xperia Z5 Compact Q&A, Help & Troubleshooting] lolollolol:
Hi,

After disabling some app and disabling background data for some else apps, I turn my phone off.

Now, it could not charge and do not respond with the power button.

Z5C on Android 7.1.1 root with TWRP.

Plugged in usb, on the power adapter : nothing on screen. And on USB, the same.

I saw this list of apps :

https://sky11362.pixnet.net/blog/post/35365493

I'm sure I have disabled this one : SemcAutoPowerOff.apk

For others, I don't remind me... I've got a TWRP backup of my phone (outdated but maybe useful, 2017).

Is it possible to restore the apps states and privileges with TWRP or something else ?

I'll retry later, when battery will be really empty. Hope it can rebirth !
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Deleted member 7835385:
try to hold power button + volume up button to force shutdown.

Maybe it just hang during the shutdown phase
[Xperia Z5 Compact Q&A, Help & Troubleshooting] lolollolol:
So... After waiting all this afternoon, I push the power button during maybe 30 seconds.

It came back ! Battery was below 25%. Everything is ok. :silly:

I'll recheck my disabled apps... :D
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] xK4m3l:
nice
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] henmadx:
Good :good:
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] mrchino_mapache:
the ROM is perfect, but since I don't have the mobile messaging app I can't receive the message with verification code e. social networks. otherwise it is super powerful

Enviado desde mi MI 5s Plus mediante Tapatalk
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] mrchino_mapache:
How can I put the mobile messaging app, without that app I cannot enter the networks that use the verification code via SMS

Enviado desde mi MI 5s Plus mediante Tapatalk
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] incondesign:
Just install Message app by Google LLC from GooglePlay
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] mrchino_mapache:
I thought and tried, but I don't get SMS

Enviado desde mi MI 5s Plus mediante Tapatalk
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] incondesign:
Sms working fine on my device, do you check your xiaomi firmware and update to the latest version? My firmware is 11.0.2.0

In case it can't fix your sms problem, you can try clean flash rom (after update latest firmware)
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] mrchino_mapache:
clean installation of the latest FW, rom, magisk, and skip this error and even without smsView attachment 5025423

Enviado desde mi Mi 5s Plus mediante Tapatalk
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] turkuazzz99:
What does hotboot mean and how? i know open fastboot, i know open recovery but i dont know hotboot.
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] turkuazzz99:
Why is it stuck in the logo?

i am flash the last firmware.
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] turkuazzz99:
i flash 08.05.2020 rom no problem but ; i flashing 26.05.2020 rom stuck the logo.
[Xiaomi Mi 5s Plus ROMs, Kernels, Recoveries, & Oth] kraptor121:
stuck at boot screen i tried twice
[Xiaomi Mi Note 10 Guides, News, & Discussion] borelis:
This is the official global stable beta android 10!

Downloaded and tried to apply, but got the error message cause mine is EU version ?

https://piunikaweb.com/2020/05/07/xiaomi-mi-note-10-android-10-update-rolls-out-in-stable-version/
[Xiaomi Mi Note 10 Guides, News, & Discussion] MacGuy2006:
I get the same message on the Global 11.0.17.

File was from the miui.com direct download link.
[Xiaomi Mi Note 10 Guides, News, & Discussion] MAGAZINEBRIAN:
Same message.
[Xiaomi Mi Note 10 Guides, News, & Discussion] Ferdinantstr:
Any ideas how to install without losing data?!
[Xiaomi Mi Note 10 Guides, News, & Discussion] eamon.ash:
This is because your devices is in different region with the rom, if your bootloader is unlocked you can install it with no problem
[Xiaomi Mi Note 10 Guides, News, & Discussion] MacGuy2006:
Yeah, I figured, but unlocking for an early update is not worth it for me, so I will just wait for the OTA.
[Xiaomi Mi Note 10 Guides, News, & Discussion] engineer000:
miui V11.1.2.0.QFDMIXM OTA is being downloaded on my device.
[Xiaomi Mi Note 10 Guides, News, & Discussion] bbmanager:
This just popped up on my phone as well, let me know how it runs :good:
[Xiaomi Mi Note 10 Guides, News, & Discussion] BundyR25:
This is Miui 11, not 12. I have this update, everything is working nice
[Xiaomi Mi Note 10 Guides, News, & Discussion] engineer000:
haven't reviewed yet however it looks the same as before.
[Xiaomi Mi Note 10 Guides, News, & Discussion] OC-Freak:
Still no android 10 update for EU Global while global got a second android 10 update? bleh.
[Xiaomi Mi Note 10 Guides, News, & Discussion] MacGuy2006:
I am on Global and no update to Android 10 either.....
[Xiaomi Mi Note 10 Guides, News, & Discussion] grenat:
The same for me, always on 11.0.1.7.0..
[Xiaomi Mi Note 10 Guides, News, & Discussion] freeDom21:
Yes for me too - V11.0.17.0.PFDEUXM.

Also, anyone noticed when checking "What's new" section it shows that it is not accesible and required permission for the account signed in has to be granted? Have not seen that before.. And also when clicking "download latest package" - it shows like error and asks to wait a minute or two and try again? Have anyone experienced that?
[Xiaomi Mi Note 10 Guides, News, & Discussion] IO ME MEDESIMO:
Finally android 10 update on my mi note 10 Global EU
[Xiaomi Mi Note 10 Guides, News, & Discussion] borelis:
Just got it here In Sweden