Hello there
I have a Touch Pro device, and since yesterday evening, after the phone goes in sleep mode (or after i press the power button), it doesn't turn back on. I can't reset, can't Hard reset even. If i call the phone, it rings, but the screen doesn't turn on, neither the illumination of the keys, or the keyboard. If I take out the battery and put it back, it boots OK, screen works, until it goes to sleep mode, after that... the same.
I had Romeos ROMeOS² v1.90.2] when the problem started, now i was able to flash it to ShEp's Rom Ver 2.3a][WinMo 6.5][Build 21198 Ver 2][TF3D Ver 2] and the problem still persists.
Thanks for your help.
Update: I haven't done anything and now it's does not even boot, it vibrates when its turned on, and i can hear the start up melody, bot no screen and no keyboard illumination.
might help
I'm no expert, but have you tried Bootloader mode? If you can get into bootloader mode after taking out the battery and restarting, try flashing Hard SPL again then a stock ROM with a radio. With the phone plugged into the USB port it shouldn't go to sleep. If that doesn't work it may be bricked.
Untill now the phone started after i took the battery out, and i flashed it to another rom. Even after this it started up after i took the battery out, after that i haven't done anything and now it doesn't screen wont start even after i took the battery out.
The only thing i didn't try was hardspl again......
OOh man, i was trying to do a hard reset without the screen. and now if i turn the phone on, every time i press vol down/up after i certain time, the phone vibrates as when you turn it on. It's stuck at the hard reset phase ?
How is the hard reset ? Vol up to hard reset and after that vol up to boot ?
Suggest you read the wiki
Have a look at the wiki for beginners. Hard reset is normally hold VOLUME DOWN AND CENTER BUTTON then reset with stylus.
Thank you for beeng so friendly and helpfull, since the display was off, i asked what too push AFTER entering the hard reset screen. It was VolUp to hard reset, and afther that VolUp again to reboot. Or VolDown... It doesen't matter, i took the phone back to Orange warranty
I don't know what will they say... HardSPL+ Custom Rom... But phone won't start so mabey they wont notice
Cheers
well my phone is now stuck on the htc screen... help please
I was running meanrom 3.0 then dirty flashed 3.9. My phone would turn off randomly so i restored it to 3.0. Then my text messages wouldnt work couldnt send or receive. So then i full wiped, restored and still no text. Then I full wiped and hit reboot system. And now it is stuck. I guess it is stuck because i didnt restore or install a rom? I cant even get to the bootloader. So is this phone a paperweight now?
Hold power down, this will cause a simulated battery pull, the phone will turn off, wait a second or two then press and hold power button and volume down and you will boot to the boot loader. Be very careful next time
Edit so long as your phone responds there is almost always a way to fix it, you only worry when phone stops responding (screen off won't charge won't turn on)
I wish more people would read my guide I included problems (even this exact one) to help people avoid them
ok got to bootloader. THANKS
No problem I'm glad I helped.
Note: This exact problem and many others are in the troubleshooting section of my guide. (Sorry if I don't advertise no one will use it lol)
Yep.... you wiped the ROM and then tried to boot nothing.
yeah....this is clearly covered in my guide...lol
I have a T-679. it is only lightly modded. I still have stock UVLE1 with Clockworkmod recovery...v5.5 i think. All has been well until recently I have been trying out a lot of new apps. recently i got the adw launcher and camera sensor. now when i reboot i see one Samsung logo, then tmobile/android logo and jingle, then another Samsung logo and it hangs here. if i wait some time and start pushing buttons I see that the phone seems to be active. if i push the power button then the vol-up/down i hear the sound of the volume being adjusted. also very curiously i just found that if i hold down the home button and press the power button i hear a shutter sound!? In some instances, haven't figured out if its a particular button press of just random, i can get the lock screen to come up, which then allows me to unlock the phone and all works normally... until i reboot again.
any ideas suggestion how to proceed? Thanks.
edit: I just checked I have CWM recovery v5.5.04,b
I have a backup from a while back and i just made another backup
I also tryied wipe cache/dalvik which i thought it helped because i think it booted directly after that, but i just tryed again and
this time i see no benefit/effect
overload1 said:
I have a T-679. it is only lightly modded. I still have stock UVLE1 with Clockworkmod recovery...v5.5 i think. All has been well until recently I have been trying out a lot of new apps. recently i got the adw launcher and camera sensor. now when i reboot i see one Samsung logo, then tmobile/android logo and jingle, then another Samsung logo and it hangs here. if i wait some time and start pushing buttons I see that the phone seems to be active. if i push the power button then the vol-up/down i hear the sound of the volume being adjusted. also very curiously i just found that if i hold down the home button and press the power button i hear a shutter sound!? In some instances, haven't figured out if its a particular button press of just random, i can get the lock screen to come up, which then allows me to unlock the phone and all works normally... until i reboot again.
any ideas suggestion how to proceed? Thanks.
edit: I just checked I have CWM recovery v5.5.04,b
I have a backup from a while back and i just made another backup
I also tryied wipe cache/dalvik which i thought it helped because i think it booted directly after that, but i just tryed again and
this time i see no benefit/effect
Click to expand...
Click to collapse
After wiping everything such as data, cache, dalvik-cache, battery stats in CWM, try restoring the Nandroid backup which you've created. If still, it gives weird issues, fresh install another ROM.
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?
Now, The circle is running all the time.
Last night I was watching a movie. And then after clicked the 'recent tasks' button, it stuck. The thing I can only do was to press the power key or to throw it and hit something heavily. So I pressed. But it still stuck, in another way, left me a boot animation. Flashing again or restoring a backup of system folder is useless. Today, I reinstalled the whole system in a clean way, :laugh: and it get recovered for a shirt time.
Why 'a shirt time'? Because I forget to flash 'su', and tried to restart it to recovery mode, but it restarted as usual, so I pressed the power key again.
Hope you can understand me. I'm still studying English.
LineageOS Version: 14.1 20170706
Well, the battery is emptied.