Related
After a long time it's a moment to realease HTC HD2 ToolBox app with HBL. Small app that will allow you to boot linux inside android, and display everything on screen or through VNC connection. ToolBox app is also redesigned and added some new functions.
In pack is barebone debian distro with xfce4 interface.
There is also posibility that this app and HBL will work on other phones like leo (desire, nexus one ...)
Everything else you need to know is in Readme file.
Bug reports or suggestions on this thread, i'll answer when i'll get some time.
Enjoy !!!
EDIT: I added Readme file to this post so lazy people can read everything before downloading pack, or asking silly questions!
EDIT 2: I'm currently working on support for sdcard roms and other non-working builds. Also i would like to mention that is possible to run ANY linux distro with HBL (with some modifications) or even to run another android rom!
So consider this early versions only as "technology preview", more support and bug-fixes in next few days...
P.S Thank you all for your support !
Download Link
wow awesome
Does it work within Android like vns versions?
I've been waiting for (something similar, but this should do the work) such an app.
Thank you.
@hd# ..
Read the "Read-me" file ?
been waiting for this too.
But my broadband is down and I've already exceeded my monthly data allowance using wifi tether (500mb !!!)
... might have to do it anyway
Edit; still downloading... I assume there is no sound enabled on this
hi
can i boot ubuntu with it?
hi first big thanks for your hard work.
now i need some help to get linux running from HBL.
i´m using kingdom sense3 rom from dungphp.
i installed hd2 toolbox and copied linux folder to root of sd card.
i installed HBL (Busybos is installed in version 1.19.x.x) i took rootexplorer and give /system/bin/ write permissions for owner/groups/others.
But i need initd support: what i have to do to get this?? or is it on my rom?
please help cause at the moment i´ve bootloops everytime i want to boot linux.
Thank's a lot for this! I've been waiting for this for for a while!!!
So if I understand this right.... which I don't think I did at first..... this is basically the same thing as booting ubuntu and connecting to it with vnc, the ubuntu that is in another thread.... i ask because what I am looking for is usb host support.... which I don't believe is possible with the other ubuntu that boots in android.... and I think if I undestand this right... is not possible with this one either......i do appreciate the work done on this app a lot.... but to me, it's useless unless usbhost is supported because of tiny menus and buttons not being easily clickable with fingers..... so I want to use my wireless mouse that has a usb receiever......
edit: download finally finished, I tried it out.... I really like it, couple questions.... is it normal for shutdown not to work? I chose to boot and show on local screen instead of vnc..... when I did that, it started fine, I messed around a little, then tried to shutdown... it said shutdown command failed or something similar.... then rebooted android..... and when you choose to boot on local screen, is this kicking android out so it's only linux, kind of like haret and booting android from winmo off sd? And last, is it possible for usbhost?
Edit2: I could barely see the text at the bottom of the hotboot screen that says to use log out feature to return to android... I did that instead of shutdown, there were no errors and it went to my android boot animation, then booted back to android just fine.....
Its working well. Thanks .I have the same question as Diesburg does. One more how to make right click.
diesburg said:
So if I understand this right.... which I don't think I did at first..... this is basically the same thing as booting ubuntu and connecting to it with vnc, the ubuntu that is in another thread.... i ask because what I am looking for is usb host support.... which I don't believe is possible with the other ubuntu that boots in android.... and I think if I undestand this right... is not possible with this one either......i do appreciate the work done on this app a lot.... but to me, it's useless unless usbhost is supported because of tiny menus and buttons not being easily clickable with fingers..... so I want to use my wireless mouse that has a usb receiever......
edit: download finally finished, I tried it out.... I really like it, couple questions.... is it normal for shutdown not to work? I chose to boot and show on local screen instead of vnc..... when I did that, it started fine, I messed around a little, then tried to shutdown... it said shutdown command failed or something similar.... then rebooted android..... and when you choose to boot on local screen, is this kicking android out so it's only linux, kind of like haret and booting android from winmo off sd? And last, is it possible for usbhost?
Edit2: I could barely see the text at the bottom of the hotboot screen that says to use log out feature to return to android... I did that instead of shutdown, there were no errors and it went to my android boot animation, then booted back to android just fine.....
Click to expand...
Click to collapse
HBL actually shuts down all android processes (except init and some critical ones) and then switches to linux. It's normal for shutdown not to work right now, in future it will work but for now use log out to exit from linux. USB Host support for now is not possible without modified kernel, but i'm working on custom kernel with usb-host/normal mode switching.
I must admit i didn't have much time to work on this project so many things can be improved, and i hope in fallowing days/weeks i will have much needed time to work on it. So everything is still a "prototype"!
@alltome
99.99% of custom roms have init.d support, just check if you have init.d directory in /etc.
Hi managed to install HBL but when I try to start linux using local screen the screen just hangs on "loading linux..." for ages. Tried vnc but doesn't work either. it doesn't seem to start shutting down android because if I press hardkey back button the phone is normal.
tried changing "writtable" statuses on the mount screen, but no joy. Is this what you mean by " writable /system/bin folder", or must I use rootexplorer?
Many thanks
u rock
hey dan1j3l HBL works flawlessly
keep on rockin'
Robbie P said:
Hi managed to install HBL but when I try to start linux using local screen the screen just hangs on "loading linux..." for ages. Tried vnc but doesn't work either. it doesn't seem to start shutting down android because if I press hardkey back button the phone is normal.
tried changing "writtable" statuses on the mount screen, but no joy. Is this what you mean by " writable /system/bin folder", or must I use rootexplorer?
Many thanks
Click to expand...
Click to collapse
The same problem for me, stuck at "HTC HD2 ToolBox loading linux.." screen
I'm using MIUI Offician 1.5.20
All those with problems starting HBL can you send me output of these few commands so i can get more info (use adb shell)
busybox ps | grep hbl
busybox mount
busybox ls -la /system/bin/hbl
busybox ls -la /etc/init.d
busybox df -h
Hello dan1j3l First of all I'd like to Thank you for your hard work and this cool app which has great potential...
now that being said, I'm also having some troubles like stated above from other users i managed to install HBL (i think, cause i got the success message when clicking install HBL) but when I try to start linux using local screen, the screen just hangs on "loading/booting linux..."
Below i attached the output from commands on adb shell
Have the info you wanted.
Thanks dan1j3l
Have also added signature below
Robbie P said:
Have also added signature below
Click to expand...
Click to collapse
Hmm... I see you are using sdcard rom, never tested HBL with sdcard roms. It seems i need to make a different installer for sdcard builds... I will try to test it this weekend, then i will know more.
when i try to start hbl my phone vibrates two times and restarts. but it starts already with the bootanimation. then it boots back to android.
i'm using ndt miui. busybox is installed and linux image is in the root of the sdcard in linux folder.
Howdy folks,
Yesterday, I was the proud owner of a sleek little TCT.Alcatel OneTouch A554C, formally know as a Virgin Mobile Venture running Android version 2.3.5.
It was successfully and surprisingly easy to root by utilizing 2 cool little apps, Ministro and Poot-Debug.
After root, I subsequently downloaded some root tools (eg., Titanium Backup Pro, Superuser Elite, System App Uninstaller).
That was last week.
Yesterday, I got a bit cocky. I needed to clear up some internal memory so I used "System App Uninstaller" to uninstall a few apps. If I remember correctly, the apps were as follows: Google Maps, Google Maps Street View, Calculator, Digital Clock, Setup Wizard, Android Live Wallpaper, Live Wallpaper Picker, Magic Smoke Wallpaper, Music Visualization Wallpaper, and the TouchPal Keyboard French and Spanish Language Packs.
So far so good, right? However, I believe I may have snarfed-up when I uninstalled the Setup Wizard. But I'll get to that in a minute.
Now with Titanium Backup, I moved some apps to the sd card. Included was the stock launcher, Smart Launcher Pro, SPB Shell, AVG Anti-Virus, and Superuser Elite. Then I rebooted through Titanium Backup and I haven't viewed any pornographic material since!
After reboot, the phone got stuck on the final boot animation frame. I panicked, pulled the battery, booted into recovery then rebooted a 2nd time.
This time it booted to the pull-down lock screen. I unlocked and seen:
"Sorry! The application com.android.setup wizard has stopped unexpectedly. Please try again." Along with a "Force Close" option. I forced closed and the screen went black with the exception of the status bar. The phone is still on but otherwise...nada.
When I press the power button, same thing happens: pull-down lock screen, screen goes black. Or sometimes, it will turn on and boot loop.
Major panic time!!! I booted into recovery again and performed a factory reset to no avail.
Another clue to note: I can connect & access the sd card via usb to desktop.
Also, I did have the good sense to backup all apps, system and user, through ES File Explorer and stored them both on sd card and in the cloud via Yandex Disk prior to this bricking fiasco. Now, what do I do with them? I now realize it was possibly a mistake moving all 3 launchers to the sd card. How do I get the stock launcher back to the phone?
Or, should I:
1- Attempt a base rom reinstall or
2- Attempt a custom rom install or
3- Use it solely as a time piece/mass storage device or
4- Throw it very hard and very ******* far away from me!?
I realize this is an obscure little cheap phone but it's the only one I have. Any valid feedback would be greatly appreciated.
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
es0tericcha0s said:
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
Click to expand...
Click to collapse
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Silver Rivers said:
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Click to expand...
Click to collapse
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
es0tericcha0s said:
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
Click to expand...
Click to collapse
Well, on these PCs it certainly does. I thought I was on track yesterday and tried to install a copy of Odin that I found. Can't install without a frigging admin pass.
Someone else just suggested I try a stock rom flash. Might as well, right? Happen to know where I could find a good reliable copy? That also happens to be free?
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
Click to expand...
Click to collapse
Yeah, me either. I was all over the place yesterday grasping at anything. So Odin is only for Samsungs, huh? Guess I can delete the exe file from my sd.
Right then. I'm about to proceed with your advice. Cross your fingers and toes.
Thanks mate!
The CWM img will need to be in the folder you unzipped for adb/fastboot.
Click to expand...
Click to collapse
and
launcher apk must be in adb folder then while in CWM
Click to expand...
Click to collapse
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Silver Rivers said:
and
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Click to expand...
Click to collapse
Sorry, I meant in the folder that it extracts the files too.
es0tericcha0s said:
Sorry, I meant in the folder that it extracts the files too.
Click to expand...
Click to collapse
Right, got it.
Silver Rivers said:
Right, got it.
Click to expand...
Click to collapse
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
es0tericcha0s said:
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
Click to expand...
Click to collapse
That would be really cool, actually. But check this out:
I talked someone into allowing me to utilize his laptop. I installed ADB, moved the Launcher APK to the folder suggested, ran the commands but the command prompter responded with "waiting for device" and progressed no further. Could it be a driver issue? I was under the impression that if the PC recognizes your device (which it did) then a new driver install was not necessary.
Dude was real cool about it even though I ran his battery down quite significantly and didn't even accomplish anything.
So, if I had the ADB files then I could just copy them to...say the PC desktop and run the command prompter from there? If so, then yes please upload and I'll just try it that route rather than rely on someone's personal PC. Know what i mean?
I do appreciate all of this. I'm getting quite the education here. If you ever get married, let me know and I'll come and dance as my favor to you.:good:
Peace...I'll return tomorrow.
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
es0tericcha0s said:
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
Click to expand...
Click to collapse
I was in Recovery and I was also attempting to install the just the Launcher versus the entire ROM. And I was also feeling a tad bit rushed, cause dude was right there informing me of his battery status. "Well, it's down to 30%." Then 2 mins later.."Ok, looks like it just fell to 25%."
Haha...so yeah, with him pressuring me, I spaced on checking the device manager. This desktop that I'm on today seems to be cool. Just checked the manager & it informs me that my device is 'working properly'.
Off to give it another bloody joust, mate. Wish me luck...
Can you fully explain how to do this
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
Click to expand...
Click to collapse
I have a old ass iMac desktop that has not been used in 5plus years at all and I'm a mother of 3 with no clue how to do any of this if you can dumb it down for me that would be very help full as well I have no clue where to download any of the needed files please help. My email is [email protected]
Thank you
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...
This is my first time posting on the website so I apologise ahead of time. I am trying to dual boot my laptop with Remix OS. It is the Asus ROG GL551JW-DS71 (i7 4720hq, 16 gb ram, 1 tb hdd, gtx 960m, windows 8.1, if anything else is needed, let me know). I've done some research and it seems that it might be an issue with my GPU. I've tried putting the "nouveau.modeset =" and what not but I can't get it to load past the "ANDROID [email protected]_x86_64:/ #" I put "DEBUG=1" in the Grub line thing and I took pictures of my screen. I'm not sure what site you guys would like me to use to upload so I'll upload them once someone lets me know. Thanks in advance!
Have you searched for a disable dedicated/discrete graphics in BIOS? You need to disable it, because Remix will not boot with your GTX960M enabled.
If you don't have that option, then I'm sorry but for now you will be able to boot only using software rendering; graphics handled by the CPU. This means a less stable experience and less performance, but it will work 100%
Add this in the kernel grub line:
Code:
androidboot.swrast=1
Sent from mobile
ethansky said:
This is my first time posting on the website so I apologise ahead of time. I am trying to dual boot my laptop with Remix OS. It is the Asus ROG GL551JW-DS71 (i7 4720hq, 16 gb ram, 1 tb hdd, gtx 960m, windows 8.1, if anything else is needed, let me know). I've done some research and it seems that it might be an issue with my GPU. I've tried putting the "nouveau.modeset =" and what not but I can't get it to load past the "ANDROID [email protected]_x86_64:/ #" I put "DEBUG=1" in the Grub line thing and I took pictures of my screen. I'm not sure what site you guys would like me to use to upload so I'll upload them once someone lets me know. Thanks in advance!
Click to expand...
Click to collapse
Try to add "nomodeset" instead of "nouveau.modeset =".
nomodeset might work, but it's highly unlikely.
I've made a guide for these kind of problems today: http://forum.xda-developers.com/remix/remix-os/solution-problems-booting-remix-os-dual-t3466027
Vioner said:
Have you searched for a disable dedicated/discrete graphics in BIOS? You need to disable it, because Remix will not boot with your GTX960M enabled.
If you don't have that option, then I'm sorry but for now you will be able to boot only using software rendering; graphics handled by the CPU. This means a less stable experience and less performance, but it will work 100%
Add this in the kernel grub line:
Code:
androidboot.swrast=1
Sent from mobile
Click to expand...
Click to collapse
I have looked for that option in my bios and I couldn't find it. I forgot to mention in my original posting that I had my Windows reinstalled with because the hard drive failed. I don't believe that I have the option to boot to the UEFI so I wonder if that has to do anything. I tried putting the "androidboot.swrast=1" code after the kernel line in the GRUB line editor thingy and I got it to boot. It's a bit unstable and the screen tends to tear when I move a large window around. The only problem now is how to make it permanent. I tried editing the file that was mentioned in some guides but it doesn't seem to stick.
tomekumb said:
Try to add "nomodeset" instead of "nouveau.modeset =".
Click to expand...
Click to collapse
I have tried both of the commands and it still hands at the Android root part. Are there any other commands or combination of commands that could work? I don't have an option in my bios to disable my gtx 960m and there isn't an option to boot to the UEFI. I wonder if the Windows reinstall due to a hard drive failure has something to do with it. Thanks in advance!
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
xxXPANDER said:
I want to dual boot android on my pc. I downloaded the ISO, installed ISO via Rufus. When I boot this flash drive, the live image works fine but when I click on installing it, it just gives me a blank screen. Any suggestions?
Click to expand...
Click to collapse
GRUB bootloader installed?
Complete guide here.
jwoegerbauer said:
GRUB bootloader installed?
I saw the link. Followed the steps. Stuck after step 5 in the link and cant proceed to step 6. I dont think grub is the issue here?
Click to expand...
Click to collapse
I'm having the same/similar problem (no choice to install is presented)
Context: I use a USB stick with refind to find and boot an android-x86_64-9.0-r2.iso that I have already imaged onto /dev/sda8 (imaged using the linux dd command).
When I use refind and select to boot /dev/sda8, android-x86 boots to the console shell prompt, and then seconds later starts a live run GUI screen. The boot process never stops to present me with a choice of install versus live run, as it should do. And that is my problem.
I'm looking for a workaround. I can switch between console and live GUI using Ctrl-Alt-F1/F7, so I can do command line stuff as root . Anything I can do to kill the live GUI and start the disk installer mode from the console? Name of installer program? Name of GUI is not Xorg or X or anything usual, it seems .
PS: If I knew which distro is underlying android-x86_64-9.0-r2.iso , maybe I could look up some keyboard salute to select installer mode during the boot?
one workaround found
@xxXPANDER, the following may be of interest to you, and @jwoegerbauer, too:
I managed to get the installer going by booting the iso from refind with one trick applied. Details: From refind gui boot, select the iso partition, and then use the hit-key-F2-twice method to edit the refind command line and append the phrase INSTALL=1 and then hit ENTER to boot.
At that point the installer mode came up, rather than the android live GUI mode, and I selected to install according to my plan, onto the empty partition /dev/sda9 with ext4.
I had a surprise that the installer put the data section of the installation on sda6:/android-9.0-r2/data/ (about 180MB), but the rest of the installation on /dev/sda9. Not sure how the installer figured out that I had tried before to do an alien-rpm-based install onto an existing ub18 on sda6. The image I booted was on sda8, and the destination I set was sda9. But still /data ended up on sda6:/android-9.0-r2/data/ . Weird.
Upshot: you need to shoehorn INSTALL=1 into the boot recipe, one way or another. I think the whole problem we're having should be considered a bug, though. It is almost as if the iso checks whether it is being booted from grub2 or not, and if not, jumps straight into live mode. This certainly caused me at least two full days worth of trouble so far, and I see no documentation of this strange behavior. At the very minimum there ought to be some documented keyboard salute that prevents this behavior during a standalone (non-grub2) boot. Maybe someone will disagree, but AT LEAST there should be prominent documentation, say on page https://www.android-x86.org/installhowto.html