Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Conrad-007 said:
Hello everybody,
I bought the Nabi 2, as refurbished, for my little child and from the beginning I am having problems to turn it on or wake it up from sleep. It is not rooted, has everything stock and I have also applied all available official updates (OTA).
The problem is to turn it on, both from sleep or from powered down state. For example, being in sleep mode (display off) for a few hours, to wake it up I have first to press the power button for about 10 seconds, than release it and press again until... the start up Logo appears, as it was completely shut down! Maybe through pushing the power button first time I turn it off unintentional, so the second time it has to power up and load the OS? But just pushing the power button shortly will not wake it up at all from sleep mode... Is this a known problem and is there a solution for it?
Thanks in advance for each advice!
Conrad
Click to expand...
Click to collapse
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
aicjofs said:
The only semi known issue I have seen is when you put the tablet to sleep and it's charging. In some instances the tablet will lock up at some point after going to sleep. When you try to wake in up via power button it is locked up. When you hold the power button for 10sec you are hard powering it off and then it reboots. If yours wasn't charging then I haven't read much about anyone having a similar problem.
Click to expand...
Click to collapse
Thanks for your reply, aicjofs.
In my case it happens always, no matter if charging or not... and it's annoying.
Would rooting and installing a custom ROM solve the problem? If yes, is there a custom ROM dedicated to kids, similar with the stock one?
Conrad
Wrong Section Buddy !!!
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
and why ???
StariX37 said:
Wrong Section Buddy !!!
Click to expand...
Click to collapse
:thumbdown:
Ignore this guy. I have a friend with the same power on issue with her Nabi 2, and I'm interested to read the solution here.
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Conrad-007 said:
...no other hints concerning my problem ?
Please, if somebody has an idea, just reply here.
Click to expand...
Click to collapse
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Conrad-007 said:
I'm still struggling with the random problems on my Nabi...
Is it possible to check the integrity and/or health of internal memory, find and mark bad blocks, etc. using a computer (Windows or Linux) connected through USB? If yes, how? Do I need to flash TWRP or something else on the Nabi before?
Thanks in advance for your help.
Conrad
Click to expand...
Click to collapse
The latest TWRP should have a section under the wipe menu where you can repair the file system which is probably easiest, although you need to be careful what you are doing in there as it is called the "wipe" tab for a reason. Should be able to go to wipe menu, select data partition checkbox, select change or repair filesystem(don't swipe to wipe, click the words check/repair etc) and select check in the next screen.
To do a filesystem check the partition can not be mounted so you do it from recovery not in Android. Since stock recovery you can't use ADB you pretty much need TWRP one way or another.
If you don't want to use the graphical interface in TWRP you can do it over USB with ADB and use e2fsck on the partitions after unmounting them, but it's going to be doing the same thing you will just see a more verbose version if you do it over adb.
Thanks a lot, aicjofs.
I will try to root and install first TWRP, as my Nabi is still untouched.
One thing I remarked: at the moment, when I go in the (stock) recovery and want to do a "Wipe data/factory reset", 2 lines are displayed before "-- Wipping data...": "E: missing bitmap stage_empty (Code -l)" and "E:missing bitmap stage_fill (Code -l)". After that, the wiping process seems to run normal, as I get the message "Data wipe complete." at the end.
Do you know what that lines are meaning? Could those lines help to debug the main problem ?
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Conrad-007 said:
Update: NO WAY to get TWRP on my Nabi, regardless how hard I try...
NabiLab 2015 recognize the Nabi without problems, but as soon as I select "Recovery installer", Nabi should reboot-bootloader (I suppose), but hangs at Nabi Logo (the small icon in the middel of screen) forever. Also in Control Panel, the device is shown as ""Fastboot" with the error symbol and the indication that the driver should be installed again (but of course, when I try to do it, Windows tells me that the newest drivers for that device are already installed).
I also tried with using directly adb in a cmd window, with the same result, as soon as I type "adb reboot-bootloader" and press enter.
I am really out of ideas...
Click to expand...
Click to collapse
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
aicjofs said:
The hang with Nabi logo is because the fastboot driver is somehow broke. You will likely have to install it manually. Which driver are you using?
I gave most of the driver options here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Click to expand...
Click to collapse
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Conrad-007 said:
You were right! I've installed the "nacked" driver on a fresh windows 7 and now I have TWRP on my Nabi 2!!! Thanks a lot!!!
Now is there a way to get rid of the freezing problem when I attach the charger while Nabi is on? Right now, if I attach the charger this way, Nabi 2 will freeze completely and only a reboot can get the normal functionality back!?!
Charging the Nabi in "off" state works however...
Click to expand...
Click to collapse
I dont have Nabi2's anymore but both my kids tablets did the same thing. I never really found a solution. I did buy a cable from Nabi store that has the orange braid covering. It seemed to make a difference, but it still happened from time to time.
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
... aicjofs, please... help
Conrad-007 said:
Happy New Year!
As I mentioned, I was finally able to install TWRP and did all wiping, cleaning, repairing tasks that were available
After that I flashed the "Nabixus 0.1beta for Nabi 2" ROM which worked very nice.
But... I still have the same problems starting up the Nabi!
When I finally succeed to start it (after many trials), it works well, but if I let it go in standby and wait more that a few minutes, I am not able to wake it up again and I have to do a restart (about 10 sec. hold the Power button down).
What I`m not getting at all: is this a software or a hardware problem? Can my Nabi 2 be repaired after all, or I just have to scrap it?
The last thing I could still think to try would be to repair the partition table through TWRP / Adb / Adb shell. Should I try it? Where can I get a good partition table for my NV7A and, after having it, which commands are required?
Click to expand...
Click to collapse
You can't repair the partition table from adb/TWRP. It's read only. You could through nvflash but I don't think the partition table could possibly cause the issue. I think you are meaning fix super blocks and inodes of the filesystem? Even that is a stretch if it's happening how you describe it but with a try. Did you try repair filesystem like we talked about earlier? If not backup all the data and try a wipe data. That will make sure to blow away and reformat the data partition.
It could be hardware. I know for sure the charging system causes it when plugged in but not about the first boot stuff or when it's not charging.
Thank you aicjofs for your answer,
yes, I did attempt to repair the system, data, cache and it was successfully. I did it several times. I also wiped everything a few times and installed the Nabixus ROM afterwards. Nothing helped. It's like the operating system needs to "get warm" somehow, because I have to try to power on the system many times, until I get it work... but after that, if the Nabi goes in standby, I have to start the whole thing over
How can I check for damaged blocks, etc.? If I can do it and find some, could they be marked as "bad" and isolated? Would it make sense?
Related
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Has anyone experienced this or am I the only one?
M5devil said:
Has anyone experienced this or am I the only one?
Click to expand...
Click to collapse
Sorry I have never heard of this or witnessed it while flashing anything to my device. Obviously the battery screen signifies that the phone is off but is in charging mode and hitting the power button will boot the device up. (I'm sure you already know of this). Never heard of it being stuck at that screen after flashing. Hopefully you can get this solved soon. Good luck
M5devil said:
Hi guys,
I figured I'll post again here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6.zip and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else...
What I did prior to this was I formatted system and data on the recovery screen as per some posts here and it would just boot into a loop. Windows won't recognize a device and it just shows grey battery image and it doesn't seem to be charging. Anyone can help me?
EDIT:
Out and in the battery, plugged in to USB and it just loads the battery image and it's all grey color as if fully discharged and just stuck on it. Device is also not found in my system so I can't do any adb commands. If I just reset it without the cable it would just sit on the Samsung boot loop. Anything I can do?
UPDATE: Ok, some good news! I heard the sound as it connected via USB, I can see the 2 drives, but they read as Removable Disk and I can't access them...
adb reboot recovery or download
error: device not found
What if simply format the drives via Windows right click menu? Will that do any good or bad? What are my options here? Any help will be appreciated!
UPDATE: Well... looks like this is pretty much a dead phone.... I right clicked and selected Format in My Computer and it just says There is no disk in Driver F: Insert a disk and try again.
Can I a mount an image somehow via MagicISO? Or is there something simpler that I just can't figure out?
Again, thanks for your help!
Thanks.
Click to expand...
Click to collapse
Slow down for a second. Your phone is definitely not bricked. Ive been over the edge, and been able to bring my phone back to life.
To clarify, you flashed vibrant6.zip through clockwork mod, and then the phone got stuck on the samsung S? How long did you let it sit there?
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
I flashed the stock ROM via Odin and then wanted to install Vibrant6.zip. For that I entered into a recovery mode via Clockwork and as someone in the other thread advised, I formatted system and also data, don't recall exactly. Then it looped to a standard recovery mode and I just rebooted the phone. This is where it got stuck... Vibrant in the center and Samsung at the bottom of the screen. To test it I left it like that from night till this morning. In the morning I woke up it was on the same boot screen.
Before that at night, after seeing it hand at the boot, I held both volume keys and power, waited for it to reboot, and immediately it showed a circular progress bar, but not moving just highlighted the 12 o'clock bar and second later I see the battery image all in gray and nothing else. It just sits on that grey static image without actually charging it (no green section or flashing dots)
Boot logo only appears if I am trying to reset without the USB cable. On the boot loop I plug in the cable and I hear the USB connecting it, I see the 2 Removable disks, but both inaccessible and adb commands don't recognize the device.
Very weird, as in turned off mode it's not charging at all.. just shows this grey battery image with a circle progress froze on 12 o'clock bar.
That's pretty much it.... I was never able to enter into recovery nor download via the buttons. It would just always reboot into this grey battery screen....
Completely helpless.... I did order a new battery from TMO, maybe the battery is fried and that's why it's not charging and just sits on this stupid static grey battery screen.
ArbitrageMan said:
It sounds like just your ROM is messed up.
Are you able to "get into recovery"? Holding both volume buttons while you power on the phone, without it being plugged into usb.
Do you have Odin? And have you ever used it?
Its totally frustrating when your phone gets messed up and you don't know what to do.
Click to expand...
Click to collapse
Holding both volume keys and releasing power once screen goes blank, only show Vibrant logo again... I have tried this a million times
With USB cable it shows grey battery screen, without the cable just a Vibrant boot loop...
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
zephiK said:
I'm assuming that you have the Samsung drivers installed.
Try the following steps:
Take out the battery and then put it back in but don't turn the phone on.
Plug it via USB.. does anything show up on the screen?
Click to expand...
Click to collapse
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
M5devil said:
Yes, I have the drivers installed as I was able to locate my device and use adb commands to enter into recovery and download. Also Kies worked.
Doing what you asked simply load the grey battery image and nothing else with a progress bar not spinning. Just sort of hangs on this image and that's all.
Booting without the USB cable loads the Vibrant boot loop. Connecting USB at this boot loop state, would play a sound as if it connected to my windows, but I can only see Removable disks that are inaccessible and adb doesn't find the device...
Very strange.... trying to use the button keys to enter into recovery or download is no use, as that just won't ever happen, even when phone was working fine.
Any other suggestions? I would return the phone for replacement... but I am not sure how it would look with all the files still on the internal disk including root if I am not mistaken... I had only few hours of sleep because of this headache
Click to expand...
Click to collapse
Are you sure that you're doing the right things to get to download? I've been in this situation and I wasn't able to get into recovery but I was able to get back into download mode.
I believe if you return it back and they find out it was rooted, they will charge you for it. If not, it'll appear on your bill.
I'm sure that you're doing the wrong things to get into download mode. If something is appearing on your screen it is a soft-brick and you're not bricked.
1. Take out battery, put it back in. (to turn the phone fully off)
2. Don't turn it the phone on!
3. Plug the phone into your PC, do not hit the power button!
4. See if the phone shows anything on the screen (powers on its own when plugged in)
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons.
6. Hold the power button as well as the volume buttons until the screen goes black.
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons!
Click to expand...
Click to collapse
A tip to get into download mode is to put the phone HORIZONTALLY (sideways) and it will make it a lot easier.
I am pretty much positive about it. I know a lot of people can easily enter into recovery or download modes, but I know many can't and I am one of them. It would just load the grey battery image instantly as I let go of the power button.
1. Take out battery, put it back in. (to turn the phone fully off) DONE
2. Don't turn it the phone on! DONE
3. Plug the phone into your PC, do not hit the power button! DONE
4. See if the phone shows anything on the screen (powers on its own when plugged in) FIRST THING THAT APPEARS IS A CIRCULAR PROGRESS BAR THAT CHANGES TO A GREY BATTERY IMAGE WITH A BAR IN THE MIDDLE OF IT. STATIC IMAGE, NOTHING ELSE.
IF the phone screen does 'turn on' after being plugged in without you hitting the power button, so far so good.
5. Now while it's on like this, hold the volume up and volume down buttons. DONE
6. Hold the power button as well as the volume buttons until the screen goes black. DONE
7. As soon as the screen goes black, let go of the power button! But DON'T let go of the volume buttons! DONE
THE STUPID GREY COLOR BATTERY IMAGE APPEARS AS BEFORE....
I'm thinking maybe battery is fried and that's why the grey color screen appears and not the usual screen where you see the battery charging...
After reading this thread it's clear that my handset is one of the new ones that have recovery/download modes disabled via the volume+power buttons.
So that pretty much covers it... I hope TMO will not ***** about the files that are on the internal sd that I am unable to access and remove... unless anyone else has any fresh ideals how to gain access to the disk
I think I might have a similar problem.
I accidentally deleted the touchwiz framework so I can't do anything ON the phone. It boots up, and gets me to the lock screen. As soon as I unlock, I am greeted with dozens of unending force closes.
I can get into both download and recovery mode, however, I have not been able to get ADB to recognize the device. I am attempting to push the stock ROM to the internal memory to flash over everything.
I'm not sure what to do to get ADB to work but it's driving me nuts!
Stuck at vibrant? I have a fix
Check out android Dev Section... I figured out how to access download mode or stock recovery mode when you are stuck at the vibrant screen!!!! BACK IN BUSINESS VIBRANT OWNERS!!!
i got the same problem and nothing seems to work
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
eduardo_reflex said:
i got the same problem and nothing seems to work
Click to expand...
Click to collapse
... do i even have to say it?
droyd666 said:
Try this out http://forum.xda-developers.com/showthread.php?t=1103706
Click to expand...
Click to collapse
this problem is most likely solved. After 2 years!
mylostlonelysoul said:
Feels like I'm having same issues..
the previous post requires opening the phone and I don't have tools for that..
Here's my issue.
I can't get into Recovery or Download and computer won't see phone to Odin.
I've got drivers installed and AIO Toolbox as well as ADB(which won't work because of computer not seeing phone.
Using the manual option(vol+ vol- power), nothing works.
I've done all the tricks like unplug it then hold vol keys plug it insert battery..
When I do plug in the phone to to even just get a charge in it goes the the battery, but my is is frozen or something. doesn't turn green or have a charging animation. After about a minute or so it was start up and boot loop. I read something about a bad battery? I've got two of them and they seemed fine before..
Before all this I had to Odin and go to stock. I was attempting to get ics back but I was being lazy and trying to do as little as possible..bad idea. I was following slim ics install and flashed cm9 daily, slimics and commons..and now this..
I'm not sure what to do..I usually search around xda or google..10 hours later.. idk..Anyone able to give help please?
:crying:
Click to expand...
Click to collapse
Try asking another question. But I suggest using a USB jig. They usually work. Then odin
Sent from Mount Olympus via Hermes
Did you ever get it fixed man? I literally did the very same to mine a while back and It works like butter as we speak. It is fixable with a mini-usb jig or dongle. You can make your own with about $3 worth of parts from radio shack but I recommend buying one, it will be easier. I for the record made mine simply twisting together the resistors and though it was tough to touch the right pins it did eventually work and get me back into download mode.
Hopefully you already got it fixed though. If not I can help you out.
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolDown+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
qery said:
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolUp+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
Click to expand...
Click to collapse
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Most important thing, this is no big deal at all, it's really a minor issue. Don't let yourself get stressed out over it, the community will make sure you're good to go.
CharliesTheMan said:
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Click to expand...
Click to collapse
Yes sure my bad, it was typo (I was kinda sleepy and tired when I was writing)
CharliesTheMan said:
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Click to expand...
Click to collapse
Nope, this is my first time flashing.
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
leppie said:
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
Click to expand...
Click to collapse
nope it's not there. I was holding voldown from the start and as soon as it should say 'press volup for recovery' (time 0:04) it jumps (skips 5 seconds of waiting) directly to wipe/fastboot options (wipe is one that is selected on video)
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
qery said:
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
Click to expand...
Click to collapse
glad it's fixed, im sure hanzo001 will appriciate a simple thanks on his thread too..and let others know it worked for you
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk
I have problem with getting back to stock fullmics 5.5 on h850. I have installed it reboot and now Im stuck in secure start-up lock pattern from previous rom I believe. Pattern wont work and also meanwhile "FC system UI has stopped" warning is showing all the time.
I can get into download mode but port is not recgonized in vista so ADB cant be used (WHQL usb drivers 4.4.2 are installed ok)
problem is also that I cant get into recovery mode or
factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect.
Im really getting out of ideas to solve this...tech brain of the world please gather for help
fonejay said:
I have problem with getting back to stock fullmics 5.5 on h850. I have installed it reboot and now Im stuck in secure start-up lock pattern from previous rom I believe. Pattern wont work and also meanwhile "FC system UI has stopped" warning is showing all the time.
I can get into download mode but port is not recgonized in vista so ADB cant be used (WHQL usb drivers 4.4.2 are installed ok)
problem is also that I cant get into recovery mode or
factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect.
Im really getting out of ideas to solve this...tech brain of the world please gather for help
Click to expand...
Click to collapse
Go into twrp format data type yes how I fixed it on mine
TheMadScientist said:
Go into twrp format data type yes how I fixed it on mine
Click to expand...
Click to collapse
Why dont you fully read what I wrote
"...problem is also that I cant get into recovery mode or factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect."
ps: please excuse my writing my first language is clearly not english :fingers-crossed:
edit: just right now I opened phone up for check if buttons are OK...well turns out I wrecked button pins on motherboard.f*ck...now I know why I cant get into powerup menus...more specific I wrecked power button down pin on MB while opening back case with plastic card fkmylajf. Can be closed. SORRX
edit2: luckly I solved problem with straighteing pins so now twrp works as it should. What a noobish mistake huh...Be careful w with opening case!!??!
fonejay said:
Why dont you fully read what I wrote
"...problem is also that I cant get into recovery mode or factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect."
ps: please excuse my writing my first language is clearly not english :fingers-crossed:
edit: just right now I opened phone up for check if buttons are OK...well turns out I wrecked button pins on motherboard.f*ck...now I know why I cant get into powerup menus...more specific I wrecked power button down pin on MB while opening back case with plastic card fkmylajf. Can be closed. SORRX
edit2: luckly I solved problem with straighteing pins so now twrp works as it should. What a noobish mistake huh...Be careful w with opening case!!!
Click to expand...
Click to collapse
Sorry bout that mate I speed read a lot of stuff and sometimes miss Key details:silly::silly:
I ran into the problem with the corrupt startup and couldn't get out of it.So thats what I saw...
I run across a lot of devices so i spend a lot of time reading many many pages hard to catch it all