Related
Hi guys,
I'm not new to the xda forum, used it for ages for bits of info and things and as a result successfully rooted an Orange Barcelona and an Alcatel One, but the problem I have has made me sign up to ask
My A500 was happily playing some music in my bedroom while I was in the bath, when I came out it had switched itself off. Odd I thought, so I tried to turn it on and it got stuck with the flashing android logo. Again odd, so I attempted a reset, same thing, tried a factory rest and got a bootloader error, poo I thought, must have done some wierd update and broke its bootloader.
So starts an ENTIRE day of searching the xda forum looking for a way to unbrick the thing.
So first thing, do I have APX mode - yes.
Do I have an SBK and UUID - no, thats a problem.
So, i've been through ALL these threads, meticulously...
http://forum.xda-developers.com/showthread.php?t=1829731
http://forum.xda-developers.com/showpost.php?p=23783875&postcount=9
http://forum.xda-developers.com/showthread.php?p=32464439
http://forum.xda-developers.com/showthread.php?t=1585907
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
http://forum.xda-developers.com/showthread.php?t=1998650
http://forum.xda-developers.com/showthread.php?t=1762991&page=2
Blackthunders flash tool causes the tab to disconnect and doesn't flash.
V8-UNL-ICS-HC-bootloader-MULTI-cwm generates an error (usb write fail) and causes the tab to disconnect.
I've determined that SBCALC is not generating the correct SBK from the UUID generated by eppeP's apx code. I compiled it several times on a 32bit Ubuntu 13.04 system and again on an 64bit Ubuntu 13.04 system altering this line of code to reflect the relevent OS
printf("uid: %#016lx\n", *(uint64_t*)data);
In one of the threads i found eppeP had offered three versions. The 32bit lines generated UUID's that were too long, the 64bit line generated the correct length but caused the flash tools to fail. I've tried omitting the preceding 0x SBKCalc says check CPUID or just leaving off the 0, that gives me an SBK but still causes the tools to fail, so again, I think it isn;t generating the correct SBK or the apx tool by eppeP isn't retrieving the correct CPUID.
Throughout the whole day I managed to get the tab to factory reset ONCE, got it to boot, got as far as entering my WIFI PSK then it crashed and went back to 'i'm not going to boot so nah nah' mode.
So status is, tab powers and hangs with the Acer logo, and still has APX mode available.
What, if anything, can any of you wonderful people offer as a next step short of calling Acer Monday and paying silly amounts of money for them to unbrick it. (Amusing anecdote, this is my second A500, it was a replacement for a unit I sent in for repair which came back bricked BY ACER.....)
I'm tearing my hair out now, so help greatly appreciated.
Wee update,
Successfully got a working CPUID and SBK by building eppeP's Visual Studio project, had to update it to VC++2012 libraries as I have Visual Studio 2012 Ultimate through my university.
Trying to flash now, so far I've got a wee message saying nvflash started and nothing else, been sat for a good 2 minutes, is it supposed to go faster?
Kess_Tacy said:
Wee update,
Successfully got a working CPUID and SBK by building eppeP's Visual Studio project, had to update it to VC++2012 libraries as I have Visual Studio 2012 Ultimate through my university.
Trying to flash now, so far I've got a wee message saying nvflash started and nothing else, been sat for a good 2 minutes, is it supposed to go faster?
Click to expand...
Click to collapse
Do u have an apx device listed in device manager or safely remove Hardware icon???
I'd say you'll need to d/ babsector.rar to reset yr partitions. Usually its the only thing that works when yr tab has spontaneously bricked itself. You can get the file and instructions from post #2 of the root guide n my sig...probably the only thread u never posted above
good luck
dibb
Sent from my GT-I9300 using Tapatalk 4
All good with device manager, device is seen ok.
RIght, with BabSector, I get failure to read/write mass storage (code: 9) nverror: 0x8 (0x19000008).
I believe this indicates a physical problem with the internal sdcard requiring a motherboard replacement.
Well, that sucks but I've had this two years so I guess it's had a fairly decent run
Kess_Tacy said:
All good with device manager, device is seen ok.
RIght, with BabSector, I get failure to read/write mass storage (code: 9) nverror: 0x8 (0x19000008).
I believe this indicates a physical problem with the internal sdcard requiring a motherboard replacement.
Well, that sucks but I've had this two years so I guess it's had a fairly decent run
Click to expand...
Click to collapse
I got around this very same problem with Timmy Deans solution. Because of the bad blocks of memory, this was the only way I was able to solve. I don't remember which bat file I used. There were two, depending on whether you were doing single or dual partition. But the limitation was that BCT partition that was being format was larger than available. Once I used his script it worked and my brick A500 is still working well today.
EDIT: @Kess_Tacy
could try contacting acer...someone else just recently had some joy with them. They paid shipping both ways and repaired for free!! Worth a shot
Plot: I have a Nexus 4 with a broken nand memory, I bought a £32 nexus 4 16gb from eBay with a broken glass and broken digitizer, I replaced the motherboards and voila, I have a working Nexus 4 and a device with a broken digitizer that won't go pass boot.
So, my "broken" nexus 4 doesn't have a working touchscreen, nor a NAND memory, but what it has 2GB of RAM and a nice processor it's the ability to boot an image with Fastboot, eg: I've booted stuff like Clockworkmod Touch Recovery or TWRP Touch Recovery.
What I would love to do is to boot a Linux version on my broken nexus and use it as a web server, or other stuff like ... display my CCTV cameras, since the display still works...
I tried multiple ARM variants, and the closest I got was with distro.ibiblio.org/tinycorelinux/4.x/armv6/piCore.gz . It was the only image small enough to download via fastboot, but... it's stuck at booting, probably I need to do smt else for it.
Has anybody got any tips for me? Anybody tried it before?
My plan would be:
1. Boot successfully any linux kernel
2. Buy an OTG Y cable to connect an external HDD.
3. Create a linux image that would boot from that external HDD
4. Control my new "linux server" via SSH
Hope this post will get some attention, I think it could be a nice thing for old unused phones as well as phones with broken displays that nobody took the time to repair.
tcr92 said:
Plot: I have a Nexus 4 with a broken nand memory, I bought a £32 nexus 4 16gb from eBay with a broken glass and broken digitizer, I replaced the motherboards and voila, I have a working Nexus 4 and a device with a broken digitizer that won't go pass boot.
So, my "broken" nexus 4 doesn't have a working touchscreen, nor a NAND memory, but what it has 2GB of RAM and a nice processor it's the ability to boot an image with Fastboot, eg: I've booted stuff like Clockworkmod Touch Recovery or TWRP Touch Recovery.
What I would love to do is to boot a Linux version on my broken nexus and use it as a web server, or other stuff like ... display my CCTV cameras, since the display still works...
I tried multiple ARM variants, and the closest I got was with distro.ibiblio.org/tinycorelinux/4.x/armv6/piCore.gz . It was the only image small enough to download via fastboot, but... it's stuck at booting, probably I need to do smt else for it.
Has anybody got any tips for me? Anybody tried it before?
My plan would be:
1. Boot successfully any linux kernel
2. Buy an OTG Y cable to connect an external HDD.
3. Create a linux image that would boot from that external HDD
4. Control my new "linux server" via SSH
Hope this post will get some attention, I think it could be a nice thing for old unused phones as well as phones with broken displays that nobody took the time to repair.
Click to expand...
Click to collapse
Sounds like an interesting project, but why not you just replace the phone? Google will accept your phone (even if you didn't buy it from them) in almost any condition and give you a replacement if you call them (85583NEXUS is the number)
If you are really interested, I was able to get a 3.6 kernel running on my galaxy nexus about a year ago by building it myself. Any prebuilt images will surely not work. Even though I got the kernel running, it was basically worthless as I did not have any mechanisms of controlling it, you could try configuring it to boot from your hard drive to get an SSH session running.
How come you didn't go through warranty for the initial NAND issue?
That said, you might be able to modify a ramdisk to point your partitions to those on a usb disk (of course with an otg capable kernel). Or perhaps you could look into multirom/kexec hardboot, and be reliant on the initial fastboot boot just to kick that into action. Multirom bases off twrp though, so that'd be hard to execute without a working digitizer. If anything, you could branch off that idea (if you can't manage to directly tweak your ramdisk to mount everything off a usbdisk)..
If anything, see if it's google would replace the phone for the bad nand. Swap the board back.. Then you'd end up with "just" a back digitizer and be in a much better position.
ziddey said:
How come you didn't go through warranty for the initial NAND issue?
That said, you might be able to modify a ramdisk to point your partitions to those on a usb disk (of course with an otg capable kernel). Or perhaps you could look into multirom/kexec hardboot, and be reliant on the initial fastboot boot just to kick that into action. Multirom bases off twrp though, so that'd be hard to execute without a working digitizer. If anything, you could branch off that idea (if you can't manage to directly tweak your ramdisk to mount everything off a usbdisk)..
If anything, see if it's google would replace the phone for the bad nand. Swap the board back.. Then you'd end up with "just" a back digitizer and be in a much better position.
Click to expand...
Click to collapse
I don't think google would have accepted it because:
- NAND Memory failed 99% because I flashed Franco Kernel's nightly version every... night.
- Obviously the phone's bootloader was unlocked and for some reason I haven't managed to lock it
- The back was cracked
I guess I can use my working version to play around with the kernel till it does what I want, I'll look into multirom/kexec. Any idea where can I get a good OTG Y-Cable. I've seen some, but I want to go for one proven to work well.
Bleh, there are times when I'm testing some code and end up flashing boot 100 times a day.
ziddey said:
Bleh, there are times when I'm testing some code and end up flashing boot 100 times a day.
Click to expand...
Click to collapse
Yeah, me flashing may not be the reason, however, my phone had the back cracked and a bit of the middle line damaged, so I bet nobody would have fixed it on warranty. I got really cheap and fast getting a replacement on ebay with a broken screen and do the swap, I posted two images below to show that the nand was really just... write only (is).
i.imgur.com/2VrVw6U.png - Via LG's Own Recovery Software (I know the DLL is wrong, but it's supposed to work) // i.imgur.com/SJDmTk9.png (Via Fastboot)
Sorry for not being able to post images, still have to go up to 10 posts. I've been quite selfish so far and only got info from XDA, promise if I will get anywhere with this threat I'll make a tutorial of how to do it and an example of a useful thing you can do with a broken phone .
==============
Anw, back on the subject, can anybody help me with how to install MultiBoot on a USB Stick? I would assume the things will go as follows: Have some magic on the USB stick, have a boot image that boots from there (via FASTBOOT) ==> multiboot boots my desired OS from the USB stick as well.
not sure what you're doing there for the second picture. Looks like some sort of script..
first pic looks fine. It's supposed to only get to 85%.
As for multirom, it's on you to learn how to create a ramdisk->boot.img that will mount usb partitions instead of mmcblock.
ziddey said:
not sure what you're doing there for the second picture. Looks like some sort of script..
first pic looks fine. It's supposed to only get to 85%.
As for multirom, it's on you to learn how to create a ramdisk->boot.img that will mount usb partitions instead of mmcblock.
Click to expand...
Click to collapse
It's supposed to get to 85% and restart. However it does not, I restarted it manually into bootloader, and tried to use flash-all.bat from the flashfactory for my model.. and then I get all of those write errors (as before) (that was a try to flash a custom recovery with Nexus Toolkit, I tried it manually). As a note, erasing all the partition works, formatting emmc partition obviously doesn't, formatting ext4 partitions: starts creating the filesystem, the partition is sent and then ... BOOM failed flash write failure as when I am trying to flash anything else.
As for the ramdisk and all, I shall use my medium Linux experience to dig into that and I'll let you guys know if I will get anywhere. For now I'm doing my best to make my own Y Cable ... this will be tricky.
Thanks to all of you who support my post, it's really cool to find a place where I can talk about stuff like this. I really hope if I manage to get somewhere I will make a tutorial that will help someone to put their old/bricked phones to good use.
For the last two weeks, I've tried pretty much everything I can think of to get my TPT booted again. Symptoms of its current illness include:
Lots of error messages when booting into CWM recovery ("E:Can't mount /sdcard" for example)
If I attempt to boot normally, I get stuck on the Lenovo logo screen.
Randomly I'll boot into CWM recovery and get its logo on the screen, and a line of text, but no menus.
Other times I'll attempt to boot into CWM recovery, and just get a blank screen
So last night I used nvflash to put a new CWM recovery into partition 6: after which I was able to boot into CWM with no errors. (Yay) However, when I tried to reinstall CynogenMod (whose zip file was sitting on my external sd card), it hung during the installation. I rebooted anyway; this time it got as far as the CyanogenMod spinning logo and hung there. I went to bed, and seven hours later it was still spinning away.
Then I rebooted into CWM (without errors) and managed to install CM ROM this time also with no errors. However, again I can't boot. I get as far as the Lenovo logo, and if I boot into CWM recovery I have all the mount errors again.
Along the way I've erased the cache; done a factory reset, etc.
So: nvflash, new CWM recovery (but still errors), reinstalled CM ROM, but can't boot into it.
Any suggestions? Has this machine packed it in - is its hardware faulty in some way? Or is there something I could try which I haven't already?
Thanks folks - I think I've reached the limits of my fixing ability, and would be very gratefiul of some advice.
Thanks again,
Al
In CWM check to see if your /System folder is mounted with read-write privileges or only with read-only. If the former, then your bootloader may have locked itself. Also, what is your device model? If you have a have a US device then it cannot be unlocked as it has been encrypted by Lenovo...
Sent from my ThinkPad Tablet using Tapatalk
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
amca1960 said:
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
Click to expand...
Click to collapse
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
eKeith said:
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
Click to expand...
Click to collapse
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
amca1960 said:
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
Click to expand...
Click to collapse
No offense intended but you are somewhat peculiar as you are familiar with NVFlash, can determine which partitions to flash with the correct images but you don't have a record of, or can't find your device's model number? Check on your SD Card port flap (or your invoice). Then check out this page for details.
However if you decide to replace the motherboard then search eBay for "thinkpad tablet motherboard" and choose either of the 1838 or 1839 options. Any will fit and work but you probably won't get your (non-US) choice of replacement motherboard so will probably just have to get what's available.
See here for some basic dis-assembly instructions. Then just take you time and the rest will be obvious. Good luck!
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
amca1960 said:
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
Click to expand...
Click to collapse
No problem at all.
"I'm in the same boat": I replaced my motherboard with another US version about 6 weeks ago, rooted, installed CWM recovery and steady so far... "with fingers crossed"...
Let us know how it goes...
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
chas0039 said:
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
Click to expand...
Click to collapse
With format+download make sure preloader is not checked....
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
chas0039 said:
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
Click to expand...
Click to collapse
If you had a Prime version and it was within the first 30 days of purchase, you could've send it back to Amazon to get a replacement, no questions asked, for free (this only works once by the way). Either way, glad to see Blu is willing to fix our mistakes. Maybe request that your R1 is restored with older, non-6.6 firmware. Probably won't work, but it's worth a try.
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
yaconsult said:
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
Click to expand...
Click to collapse
My guess is, they will load it with the factory shipped image, unless QA loads the update during testing, but perhaps they wont.... Kinda like a roll of the dice on this one...
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
This is why I just paid the extra $50 and bought the ad free version. $110 is still a great price for the device, and no hassles with any ad removing nonsense
mrmazak said:
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
Click to expand...
Click to collapse
Im sorry for the delay, ive been trying to drop a transmission into my car but I'll try to get a list together for you tonight. I did some manual tinkering with my scatters and frankenstein work with file lists so i'll need some time, but ill get back to you when i can.
I wish I have seen this before bricking mine......
How did you brick it? I have rooted and twrped two of them now without any issues. What did you do that people need to be careful to NOT do?
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