Related
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?
Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.
Hello,
I am a newcomer to the Forum and I would be grateful if I could benefit from the experience and the knowledge of the experts.
I have an unlocked HTC G1 phone. I use the ATT network.
I would like to install Gingerbread.
Could somebody give me the direction where I would find a step by step guide to replace my actual Donut version with Gingerbread.
Here are the specs of the phone:
Model number Android Dev Phone 1
Firmware version 1.6
Baseband version 62.50S.20.17H_2.22.19.261
Kernel version 2.6.29-00479-g3c7df37
[email protected]#19
Build number DRC83
well if its a dev phone it should already be rooted so ignore those steps, check and see your radio/spl (power on holding camera button)
your answer here will determine the next step
chances are you need to follow this link _ http://forum.xda-developers.com/showthread.php?t=831139
once this is complete follow the steps here _ http://forum.xda-developers.com/showthread.php?t=882356
if you need more help let me know!
Thank you very much for your reply.
Unfortunately my knowledge in this field is infinitesimal small.
That is why I am looking for a step by step guide.
Maybe I put myself in the wrong forum for my level and my needs. My apologies.
The only thing I know is that my phone does not need to be rooted.
Thank you again for your advice and your time.
Happy New Year to all of us
if your not finding what you are looking for ill see what i can do
first off i need to know your radio/spl - this will help me determine what you need to do next
just type in everything off the screen that will be rainbow colored or have three androids on skateboards
to check the screen, power off your phone, then hold down the power (red button) and the camera button at the same time. tell me what it says...
after you write all of that down press the green, red and menu buttons all at once and the phone will reboot normally.
gunner1937: There is a link I found in another thread for an older version of ROM Manager which will work on Android 1.6. Since you're rooted with a Google ADP phone this might be all you need. But I would go in the menu and do a factory reset.
I upgraded my T-Mobile G1 from stock Android 1.6 to CyanogenMod 6.1 (Android 2.2.1) three days ago following the instructions on http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
I will stick with it for now. It came bundled with the ROM Manager app.
In the past week I've researched upgrading to Gingerbread and just recently there may be a bug uncovered where the phone no longer goes into Deep Sleep mode. This means the battery usage is not ideal compared to other earlier ROMs. It turns out virtually all Gingerbread Dream ROMs use some code by ezTerry, so they may all have this issue. So.. I think I will hold off on going to a flavor of Gingerbread until I get more info on this possible bug.
In your case I believe I'd do the factory reset, then load this ROM Manager onto it. You'd need to copy the ROM Manager.apk file to your phone's SD card. I would backup the contents of your SD card onto your PC just so you have any files/songs you want, and then format it with FAT32. You can format the SD card from a Settings menu on the phone if you like. I think there's another setting in the menu to allow installing a program from unknown sources. Find that and check it in order to be able to manually install an app like this. Or I dunno, that may not be in the ADP phone. Next you'd need to get on the Android market and get a file manager to be able to dig into the SD card's file directory and install the APK file. I used a text editor called TxtPad Lite which included a usable file manager. Another one is called Astro File Manager. With something like that you can browse the file system to be able to look at the files on your SD card and install ROM Manager. You'd just find the APK file and tap on it.
So then you're reset, got the ROM Manager app that will work on Android 1.6, then you can use it. You want to let it install the ClockworkMod Recovery first thing. It's required and what the app uses to manage installing your ROMs. I myself have never actually used ROM Manager to install a ROM (I did use it to install the ClockworkMod Recovery). I've gone in and out of the app. It asked me to update it, so I did. And I decided to stick with CyanogenMod 6.1 for now. It looks like it's gone through a ton of vetting to get it really honed.
I kind of wanted a more full introduction to flashing the ROMs and stuff and the CyanogenMod guide was great for me. This looks like a relatively painless and less complicated way to safely upgrade and switch out ROMs for you, and I might've done it more or less this way if I'd discovered it first.
Thank you.
HBOOT: 0.95.0000
Radio: 2.22.19.26I
CPLD4
Personally I would recommend you install froyobylaszlo
But anyways, first of all before you start installing the 2708+ kernel, you're gonna need fastboot and adb on your computer
What OS do you have on your computer?
one laptop is Vista and the other is Win7
JediDwight said:
In the past week I've researched upgrading to Gingerbread and just recently there may be a bug uncovered where the phone no longer goes into Deep Sleep mode. This means the battery usage is not ideal compared to other earlier ROMs. It turns out virtually all Gingerbread Dream ROMs use some code by ezTerry, so they may all have this issue. So.. I think I will hold off on going to a flavor of Gingerbread until I get more info on this possible bug.
Click to expand...
Click to collapse
If you are not testing it this is a bad conclusion:
*) Deep sleep may or may not be working.. this has mixed results but the device is mostly sleeping.. so yes if completely idle (ie no cell network no wifi, screen off, no services running..) you might go from 4days uptime that the system currently gets even with an sdcard to 5 days if the problem if it exists is solved
problem is deep sleep is when the ARM11 CPU is turned completely off (it is going into low speeds correctly, and disabling other hardware into low power modes) This means when you are using the phone this state will not be entered (and thus the phone uses the same power as it is now) when a service is actively running.
Thus most peoples battery enhancements in GB are from the new APIs to allow applications to stay in the background more in Gingerbread; and a much larger problem is many applications these days are running more services than the G1 can support thus the system is constantly swapping in and out applications from memory.
Thus those whose battery on gingerbread roms is draining fast will more likely benefit from checking what is running in the backgound than waiting on a deep sleep fix if its even a problem.. since the services will still run after any fix and the battery life won't improve.
What the op needs is the 2708+ radio/SPL (that others are helping with) than nandroid in recovery can be used to switch between roms; since it provides more ram to CM5/CM6 and gingerbread roms all work with the 2708+ combination then the op can pick what works best for them in a more overall evaluation... and not just what lasts the longest when not used as a phone.
To OP:
the best way to continue is to:
1) Install fastboot (and the sdk) on your computer. you will need to search for this since the since I don't know the details for windows
2) If you already have a custom recovery (clockwork or ra-recovery) continue; otherwise you will need to install one: http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
3) then since you have HBOOT: 0.95.0000 install 1.33.2003 from: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76 this will allow fastboot and let you continue with:
4) Then the installation section at: http://forum.xda-developers.com/showthread.php?t=831139 (The files section will have the various files required and older roms that have been ported to work on the new SPL/Radio.. newer roms mostly will work per instructions on the rom's thread) .. read the entire post before doing anything.. as this is a major change to the phone, and the actions to fix something if you run into a problem may be slightly different than they were with more stock roms..
Try to get a feeling for what is needed before you begin .. we know its a bit of an involved process.. but most users have auctioned this in smaller steps originally.
(Note the cmwiki will probably be the best way to install recovery)
forum.xda-developers.com/showthread.php?t=910008
Download the drivers only pack
I think it includes fastboot
I can't check, if not tell me and ill upload my files as soon as I can get to a computer
search in google (or probably even xda) for "easy fastboot" if your having issues using fastboot, its exactly that an easy way to use fastboot for noobs.
also you can flash your new radio/spl as well as your rom via recovery, it isnt recommended but it can be easier if you have issues. ill tell you i have done it this way many times and have yet to brick a phone but as always my experience dosent me you will have the same. so try to follow the suggested route of fastboot is best.
upgrading to Gingerbread
I should have taken a longer rest.
I am starting the New Year with the feeling that everybody gets the right to flame me: my G1 does not work after a very bad step.
I installed on the re-formatted SD card 2 files namely DREAIMG.nbh and cupcake.
In short, I got the message "E: cannot open /sd card /update.zip (no such a file or directory). Installation aborted".
The next step was to sign my google account. It failed.
At this stage I cannot format, read, transfer, and use the SD card because it is not recognized by the computer. And of course the phone is not working.
Right now the G1 shows in the colored bars:
DREA100 PVT 32B
HBOOT- 0.95.0000
CPLD-4
RADIO- 1.22.12.29 (before doing anything to the phone the radio was 2.22.19.26I)
This phone was unlocked and set on the AT&T network.
Thanks to my wife Nexus One I can use, format, transfer files (which I did, to no avail) by inserting my SD card in her phone.
The least to say is that I really need the help, knowledge, and assistance of the Forum members.
What you don't want to hear is we see no error in what you have described. > well apart from the nbh file used it may be the original way to root but its not the easiest.
The message you are seeing in recovery is not am indication of a problem.
Ok, 0.95.0000 has no fastboot and thus you really need a custom recovery, to do that you. Need to flash it from the rom after rooting it, this means you need to try and boot the phone normally and log into Google normally.. if this fails try the following:
A.) go into recovery (home+power) and press alt+L then the combo to wipe the phone
B.) If its still not working try re-flashing the nbh
Oncce logged into google the telnet trick can work..
C.) While it needs a bit more setup, this third option is easier to install the 3rd party roms without a Google login and manual flash of recovery from system: make a goldcard ( you can do this on the n1) then put the orange nbh from the 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139 this can be renamed DREAIMG.nbh and then be flashed with the gold card you made. (There are many guides on making the goldcard for HTC phones) Once flashed you will have a fastboot enabled spl that will let you flash anything by fastboot.
Thank you for helping me to breathe a little bit deeper, better, and slower.
So far I am in the same situation.
Dropping by BestBuy I found an SD micro with an adapter. It makes life easier for everybody.
I did again what I started, trying 2 different downloads of the .nbh file. Still locked at signing my google account.
Following your advice I will try to create a goldcard and follow the procedure you mention this evening.
Wait...locked at signing in to google account?
What do you mean? It shows google sign in but you can't sign in?
Do you not have a data plan?
If so, just google "activate g1 wifi"
Sent from my Gingerbread on Dream using Tapatalk
gunner1937 said:
Thank you very much for your reply.
Unfortunately my knowledge in this field is infinitesimal small.
That is why I am looking for a step by step guide.
Maybe I put myself in the wrong forum for my level and my needs. My apologies.
The only thing I know is that my phone does not need to be rooted.
Thank you again for your advice and your time.
Happy New Year to all of us
Click to expand...
Click to collapse
I'm on my phone so idk what link he posted.. but if you got the G1 development section.. look for a thread titled G1 rooting,unrooting and more or something like that by ldrifta, then look around on that thread for a gingerbread ROM
Sent from my T-Mobile G1 using xda premium
ezterry said:
What you don't want to hear is we see no error in what you have described. > well apart from the nbh file used it may be the original way to root but its not the easiest.
The message you are seeing in recovery is not am indication of a problem.
Ok, 0.95.0000 has no fastboot and thus you really need a custom recovery, to do that you. Need to flash it from the rom after rooting it, this means you need to try and boot the phone normally and log into Google normally.. if this fails try the following:
A.) go into recovery (home+power) and press alt+L then the combo to wipe the phone
B.) If its still not working try re-flashing the nbh
Oncce logged into google the telnet trick can work..
C.) While it needs a bit more setup, this third option is easier to install the 3rd party roms without a Google login and manual flash of recovery from system: make a goldcard ( you can do this on the n1) then put the orange nbh from the 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139 this can be renamed DREAIMG.nbh and then be flashed with the gold card you made. (There are many guides on making the goldcard for HTC phones) Once flashed you will have a fastboot enabled spl that will let you flash anything by fastboot.
Click to expand...
Click to collapse
I am still trying to create a goldcard with the nexus 1. I cannot install a driver for it, I cannot install a driver from HTC sync, I get a message that "the device is not connected" but I can see the microSD on the computer.
This is where I am. And I do not know anymore what I have to do next since I feel I am in front of a wall.
frankdrey said:
Wait...locked at signing in to google account?
What do you mean? It shows google sign in but you can't sign in?
Do you not have a data plan?
If so, just google "activate g1 wifi"
Sent from my Gingerbread on Dream using Tapatalk
Click to expand...
Click to collapse
I did not express myself correctly.
When one reaches the sequence to sign into a Google account one has to enter email address then password.
I did that and few minutes later I got the message it could not reach the google servers.
Also, I have -rather had - a wi-fi connection since I got the G1 in December 2008.
gunner1937 said:
I did not express myself correctly.
When one reaches the sequence to sign into a Google account one has to enter email address then password.
I did that and few minutes later I got the message it could not reach the google servers.
Also, I have -rather had - a wi-fi connection since I got the G1 in December 2008.
Click to expand...
Click to collapse
There's your problem...
Wifi is off when you first turn on the phone
wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection
Use that guide to turn it on and sign in
And if you don't want to download the entire sdk just wait until I get on my computer and ill upload just the files you need
But tell me if you still need the files or not...I don't wanna upload for nothing
And if you can't get the steps right, I can try tell you more stepbystep instructions
Sent from my HTC Dream using Tapatalk
wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection.
Thanks for the link.
I cannot take advantage of it: Device manager shows 7 Intel ICH* universal controller, 1 USB composite device and 7 USB root hub.
Nothing else.
No USB mass storage device.
Android SdK is installed on C: but I do not know if it is properly installed or activated because I could not check "adb devices"
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
My Touch Screen DiED!!! (A Sad Story that Ends Happily)
I have flashed many a rom on my N910T Note 4. But yesterday I thought I'd update my TWRP install, and elected to use the new TWRP app to do so. Right TWRP file (double-checked). Fired up the app... and apparent success. On reboot, however, what looked to be
*DISASTER*
I touched my screen but nothing happened. Then I moved my finger and something elsewhere than under it opened up. In short, the sensors had become non-calibrated - they no longer properly detected where on the screen I was touching. The fact they did at all was better than nothing... but not much.
First, then, I did at least have some ability to still do things.
Second, better, I found that the s-pen's sensors worked just fine! Boy, was that helpful when it came to trying to type in my pin number / password.
Third, initial looks on the ol' google revealed people saying I'd have to buy a new sensor for the touch screen. Arrrgh!!
BUT THEN THE GOOD NEWS... I HOPED!
I discovered a number of folks suggesting what sounded almost James Bond-ish... a code, input into the phone touchpad, that when "called" could result in a calibration reset. Over and over again, there it was:
=================================
"dial *#2663# and update the touch FW by pressing TSP FW update (General)"
=================================
Okay, said I. Tried it from my new TWIZd rom. But no love. I got an error message. But then it occurred to me to read the many posts on this code more carefully... and sure enough, they did suggest that using the OFFICIAL rom provided by Samsung/my provider was necessary. Sigh... that meant navigating TWRP -- which by the way was also affected by the bad calibration. It was doable... just... by figuring out where my touches were actually activating the screen (it was less severely affected at the top but very severe near the bottom). Eventually got the phone wiped (Thank God I had just backed up my sweet TWIZd install to the ext sd card!). Luckily, I had a generic old copy of my phone's original rom on the ext sd, though it was one that had been debloated and rooted. I hoped it would work....
The flash hung. Forever. heading for 20 minutes. Finally I pulled the battery, not hopeful, and restarted the phone. *WHEW* it came up with the rom installed. Skipping both google and samsung installs, I went right to the Home screen and used my s-pen to type in the code then hit the call key.
Up came a screen of buttons, including a greyish TSP FW update (General) button. (See pics; neither is a Note 4 but both give accurate idea of what the screen looks like when the code given above is dialed in and works correctly.)
I tapped it with the s-pen.... and my screen was fixed!!
I made sure to use TWRP to backup that generic rom to my 128g external sd card - that way if this happens again I can "restore" it via TWRP and repair the phone quickly.
One thing is for certain... I sure appreciate this community of folks, which is where I found much of the info. And I will not be using that TWRP app (created by commercial interests anyway) again. Back to installing TWRP the old way, via either a *.tar TWRP file and ODIN via a PC or via flashing an *.img file w/ TWRP itself.
That's my story and I'm sticking to it.
Hit thanks if you found this amusing / helpful / or just plain odd.
Hi,
SO...I am pretty much in the same boat you were... but I have not been able to get the dialer thing to work...
when I type it in, it just flashes something to fast to see.. and then says "MMI complete" .
So far the ONLY thing I have done with this phone is root it (using Odin and chainfire) ... and install the wrong TWRP ... and then install the correct TWRP.
As far as I know, I still have the original ROM on it! I had not gotten to the point putting a rom on!!
Any suggestions?
Thank you for any help...
Thanks Shonkin, this worked for me on my SGN4, after flashing the bootrom with a Vodafone stock image.
Much appreciated