So I just thought id let everyone know what I did. I was trying to get the semi-new "YouTube 360" to work with my fire so I decided to change the build.prop to a Google nexus 7. Now before you come after and tell me I'm stupid I had done this before on my original kindle fire and 360 was working but only with touch because the gyroscope is kinda wonky. But I was running a custom rom for my kf so what I think the difference was that it took out all the Amazon info like os version etc. Because I was messing around with other stuff before and it didn't do anything. Anyway my fire is now stuck in a boot loop with a black screen. If anyone knows how to restore my build.prop file I will literally sell you my soul.
Related
Hi Everyone,
I searched and read many threads but didn't see my problem listed. I apologize if it has and I missed it. I received a Kindle Fire for Christmas yesterday. I plugged it in and let it reach a full charge. I then went through the registration steps. Upon completing registration, it automatically went to an updating screen. I left it alone to finish updating. After returning over an hour later I find it stuck on the "kindle fire" black screen. I've tried many hard resets but it always boots to the same black screen.
As I mentioned, it was brand new and I did not attempt to do any rooting or custom installs. If I plug it into my computer, Windows XP recognizes a device but does not having any drivers to install for it. Is there anything I can do to unbrick it?
Thank you in advance.
if u didnt install any roms like cm7 or havent even rooted it yet then its probably a hardware prob.. Try holding down power for like 20 secsand see what happens
Thanks for the suggestion movieaddict, but I've tried that many times now and it still just brings up the kindle fire screen.
Not as helpful as I would like a post to be, but I've had it freeze on that screen a few times as well and a hardware reset has always fixed it. If you have not rooted or done anytthing to void your warranty I see no reason to not contact amazon customer support as it is their problem to fix and hopefully they can, or get you a new one in a hurry. Good Luck, I know this is frustrating, my first one had a flickering line on the lcd and had to be rma'd.
Sent from my Epic (sleeper rom) using XDA App
Thanks Kapurnicus. I've already placed a called to Amazon and they are sending a new one and it should arrive later this week. I just thought I could play around and possibly fix this one in the meantime.
I don't blame you. Might as well try. Sorry I couldn't be of more help, mine is still stock lol. I only screw with the phone for now. Just have a new launcher and some streaming apps on the kindle, although, I still love it. Haven't put it down in days. Its going to be your best friend lol.
Sent from my Epic (sleeper rom) using XDA App.
Ok guys, i need the experts here. I just received a N7 tablet today off Woot.com for my wife for Christmas, so i unboxed it and turned it on.
Booted no problem and then i put on the charger. I turned it on because i wanted to install her games she plays on her phone so come
christmas day when she unwraps it the thing is ready to go. Well i left on charger and came back a few hours later and was prompted to install
OS update. I said to my self cool, no big deal. tapped it and it asked to update so i confirmed. The N7 shut down and loaded up with our favorite
little android with his chest cavity open for the world to see while he made himself better. But after some time he fell over and said ERROR!! i
said aw crap, and left it alone because i have seen this happen on my old HTC evo before and the phone recovered no problem. So i left it on
that screen and after a while the device did restart i thought ok good. But then it just got stuck on the Nexus loading screen, stayed on that for
about an hour before i started to get worried and looking online for help. Seems others have had this issue but i have not seen it on these
forums, although i did not look very hard either. So after reading and reading some more i went into bootloader and factory reset which did not
work. just stuck on nexus logo. i tried to install the update though the ADB sideload but always got an error saying invalid signature verification
failed. after reading some more found out the bootloader is locked and wont accept anything not signed. So i tried googles offical updates off
their site.Still got that error. Now i have looked into unlocking/rooting but you have to turn on USB debugging and also you seem to have to know
what version of android was on the device to start with which i never got a chance to look at. The website says it comes with 4.1 upgradable to
4.3. I have spend around 4-5 hours trying to get this working and i hope with the help of the people on here i can get it working so it can be a
great gift. If only i had gotten it from a store i could return it and have another one ready to go by the 25th but i know woot wont be fast to
exchange or asus if i have to go through them. Any and all help would be appreciated and thanks in advance for it. I am sorry i wrote so much.
N7 - android version----- unknown. possibly 4.1
Gen 1 or 2012 model
32 gig
wifi only
Try downloading Wug Fresh Toolkit. I used to use it all the time when I'd soft brick my Nexus 7 2012. It's a really simple tool to use and takes a lot of the guess work out of the equation. Should restore your device to stock, and it'll download whatever version of Android you specify for it.
If it works, I recommend going back and taking another crack at using ADB commands in the future, so you have a better understanding of the program under the hood. But for right now just get it up and running and ready for your lady to open on Christmas... Or at very least get it sent back in and get another.
Sent from CAMACHO, my Verizon G2 (VS980) running PAC ROM.
well using that tool seemed to make the problem worse. Now the bootloader wont even load up. When tablet turns on it says boot failed in the top left hand corner and the google name is shown. in the top right corner it says start and i can use the volume keys to go up and down to select recovery mode, power off, start, and restart bootloader. but always come back to same screen with the google logo where it just says google in white. What else might i try?
Hello, I have been given a nexus to try fix, Its one of the older style ones 7 inch i think with only front facing camera and wifi only, It seems to have an intermittent problem powering on, I've checked and rechecked all hardware so think now maybe its some software problem as the owner has tried to root the device unsuccessfully and i think flashed wrong ROM,
Is there anyway i can restore the device and possibly even root it for them at the same time without being able to boot into the device and see build version etc, I am able to get it to power on eventually but takes some playing about removing battery a few times till it decides to boot but once its on it stays on but cant access anything as it just keeps constantly throwin up the same error sayin "Unfortunately the process com.android.phone has stopped" and i can close them all fast enough to view anything in the tablet,
Any help here would be great, Im guessing i just need to flash the correct ROM plus whatever other files are needed the ODIN/USB way, Im just not sure what files to use for this device, Think its Grouper
Anyone any ideas how i can fix this?
Did I post in wrong section or something, ?? :-o
campbell4tec said:
Did I post in wrong section or something, ?? :-o
Click to expand...
Click to collapse
just need someone to read over your post is all & give a response ... Sounds like an app/service is crashing, best thing to do is hook it up to a pc an play around with the Nexus Root Toolkit, if you can boot the N7 you can fix it with that program, just make sure your comfortable with that level of modifications, with that tool you can do just about anything with your N7 sorry but it doesn't sound as if you have much knowledge of the working of the N7, I only mention it an suggest you do a lot more research before fixing what is a simple fix in the grand scheme of things of what could be wrong.. Don't forget the make sure its got a decent charge before "flashing"... for the power on issue, just pull the back plate off an unplug the battery cable "carefully", and then pop it back in making sure its in even, flush an all the way.. good luck :good:
Ok I just managed to really screw up my nSATVP last week by basically deleating the bootloader from my Device.... Why did I go and, do that for? You ask. Well thats 'cause I signed up for nVidias Beta Test Program for v5.0.1 which hasn't been released yet. And like always TWRP choked on it, and the Shield couldnt install the OTA. So in a fit of desperation I decided to stupidly downgrade it back to v3.3.0. which resulted in the Black Screen of Death. Though as a consolation I still had Fastboot, at that time.
In any case I managed to recover my Shield, via the SSD Conversion Thread(s), where someone was kind enough to post the needed start, and end bins which can then be copied to the SSHD/SSD. Of course this comes at a cost. You loose Netflix, and of course Amazon as well... Some People have likened this to be down to the ESN (Netflix: Electronic Serial Number).
Having a bit of a nose 'round... I'm inclined to think its more down to the lose of Widevine L1.... At the moment I only have L3 access. And, I'd be willing to jump in a fire at this point as the cause.
What I was wondering was it it could be possible to copy the missing /data/mediadrm/IDM1013L1 Files back from a working Shield TV?
I was hoping you'd get a response.
I lack the technical know how to find a solution to this. But I do have a 1st gen shield running that start and end bin files, and I (stupidly) tossed the original Shield drive before finding out Netflix and Amazon would be broken.
I've done a fair bit of reading and have yet to see a fix, or really anyone working on one.
Would love to have my 1st gen Shield able to work with Netflix and Amazon once again.
Well my understanding on this matter is that once you lose Widevine L1, than that's it! The only way to get it back would be to send it back to nVIDIA (Or hereafter The Factory), and let them to reset it. As only the Factory can install either L1, or L2 Widevine. Widevine L3 (The lowest level DRM Setting), however can be installed pretty much by anyone. As unlike L1, and L2 which are Factory set. L3 is Field settable, so we're just SOL.
Perhaps I might try contacting nVIDIA at some point about what it would cost to fix this outside of warranty. My only fear is that it would likely be the same price as a new Shield.
So the plan (for me) right now is to just suck it up, and lay some money again to the side, and pick up another Pro, down the line. And than strip the SSHD, and create the start, and end bin, backups, and than make multiple on, and off site copies of that. Than most likely, as not resell the broken Shield TV on FleeBay. To recoup some of the loss.
The morale of the story here is if your going to root, and install TWRP on your Shield Pro. You should first make the appropriate backups, and for the same reasons. It's rather disappointing in hindsight that all the How To's out there never bother to mention it. There are plenty of veiled threats about downgrading the Shield. But, bricking the Shield TV that way is way to easy. Easier than it should be.
wikkid76 said:
I was hoping you'd get a response.
I lack the technical know how to find a solution to this. But I do have a 1st gen shield running that start and end bin files, and I (stupidly) tossed the original Shield drive before finding out Netflix and Amazon would be broken.
I've done a fair bit of reading and have yet to see a fix, or really anyone working on one.
Would love to have my 1st gen Shield able to work with Netflix and Amazon once again.
Click to expand...
Click to collapse
Ichijoe said:
Well my understanding on this matter is that once you lose Widevine L1, than that's it! The only way to get it back would be to send it back to nVIDIA (Or hereafter The Factory), and let them to reset it. As only the Factory can install either L1, or L2 Widevine. Widevine L3 (The lowest level DRM Setting), however can be installed pretty much by anyone. As unlike L1, and L2 which are Factory set. L3 is Field settable, so we're just SOL.
Perhaps I might try contacting nVIDIA at some point about what it would cost to fix this outside of warranty. My only fear is that it would likely be the same price as a new Shield.
So the plan (for me) right now is to just suck it up, and lay some money again to the side, and pick up another Pro, down the line. And than strip the SSHD, and create the start, and end bin, backups, and than make multiple on, and off site copies of that. Than most likely, as not resell the broken Shield TV on FleeBay. To recoup some of the loss.
The morale of the story here is if your going to root, and install TWRP on your Shield Pro. You should first make the appropriate backups, and for the same reasons. It's rather disappointing in hindsight that all the How To's out there never bother to mention it. There are plenty of veiled threats about downgrading the Shield. But, bricking the Shield TV that way is way to easy. Easier than it should be.
Click to expand...
Click to collapse
I'm trying to locate the partition containing the serial number.
If any of you guys could post me an output of the nct partition, it would be a help hopefully.
Extract it using this dd command:
Code:
dd if=firstpart.bin of=nct.bin skip=20480 count=4096
Substitute "firstpart.bin" with whatever your bin file has for a name.
Ok heres the nct.bin File you asked for. you can find (I think... according to my Hex editor on Linux), the S/N @ Offset 040014.
Please note that since I can not post *.bin Files to this Board I took the liberty of simply renaming it *.zip instead.
SO PLEASE REMEMBER to rename this back to *.bin. Before you start looking at it.
BTW: Assuming your going to do what i think your going to do with this how would you re-insert this again?
To the File which you (or I), ripped it from, or to the SSHD direct?
Thanks
Hello, first post here, somewhat of a noob but not completely. Please tell me if I am using the wrong lingo on specific things.
Fire os 7.3.2.2
I am looking for information on the locked rom of the 10th. Gen hd 8, a have read quite a few threads from the past two years asking if there is a proven method to get in but I couldn't find anything promising. I did run across this one website that claims it is simple, just unlock the bootloader first.https://www.rootingsteps.com/root-amazon-fire-hd-8-2020/
Of which I can find no information on how to do. There is an "oem unlocking" switch in developer options but it automatically goes to "off" after clicking it on and selecting "ok" on the device protection pop-up.
I also am aware of the 8th gen method and i have the back off my 10th but it is completely different.
I am willing to help any way I can, that being said though if everyone has given up on these I could buy an 8th. but with the sale amazon has the newer one is almost cheaper than a used 8. If anyone is interested I'll upload pictures of the circuit board, there is no clock pin marked but I would think it is still there, and I will try shorting it to ground, and if it lets the magic smoke out I'm sending it back to amazon lol. If it makes any difference I don't need to save anything that is on the tablet now, it's new, never account linked, or connected to wifi and I'd be fine with completely wiping the fire os and everything, if there is a way to load linux.
My goal is to load linux mint and run it as a touch screen "laptop" to use as a digital dash with Tuner Studio on stand alone efi on a "race car".