yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] zeeshee:
Yes Sir i noted that. Thanks

Just one last question before i click on start, my current Indian ROM is 10.3.3

International ROM file on OP is 10.0.8 so i will be actually downgrading. Will that be fine? I read somewhere oneplus dont allow downgrade anymore so just wanted to make sure. Thanks
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
The downgrade restriction only applies to zip flashing via local update. Yes that will be fine. You can thank OnePlus for having a specific version number for India and making things confusing by the way.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] zeeshee:
oh thx.. In that case wont it be better for me to just flash the international ROM via fastboot method instead of using msm tool as my device is not bricked.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Both method work, you can use MSM tool even if your device is not bricked
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] zeeshee:
I used MSM tool and worked perfectly without any issues. Followed instructions exactly as in OP. Thanks.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] ArchaosAngel:
Rollback

Hi i am currently on 10.0.9 and want to rollback to 10.0.8.

just want to check when i go into EDL the phone shows connected on MSM tool for a few seconds before it starts charging the phone.

So do i press start when it shows connected before it starts charging the phone, will anything happen if it suddenly starts charging when i press start on MSM.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] jameslfc5:
I have just used this tool to fix a bricked phone and it worked perfectly thanks!

**issue with phone**

When going through the intial set up, the phone randomly freezes and reboots, any idea what this could be? it hardware?
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
It could be an OxygenOS bug, could you retry without a SIM inserted? A similar issue happened to someone with a 7T on /r/oneplus discord and it was fixed that way.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] jameslfc5:
Thanks, I have only ever been using it without a SIM card as I was trying to get it all set up first. I will give it a go with a sim :)

Tried it and have tried to fastboot install 10.0.9 and I can hardly get passed the set-up screen.

I have tried the MSM stock, fastboot stock etc and nothing at all works, going to need to return the phone. But out of interest, is this hardware related?
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
If this persists across different OxygenOS releases it might be, yes.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] jameslfc5:
Thanks, your MSM tool and mirror server was a great tool anyway and it's helped me get back to locked bootloader stock so I can get the device returned to amazon.

:good:
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] forever_lol:
I'm new to oneplus and I've just managed to revert back to stock after short adventure with RR (great rom btw) using your guide.

It went smoother and easier than I thought. I was afraid it would keep rebooting/disconneting when I released volume up & volume down right after I presses "start" but nothing like this happened.

So i managed to revert back to 10.0.8 but I couldn't update to 10.0.9 in a regular way via system ota update. Is this normal?

I managed to fix it manually thanks be to Oxygen updater and local update but it's bit weird that there was no 10.0.9 ota available to downlaad via system update.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
I think something weird is going on with OnePlus OTA system at the moment, since 10.0.9 is available on support website since approximately a week and since I have a problem related to it as well on a spare device I have (OP3T on 9.0.5 suddenly not seeing anymore 9.0.6 while it has been released in November 2019). Logcat said something about a JSON error.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Added 10.0.9 HD01BA MSM tool.

If anyone is willing to get HD01AA one, please get in touch with me as I need your help for that.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] vinu4u4ever:
Yes, I need the 10.0.9 HD01BA MSM tool. Let me know how can I help you out.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Sent you a DM (I'm assuming you made a typo and meant to say AA)
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] jujomar:
Hi, I'm also interested in the AA one. What I should do?
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] cbomb1337:
Thank you for the hd 01 ba 10.0.9 Europe. I used it a few times with msm tool on my 7t pro mclaren hd1913. I found a termux command to backup persist.img. How do I backup reserve.img. Is that one needed to be backed up to As a safety
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Aleplus:
I encountered an Unsupported Target H2 error help please
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Sent you a DM

It shouldn't be needed to back it up

Ensure you set a target as explained in OP
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Desensitized:
Thanks! This worked perfectly on my McLaren edition.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] cbomb1337:
will you be adding 10.0.10 hd01ba?
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] tdrahnier_13:
Hi, thank you so much for your work

I have a couple of questions

1) do you plan to update the utility to version 10.0.10? HD01AA?

2)Can I update your utility and firmware version myself?
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
I got asked similar questions few days ago in OP6 forum, please refer to https://xdaforums.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109/post83256243
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] JoeF2:
My 7T Pro McLaren is stuck in Qualcomm Crashdump mode, shows up in Device Manager as 'HS-USB Diagnostics 900E'. Even though I changed the driver to 9008, the tool does not recognize it.

Any advice, before I send it in for repair?

Nevermind: I found a way explained here: https://xdaforums.com/redmi-note-3/how-to/method-to-unstuck-edl-mode-qualcomm-hs-t3633442

Pressing Volume up, down, and power simultaneously got me unbricked.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Added 10.0.11 HD01AA and HD01BA MSM tools
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Montero7o:
Hello

Thank you for this provision

I am looking for version 10.0.10 HD01BA MSM tools, is it available?

cordially
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
No, I would have posted it otherwise.

Also you don't need latest version to unbrick your device, I just post newer versions for the sake of convenience.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] DrBazinga:
Hi,

My phone has bootloader unlocked and is rooted. I'd like to give it a fresh start when OOS 11 is released, including relocking bootloader.

I have a HD1913 (European version), will it be ok if I flash the global rom instead of the European one in order to get rid of audio restrictions ?

Thanks
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
You should be able to crossflash, but I don't believe you will be able to get rid of audio restrictions. Also as a sidenote OOS 11 should not be released before December ish for that device.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] DrBazinga:
Sorry I meant in Europe we don't have the full equalizer and there's also a volume limit as a result of some European regulations.

Flashing global rom removes these restrictions according to forum members.

Thanks for providing such a tool anyway, I don't mind waiting for OOS 11.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] leginhee:
Hey,

When I'm trying to boot into edl mode, my phone boots normally. I am in edl mode for like 10 seconds. After that it just boots normally. The computer detected the device during the 10 seconds. Am I doing something wrong?

My bootloader is not unlocked, idk if it have to be unlocked.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Try to be faster at clicking Start button or launch the tool and click on start before plugging your device.

Also you don't need to unlock your bootloader to use this tool.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] manuelean:
Hi, I have an HD1910 with a HD01AA 10.0.12 version, and yesterday I have in my screen Qualcomm CrashDump Mode, I allready tried to use MSM tool (10.0.8 and 10.0.11) to restore my phone. but when the MSM process conclude nothing happens and I still have the same Qualcomm CrashDump Mode.

Any sugestions that what I'm doing wrong.

Thanks in advance for your help :)
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Added OOS 10.0.12 HD01AA MSM tool

[MENTION=11239985]manuelean[/MENTION] try with .12 version, otherwise I don't know and you may need an RMA.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Ignore, above post has been posted twice.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] manuelean:
Thanks man!!! but I tried with the 10.0.12 version and still not working... I should give up? I can't do a RMA because I bougth this phone in Aliexpress.

Any other suggestion? thanks in advance.

Manu
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Besides contacting OP support for an out of warranty repair, I don't know. Note they might charge you a whole motherboard.
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Anakha56:
So I rooted my HD1910 McLaren Edition, flashed ElementalX kernel and ... realized that I honestly don't need root in my life. Going by the first post and subsequent posts below I can use this tool to get back to stock and lock the bootloader? I will still get all the McLaren themes and boot logos?

To confirm you just follow the steps in post one and should be done? Is EDL mode the same as fastboot mode by any chance? Was watching a YouTube video on this process and he did the exact same key combination and that went into fastboot mode.

*edit*

I have downloaded hotdog_14_O.20_201011, I hope that is the correct one?
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Anakha56:
So I thought about throwing caution to the wind to flash it and get back to stock. Sadly I am unable to get fastboot mode to install the Qualcomm EDL driver. Instead it want to install the Google ADB driver with phone being picked up as "Other devices --> Android." I did the key combination, volume up + down and power at the same time so I am not sure what I should be doing? Switch off USB debugging maybe?

*edit*

Found what was causing my issue. Power off phone, while it is off hold down the vol up + down buttons, connect cable. That gets the EDL mode and the Qualcomm drivers installed no problem. Enum says connected so I am assuming I can proceed but will work up the courage a little later on to do that rofl
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Anakha56:
Tool worked perfectly! Thank you :).
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Some_Random_Username:
Added OOS 10.0.13 HD01AA/HD01BA MSMs
[OnePlus 7T Pro (Regular & McLaren) Guides, News...] Bidull:
Hi!

Thanks for the tool. I'am stuck in fastboot mode. I have tried the All-in-one tool to get back on stock on my oneplus 7T Pro.

I've tried the msmtool but everytime (Eu,O2 and India) I get "Device not match image".

Can someone help me ?
[Shift General] Settembrini:
Hi,

okay, so I am eagerly waiting for the ROM with all the features we all like to have.

I don’t know, but it might still take some time. There is one “small”, that is, there are two “small” things I really would like to have changed: the black bars on the WM screen. Does anyone know how to get rid of them? That would be really, really nice.

Is there anyone working for the project who can at least tell, if they have been able to conjure away the damned stripes?

Thanks!

S.
[Nook Touch General] Renate:
Well, I finally got it together and figured out how to use the ROM bootloader on the iMX6 Nooks (Glow2, 3, 4).

You can get into u-boot even with a trashed disk.

Of course, that may not be the end of your problems.

You may have to repair stuff.

Having a UART console wired up will certainly make things clearer/easier.

So, if you have a bricked Glow (that still bongs when you plug it into a computer),

I have a program for downloading the u-boot.

I can try to make a version of u-boot that goes straight into fastboot.

So, does anybody have a bricked Glow?

You can check in Device Manager (devmgmt.msc) if you can find:

Human Interface Device
USB Input Device
USB\VID_15A2&PID_0063
[Nook Touch General] Renate:
Well, I've been playing around with all this.

I got a bit too arrogant playing around and swapping u-boots.

If you have a SBL (secondary bootloader, possibly u-boot) that looks good enough to the ROM bootloader

but doesn't actually work, you can sort of lock yourself out.

I had to disable (by grounding a test point) the eMMC to allow the ROM bootloader to run.

I've got to wiggle out and see if the boot options actually have their own test points.

I'm trying to get some more UARTs configured for GPS sensors.

The iMX6 bootloader is a known thing, but all the software out there seems half baked.

I tried one that was 7 Megs in size, but it didn't actually work.

My version weighs in at 68k, i.e. 1/100th the size.
[Nook Touch General] Renate:
So, I've got a cleaned up version (available in the signature).

C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle

C:\>imxboot ub3
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Device disconnected correctly
[Nook Touch General] companion79:
Hi.

I have bricked Glow 3.

I tried to restore the bootloader according to your instructions and I have a problem

C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Could not write device
[Nook Touch General] Renate:
Hmm, strange.

Hold the reset button for 10 seconds. It should get a disconnect "bong".

Hold the reset button for 3 seconds. It should get a connect "bong".

Try imxboot by itself again.

It's strange because I have a separate error if the connection got disconnected.

I've been using imxboot alot myself on a Glow3 and never a problem.
[Nook Touch General] companion79:
Reset button on the book? Where is this button? Perhaps I do not understand, perhaps you need to connect through the UART module? I was connecting through the command line.
[Nook Touch General] Renate:
Err, I meant the power button.
[Nook Touch General] companion79:
I performed all the actions, but the result is the same.

Could not write device
[Nook Touch General] companion79:
So write about an attempt to restore bricked nook Glow3, now position here is such

C:\>imxboot
Found iMX6SL, VID=15a2, PID=0063
Security: Unlocked
Status: Idle

C:\>imxboot ub3fb
Load addr 87800400, DCD offset 002c, DCD size 0220
Found iMX6SL, VID=15a2, PID=0063
67 DCD ops processed
Write, addr 87800400, size 00039270
**********************************************************************************************************
Jumping to 87800400
Could not read device

Now in Device Manager I find

Android ADB Interface:

USB\VID_18D1&PID_0D02&REV_0311

USB\VID_18D1&PID_0D02

I trying to run

C:\>adb reboot fastboot
error: no devices found

please help me what should I do next
[Nook Touch General] Renate:
Oops, sorry, my stupid. Fastboot uses its own bogus VID/PID.

You booted ub3fb, therefore you should be looking for fastboot, not ADB.

Windows handling of WinUSB drivers makes this all a bit obtuse.

C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
12345678 fastboot
C:\>fastboot boot nnglow3.img
C:\>adb shell
# ls -l
[Nook Touch General] companion79:
That's what I see now

C:\>imxboot ub3fb
...
Jumped to ...
...
C:\>fastboot devices
???????????? fastboot
C:\>fastboot boot nnglow3.img
Sending
Booting
Finished.
C:\>adb shell
Error: no devices/emulators found

After that, the device in the Device Manager disappears and is not detected again, reboot again returns the device to its original state.
[Nook Touch General] Renate:
Ok, but if at this point you pull the USB connection does Windows make a "bong" that something has been disconnected?

If so, that means that you've got something there and that the problem could be drivers for the ADB.

If not, that could mean your hwcfg is badly broken.
[Nook Touch General] Renate:
Try with the just-now uploaded Neo Noogie images that should be more resilient to bad NTX hwcfg.

https://xdaforums.com/nook-touch/de...store-glow2-glow3-t3784575/page3#post81256205
[Nook Touch General] egor_omsk:
Hi! In response to "imxboot ub3fb" the request writes "Could open file ub3fb". Where can I get this file? Please help!!!
[Nook Touch General] Renate:
Mmm, it's attached.

(It's the stock u-boot for the Glow3 with automatic jump to fastboot.)
[Nook Touch General] egor_omsk:
Thank you very much

---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------

imxboot

Found iMX6SL, VID=15a2, PID=0063

Security: Unlocked

Status: Frozen
[Nook Touch General] Renate:
Yeah, that's an undocumented status that I get from the bootloader when it tried to load once, failed and didn't do a complete reset.

Do a long (10 sec) power off press, then a long (3 sec) power on press.
[Nook Touch General] egor_omsk:
do not work
[Nook Touch General] Renate:
Umm, you could be more specific.

You can't power it down, up, it acts the same?

Is it making USB up/down "bongs" on your desktop?

If nothing else, open the case, disconnect the battery for a few seconds.
[Nook Touch General] egor_omsk:
Unfortunately it didn't work out
[Nook Touch General] Renate:
Sorry, I can't help you unless you give me actual information of what you did and what happened.
[Nook Touch General] companion79:
When I disable Nook Windows does not Bong, tried a new version of the file nnglow3.img, nothing has changed. Tried running WINDOWS 7 and on WINDOWS 10 no difference in result.
[Nook Touch General] Renate:
Ok, so if I understand you:

The imxboot ub3fb, fastboot boot nnglow3.img works fine, prints "Finished. Total time"

and then you get no USB, no screeen anything?

If you had a UART console connected we would have eyes to see what's going on.

Ok, just to be sure, you are talking about the black, 6" Glow3?

We can try flashing the NTX hwcfg.

C:\>imxboot ub3fb
C:\>fastboot flash hwcfg hwcfg3.img

Note that in the last command "hwcfg" is the flash area, the thing after that is the local file name

After that, try the normal imxboot ub3fb, fastboot boot nnglow3 test.
[Nook Touch General] companion79:
You've got it all right.

Yes, that's right, I have black 6" Glow3.

I have a UART console connected to the lower connector near the USB connector, right?
[Nook Touch General] Renate:
Is that a question? If you have one, let's see the output.

If not, go ahead and flash the hwcfg and tell me about it.
[Nook Touch General] GNUS inc:
Hello, I've got a completely bricked GL3.

What I did - embedded TWRP, installed a custom FW image, and then tried to get back to the stock image. I installed it via TWRP and got a dead Nook.

When I try to turn it on - it shows a standard booting screen, turns on the light, and that's it.

Never managed to get into fastboot or recovery (honestly, I never could do it by pressing power+lower right/home buttons, always had to use "adb reboot recovery").

Now all I can see when I attach it to my PC is this - https://ibb.co/9hkDH4x (it's a shot from my device manager)

No new USB input devices.

The bootloader does not see it too.

C:\ADB>imxboot
Could not find device

It'd be great to hear some ideas :)

Upd:

Not that bricked.

Finally booted into fastboot and recovered.
[Nook Touch General] Renate:
Yeah, the thing is, if you totally trash the flash, then you will get the iMX bootloader.

If you sort of trash the flash it will try to boot something damaged, lock up and not let you do anything.

Playing around I have mostly trashed the flash one time.

I had to electronically deactivate the flash to allow the iMX bootloader to work.
[Nook Touch General] cave_iar:
I do have :)

Let me describe the status first (havent seen similar cases at the forum yet). Now is have factory reset Nook Glowlight 3, but after some unwise rooting attempts. It starts with standard welcome screen, leads to launguage select and then freezes at wi-fi switch-on screen. Also performance and response to actions (buttons press and taps) is veeery slow.

So, when i connect the device to PC after normal boot (long-press power button), it appears to detect it in a weird way - in devmgmt is see it as Linux File-CD Gadget USB device (0 bytes free space), and in Win10 user menu "Other devices" it sees BNRV520 (although i dont see it in devmgmt).

If I boot it holding "nook" and power buttons simultaneously, i see it as i.mx6sl NTX Smart Device and cant see it anywhere in devmgmt.

I tried C:\>imxboot in both case - "could not find device"

Could you please help with the issue?

I would like to restore the device to normal state and root it again more carefully (had much better rooting case with another Glowlight 3).

PS: Thanks for extensive help accross the forum!
[Nook Touch General] Renate:
I've been working all morning on a major rewrite of this tool.

It's now called "imxlink.exe" and can be downloaded in the signature.

It should be a bit better on identifying things and have only a few more bugs. :p

Yeah, the names that you see are not really helpful.

You want to know what interfaces you have, not some silly name like " i.mx6sl NTX Smart Device".

That name could be the fastboot through the u-boot.

Give it a try and tell me what you see.

You can try fastbooting nnglow3.img

You probably have to fix something broken somewhere on your Nook.
[Nook Touch General] cave_iar:
Thanks! used the new tool to indicate fastboot. I was able to fastboot Neo Noogie for Glowlight 3, and it gets me to adb mode ( see "5084010046003168 device" after adb devices)

Windows locates a new USB-disk G, which it offers to format (cancelling it as per instructions), however, im not able to access it through windows file explorer. I also tried to install Relaunch through adb, but cmd returned to me that "/sbin/sh: pm: not found"

Now - if i want to completely restore memory to factory level (to avoid finding what actually was broken) - what should i do?
[Nook Touch General] Renate:
Well, G: will be the entire EMMC flash in the Glow.

If you want to do a whole backup or restore, that will do all the partitions.

I would try (manually) installing a new 5.0 update and see how that works.

For the Glow3 http://su.barnesandnoble.com/nook/piper/5.0/jay/0.117/update.zip

# mount /system
# mount /data
# mkdir /cache [color="red"]Oops, I should fix this in Neo Noogie[/color]
# mount /cache

C:\>adb push update.zip /data/media/0

# cd /data/media/0
# unzip update.zip META-INF/com/google/android/update-binary
# chmod 755 META-INF/com/google/android/update-binary
# META-INF/com/google/android/update-binary 2 1 update.zip