Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Same problem. When WiFi is ON.
When I put WiFi OFF - the tablet works fine.
Last firmware doesn't help, reset too. I think there is no solution at this moment, except maybe to flash an old firmware with Android 6.
I'll replace it in store. No idea about Asus control quality of their firmware... but this problem is pretty common.
???
Belnadifia said:
Hi everyone,
I just updated my Asus Zenpad 10 (Z300M) via OTA.
The tablet booted and I saw the Lock screen. But after a couple of second it reboot.
I've tried a factory reset. BU it's the same probleme: It boot up to the "first start" prompt, and after a couple of second reboot.
I tried to install a custom recovery to flash a new rom with SP-Flash Tool (following this post nstalling TWRP and rooting Asus Zenpad 10 (Z300m))
But I got an error when I readBack.
And even if I flash the recovery, I can't access it on the tablet. I got a message "Your device has failed verification and may not work properly" when I try to go to recovery
Can you help me with this ?
Thank you
Click to expand...
Click to collapse
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
coolbeans2016 said:
What I do not understand! Purchased this tablet due to the thread you mention on here for TWRP using the SP Flash Tool 5.132, right? I just went ahead and used the SP Flash Tool version been using and got that individual error right at the end so did NOT try flashing the recovery! He was very talkative B4 getting this tablet but now after speaking of errors, no responses.....? The version SPFL he says is the only one that works, its option.ini file DOES NOT have the READBACK part in it for changing from false to true...... the very next versions of SPFT after do.....
any ideas????
zach
Click to expand...
Click to collapse
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
I'll give you that
diplomatic said:
Bro, are you serious? I don't reply to your messages for a few hours so you call that whole recovery/rooting thread some kind of a scam or conspiracy? (This is not my day job btw.) The error messages you are talking about are a result of you rushing into this thing and not doing your homework, skimming the directions and/or failing to use common sense. Of course SPFT 5.1532 does not have the read-by-partition option. That's why we use a later version for that. Exactly as it says in the OP. And if you were to do your homework, you would find out that the "..failed verification.." and/or "...different operating system.." messages are expected because of verified boot process built into the bootloader.
Click to expand...
Click to collapse
The link on the Z380M is what threw a flag for me because that Asus tab isnt rootable. If this is some combo of slipups between tools & devices that lines up just right to get TWRP on its not described very well in the OP. Using the 5.132 (?) you can not readback with that option.ini file.... so what am I missing? The bootloader unlock app isn't written for this tablet is it? written for the zenphone 2 (3)?
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Just want to mention for anyone else struggling with this issue, what fixed it for me:
I found the reboot would only happen when wifi was turned on, and even more weird, it would only happen when connected to specific wifi networks. After doing a factory reset I was able to set it up again by tethering to the wifi on my phone. I then found that I actually was able to connect to the problematic wifi network but only by setting a static IP! This has completely resolved the issue for me.
Thaniks
diplomatic said:
Wow, I'm not sure if you're trolling at this point or what. If your ASUS ZenPad 10 Z300M tablet is not rootable, then you are the first one to report such a device on XDA. You still keep saying you can't readback with SPFT "5.132". I hate to sound pedantic, but I think it's better if I make my reply in list form.
There is no 5.132. The recommended version is 5.1532.
SP Flash Tool version 5.1532 does not have the "ShowByScatter" feature at all, as I've told you at least twice.
You can read back any part of the flash ROM by specifying the range manually in 5.1532 or other versions.
You can read back by partitions specified in the scatter file by enabling "ShowByScatter" with SPFT 5.1548 or higher only.
You can flash to this device by using SPFT 5.1532 only (and a couple of older versions).
As for the guide not being clear
I did not write that guide. That is @justshaun's post. I only wrote one section of it and made some corrections to other parts.
Yes, you might encounter some stumbling blocks when blindly following the steps without knowing why you are doing them. But this is a good thing, to be honest. Because if you don't understand even a little bit about what you're doing, and are not able to solve those types of problems, then you have not crossed the pretty low bar for safely modifying your device. In that case, I think you're better off not bothering with this whole recovery/root thing. It's for your device's safety.
All of the problems that you're having have probably been discussed in one thread or the other.
As for the bootloader unlocker
I have never used the unlock tool.
It does not work sometimes, maybe even most of the time.
ASUS has removed the link to it from their download page
Take it up with ASUS if you want to make it work.
Click to expand...
Click to collapse
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
coolbeans2016 said:
I have downloaded everything in the OP again and will attempt to get twrp on tablet again. I did notice one item that was causing my problem that you could call a newbie f/u... I'm using a new browser that has adblock builtin & on by default and it was causing the "loop" when trying to download the recommended SP Flash tools. I got the ones from the link downloaded and they have more internal components like the newer SP Flash Tool versions....... My bad.
Will go through the steps again hopefully later today, my apologies man.
zls
Click to expand...
Click to collapse
Ohhh... ok. No problem man. Just please get your facts straight before posting next time. Good luck. BTW, I'm not sure if you saw this post on the TWRP thread from 2 weeks ago. You didn't reply.
diplomatic said:
What is the error that you got when trying to flash it? Can you post a screenshot of the Download tab along with the Help/About dialog box?
Click to expand...
Click to collapse
Related
[K1] "Unsupported menu option selected" error & where to get TimmyDean rooted 13-13?
I just got a brand new K1. Fresh out of the box with 3-3 pre-installed, I downloaded and used TimmyDean's permanent root tool, flashing a rooted 2-2 firmware. I then enabled the backdoor and ran all the OTA updates up to 14-14. This took several hours in all. I then ran the BusyBox and SU Tools install script. Everything was looking okay. I selected the choice to exit the script with reboot. The K1 turned off and came back on with the Lenovo logo, but, at the top of the screen was red writing:
Unsupported menu option selected: 1
Unrecoverable bootloader error (0x00000002).
It stops there and goes no further. No bootup.
Attempting to research the error, it seems this is not an error too many people encounter or know about, so my guess is that my only way of fixing this problem is to flash the whole thing over again from the beginning. (Unless someone here knows something about this problem. That would be tremendously helpful.)
Having already experienced what it took to go from 2-2 to 14-14 the first time with the permanent root package, I'd certainly like to shortcut it however possible. In this thread, http://forum.xda-developers.com/showthread.php?t=1404351 , TimmyDean posted a rooted 13-13 that we can start from. However, the link to the download file for it is Multiupload.com, and Multiupload.com does not seem to be up for me. Does anyone know where else I can go to try and download a copy?
I'd have posted directly in that Development thread, but, since I am an XDA noob, the forum system only allows me to post in this General section.
After experimenting with the "permanent root" package several times now, each time ending up with the "Unsupported menu option selected: 1" error after any OTA update, I have to believe there is an incompatibility between the K1 I have and the bootloader files in the "permanent root" package. I do not know if my K1 is recently manufactured and they are now doing something different with them that causes this incompatibility or what, but I felt I should warn you all that flashing the "permanent root" package could cause your K1 to not take official updates or to otherwise brick it with the "unsupported menu option" error. Perhaps the 13-13 package, which I don't have and can't test, didn't have this problem.
My serial number is CB1245XXXX. Manufacture date is "11/11/27."
I have now given up on getting root on my K1 and would just be happy to get it back to a working condition that can take Lenovo's OTA updates without bricking. I am currently trying these instructions and will update as to whether or not that resolves the problem: rootzwiki.com/topic/13877-guide-ideapad-k1-restore-to-mostly-stock-with-ota-updates/ (The forum software will not allow me to post hot links, so copy and paste that to browser.)
The rootzwiki procedure did not work to correct the problem. After any update, the tablet is bricked with the error. There are a few threads on the Lenovo support forum on this issue now, and there is no solution.
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/K1-not-booting-after-update/td-p/548285
forums.lenovo.com/t5/IdeaPad-Slate-Tablets/Unrecoverable-Boot-Loader-Error/td-p/683633
I believe these old bootloader files will not work and will brick newer K1's, so my warning is:
DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
This might only apply to more recently manufactured K1's, but, since we do not know when this problem begins, it is not possible to know beforehand whether or not you will brick yours.
To be on the safe side, DO NOT ATTEMPT TO ROOT YOUR K1'S. DO NOT CHANGE THE EXISTING BOOTLOADER IN ANY WAY WITH NVFLASH. SOMETHING HAS CHANGED.
Unfortunately, there was no backup option in the rooting packages, so I could not get a copy of the stock bootloader or any other files, if they are indeed of a different and newer variety. If someone has a recently manufactured K1, perhaps you can get those files and share them, because a lot of people are starting to see this problem now.
I have one with sn#1250xxxx, mfg dt 11/11/29. I wasn't even trying to root the thing. I happened during an OTA update. I tried probably all the recovery/rooting option out there. None of them worked. I have the tablet booting at lenovo screen. But I think you are right about the bootloader. If we can get the correct bootloader, we might be able to the the tablet back to life.
fix?
Has anyone come out with the fix for your issue.. I have the same issue . Used TImmy Dean's method.. and anything updating past the 02_02 (loaded from the tool I get the error... Anyone here have access to contact JimmyDean to ask him for help?
I see that he updated the tool to K1_A301_13_13_111209_US and maybe K1_A301_14_14_111209_US but all the links are dead.. anyone have a good place to download the files?
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
those are just OTs.. not image files.. If you don't have a compatable boot loader, you can't load those files.. We don't have a compatable bootloader.. so this is why we need ver 13 of timmy dean..
rezapatel said:
Try out the downloads on the following Lenovo's link -
download.lenovo.com/slates/k1/OTA
Click to expand...
Click to collapse
Can someone who's getting this bootloader error send me a pm. I put together a stock 120109 update that may work around the issue and I need someone to test.
Was this issue ever resolved, I didnt attempt to root mine, only attempted to wipe it clean and got this..
No, no real resolution. What I ended up doing was NVFlashing one of khanning's ROMs, like this one: http://forum.xda-developers.com/showthread.php?t=1560441
I don't know what's going to happen when I have to update again, such as the upcoming Ice Cream Sandwich update promised by Lenovo.
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
OP6TNewb said:
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
Click to expand...
Click to collapse
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Problem SOLVED!!!
justibasa said:
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Click to expand...
Click to collapse
Thanks for your follow up.
Just want to let you now that I fixed it using the Stock Fastboot tool posted here
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I just did exactly as instructed; my phone was already stuck in fastboot so I plugged to my PC and ran the flash-all.bat file. I really didn't think it would work because the phone did not seem to respond or do anything. I went to the toilet, came back and it was reset to factory!!!! Amazing.
Thank you so much @mauronofrio for posting this amazing tool. You saved my bricked phone! I sent you a donation for your assistance. Thanks again.
Just for future reference, as long as you can get this phone into fastboot, you should be fine. For now that's where all the flashing happens until we get a custom recovery.
But I'm glad to hear you fixed it lol
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Pain-N-Panic said:
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Click to expand...
Click to collapse
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
OP6TNewb said:
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
Click to expand...
Click to collapse
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
They probably have gone off to brag to their friends about what happened. Lol
I, too, am curious about what he did. It's been so long since I first began tinkering, but certainly remember some times I goofed.
Sent from my ONEPLUS A6013 using Tapatalk
Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
I forgot to mention one thing which may also be the reason. Initially, before using Adam Conways instructions, I started with the steps on High on Android (Max Lee) for the OP6 but on their download page, I mistakenly downloaded the twrp zip for the 5T and I flashed it. This initially cause the device to brick but I got it back into fastboot and into recovery and thats when I flashed the OTHER twrp file above. After I did this, I could no longer get into recover and was stuck in fastboot only.
So you can see that I made multiple errrors and I am not sure which one lead to what. Thank goodness OnePlus is friendly to rooting so I could save the phone!
OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
Ah, I see. Looks like you flashed a kernel zip instead.
Im not a noob, but have been so out of practice with the latest Android ROMS and flashing and the changes in the partition arrangements. I managed to soft brick my phone as well and this post totally saved the day! Mauronofrio totally deserves a donation and I also gave one.
Thanks XDA! This place has saved me many times and helped me get the most of all my Android devices!
Hey guys. i am also no noob in flashing/rooting my devices.
Don thishundres of times.
Today my OP6T has shown an Magisk update (before it was 21.4 + Magisk Manager) and now it showed the popup to update -> done and error "bad image format" (i think for the kernel). Rebooted and now i am stuck in the same fastboot bootloop.
Tried to boot up TWRP with "fastboot boot tmrp.img" sadly it doesnt boot.
Any hints how i can recover my phone without wiping everything?
maybe @mauronofrio has an idea?
thx a lot
Other users facing the same issue with magisk 22, see here: https://forum.xda-developers.com/t/...oot-roms-for-oneplus-6t.3862516/post-84553217
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
turtleletortue said:
Hey, if you still have this device laying around somewhere, could you try updating from that firmware to see what happens?
Click to expand...
Click to collapse
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
hassanhassan said:
I flashed the extracted aiomobilestuff.com BNTV460-v1.0.0_20180724.zip using spflash tool. However, the tablet now barely runs. The barnes and noble settings and apps crash if I try log in. The startup wizard crashes the first time, and I sometimes get a red border around every time I tap something.
Is there a way to fix this tablet or is it a dud now?
Ive tried factory reset, clear cache, nothing works. Interestingly, if I go to the normal settings app, nothing appears under serial number, etc. So it's no longer being able to read some of the hardware I'm guessing.
Click to expand...
Click to collapse
I've been experimenting with my own since I bricked mine as well, and I was able to bring mine to full functionality. Here are a few things I learned. The scatter file in the firmware on the internet is messed up. They made the scatter file incorrectly, so as a result, whenever you flash the device with it you have to completely flash it. Their firmware has also been tampered with and probably doesn't have a serial number in it. So, I bet you wiped all of your partitions, including ones that potentially had the serial number. I dunno how to fix it, maybe see if you can get a new one from B&N for no extra cost. Unless you have a full sp flash tool backup of the device before you bricked it, I'm unsure of what to do for you. I was able to help myself because I only messed up system.img, which I took a backup of before modifying it, and I used the wwr_mtk + sp flash tool guide to make a proper scatter file so I could flash my system.img using download in sp flash tool. (Also sorry that it's been a few months since I've responded, I just thought up how I could fix my own device last night and successfully did it). Also, here is my scatter file.
hassanhassan said:
I can't update, every time I try to access the barnes and noble settings app it crashes, every time I try to open the B&N app to log in, once I enter my username and password it crashes also.
Click to expand...
Click to collapse
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this. NOTE: This rom is only for the Oreo version of this device, BNTV460, so for anybody with the BNTV450/Marshmallow device, your device likely will get messed up by this.
turtleletortue said:
So here is the only solution I can think of (if you still have this device).
Download the latest boot.img and system.img (available here https://androidfilehost.com/?fid=4349826312261752630 ) and use the scatter file to flash them to the device (download mode and check system and boot and select both of the files). Let me know if you encounter any errors if you try this.
Click to expand...
Click to collapse
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
xKroniK13x said:
I'm getting an error, "S_DL_GET_DRAM_SETTING_FAIL - Obtain DRAM Failed" when trying to flash any firmware files. I've tried a few different versions of SP Flasher and drivers... any input on that? How did you power on your device for flashing? My battery is completely dead and I'm plugging it in after hitting Download of SP Flasher... it recognizes the device and begins flashing, but fails.
Click to expand...
Click to collapse
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
turtleletortue said:
Questions I have for you that may influence how you should handle this:
- Is the tablet you are on the Marshmallow Nook Tablet 7 (BNTV450) or the Oreo Nook Tablet 7" (BNTV460)? Ignore the rest of my questions and my advice if it is the Marshmallow BNTV450 one.
- Did you flash the stock rom that the original author of this thread flashed (the shady one that messed his device up) before trying this?
- Are you able to boot into any kind of OS? If so, let it charge and then go into that OS and finish charging before doing anything
That error sounds like a result of the shady stock firmware, since it has a different scatter file. Flashing that rom makes people lose some specific device identifiers that make it so the original firmware from B&N won't work anymore as I have seen so far.
Here is my advice if you have the Oreo Nook Tablet 7": Charge the BNTV460 as much as you can, and follow this guide to make a backup of the exact firmware on that Nook Tablet 7" https://forum.hovatek.com/thread-21970.html If the readback step gives you that same dram setting error, your device is likely a brick if it cannot boot into any OS, and you should try to exhaust any type of warranty or replacement plan with B&N that you have to get a replacement, otherwise you can continue with the rest of the guide to make a proper scatter file and rom backup for your device. I will try to guide you to my best of my ability, but this is a really confusing area due to all of the things that can go wrong and all of the risks of bricking the device permanently.
Click to expand...
Click to collapse
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
xKroniK13x said:
Thanks for the quick response. It is the BNTV450/Marshmallow, which may be part of the problem. I do get the same error on the readback. It may be time to just retire the thing and grab a new ereader, I got a few years out of it and it was cheap.
EDIT: To respond to your question, I did use the shady ROM above. So note to others: don't do that...
Click to expand...
Click to collapse
Yeah, your device may be completely bricked. The Nook Tablet 7's are confusing due to the two of them being only slightly different, but different enough for disaster to happen.
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
I can. So last week I managed go back from a rooted situation to stock rom with LOCKED bootloader. This means that you're phone will be as you bought it and you're gonna lose everything of course.
This video on YT helped me.
***REMEMBER TO CHOOSE YOUR FIRMWARE BECAUSE I THINK THIS VIDEO IS FOR ASIA, IF IT IS THE SAME FOR YOU THEN YOU SHOULD FOLLOW THIS VIDEO***
I provide you a link with a thread on xda where I found the version for my oneplus 8 pro (EU)
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS | XDA Developers Forums (xda-developers.com)
Thanks I'll check it out and report back
glhelinski said:
Thanks I'll check it out and report back
Click to expand...
Click to collapse
Let me know
glhelinski said:
I'm not seeming to find coherent instructions to get back to stock 11.0.2.2IN11AA
I have the 8 Pro, rooted, newest magisk and I installed a magisk module that is now causing System UI crash at startup. I have tried a couple things: 1) tried the "adb wait-for-device shell magisk --remove-modules" --> nothing happens when starting back up except System UI error. 2) I've flashed back to stock boot.img (hoping to get to safe mode to disable magisk)...all I get is System UI error again.
So...what I want to do is start all over and end up with 11.0.2.2IN11AA rooted. Once I'm back to "factory" I'm pretty sure I can get back to magisk and root.
Can anyone help me with some decent instructions please?
Thanks
Click to expand...
Click to collapse
Visit the MSM thread, that's it
Sneakdovi said:
Let me know
Click to expand...
Click to collapse
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
glhelinski said:
Good site and instructions. They sure don't make it clear that msmtool is packaged inside the image download file
Click to expand...
Click to collapse
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Sneakdovi said:
I only donwloaded the EU verision (because i'm in Italy), went to qualcom recovery, and started the process
Click to expand...
Click to collapse
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
chr_rocke808 said:
Please help me, i'm bricked my new device. I want that ****** monocrome filter and make to many bull**** ! :-( I need my phone.
The MSM-Tool is give me always "Sahara" errors. Make the same misstake then you! I locked the bootloader!
Please.
Click to expand...
Click to collapse
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Post #2 above has a video and also links to the same place that freshlybaked420 referenced... Should be enough to get you back on track
FreshlyBaked 420 said:
First off, you may want to edit your language in here, no need to swear. Secondly you should check out the thread regarding the MSM tool.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, it's all true. Sorry for that i have now working for many days on this. Not sleeping enought. One more question that could bring me a step foward...
I was on IN11.0.2.2 before i locked the bootloader and bricked the device.
Now i downladed the Decrypted OxygenOS 11.0.0 IN21BA Version. I have now the error: Param Preload Device not match image. Question: Must i habe the Decrypted OxygenOS 11.0..2.2 IN21BA Version that it goes to work?
I can't the use the link for the right version, it is password protected.!
Thanks
The password is listed in the OP
glhelinski said:
The password is listed in the OP
Click to expand...
Click to collapse
Thank you, but I didn't find it.
One point I have forgotten to tell. Before the hard brick happened, I used Magistik and Patch a new boot.img then I flashed this with fastboot command. My failure was to make this 2. times. with different patches. The horrible thing is now that I must delete these files on my Laptop to get more space. When this the Problem of the MSMTOOL error is I had not really a chance to unbrick my device. Have anyone Downgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try it. I feel really scared. Maybe my device is not unbricked anymore.
The other Tool that I have (last chance) is the original Qualcomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But I found nothing here, that this tool was used. There is no special Rom here to found.
chr_rocke808 said:
Thank, but i didn't find it.
One point i forgotten to tell. Before the hard brick happend, i used Magistik and Patch a new boot.img then i flashed this with fastboot comand. My failure was to make this 2. times. with diffred pachtes. The horrible thing is now that i must delete this files on my Laptop to get more space. When this the Problem of the MSMTOOL error is i had not realy a chance to unbrick my device. Habe anyone Donwgrade with MSMTOOL the Stock Rom?
Thx for your help. I download now from OP the latest ROM. I will try. i feel realy scared. Mabye my device is not unbricked anymore.
The other Tool that i have (last chance) is the orginal Qulacomm flashing Tool QPST.
described here:
Download QPST Flash Tool & How to Use it to Flash Firmware on Qualcomm Android Devices
Download all versions of QPST Flash tool and learn how to use the QFIL and Software Download programs to flash firmware files on Qualcomm Android devices.
www.thecustomdroid.com
-- > But i found nothing here, that this tool was used. There is noch spezial Rom here to found.
Click to expand...
Click to collapse
None of that matters.
1st identify your device!
What region is it?
If you have BA then don't flash AA you'll mess things up.
2nd visit the MSM thread!
Download the tool 'for your device!'
3rd boot to EDL (I responded to you in the romaur thread how to do this)
4th as soon as it's connected to your pc in edl, flash the device
5th MSM will relock your bootloader.
6th don't do something if you're not sure, just ask.
Oh and lol chill on the swearing also on posting everywhere, just make 1 thread and stick with it, people will help
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
chr_rocke808 said:
Hey, my Phone is working like a charm. Thx for the great work !!!. I'm so happy !!!
It is better to come here to real developers, I had to get bad download links and bad Software! This was the only problem. For many years I have the first Samsung Galaxy and I'm knowing that I can get all the problems for not booting devices back. But I was scared that many Devices like Huwai bring their bootloaders with cryptographic methods in a safe trunk.
Best wishes to you, and the people that I'm working for the android project!
regardless,
chr_rocke808
Click to expand...
Click to collapse
Lol no worries pal, but trust me, always make a thread unless one exists, it'll work out.
Glad you're sorted.
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?