yashsingh1/xdaforums huggingface dataset:
[Nook Touch General] dmc123:
No response, fastboot boot nnglow4.img then heard the sound of disconnection, NOOK screen is not displayed, do I use the wrong command to enter FASTBOOT, this is not the correct method?

Ienter fastboot?
[Nook Touch General] dmc123:
It stopped here after I wrote nnglow4.img
[Nook Touch General] Renate:
Yes? And what happened to the screen?

Was there ADB available.

Please, no graphics of text, just copy/paste the text in [code][/code]
[Nook Touch General] dmc123:
Nothing appears on the screen. There must have been a problem during the reboot. I'm a little skeptical that this fastboot isn't the fastboot that used to be used on previous Android flash rom
[Nook Touch General] dmc123:
In fact, now boot can be normal into the system. It's just possible that the touch driver is damaged (touch is reactive and unlocks the screen, touch each area and you'll see the PUTTY is reactive). I have solder the sdcard slot onto the board (because of touch issues, connecting the computer cannot be clicked to allow the connection). Or where can I download the official firmware and put it on my SD card to upgrade or restore it to fix the driver?
[Nook Touch General] Renate:
http://su.barnesandnoble.com/nook/piper/5.3/quill/0.67/update.zip
[Nook Touch General] dmc123:
Thank you very much. I'll report back in a few hours later
[Nook Touch General] dmc123:
Maybe I was wrong to think it was too easy.After reading other guides ，maybe directly put update.zip on the SD card is not able to upgrade, restore the system.
[Nook Touch General] dmc123:
perhaps the reason why I could not flash boot and recovery partitions under fastboot is that I have not enable ADB debugging in the system Settings (because of touch issues, I could not enable ADB debugging, and I could not use the mouse with OTG adapter and Y-USB cable). If there's no way through uboot, there's no way out
[Nook Touch General] dmc123:
I have tested it and even with OTG converter (ID pin connect to GND) ，special USB Y cable with USB power (5V), it doesn't work. NOOK can not recognize, U disk and mouse are not good, may have to modify the system file?
[Nook Touch General] Renate:
I don't know where you are going with all this.

You can't boot nnglow4 but you're talking about touch sensors, SD cards, OTG...

There are parts of the flash that if you corrupt will prevent nnglow4 from booting.

There is also imxlink.exe for booting from the iMX6 ROM bootloader.

Try this:

imxlink ub4fb.img nnglow4.img

Then hold the power button for ~10 seconds until it resets.
[Nook Touch General] dmc123:
When only the USB cable is connected.Run the command in a normal Windows shell and reset the Glow with a long power press , The NOOK is not responding. .But if I open fastboot in UBOOT then with the command 'fastboot' , it just responds, but the write fails. 'Could not read device'

C:\Users\book\Downloads\Programs>imxlink ub4fb.img nnglow4.img

Waiting for bootloader or Fastboot or ADB...

product i.mx6sl NTX Smart Device

version 0.5

Sending boot image, 6131712 bytes...

Could not write device

C:\Users\book\Downloads\Programs>imxlink ub4fb.img nnglow4.img

Waiting for bootloader or Fastboot or ADB...

Could not read device

and putty show :

eBR-1A # fastboot

ptn 0 name='mbr' start=0 len=1

ptn 1 name='sn' start=1 len=1

ptn 2 name='bootloader' start=2 len=1022

ptn 3 name='hwcfg' start=1024 len=2

ptn 4 name='ntxfw' start=1030 len=256

ptn 5 name='waveform' start=14336 len=20480

ptn 6 name='logo' start=34816 len=4096

ptn 7 name='bootenv' start=1536 len=510

ptn 8 name='kernel' start=2048 len=12284

ptn 9 name='rootfs' start=13631484 len=1605633

ptn 10 name='vfat' start=1567715 len=12063769

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

USB Mini b cable Connected!

fastboot initialized

USB_SUSPEND

USB_RESET

cmdbuf: getvar:product

send: OKAYi.mx6sl NTX Smart Device

cmdbuf: getvar:version

send: OKAY0.5

cmdbuf: download:005d9000

Starting download of 6131712 bytes

send: DATA005d9000

................................................................................

.........
[Nook Touch General] dmc123:
I saw your old thread：

If MTP is showing then Android has loaded.

I guess that you don't have ADB enabled?-------------------------------------As I said before, I didn't go into the Settings on the NOOK to turn on ADB debugging because of touch issus

If ADB were enabled you could see your problem and fix it directly.

It could be as simple as that you don't have a "Home" application available.

You need to do the command I said imxlink.exe u-boot.bin recovery.img

Then do a long power button press to reset.

Those two files are in the zip.

If you can see MTP there, can you see in in Windows File Explorer?

Are there files that you want to back up before doing anything else.

You're not doing the command I told you.

You need u-boot.bin and recovery.img copied into the same directory as imxlink.exe

You need to run the command like I said.

Did you open a Windows command shell first? Windows-R, then cmd.exe

You want to reset the device after you run the command and look for Bootloader to light up, then Fastboot, then ADB.

I'm sure I did, but I want to know if I can run imxlink just by connecting the NOOK to my PC with a USB cable?
[Nook Touch General] Renate:
Why so loud?

If you quote things, please quote them properly.

I told you what to do.

If it doesn't work that's because you screwed something up that is preventing it from working.

It looks like you broke the partitioning somehow.
[Nook Touch General] dmc123:
bro , i have found the way to open the neo Noogie screen. what should i do after i see the 'neo noogie' appear on the screen?
[Nook Touch General] dmc123:
Sorry, I don't know how to refer to another thread's reply here, so copy and add red to show that I did what you said
[Nook Touch General] dmc123:
Why is there no detailed usage in this thread? How to backup and restore? https://xdaforums.com/t/neo-noogie-full-backup-restore-for-glow2-3-4.3784575/

I have successfully opened the NEO NOOGIE window (use uboot open fastboot) .now how to backup and use the official firmware(download here) update again?
[Nook Touch General] Renate:
So you have NeoNoogie working now?

Now get ADB working.

You need to load drivers and run adb.exe

It's all in the internet.
[Nook Touch General] dmc123:
Wait, while the NOOK screen shows neo noogie, the CMD window still shows Waiting for disconnect... Waiting for ADB... And the imxlink window displays MTP. Should I unplug the USB cable and reinsert it?

C:\Users\book\Downloads\Programs>imxlink ub4fb.img nnglow4.img

Waiting for bootloader or Fastboot or ADB...

Found iMX6SL

Status: Frozen

Load addr 87800400, DCD offset 002c, DCD size 0240

71 DCD ops processed

Write, addr 87800400, size 00039530

**************************************************************************************************************************************************************************************************************************************

Jumping to 87800400

Device disconnected correctly

Waiting for Fastboot or ADB...

product i.mx6sl NTX Smart Device

version 0.5

Sending boot image, 6131712 bytes... ok

Sending boot command...

ok

Waiting for disconnect...

Waiting for ADB...
[Nook Touch General] dmc123:
In a strange twist, NOOK storage can now be accessed using linux commands in uboot.

But it keeps popping up

# pwd

/

# [ricoh61x_displayed_work-2096] soca status 6

[ricoh61x_displayed_work-2162] status 1, DSOC 9958

PMU: ricoh61x_displayed_work Full-Clear CC, PSWR(100)

ls

RTL8189_init.rc file_contexts proc sys

acct fstab.E70Q50 property_contexts system

charger init root ueventd.E70Q50.rc

data init.E70Q50.rc sbin ueventd.rc

default.prop init.E70Q50.usb.rc sdcard

dev init.rc seapp_contexts

etc initlogo.rle sepolicy

▒▒^B^B^B^B^B^B▒▒▒▒^B^B^B^B^B^B▒▒▒▒▒^B^B▒▒▒▒^B^B^B^B^B▒▒ ^B^B^B^B^B▒? ▒▒^@ # [get_power_supply_status-4397] chg 3 SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) thaw-filesystems(J) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) Sync show-task-states(T) Unmount ETM buffe
[Nook Touch General] Renate:
You're not in uboot.

You're in Linux.

Why don't you get ADB working.

It's already enable in NN.
[Nook Touch General] dmc123:
I don't know. the nook screen display NEO noogie nook glow 4 built december 25..... I was too happy. Desperate... Or this is a test phase machine? watse of life
[Nook Touch General] Renate:
Unfortunately at XDA we don't have any specific award for jumping to conclusions.

You're running NN.

You can type at it over UART but you'll be distracted because it's a console.

You can't transfer files over the UART, you need ADB.

Instead of complaining why don't you just figure out how to get ADB running on your desktop?
[Nook Touch General] dmc123:
How to solve this problem is also what I want to know. This ADB on my computer was downloaded when I was flashing the pixel rom (from the official Google developer website), and has been successfully flash on several mobile phones. Google search minimal ADB download also tried, the problem should be the NOOK can not jump to the corresponding mode rather than ADB can not run on my computer?
[Nook Touch General] Renate:
Use Device Manager (devmgmt.msc), look for something.

Does it "bong" when you plug it in?
[Nook Touch General] dmc123:
Using the uboot method to access fastboot I'm sure there's new hardware in the device manager. However, after the screen showed NN, I was sure that there was no hardware like the former, and I remember that it did not “bong”, and the NOOK should be in a state of downtime（Dead state）
[Nook Touch General] dmc123:
is it because I've never turned Debug mode（such as developer option /usb debug） on in the NOOk's system Settings before? I thought that it could be enable that option by connecting the mouse to OTG like a pad(nook touch issues), but it failed because the mouse has no response.
[Nook Touch General] Renate:
The subject now is NeoNoogie.

I'm not talking about uboot or touch screen or mice or Android settings.

Do what I said to run NeoNoogie. Do you see the splash screen? Now, find ADB.
[Nook Touch General] dmc123:
Of course I know, but isn't this unfixable now? the NOOK's splash screen .but in the IMXLINK window(CMD), stock at Waiting for ADB... There's nothing in the device Manager and it's not "bong" .I've tried, but it's not working, so should I try something else?
[Moto G6 Play Questions & Answers] blowingoff:
Well, people, i've been trying to use GSIs on my aljeter since i bough it, but Google seems to be a major issue. First, sometimes i don't get to register the phone, simply doesnt work, even if i try to graf the gsf many times and all these times i do clean google services storage, i keep getting unregistered.

But then, sometimes i DO get to register and use the services but... i can't install many apps because they kind of act like they were already installed and i have no option to uninstall, literally as if i was opening playstore on my pc browser with my google account logged.

I really have no idea about any of these becuase this is the first time i try to use GSIs
[Xiaomi Mi 8 Pro Guides, News, & Discussion] thanas:
let me know if there is interest for my kernel. if so i can port and maintain it for your device officially.

more info:

https://xdaforums.com/poco-f1/development/kernel-malakas-kernel-t3909282

if so it would need to pass serious testing, since i have the poco f1 i cannot do that myself.
[Xiaomi Mi 8 Pro Guides, News, & Discussion] halim_wijaya58:
i'm waiting for it
[Xiaomi Mi 8 Pro Guides, News, & Discussion] ste2610:
I'd be interested
[Xiaomi Mi 8 Pro Guides, News, & Discussion] 李小控:
Thanks

I 'm waiting for it too
[Xiaomi Mi 8 Pro Guides, News, & Discussion] Infam0uspt:
That would be perfect, waiting for it ;)
[Xiaomi Mi 8 Pro Guides, News, & Discussion] SpyRoNoS:
I can help with testing
[Xiaomi Mi 8 Pro Guides, News, & Discussion] kevte89!:
Let us have a test kernel there, we like to test it
[Xiaomi Mi 8 Pro Guides, News, & Discussion] mateHD:
I am interested

---------- Post added at 02:52 PM ---------- Previous post was at 02:51 PM ----------

Can you allow usb ethernet or external wifi adapter?
[Xiaomi Mi 8 Pro Guides, News, & Discussion] nealed:
Interested. I also have some professional software testing experience and so could perhaps provide help if you could provide a kernel? ;)
[Xiaomi Mi 8 Pro Guides, News, & Discussion] Kartun:
and1
[Xiaomi Mi 8 Pro Guides, News, & Discussion] nealed:
Also, if any work is being done on this kernel, compatibility with the under screen fingerprint sensor would be really helpful...
[Tilt, TyTN II, MDA Vario III General] s2kver02:
Can anyone help me on this? it annoys me everytime i send a text message i have to go to sent messages just to check if the message was sent.
[Tilt, TyTN II, MDA Vario III General] redbandana:
There is no need to check sent messages. If the message wasn't sent you'll receive "Message was not sent. Try again?" in red text.

But if you want to activate the notification of a sent message do this:

start>programs>system tools>advancedconfig> scroll down to messaging and enable sms sent notification

if you don't have advancedconfig this option is also available on kaisertweak.
[Tilt, TyTN II, MDA Vario III General] s2kver02:
Thanks redbandana.
[OnePlus 7 Pro Questions & Answers] Dameon87:
Hey all, has anyone had issues installing the first update for the T-mobile OP 7 Pro?

I get a message: Couldn't Update, Installation problem (9.5.5.GM31CB)

Trying again results in the same message. I've tried factory reset, clearing cache, etc to no avail.

Has anyone else ran into this? And if so, how did you fix it?
[OnePlus 7 Pro Questions & Answers] justibasa:
No issues here. Sorry.
[OnePlus 7 Pro Questions & Answers] JhinCuatro:
If this is still somehow an issue, refer to unlocking your bootloader, and/or converting to international version..
[Samsung Galaxy S10 Guides, News, & Discussion] chalofito:
I was thinking of a way to block the bootloader, and I came up with something very basic, so please who can try the method, share whether it works or not. (This method was checked and it WORKS !!)

Warning: I am not a super developer, just one more user who wants to help the community

Warning 2: This Process will erase everything in its path, remember to make a backup of your internal memory.

This series of steps is aimed at inexperienced users, if you think you are missing or there are many steps, this guide is not for you.

Without more to say, let's start.

How to re-lock bootloader:

1. Turn off your device.

2. Press Bixby Volume down and connect your device to a PC to start the download mode (now you can release both buttons)

3. Read the text below on the Download Mode screen

to block or unblock the Bootloader.

4.- Long press the vol (- or +) button as best suits you.

LOCK BOOTLOADER:

5. Long press the volume up button ( ) until the computer is restarted (this will erase your data and restart automatically). :fingers-crossed:

Ready! Now you have a device with an OEM lock.

Good luck my friends!!! :D
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
Thank you for posting this. I've had this method work once before but i am in a bit of a pickle at the moment.

I no longer get the options to 'long press vol up' which i think is the key to re locking the bootloader. Have you or anyone else got any idea why that would be?
[Samsung Galaxy S10 Guides, News, & Discussion] chalofito:
This was tested once and it worked, it was not tried for the second time .. What version of Compilation do you have?
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
It has definitely worked before but not having much luck now. Maybe the latest software update has blocked this method?

This is my current version. I'm in Australia.

View attachment 4767541
[Samsung Galaxy S10 Guides, News, & Discussion] chalofito:
It's a shame, I'm sorry that this happens to you, we hope that in the future this will be solved, for the moment we have to wait. someone will come who finds a definitive solution.
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
Thanks for your help. Yes, hopefully soon someone will find a method.
[Samsung Galaxy S10 Guides, News, & Discussion] SakazukiAka:
Can you tell what exactly you already did with your phone? Did you unlock bootloader, re lock bootloader, then unlocked it again and then actually rooted it? And now after you unrooted your phone you can not re lock bootloader?

I am asking because I suspect that you can not re lock you bootloader again after you actually have rooted your phone once. I am suspecting I only read a post from a guy who managed to re lock is bootloader but he never actually rooted his phone once. So in other words after you tripped knox (which seems to only happen when you install magisk) you may not be able to re lock you bootloader (ever) again.
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
Yes!! You hit the nail on the head!! So i was able to re lock bootloader once before but i wasnt successful in rooting the phone. After i then successfully rooted the phone with Magisk i restored back to normal and no i cannot re lock the bootloader.

It seems as though a few people have said you can't re lock it after successfully rooting! Quite frustrating!!
[Samsung Galaxy S10 Guides, News, & Discussion] SakazukiAka:
I see. There is another method, that seems to work, tested by [MENTION=499148]robbo1947[/MENTION] that he explained here.

I did not check it myselff yet, but it worked for robbo1947. All credits goes to [MENTION=499148]robbo1947[/MENTION] !! Please let us know if that worked for you or not.
[Samsung Galaxy S10 Guides, News, & Discussion] robbo1947:
I am going to have a go again in the next few days to prove to myself and others that it is possible to relock the bootloader after rooting. Will let you know.

Watch this space.
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
I look forward to your findings. As i am running my phone as my daily driver now i am hesitant to re root it if this method wont work. I have my fingers crossed though :)
[Samsung Galaxy S10 Guides, News, & Discussion] Lebrun213:
samsung doesn't allow you to unlock and then lock back the device multiple times. It only works once, then your bootloader stay unlocked for ever.
[Samsung Galaxy S10 Guides, News, & Discussion] drago122:
I I had root and twrp on my s10 + but I quietly put the last nobrand ASE7 firmware back and I re-locked the bootloader without any difficulty I no longer have any warning messages at startup and in the developer options I have the oem option working like new.
[Samsung Galaxy S10 Guides, News, & Discussion] robbo1947:
OK, sorry for delay in getting back to this question of locking and unlocking the bootloader on the Galaxy S10.

During the last few days I have locked, unlocked, locked and unlocked again, probably 15 or 20 times to test various scenarios.

Please remember, each time you lock or unlock the bootloader all of your data is wiped.. any Root will also be gone. You will also be needing your current firmware.

This is for the Galaxy S10 without TWRP.

Scenario 1.

Your phone is rooted with Magisk.

Go into Developers options and check OEM options, the switch must be ON (to the right). If it isn't turn it ON.

Turn off your phone. Press and hold the Bixby and Volume-down button, then connect with USB to your computer. (The cable shouldn't be connected until after you press the buttons).

Within seconds of USB connection the Download screen will appear. You will see 3 optiions, choose and Long press volume up and hold button until you see the 2 options at bottom of screen. Choose and hold volume up until screen goes off. Then the S10 logo screen will briefly apppear, before it flicks back to the Download screen with the words 'VBMETA: Error verifying vbmeta image etc' at the top, as the image below.

This is all good so far. Leave the phone exactly as it is with this screen showing and make sure the phone is still connected to the computer.

On your computer, fire up Odin3_v3.13.1, you can leave the Reboot option in Odin ticked. Locate your firmware on your computer and put the 4 file parts (BL, AP. CP and CSC) into Odin.

Let Odin finish.

The phone will reboot ready for setup.

The Unlocked bootloader warning screen will be gone.

Scenario 2.

Your phone has been rooted but isn't now, and the greyed out OEM switch is ON

Easy, turn off your phone and proceed from the 2nd paragraph of Scenario 1.

Scenario 3

Your phone has been rooted but isn't now, and the greyed out OEM switch is OFF

Sorry, but in this situation, you are going to have to root your phone with Magisk as the OEM switch will only be available when rooted.

When rooted, proceed as Scenario 1.

Scenario 4

Your phone has never been rooted, and the greyed out OEM switch is ON i.e. you unlocked the bootloader but never proceeded to root the phone

Turn off your phone and proceed from the 2nd paragraph of Scenario 1.

If you want proof that I have locked and unlocked time and time again see HERE

:victory:
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
No dramas, thanks heaps for your reply.

So it seems I am in scenario 3 meaning I'll need to re root my phone which is fine. However, when I hold down the bixby and volume up and plug in I don't get the option to long hold volume up which I previously did. I only have press volume up or down. Is this because my bootloader is already unlocked? I should still be able to re root my phone in this scenario shouldnt i?
[Samsung Galaxy S10 Guides, News, & Discussion] robbo1947:
Yep, your bootloader is unlocked.

When you have re-rooted and you go into Developer options you will be able to control the OEM switch and ensure it is ON.

Then when you get into Download mode you will see that option of LONG press Volume-up.

I've just added video proof to original post.
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
Awesome. Will give it a go in the next day or two and report back but given your success I'm hoping I'll have the same.

Cheers
[Samsung Galaxy S10 Guides, News, & Discussion] robbo1947:
Don't forget the :good:
[Samsung Galaxy S10 Guides, News, & Discussion] akkaria:
You sir, are my hero. It all worked perfectly and i no longer get the bootloader warning screen and my bootloader is now relocked!!

For anyone else having this problem, i too can confirm that this method works. The only issue i had was that for some reason, i was stuck on the Samsung flashing boot screen for nearly half an hour. A simple reboot into recovery(hold power and volume down for 7 seconds to shut down and then quickly hold power, vol up and bixby) and wipe factory data then system reboot fixed it.

I can also confirm that after doing this and re locking the bootloader, i now have access to all apps that i was previously having issues with and my google play store recognises my devices as certified.

I now have a fully working and functional device. Thank you again.
[Samsung Galaxy S10 Guides, News, & Discussion] nikolas60:
if i revert to stock rom after root and samsung status says official and relock bootloader will be able to get otas again???
[Samsung Galaxy S10 Guides, News, & Discussion] robbo1947:
Over the air update functionality is restored upon relocking the bootloader.
[Samsung Galaxy S10 Guides, News, & Discussion] VITHOR3E:
This method is right
[Samsung Galaxy S10 Guides, News, & Discussion] adzo73:
Is there somewhere other than samsmobile to get latest firmware for S10plus exynos beceause for some reason its impossible for me to download fr o m there and its not the first time I've encountered this problem there and this time i desperately need genuine firmware to lock etc as i need to hand phone back to samsung.thanks to anyone taking time to read this..
[Samsung Galaxy S10 Guides, News, & Discussion] robbo1947:
Have you tried Frija?

https://xdaforums.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584/amp/
[Samsung Galaxy S10 Guides, News, & Discussion] thiefxhunter:
This method, works to make Spay working again ?