[Q] Touchpad rebooting in loop cause of bluetooth - TouchPad Q&A, Help & Troubleshooting

Hi everyone,
I am currently having a big trouble with my hp touchpad, it was working very well until my dad asked me to try something with the bluetooth.
I just actived it from a gadget (not from the menu) and since I push the button, my touchpad restarted the cyanogen9 then when he finishes restarting, it do it again and again as a loop.
It seems that it all started after pushing the activation of Bluetooth :s
I actually tried to instal other version of cyanogen9 (I was on the version : cm-9-20130929-NIGHTLY-tenderloin, and now I am on cm-9-20130714-NIGHTLY-tenderloin but the result is the same since the Bluetooth is still activated.
I also tried to do a wipe cache but since that my touchpad just stay on the loading screen of cyanogen9...
Thanks for your help.

clad58 said:
Hi everyone,
I am currently having a big trouble with my hp touchpad, it was working very well until my dad asked me to try something with the bluetooth.
I just actived it from a gadget (not from the menu) and since I push the button, my touchpad restarted the cyanogen9 then when he finishes restarting, it do it again and again as a loop.
It seems that it all started after pushing the activation of Bluetooth :s
I actually tried to instal other version of cyanogen9 (I was on the version : cm-9-20130929-NIGHTLY-tenderloin, and now I am on cm-9-20130714-NIGHTLY-tenderloin but the result is the same since the Bluetooth is still activated.
I also tried to do a wipe cache but since that my touchpad just stay on the loading screen of cyanogen9...
Thanks for your help.
Click to expand...
Click to collapse
It sounds like CM 9 doesn't like whatever you did to your Bluetooth. What I would do would be to re-flash CM 9. If your Touchpad isn't working on the Android side, boot into Web-OS and download the CM 9 file to your computer. Connect your Touchpad to your computer and copy the CM 9 file to the SD card. Then re-boot into recovery and flash the CM 9 ROM and Gapps. This should work because to are installing a fresh rom over the old one.

Related

newly installed CM9 keeps rebooting

installed CWM and CM9 per the wiki on rootzwiki
everything seemed to install just fine, however the tablet keeps rebooting upon trying to boot into cyanogen. it goes to the loading screen then reboots shortly after. anyone have any idea as to why this is occurring?
knox07 said:
installed CWM and CM9 per the wiki on rootzwiki
everything seemed to install just fine, however the tablet keeps rebooting upon trying to boot into cyanogen. it goes to the loading screen then reboots shortly after. anyone have any idea as to why this is occurring?
Click to expand...
Click to collapse
Not sure but did you wipe the cache and the davlik cache? I'd try that first. Might want to try re-downloading the zip and reinstalling if that doesn't work.
At various times I get events:
Seems when charging cable is removed it settles down and behaves better..
When selecting the reboot it shuts down.
When shut down it reboots.
North do I get battery charging symbol when off.
knox07 said:
installed CWM and CM9 per the wiki on rootzwiki
everything seemed to install just fine, however the tablet keeps rebooting upon trying to boot into cyanogen. it goes to the loading screen then reboots shortly after. anyone have any idea as to why this is occurring?
Click to expand...
Click to collapse
Had the same issue. You need to install it with ACMEInstaller2 instead of the old one. Had to install and uninstall it 2 times before figuring that out.
If you came from cm7 also be sure to clear out the old kernel. Apparently the touchpad can have two kernels on it, which messes things up.
Sent from my android touchpad.
galaxy w with cm9 keeps restarting
hi guys sorry to bother but i recently flashed my galaxy w from http://forum.xda-developers.com/showthread.php?t=1576874 with cm9. it was wonderful at first but recently my phone just keeps restarting. i cant even use the phone. pls help!!!
junlongt said:
hi guys sorry to bother but i recently flashed my galaxy w from http://forum.xda-developers.com/showthread.php?t=1576874 with cm9. it was wonderful at first but recently my phone just keeps restarting. i cant even use the phone. pls help!!!
Click to expand...
Click to collapse
This is the HP Touchpad forum. You'd be better off asking in the Galaxy W forum.
http://forum.xda-developers.com/forumdisplay.php?f=1474

[Q] Changing from CM10.1.3 to 10.2.1 Spinning Wheel can't enter recovery mode

Hey guys I've decided today to update my Samsung galaxy s I9000 from 10.1.3 to 10.2.1 so when the final release 11 comes it would probably be easier to update.
But it kept giving me this error This ROM uses an incompatible partitionlayout status 7
I tried using external sd card and internal sd card it didn't work.(obviously going trough all the right steps like wipe's, even cleaned dalvik whatever that is).
EDIT: for some reason i called it boot loop but it isn't the same, i just can't pass trough the spinning cyanogen wheel, everytime i try to turn off and restart phone it goes directly to the wheel.
What should i do? There's a lack of certain steps to fix this, at least i found none.
Thanks in advance.
PS: Loosing all data is no problem i saved my contacts and sms before

HP Touchpad Toolbox not working????

So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
josh426 said:
So I downloaded all the files that I need and start with a fully charged touchpad. I currently am running an older version of android on it with webos, but decided since I have not used webos in over 2 years, why not wipe it clean, install a new version of android and just leave off webos.
Now with everything in place, I connect the touchpad in recovery mode, start touchpad toolbox, i see the commands scroll on the touchpad screen for maybe 1 or 2 seconds and it then just reboots itself. Am I missing something or is this just not working?
I even thought maybe I was running low on storage and did a factory reset of android to wipe everything that was installed off with no luck.
I just want to wipe this clean and do a fresh install of kitkat or whatever. dont need anything else on it, dont even need the multiboot. Any recommendations out there?????
Click to expand...
Click to collapse
I have heard no reports of what you describe.
I suggest using TPToolbox v41 from here (download link in that post):
http://forum.xda-developers.com/showpost.php?p=54986968&postcount=293
and try again.
If it does it again, I will need to see a kernel log file to help diagnose what's happening.
To get that, following the instructions on this post:
http://forum.xda-developers.com/showpost.php?p=53258228&postcount=10
but replace steps 1-3 with:
1) Load Touchpad Toolbox
2) Start holding the Volume Up button
3) Continue to hold VolUP until you see the big USB symbol (i.e. webOS recovery)
Errgghh
Downloaded but not sure what is going on. I think the problem my be with something being overwritten during one of the first attempts. With the USB logo displayed, I connect it to the PC. The minute it starts to transfer, it resets and I see the hp logo and then the boot screen. At this point it is stuck in a rebooting loop for several times. I even just tried webos doctor and it starts at 1% and as soon as it hits 2% it reboots the same way.
Also will not mount as a USB drive on the PC. Just as a palm noobie or something so I can not access anything on the device manually.
While I have not experience your issue I have had other issues that were resolved by changing to a different USB cable. Might be worth a try.
Sent from my MT2L03 using Tapatalk 2
Having the same issue. From USB to HP logo, then 1.5 seconds of text and then reboot. Tried V41 and V42 and tried multiple USB cables.

Asus memo pad 7 (k013) does not start after un-root

Hi all,
I am trying to build a car headunit system using the Asus memo pad 7 ME176CX (k013). I got everything sorted out and the last thing I had to do was to kill the player when the ignition of the car is off.
For that reason I installed llama and made an event to kill the player when on battery. This did not work so I decided to root the tablet so I could force-kill the app.
I downloaded the one-click zenfone root from and followed the instructions. Everything worked just fine and I got the Super SU icon and so on.
Unfortunately, llama still could not kill the process, so I decided I did something wrong and started the un-root.bat file. The process ended with success, but.......I got stuck to the ASUS logo with the loading
indicator below (just before the home screen loads) . I could still connect to the tablet and performed the CheckBeforeAction.bat - it worked just fine. For some reason decided that it would be a good idea to root again and did it - again successfully (or so says the shell).
However, I could not go pass that ASUS logo. So (as if I haven't created a big mess already) I entered into fastboot mode and performed factory reset. That did not help at all.
I followed the instructions and downloaded the stock 182 ROM (I saw the WW version from the fastboot screen), put it in the root of my external 16GB SD card and renamed it.
Well.....when I enter fastboot mode I do not see an option involving SD card. All options I have are droid reboot, something I can not remember but has nothing to do with SD, recovery, power off.
When I go to recovery there I see
- reboot
- apply update from ADB
- wipe data
- wipe cache
Strangely, I can no longer connect to the tablet via USB, so I do not know how to make use of the CWM.
I downloaded ADB_driver.zip and ASUS_Android_USB_drivers_for_Windows_20140325.zip, but for some reason these do not work - I get ERROR 10 when starting the driver.
Well, after all the things (probably really stupid) I did, now I am still not able to boot, but it also looks like I have no more USB access to the device and do not know how to take advantage of the
procedures that I have seen in the different threads.
Is there a way to still recover the device?

Samsung Tab s2 stuck booting into TWRP

Ive been lurking on this forum for a while but ive finally hit a wall I cant find an answer to
I successfully rooted my tablet using magisk and TWRP about 4 months ago, everything was going great. about 2 months ago my tablet booted up into TWRP and would not get out, no matter what I tried. eventually I fixed it by wiping everything and reflashing stock ROM from ODIN and going through the root process again, not a big deal. cut to 2 days ago, my tablet restarts and boots into TWRP again and wont boot into system, basically seemed like the same as before, until I plugged it into my computer
For some reason, my tablet no longer connects to ODIN or my laptop at all. Ive used the same cable and different device and same usb port and it worked just fine, ODIN picked up the connection and everything. Ive updated and unistalled and reinstalled drivers for all the USB ports and I dont think that is the issue. I even deleted and reinstalled ODIN but still nothing.
I thought maybe there was some setting on the tablet that might be preventing a connection to ODIN, so I wiped the rooted ROM off the tablet (im new to this, dont know if this was a bad idea) and tried again but got nothing. now with a soft bricked tablet I got a micro SD card, put a TWRP flashable version of the ROM onto it and plugged that into the tablet and flashed this new ROM onto the tablet, and that worked from what I can tell (system folder went from like 8mb to 17000 or something) but I still cannot get the tablet to boot into system.
I can access download mode (there appears to be two versions, one where it just says downloading and another where a bunch of text appears on the top left, some of it mentioning ODIN) and all the functions of TWRP, but ODIN does not connect and I cant get it to boot into the system.
TWRP version 3.1.0.1_ashyx
link to the post where I got the stock lite version of the ROM currently flashed to my tablet:
https://forum.xda-developers.com/tab-s2/development/rom-nougat-stock-lite-v1-t3746583
any help would be greatly appreciated, sorry for the wall of text.
Wish I had something useful to add. I'm having the same issue. TWRP 3.4.0.0 and LineageOS. I've had this issue forever. I flash a clean ROM, it works for a week or two, then I come back to it and all I get is recovery.
I can access Odin however.
Usually it takes wiping and installing a ROM to get the device working again, in fact it issue takes several rounds of that. But of course, in all of that I've lost my setup and some files.
Is there an actual solution to this?
On my T810 I'm having TWRP 3.3.1-0 with this ROM https://forum.xda-developers.com/tab-s2/development/rom-aospextended-rom-v6-7-t3979381
plus Magisk and Pico Gapps.
Of course it's only Pie and not Q, but working well.
3.4.4-0 not tested yet.
Once had an issue with black screen, but at that time I was using case with a screen cover.
Since that I've switched to TPU case only covering the back.
No more issues after that, perhaps it was a problem with FlipFlap like on other devices.

Categories

Resources