Related
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
- Tried Kies and the phone was not recognized in either DL mode or boot loop. Was hopeful Kies could reinstate the firmware.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
tone_la said:
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
Click to expand...
Click to collapse
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
dandrumheller said:
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
tone_la said:
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
Click to expand...
Click to collapse
Unplug the USB when you do that
Sent from my Galaxy Nexus
Stop using brick. It turns on it is not a brick
Sent from my GS4 running CM11 Kandy Kane
Pirateghost said:
Unplug the USB when you do that
Click to expand...
Click to collapse
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
Click to expand...
Click to collapse
I've tried very hard to not "waste" anyone's time by doing my research, searching, and thinking; BEFORE posting. My question above is not so much "how" to clean the port, but "does this symptom I'm experiencing sound like a 'bad port' issue?". Believe me, I've done tons of searching to try to solve this problem before posting so that I can be worthy of receiving assistance.
And to the guy who says, "don't use the term brick". Sorry I said "Apparent brick"; just looking for some neighborly help to get my phone working again. At any rate, I very much appreciate any advice to help me get this fixed.
Trying hard to keep the forum clean and think for myself when possible!
dandrumheller said:
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
tone_la said:
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
Click to expand...
Click to collapse
I should elaborate a little for safety's sake - probably a no brainer, but in case - TAKE YOUR BATTERY OUT BEFORE CLEANING THE PORT. Don't know if it matters or not, but I wouldn't want you to short stuff during cleaning - rubbing alcohol IS part water.
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Red_81 said:
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Well, I cleaned the heck out of the USB port with rubbing alcohol and a toothbrush, followed by a thorough drying with compressed air. Yes, battery removed during the process; thanks for that! Unfortunately, same exact symptom. Only goes into DL mode and boot loop.
I'll now try your portable adb suggestion and see if I can get a connection.
Does anyone else have any thoughts on what may have gone wrong and/or anything I can flash via ODIN to fix the issue? Many thanks!
Installed your portable adb and followed your instructions. Ran the recovery_mode batch file and adb initialized (daemon not running, starting daemon...) followed by red text "Waiting for your device to be detected". I already installed the Android SDK yesterday and the following modules are installed: Android SDK Tools, Android SDK Platform-tools, and Google USB Driver
Powered on the phone and after a few seconds the "Rethink Possible" logo showed up and shortly thereafter, I heard the computer beep indicating it connected with the phone. Win7 device manager shows "SAMSUNG Mobile USB Modem" under the Modems category.
However, the portable ADB continues to show "Waiting for your device to be detected" and the boot loop continues. Did the same thing in DL mode, same result.
I reinstalled the Samsung I777 driver from Samsung's site. Going to reboot my PC now to see if that makes a difference.
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
tone_la said:
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
Click to expand...
Click to collapse
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
dandrumheller said:
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Click to expand...
Click to collapse
Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.
Phalanx7621 said:
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
Click to expand...
Click to collapse
I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.
After many many hours of frustration and dead ends, I've finally recovered my phone! YAYYYYY!!!!!
Here's how I got it done...
- No matter what I flashed, I kept getting the boot loop. This was really throwing me for a "loop" when I thought I was flashing standard original Sammy full ROM with ODIN; yet that wasn't enough to recover the phone.
- Something was missing with the boot process, so I started looking for CWM that I could flash via ODIN. Most sites had the zip CWM file, but only a few had the TAR file. Finding a valid file proved more difficult than I thought with all the download sites that went offline for legal reasons. But I did find one!
http://www.mediafire.com/?bjhx33o4viz8tza
The above link is for file name: SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar
- Once I installed the above via ODIN, all of a sudden ADB recognized the phone and I was able to run: ADB REBOOT RECOVERY
It's very possible that the 3-button recovery may have worked too, but when I saw the device show up on ADB, I didn't want to take the chance.
- The device then rebooted and entered RECOVERY mode! FINALLY!!!!
- I then did a factory reset / wipe and rebooted the phone. It came up just fine, NO MORE BOOT LOOP!
Thanks to those who replied to this thread. The responses helped me think hard about what was going wrong and ultimately I dug up a solution.
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
knismaps said:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
Click to expand...
Click to collapse
why do you want to enter the bootloader? and have they made any roms or cwm recovery for these types of generic android tablets?
[RESOLVED] finally, ROOT for Neutab N7 pro tablet.
knismaps said:
I have a fairly generic Chinese tablet, a Neutab N7 (not a Nexus 7), but I have no idea how to enter the bootloader/fastboot mode.
Using adb, "adb reboot bootloader" or "adb reboot-bootloader" just makes it reboot normally.
From a shell, doing "su reboot bootloader" also reboots normally.
I tried Quick Boot from Google Play which has an option to reboot into the bootloader, but it also just ends up rebooting normally.
While powered off, I tried holding power and volume up, power and volume down, and power and both volume up and down, but they all just boot normally.
Doing "adb reboot recovery" does boot me into recovery mode, but the menu doesn't have a bootloader/fastboot option.
Does anyone have any idea how to enter the bootloader/fastboot mode for this tablet? Any help would be appreciated.
Click to expand...
Click to collapse
Having been looking for this information myself i'm sharing real quick here what i've found. Scouring the net all over i've found NOTHING specific for these Chinese tablets but after finally getting on the scent of VROOT I downloaded and tried iROOT essentially a one-click rooter the .APK **DID NOT WORK** but the PC version **DID** can be found by googling iroot or vroot.
RE: bootloader, i've still found no way or any good info on entering the bootloader AFAIK this is locked and may not be possible without some good hard hacking on the firmware, I DO KNOW that if you try entering the "bootloader" with a reboot manager on the device u will find yourself at the "NeuTab" welcome screen and stuck. Fortunately at least in my experience, letting the tablet battery run down low you can boot back into it and root condition is still good.
Hope this helps somewhat I know its an old post but a lot of people have been looking for this info have yet to post on authors site confirming that the NeuTab also works with his software.
peace.
VE3UND
BTW I forgot to mention the site and the software (ALTHOUGH IT STATES OTHERWISE) is in Chinese. A leap of faith needed there I know but i confirm this method works. l8z
BTW^2 ALSO the android version was KitKat as received from the mfg, also have been told that Jellybean will install on the tablet after rooting and maybe is now included with device but don't quote me on that.
all in all a really nice tab for the price, especially now we have root biggest missing option: GPS but you can tether to another device with gps if you need to. Also no built in USB HOST MODE. //out
I've got the NeuTab N10 and can't get ADB to see it at all. How did you get ADB to work with your N7, were you able to find NeuTab ADB drivers somewhere?
So i recently came across this tablet in my stuff... something i picked up for the wife a few years back.
I also came across this website.... http://neutab.com/info-detail.php?InfoId=11
It has all the tools and programs that the company uses. includes all files for development of their entire line of tablets.
Thought this may be useful. just click on the link that says pheonixtools.zip and it will take you to a back end file server... This tablet is about as open sourced as it gets... so... this leads me to ask a question i have been struggling with for the last 2 years of being a member on this website...
can anyone... please... help me develop my first recovery and custom rom for this tablet? I just have never done it all the way... i have set up a couple things here and there... figured out how to strip the stock recovery and boot... but never got further than that.
Thanks for the help.
• Unzip phoenix tool.zip you just downloaded; (to open a .zip file, download WinRAR)
• In the folder of phoenix tool you just unzipped, depending on your system specs, select "drvinstaller_X64", "drvinstaller_x86" or "drvinstaller_IA64" to install tablet driver; Or you can run all three driver installer and at least one will work;
• Run "PhoenixSuit.exe", select "firmware" tab;
• Click on "Image" button, choose the firmware you just downloaded;
• Turn your tablet completely off (by press and hold power button for 20 seconds), press and hold "volume -" button, connect tablet to computer via usb cable, keep volume button held, press power button 10 times repeatedly；
• The phoenix tool should recognize the tablet. On pop-up dialog window, select if you want to format and wipe out everything on your tablet；
• The phoenix tool will start flash the firmware to the tablet. Wait till it is done；
• When upgrade is finished, disconnect your tablet from computer, press and hold power button for 10 seconds to quit upgrade mode. then press and hold power button for 2-4 seconds to turn tablet on；
Congratulations! Your tablet is now refreshed.
Ok so I have a NueTab Air 7 Android and I have talked toto their customer support which did neurologist absolutely no good. I have been trying to hard reset my tablet and do a factory reset by holding down the volume up and down keys and the power keys until it gives me the option of rebooting. However, there is no option for a factory reset. Only a Recovery mode, Fastboot mode, and Normal mode. I tired the Normal and Recovery an both sent me back to enter password that I can't rremember, which isthe why I'm resetting it lol. Finally I chose the Fastboot option and now it is stuck on that option and has been for almost an hour. It willwas not let me power off, try to hard reset, it is literally stuck. And it is a hundred percent charged. I do jot hav the optiontime to connectbe the tablet to acall Windows computer at this timetime, as the forums I have read say can possibly fix the issue. And what a surprise the customer service phone number for this specific tablet does not know how to fix it!!!!! Not surprised at all. If anyone at allthe has any ideas or knows what to do or howsomething to fix it please help meme. I'm very frustrated to say thethat least and in desperate need of help. Anything would be immensely appreciated. ~Melissa
How to identify the exact firmware of the N7 after this page (Oficial NEUTAB), I have 3 options but that IMEI series is nowhere in the table.
---------- Post added at 11:35 PM ---------- Previous post was at 11:35 PM ----------
this page http://neutab.com/info-detail.php?InfoId=11
n7s root
therealtaynak said:
So i recently came across this tablet in my stuff... something i picked up for the wife a few years back.
I also came across this website.... http://neutab.com/info-detail.php?InfoId=11
It has all the tools and programs that the company uses. includes all files for development of their entire line of tablets.
Thought this may be useful. just click on the link that says pheonixtools.zip and it will take you to a back end file server... This tablet is about as open sourced as it gets... so... this leads me to ask a question i have been struggling with for the last 2 years of being a member on this website...
can anyone... please... help me develop my first recovery and custom rom for this tablet? I just have never done it all the way... i have set up a couple things here and there... figured out how to strip the stock recovery and boot... but never got further than that.
Thanks for the help.
Click to expand...
Click to collapse
I would love to root this tablet purely because it's my daughter's and some of the games she likes has some real funky permissions That they want! A custom rom would be nice but I will be satisfied with being able to revoke some of the permissions that the apps want to have access to.
n7s software download issue
therealtaynak said:
• Unzip phoenix tool.zip you just downloaded; (to open a .zip file, download WinRAR)
• In the folder of phoenix tool you just unzipped, depending on your system specs, select "drvinstaller_X64", "drvinstaller_x86" or "drvinstaller_IA64" to install tablet driver; Or you can run all three driver installer and at least one will work;
• Run "PhoenixSuit.exe", select "firmware" tab;
• Click on "Image" button, choose the firmware you just downloaded;
• Turn your tablet completely off (by press and hold power button for 20 seconds), press and hold "volume -" button, connect tablet to computer via usb cable, keep volume button held, press power button 10 times repeatedly；
• The phoenix tool should recognize the tablet. On pop-up dialog window, select if you want to format and wipe out everything on your tablet；
• The phoenix tool will start flash the firmware to the tablet. Wait till it is done；
• When upgrade is finished, disconnect your tablet from computer, press and hold power button for 10 seconds to quit upgrade mode. then press and hold power button for 2-4 seconds to turn tablet on；
Congratulations! Your tablet is now refreshed.
Click to expand...
Click to collapse
I have yet to be able to download the zip or the firmware software. i got root with kingo pc version but that's pretty much it and I can't change the route manager because once I delete that then I don't have root anymore and can't add another one. Also I have yet to been able to get into or see download mode on this either. It just stays on the screen with the name on it and that's pretty much it. no bootloader unlock either
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
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?
This is the Fusion5 in question
https://www.amazon.co.uk/gp/product/B01CCYEIW2/ref=oh_aui_detailpage_o05_s01?ie=UTF8&psc=1
I tried rooting the tablet using kingoroot - both the Android app & the PC program..All 'failed' - but tablet was still running ok, so I'm guessing it's not possible to root it with these programs
Anyway, I accidentally left the battery to drain out, causing it to turn off - so started recharging it.
Once I thought it had enough charge I tried turned on the tablet, saw the White 'Fusion5' title screen followed by the black 'android' text screen... but now it's stuck on the android screen
So I've tried:-
> Turning off/on by power switch - same thing (White Fusion5/Black android screens)
> Press the small 'reset' hole on the back - same thing
> Tired different combo's of Power button/ vol +/vol - buttons - same thing
Have I bricked it ??
Is there a way to get the thing to boot up into recovery.. if so what's the button combo's ? or is there some other way using PC
IS there a recovery mode for this tablet or did kingoroot wipe it/corrupt it somehow ??
Any help greatly appreciated
EDIT: btw further searching seems to show theres a 'kingroot' and a 'kingoroot'
- but 'kingroot' website [https://kingroot.net] doesn't exist but a google search shows kingroot [https://king-root.net/] however the download is being picked up by Virus checker as malware
Has it booted far enough to retrieve a logcat?
If ADB is responding, adb reboot recovery is another hope.
qeexo said:
Has it booted far enough to retrieve a logcat?
If ADB is responding, adb reboot recovery is another hope.
Click to expand...
Click to collapse
Thanks for the quick reply however the main reason I went 'kingoroot' was for simplicity since I don't know anything about ADB
(I know of it, just not how to use it)
Anyway,tried following one of the many guides (this one in fact)
but when I do 'adb devices' it's not showing anything, although it's possible something is conflicting because even though my Samsung phone shows up when I plug it in, doing 'adb devices' shows nothing - I would've expected the Samsung to show up at least
I'll have more time during weekend to try & figure out why phone not showing in ADB & experiment with ADB a bit more