I have been reading for many days and there is no way I can get into fastboot , to install new system ,no boot logo, not fastboot.
I have some other way to repair fastboot?
Is it possible to delete the fastboot?
If so, can it be rewritten?
thanks
Pro, or Standard?! I don't know what to tell you about the Standard though.
If it's the Pro we're talking about I would slow down FAST! And, have a look at the SSHD to SSD Migration Threads here first. Namely the bits on cloning it. Which might at first seem to be pointless. But let me explain.
Each Shield TV has a hidden Partition inside the SSHD that contains the valid Widevine L1 Keys. In short you will want these if you have plans to use either Amazon, Netflix or <Insert other heavy handed OTT Service here!>.
While you may have forked the Bootloader to a permabricking state. You could use the Op's Backup Image of his own Shield TV which he was generous enough to make public.
That however would way out your own Keys FOREVER! The practical upshot would be like an XBOX Live Permaban.
So heres the "Idea", you backup what's left of your SSHD Under normal circumstances you should never have need to touch the Security Sectors of the SSHD. Once you have made that Backup... Following the info from that Thread. Go ahead and install Ops backup Image to your Shield.
(Full disclosure) It's to late for me, so I can't tell you exactly which Partition you need or which DD command to enter, in order to flash back your personal Security Sector to your Device. I think I may have inquired about it in that Thread. But not having bothered to make a backup even at that point means I no longer have those Keys, even if I do have a working Shield TV. But as long as you can replace the correct Partition with the One that came with the Shield you should be able to recover.
Now outside of that advice. You really don't need to ask me anything further. Again I never managed to get that far. I was going on what turned out to be false information at the time that only Netflix would be affected, by a broken ESN. What the people in that Thread probably faild to realize was that it was the Widevine Keys that were to blame. So I thought ok fork Netflix! As long as I can use Amazon.
Needless to say: WRONG ANSWER!
But, if I were in your shoes now, the above would be my plan of attack. But, I'm not the One to be asking about how to do all of that. Besides most of the foreseeable questions should already be answered there.
if you cant boot into bootloader or fastboot mode, at least in 16gb, your screwed. Better request for RMA.
Sent from my Tapatalk Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
Ichijoe said:
Pro, or Standard?! I don't know what to tell you about the Standard though.
If it's the Pro we're talking about I would slow down FAST! And, have a look at the SSHD to SSD Migration Threads here first. Namely the bits on cloning it. Which might at first seem to be pointless. But let me explain.
Each Shield TV has a hidden Partition inside the SSHD that contains the valid Widevine L1 Keys. In short you will want these if you have plans to use either Amazon, Netflix or <Insert other heavy handed OTT Service here!>.
While you may have forked the Bootloader to a permabricking state. You could use the Op's Backup Image of his own Shield TV which he was generous enough to make public.
That however would way out your own Keys FOREVER! The practical upshot would be like an XBOX Live Permaban.
So heres the "Idea", you backup what's left of your SSHD Under normal circumstances you should never have need to touch the Security Sectors of the SSHD. Once you have made that Backup... Following the info from that Thread. Go ahead and install Ops backup Image to your Shield.
(Full disclosure) It's to late for me, so I can't tell you exactly which Partition you need or which DD command to enter, in order to flash back your personal Security Sector to your Device. I think I may have inquired about it in that Thread. But not having bothered to make a backup even at that point means I no longer have those Keys, even if I do have a working Shield TV. But as long as you can replace the correct Partition with the One that came with the Shield you should be able to recover.
Now outside of that advice. You really don't need to ask me anything further. Again I never managed to get that far. I was going on what turned out to be false information at the time that only Netflix would be affected, by a broken ESN. What the people in that Thread probably faild to realize was that it was the Widevine Keys that were to blame. So I thought ok fork Netflix! As long as I can use Amazon.
Needless to say: WRONG ANSWER!
But, if I were in your shoes now, the above would be my plan of attack. But, I'm not the One to be asking about how to do all of that. Besides most of the foreseeable questions should already be answered there.
Click to expand...
Click to collapse
Many thanks for your reply, but I do not have the pro and I do not have a backup.
demondhume said:
Many thanks for your reply, but I do not have the pro and I do not have a backup.
Click to expand...
Click to collapse
If you have a "Standard" (i.e. The 16Gb), then it's pretty much the end of the Road for you. As there is no way outside of a nVIDIA Factory, that I'm aware of that would allow you to recover your Bootloader on an eMMC Chip. Without some very expensive equipment, and some very MAD SKILLZ. Apperently someone here managed to do that by upgrading the Chip to 32Gb's, from the usual 16. But, this is likely beyond the scope of most People.
It kinda sucks to say it, but I think it's time to start looking for a replacement.
demondhume said:
I have been reading for many days and there is no way I can get into fastboot , to install new system ,no boot logo, not fastboot.
I have some other way to repair fastboot?
Is it possible to delete the fastboot?
If so, can it be rewritten?
thanks
Click to expand...
Click to collapse
It is possible to delete the fastboot if you've performed this command
fastboot erase bootloader
If not, I suspect that you just can't deal with the hardware trick to enter the bootloader which it is tricky indeed
- with the TV box disconnect from the power cable
- Connect the hdmi both to TV and TV box
- connect the USB cable to both pc /laptop and TV box
- connect the power cable and on the next split second hold the power button of the TV box for few seconds, it should go to bootloader
From there, use the Nvidia TV box recovery image to flash it, there are instructions on website about how to which consists on a set of fastboot commands
Before starting be sure that the fastboot drivers are correctly installed and functional
Sent from my Darkside of Oneplus 3T
it is clear that OP's device is in that state because he already flashed something (wrongly) and nuked the bootloader.
If he already flashed something, it means he knows how to get into fastboot or bootloader mode, so that is not the issue. The issue is that OP bricked his device by flashing wrong bootloader, and if the bootloader gets corrupted in 16gb model you won't be able to boot into that mode, thus not able to flash anything anymore.
Best advice is to request for RMA.
Sent from my Tapatalk Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
Related
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Cannon Fodder said:
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Click to expand...
Click to collapse
Looks like you will need to replace the mb, if you have not already generated nvflash binaries. You can't read/ write to internal memory because when connected to a pc this is done using the mtp protocol which os loaded by android, and hasn't in your case.
JoinTheRealms said:
Looks like you will need to replace the mb, if you have not already generated nvflash binaries. You can't read/ write to internal memory because when connected to a pc this is done using the mtp protocol which os loaded by android, and hasn't in your case.
Click to expand...
Click to collapse
Ok another n00b question...
Why can't I download someone else's binaries from the same type of product?
Forgive me, I'm used to working with Windows and I'm thinking in terms of an install disc...
Cannon Fodder said:
Ok another n00b question...
Why can't I download someone else's binaries from the same type of product?
Forgive me, I'm used to working with Windows and I'm thinking in terms of an install disc...
Click to expand...
Click to collapse
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Cannon Fodder said:
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Click to expand...
Click to collapse
Here is a link to my guide to enter the bootloader.* Try these each several times as this tablet morphs as you progress.
Provide us a little more info.
What happened to create this problem? *Details please.
Did you have a custom recovery, rom, etc? *If so which ones?
Can you fix it; maybe. *We'll have a better idea once we know your details.
cmendonc2 said:
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Click to expand...
Click to collapse
Thank you for that illustration. It did help me understand.
One last thought of desperation: Is the internal storage an actual SD Card? Or is it just called that on the device menu for some odd reason?
tobdaryl said:
Here is a link to my guide to enter the bootloader.* Try these each several times as this tablet morphs as you progress.
Provide us a little more info.
What happened to create this problem? *Details please.
Did you have a custom recovery, rom, etc? *If so which ones?
Can you fix it; maybe. *We'll have a better idea once we know your details.
Click to expand...
Click to collapse
I was installing a custom ROM, when I went to "RCK"(?), it hung up when it said it was booting kernal. It didn't do anything for quite a while, so I held down the power buttong and reset it. And now it is stuck in the boot loop.
cmendonc2 said:
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Click to expand...
Click to collapse
off topic but that is a pretty good analogy :highfive:
One question tearing me long enought: did someone tryed to hack nvflash binaries? As far as I know there is only one unique file and may be not all of it's content is specific for certain device. Did someone dig in that direction?
Graiden05 said:
One question tearing me long enought: did someone tryed to hack nvflash binaries? As far as I know there is only one unique file and may be not all of it's content is specific for certain device. Did someone dig in that direction?
Click to expand...
Click to collapse
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.
I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Cannon Fodder said:
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.
I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Click to expand...
Click to collapse
Think of it like a cryptographic key. Each tablet's NVFlash blobs has a certain signature. To compare it to the Windows situation, assume that you have a legal, non-volume licence key for Windows, only that when you installed it the first time, the key was permanently bound to the motherboard.
Assume that it is a string of lower-case letters (good chance that it has numbers, capital letters, and all sorts of fun stuff). A two-character signature has a space of 26*26, which is already over 625 keys. That number scales hella fast when you add more characters.
Asus will fix your tablet by either replacing your motherboard completely (more likely), or they may have the NVFlash keys for your device by its serial number. However, since your bootloader is unlocked, and they will have your serial number on file as "unlocked", they may just refuse to repair it outright. Surely, they will refuse it for a warranty repair, though I don't know if they will even repair your device for money.
Hi there,
i got a little question prior rooting my Shield TV 2017 pro.
I read a bit about the L1 +L2 Widivine keys on the shield so my question is, does rooting the shield has any influence with the keys, for example will Amazon + Netflix 4k stream work after?
The second question is, is twrp on the shield able to create a backup of thoose partitions in case the hdd bricks or something went wrong during flashing?
EDIT:
In case anyone needs the answer, too just read the two following posts by lavero.burgos and mr-tee and some warnings from ichijoe in 3rd, which are very detailed and helpfull
Thanks in advance
JeckyllHavok
Hello, the answer is NO, rooting your device will NOT mess with your keys nor damage them, simply because as systemless root it only safely modify boot.img and the rest goes to the data partition, so it won't touch sensitive data. The recommended method is to install SuperSU which is developed by Chainfire (the guy know what he does, he's an excellent dev).
Netflix and Amazon work for me with root, but yes there are services out there with their own apps that don't allow root. If they detect root you won't be able to play their content (IMO bad practice, i would change service if that is the case).
About TWRP, no it won't allow you to backup the relevant partitions because TWRP handle standard partitions that every Android device has, so unless someone makes a custom TWRP to include that the only way i know off is running dd comands from linux distro to backup the needed partition(s). I have done it myself in the past (many years ago) with the old Nook Tablet.
I made videos about that but you first need to know the partition block name, for example mmcblk0p8, once you have that info you can go to YouTube and search how to backup partitions with dd command and also check the following playlist where you can find the videos i made long ago:
Community Forums: http://www.youtube.com/playlist?list=PL216837379418927A
I'm very curious why many 500 PRO users have bricked their devices. What you really need to be careful with is the bootloader (blob file), don't mess with it. You can no longer downgrade bootloader from Nougat or newer to MM or older and in case you want to upgrade your hdd with a ssd and clone it then you also have to prepare to damage your device in the way.
I only have the 16GB 2015 model but would be great if someone post a screenshot of the famous backup a user has posted for the 500GB PRO, i would like to see what is inside.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
First of all I would say, try root first, see if it affects the apps you want to use.
Don't FLASH TWRP, yet tell fastboot to boot the recovery image. But even flashing it won't harm anything. There are stock ROMs on the nvidia developer website, with the original recovery image, so you can always flash back the stock recovery, but well, not flashing a different recovery will save some effort and time.
If you have installed supersu you'll be able to fully UNROOT inside the supersu app. So, first try it out, without changing any system files, see if the apps you use work, then you could consider going further with customizations. But you can always return to stock, just don't mess around with files outside the system or vendor folder. And especially not the bootloader (blob). But there is a blob file inside the official stock ROM from nvidia.
One warning: DON"T use the flash-all.bat file included in the nvidia ROM.. use the commands manually...!!
Thanks for the detailes answers, yeah i know about dd commands, and fastboot or adb, just wanted to be sure that nothing strange happens.
Cause i never got any Widevine L1 certified device
So tonight rooting a shield...
To answer some of your questions.
Rooting will NOT mess with your Keys directly. But, sooner or later nVIDIA are going to start lobbing Updates again. And, if you have a setup which involves say a 4k (2160p) TV*. Then you CAN NOT just simply load up TWRP from some location. To do your business (i.e. rooting it), then exit back out and leave the Shield otherwise stock. (e.g. you never actually replaced 3e (or whatever nVidia calles the Recovery, with TWRP.)
This does not mean that you can not install (i.e. replace) 3e, with TWRP, and then just boot into that. That, would work perfectly, and that's what got me into the deep Dodoo.
Again whatever you do DO NOT replace your Recover with TWRP! Sooner or latter this will bite you in the 455! The moment when nVIDIA decide to push out an update, and sends your Device into a bootloop. Which will make you want to downgrade, and then hardbrick the Device.
But, beyond all that, there are plenty of other good reasons to make that backup of the original SSHD. Beyond having a simple backup of just the Keys. As these Drives, like all Drives eventually fail.
* I gather those with them old fangled 720p, 1080p Sets out there will NOT have this problem. Which I can confirm, as I can load up TWRP just fine over the fastboot command line on my Old Man's 1080p Samsung. Alas back home it's just the One 4k Set. And that will not work. Unless loaded directly on the Device.
Ichijoe said:
To answer some of your questions.
Rooting will NOT mess with your Keys directly. But, sooner or later nVIDIA are going to start lobbing Updates again. And, if you have a setup which involves say a 4k (2160p) TV*. Then you CAN NOT just simply load up TWRP from some location. To do your business (i.e. rooting it), then exit back out and leave the Shield otherwise stock. (e.g. you never actually replaced 3e (or whatever nVidia calles the Recovery, with TWRP.)
This does not mean that you can not install (i.e. replace) 3e, with TWRP, and then just boot into that. That, would work perfectly, and that's what got me into the deep Dodoo.
Again whatever you do DO NOT replace your Recover with TWRP! Sooner or latter this will bite you in the 455! The moment when nVIDIA decide to push out an update, and sends your Device into a bootloop. Which will make you want to downgrade, and then hardbrick the Device.
But, beyond all that, there are plenty of other good reasons to make that backup of the original SSHD. Beyond having a simple backup of just the Keys. As these Drives, like all Drives eventually fail.
* I gather those with them old fangled 720p, 1080p Sets out there will NOT have this problem. Which I can confirm, as I can load up TWRP just fine over the fastboot command line on my Old Man's 1080p Samsung. Alas back home it's just the One 4k Set. And that will not work. Unless loaded directly on the Device.
Click to expand...
Click to collapse
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
JeckyllHavok said:
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
Click to expand...
Click to collapse
As long as you do NOT replace the Recovery with TRWP. But, just call it up though Fastboot ~boot recovery <path to TWRP> then you should be nearly 100% safe.
But, having learnt my own lessens I would personally recommend leaving the Shield alone I'm not sure what good Rooting it actually has. And I'm a very big fan of AdAway, but AdAway just doesn't seem to do jack on the Shield. And, though you have to root to add Unofficial channels to Plex. At the end of the day. Those Channels have like for like Kodi Addons.
But again as long as you don't flash (replace) the stock Recovery with TWRP, you should be ok. Assuming an Update rolls along, (as they do), you should just be able to load up TWRP, like before, and flash SuperSU, and then go on with your business.
JeckyllHavok said:
Thanks for the hints, the way i would root the shield would be:
-Unlock Bootloader
-fastboot boot twrp.img
-flash the su stuff
I got no need atm to replace recovery, so i keep it stock, just want root for droid mote, launcher and maybe xposed, and a dd backup of the whole shield hdd
Click to expand...
Click to collapse
Those steps are correct, just know that in a 500gb PRO model unlocking the device will securely wipe your device and that task takes around 2 hours to complete in that specific model.
You can also use adb to sideload SuperSU package while in TWRP (Advanced >> ADB sideload):
adb sideload supersu_package_name.zip
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
I know I’m a newb here but I wanted to make a thread dedicated to theses devices in which I I have detailed instructions for rooting as well as CFW’s and unbricking!
I appreciate any donations sent via PayPal email for PayPal is on my profile.
Onn 100003562 Root instructions:
****UPDATE*****
With the newly uploaded rom all you have to do is download use sp flash to install .
May still have to run " fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img " command in fastboot mode.
Step 1: Downloads
Download Magisk manager and update.
Download ADB & FASTBOOT.
Below I'll have a link for windows. for linux run command "sudo apt install adb".
Dwnload boot.img and vbmeta.img.
Download SP Flash Tools and wwrMTK <---Will make this much faster XD.
I have all of these available
here--> https://drive.google.com/drive/folders/1lREGI_nd7kghuR6vCDjhiOZvbWrpJfBo?usp=sharing <--here.
Step 2:
Install magisk manager and update.
You can either download on the tablet or sideload with adb.
For sideload in windows shift + right click in the platform tools directory and click open power shell here.
Make sure you have MagiskManager-v8.0.0[1].apk saved within this directory.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
For linux Right click the directory in which you have MagiskManager-v8.0.0[1].apk stored and click open terminal here.
Then run command "adb install MagiskManager-v8.0.0[1].apk"
Step 3:
Either make a backup with SP Flash tools or use the boot.img i have provided and copy it to your tablet.
Open magisk on the tablet and click the install then click select image to patch. Locate the boot.img and select it by clicking on it. Watch it finish make sure it fully completes the patch and creates the magisk-patched.img file. Also it may or may not be necessary to patch the recovery.img depending on your system. most likely not.
Step 4:
Flashing the .img files.
Now that you have adb and the images necessary to flash your device power it down and back up holding the volume up key. Once It boots it should load into the bootloader screen click the up key until you have fastboot selected and then click the down key.
Now that you are in fast boot mode you are going to navigate to adb fastboot directory and right click and select open powershell here. again make sure you have all necessary .img files stored in the adb fastboot directory. you should have the patched .img and the vbmeta.img stored in the directory for windows.
Run these commands:
fastboot flashing unlock
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
Wait for it to reboot and then you will be rooted with magisk. enjoy.
I'm always grateful for donations paypal email for donations is on my profile.
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets
Okiera29 said:
That thread has a modified lk.bin file to remove the orange state warning. It has worked great on both of my Gen 2 7 inch tablets
Click to expand...
Click to collapse
I'm looking to do the same on my 10", do you think they're interchangeable?
Yes onm
Abelbody said:
Yes onm
Click to expand...
Click to collapse
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.
PleaseBeNicetoMe said:
Something must be lost in translation. I'm looking for a patched lk.bin for the 10.1", not the 7".
If anyone is interested, the 7" version is not compatible with the 10.1" version. Luckily SP Flash restored it.
Click to expand...
Click to collapse
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today
Okiera29 said:
Sorry about that. It appears that Fred patched your lk.bin file for you on the other thread today
Click to expand...
Click to collapse
Yes it worked too if anyone has the same question
Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
hightowerc said:
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
I believe that you need to download SP Flash tools if you haven't already. You can then, using the provided scatter file and the downloaded firmware, just reflash the stock firmware to the tablet. You will of course, have to re-root the tablet after it finishes
PleaseBeNicetoMe said:
Thanks for everyone's work for these tablets. I have both the new 7" and 10.1". Does anyone know how to edit the lk.bin file to remove that ugly Orange State warning after unlocking the bootloader?
This is a post that works great for the 7".
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
I just want to see if the same thing can be done with the 10.1"? If the files are identical great, but I don't want to risk needing to restore my tablet by just trying it blind. Not yet anyway.
Click to expand...
Click to collapse
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.
KaosKreationz said:
I’ll look into it sorry I’ve been having some issues lately and haven’t gotten much done on this thread. I was hoping to make an all in one spot for the newer android 10 models. I’ll get the 7 model info and stocks here soon. Is there already a working orange state mod already? If so can you link it and I’ll get into messing with it.
also these Mtk devicesseem to be difficult to get the source for. I’ve contacted mtk multiple times now and still have not gotten a response. I have however been digging through the hidden settings of thesedevices and it seems if they were to release their source they and Walmart may get into a huge amount of trouble as well as lawsuits filed against them. I’m finding these tablets have a sim installed somewhere and are uploading and downloading data via hidden software I’ve disabled the Verizon network locks and the data services in my device I just haven’t been able to really get into it to see what data is being transfer but I have also found some kinda remote camera and sound recorder software also hidden on the device.
Click to expand...
Click to collapse
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
PleaseBeNicetoMe said:
Don't know about your data transfer theory but there's the post with the 10.1" Pro lk.img edit to remove the Orange State warning.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com
Click to expand...
Click to collapse
thnx ill check this out very soon. im working on a Wiko Ride rn. frp bypass was a total pain took 2 days of trial and error but i was able to bypass.XD
hightowerc said:
Help! I followed the instructions in the OP, and everything worked fine. I then used ADB to uninstall some of the preinstalled apps, but I think I uninstalled something I shouldn't have. i'm getting crashes from mutltiple apps (Bluetooth, Contacts, etc).
I've downloaded the stock firmware/full in the linked GDrive share; how can I restore back to this stock firmware? I'm pretty new/noob with this, but I am familiar with Linux commands. (familiar enough to be dangerous...)
Click to expand...
Click to collapse
What’s your system? Did you get it fixed? I know I screwed up my first go round with the 10.1 Bluetooth and such kept crashing after I removed one of the un used features well supposed to be unused. It was the telephony and the contacts and autodialer that caused my issues. But like I stated before there seems to be some kind of wireless data traffic that’s not supposed to be there hidden software wise and it seems to utilize the cellphone apps that are supposed to be unused. Like the original bloatware remover from one of these threads on the original android 9 versions cannot be used bc there is something utilizing the cellphone data apps.
Anyway if there is anything you need firmware wise let me know I’ll upload whatever I have available.
This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless
I used this method to root the new tablet I just picked up, and now whenever I launch any app it freezes my tablet and forces a fast reboot of the tablet, I believe I am on android 10, but I can't confirm as I can't even open settings
okay, so I tried to completely flash the stock images you provided in the other thread, got everything working again, without root, then flashed the patched images you had and got stuck in a screen that just said onn with nothing else happening
edit: I have adb access to the device when it's plugged in so I'm not sure what is happening
Alright, I found out my issue, I was flashing the wrong patched boot img on an older firmware instead of updating to latest, I have gotten a working magisk root on the 10.1 tablet.
So as promised I have attached the lk.bin with the no orange state modification it does still seem to hang for 5 seconds but the ugly message is no longer visible.
this is for the 100003562 10.1 inch model but should work with the newer 10.1 inch models with the MT8768WA chipset that come with android 10.
Installation Instructions:
1. Download lknoorange.bin attached to post.
2. Open either powershell (Windows) or Terminal (linux) where you have the file saved.
3. Put device in fastboot mode by powering on and holding the volume up button and selecting fastboot with volume down button.
4. Use command:
"fastboot flash lk lknoorange.bin"
5. Use command:
"fastboot reboot"
Now you should no longer see the ugly message on boot.
Always love getting donations thanks again all and I wish you the happiest of holidays.
Trixi Needs a Rabbit said:
This is just BS. I agree about the hidden sim. I went through the different log files. This entire system is corrupt. My Google play store was installed by.... You guessed it Google Play. Click on it and I get a retry
My new Samsung phone is also screwed up and the 102.00 for Norton VPN and security was shredded in seconds.
There is NO original boot, no original system. What an I supposed to do? This is the 2nd one. Can't hard reset damn phone, Cricket because I've lost so many. I was able to hard set the Samsung without the SIM card, and it was perfect. Put the SIM card in, and all that freaking bloat comes in.
So I'm no IT person, with compromised systems that's supposed to download ANYTHING and just hope I'm not redirected?? I'm just so suck and Tues off this. I just need to search, make phone calls. I don't even do any social media any longer! Please, tell me what I can trust anymore??? And I'm just out another round it up to 500.00 and I'm in disability. I'm so disheartened and hopeless
Click to expand...
Click to collapse
I guess i'm kinda lost here at what you may be stating and or asking? what device are you needing help with? I do not have a samsung so i honestly can not be of much help other then to point you in the right direction.
If you need help with a stock image for the 100003562 i have one here.
Hello , i have a problem which occured from one day to another.My Shield TV was not booting. I tried to go to recvery and do Wipe and reset and it didn't let me.Then I tried with different recoveries from Nvidia , and still no luck.I went i tried it with this https://nvidia.custhelp.com/app/ans...hen-you-are-unable-to-access-android-settings I only got errors Failed to mount... failed to format I/O Error ... also mke2fs returned 1 .....failed to clear BCB message and so on when i start i see the nvidia logo and after a minute the android logo flashing slowly, but after that nothing more. Is my device storage dead???
Did you ever manage to fix the device? I got EXACTLY the same errors on my 2017 shield pro.
Unfortunately not. I ordered a new SanDisc memory and soldered it, but it didn't work. i Also found this site
Unbricking SHIELD TV (2015) with a Bootrom Exploit
Last year, a friend gave me his SHIELD TV when he moved. He worked at NVIDIA and got it for free and had used it only a handful of times before it traveled from his closet to my own. I had forgotten about it until I had a need for a Raspberry Pi and discovered that they were all still sold out...
yifan.lu
and talked to the guy about my atempt.He told me that the Storage chip is somehow bound, and I should try to dump something from the old chip to the new one. I can solder but dumping was to high for me.
You can check his site and try his method described there. I also asked him about which pin has to be grounded and here is a clearer picture than on his site. Good Luck !
Okay if you see APX that’s good because you can use the recovery tools worst case. However, if you have access to your old emmc still, you can dump it and copy it to the new emmc. Also know that the emmc contains per-device unique identifiers that are required if you use Netflix or any drm. If you flash someone’s else’s backup, they wont work.
If all else fails, you need to use the brom exploit and APX to run the recovery cboot and manually flash a backup that way. Not sure if that’s easier or harder than flashing the emmc externally.
Click to expand...
Click to collapse
Thanks for the reply! As fascinating as the linked article is, this is way beyound me. Also, thinkgs will probebly not be 100% the same as I have the 2017 model.
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 ?