yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] cave_iar:
did all the steps, but during the last

# META-INF/com/google/android/update-binary 2 1 update.zip

i had the following

inflating: META-INF/com/google/android/update-binary
m/google/android/update-binary <
ndroid/update-binary 2 1 update.zip <
ui_print Upgrade : ALL
ui_print
progress 0.100000 3
[B]script aborted: This package is for "ntx_6sl" devices; this is a "".
ui_print This package is for "ntx_6sl" devices; this is a "".[/B]
ui_print

not sure i understand if it is important, but eventually after adb reboot i had the same sort of problems during B&N default load screen - very slow response to taps (maybe 10 secs per tap) and frozen Nook at "Turning Wi-Fi on" screen. It's actually not frozen, as it reacts to taps, but Wi-Fi does not turn on anyway.

looks like adb push was unable to delete all the memory - maybe there is another way to fully restore the devices, using software methods. Previously I also unmounted system battery for required time, but it did not help (same problems).

PS. tried fastboot erase cache, which returned

C:\ADB>fastboot erase cache
Erasing 'cache' FAILED (remote: '')
Finished. Total time: 0.038s

PPS. fastboot erase system -w returns

C:\ADB>fastboot erase system -w
Erase successful, but not automatically formatting.
Unable to get partition size
FAILED (remote: 'unknown var')
Erasing 'system' FAILED (remote: '')
Finished. Total time: 0.178s
[Nook Touch General] cave_iar:
OK, what i finally managed to do is to flash recovery with TWRP, reboot in recovery mode and install alternative firmware from one of the threads here on the forum. It works perfect and smooth up until I go to settings and turn on Wi-Fi. Looks like a problem with it. Is there an img of default "radio"?

Also, when doign fastboot getvar all, it returns an error

getvar:all FAILED (remote: 'unknown var')
Finished. Total time: 0.000s
[Nook Touch General] Renate:
Before that, do this:

# setprop ro.product.device ntx_6sl

Some fastboots (like the one built into u-boot) don't understand fastboot getvar all.

C:\>fastboot getvar version
C:\>fastboot getvar product
C:\>fastboot getvar serialno
[Nook Touch General] cave_iar:
Still some errors, pls see below:

ui_print Upgrade : ALL
ui_print
progress 0.100000 3
ui_print Target device check: ok
ui_print
ui_print installing system...
ui_print
progress 0.500000 15
Creating filesystem with parameters:
Size: 402644992
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1535
Label:
Blocks: 98302
Block groups: 3
Reserved block group size: 23
Created filesystem with 11/24576 inodes and 3130/98302 blocks
mount: failed to mount /dev/block/mmcblk0p5 at /system: Device or resource busy
minzip: Can't create containing directory for "/system/app/Browser.apk": No such file or directory
minzip: Extracted 0 file(s)
failed to mkdir /system/fonts/DroidSans-Bold.ttf: Read-only file system
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to Roboto-Bold.ttf: making parents failed
symlink: failed to symlink /system/fonts/DroidSans-Bold.ttf to Roboto-Bold.ttf: No such file or directory
script aborted: symlink: some symlinks failed
ui_print symlink: some symlinks failed
ui_print
[Nook Touch General] Renate:
Oops, try:

# umount /system
[Nook Touch General] cave_iar:
thanks, the code worked, but after reboot still the same problem - very slow performance, almost frozen default B&N screen.

Do you think the fact that i cant erase system-related stuff ('cache', 'system') is important to detect the issue? And also Wi-Fi not being able to switch on both at standard ROM and alternative one

I think in the worst case, ill stick to an alternative ROM avoiding switching on Wi-Fi, as it appears to work fine
[Nook Touch General] Renate:
Well, look at dmesg, look at logcat, look at "ps".

WiFi can be a problem maker as it uses a driver that is in /data that is not updated by the update.zip
[Nook Touch General] cave_iar:
Attached is logcat, generated some 5 mins after i switched-on wi-fi (i believe switching on of wi-fi is somewhere in the begining)
[Nook Touch General] Renate:
I can's see anything conspicuous.

# top

Is something eating all the CPU?
[Nook Touch General] dmkbox:
Hi. I'm bricked my Glowlight plus 2015.

I'm install twrp. After that I wipe all partition, forgot to uncheck system. Than I flashed custom firmware.

Now I have NOOK logo. i'm able to do factory reset. But if can't help. Windows cannot identify device

What should I do? I can open my Nookand connect via UART. But what's next?
[Nook Touch General] Renate:
Presumably you now have a Glow2 with no installed Home app and the ADB turned off?

You can look in (Windows) Device Manager and see what it's presenting over USB.

Or download imxlink.exe (in sig) and see which "LEDs" light up.

C:\>imxlink.exe

If you can do factory reset, I'd try that.

I don't know what you flashed this with.

If you can fix this without opening it would be easier.
[Nook Touch General] dmkbox:
My nook glowlight plus. My mistake, I format system partition from TWRP.

When I start imxlink.exe and connect device only MTP light on.
[Nook Touch General] Renate:
Which means that the stock Nook is running, without the ADB enabled and somehow you have no Home app.

What the heck did you put on this?

You can try doing 8+ times letting it boot up halfway and hit a long reset and see if you can get it to go to recovery.

Recovery is only useful if you can get there.

That's why total failure is good, it will try something else.

Halfway success is bad, it won't try other things.
[Nook Touch General] dmkbox:
Nothing works.

I'm ready to open book. But what`s next?
[Nook Touch General] Renate:
Just to be sure...

You had ADB working before on the desktop?

Just double check:

C:\>adb kill-server
C:\>imxlink.exe

You have a 3.3 V UART, like Adafruit FTDI Friend or something?

It's (in worse case) like this thread: https://xdaforums.com/t/fixing-a-dead-glow-glow2-brnv510.4229851/

But in your case, all you really need to do is install a launcher.

# settings put global adb_enabled 1
# setprop sys.usb.config adb
# setprop persist.sys.usb.config adb
# getprop sys.usb.state
[sys.usb.state]: [adb]

(This is complete overkill, but hey.)

C:\>adb install whatever.apk
C:\>adb reboot
[Nook Touch General] dmkbox:
Yes. I'm used adb to boot to TWRP.

Sure, not work.

In next few days I will get all this stuff.

I will post my results. Thanks.
[Nook Touch General] Renate:
@nmyshkin had some secret finger swipe to get to recovery without that 8 times boot failure.

I can't seem to find it on search (or anything else, actually).
[Nook Touch General] nmyshkin:
I wish. I don't think it actually goes to recovery but rather is a shortcut to wiping user data or effectively deregistering without being online. Still, here is what "works" for the NST:

Turning the Nook off completely

Turning it on

As soon as you see the screen flash begin holding the bottom page turn buttons until the screen flashes with a message asking if you would like to do a reset

Press the 'n' key twice to start the reset

In NookManager the actual return to factory script is:

mount -t vfat /dev/block/mmcblk1p1 /sdcard

mount -t vfat -o remount,rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=117,dmask=007 /dev/block/mmcblk0p2 /rom

cp /sdcard/files/rom/devconf/BootCnt /rom/devconf/BootCnt

sync

mount -t vfat -o remount,ro,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=117,dmask=007 /dev/block/mmcblk0p2 /rom

umount /sdcard

and this is the content of /sdcard/files/rom/devconf/BootCnt on the NookManager sdcard reads in Notepad++ as "BSNUL" (two white-on-black characters with no space between), probably a binary file with the value "8". But you could probably guess that.

Using that or similar without NookManager would require functioning ADB.
[Nook Touch General] dmkbox:
HI!

I`m successfully connect to console and get

U-Boot 2009.08-00728-ga4ff22e-dirty (Apr 09 2017 - 22:25:18)

CPU: Freescale i.MX6 family TO0.0 at 792 MHz

Thermal sensor with ratio = 180

Temperature: 43 C, calibration data 0x5754f75f

mx6q pll1: 792MHz

mx6q pll2: 528MHz

mx6q pll3: 480MHz

mx6q pll8: 50MHz

ipg clock : 66000000Hz

ipg per clock : 66000000Hz

uart clock : 80000000Hz

cspi clock : 60000000Hz

ahb clock : 132000000Hz

axi clock : 198000000Hz

emi_slow clock: 99000000Hz

ddr clock : 396000000Hz

usdhc1 clock : 198000000Hz

usdhc2 clock : 198000000Hz

usdhc3 clock : 198000000Hz

usdhc4 clock : 198000000Hz

Board: MX6SoloLite-NTX:[ POR ]

Boot Device: MMC

I2C: ready

DRAM: 512 MB

MMC: ram p=80000000,size=536870912

mmc0(part 0) is current device

MMC read: dev # 0, block # 1023, count 1 ... 1 blocks read: OK

MMC read: dev # 0, block # 1024, count 1 ... 1 blocks read: OK

FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2

hw_anadig_reg_core=7c3e1f

MMC read: dev # 0, block # 34815, count 1 ... 1 blocks read: OK

MMC read: dev # 0, block # 34816, count 1516 ... 1516 blocks read: OK

*** Warning - bad CRC or MMC, using default environment

In: serial

Out: serial

Err: serial

ntx_hw_late_init()

ntx_config_fastboot_layout():7 binaries partition added

ntx_config_fastboot_layout():7 mbr partition added

Detecting Magic keys for recovery ...0 0

Checking for recovery command file...

mmc0(part 0) is current device

Partition Map for UNKNOWN device 0 -- Partition Type: DOS

Partition Start Sector Num Sectors Type

1 2048 12224 83

2 38912 65536 83

3 104448 1605569 5 Extd

4 1710017 5990459 83

5 106496 786416 83

6 894960 786416 b

7 1683424 16368 83

8 1701840 8176 83

Writing recovery BCB to misc partition...

mmc read 0x875ffd40 0x19f7d0 0x1

MMC read: dev # 0, block # 1701840, count 1 ... 1 blocks read: OK

Recovery BCB found, skip count!

Net: No ethernet found.

Detecting Magic keys for fastboot ...0 0

Hit any key to stop autoboot: 0

eBR-1A #

What's next? Your commands not recognized by console. I can execute fastboot command but got

fastboot initialized

USB_RESET

USB_SUSPEND
[Nook Touch General] Renate:
No, they wouldn't be. That's the u-boot console. The commands I quoted were for the Linux console.

Did you hit a key to stop the regular boot?

If so, just let it boot and try my Linux commands.

If not, then try the u-boot "boot" command.

If nothing works, you have to get fastboot working.

There may be a problem with the drivers on your desktop.

Use imxlink or usbview to see what your Glow is presenting when you have told u-boot to fastboot.
[Nook Touch General] dmkbox:
I'm stop regular boot. Than start fastboot.

Got

fastboot is in init......flash target is MMC:0

USB Mini b cable Connected!

fastboot initialized

USB_RESET

USB_SUSPEND

Imx link shows yellow but crashes.

Adb cannot show any devices

Also got ADB interface in device manager.

If I try normal boot I've got this

mtp_bind_config

mtp_bind_config

binder: 2012:2012 transaction failed 29189, size 0-0

arch/arm/mach-mx6/mx6_mmdc.c(282) update_ddr_freq(24000000)

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

binder: 2012:2012 transaction failed 29189, size 0-0

continuously
[Nook Touch General] dmkbox:
del
[Nook Touch General] Renate:
Binder failures are simply a sign of Android having a major headache.

Don't flash, simply fastboot boot.

You can try the NeoNoogie (in the sig) as a reality check.

C:\>fastboot boot nnglow?.img
[Nook Touch General] dmkbox:
After few attempts I successfully load whatever.apk , thеn TWRP thеn I reflashed custom image.

Renate NST​

Thanks for help!
[Nook Touch General] curtisk:
Happen to remember which test point disabled the eMMC? (for the glow3)

And any luck with changing the boot options via the GPIOs? (Though I'm guessing that the fuses are burned and the boot config registers are stuck).

I'm thinking of playing around with NXP's newer uboot/kernel/android sources but I'd like to know that I can recover from the "not quite dead enough" state before diving in.
[Nook Touch General] Renate:
No, it was pretty much hit/miss.

I'd try the two small gold test points on the far corner of the Samsung chip.

Just use a resistor, a few hundred ohms to ground.

That will be high enough that if you hit power or something nothing will be harmed, but low enough to screw up data communications.

The number of occasions you'd have to do this is pretty rare.

As you can see from that other thread, the Onyx Boox Poke3 is comparatively a piece of cake.

https://xdaforums.com/t/has-the-nook-had-its-last-gasp.4141735/page-5#post-85025339

Having the Qualcomm EDL bootloader available under any circumstances is helpful.

Moreover, you need no long pushes! It seems that I've spent half my life holding reset buttons for 10-30 seconds.
[Nook Touch General] robonxt:
I've recently pulled out my Glowlight Plus, and flashed TWRP. I was installing a custom ROM when I forgot to unmount the system according to the instructions, and now the nook is perma stuck at the nook logo. I read this thread as it seems like my best bet to get back to recovery, but no dice for fastboot or adb mode. dmkbox mentioned that they ran into the same problem, and they resolved it using a UART, I have something similar already, but how would I wire it up to the nook?
[Nook Touch General] Renate:
The first thing to check is if you still have ADB. The display not going to your launcher is no exact indication of what's going on. If you have ADB, obviously you just reboot recovery (or bootloader).

You can try resetting a whole bunch of times and see if it exceeds boot count and goes to recovery.

Yes, you can hook up a 3.3V UART at 115200-8-n-1 to see what's going on.

There are two problems with this: Unless you have new special Tesa film to put back on and the time and patience to redo it, opening and closing the Glow2 will not leave it quite the same. Also, watch out, the touch panel flex printed circuit is too short and it will pull out of the connector if you aren't careful.
[Nook Touch General] robonxt:
Thank you @Renate !

After following your wiring and playing around with console + adb combos, I got it back to twrp and reflashed the rom. I ended up having to use adb sideload to flash in twrp, as twrp install continued to have issues even with unmounted /system.

Note to future self when stuck at boot screen:

1. use FTDI 3.3v to connect to left side pins, console speeds set at 115200 8n1

2. spam fastboot in console at reboot

3. type fastboot boot <recovery_maybe_is_twrp>.img in adb terminal.

4. while in recovery mode, install rom to heart's desire using recovery built-in installer or adb sideload <new_rom>.zip from computer terminal

5. profit
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Goneg:
Hello! Im having some trouble with my phone. I tried to installed custom rom via TWRP but something whent wrong and now I can't get out of fastboot mode. It just keeps on rebooting to fastboot mode no matter what I have tried.

- Tried flashing Global, China, EEA, with fastboot rom threw Xiaomiflash but without sucess. It finished in like a second but still with the same result.

- Tried flashing TWRP threw fastboot but with no success. It writes and all that but it wont boot to it. Just keeps coming back to fastboot mode.

- Tried diffrent versions of Xioamiflash - No luck.

So i have no idea left of what to try. Do u guys have any ideas?

Thanks in advanced.
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] nosiobadx:
Go to telegram on havocOS grp and download the twrp and flash it through fastboot
[Samsung Galaxy Fold Guides, News, & Discussion] keyz86:
Seems like an obvious idea that Samsung missed but I thought it would be cool if when using the camera with the main screen, the front screen could also be on showing the person you're taking a photo of a live preview.

If Samsung is lurking here maybe we could see it an update.

Anyone else think this is a good idea?
[Samsung Galaxy Fold Guides, News, & Discussion] STEVEcKONG:
I had a similar idea when I used my phone for vlogging, if I could open the fold and still use the front screen for the framing of the shot, it could be great... but I doubt Samsung would do it...
[Samsung Galaxy Fold Guides, News, & Discussion] _sC:
its a small screen for anyone to see from a proper distance away, but yes it would be an added benefit regardless.

but i agree with the previous user. i doubt samsung would do it.

i think there is too much concentration on the S11 and Fold 2 at the moment, i don't think they will add very many "quality of life" updates to the fold.
[Samsung Galaxy Fold Guides, News, & Discussion] shameemindia:
https://xdaforums.com/galaxy-fold/themes/view-resolution-camera-unfolded-galaxy-t4110369
[Samsung Galaxy Fold Guides, News, & Discussion] hashcheck:
I have switch to use front screen with latest update and Camera app ver
[Android Apps and Games] samsungcuadem:
xBrick Block Game requires players to strategically rotate, move, and drop a procession of blocks that fall vertically into the rectangular Matrix. Players attempt to fill and destroy as many lines as possible by completing horizontal rows of blocks without empty space, but if the blocks surpass horizontally the Skyline the game is over!

Retro xBrick Block game again on mobile phones!

in xBrick Block Game you can use different blocks:

I - blocks are useful for competing four lines at once.

O - blocks are great for filling large gaps.

L - blocks are great for filling medium-sized holes.

J - blocks face the opposite direction as L - blocks.

S - blocks are great for filling small holes.

Z - blocks face the opposite direction as S - blocks

Features

- Compare scores

- Original screen graphics

- Original sounds and music

- Amazing to spend your time

- Play using buttons. Like old retro gameboy!

- Adjustable drop speed

- Endless mode

- Arcade Mode

- 8 difficulty categories

- No internet request

- Time countdown mode

Classic xBrick Block Game is free and fun

Get it on Google Play
[Android Apps and Games] ArrowStrike:
Arrow Strike

After quite a lot of time I've been working on it – My first serious project, Arrow Strike, is now available on the Google Play.

This game features unique and not copied, different concept compared to other games on the Google Play which are trying to emulate the big shot games.

In This game you're playing an Arrow.

Different colored hoops are appearing one after another, coming from different directions while moving in different speeds – Your goal is to match the color of the Arrow to the Color of the hoop and quickly shoot the Arrow trying to hit the center of the Hoop.

For a perfect shot (hitting the center of the Hoop) you get 2 points, while for any other successful shot you get 1 point.

But it's not as easy as you might think....

The Game Timer is ticking.

The Hoops are becoming faster and faster, starting to do some "weird stuff" (no spoilers here, my friends) – Now it becomes a true challenge!

Are you skilled enough to keep up in a race against yourself and time all at once? Would you be able to survive and become The Perfect Arrow Striker?

Well, you can give it a try and see for yourself. (:

*The game does not contain Ads at all!*

Some screenshots from the game:

Wanna give it a try?

You can download it by clicking here or on the picture down below.

​
[Windows Mobile Development and Hacking General] kidnamedAlbert:
you should add my htc home or my audiomanager

:D
[Windows Mobile Development and Hacking General] infernalshade:
Your HTC Home, yes of Course, but your Audio Manager is just for the Audio-Manager and not a Theme for the WM-shell :) But good work anyway!!

greetz,

infernalshade
[Windows Mobile Development and Hacking General] philocritus:
Throttlelauncher!!!!

You forgot the best one out there!!

;)
[Windows Mobile Development and Hacking General] infernalshade:
Hey thx, maybe its better than the MobileShell one :)

I'll test it now..

greetz
[Windows Mobile Development and Hacking General] infernalshade:
Is there a Graphics driver out there for Kaiser to use the Orig Manila?!
[Windows Mobile Development and Hacking General] flaviopac:
No, it's impossible....
[Windows Mobile Development and Hacking General] infernalshade:
Why?

Kaiser has an Graphics Card and i think good Specs (400Mhz, ...)
[Windows Mobile Development and Hacking General] mchapman007:
All these themes are great... Thanks for posting....
[Windows Mobile Development and Hacking General] alexnad123:
any version working on VGA?

no VGA theme found so far
[Windows Mobile Development and Hacking General] sanderz6900:
Don't forget these....

http://forum.ppcgeeks.com/showthread.php?t=28663

http://forum.ppcgeeks.com/showthread.php?t=28385

http://forum.ppcgeeks.com/showthread.php?t=27868 (3D not MS)
[Windows Mobile Development and Hacking General] richabi:
excellent idea! your thread is VERY helpful. THANKS! If i come across anything else I haven't seen here, I will let you know.
[Windows Mobile Development and Hacking General] Nikole:
Thanks nice thread, very helpful
[Windows Mobile Development and Hacking General] infernalshade:
Well the original Manila Theme is VGA...but its not working for now...

Maybe the MobileShell One support VGA?! I don't know, try it!

greetz,

infernalshade
[Windows Mobile Development and Hacking General] infernalshade:
Well the first one is just a S2U2 Theme and not a WM-Makeover!

The Second one, yes, i'll update :)

The third one is the MobileShell one i've already posted!
[Windows Mobile Development and Hacking General] theme freak:
It is more better to post whether the themes work for what type of device..because its really a problem for VGA users if after they installed it, they found out its for QVGA :(
[Windows Mobile Development and Hacking General] sanderz6900:
The third one I specify to try the 3D not Mobile Shell one. There are two different links to two different themes. Try the 3D Diamond one by AM1759.
[Windows Mobile Development and Hacking General] philocritus:
VGA apps being in small number as opposed to to QVGA are always labelled.

so:

if labelled VGA... it's VGA or has VGA support.

if not labelled... no VGA or "at your own risk" VGA support.

That's my view, of course some posters might forget about it :)

About the diamond 3D... I've always seen it as a variant to greatbal's. It's another SPB mobile shell theme...

UI is the same as greatbal's, just glossy... Very good notheless!!

Besides, on the same post as greatbal's and 3D you have a white diamond theme and dozens other variants.

The white/blue theme is also available on throttlelauncher.
[Windows Mobile Development and Hacking General] infernalshade:
Huh?! I see two Themes, but it seems, theyre both for MobileShell!

What do you think for which Program this Skin is?!

greetz

infernalshade

PS: Sadly i cannot try which Programs have VGA-Support and which not...To test it, i must have a VGA-Device, but i haven't one!

And i don't think anyone would Donate for this little Thing...I mean, the easiest way to see for what Device is:

-Make a Backup with SPB Backup

-Install the App and see!

-If you don't like the Theme or it's not working, Restore the Backup...
[Windows Mobile Development and Hacking General] infernalshade:
Yes...i made it ;)
[OnePlus 7T Pro 5G McLaren Questions & Answers] Goku1992:
Hey guys, got my 7t McLaren yesterday amazing device. But its late now so screen is dim and using dark mode with Samsung browser, low brightness and i can see a small cicle where the fingerprint is.Have a panzerglass on my screen so maybe its reflecting the light to the sensor? Is this normal behavior?

My mate 20 pro dont have this (also with UV glue panzerglass)

Thanks guys :)
[OnePlus 7T Pro 5G McLaren Questions & Answers] jaythenut:
No I've not got that at all ?