I've got a three day old Inn tablet that I tried to root according to the directions in this thread: https://forum.xda-developers.com/t/...0015685-series-root-and-cfw-linux-os.4195577/
The command fastboot --disable-verity --disable-verification vbmeta vbmeta.img returns an error saying "unknown command --disable-verity"
I have tried reflashing the stock boot.img, vbmeta.img, vbmeta_vendor.img, and vbmeta_system.img I downloaded from that same thread and I have tried the boot.img I patched with magisk.
The message I get on startup is either the orange state if the bootloader is unlocked or "bad state. Your device has failed verification and may not work properly. Please install boot image with correct signature or disable verified boot".
SP Flash Tools will not work on my laptop. The laptop is up to date and is working right, it runs Windows 10.
I have tried installing twrp to the recovery partition but it makes no difference. I was not able to back up anything from the tablet at all.
I have the back cover off. The only way to stop the bootloop is to unhook the battery.
EDIT: This tablet is brand new and came with Android 11 preinstalled. I had no personal stuff on it to lose, but I do have a similar, smaller Onn tablet that I *do* use some and would like to root once we figure this out.
How do I disable verified boot on the 100003562? Does someone have a vbmeta file they are willing to share that has the verified boot disabled already? If that's not possible, how do I restore the stock, non rooted ROM so it'll at least work?
Yes re-flashing tablets's Stock ROM to get rid off of all modifications you applied so far is best.
Flashing a Stock ROM typically is done by ADB Sideload method.
Will it work without being able to boot into recovery mode? That bootloops also, but I can get it into fastboot mode with no problem. The image I downloaded from here appears to be a recovery zip of some type. It's where I pulled the boot.img from that I patched with Magisk.
I don't have anything that was in the stock ROM in that particular tablet, just the stock ROM downloaded from this site. from that same model of tablet. I have considered picking up an identical one and trying to copy the ROM from it, but I'm not going to risk rooting a second one if I can't get this first one done.
There's a different file linked to later in that guide, I'll try it because I may have the vbmeta files from a totally different tablet. The file I just grabbed is at https://drive.google.com/drive/mobile/folders/1KG6IIULGfxVXM9msuaWMUvO8Vs9ih-w0?usp=sharing , later in the guide I used to root the device.
I'm not sure how to do the ADB sideload. I'm thinking it's "ADB sideload <filename>, not sure though.
I'm not near the tablet ATM.
If phone stucks into a bootloop then ADB Sideload won't work because a stable USB-connection isn't given.
There's a flash all command in fastboot. Will that help?
OK. I had a soft brick due to Android Verified Boot. I have it running the stock unrooted ROM, will try later to root Onn later.
WARNING WARNING WARNING
Some of these tablets are shipping with Android 11
"fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img" does NOT work on these devices. This is a command to disable Android Verified Boot.
YOU WILL SOFT BRICK THE DEVICE if you flash a magisk patched ROM through fastboot without first disabling the Android Verified Boot. It is possible to recover so Read Onn.... (pun intended).
There are certainly other ways to root this tablet and I am all ears to hear them.
END WARNING
I have, in the past, revived devices that appeared to be hard bricked. Most devices these days have an emergency boot block. The Onn 100003562 is no different. During a bootloop, it allows access to the filesystem at certain times. Enter SP flash tools and a known good image of the ROM, including the initial scatter file.
The newest version of SP flash tools is more busted than my tablet was. Get an older one from 2020. Get ADB and fastboot.
Now grab a PC and make a folder in the root directory called ADB. Extract ADB and fastboot into it. The rom image you downloaded should have a scatter file in it, make sure that gets into the ADB directory with everything else.
This is with Windows 10 in mind, but may work on UbuntuMATE 18.04 from my Toughbook, I think the directory there is "home". Get the tablet into fastboot mode (vol up + power), connect it to the PC with a USB cable, then type in
"fastboot flashing unlock"
and press Vol Up on the tablet to confirm. Next
"fastboot reboot" and if it's going to bootloop, it'll do that now.
If you want better control over the tablet, flex it slightly and insert a spudger into the crack that'll form on the side between the device's plastic frame and back bathtub panel. Gently remove the bathtub and locate the jack where the battery connects. Voila, you can stop the bootloop by removing the power!
Get the tablet to start bootlooping. A good way is to either hit the power key or get it into fastboot mode (hold volume up, press power, and hold til the bootloader shows up) then "fastboot reboot".
Unzip the ROM files you downloaded into the ADB folder. Set up SP flash tools and open it (mine requires double clicking the flash.exe file). Click the Format tab and click both "Auto Format Flash" and "format flash except bootloader"
WARNING: do NOT format the bootloader!!!
Wait for the tablet screen to go dark and then hit "start". This will erase everything except what I call the emergency boot block. You should hear the PC ding every few seconds while the tablet is powered up and physically connected to it. The tablet screen will not light up at all for now. Fastboot mode will be inaccessible.
Now on SP Flash Tools, click "Download" and click "choose" on the line with the scatter loading file. Navigate to c:\ADB or Home:\ADB and click the file. If you put the scatter file in another directory, navigate there instead and click it. The scatter-loading file line will populate. Just below it is a checkbox next to "name", uncheck it and ensure ALL the checkboxes are empty in the spreadsheet below that. Check the box next to "boot".
Your PC should still be singing, this means the tablet is bootlooping and searching for a command right after it reconnects electronically to the PC every few seconds. Wait for the USB connected sound then hit "download". The boot.img file will be written to your tablet but it will still continue to bootloop. Fastboot will still be inaccessible.
Go back to SP Flash Tools and check the box next to "name" at the top of the spreadsheet. All the boxes will be checked that you have files for in the ADB directory (or wherever you extracted them with the scatter file). Wait for the USB connected sound, then hit download. Grab a beer or go use the restroom, this will take a few minutes.
When it's done SP Flash Tools will display a message stating such.
Charge the tablet if necessary then press the power key. Bam, no Orange or Red state warning. The white One logo will appear for a few seconds, disappear, and be replaced with the shiny Onn animation. This first boot will take several minutes, so finish up the beer while you wait.
If all is well you should be looking at the inroductory screen. Walk through setup, enable developer options, enable bootloader unlocking, and try whatever it was you were doing again.
I see this forum and our devices as an opportunity to learn. I hope I have been helpful with this, and if I there's something wrong or that can be done better, by all means, post it.
Have a fantastic day!
Related
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
First I'll give credit where it is due. From two threads on this site is where I got help with this issue:
I followed THIS guys steps for manually erasing and got the recovery images and lots of other useful information from HERE. Thank you guys very much!
OK, so, hopefully I can help someone with my little story as well. I was having issues with apps and programs crashing on me with lollipop and the new marshmallow update. The tablet just wasn't working properly and moving slow. I even had the SD card holding all my apps and larger files so I didn't overload the internal storage. So, I decided I wanted to flash back to factory/stock recovery and go from there. I did this using THIS method. I flashed via the "flash-all.bat" file (the command in fastboot is the same as the file name). I should note that there was one instance that failed during the install (I did try it again and got the same failure). Said something about “did you mean you wanted to flash this partition” or something, then showed it failed. After flashing I hit continue on the bootloader screen of the tablet and it said it was "cold booting." After about 5 minutes or so it started to boot but never made it past the NVidia screen. I tried wiping the phone with factory reset, wiping the cache, etc. and then re-flashing the recovery (again with the .bat file). I tried flashing TWRP but it didn't install apparently, because it still went to factory recovery. I even re-locked and then unlocked my bootloader to see if that would set everything straight. Nothing seemed to work. I knew I would eventually find a solution though so I kept looking. Stumbled on some other people that had the same issues but no solution (hope those people got it figured out). So here's what I did after some more research:
First, if you're in this situation and you did factory reset to try and resolve the problem, you may feel like you can no longer communicate with the device via fastboot/adb, but as long as you have the usb drive and your SDK tools installed (I used CodeWorks for Android all-in-one program) that shouldn't be a problem. You'll just have to be in the bootloader on the tablet.
-If for some reason you deleted or uninstalled your drivers and tools you'll have to download them again and then, the computer should still be able to communicate with the tablet. In the device manager under portable devices it will still show up as Module something or other. So the computer still sees the device but doesn't fully recognize it yet. Don't worry, this should still work! Just make sure you that fastboot is seeing the device by inputting "fastboot devices" in the command window and a 14 digit serial number should pop up. If it just says "list of devices" or there's nothing then you wont be communicating with the tablet.
Your device should be connected to your computer and started in bootloader mode. On your computer you should have the command prompt for adb/fastboot open. I just go to the folder where the .exe files are located and hold shift and right click in the white space of the folder, then select "open command window here."
From here follow the erase steps: stolen from manigault! :highfive:
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
Then flash your recovery MANUALLY:
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
You can download whatever recovery version you wish. I downloaded 2.2.2 because that's what my device came with out of the box on Christmas 2014. It will more then likely be a .zip file. To make this whole process a little easier simply extract the files in the .zip file where the adb.exe and fastboot.exe files are located (folder should be named platform-tools) and you can completely eliminate typing the whole directory before the file name. ***After your done flashing everything you can go back and delete those files if you want. Just double check that you're deleting the right files by looking at the original zip file. Not sure if it makes a difference but I deleted them anyway.
For example the commands in fastboot will look like this exactly :
(after extracting recovery files into platform-tools folder)
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
Note: Do NOT use the flash-all.bat command as this doesn't seem to work for this situation. Do it manually like shown above. And let each individual process complete before attempting to input another command.
After this step I didn't select continue on the bootloader. You can either select reboot or simply input "fastboot reboot" into the command window. It may take about 5 minutes to start installing everything but just be patient, it should start. Sometimes with these things you have to do things twice before it works. If for some reason it doesn't work the first time then start from the beginning and try it again. It took two times for me, but that's because I installed system.img twice and was getting double screen. Newb error... and I was a bit inebriated last night when I did this.
Hope this helps someone!
Thanks again to manigault and MidgetMob!
NVIDIA download files HERE!
i think i done the same thing
but the problem i now have is i cnt get tablet into fastboot on pc. i can load fastboot on tablet with power and volume down , but the tablet only shows as MTP device in device manager. i have downloaded drivers from nvidia and no matter what i try i cant install them i have been through all instructions but scince it went to mtp device i cant get device showing in adb. The only way i can get device showing in adb on pc ist to select apply update from adb ! but none of these commands listed in your post will work because its in sideload. is there anyway i cn reset , flash custom rom ect bu using commands while device is in adb sideload.
all i get is now send the package you want to apply to the device with "adb sideload <filename>".....
if you could shed any light on this it would be much appreciated , thanks , lester
did you update official android 6.0 before? then, not working stock recovery, stock boot...
If you can enter bootloader mode, download unofficial twrp 3.0.0.0 (here http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117) and flash it.
i have a working boot.img file on marshmallow if you want.. please reply.
Sorry for the late response! I have no clue how you got into sideload??? Are you talking about through the recovery on your device? You're not able to get adb/ fastboot to recognize the device, right? It doesn't matter how you get the tablet into the bootloader. Whenever you have the phone in the bootloader then you'll use the fastboot command to "talk to" the device; i.e. "fastboot devices" without the quotes. That command should show your device if it shows as an MTP device whenever you open your "device manager" in windows. That's the same exact situation I was in. Download the codeworks from nvidia like I linked above. Hopefully then you should be able to recognize your device through the bootloader. If not DM me and I'll try to help you.
I'm having the exact problem as Lester. Tablet boots into bootloader but won't connect to computer. So I go into recovery mode and nothing works except apply update from adb. Which brings up the side load message that Lester quoted. And bootloader is showing "device=locked". I am attempting to fix this tablet for a friend that messed it up trying to flash a custom rom. Problem is he had no idea what he was doing and I'm not exactly sure what he did. I do however have a lot of experience with rooted android devices and flashing so any help would be GREATLY APPRECIATED!
---------- Post added at 05:59 PM ---------- Previous post was at 05:55 PM ----------
Also, I've already tried flashing stock rom back onto the tablet by applying update from sd card function in the recovery but when I try to do that the tablet for some reason can't mount the sd card.
rom fiend said:
Tablet boots into bootloader but won't connect to computer.
Click to expand...
Click to collapse
If you've got the device in bootloader then you need to use fastboot, not adb. Try the command 'fastboot devices' and see if the device id is listed. If so then grab a factory image, unzip it and use fastboot to flash the .img files using the commands 'fastboot flash system system.img'. Just make sure to match the partition names to the files.
Hello i have similar issue except when i try flash something i get this error ''remote: file write failed''
and i have to reboot into fastboot to get it flashing fully
but even though i managed to flash everything by rebooting when i boot system nothing shows up, i can just see the back light coming on and turning off after a while
Please help
Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?
boot-to-root is for Android O, you have to follow this guide
I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.
falsh factory image inside the bootloader, don't need to go to recovery.
Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.
Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018
"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin
volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs
Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.
unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!
Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this
@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs
not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s
What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs
Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.
@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs
I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?
ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.
@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs
I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).
I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.
unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.
Hello,
I have a TCL 20y (model 6156D) phone and i'm trying to gain root access in any way.
I've tried to enable oem unlocking and go to fatboot mode, but the command
fastboot oem unlock returns "FAILED (remote: 'Command not supported in default implementation')".
On producer website i can't find this model and in the "repair software" this model (6156D) is missing.
I don't have any recovery file (stock or trwp), and i don't know how to dump original recovery to file (for install magisk, but anyway i think i can't flash modified versions without unlock bootloader).
Is there anything i can try?
---
Edit: I finally found the original flash tool at the following url:
Modello
www.tcl.com
https://www.tcl.com/content/dam/tcl-html/TCTService/support/tcl-20-r-5g/Mobile_Upgrade_S_Gotu2_v1.1.5_Setup.exe
It seems to support model 6156 and, with connected phone, it has downloaded a lot of files and created a folder "6156D-2ALCWE12\ANAJEAJ0" (model\version) with a lot of files with MBN extension and a zip with system.img inside.
Maybe these files may be useful to root the phone. Anybody knows how to open MBN files?
--
Edit: I've notice a strange thing. When I boot to recovery, i see two interesting options:
- Enter fastboot: this stats "fastbootd", a graphical menu with a few reboot options. In this phase the computer recognizes the phone with fastboot driver and list it with "fastboot devices" command.
- Reboot to bootloader: this clear the screen, writes "FASTBOOT>" in the low position of the screen. In this phase the computer recognizes the phone with adb driver and don't list it in fastboot devices nor adb devices.
I've also tried to flash magisk apk (renamed as zip) with adb sideload, but as expected i got Error 21.
Is there a way to sign any root manager or su binary and install it using this method?
What am i doing wrong?
Hi!
I've managed to unlock the bootloader on a TCL 20Y by following this guide: https://romprovider.com/tcl-20y-unlock-bootloader/.
I used the mtk_gui utility, which is really straightforward. The only tricky thing was going into brom/preloader mode - sometimes it works, other times it doesn't.. The trick is to hold both volume buttons while plugging in the USB cable to the computer.
Then, I've also managed to root the device with Magisk by patching both the boot_a.img and boot_b.img images and flashing them using fastboot by following the official guide: https://topjohnwu.github.io/Magisk/install.html.
Haven't yet played with the orange state disabler as I've read that it can result in a brick.
BR
Hey there!
With bevvare's help I was also able to root my TCL 20Y without much issue, though I encountered a few minor differences and details so we agreed it would be good if I wrote them down here.
Regarding the first guide used to unlock the bootloader:
The mtk_gui utility packed in the, as of today, latest release of mtkclient (1.52) refused to launch. That wasn't too bad seeing as the guide provides the necessary commands, but it's something to keep in mind.
In addition, I found that the phone would stop accepting commands after the first one was issued or after the log got too long*. This might have only been an issue on my end, but just in case, this is how i ran each command:
-Turn the phone off
-Hold the power button along with both vol+ and vol- (you may plug in the phone at this stage)-While in the Recovery Mode screen, issue the command on your terminal-Select the option to restart the device in the recovery screen, then hold both vol+ and vol- until the terminal starts printing output (the phone's screen will stay off while this happens)-After the command has executed, unplug the phone (probably optional) and hold all three buttons again to restart and boot into recoveryRepeat as needed
* Remember how I mentioned the command seemed to fail if the log got too long? Well, this is what happened to me with the very first command on the guide (the one that erases three partitions at once). Just to be sure, I erased them separately using the same command.PS: booting into recovery first may not even be needed, I just found it easier that way.
The guide provides two unlock commands, the first one being python mtk xflash seccfg unlock, this ran without issue and triggered the orange state warning on boot. The second command (fastboot flashing unlock) refused to work, but the bootloader was nonetheless unlocked.
Also, the guide provides the relock command right after the unlock one as if it were the next step to take. This might be obvious, but don't relock your bootloader until after you're done flashing the new boot image (even then there's no real reason to relock it).
Regarding Magisk's guide on patching boot.img:
Magisk failed to patch boot_b.img. This turned out to not be a problem because my device was using the boot_a partition as the active one (I used this guide to check https://krispitech.com/check-partition-slot-a-b/ )
In order to get the necessary files, namely boot_a.img and vbmeta_a.img, I used this guide to dump all the partitions within the phone into my PC: https://forum.xda-developers.com/t/...sing-mtk-client-oppo-reno6-5g-mt6877.4406069/
You may also decide to dump only the two partitions you need, in which case you could issue the following command instead: python mtk rl boot_a,vbmeta_a boot_a.img,vbmeta_a.img (this assumes your phone is also using partition A, adjust as needed).
If you used the above guide to dump all the partitions, the files you need will have the .bin extension, just rename them so they are .img files instead.
I recommend flashing vbmeta_a.img (it's optional and doesn't need to be patched in the Magisk app like boot_a.img). Otherwise your device will print a spooky warning at boot about being corrupt and demand you press the power button, which is annoying.