I initially bricked my phone when I took an OTA update by accident while the phone was rooted. When I got the new phone I decided to let it update first and then try to root it but now the Gingerbreak/ZergRush method doesn't seem to work. It never reports that it failed but doesn't say success either, just the "Blue Hellions" thing. The script fails at the "adb remount" saying that the operation isn't permitted.
I've tried a few other methods but have had zero luck with them but most of them used ZR so I didn't expect a lot.
Since they don't seem to have a recovery image for this phone, there's not a lot I can do.
I'll take any ideas and upload logcat, etc.to help out (if I can...it seems to be about 100k which was double the allowed size for the last forum I asked this on)
Any and all help appreciated.
Kyocera Milano Root?
ehrichweiss said:
I initially bricked my phone when I took an OTA update by accident while the phone was rooted. When I got the new phone I decided to let it update first and then try to root it but now the Gingerbreak/ZergRush method doesn't seem to work. It never reports that it failed but doesn't say success either, just the "Blue Hellions" thing. The script fails at the "adb remount" saying that the operation isn't permitted.
I've tried a few other methods but have had zero luck with them but most of them used ZR so I didn't expect a lot.
Since they don't seem to have a recovery image for this phone, there's not a lot I can do.
I'll take any ideas and upload logcat, etc.to help out (if I can...it seems to be about 100k which was double the allowed size for the last forum I asked this on)
Any and all help appreciated.
Click to expand...
Click to collapse
My wife has same phone and I also have tried many diff ways to root this phone with no luck. If someone out there has a suggestion...plz offer... tired of sleeping on couch while Milano is acting up.:crying:
Root Milano patched 2.3.4 Gingerbread
hawkeyez731 said:
My wife has same phone and I also have tried many diff ways to root this phone with no luck. If someone out there has a suggestion...plz offer... tired of sleeping on couch while Milano is acting up.:crying:
Click to expand...
Click to collapse
I just got my phone from Ting a couple weeks ago and rooted it yesterday.
Unfortunately I can't directly post Outside links (Not at 10 posts yet, and have no idea what else to post about other than this at the moment, which requires a link (For Credit Due Purposes) and I know it will be helpful to people that were as desperate as me for something that was starting to seem rather impossible and no one was paying that much attention to it.), but this is important enough that I'll try to just chop it up - You'll just have to put it back together to go to that site.
This works:
androidforums
.com/milano-all-things
-root/709963-no
-pc-root-method
.html
Not sure why the guide says "Enable usb debugging in Settings, Applications, Development" since you never use the PC, I enabled it anyway, and also enabled to install third party apps, or else Poot won't install, not sure why that isn't on the guide. (Maybe they got mixed up?)
A few things you might want to know:
After hours I finally found the solution. But the terminal still doesn't work for uninstalling ("pm uninstall com.google.android.books.apk" = Failure), you have to do everything though your phone (I'm using the app "RootAppDelete"). The phone roots itself with a third party app called "Poot" using libraries from "Ministro 2"
Before doing this you're gonna need something like 25MBs of storage or so (Can delete everything afterwards with the exception of SuperUser (Can't delete that) to get the space back (Also, you need a app to actually use root actions). - The "Ministro 2" packages are huge for this phone's tiny internal storage! 11MB around)
Make sure to install anything small first and anything big right before the phone gets over 15MB full, because at that time you can't install anything else, with low memory errors.
Another thing that might have helped me when I did this is - back when I couldn't root I made all apps default install to the phone with the android sdk platform-tools (I didn't want to risk anything so I moved Poot, Ministro 2 and SuperUser back to the phone before running Poot. since they default installed to the SD)
"adb shell"
"pm SetInstallLocation 2"
Know its been said elsewhere, but this works with the Milano. Wanted to say that in case you needed the space to use Poot.
And the last problem is after I did all this, now my headphone jack wants to think it has headphones plugged in all the time, If I move the phone around it starts playing on the phone's speaker. It seems like something is lose. Not sure if that was caused by the root (since it wasn't doing it before, and I've never used the headphone jack before) or because there was lose hardware, not sure. Still working on a solution to that, which I found
something similar here, almost looks like a common problem: http://forum.xda-developers.com/showthread.php?t=817872
I would put my proof of doing this have a screen shot of root checker, but alas its an outside link. Understand though.
And as I've read a million times before this, here's a disclaimer: I'm not responsible and use at your own risk.
I have a samsung galaxy tab 2 7inch that is rooted and running a cyanogenmod 11(i think) nightly. So here's the story:
I was looking on google for a way to shut down my tablet through adb and came across "adb shell halt". After typing this, the screen immediately turned off and would not turn back on. After google searching I only found one person with the same problem. Looking into the "halt" command a bit more, I've learned that apparently it forcefully shuts down the Zygote which causes the Android system to forcefully close everything without giving anything a chance to save. Apparently the only thing left active is the Linux kernel, or at least that's what I've read. It's said that a battery pull can fix this, however I've repeatedly removed the battery, waited 15 minutes (and once overnight) and put the battery back in, only to constantly have the same result; it simply won't turn on, or at least show any signs that it is on. I've seen people saying that "adb shell start" will restart it, but I can't reconnect it to adb, I've tried several times. The only other thing I have seen is to mod the board and solder a chip to test pads that will allow me to communicate with the Linux kernel, but I'm hoping that there is another thing I can try first. If anyone can help me, I would REALLY appreciate it.
the100guy said:
I have a samsung galaxy tab 2 7inch that is rooted and running a cyanogenmod 11(i think) nightly. So here's the story:
I was looking on google for a way to shut down my tablet through adb and came across "adb shell halt". After typing this, the screen immediately turned off and would not turn back on. After google searching I only found one person with the same problem. Looking into the "halt" command a bit more, I've learned that apparently it forcefully shuts down the Zygote which causes the Android system to forcefully close everything without giving anything a chance to save. Apparently the only thing left active is the Linux kernel, or at least that's what I've read. It's said that a battery pull can fix this, however I've repeatedly removed the battery, waited 15 minutes (and once overnight) and put the battery back in, only to constantly have the same result; it simply won't turn on, or at least show any signs that it is on. I've seen people saying that "adb shell start" will restart it, but I can't reconnect it to adb, I've tried several times. The only other thing I have seen is to mod the board and solder a chip to test pads that will allow me to communicate with the Linux kernel, but I'm hoping that there is another thing I can try first. If anyone can help me, I would REALLY appreciate it.
Click to expand...
Click to collapse
Can you get into recovery or download mode? can you get your device to connected to pc via adb? if none of these, then that's the only way my friend.
Seems like i have same problem.I also had cyanogenmod11 runing for like 3-4 months before it simply...died 2 days ago.It does not respond to any charger/usb/ car charger/ battery pull. Even tried to power the motherboard on without any daughterboard connected.Still dead.
It's a P3110 (wifi).Any suggestions?Thanks alot, i can and i'm willing to try anything that does not include desoldering/soldering chips.Thanks alot
I'm going on a well educated guess that the EM756 is a very unpopular tablet, but I have a hard time believing that it's so unpopular that NO ONE has attempted rooting it.
Going on that hope (what little is left), let me explain why I'm having such a hard time.
I updated the tablet to the latest Android version. Somehow in doing so, it deleted all my accounts. I am unable to add a new one at all as I get the error "Unable to establish reliable connection". Rebooting my router and the device didn't work, nor did switching to another network. I have tried various workarounds and trick to work past it, but without having a google account to sign in with, the tablet is pretty useless as an account is needed to access things like the play store.
I finally read somewhere that there is a line of code I need to delete to get past the error or something to that effect, but to do it I need to root the tablet.
Every "One Click" tool I have used has failed (I've tried about 9 so far I think). The closest I got was using this guide on the forums here. My issue with that one is the programs provided don't see my device even after switching from MTP to PTP (At which point my computer doesn't recognize the device anyway)
I have spent a combined time of 16 hours trying to do this to no avail.... Any help would be nice by this point.
Bump.
rjvegeto said:
I'm going on a well educated guess that the EM756 is a very unpopular tablet, but I have a hard time believing that it's so unpopular that NO ONE has attempted rooting it.
Going on that hope (what little is left), let me explain why I'm having such a hard time.
I updated the tablet to the latest Android version. Somehow in doing so, it deleted all my accounts. I am unable to add a new one at all as I get the error "Unable to establish reliable connection". Rebooting my router and the device didn't work, nor did switching to another network. I have tried various workarounds and trick to work past it, but without having a google account to sign in with, the tablet is pretty useless as an account is needed to access things like the play store.
I finally read somewhere that there is a line of code I need to delete to get past the error or something to that effect, but to do it I need to root the tablet.
Every "One Click" tool I have used has failed (I've tried about 9 so far I think). The closest I got was using this guide on the forums here. My issue with that one is the programs provided don't see my device even after switching from MTP to PTP (At which point my computer doesn't recognize the device anyway)
I have spent a combined time of 16 hours trying to do this to no avail.... Any help would be nice by this point.
Click to expand...
Click to collapse
Hi
Thanks for using XDA Assist.
I believe kingroot works on the EM756 > Android Development and Hacking > Android Apps and Games > [ROOT ANDROID][2.x-5.1] KINGROOT: The One-Click Root Tool for Almost All Devices . I noticed another user in that thread got it to work.
Good luck
tl;dr: I managed to soft-brick my Fire HD 10 (7th Gen) by trying to use the KingoRoot APK. I've managed to mostly recover, but it was a pain in the neck.
THE SITUATION: There's a popular thread at the moment showing how to get root access on your Kindle Fire HD 10 (7th Gen). This sounded pretty exciting to me because I had a 5th gen HD 10 that I rooted soon after I got it, and one of the few things I felt was missing from the new toy I bought myself for Christmas was root access.
There was one hitch, though. The root process Bibikalka describes in his tutorial requires you to download, install and run a Windows version of the KingoRoot rooting app. All well and good for the many people out there who have Windows machines, but I am a dedicated Linux and Mac user and don't have access to a Windows computer. Kingo doesn't have a version for those platforms.
It does, however, have a version for Android itself, so I decided what the heck, I can give that a try. Odds are good that if they have a rooting solution for Windows, it's present in the Android version, right?
Right??
THE SETUP: So I removed my SD card for safekeeping (nothing on it but tunes, books and videos) and plugged in my USB cable. I'd done a fair amount of ADB work before so the tablet was already set up for USB debugging and to accept APKs from unknown sources. I successfully installed the KingoRoot APK after downloading it from their site, launched it and sat back to watch what happened.
KingoRoot seemed to progress about like I would have expected, except that it stalled three times, once at 40%, once at 70% and once at 90%. When it hit 90% I waited for a few minutes to see if it would give me any kind of yea-or-nay as to whether the tablet was rooted (it never did), and then went back to the ADB window and opened up an ADB shell session to see if I could figure out what was going on.
Code:
adb shell
[email protected]:/ $ su
[email protected]:/ #
Success! I had a root prompt! I immediately started following some of the steps in the tutorial and contemplating how I was going to accomplish some of the other steps I'd done on other Fires, like replacing Amazon's launcher with my beloved Nova.
After about fifteen minutes, though, I began to wonder why KingoRoot was still showing 90%. Surely it should have finished by now? so I used ADB to reboot the tablet. That's where the fun started, and by "fun" I mean "pain."
THE SINKING FEELING: I rebooted the tablet, watched the Amazon logo come up, followed by the Fire logo. And I watched the Fire logo. And I watched it cycle through its animation for at least five minutes. At the same time I opened another ADB session, and I could still get a root prompt by running the "su" command, and some other onboard commands like "ps" and "du" worked fine, but once I returned to ADB I found that I couldn't install or uninstall APKs, just to use an example. The command would launch but then hang, and I would have to control-C out of it to get back to my Mac shell prompt.
After about fifteen minutes I started getting this sinking feeling that I had just reduced my nice, big, shiny toy to a thin plastic box that did the visual equivalent of screaming its name over and over again.
THE RECOVERY: By this time I was pretty sure I had hosed my tablet, so nothing ventured, nothing gained. I downloaded the latest Fire HD 10 firmware update from Amazon, watching all the while as it continued to cycle through the Fire logo. When the update was downloaded I booted into the recovery menu, sideloaded the update, and watched nervously as the tablet updated, restarted and . . . went right back to cycling through the Fire logo animation. Head, meet desk.
Then, suddenly, the message that my tablet was optimizing its programs! I have never been so happy to see that particular piece of annoying information. About ten minutes later after re-registering the tablet and completing setup I was right back where I had started when I first bought the device. No Google Play Store, no Nova Launcher, no Ticket to Ride or other favorite games, but it was working.
That sudden gust of wind you heard was my exhaling a sigh of relief.
LATHER, RINSE, REPEAT: Now that I had a blank slate, as it were, and knew that I could recover when I needed to, I decided to try the process once again just to make sure I hadn't missed any steps or done something out of sequence. Long story short, I ended up with an unusable tablet again and had to reload the Fire firmware update.
THE TAKEAWAY: I am posting this as a cautionary tale. I was lucky in that all of my music files, videos and downloaded books live on my SD card so all I lost in this process was some time and customization. It could have been much, much worse.
Until someone can document success with it and explain how they did it, please don't try to root your Kindle Fire HD 10 (7th Edition 2017) using the APK version of KingoRoot. Use the desktop version of the software documented elsewhere in the forums. You'll be happier and more likely to succeed.
Best of luck to you!
I am posting this to share my experience with HD8 (7th Gen) OS 5.3.3.0 using KingoRoot APK.
The purpose is to share the experience that : when KingoRoot stuck at 90%, it might take as long as 30 minutes for KingoRoot to finish.
Here is my note from 12-23-2017:
https://root-apk.kingoapp.com
Kingo ROOT APK version v.4.3.4
(1). Un-check “Install recommended app”
(2). Tap “One Click Root” at the bottom of the screen
(3). In 10 seconds, the status indicator reached 90% and stuck there.
(4). After 30 minutes, it finished with tablet screen displaying: ROOT FAILED & Error Code: 0x1323F7
Dan_firehd said:
I am posting this to share my experience with HD8 (7th Gen) OS 5.3.3.0 using KingoRoot APK.
The purpose is to share the experience that : when KingoRoot stuck at 90%, it might take as long as 30 minutes for KingoRoot to finish.
Here is my note from 12-23-2017:
https://root-apk.kingoapp.com
Kingo ROOT APK version v.4.3.4
(1). Un-check “Install recommended app”
(2). Tap “One Click Root” at the bottom of the screen
(3). In 10 seconds, the status indicator reached 90% and stuck there.
(4). After 30 minutes, it finished with tablet screen displaying: ROOT FAILED & Error Code: 0x1323F7
Click to expand...
Click to collapse
I will admit to the possibility that I was impatient.
Let me try it again. I mean, I do have a clean tablet at the moment . . .
NerdFire said:
I will admit to the possibility that I was impatient.
Let me try it again. I mean, I do have a clean tablet at the moment . . .
Click to expand...
Click to collapse
Please do let us know whether you are successful.
Best of luck.
NerdFire said:
tl;dr: I managed to soft-brick my Fire HD 10 (7th Gen) by trying to use the KingoRoot APK. I've managed to mostly recover, but it was a pain in the neck.
THE SITUATION: There's a popular thread at the moment showing how to get root access on your Kindle Fire HD 10 (7th Gen). This sounded pretty exciting to me because I had a 5th gen HD 10 that I rooted soon after I got it, and one of the few things I felt was missing from the new toy I bought myself for Christmas was root access.
There was one hitch, though. The root process Bibikalka describes in his tutorial requires you to download, install and run a Windows version of the KingoRoot rooting app. All well and good for the many people out there who have Windows machines, but I am a dedicated Linux and Mac user and don't have access to a Windows computer. Kingo doesn't have a version for those platforms.
It does, however, have a version for Android itself, so I decided what the heck, I can give that a try. Odds are good that if they have a rooting solution for Windows, it's present in the Android version, right?
Right??
THE SETUP: So I removed my SD card for safekeeping (nothing on it but tunes, books and videos) and plugged in my USB cable. I'd done a fair amount of ADB work before so the tablet was already set up for USB debugging and to accept APKs from unknown sources. I successfully installed the KingoRoot APK after downloading it from their site, launched it and sat back to watch what happened.
KingoRoot seemed to progress about like I would have expected, except that it stalled three times, once at 40%, once at 70% and once at 90%. When it hit 90% I waited for a few minutes to see if it would give me any kind of yea-or-nay as to whether the tablet was rooted (it never did), and then went back to the ADB window and opened up an ADB shell session to see if I could figure out what was going on.
Success! I had a root prompt! I immediately started following some of the steps in the tutorial and contemplating how I was going to accomplish some of the other steps I'd done on other Fires, like replacing Amazon's launcher with my beloved Nova.
After about fifteen minutes, though, I began to wonder why KingoRoot was still showing 90%. Surely it should have finished by now? so I used ADB to reboot the tablet. That's where the fun started, and by "fun" I mean "pain."
THE SINKING FEELING: I rebooted the tablet, watched the Amazon logo come up, followed by the Fire logo. And I watched the Fire logo. And I watched it cycle through its animation for at least five minutes. At the same time I opened another ADB session, and I could still get a root prompt by running the "su" command, and some other onboard commands like "ps" and "du" worked fine, but once I returned to ADB I found that I couldn't install or uninstall APKs, just to use an example. The command would launch but then hang, and I would have to control-C out of it to get back to my Mac shell prompt.
After about fifteen minutes I started getting this sinking feeling that I had just reduced my nice, big, shiny toy to a thin plastic box that did the visual equivalent of screaming its name over and over again.
THE RECOVERY: By this time I was pretty sure I had hosed my tablet, so nothing ventured, nothing gained. I downloaded the latest Fire HD 10 firmware update from Amazon, watching all the while as it continued to cycle through the Fire logo. When the update was downloaded I booted into the recovery menu, sideloaded the update, and watched nervously as the tablet updated, restarted and . . . went right back to cycling through the Fire logo animation. Head, meet desk.
Then, suddenly, the message that my tablet was optimizing its programs! I have never been so happy to see that particular piece of annoying information. About ten minutes later after re-registering the tablet and completing setup I was right back where I had started when I first bought the device. No Google Play Store, no Nova Launcher, no Ticket to Ride or other favorite games, but it was working.
That sudden gust of wind you heard was my exhaling a sigh of relief.
LATHER, RINSE, REPEAT: Now that I had a blank slate, as it were, and knew that I could recover when I needed to, I decided to try the process once again just to make sure I hadn't missed any steps or done something out of sequence. Long story short, I ended up with an unusable tablet again and had to reload the Fire firmware update.
THE TAKEAWAY: I am posting this as a cautionary tale. I was lucky in that all of my music files, videos and downloaded books live on my SD card so all I lost in this process was some time and customization. It could have been much, much worse.
Until someone can document success with it and explain how they did it, please don't try to root your Kindle Fire HD 10 (7th Edition 2017) using the APK version of KingoRoot. Use the desktop version of the software documented elsewhere in the forums. You'll be happier and more likely to succeed.
Best of luck to you!
Click to expand...
Click to collapse
You can easily install kingoroot pc on a virtual box windows vm (freely available from Microsoft for testing IE) and root that way. I too only have a Mac and it works fine.
NerdFire said:
I will admit to the possibility that I was impatient.
Let me try it again. I mean, I do have a clean tablet at the moment . . .
Click to expand...
Click to collapse
Why not do something actually useful with your life (err.. tablet)?
Once you get root prompt in adb (#), start my guide from Step 13.
You may need to figure out the exact name of the Kingoroot app, run the command below and then figure out which app names to feed to "adb uninstall":
Code:
adb pm list packages -3
You can run this command before installing Kingoroot apk, so you have the baseline.
The impact I'd be hoping for is that before Kingoroot finishes, you'd already uninstall it (how is that for a nice twist?). A working 'su' that it leaves behind could be sufficient for SuperSu to install itself, and you'll be in business (without needing a PC to run Kingoroot).
bibikalka said:
Why not do something actually useful with your life (err.. tablet)? .
Click to expand...
Click to collapse
Sure, why not, I mean there's a first time for everything.
bibikalka said:
Once you get root prompt in adb (#), start my guide from Step 13.
You may need to figure out the exact name of the Kingoroot app, run the command below and then figure out which app names to feed to "adb uninstall":
Code:
adb pm list packages -3
You can run this command before installing Kingoroot apk, so you have the baseline.
The impact I'd be hoping for is that before Kingoroot finishes, you'd already uninstall it (how is that for a nice twist?). A working 'su' that it leaves behind could be sufficient for SuperSu to install itself, and you'll be in business (without needing a PC to run Kingoroot).
Click to expand...
Click to collapse
That's a nifty command. Maybe it can help me get a handle on what Kingo is doing so I can undo just enough of it to keep it from preventing me from running "adb install" or "adb uninstall" once I've achieved root.
By the way, THANK YOU for posting the tutorial. I hope eventually to get to where either I can use the APK to root my tablet (which I will happily document if I can get it figured out) or use some other workaround like the Windows Virtualbox VM trick.
UPDATE 1-5-2018 1850 UTC: Well, it was worth a try, and this time for whatever reason I managed to obtain root access much faster than I had before. Unfortunately that's still where the process comes to a screeching halt. Step 13 works (I'm able to remount /system as RW instead of RO) but I am still unable to install SuperSU, or run "adb shell pm" or indeed do anything that has to do with package management, including "adb install", "adb uninstall", "adb shell pm" or "ad shell am". Something is still blocking any such processes from completing, whether run from adb or on the tablet itself, which I'm sure is why the tablet never gets past the Fire logo after rebooting.
I'm still investigating but also leaning heavily toward just running the process from a Windows Virtualbox once I gather all the pieces I'll need, like a Windows version of ADB.
Blaiser47 said:
You can easily install kingoroot pc on a virtual box windows vm (freely available from Microsoft for testing IE) and root that way. I too only have a Mac and it works fine.
Click to expand...
Click to collapse
Easy?? Ha-ha, it is to laugh. I've been fighting with my virtualbox setup all morning and can't get it to recognize the Fire as anything other than an MTP device.
I'm sure it's a driver issue. Should I be using driver files other than the ones that came with the standalone ADB in the OP? And if so, what files do I need?
NerdFire said:
...
By the way, THANK YOU for posting the tutorial. I hope eventually to get to where either I can use the APK to root my tablet (which I will happily document if I can get it figured out) or use some other workaround like the Windows Virtualbox VM trick.
Click to expand...
Click to collapse
No problem! I hope you can use it at some point !
NerdFire said:
UPDATE 1-5-2018 1850 UTC: Well, it was worth a try, and this time for whatever reason I managed to obtain root access much faster than I had before. Unfortunately that's still where the process comes to a screeching halt. Step 13 works (I'm able to remount /system as RW instead of RO) but I am still unable to install SuperSU, or run "adb shell pm" or indeed do anything that has to do with package management, including "adb install", "adb uninstall", "adb shell pm" or "ad shell am". Something is still blocking any such processes from completing, whether run from adb or on the tablet itself, which I'm sure is why the tablet never gets past the Fire logo after rebooting.
I'm still investigating but also leaning heavily toward just running the process from a Windows Virtualbox once I gather all the pieces I'll need, like a Windows version of ADB.
Click to expand...
Click to collapse
Good test! I remember now rooting something else with Kingroot apk, and it'd have similar unpleasant behavior, I think I ended up having to do a factory reset to get rid of it. I guess Kingoroot apk hangs the package manager, and then it's all downhill from there. If one could hunt down the corresponding process, there could be a way to kill Kingoroot. But who knows ...
NerdFire said:
Easy?? Ha-ha, it is to laugh. I've been fighting with my virtualbox setup all morning and can't get it to recognize the Fire as anything other than an MTP device.
I'm sure it's a driver issue. Should I be using driver files other than the ones that came with the standalone ADB in the OP? And if so, what files do I need?
Click to expand...
Click to collapse
Yes. I can't remember exactly where but there are explicit directions for fire specific drivers. If memory serves me correct it is all on Amazon's website. Try searching there. If you can't find it let me know and I can try to find it again
Edit. Found it quickly. Follow this and see if you can get the to recognize it...
https://developer.amazon.com/docs/fire-tablets/ft-set-up-your-kindle-fire-tablet-for-testing.html
Can you report back the results of VIrtual Box? I am a Mac user too
I had gone the same process and soft bricked the tablet.
Updated 31 May 2020
I had done the adb sideload process and successfully solve the issue.
Yikes!
I just did the same thing on my device HD 10 7th Gen.
It will not bootup and my head is spinning around around as all I wanted to do was install lineageOS.
Can you please tell me exactly what I would need to sideload to get this device back up and running. I am using a Mac to do adb commands. My device is not rooted, I have no twrp recovery, I cannot boot up to the desktop.
Thank you friend
Problems about "dev/block/loop", I/O error, and iosetup failed 1 Android-x86
So, I've been using Android-x86 for years without any problems, until recently.
A while ago, while I was playing some games on my previous Android-x86, my wifi died all of a sudden, and since I don't have anything else to do without an internet connection to it, I turned off my laptop and reboot when the wifi is back up.
While rebooting, I was then stuck in an infinite loop on the splash screen (which had happened a few times already), prompting me to reinstall Android-x86 (as per usual) because I can't think of any other method to fix it.
Normally, everything would be just fine, I just need to enable native bridge to be able to play the games I usually play, but this time something was off, and almost every games I used to play crash right away as if native bridge hadn't been enabled (which it was).
So I looked up to try finding a solution, and came across a guide to manually install houdini.sfs through terminal console, and the following kept happening:
mount: dev/block/loop(xx) I/O error
or
mount: iosetup failed 1
I absolutely have no idea what's causing this, and I can't find anything that talks about this error, and I hope I can find an answer here
Thank you for your time in advance