I have been looking at the a500 forum for a few days now.
I have picked up a bricked a500 from a yard sale for pretty cheap. I have used many of the different guides on here was even able to boot up my old copy of Back Track 5 to get my CPUID.
when i turn the tab on nothing but the power light comes on the screen is dark and off there is no light comming from it.
when i do the manual APX mode it works and the PC can recongize it as such.
Im not sure but i have completely dissembled the entire tablet and found no burn outs or even any sign that it was ever taken apart before. The screen may be out but im not entirely sure. Now on to my issue every guide i use on the a500 forum works to some extent they all see it in apx mode they all successfully connect and start to load the .bct's (the vibration motor even pulses after the first success) and such but most stop working at initializing the bootloader and other various parts. The programs ask if i see anything on the screen but the screen is still off (by off i mean no back light or any indication of it displaying anything) i have shined a light at the screen to see if it was just the back light but in truth the entire screen is completely off.
im kinda stuck and not sure where to proceed i would like to use this tablet but if it is beyond me being able to repair it id rather take the small loss and not spend anymore time or money on it
any help would be greatly appreciated,
Thank you.
insta_gib said:
.....
when i turn the tab on nothing but the power light comes on the screen is dark and off there is no light comming from it.
when i do the manual APX mode it works and the PC can recongize it as such...........
any help would be greatly appreciated,
Thank you.
Click to expand...
Click to collapse
Go here, second post. Download TDV4 (Timmy Deans Rollback Tool). Unzip it to your PC. Run the PB.....exe file while using "Administrator Rights". In other words, "Run as administrator".
http://forum.xda-developers.com/showthread.php?t=2049778
Ignore all the stuff in the beginning, like looking for current image, etc. After a few minutes it will prompt you with a dialog to start your tab in APX mode, and plug it in. Enter CPID when asked, and hopefully it will finish. If it does, you should have a pre-rooted 3.2.1.
If it hangs for more than 15 minutes during the process, try it again. Also, I have a post with a link to another EUUS, for the A501. (don't worry, it will work on a 500). Sometimes must switch back and forth between the 2 EUUS files, until it completes.
What you have mate, is a corrupted bootloader partition. And unfortunately, there might be little to do to fix it. If you're lucky, like the rest of us, you can still run 3.2.1, but won't be able to upgrade to ICS.
Another thing you may try, if the above fails, it put the mainboard in an oven at 200C for 5 minutes (this is what I did). There's a thread here on that also.
MD
Moscow Desire said:
Ignore all the stuff in the beginning, like looking for current image, etc. After a few minutes it will prompt you with a dialog to start your tab in APX mode, and plug it in. Enter CPID when asked, and hopefully it will finish. If it does, you should have a pre-rooted 3.2.1.
Click to expand...
Click to collapse
I used the linux tutorial to grab my cpuid and it worked with no issues but when i put it into this program it says wrong cpuid and asks me to reset the tab and try again i will be getting on my linux machine after work to try again any insite you may have on this issue would help.
thank you
insta_gib said:
I used the linux tutorial to grab my cpuid and it worked with no issues but when i put it into this program it says wrong cpuid and asks me to reset the tab and try again i will be getting on my linux machine after work to try again any insite you may have on this issue would help.
thank you
Click to expand...
Click to collapse
make sure the first digit is 0, here is mine for example
038061c7409fa617
And should be the exact same amount (16)
Other than that, I don't have any idea.
Moscow Desire said:
make sure the first digit is 0, here is mine for example
038061c7409fa617
And should be the exact same amount (16)
Other than that, I don't have any idea.
Click to expand...
Click to collapse
Ahhhh. LOL i was doing the 0x and then without the 0x trying it now.
KingKwentyne said:
Ahhhh. LOL i was doing the 0x and then without the 0x trying it now.
Click to expand...
Click to collapse
Aha........
Yep, try it without the "0x". Now note that an SBK (secured bootloader key), demands the "0x".
Example: 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
Moscow Desire said:
Aha........
Yep, try it without the "0x". Now note that an SBK (secured bootloader key), demands the "0x".
Example: 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
Click to expand...
Click to collapse
So i have tried what you posted a few times. No luck it just hangs im going to try on my desktop at home and see if its enviromental. could you link the a501 and ill try it at home tonight and again. Thank you for all the help you have provided so far.
back from a long break of trying to mess with my Tablet. Still nothing i have tried has worked fully a few things have completed the flash with no visable result. Im not really sure what exactly is wrong with the tablet but i can enter apx mode with no issue what so ever but the screen will never display anything. there is no indication the screen was damaged but it is possible that it needs a new LCD i hope it dosnt but im starting to think the tablet works fine just the screen is bad. if anyone has had/recovered an a500 with an issue similar to mine any help on how you fixed the issue would be a great help.
Related
i was trying to update my acer with the V4 program from here: http://forum.xda-developers.com/showthread.php?t=1307539 to try to root it and i left my computer and the tablet on while i went and did something for 30 min because it was updating and when i came back my computer was off and my tablet was on the acer screen. i ended up turning it off and now when i turn it on the power light comes but it doesn't vibrate and the screen doesnt come on.
Can anyone help me?
mdillard1992 said:
i was trying to update my acer with the V4 program from here: http://forum.xda-developers.com/showthread.php?t=1307539 to try to root it and i left my computer and the tablet on while i went and did something for 30 min because it was updating and when i came back my computer was off and my tablet was on the acer screen. i ended up turning it off and now when i turn it on the power light comes but it doesn't vibrate and the screen doesnt come on.
Can anyone help me?
Click to expand...
Click to collapse
Looking at TimmyDeans thread, and in the instructions, it says, if it doesn't succeed the first time around, to repeat the process.
I hope you wrote that UID number down, just in case.
I have never used it, but, from what I have read in the thread, it is better to use a Win7 PC, rather than XP. Also, when you start the app, as with most Linux and Java, it is better to "right" mouse click the application file, and select "run as administrator".
Additionally, you may want to post this also, in TimmyDeans's thread as well.
Anyhow, I believe he says to restart both the PC and Tab, and start the process again. From what some users said, it may take several times.
Ok so I have been reading around and most of what I found about my specific problem (boot loop with never putting any custom restore or root or ANYTHING on it) was pretty much was useless. I am not a complete beginner I have put custom mods on many of my devices, defy, atrix, dell streak, ect, and I have used ADB among other things (not that I am a pro at it mind you!)
I realize theres a thread up for this here
http://forum.xda-developers.com/showthread.php?t=1356257
but I want to know if this will work or is for people WHO HAVE NEVER DONE ANY MODIFICATIONS TO THEIR KINDLE FIRE
If it is then I will give it a shot.
What happened is (to my knowledge) my daughter was playing with it, and the next morning, it was boot looping, and quickly. So when I turn it on, it shows kindle fire then goes black, then repeats or once in a while will make it to the slide to unlock but 2-3 seconds after goes black and continues the bootloop
ANY HELP GREATLY APPRECIATED!
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
AustinFire said:
I recommend giving Amazon a call and get the device replaced.... If you still have a warranty?
Click to expand...
Click to collapse
Why would I even try to fix it if I had a warrant? .... thanks anyways...
so ive downloaded the drivers and its basically not working, and the method for deleting the drivers (the one some idiot posted at least) will only work IF THE DEVICE STAY CONNECTED... Which it obviously isnt... and the 3-4 seconds of it saying KINDLE FIRE isnt long enough for me to find it in the device manager... by the time that updates its already rebooting...
so please anybody.... i dont understand why it would be so difficult.... I JUST NEED A RECOVERY I DONT NEED ANY OF MY STUFF
I have tried running ADB shell it says device not found....
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Ixthusdan said:
If it is a hardware problem, then flashing is pointless. It did this on its own. Processor or board issue. Given the variety of things I see posted, hardware is an issue at least 1/3 of the time, my guess.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
I would agree with you but i had installed some apps prior that seemed to make it glitchy and slow, and my daughter probably just triggered something (she is 3 and just constantly opens and taps things, i caught her in settings before) ... im pretty positive its software, especially since I read a few people with the same exact symptoms of mine... (it shows logo then reboots repeatedly, but sometimes makes it to the slide screen for like 4 seconds then it goes back to boot loop) Im sure I could fix it but I need help with getting my ADB in order or im screwed xD
I have also read several places that my problem could be fixed with a factory cable...
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Dead Battery
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
JimCo06 said:
Have you tried a hard reset (hold the power button down for 30 seconds then power back on)? That should clear any stuck apps. It also sounds similar to a low power boot loop. If you haven't tried charging it you might want to put it on the charger overnight and see what that does. Other than that I don't know why a stock KF would bootloop.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I have tried all of that, many times in fact. I also think its odd that it got stuck in a bootloop but from what ive read stock KF do that sometimes and its usually as simple as changing the way it boots which is why I think the factory cable is what I really need...
kinfauns said:
This is covered in a sticky post
http://forum.xda-developers.com/showthread.php?t=1623244
Click to expand...
Click to collapse
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Untraumatized said:
like i said... thats why i think i need a factory cable (fastboot)... but the problem here is i dont have a factory cable... lmao!
so basically im stuck at the fact that the drivers arent working, thus the KF is not being recognized, making fastboot impossible, or am i wrong? somebody please clarify...
Click to expand...
Click to collapse
You don't know whether or not your fastboot drivers are working because you must first put the device into fastboot mode to see if Windows will load the appropriate drivers.
Your problem is that on a stock device unable to boot into the system, 2 out of the 4 possible ways of putting the KF into fastboot mode are unavailable to you. The remaining options are to use a factory cable or to crack the case open to get access to the motherboard.
http://forum.xda-developers.com/showthread.php?t=1668159
There's another thread on the forums here about someone who disconnected the battery and hardwired it to a charger, but that seems like a really bad idea to me. A factory cable is your best/safest first step to getting out of your situation.
Hi all
Apologies at coming on here and immediately asking for help, but....
I've had my Nexus 7 since July and have been very happy until NOW!
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
I've tried all the methods of long push of buttons/multiple buttons/etc but to no avail.
I can bring up the factory restore option so I know I can get it working again, but....
I have an exam in a week which foolishly had work stored for on my n7 without back up (yes fool) so....
Please is there anyway to retrieve my files via PC etc before factory resetting
All help genuinely appreciated
Mark
rooted vs unrooted (or unlocked bootloader even if not rooted) makes a huge difference in the answer.
Please state which.
Sorry about that
Not rooted.
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
pleading said:
Sorry about that
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
Click to expand...
Click to collapse
I believe you are SOL in that case. Sorry.
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Sent from my Nexus 7 using xda app-developers app
bigbop said:
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Click to expand...
Click to collapse
pleading mentions the battery, but then says "stalls" - not "shuts down", which is what you might expect if the battery was drained:
pleading said:
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
Click to expand...
Click to collapse
But, bigbop could be correct if pleading meant "low battery shutdown"
One other very long shot - assuming that that the device is hung - is to see if either adb or MTP are available. Normally that happens very late in the boot & I have to imagine that he has already tried that though.
Hi again guys
Firstly thanks for not giving up on my situation!
Bad explanation by me I guess....
The battery went flat/dead (my bad)
Plugged in to charge and screen lit up again but showing the 'powering off' script
Left over night on charge, wouldn't switch on again next morning
Left on charge all day still no joy but if I try switching on whilst plugged in I first get the Google name, then the Google X but then gets 'hung' (probably a better description than freezes etc as it still pulsates the colours)
Only way to get out of this is to keep power button pressed which switches n7 off and starts the cycle again
If during the recycle I keep the volume down pressed then it accesses the option screen to recover/reboot etc
Hope this helps, and again thanks (desperate to recover course work)
Mark
Hi again
Update...
Battery is showing full now
But still same 'hung' situation
Regarding the 'ADB'
I can get to the 'apply update from ADB' option
And if I choose it states.... 'now send the package you want to apply to the device with "adb sideload <filename>"'
As always thanks for any help or suggestions
Mark
Mark,
It sounds to me like what you are describing is ADB in the stock recovery, not a ADB when the regular operating system is running. (Is that right?)
Unfortunately, the stock recovery is only good for 2 things: applying an OTA update, and doing a factory reset. Even if your tablet needed an OTA update (and it probably doesn't if it is up to date), it probably wouldn't fix the looping/wedged phenomenon: usually that is caused by stuff in the userdata partition.
Doing the stock recovery factory reset might cure the wedged/looping problem - but only if it wipes all the data from your tablet. (Including the /sdcard area too).
The only hope I held out was if your tablet was reachable via a ADB or MTP with the wedged operating system sitting there looping. Usually those facilities start up quite late in the boot sequence, however so probably you don't have that.
Sorry. I think you are still SOL when it come to retrieving files.
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
I had same sort of problem N7 went flat tried to charge but would not power on
Took back panel off and disconnected battery for 10 mins reconnected battery and put back on charge
it then booted up as normal
pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
Uhhh ... what?
The OP was about a tablet that you couldn't get into because
[a] it had a correctable soft-fault
you didn't want to exercise an available soft-fault recovery method because of a desire to reclaim user files not backed up
... and so far as we know the soft-fault recovery mechanism still is available to you.
How did that morph into "this is the end"?
You need to re-do your homework, perform a factory reset, and move on with your life.
You have used either software or hardware in the past haven't you? That thing isn't a toaster or a waffle-iron! No backups of important stuff? Come on!
OK, well then. Pack it up and send it to me with the charger and I'll pay for the shipping - UPS ground.
Doesn't the Nexus have a safe-boot mode?
Sent from my Nexus 7 using xda app-developers app
bigbop said:
Doesn't the Nexus have a safe-boot mode?
Click to expand...
Click to collapse
Just tried right now - held the Vol-down button down continuously from about 2 secs after the Google B&W splash screen appeared until the lock screen appeared. That worked. (Stock 4.2.2)
"Safe mode" appears in the lower left corner. I had access to all the market apps (that I tried), but did not see a toast notification from StickMount after the boot - suggesting that safe mode only inhibits apps from starting on boot.
I suppose this could work (although the OP's deadline has probably come and gone) for bypassing a hung boot - but only if the hang is due to a market app that normally starts on boot.
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
skalicioustimes said:
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
Click to expand...
Click to collapse
I would find the correct firmware for your tab (from the Samsung site) and reflash the full Odin tar. If that doesn't help I'd contact Samsung about the issue.
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
skalicioustimes said:
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
Click to expand...
Click to collapse
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Yes unfortunately the Tab 4 has been opened.
By disconnecting and reseating the battery sockets i believe the warranty is void. The back has been opened.
I find if i get the device running momentarily then by gently plexing "twisiting" the unit in my hands can cause the screen to switch back to normal.
But soon after the dreaded horizontal and vertical lines appear then the device becomes frozen again, the intermitent lines jump around the screen with whatever is in the background leaving the display frozen.
Only solution is to gently open up the device and disconnect the battery and then reconnect again.
This is only a temporary solution as the problem reappears very soon after.
moonbutt74 said:
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Click to expand...
Click to collapse
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
skalicioustimes said:
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
Click to expand...
Click to collapse
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
moonbutt74 said:
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
Click to expand...
Click to collapse
I'm unsure about your suggestions, as i don't know were to locate those commands.
I have done a factory reset, so i am just waiting for the device to charge before attempting to load new firmware through Samsung Kies which i downloaded through this link... http://www.samsung.com/uk/support/usefulsoftware/KIES/#versionInfo
are the commands you suggested within the Samsung Kies software?
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
moonbutt74 said:
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
Click to expand...
Click to collapse
When i was having the problems initially, i could not for the life of me get into recovery mode using the button combo's. Eventually i did get into recovery, so as a last resort i cleared cache, and done a factory reset. Now it is booting up as normal but i was going to use Kies on windows to see if it is a software issue.
So were do i go about getting
adb
logcat -d
mount
ps
dmesg.
And what would you suggest as a step by step guide from were i am at now?
Note: i haven't physically messed with the device to see if the Horizontal and Vertical screen issue is still there.
Thanks
XDA search bar
adb install
moonbutt74 said:
XDA search bar
adb install
Click to expand...
Click to collapse
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
skalicioustimes said:
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
Click to expand...
Click to collapse
You're not supposed to revoke adb debugging.
Look, i'm at a loss, the thing is, do you blow more cash on a quess, or cut your losses.
As to learning how to use adb, XDA searxh box, using adb.
m
not a bother.
thanks for your help :good:
skalicioustimes said:
not a bother.
thanks for your help :good:
Click to expand...
Click to collapse
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
moonbutt74 said:
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
Click to expand...
Click to collapse
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
skalicioustimes said:
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
Click to expand...
Click to collapse
dude are you on hangouts ? if so pm me.
moonbutt74 said:
dude are you on hangouts ? if so pm me.
Click to expand...
Click to collapse
sent you a message on hangouts. thanks
Flashed the stock kernel using Odin, i hope that gets rid of the screen issue :fingers-crossed:
Well 3 hours later and the Tab is going good
My daughter is delighted that it's sorted and she hopes it stays that way
Many thanks to Moonbutt74 for your time and effort, it's very much appreciated.
Would you say that it's good to go? And is there anything else i need to do to the device before handing it over to her?
Cheers
I think I'm bricked. My shield is stuck in a simple bootloop and should be considered a softbrick. I can't seem to get into fastboot. Forget adb, that's not responding, but I'm still getting the android boot logo. I've tried so many ways. Holding the button, mashing the bettenbetter, plugging at the brick, power at the console, just about everything. Anyone figure out how to get into fastboot with hardware? If so, please let me know or I'll be throwing this out. It just won't seem to respond to fastboot. Such a shame.
EDIT: Android figured it out somehow and just booted, but I'd still like to know how to get into fastboot for when I'm not so lucky next time. Or any other way to get into recovery.
EDIT 2: Thought I posted this in troubleshooting. My mobile data was lagging somethinf fearce. Sorry.
It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"
baileyjr said:
It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"
Click to expand...
Click to collapse
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.
kdb424 said:
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.
Click to expand...
Click to collapse
It certainly doesn't help that there isn't a physical button on the Sheild, so your not absolutely sure your pressing in the right place after re-inserting the power cable.
In my experience the whole button is sensitive, bit that's still a pain. I have no problems booting my phone to recovery or fastboot, but that's just nuts. Oh well. Hopefully teh learned something as I'm sure their techs are complaining too. It is a consumer device, so I guess I can't be too mad, but still, they expect us to reflash before an RMA when needed sometimes, and that's not fair to ask with thes device lol.
I have the same issue here. I was able to get in fastboot hardware wise a bunch of times before. Now I think the device is done. I've tried every combination. What's weird is I did get a flicker of the bootloader continuing once. What could have changed that the bootloader is not responding anymore? How did you get lucky, let it sit there loading for a day? I've tried to see if fastboot commands can reboot the bootloader when I plug it in timing it correctly. So frustrating.
Yesterday from many many trying times I did it only once and don't wanna go cross again and don't ask me how I don't know how and still don't know how. I did everything by "book/instructions" finally give up and just randomly (panicly ) pressing / holding finger on it, power on / off...and then somehow bootloader screen appear. That should be fix by Nvidia
Sent from my SM-G925K using XDA Free mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:49 AM ----------
I hope some developers out there will create some magic solution how enter easily in bootloader mode, like using micro sd ports some modded scripts or usb ports where in plugged in mode console entering bootloader mode or recovery etc.
Sent from my SM-G925K using XDA Free mobile app
Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.
mow4cash said:
Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.
Click to expand...
Click to collapse
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.
kdb424 said:
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.
Click to expand...
Click to collapse
Same here - finally haotic random pressing / unplugging and at the end done only once
Sent from my SM-G925K using XDA Free mobile app
Im also in the same boat
Just tried to flash stock 2.1 and Full android 2.1 and now the shield wont boot into anything
Im trying the hardware bootloader method but thats not working so far.........ive just unplugged everything, and giving it a while before i keep trying.........i suspect i might have to try rma......that'll be fun...........(im implying, that it wont)
Same here, mine is stuck on on screen and stating production fused , and couple of options like recovery kernel forced recovery, none works fallowed nvidia instructions , tried downloading SDKS And followed commands nothing working , as well tried holding power button , and unplugging and nothing works, I will try what you guys did and see maybe I get lucky somehow
I have a Shield TV power device but the screen is black and I can not go to the Hardw
I have a Shield TV power device but the screen is black and I can not go to the Hardware Bootloader Access:crying::crying::crying:
Same here - when I plug int he power the green light comes on for about half a second then goes off.
Quite infuriating really.
I get a screen that sasys "continue booting..." and then it loads normally do I need to let go once it says this or should I continue to hold?