Database Develop

[Q] Need some help getting into Emergency - mode

Hello,
I just got my new Optimus 2x in.
After 2 days using it and draining a lot of battery life installing apps and getting the phone the way I liked it.
The LG apps installed on it started to annoy me bigtime.
So i did the most respectfull thing every tweaker does, i rooted the phone.
Installed the Titanium Backup software and started deleting LG apps.
The deleting part went perfect, then my screen turned black and the only thing working was the kill andriod app software on top.
So i pulled the battery and rebooted, nothing.... the phone got stuck at the LG logo.
Did a Hard reset Volume down + the power button.
It started the installation --> google login --> setting up extra account --> and then got the error about a wizard having problems.
So i guess my rom is corrupt.
Tried updating trough the LG software - emergency and got the message "not possible anymore".
Tried updating trough KDZ firmware update tool but it can not find the phone*.
*Downloaded the original firmware from a thread located here.
Does anybody know how to get in emergency mode so i can try different things.
Or maybe other options i could consider?
If not i'd might considering sending it in for warranty.
But it boots so there must be a way to get things working again.
Thx i appreciate getting all the help and ideas.

Im sorry to hear about your problem
Hope u can fix it
But may i ask how do u root it? I try z4root but no use...

heroddaji said:
Im sorry to hear about your problem
Hope u can fix it
But may i ask how do u root it? I try z4root but no use...
Click to expand...
Click to collapse
I rooted it with superoneclick.
--small update--
If i skip the setup part after my google login, i can force stop the wizard error.
But it does not go into android itself, i get the top bar but thats it.
The LG software recocgnizes my phone but says it's OK and it does not need a update.
Wait for android 2.2.3?
That might do the trick, but then i might have to wait more than 2 weeks

1.Turn the power off. If your LG Optimus 2X is frozen, pull the battery out and reinsert it
2.Hold the Home and Volume Down button
3.Press and hold the Power button until the device turns on
4.Follow the on-screen instructions to reset your device
That's the only option, on this time.

Tried this.
It says S/W Upgrade
Please wait
while upgrading...
and then nothing.

Try boot your phone to android then connect it to pc and run adb shell if shell working put all apk,s from rom dump here.
You have to copy all files to /system/app.

I'll give it a try tomorrow, have to get to work in like 3 hours =)
Im done for today.

Actually, if you get the notification bar, Android is working.
Sounds like you just deleted the Launcher, did you replace it?
If not, adb install and new launcher and you'll be good to go. Although you'll want one on your system partition too!
Have a look in the "Safe to remove" apps thread.

That's it, that's the one i accidently removed.
Any idea how to put it back on the phone?
As described above your post, trough ADB shell?
Can someone post LGLauncher in this thread?

FEARME said:
That's it, that's the one i accidently removed.
Any idea how to put it back on the phone?
As described above your post, trough ADB shell?
Can someone post LGLauncher in this thread?
Click to expand...
Click to collapse
Download here LGHome

Thanks i downloaded it.
But the thing is i can't run adb it gives me the error: device not loaded.
Tried installing the google usb drivers, gives me a no can do.
Another thing i figured out is this: Installing LG PC Suite IV.
It does give me the device connected, but i can not update.
* Can sync contacts
* Can sync Favourites
* Can sync Memo's
But no update (because it's not out yet)
Isn't there a way to fool the suite there is an update but in fact it's just the old firmware and replacing it (making it a repair).

This Thread is discussing the same problem as i am, btw

Fixed!
Obtained the LGLauncher.apk and emailed it to my google account!
Got it out of the above link i posted.

FEARME said:
Fixed!
Obtained the LGLauncher.apk and emailed it to my google account!
Got it out of the above link i posted.
Click to expand...
Click to collapse
Great, but you going to want to fix this problem:
FEARME said:
But the thing is i can't run adb it gives me the error: device not loaded.
Click to expand...
Click to collapse

djmcnz said:
Great, but you going to want to fix this problem:
Click to expand...
Click to collapse
as i said in the other thread you should use root explorer to copu the launcher to /system/app
if you dont it will be gone again if you ever factory reset.
And next time dont delete stuff... just freez it from titanium... Frozen apps are gone (cant be started by the system or seen in launcher) but you get them all back if you factory reset (so no risk of bricking)
OK... we dont get the few megs of free space by freezing... but that is not really an issue on this phone.

[Q] Please help me, is my phone bricked?

I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.

NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.

Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?

Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/

Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).

sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.

Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.

So, how did it go?

TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.

Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...

So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.

Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks

gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?

sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.

TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?

sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.

Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks

Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?

Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.

[Q] recover bricked Samsung ATIV Odyssey ? HELP !!!!

Hi all,
Wondering if anyone could help me. On the Samsung ATIV Odyssey I have, when it boots, it will show, Windows Phone, Samsung screen then just shows the spinning gears..this will go on forever. I tried to reset and "tried" to hard reset it but could never get the "!" To show up.
Is there any way possible to recover this phone or am I stuck having to send it out to Samsung?
I have not been able to get anywhere with this phone and can't find recovery software like Nokia has for their phones for Samsung models....
Thanks in advance!!
Can anyone help with this issue ?

I ended up calling Samsung, the phone is out of warranty (of course) but, they say they will do a free one time flash to attempt to recover the phone. The provided free shipping and will flash it and return the phone to me at no charge.
Nice, didn't know they offered that....

DavidinCT said:
I ended up calling Samsung, the phone is out of warranty (of course) but, they say they will do a free one time flash to attempt to recover the phone. The provided free shipping and will flash it and return the phone to me at no charge.
Nice, didn't know they offered that....
Click to expand...
Click to collapse
If 'someplace in CT' means 'quacche patte a Catania vicinu a fera o luni' we live in a similar place
Anyway you can get informed better here:
http://forum.xda-developers.com/showthread.php?t=2692049
Take a Flash tool. more infos here(the procedure should be the same for the odissey)
http://forum.xda-developers.com/showthread.php?t=2391138
You can try to flash the fake wolfROM with the customwolfROM.csc(or mbn, I don't remember) for Odissey (You'll find it in the first thread i've linked you)
OF COURSE FOLLOW THE GUIDE NOT TO BRICK MORE YOU DEVICE.
If you have any problems you can ask.

Thanks, does the Odyssey (SCH-I930) can be flashed with the roms for the ATIV S ? Interesting, If I can get this phone up and running again, I might try to go the ROOT route if I can. That is if it can be recovered.
2 computers would not even detect this phone because of it being a reboot loop. So even if I had a rom or something else for it, the computer would not even see it.
Not my primary phone, so no big rush if I have to wait for a week...

DavidinCT said:
Thanks, does the Odyssey (SCH-I930) can be flashed with the roms for the ATIV S ? Interesting, If I can get this phone up and running again, I might try to go the ROOT route if I can. That is if it can be recovered.
2 computers would not even detect this phone because of it being a reboot loop. So even if I had a rom or something else for it, the computer would not even see it.
Not my primary phone, so no big rush if I have to wait for a week...
Click to expand...
Click to collapse
NO IT CAN'T OF COURSE BE FLASHED WITH OTHER PHONES' ROMS BUT IF YOU KEEP READING ALL THE PAGES OF THE THREADS I'VE LINKED YOU YOU'LL LEARN THAT WOLF MADE OTHER CUSTOM CSCs(the smallest,editable part of a WP rom) SPECIFIC FOR YOUR DEVICE AND HOW TO FLASH 'EM
(I wrote with caps lock in order to let you get the importance of the point )
It's normal that every pc doesn't see your phone:something in its os is missing.I would advice you to flash another csc -description in this the customwolf rom thread I've already link to you -(see the specific combination of your model in order to know if your phone turns on in download modus and you can try to flash again it)
EDIT----
Sorry man,I just Thought now to it: You could simplify your life just trying first a Hard reset from buttons combination (I think this is the correct one,but you can search for yourself for the specific combination of buttons of your phone).
Alternate Method
Step 1
Turn off the phone and wait 15 seconds.
Step 2
Press the "Power" button. Press and hold the Volume Down button until an exclamation mark appears on the screen.
Step 3
Press the Volume Up button and then press the Volume Down button. Press the Power button and then press the Volume Down button again. The screen goes black and then the reset process completes.
In this way you should be able to HR your device without turning it on and risking to damage it more with flashing

gidannifico said:
NO IT CAN'T OF COURSE BE FLASHED WITH OTHER PHONES' ROMS BUT IF YOU KEEP READING ALL THE PAGES OF THE THREADS I'VE LINKED YOU YOU'LL LEARN THAT WOLF MADE OTHER CUSTOM CSCs(the smallest,editable part of a WP rom) SPECIFIC FOR YOUR DEVICE AND HOW TO FLASH 'EM
(I wrote with caps lock in order to let you get the importance of the point )
It's normal that every pc doesn't see your phone:something in its os is missing.I would advice you to flash another csc -description in this the customwolf rom thread I've already link to you -(see the specific combination of your model in order to know if your phone turns on in download modus and you can try to flash again it)
EDIT----
Sorry man,I just Thought now to it: You could simplify your life just trying first a Hard reset from buttons combination (I think this is the correct one,but you can search for yourself for the specific combination of buttons of your phone).
Alternate Method
Step 1
Turn off the phone and wait 15 seconds.
Step 2
Press the "Power" button. Press and hold the Volume Down button until an exclamation mark appears on the screen.
Step 3
Press the Volume Up button and then press the Volume Down button. Press the Power button and then press the Volume Down button again. The screen goes black and then the reset process completes.
In this way you should be able to HR your device without turning it on and risking to damage it more with flashing
Click to expand...
Click to collapse
Thanks again for your help here !!!!!!!!!!!!!!! The hard reset is not working. I tried this MANY time before posting (after about a day playing with it, at the point of giving up hope). I can try the key commands but, at no point will I EVER see the exclamation mark. No kidding, I must of tried this 40 different ways, with different timing, I can 100% confirm that something is screwy with this phone.
If I do the Power plus volume down (to try to get the exclamation mark), as soon as a let go of the power button and holding the vol down, the phone will go in a reboot loop.
The phone does not get to a point where the PC will detect it, it will start to boot up and it will show on the display Windows Phone, then Samsung logo, then it will just show the spinning gears(like it had a failed update). It does this for ever (I let it go 24 hours before pulling it). I can do the soft reset but, that is it...
It's packed up ready to go but, I'll hold it for a day, do you think I could actually recover this phone with a rom ?

DavidinCT said:
Thanks again for your help here !!!!!!!!!!!!!!! The hard reset is not working. I tried this MANY time before posting (after about a day playing with it, at the point of giving up hope). I can try the key commands but, at no point will I EVER see the exclamation mark. No kidding, I must of tried this 40 different ways, with different timing, I can 100% confirm that something is screwy with this phone.
If I do the Power plus volume down (to try to get the exclamation mark), as soon as a let go of the power button and holding the vol down, the phone will go in a reboot loop.
The phone does not get to a point where the PC will detect it, it will start to boot up and it will show on the display Windows Phone, then Samsung logo, then it will just show the spinning gears(like it had a failed update). It does this for ever (I let it go 24 hours before pulling it). I can do the soft reset but, that is it...
It's packed up ready to go but, I'll hold it for a day, do you think I could actually recover this phone with a rom ?
Click to expand...
Click to collapse
I really don't know because I don't have the phone in front of me,so I can't 'think' to anything.
I just know that People flashed the custom csc..who knows,that could be Your solution-but could be not-.
I recommend you to read very well and many times the procedure.
Good luck and let me know.

gidannifico said:
I really don't know because I don't have the phone in front of me,so I can't 'think' to anything.
I just know that People flashed the custom csc..who knows,that could be Your solution-but could be not-.
I recommend you to read very well and many times the procedure.
Good luck and let me know.
Click to expand...
Click to collapse
Yea, I tried everything I could find in google and Bing...No luck, I'll send it back to Samsung to see if they can recover the phone....
Thanks again for your help. When I get it back, if it's running, then I will try to interop it....

DavidinCT said:
Yea, I tried everything I could find in google and Bing...No luck, I'll send it back to Samsung to see if they can recover the phone....
Thanks again for your help. When I get it back, if it's running, then I will try to interop it....
Click to expand...
Click to collapse
You're welcome
When the phone will be perfectly working you 'll be able to interop it with wolf's custom csc (the thread I've linked to you)
Cheers

BTW, I have the custom rom for the Odyssey, its definitely got some odd bugs.
Verizon stores can reflash it for you too for free, just need to hit up a Verizon CORPORATE store. Apparently they have the tools and the ROM, instead of waiting for it to be mailed and come back.

Well I used the wolf custom rom and follow the exactly instructions but my phone now say is corrupted, and instead of boat show me a message telling me that!
So, I got another one and now has the same problem, so, somebady knows if there is at day an original rom available?

Still no public Odyssey ROM yet.

Please help me with problem

Hey guys since the last rom i've installed ...it's a rom my own edition
m having this trouble shot in everytime i restart my phone
it says : the process com.android.phone has stopped unexapctedly please try again
look in the uploaded image please help me
i tried reflashing the phone then reflashing the rom i tried wiping data i tried factory reset but non of those methode worked for me please guys m begging for help

farrouk said:
Hey guys since the last rom i've installed ...it's a rom my own edition
m having this trouble shot in everytime i restart my phone
it says : the process com.android.phone has stopped unexapctedly please try again
look in the uploaded image please help me
i tried reflashing the phone then reflashing the rom i tried wiping data i tried factory reset but non of those methode worked for me please guys m begging for help
Click to expand...
Click to collapse
This issue cannot be solved by Reflashing ROM by wiping data (experienced )
jerry.goyal said:
i just went through this problem on my bravo so i want to share the solution.
actually i searched the XDA but didnt get the solution.
"think again before going to hard reset or clear cache, there might be some easy ways to get rid of it "
i got this message whenever i receive a phone call.
This error message is a common complaint among Sprint users, but it can easily be removed by taking the following steps:
method #1
1. From the Home screen, hit the Menu key.
2. Tap on Settings.
3. Select Call settings.
5. Select Reject with message.
6. Count how many messages are in this section.
7. Delete them until you have less than five.
After reducing the number of messages to fewer than five, you should be able to receive calls without an error message compelling you to force close the call.
method #2
Something I've also had to do to get the phone working again was going into the 'manage applications' screen and clearing the data for the phone application. This can be accomplished as follows:
From the home screen, press Menu
Tap Settings
Tap Applications
Tap Manage Applications
At the top, tap the All tab
Navigate to and tap your equivalent of the phone app (may be called Phone or Dialer)
Tap Clear Cache and Clear Data as available
Turn your phone off, then back on.
Another means of resolving those app errors, hope this helps!
method #3
didnt work above methods? strange!! hmm
100% solution
1.go into recovery
2. go to wipe/format option
3. clear cache
4. hard reset( not necessary,try only clear cache if works)
5. reboot.
Click to expand...
Click to collapse

thnx
crazysuraj said:
This issue cannot be solved by Reflashing ROM by wiping data (experienced )
Click to expand...
Click to collapse
but non of this methode had worked i tried them alll please any other methodes??,

farrouk said:
but non of this methode had worked i tried them alll please any other methodes??,
Click to expand...
Click to collapse
well, for now, I have no other methods...
But, it may be okay... This error shows once on restarting the phone..
Solution is not to restart phone without any cause...

farrouk said:
Hey guys since the last rom i've installed ...it's a rom my own edition
m having this trouble shot in everytime i restart my phone
it says : the process com.android.phone has stopped unexapctedly please try again
look in the uploaded image please help me
i tried reflashing the phone then reflashing the rom i tried wiping data i tried factory reset but non of those methode worked for me please guys m begging for help
Click to expand...
Click to collapse
to only know what cause of that problem is the logcat. so you can know that cause the android.phone crash. maybe png or what you can provide logcat here also so we can see and to help you with your problem.

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