Database Users

Nook rootable? Seems like it!

So I was poking around the settings, and I found how to enable developer mode on the Nook.
You just tap on the Build number (Not the serial number) in Settings > About Tablet
then go back one menu and it's there "Developer options".
I was able to turn on "OEM unlocking" -- does this mean the boot loader is unlocked?
Which means, you could run the "root anything" boot.img ?

Ok, the Nook shows up in ADB!
fastboot devices worked as well.
However, fastboot oem unlock
and
fastboot flashing unlock
both do nothing

fastboot oem unlock works but you have to go into developer options in settings and enable OEM Unlocking (3rd option on the screen). It's an extra little safety step.
dokihara said:
Ok, the Nook shows up in ADB!
fastboot devices worked as well.
However, fastboot oem unlock
and
fastboot flashing unlock
both do nothing
Click to expand...
Click to collapse

jsonger said:
fastboot oem unlock works but you have to go into developer options in settings and enable OEM Unlocking (3rd option on the screen). It's an extra little safety step.
Click to expand...
Click to collapse
I did enable that. How long do you have to wait? I waited about 5 minutes. at the "..." prompt before cancelling.
this is the 2016 Nook right? the brand new one..

dokihara said:
I did enable that. How long do you have to wait? I waited about 5 minutes. at the "..." prompt before cancelling.
this is the 2016 Nook right? the brand new one..
Click to expand...
Click to collapse
Once you're in fastboot on the device (adb reboot bootloader after enabling USB debugging on the tablet) and you get the "FASTBOOT mode ..." prompt. Then do "fastboot oem unlock" and it should prompt you on the screen with the usual warranty voiding, going to wipe the device, etc. Press Volume Up to confirm and that should be it. It'll spin it's wheels for a bit while it's doing the wipe and all.
---------- Post added at 04:45 PM ---------- Previous post was at 04:31 PM ----------
jsonger said:
Once you're in fastboot on the device (adb reboot bootloader after enabling USB debugging on the tablet) and you get the "FASTBOOT mode ..." prompt. Then do "fastboot oem unlock" and it should prompt you on the screen with the usual warranty voiding, going to wipe the device, etc. Press Volume Up to confirm and that should be it. It'll spin it's wheels for a bit while it's doing the wipe and all.
Click to expand...
Click to collapse
I went back and rechecked everything and I hadn't unlocked the Nook yet. (I have a couple of different tablets I'm messing with right now.) The procedure is right but it looks like there is another firmware glitch (along with the lack of brightness control) where it isn't reading the volume up or down buttons in fastboot.
Wow the software on this thing is sloppy.

I went back and rechecked everything and I hadn't unlocked the Nook yet. (I have a couple of different tablets I'm messing with right now.) The procedure is right but it looks like there is another firmware glitch (along with the lack of brightness control) where it isn't reading the volume up or down buttons in fastboot.
Wow the software on this thing is sloppy.
Click to expand...
Click to collapse
Yeah, running that command doesn't do anything.

Hi, I'm new to Android development and stuff.
It seems that there are conflicting reports. Is the bootloader for the Nook Tablet 7" unlockable?
I picked up this Nook on this past Black Friday. I'm using a SD card formatted as internal, but I'm running out of space on the actual internal storage. I want to root this thing so I can remove the Nook bloatware and move unmovable apps to SD card.
I tried towelroot and Kingo root, but after it failed I found out Marshmallow isn't supported...
I saw the how to geek's article here - howtogeek(dot com)/115297/how-to-root-your-android-why-you-might-want-to
It explains how to root by unlocking the bootloader then flashing superSU using TWRP. I'm wondering if it will work. Can I actually unlock the bootloader without an OEM code? But I looked at the TWRP website, and the Nook 7 isn't supported. I know this is a really new device; how long does it usually take for TWRP to add a device?
Sooooo... is there another way to root?
I'm also waiting for CyanogenMod to release a build. If I understand correctly, my device must be rooted before flashing any custom ROM, right? So does that mean that every device for which a custom ROM has been written is rootable? Anyway, how long will it take for a build to be written? Should I stop looking because it will be a long time?
Thanks!

I am also able to run 'fastboot oem unlock', but then I run into the issue where it doesn't detect the input of either volume button, and my only option is to power off the device. I fear we won't see a fix for this. It may even be deliberate as a way for them to lock down the device. Has anyone so far had luck actually getting the oem unlock to work and wipe the device?

Did you enable OEM unlocking from developer options as jsonger suggested?
soundtoxin said:
I am also able to run 'fastboot oem unlock', but then I run into the issue where it doesn't detect the input of either volume button, and my only option is to power off the device. I fear we won't see a fix for this. It may even be deliberate as a way for them to lock down the device. Has anyone so far had luck actually getting the oem unlock to work and wipe the device?
Click to expand...
Click to collapse

Yes, of course. This is not my first rodeo. Have you gotten this working? It sounds like everyone is stuck at the same point.

soundtoxin said:
Yes, of course. This is not my first rodeo. Have you gotten this working? It sounds like everyone is stuck at the same point.
Click to expand...
Click to collapse
Sigh. We must be stuck, then.
No, I haven't tried anything yet. I was trying to install the ADB but then I learned that SDK Manager needs Java to run, apparently? So I started downloading the JDK but my internet is slow so I canceled it. I'll try again later.
I've been trying a number of different root tools, but no luck yet. IF I successfully root my Nook (kind of unlikely) and TWRP adds it as a supported device (even more unlikely), would it be possible to flash TWRP recovery using the app from the Play Store?

Has anyone tried unlocking the bootloader after this last update?

I believe I have discovered the complete firmware for the T8370, the Chinese tablet that Nook rebranded. As emdoor (the company behind the T8370 tablet) still handles the Nook's software, I'm guessing the firmware will be very similar. At the very least the firmware should give me an idea of why the bootloader is not unlocking and/or what the bootloader does in the unlocking process. Sadly, the firmware is stored on unreliable Chinese servers, so it may be a day or two before I can finish the download. While we did receive Chinese malware with the Nook, the rebranding of a Chinese tablet may ultimately pay off... I doubt B&N would have readily released the complete firmwares for their devices.

I tried unlocking after doing the upgrade and it still has the same problem of not responding to Volume up/down in fastboot.

kingramon0 said:
I tried unlocking after doing the upgrade and it still has the same problem of not responding to Volume up/down in fastboot.
Click to expand...
Click to collapse
That is unfortunate. :/ Let us know if you make any progress.

I haven't been serious in my efforts to unlock the bootloader. But the one time I tried, I sent an adb reboot bootloader, and the nook went to fastboot mode. But then adb lost the connection, and when I sent fastboot oem unlock, adb said waiting for device. So I hadn't even gotten to the problem of the volume button.
This was before the update, btw.

Is anyone else getting tired of micromanaging storage space? I have a huge 32GB SD card, but preloaded apps are eating up my space. And they can't be moved to SD card.
*Sigh*

smileygon10 said:
Is anyone else getting tired of micromanaging storage space? I have a huge 32GB SD card, but preloaded apps are eating up my space. And they can't be moved to SD card.
*Sigh*
Click to expand...
Click to collapse
Yeah.... it's getting to be a real pain in the arse. That and there's no way to force it to install two micro SD card if you've got the card formatted as unified storage you would think that Google Play would realize that and automatically move everything over. What's worse is that when you update apps move them back to internal storage and then you you have to move them again.
I wish someone would go ahead and figure out how to root this thing so we can get rid of things like YouTube kids which no one with this tablet is going to use.

smileygon10 said:
Is anyone else getting tired of micromanaging storage space? I have a huge 32GB SD card, but preloaded apps are eating up my space. And they can't be moved to SD card.
*Sigh*
Click to expand...
Click to collapse
Ditto. Anybody have luck with this yet? B&N is probably about to put these on sale for $39.99 again, and I'd like to pick up a couple more if I can beat the "no space" issue by adding a fully integrated microSD.

Was thinking about grabbing one of these once I got the money. Has anybody tried making an MTK Scatter file to load a custom TWRP in SPFT?

Samsung S7 Edge is locked - Unlock or Data Extract help? Unique Situation...

Ok guys, new here and I've done a bit of reading on this already. From what I gather, the S7 Edge is difficult if not impossible to unlock without a factory reset. Here's the issue.
This phone belongs to my friend's husband who was severely injured in an accident at work. He's in a coma and probably won't survive. He was severely burned over 90% of his body with chemicals and he has no fingerprints to unlock the fingerprint scanner. In addition, his wife doesn't know his password, so I figured I'd see if I could do anything for her. I tried the Dr. Fone program, but it's apparently incompatible with the S7 Edge. He keeps getting texts and messages and we can't check them. The phone is also set for a daily alarm at 1:30 AM, and apparently you can't power it down without the lock code either. Ideally, I'd like to either gain access for her or at least extract what data we can from the thing before factory resetting it. It would also be nice to power it down so that it doesn't keep putting out an alarm every night in the middle of the night. All his contacts with his family are inconveniently stored in the phone as well. It's kind of a worst case scenario.
Any assistance or recommendations for a course of action for this situation would be fantastic. I don't have any other information on the device itself other than that it's running on Freedom Mobile's network in Ontario, Canada. They've said they can factory reset it for her, but we were trying to avoid that and get any contacts or messages from his phone if possible.
Thanks in advance for any help! I know it's a long shot!
Edit: I managed to power down the phone with the Power Button/Volume Down trick after about 9 tries, so at least the alarm won't go off. Other than that, no luck.

Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.

Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
UnNaMeD__ said:
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Click to expand...
Click to collapse

maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Use odin 3.13 the latest
Then download twrp recovery 3.2.2.0 tar file for hero2lte the latest.
Boot your phone into odin mode by restarting your phone while holding power home button and vol down. When your reach the confirmation screen press OK.
Open odin and put the tar file in the ap slot and click the ap box and hit start to begin flashing.
Now restart ur phone by holding power home and vol down then immediately hold power home vol up to reach custom recovery.
Edit I just tested this myself
Flash the zip file from this thread no need to go looking for files in system.
https://forum.xda-developers.com/showthread.php?t=2780696
Should remove password pin or pattern.
To check if it's network locked just look at the back of your phone if it says 935u or Verizon wireless or 935W8 then the phone is unlocked for different networks.

maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.

I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
UnNaMeD__ said:
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
Click to expand...
Click to collapse

maxlords said:
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
Click to expand...
Click to collapse
Hey alright no problem.
Download TWRP for G935W8 from official TWRP website:
https://teamw.in/samsung/samsunggalaxys7edge.html
You can follow some instructions from this thread regarding flashing:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Flashing TWRP might cause your phone to not boot. You will need to download dm-verity disabler from the thread above.
So download TWRP, Aroma file manager, dm-verity bypass, and zip file to disable pass that the other user posted: https://forum.xda-developers.com/showthread.php?t=2780696
Download all these files and put aroma file manager, dm-verity bypass and that password zip file bypass on your SD.
Make sure auto reboot is disabled in odin, follow instruction in thread about how to install twrp. If the auto reboot is disabled, phone will just remain at the same screen, so after the flashing is done from odin. You need to force reboot on your phone (volume down + power button for few seconds), just when the screen goes off, you need to immediately press recovery button combination (vol up + home + power). Here once you enter TWRP recovery see if you can enable MTP and trasnfer data to PC, if not, goto install zip and try password bypass zip file. If it works file then ok and proceed to install dm-verity bypass file and reboot your phone. If that zip doesn't works. You need to go to same install zip file option and now install aroma file manager. From there delete the password files that I told you about earlier, flash dm-verity and reboot again.
Thats it, if get confused about a step, tell me.

Well, I attempted to install TWRP through the latest version of Odin, but it didn't work. The error message I got in Recovery/Download mode was:
"Custom Binary (RECOVERY) Blocked By FRP Lock."
I looked that up online and apparently to install TWRP, I need to remove the FRP lock. I found a program called RealTerm which can supposedly bypass the FRP lock, but it doesn't seem to be connecting to the locked phone and it's not exactly user friendly.
Am I missing something here? Or is there no way to bypass the FRP lock on the unit?

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.

For anyone having issues changing from CN to NA ROM on the 5S

There's a little story i needed to rant about before i wrote this guide so read if you'd like if not tldr; will be down below
NO ROOT OR BOOTLOADER OR ANY FORM OF CODING NEEDED FOR THIS FIX, THIS METHOD WE WILL BE USING OTG AND THE RENAMED STOCK NA 8.07 ROM FOR THE 5S GOING FROM CN 6.23
Requirements​ - NA 8.07 rom from the official redmagic website
- A Computer/laptop
- USB stick (mine was usb2.0)
- OTG adapter (if you have any old samsung phone boxes look in them there's usually one)
Hey guys! First of all im terrible with technology, i havent touched a computer in over 15 years before 4 days ago.. So i bought this phone 4 days ago as i needed a decent phone with a snapdragon soc (samsung uses trash exynos in Australia). The shop i bought it from didnt tell me it was the cn version and thought he would just have NA version as thats what it says australians will recieve on the official site.
So i did some research and found out we can easily change roms using the local update thingy so i dl'ed the 8.07 NA rom and it would load to 25% then freeze, reset and nothing would happen.
So i tried the OTG method, same thing again, 25% then crash and reset. So at this point im starting to get pissed, i downloaded the latest 5G NA rom and tried to otg method that rom to the phone. It loaded to 80%, crashed and hard bricked my phone to the point of where it was corrupt, couldnt get into recovery and couldnt factory wipe,
I was however, happy to see the boot logo had changed to english though so i didnt give up, 3 days, 3 f##ing days i was trying to research flash guides, recovery guides, root guides, downloaded about 100 usb drivers because i wasnt updating to the right drivers at the right times when plugging in and unplugging my phone, i tried unbrick tools and when trying to fastboot it was saying the password was incorrect (fastboot oem nubia_unlock NUBIA_NX659J is what worked for me to unlock fastboot. all the guides i read said the fastboot cmd was
fastboot oem nubia_unlock NUBIA NX659J) nothing worked. Luckily i had gone into dev options after reading a guide and unlocked oem unlocking and usb debugging before the phone bricked as this is what helped unbrick my phone. I had to individually flash each .img file from the CN rom back to the phone.
I didnt know how to code or do cmd thingys before i bought this phone. Now i could f## join anonymous im that good LOL but yeah i managed to unbrick, wipe, and flash the NA 8.07 rom to my CN 5S using OTG. You wanna know what i did to make it work? I can tell you right now it didnt need a f##ing 4 day crash course on hacking and coding.
TLDR; bought CN rom 5S brand new from shotty phone shop, i couldnt get the NA rom to load past 25% on the local update so i went through hell and back.
I highly highly recommend unlocking developer options in your phone, turn on oem unlocking and usb debugging before doing any updates or experiments with this phone, just incase anything goes wrong with any updates
Solution:
- Always back up your phone before anything you will need to do a factory wipe after doing this
- Change the name of the NA 8.07
NX659J-update.zip folder you downloaded to "update"
- Copy that update.zip folder to a freshly formatted fat32 USB stick, do not unzip and copy. It has to be the zipped folder then safely eject the usb from the PC
- Hold the Volume up button and the power button until the screen turns on, once the screen turns on release the power button and you should reach a blue screen with 2 language selection buttons, use the volume keys to navigate and the power button to interact.
- After choosing language you will see "choose a package" and some other buttons, this is recovery mode.
- select "choose a package" and plug in your OTG adaptor and USB stick
- Select OTG method
- Find your "update.zip" folder it should be right there
- Start update and keep an eye on the phone incase any errors pop up it should take about 5 minutes to update and it will stop at certain points (stopped at 80% for a good 30 seconds for me) for bigger files so dont stress if the numbers aren't moving. I was tapping the screen so fast with anxiety at 80% hahah
- After the update go back to recovery and wipe data/cache partition and reboot
- Enjoy your goog apps

unlocking dev options and using the oem unlock option is not necessary for our device.
Unlocking the bootloader also corrupts the fingerprint sensor data, making fingerprint break.
when you need to flash a rom and the normal method does not work, flashing though recovery normally works.
as you have a CN variant of the phone. note you cannot use the NFC function. as there is no NFC chip on CN variant devices.

Patrick Morgan said:
unlocking dev options and using the oem unlock option is not necessary for our device.
Unlocking the bootloader also corrupts the fingerprint sensor data, making fingerprint break.
when you need to flash a rom and the normal method does not work, flashing though recovery normally works.
as you have a CN variant of the phone. note you cannot use the NFC function. as there is no NFC chip on CN variant devices.
Click to expand...
Click to collapse
Oh i didn't know that! I was unable to flash the na rom through recovery until i renamed the zip folder lol but i wish i knew i had to rename it before i bricked my phone.
Im not sure how to relock my bootloader and fix the fingerprint sensor, i read somewhere theres a number to dial #xxx# for the calibration but i cant find it

Brae2 said:
Oh i didn't know that! I was unable to flash the na rom through recovery until i renamed the zip folder lol but i wish i knew i had to rename it before i bricked my phone.
Im not sure how to relock my bootloader and fix the fingerprint sensor, i read somewhere theres a number to dial #xxx# for the calibration but i cant find it
Click to expand...
Click to collapse
fastboot flashing lock or fastboot oem lock I think are the commands to relock your bootloader. which after a wipe should restore your fingerprint.
you can then follow my TWRP and ROOT guide on XDA here for the 5S and not have flashing problems again.

Patrick Morgan said:
fastboot flashing lock or fastboot oem lock I think are the commands to relock your bootloader. which after a wipe should restore your fingerprint.
you can then follow my TWRP and ROOT guide on XDA here for the 5S and not have flashing problems again.
Click to expand...
Click to collapse
Thanks for the help! Im wondering if i should just return this phone and just buy the na version from the website, i find it a little annoying that the shop didnt mention it was the cn version, i dont know what else im missing apart from NFC aswel so im stressing

Brae2 said:
Thanks for the help! Im wondering if i should just return this phone and just buy the na version from the website, i find it a little annoying that the shop didnt mention it was the cn version, i dont know what else im missing apart from NFC aswel so im stressing
Click to expand...
Click to collapse
all 3 regions had the exact same hardware.
with the exception of the NFC chip on the CN units.
if you can live without NFC the phone should be the same and function correctly with any of the roms once you're able to flash them.
its just that there will be an NFC option in the rom, it just wont activate, since you dont have the actual hardware.
if you were to give the phone back look into buying it from redmagic directly. as Nubia's Warranty only covers direct sales, it does not cover any 3rd party website this includes places like Nubia store on Aliexpress. you won't get official warranty from there.
only the redmagi.gg or nubia homepage which normally directs you to redmagic.gg will support official warranty so this is something to consider.
but also, as you've unlocked the bootloader, flashed things and what not. if the seller knows or finds this out they can refuse a refund as you've modified the system.
good luck either way.

corrupt

Is my Mi 9t bricked?

Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.

yurtal said:
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
Click to expand...
Click to collapse
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly

zgfg said:
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
Click to expand...
Click to collapse
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?

yurtal said:
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
Click to expand...
Click to collapse
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything

zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Oh ok. Yes I'll read up on it. Thanks for your help.

zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Hey, just to follow up. I managed to get it back up and running from someone with EDL support.