Loop Device Support - Galaxy Tab 4 Q&A, Help & Troubleshooting

Hey all,
I've got a Galaxy Tab 4 8.0 (milletwifi), and I was trying to install Kali Linux trough Linux Deploy, but after a few attemps, I discovered that that problem was that I didn't have Loop Device support.
Is there any kernel that enables it? Or any mod/method that let me run Kali without Loop Device?
EDIT: I ran Loop Device Checker, and it told me that I have Support, but the Linux Deploy says I don't have it. Sooo
I would appreciate your answer.

Related

Bricked Lenovo Yoga 10 HD+ Tablet

Hi Everyone,
My tablet is Lenovo B8080-F model, 16GB with Wifi. I got it rooted and installed TWRP on it. I was so over excited about this and wanted to flash custom ROMs on it. I searched and could not get the proper ROM for the B8080-F, in my eagerness, I decided to flash the ROM for Lenovo A3000. Since then my tablet could not boot up again. It got stuck at the Lenovo logo. My windows system can still detect the tablet when plugged to the PC, but ADB DEVICES command shows nothing.
I need help. I need step-by-step guides on how to revive the tablet. I appreciate.
Muyiwa.
Update:
My PC can detect the device. It is shown as Android ADB Interface under Windows Device Manager. There is no COM Port.
If I type: adb devices
Response: ? Unauthorized.
Please help!
Thanks.
Muyiwa.
Ouch
Me too, i need help
I actually have such an tablet lying around. Haven't been used in five years. Never got custom ROMs, right? I don't think Lenovo ever bothered to upgrade from Kitkat.
@[email protected]
@Mirage20000C

SM-G570F Doesnt get into Recovery Mode and Download mode stuck at logo

Samsung Galaxy J5 Prime - SM-G570F
Build - MMB29K.G570FXXU1AQB5
OS - Android Marshmallow 6.0.1
I tried to root the OS. I managed to connect to ODIN and did a recovery from a recovery file shared over internet. However that recovery has a password pattern which didn't allow me to access my phone. After several attempts phone showed a message saying that phone will reset to factory settings. After which phone stuck at Initial LOGO.
Please provide some inputs in getting my phone operational.
Dear Experts, Please help!
android_sriniram said:
Samsung Galaxy J5 Prime - SM-G570F
Build - MMB29K.G570FXXU1AQB5
OS - Android Marshmallow 6.0.1
I tried to root the OS. I managed to connect to ODIN and did a recovery from a recovery file shared over internet. However that recovery has a password pattern which didn't allow me to access my phone. After several attempts phone showed a message saying that phone will reset to factory settings. After which phone stuck at Initial LOGO.
Please provide some inputs in getting my phone operational.
Click to expand...
Click to collapse
There may be two things which may be done
1. Since you've done factory reset The first boot may take some time so wait for 20min and make sure it's working
2. If it's not working yet . Then the recovery file you've have flashed is wrong or you've flashed in the wrong partition . There is also chance that you've interupted the process.
These flashing tools are somewhat complicated I've faced many problems because if any settings weren't set correctly then it would mess all your mobile and also the version you use is very important..
So, contact the developers who are working for the specified mobile for more help. Because they would have over come these issues .
Suggestion:- Never Experiment the odin on your mobile without knowing the every detail before

Unable to hack Asus Zenfone Laser 2 [ZE550KL - Z00L - Z00LD]

Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Uhm... no replies till now?
i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help
When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere
I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.
Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.
These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.

Android OS deleted

I accidentally deleted Android system OS while in TWRP. Now I can boot into download mode and soft reset mode. I am unable to boot into recovery mode. When I boot into rest mode the Samsung S8 displays and stays there.
I have Samsung ADB drivers installed in my Win 10 laptop. It i can detect my other Samsung phones but not my S8 thus I am unable to flash the stock Android 9 ROM with odin nor the all in one Samfirms tool AIO V2.1
My local Samsung service centre technicians told me its a motherboard problem but I don' t agree as it should be a software problem
Please advise next course of action. Thanks in advance!

Galaxy A40 OS 11 root problem

Hi all, i have a problem with my galaxy A40 (OS android 11 One UI 3.1).
I want to root the phone but I have the volume buttons not working (broken).
I have the developer option already activated and OEM and USB Debug are already active.
I have followed several guides but I come to a point where I always get stuck because the phone gives errors and I don't know how to fix. ( Kingroot stuck at 1% doesn't work, i was using odin and magisk but i have problems)
Does anyone have an updated guide to this period dedicated to this smartphone? Thank you
Sorry for my language

Categories

Resources