Hello XDA Members,
first I dont know if im in the right place, but if im not, dont hasitate to move this thread.
Story: I tried to root my Pearl Touchlet XA100 tablet (running Android 4.4.2), but i failed. At this point, it was working. Some time later i wanted to know if it has a fastboot mode were i could boot into, so I typed via adb "adb reboot bootloader", the device rebooted but the device is stuck in the kernel splash image (the image that gets displayed before the bootanimation appears). Its even stuck there when i plug in the charger (it has its own charger port, i dont know i it displayed ever this offline charging animation over usb).
While Im thinking about RMA (with luck they swap/repair it) i cant get it out of my head so i was watching the devices source code, where i found under 0709_4.4/android/hardware/qcom the folders "msm8x74" and "msm8960", the folder msm8960 where in my mind they i looked for it, and its the qualcomm S4 Plus cpu.
Now my Idea/question is that i can compile the source code and flash it... But is there any way for me flashing it if i cant do anything with it? While my PC still detect it as "Samsung Android Phone" i cant use adb, and the device has only a "Back" and a "Power" button on the side, pressing both at the same time to boot into recovery (its the only way i imagine to enter a recovery/bootloader on this device aside from adb...bootloader worked "well").
I dont know much about Android source development, but atleast i know how to flash roms/kernels via recovery and Samsung phones via odin, but maybe with a little help with you it will be enough to revive the tab from the dead.
The device has a 1,5GHz dual CPU, usb 2.0 with OTG support, Android 4.4.2, 2 hardwarebuttons ("Back" and "Power"), a seperate charger port, wifi, a 10.1 zoll touchscreen, 4,5gb internal storage (only /system and /data, no emulated internal sd), the microSD slot supports up to 32gb microSD card. Device at pearl (german cheap-things site: http://www.pearl.de/a-PX8838-1000.shtml Link to the source code of the device: (Sorry, actually i cant upload them on github, its official pearl download) http://www.pearl.de/support/product.jsp?pdid=PX8838&catid=1000&nodocs=1
Call my stupid, frankenstein or so but i cant get it out of my head and i want to repair it, first for fun at the challange and 2nd for saving time waiting on the answer of the support.
Hopefully you understand my personal reasons, the post itself and have the knowhow/right tips to help me
How to root Touchlet XA100?
Hi adi2500,
Unfortunately I do not have the answer for your post, I am new to the Android world.
I would like to know though how you rooted the Touchlet XA100. I have the same tablet and I am a bit lost with all these tools I can find on the internet, none of them seem compatible with Touchlet tablets... Information about tTouchlet tablets is very hard to find...
Which tool did you use? Before you tried the fastboot mode, did you say that your tablet was rooted and working?
Thanks in advance for your answer !
Nothing i tried rooted the device. I actually have 2 superuser apks in /system/app, supersu installed and still i cant install the su binary. Actually i got it running again bx fully discharge the battery, but what makes me wondering is the fact that the battery wasnt connected to the mainboard and the devicr still didnt Boot.
Well, my last Option is building CM11 for it, but i dont know if i can run a modded kernel in it and even if i make it bugless, i dont know how to flash it.
One APP Form bluebox (forgott the Name) tells me, the towelroot bug isnt patched and maybe we have to mod towelroot or write our own APP, but actually im happy without root (better having a non root tab than no tablet). Maybe an Android pro could help us, since im at the end with my knowledge.
Hacker kibs at your service
Never heard of that device, but I can help you
Did u tried the kingo android root
The rooting software is only for supported or unsupported android devices
So I request u to try the kingo android root
This requires a computer to do it
Thanks
HK
Thanks for the advice, I will try Kingo Root
Kingo Root worked
Thanks for the advice KIBS2173 , Kingo Root was able to root my Pearl Touchlet XA100 without any issue I just had to install Universal Android USB Driver on my PC because Windows did not manage to find a driver for it via Windows Update.
Bricked OP2 ...
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
If you flashed a ROM that's not for you're phone you're more than likely screwed
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Bhups said:
Could you try the following:
1, plug the phone back in recovery/fastboot mode
2, Open Computer Management and delete the drivers the OS finds for the phone
3, Download the ADB driver tool from here: http://forum.xda-developers.com/showthread.php?t=2588979
Try follow the steps and let me know if u get the drivers needed for the recovery
If the tool on the above link dont work, try this one: http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Click to expand...
Click to collapse
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Heisenberg said:
Two problems here. The first problem is that you didn't wipe properly when flashing Nethunter, that's why you ended up with Nethunter apps on your stock ROM. When flashing a ROM you must perform a full wipe, this consists of system, data, cache, and dalvik cache. This isn't what bricked your phone though. We know what bricked your phone; flashing a ROM for a completely different device. I'm not sure why you would flash a ROM from another device, maybe due to inexperience, but that's the last thing you should be doing, as you now know. Don't use the recovery tool that you have, it isn't for your chipset, it will only make matters worse. I honestly don't think there's any way to revive your device, you've pretty much rendered it useless. I'd strongly suggest you do a lot of research before deciding to mess with another phone, if you don't know what you're doing then don't do it. Venturing into unknown lands like this only ever ends in disaster.
Click to expand...
Click to collapse
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
mG!X said:
Thanks for your response.
I made a full wipe with Twrp ( as mentionned in your tutorial ) and al steps run without issues.
The issue is that the next day i used the nethunter install tool instead of manually installing, in the steps for one plus one ( not oneplus 2) i mentionned the specific rom which can run on the phone but suddenly when i pushed next it was flashing stock for nexus ( and yes it's in the steps of oneplus1 :/ i verified ) , well i know that it's inadmissible and can brick it seriously
now i have the bulkusb when linked to windows8 and pressing on poweron+volumeup, what do you recommend please? there is no compatible driver for snapdragon 810?flashing to colorOS won't solve the issue please?
Thanks in advance
Click to expand...
Click to collapse
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Heisenberg said:
Well flashing ColorOS using the tool you have will attempt to flash ColorOS for the OnePlus One, because that tool is not for your device. As I said, don't use it, it's not for your device so it will only do more harm. I don't know if there's a recovery tool for the Two yet, I certainly haven't seen one.
Click to expand...
Click to collapse
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
mG!X said:
Ok, i will search maybe the drivers come out or someone find a solution, i ill contact support and seek their help also. Thanks and i will keep you updated if i find something
Click to expand...
Click to collapse
I just can say, your device is not hard bricked and will be recoverable.
You just need to be a bit patient. For the OPO, there was the ColorOs emergency recovery available (which helped me already 2x unbricking my OPO after I compiled a faulty kernel).
I just have not yet seen something similar for the OP2. But as you get the bulk_device still recognized via USB, this means the Qualcomm emergency boot loader is still intact and once the recovery stuff leaks somewhere, you will be able to fully recover your OP2.
Don't ask me when this will be available, think it also took weeks for the OPO before it was posted somewhere.
All the best!
Andi
mG!X said:
Thank you for your response, the issue is that it's hard bricked, so no recovery mode no led , nothing ..
i uninstalled the drivers ( even that i had the adb working before ) and the device is detectable now only with as QHSUSB_BULK
the installation of any adb usb driver don't change anything, only qualcomm usb drivers work ( i have the 9008 only but i'm think it's not compatible with OP2) i could manually change it to adb ( mobistel Cynus f4 ADB interface ) but nothing new..
Help plz
thanks again
Click to expand...
Click to collapse
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
yanick76 said:
You can try this (but with oxygenos), but I'm not sure if it works with OP2 snapdragon 810
https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/
EDIT: It seems you will need fastboot image of oxygenos and list of partitions ... anyway, good luck
Click to expand...
Click to collapse
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Heisenberg said:
It probably isn't the smartest idea in the world to recommend using a recovery tool from for an entirely different device unless you're 100% sure it's safe, which it probably isn't.
Click to expand...
Click to collapse
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
yanick76 said:
It's Qualcomm tool, but sadly OP2 is new device and there are no guides specific to OP2. He probably can resurrect his phone using QHSUSB_BULK device(*1)
EDIT: (*1) - It depends on correct driver and firmware files (images)
Click to expand...
Click to collapse
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Heisenberg said:
Yes, I'm aware that there is nothing specific available for the OP2. My point is that you're not even sure if this isn't going to damage the device further, let alone even help in any way.
Click to expand...
Click to collapse
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Just to assure you that the hard brick issue on OPT is completely curable since I've revived two OPTs. No panic needed. I will update the complete procedure as well as the necessary files later today.
yanick76 said:
His device is almost dead and this kind of damage is not covered by warranty. I think in this situation is not much to lose
Click to expand...
Click to collapse
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Heisenberg said:
His device is not almost dead, it's in a bricked "like" state right now but it can be easily fixed with the correct tool. What you're suggesting is not the correct tool for this device at all. If you're comfortable with being so reckless with someone else's device, good for you, I'm certainly not.
Click to expand...
Click to collapse
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
yanick76 said:
Yes I understand you but my post was meant as suggestion to way how to fix it, not guide. If you think my post can lead him to kill his device you can delete my post (because I can't), I have no problem with it
Click to expand...
Click to collapse
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
mG!X said:
Hi all
I bought the oneplus 2 4 days ago.
I rooted it, installed twrp and flashed nethunter2.0 CM12 then wiped cache , well the flash didn't go very successfully as the os still oxygen but i had all applications from nethunter installed and fully functional.
I decided to use the nethunter installer provided by the official site but not including the onplus2 version, i included the custom rom in replacement of the choosed one
.. but accidentally in the process of this tool it flashed stok for nexus which completely bricked the phone... nothing works, not boot no charge no sound...
I plugged again the phone and pressed for 20 seconds the power + volume up button and i got the bulk usb driver as it was a oneplus one .. i changed the driver settings to accept the unsigned drivers and updated the unkown device to the qualcomm 9008 ( as it was like a oneplus one ) .
The issue is that oneplus two has a Qualcomm MSM8994 Snapdragon 810 and the version i found for ColorOS is only for MSM8794 .. so i couldn't do anything
please can anyone help me?
any hint please?
Thank you in advance
Click to expand...
Click to collapse
Tutorial posted here http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Heisenberg said:
I know you were trying to help, but that advice is the wrong advice. I don't want/need to delete your post. My point here is to try to help you to understand why giving advice when you're not 100% understanding the situation properly isn't a great idea. On a site like this, accuracy and knowledge are paramount because it can be the difference between helping someone revive their device or completely killing it.
Click to expand...
Click to collapse
From this point I agree it was wrong advice.
I hope I never will be in situation like this But if, I will try to fix it based on what I suggest him + hours of google for correct files, correct drivers and correct download tool. I think this "misunderstood" was based on my advice like "here is direction and google for more", this is forum if he can find answer himself (google) he need not to ask for help here
Hey everyone, let me start off by saying I NEVER post anything and Ive been playing around on this website for years, but what happened to my Nexus 7 (grouper) last night was really very odd to me. I put together an old Nexus 7 (grouper) from parts laying around and had to reflash system, recovery, boot EVERYTHING. So i finally got it going and managed to flash over a NetHunter image, well as usual it got stuck in a bootloop I wasnt suprised with these snailtablets. So I shut it down and tried to play around with the NetHunter image and even the NetHunter Installer a few more times until I decided hell with it Ill just install PureNexus (my favorite/only) rom I use.
Well after it was done flashing It booted up to the main screen, when I saw the NetHunter wallpaper i was like WTF, well sure enough Ive got a full Kali NetHunter 3.0 chroot that runs flawlessly on top of my beloved PureNexus. I dont know why but this struck me as odd. I was always under the impression that Kali should be 1st and everything else after, I do not have multiROM or anything. Is this ouyt of the ordinary or have i been depraved of a tablet for to long? lol let m e know what yall think
AFAIK the procedure would be
unlocking bootloader
rooting
Flashing ROM
Falshing nethunter
Anyway - never did this before
I have the grouper/nakasi device
So I would gretly appreciate a step by step hint to start based on this hw with 5.1.1 (LMY47V) ROM aka Lollipop and maybe tools involved
OK, fouund a nice - real nice - guide here for PwnPad on the grouper tablet (Nexus 7 - 2012) - ouch wrong this is dealing with Nexus 7 (2013)
https://forum.xda-developers.com/showthread.php?t=2577356
Hey all !
Yesterday I downloaded Lineage OS 15.1 for my One Plus 2 (A2003).
Before this I was using Resurrection Remix OS and wanted to upgrade.
So I wiped everything except Internal Storage using TWRP and tried flashing the ROM. However, it gave back an error stating
This package is for "OnePlus2" devices; this is .
Click to expand...
Click to collapse
And I was stuck in between an uninstalled ROM and wiped device. So I tried connecting my device to my PC via ADB, and got the following message:
USB Device not recognised. The device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
I'm able to use ADB with my other devices, but my OP2 does not show up on connecting, both in Fastboot or ADB, neither on Linux nor on Windows.
After hours of trying, I decided to go for the UNBRICK HARD BRICK method and followed all the steps as stated in the forum. I used the QHUSB method and surprisingly my PC had detected the Port. After the 9th step, I had a custom recovery, but the device got stuck at Boot Logo, so I proceeded further.
Now, I've got stock recovery, wiped up system and the same USB error message stated above ^. I can't use ADB, fastboot because both of them are not showing any devices, neither on windows nor on ubuntu.
Please help !
Thanks in advance.
SOLUTION
The problem was with my wire, I used another OP Type C and everything works perfectly fine.
hmm, the mega unbrick guide worked for me. I'm surprised it isn't working for you.
I'd be really interested to hear your outcome, mine started giving me other issues after I got it back to a "working" state.
SOLVED
cyrus104 said:
hmm, the mega unbrick guide worked for me. I'm surprised it isn't working for you.
I'd be really interested to hear your outcome, mine started giving me other issues after I got it back to a "working" state.
Click to expand...
Click to collapse
I feel like a noob saying this, but the problem was with my wire.
Dr0nz3r said:
I feel like a noob saying this, but the problem was with my wire.
Click to expand...
Click to collapse
That fixes the connection issue. Can you tell me what did you do about the TWRP error ("This package is for "OnePlus2" devices; this is .")? I just got the same error when trying to update from a previous (November) Lineage unofficial rom to the latest build. I didn't change TWRP version, so I don't know why doesn't it recognize my phone correctly now...
EDIT: Other sources I just found suggest I may actually need to update TWRP after all, so I'll try that tomorrow.
UPDATE if anyone googles this as I did: indeed, updating TWRP fixed the problem. (though I only updated from 3.1.1.0 to 3.2.1.0)