Database Develop

can't rollback to get root

I'm not a total noob to rooting as I've already rooted my G1 and am running cyanogen's mods for months now. My problem is on a different phone.
This dream was dropped in water months ago (that's when I purchased my 2nd on craigslist). The touchscreen wouldn't work so I was stuck at the setup screen. I read on many forums, xda included that it might eventually dry out and today I found that it was indeed working fine.
It works fine on stock 1.5 ota update crc1 but now that I rooted one I want this one rooted as well. This is where my problem starts. I'm trying to rollback using the dreaim.nbh found inthe latest "how to root" thread in the dev forum. Problem is I can't load the image. I powe up holding camera and power button, get to the multicolored bootloader, insstructions on the grey/whitish screen say press power button to load, and then I am stuck.
Power button does nothing and the phone is stuck on that screen until I pull the battery. Been through this process 5+ times, with redownloaded image (file is not corrupt) My concern is Ill end up bricking but I really want root. I'm think their might be water damage on the phone but everything else works fine.
Any suggestions for a workaround or a way to troubleshoot the problem? Thanks in advance!
-Air

nbh
heres a link to where you can get the nbh dwnload this one nd try agian.
http://coolpstuts.blogspot.com/2009/07/all-download-links.html

no dice
pistol thanks for the try but it didn't work. same 87.3mb file, rc29, same result.
the greyish white screen loads, but the update (rollback) never starts. Does anyone know of another way to load the dreaim.nbh image? or heard a similar issue?

are you sure you grabbed the t-mo image?? go to the original how to root your phone thread and grab the t-mo image, nothing has changed so there is no reason for us to have an updated thread other than to confuse people even more

my problem is not the rc29 image
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.

Was not implying that this thread would be a how-to and confuse people, merely that we have so many and people are constantly asking how to do something even though the steps didn't change. The physical abuse your phone has sustained "should" have no effect on the image flashing. I would suggest you format your card again(not in windows as windows seems to screw up a lot), so long as you are using the correct image and a fat32 formatted card you shouldn't have any problems, does the screen pop up and say "no image found"

airmaxx said:
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Click to expand...
Click to collapse
hmmm, have you tried re-formatting your card?

trying it now
reformatted at home using gparted but I'll try paragon now that I'm at the office.
tubaking, thanks for the advice and willingness to help. it does not say no image found. It actually shows the steps that it needs to install including, radio_vz, and a few other things i cant recall right now...
hopefully the reformat will do the trick. I will try to format the entire card fat32 for now and then add my ext3 after. reporting back shortly....

still not working
so reformatted again to fat32, used paragon, gparted, and built in format on the G1 still the same result
grey white screen, reads the image.... then stuck at:
Code:
DREAIMG.nbh -
BOOTLOADER -
RECOVERY -
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_VZ -
Press power button
to start update image
Press action button
to cancel update image
and then I'm stuck

So even after you press the power button to start the update, it just stays at that one screen and never gives any "ok"s next to any of the listings?

exactly
no oks, just hangs there
I've been letting it sit since before my last post, about 45 mins so far and still nothing. I may have imagined it but when i did this process last week it felt like it was getting hotter, but still nothing happened
also I remember doing this on my other G1 that is already rooted, so I know how easy this step should be

Stupid question, but are you making sure not to rename the original DREAIMG.nbh to anything else other than what it is? Some people make the mistake of thinking they have to rename it to update.zip or make the mistake of not leaving it in capital letters (although I don't know if that matters). You have said you have downloaded the file multiple times so I doubt this is the case but I'm just spitballing here

no rename
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh

airmaxx said:
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
Click to expand...
Click to collapse
I wasn't suggesting to rename it, I just wanted to make sure that you never had renamed it to anything but the original filename DREAIMG.nbh

its all good
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!

airmaxx said:
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
Click to expand...
Click to collapse
I re-read your original post and was curious as to whether the power button could be the culprit considering that its needed to flash the image. Perhaps the water may have damaged the power button interface. I can't imagine that it would be the problem considering your able to get into the rainbow screen via power+camera. Have you tried pushing it harder, many times, on the side etc?

i did, tried holding it for a 10 count, multiple presses, long press. I'm pretty sure the problem is not with the button itself because it works fine when I have the phone booted up and press power to turn it off.
When I first posted I was hoping someone might know of an alternative button combo that might have the same effect of loading the image from that greyish white screen

there is no way to write the image through adb right?

Multiple questions, multiple problems, may be multiple cracks in my G1 after I throw

First off I would like to say that this is one of the best forums I have ever seen as the amount of support and helpful users and creativity put into these phones are staggering. I was going to go to Windows mobile for my next phone but I now doub it with this site or at least maybe I will dual boot.
So I am sure I am asking questions that have already been answered but my problems with the phone (USA G1) are many and the answers to some of the problems are so fragmented that I had at one point 14 tabs open for reference to solve just a few issues. I am 70% noob with the G1. I have had the phone for a year with no major issues just the annoying Force Close that seemed unecessary for the commonality of the app that had problems. Texts were annoying because I could not tell if they had been sent the previous day or recently as service at my home is come and go and my older Verizon phone had envelope information and even said if the person had read it or not so no annoying duplication. However, otherwise it was stable and would last about a day and a half with the double size battery.
Recently, however I had rebooted from the power button prompt and it got stuck (I can't remember on what screen) and figured installing a different ROM and other files would fix the problem. By the way, I had bought the phone rooted and I believe it was using JF 1.42 and a Cyagen mod (forgive my spelling). So I followed step by step from this forum the wiki on the lastest stable Cy ROM. I followed the instructions to the T.
Being new to the software, it was a slow process with a lot of repeating of steps discovering little details that were not mentioned like naming something update instead of update.zip like instructed or adding the .img as an extension. So I had nearly made it and then I came to the DangerSPL and other files to be loaded on the phone in order via fastboot. Despite, several attempts I could not get the skateboarding droids or the rainbow screen to come up so I finally decided to just continue as I had been using Amon-RAs 1.7 update zip feature to follow the instrucions and install the software in order. All was well until I got to flashing the actual ROM which said something about how it said the E: [insert file name here] was not correct so it aborted everytime but it did show some progress on the yellow bar.
Next came the issue of the G1 screen hanging up after the above problem and for some reason I could get to the 1.7 screen but only by holding the button required to access Amon RA longer than usual other wise it would say the build of Amon RA at th ebottom with no commands and the reboot itself or hold it longer and finally get to the Amon RA but it would not load my recovery files as I had made many along the way.
I nearly gave up but then came across this solution which worked by using method 1 at well I am not allowed to pu the websit in here but I am not allowed by the mods. but it is the 4th one down if you google "how to fix a soft brick g1" and the link is titled Unbrick - android-roms - How To: Recover your G1 from a bring ...However, it did get stuck at the rainbow screen as it finally let me do the fastboot and I saw the Androids skateboardig but it hung at the rainbow screen. It was here I noticed that my 32A phone was now a 32B. I took the battery out and powered it up and lo and behold it was asking me to put in my google information and I finally made it to the home screen.
I thought "Yes!". Now, I can try again since it will fastboot now which was what was recommended at the final steps but I was mistaken. I could not searc the market for common apps like wave secure and it frequently said it does not exist. I saw that my terminal app was gone and when I was finally able to download it from the market and my superuser app was gone and the termina would not respond as before to the input of SU.
Then, I noticed my phone's screen would randomly come on and only sometimes go off. When I pressed menu it was as if it the call button was stuck and it would either repeatedly bring up voice dial or call someone. The buton does not appear to be stuck otherwise. When it would briefly stop, acting like the call button was in turbo mode it would give me the option to mount the SD card as I had lost my micro sd card reader but never give me a chance to mount it before the call button interrupted with google dial or calling some number.
I do not believe this to be a hardware issue because as far as I remember the call button worked normally during the steps as it was requently used. So my questions, at the moment, are these:
1. How do I tell if the call button problem is a hardware or software issue?
2. Once I find my card reader and will I be able to use the factory bootloader to go through the updates.
3. Obviously I have derooted my phone (or maybe I can delete the diag from sd card and it will operate as it is derooted), will I be able to reroot my phone by using my backups of nandroid basically leaving me at whatever step I was on to the road of recovery?
4. How do I use my nandroid backup to recover especially if I am stuck with the factory bootloader?
5. I copied my SD card before I did the wipe originally so will I be able to find a .xml from handcent with my texts? (I text myself my mileage for work as with my hours, it is easier than using an app plus it saves space for other apps)? Should I load that backup nandroid first and start over?
6. Is there a quicker way to root like...a program?
7. What is your advice for the future other tha obviously backing up my texts more?
8. When did wave secure start costing money? I think I might have backed up everything a few days before the crash but I have no access to it now.
9. What other key combinations can I later use for the fast boot?
10. When formating the card to fat32 what allocation do you use and do you use quick format?
11. What is lost dir. and why is it empty?
12. In Amon RA 1.7 there are several caches which I cleard all of them when asked to clear the the cache in the wiki directions? Should I clear all of them and what are the seperate caches, espicially the davik one?
I am sure I am missing some question but I will post more as I try to follow your directions or attempt other methods. I apologize for the long, long story but I wanted make sure I did not leave out any detail so this can be resolved ASAP because I am sure I am receiving texts and calls and people are probably thinking I am ignoring them (no one leaves voicemails anymore so how can I know if they called or texted during the phone's sickness). I also apologize if I have broken any forum rules or posted in the wrong section or violated some. Thanks guys in advance. I miss the fat little thing so much.

Oh My god! Sorry but that's too long for me to read, my attention span isn't all that great =p
I will try to help with your questions but I didn't read the whole intro so my answers might be a little redundant.
1.Run "adb logcat" from a cmd prompt on your computer and see if pushing the button registers on the computer
2. um ok??? not a question
3. you will have to re-root but your backups will still be usable after you gain back root
4. boot to recovery (home+power), scroll down to backup and restore, select restore, and select the file
5. I'm not familiar with handcaent so can't offer help there.
6. It's not hard. Downgrade with DREAIMG.nbh to RC29, use update.zip to upgrade to 1.5, install one click root, use it, flash a recovery, and flash a rom.
7. You should write shorter paragraphs =p
8. Again, not familiar with it.
9. HOME + POWER, and BACK + POWER
10. No clue....
11. It's a folder automatically created when you don't unmount your phone before disconectiong the usb. It's useless and you can delete it.
12. When installing a new rom, just wipe everything. It saves you trouble later on.
Hope I helped...

Thanks I will give it a try later today and probably come back with more questions and longer paragraphs

[Q] Black screen of Death

Black screen of death. It's what I call it because that's all I get.
Here is a summary of what happened.
1) My Samsung Galaxy S started to get slower and slower. I decided to turn it off and back on (using
the power down button) to see if it would get any faster.
2) I would then only get the first start screen, then the graphic S screen after which it would go
blank (black screen of death). After about 2 min, if I pressed any keys, the two buttons on the bottom
would light up and stay on. If I pressed any one of them, it would go off and back on.
3) I could hold the power button and it would reboot.
So, that's were it was, here is what I have tried so far.
a) Check to see if I could get into download mode. Yep, that works.
b) Check to see if I could get into recovery mode. Yep, that works.
c) Hmmm, oh well, lets do a system wipe. Yep, can do that but it still would not boot up. I just get
to the graphic S screen and then the black screen of death.
d) Lets take the battery out. (over night) Nope, still black screen of death.
Based on the above, a flash should work right. Sorry, but I had a lag fix installed. Well no matter
what, I could not get the phone to boot so I guess I better try flashing anyway.
I've tried several images. Most of them get the error "your storage not prepared yet, please use UI me nu for format and reboot actions" OK, this is because of the lag fix. I then installed stzupy's image and that fixed the "your storage not prepared yet bla, bla bla. But still black screen of death.
I've tried flashing over and over, with pid 512, 513, 803. Nothing. I still come up the black screen of death.
So, can someone guide me in the right direction. I've done searches on this but everyone else seems to have had a different problem. Mostly doing a Factory Reset worked for them. I've done that over and over. After removing the battery, after flashing, before flashing. Nothing seems to get me past the black screen of death.
Thanks in advance for all and any help,
Jeff
p.s. Please don't reply with a message saying something like flash X's kernel. I need descriptive instructions such as flash with "this kernel" into CSC (or pda or modem) using XXX pid while checking repartion (or not). In other words, don't assume I know what I am doing. I don't.

there is now way you can save your apps installed but your sd card files will be there.
Only thing you can do is reflash my friend

webstar1 said:
there is now way you can save your apps installed but your sd card files will be there.
Only thing you can do is reflash my friend
Click to expand...
Click to collapse
Really don't care about my apps. (I have everything backed up onto my computer via Titanium Backup) But if you check my message above, I have reflashed until the cows come home. I still get the black screen of death.
- Jeff

Sorry Jeff Your Samsung Galaxy S is 'Proper F*cked Mate'
Yes sir I believe you are toast indeed! Your internal SD card is probably toast. I believe you're a fine Canadian of course assuming you've got the Bell i9000m? A lot of us have had this and there's a poll on it actually. Mine just toasted out about 2 weeks ago, thankfully i've an awesome friend in Canada on the forum that has helped me out!
No matter what you flash or try to do, it will not mount the sdcard in there or let you format it manually. You'll have to send it back to BELL or Samsung.

BA_Flash_GOD said:
Yes sir I believe you are toast indeed! Your internal SD card is probably toast. I believe you're a fine Canadian of course assuming you've got the Bell i9000m? A lot of us have had this and there's a poll on it actually. Mine just toasted out about 2 weeks ago, thankfully i've an awesome friend in Canada on the forum that has helped me out!
No matter what you flash or try to do, it will not mount the sdcard in there or let you format it manually. You'll have to send it back to BELL or Samsung.
Click to expand...
Click to collapse
Sigh! That's what I've been worried about. Yep, bell i9000m. Oh well, if I gotta, I gotta. Only 1 month old.
- Jeff

Flash stock, then give it back to samsung to repair, they should then
Sent from my GT-I9000 using XDA App

Had the same problem today. Wanted to change from JPA to JPO so thought it best to do a factory reset, but when phone booted up again, it started, then the screen went black with the occasional vibration. Tried all the usual things, removing battery & waiting, wiping cache etc., but no luck. Then put it in download mode & installed JPA again, but same problem on bootup. Thought I had finally managed to brick my phone (horrible feeling). So I solved it this way :-
Installed JM8 using .512 pit with repartition ticked, hooray my phone booted up again. The long delay after the S logo & finally completing boot was nail biting to say the lease. Now everything is working great & I am in the process of installing JPO.

[SOLVED][HELP]Soft Brick with stock recovery access

So I have done a ton of research on the subject since last night when I made the mistake of editing my build.prop file in the system directory to try and get Milk Music installed and working on my N6.
steps I took pre soft brick
made a copy of build.prop and placed it in my nexus 6 home directory
then went in to edit the file in the system folder
Changed the following
ro.product.model=Galaxy S4 (from Nexus 6)
ro.product.brand=Samsung (from Motorola)
ro.product.manufacturer=Samsung (from Motorola)
Saved the changes using ES file explorer with root access of course and went on to DL the milk music app from http://forum.xda-developers.com/showthread.php?t=2676662 which is the tutorial page to get this all working.
dl'ed the app got it open and got an error saying milk music is only supported on samsung devices so I didnt think much of it and went to copy the backup build.prop over to replace the faulty edited one currently in the system folder. did this, or so I thought and rebooted.
now I am welcomed with just the Google while letters and the unlock symbol at the bottom of the screen and it will not move on.
I can boot into stock recovery but I only have the stock.
I do have adb installed and it worked to unlock N6 bootloader but haven't used it since and I am currently out of the house till prob a little later in the day.
steps I have taken to attempt the (known fixes) have all been shot down by the fact that I can't get ADB working from my friends computer and I am not sure if it is the phone or lack of drivers (which does not seem to be the case) or me just being very noob when it comes to adk and android sdk anything. I have only used it once and that was about a week ago to unlock bootloader.
I wont be able to check this forum till I get home a little later but will update on the situation when I get there and can try to connect phone to my PC where everything has already worked before.
thank you all in advance for all the help

I got home to test some things and I have ADB access and have tested fastboot.
I tried a fresh flash with the guide located here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
had to do the long way like everyone else in comments was describing. everything went smooth no hiccups but still stuck on black screen with Google in white letters with the white unlock at bottom.
any input would be highly appreciated.

Just did the exact same thing I did in second post and went for yet another fresh flash and IT WORKED. got the spinning dots and after a bit ANDROID popped up and the initial welcome screen popped up.
Thank you guys so much for all your help. not sarcastic at all i promise. the guys who lead me to this fix are in so many different forums and threads and have no idea i was piecing it all together to get to this outcome, so to all of them and all of you who participate here on XDA thank you so very much.

I flashed one of the first ver of Android N. It was OK but I could not updated it go back or do anything. It also took root away and unlike M there were no setting to turn it on and I could not get it back. I tried every cmd and attempted to flash forward and back and root again. I finally got pissed and software bricked it. Again I tried everything I could find but when I ran NRT_v2.1.5.sfx.exe to my surprise on the first try it fixed it and I am at 6.01. <

Recovery Mode - what to do?

Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie

Sorry - one other question!
Which key is the "enter button"?

FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.

Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!

Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.

Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.

I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect

And that's on the charger it came with?
It's not looking good.

FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks

It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?

I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.

It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.

FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.

FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548

Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks

Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.

Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.

FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one