Couldn't find a section for the HTC Desire 626S so I decided to go ahead and post it here so if my post is the wrong section, admins please correct it for me. Thanks
1. First make sure Developer Options is enabled on your device:
a. Go to 'Settings' head to 'Security' and check "Unknown Sources."
b. Next enable USB Debugging: Go to 'Settings' and scroll down until you access "About." Go to 'Software Information', and access "More". Rapidly tap on "Build number" until it tells you that you have enabled developer options. Now go back and Developer Options now appears above "About". Go in and check "USB debugging" and "OEM unlocking" (to allow bootloader to be unlocked).
2. Unlock your bootloader: this flashing procedure will wipe all the data on your device for security reasons - there's no way around that. It’s recommended that you backup what you want manually.
a. Access HTCDev which will provide the instructions to do so. Sign in first and select your device model [HTC Desire *]. First you will need to update to the latest Java, and download and install the latest Android SDK and latest HTC USB Driver v4.16.0.001.
b. Power off phone, press and hold Volume Down and then press and hold Power; hold both buttons to start the device into Bootloader mode.
c. Connect the device to the computer via a USB cable
d. Now we must get the 'Identifier Token' for unlocking the bootloader.
* With your device still in the 'Download mode', navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools". With the folder opened in a new window, hold Shift key and right click onto a blank part of the opened window and select "Open command window here" like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* When command window opened, type:
fastboot oem get_identifier_token
You will get the series of strings like this:
* Now copy the whole string and paste it into your favorite editor like Notepad and delete "(bootloader)," "<<<< Identifier Token Start >>>>" and blank space, so that the resulted string should appear like this:
Code:
<<<< Identifier Token Start >>>>
4F83B3A301842037241BA9B4960EFA06
DA5F5E6289DB07DF352BCD93227EC7E7
A96EFBB5B6B78F18EFF3120C3520F05D
B5F64931A881749FE6AE165033FD4412
1A483DD7B01A6BC96D827A80D14A4717
96857FE3C996D56873D231E73F2A23C5
554B6B081EC6589C0AE075D4EBE45B33
0046E3E0CCC5B700E4236EF6896B7D0B
4AE9A6F2DE7F2A4C4B70B5689C698E4A
4382F54F1DD24A5666FC5CC468B23446
0F1ADCBB79D780D52882FA2CF8F0AB6F
7B6572F38E4659250CD78615A4566E00
D3AAFA0DEF9F2DD9873B36B33ACECBDB
349110DD2F646007D442343415DC17DD
E1C4F1D29577B3E05A4BF79FBC25AC85
913512B173065739F0E2B155FB416A86
<<<< Identifier Token Start >>>>
* Now copy it and go to the HTCDev site (assuming you’re already signed in) and scroll down to find step #7:
* Now enter the copied string in the box provided and press the "Submit" button.
e. You will be sent an email with the unlock key as a file attachment.
* Download the attachment "Unlock_code.bin" and place it in the adb folder.
* Press Shift key and right click onto a blank part of the opened window and click "Open Command Window here".
* In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
* You will now see the disclaimer: Use the Volume buttons to highlight your choice, and make your selection with the Power button. Selecting Yes, wil reset your phone to factory settings, and your bootloader will be unlocked and selecting No, will reboot your phone and no changes will be made.
* To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made
f. Now it’s completed, your phone will be rebooted and it will start automatically with the unlocked bootloader.
OEM unlocking
On my MetroPCS I also had to got to Settings -> Developer options -> OEM unlocking and enable before I could get the unlock token.
ByteEnable said:
On my MetroPCS I also had to got to Settings -> Developer options -> OEM unlocking and enable before I could get the unlock token.
Click to expand...
Click to collapse
O ok cool. So was this guide helpful.
So what is the advantage to unlocking the bootloader if there is no root solution or no custom ROMs? Is there any real reason to unlock at this point?
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
This guide was very helpful. Now all we need is a Developer with this device to build some roms for us. I love this phone so far. It is amazing and just the right size for my hands. Thanks for this guide brother.
Informative
It was informative. I use GNU/Linux. So the only step that was missing on the HTC site was that you need to be root to run the programs.
jtrosky said:
So what is the advantage to unlocking the bootloader if there is no root solution or no custom ROMs? Is there any real reason to unlock at this point?
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
Click to expand...
Click to collapse
Well Idk if u are aware but when u unlock the bootloader, the device automatically resets to factory settings (all data lost). Someone such as myself who just got this phone would rather unlock the bootloader now (with nothing saved on the device) instead of waiting till a root solution becomes available down the line which would require me to backup all the things I find important on my device.
s3llz said:
This guide was very helpful. Now all we need is a Developer with this device to build some roms for us. I love this phone so far. It is amazing and just the right size for my hands. Thanks for this guide brother.
Click to expand...
Click to collapse
No problem man
Unlock now to avoid pain later
urbanman2004 said:
Well Idk if u are aware but when u unlock the bootloader, the device automatically resets to factory settings (all data lost). Someone such as myself who just got this phone would rather unlock the bootloader now (with nothing saved on the device) instead of waiting till a root solution becomes available down the line which would require me to backup all the things I find important on my device.
Click to expand...
Click to collapse
Sound logic. The exact logic I used. Unlock now and have a few apps blown away. However, one could always back up first but my Titanium Premium Backup wants root.
On a side note. I went to the HTC dev site to see if they had a kernel published and they don't.
Yeah, I'm aware that unlocking the bootloader resets the device - I was just wondering if there was a reason to unlock at this point. I already have my device fully setup - although, honestly, that's the great thing about Google/Android, even if I have to start from scratch, I can have it automatically reload all of my apps, app data, etc, so there really isn't much manual work involved in reseting an Android device.
Anyway, nice writeup and hopefully someone will find a way to root this thing soon - it's a hell of a phone for $80 (MetroPCS)! Can't beat the monthly fees either. This is the first Android device (out of over 10) that I couldn't root - although to be perfectly honest, so far it really hasn't caused me any grief - other than not being able to remove some of the system apps that I don't use...
The DotView case is pretty cool too - screen is always protected and I can see notifications/answer calls, etc without even opening the case! Expensive for what it is, but cool nonetheless....
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
ByteEnable said:
It was informative. I use GNU/Linux. So the only step that was missing on the HTC site was that you need to be root to run the programs.
Click to expand...
Click to collapse
Thanks
jtrosky said:
Yeah, I'm aware that unlocking the bootloader resets the device - I was just wondering if there was a reason to unlock at this point. I already have my device fully setup - although, honestly, that's the great thing about Google/Android, even if I have to start from scratch, I can have it automatically reload all of my apps, app data, etc, so there really isn't much manual work involved in reseting an Android device.
Anyway, nice writeup and hopefully someone will find a way to root this thing soon - it's a hell of a phone for $80 (MetroPCS)! Can't beat the monthly fees either. This is the first Android device (out of over 10) that I couldn't root - although to be perfectly honest, so far it really hasn't caused me any grief - other than not being able to remove some of the system apps that I don't use...
The DotView case is pretty cool too - screen is always protected and I can see notifications/answer calls, etc without even opening the case! Expensive for what it is, but cool nonetheless....
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
Click to expand...
Click to collapse
Thanks by the way. The DotView case looks nice but that's hella expensive, especially when u can go on ebay and find some going for at least $6 (from China), but more power to u.
Yeah, I saw some of those on Ebay but they were either purple (or some other ugly color) or they weren't genuine HTC cases (don't trust the chinese knock-offs). That and it would have taken 3 or 4 weeks to get here, by which time I would have most likely scratched the **** out of my phone!
I also didn't see a genuine HTC black 626s dotview case for anywhere near $6. Saw a few for other models, but not the 626. If you have a link to one, I'd appreciate it because for that price, it wouldn't hurt to have a spare. Now that I already have one, I don't care how long it takes to get here for the spare. I really do like the idea behind the dotview case though. Phone is always protected buy still useful at the same time.
Thanks.
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
jtrosky said:
Yeah, I'm aware that unlocking the bootloader resets the device - I was just wondering if there was a reason to unlock at this point. I already have my device fully setup - although, honestly, that's the great thing about Google/Android, even if I have to start from scratch, I can have it automatically reload all of my apps, app data, etc, so there really isn't much manual work involved in reseting an Android device.
Anyway, nice writeup and hopefully someone will find a way to root this thing soon - it's a hell of a phone for $80 (MetroPCS)! Can't beat the monthly fees either. This is the first Android device (out of over 10) that I couldn't root - although to be perfectly honest, so far it really hasn't caused me any grief - other than not being able to remove some of the system apps that I don't use...
The DotView case is pretty cool too - screen is always protected and I can see notifications/answer calls, etc without even opening the case! Expensive for what it is, but cool nonetheless....
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
Click to expand...
Click to collapse
jtrosky said:
Yeah, I saw some of those on Ebay but they were either purple (or some other ugly color) or they weren't genuine HTC cases (don't trust the chinese knock-offs). That and it would have taken 3 or 4 weeks to get here, by which time I would have most likely scratched the **** out of my phone!
I also didn't see a genuine HTC black 626s dotview case for anywhere near $6. Saw a few for other models, but not the 626. If you have a link to one, I'd appreciate it because for that price, it wouldn't hurt to have a spare. Now that I already have one, I don't care how long it takes to get here for the spare. I really do like the idea behind the dotview case though. Phone is always protected buy still useful at the same time.
Thanks.
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, I was thinking just like u. I went and got me a case from my local Metro PCS dealer right here (the version I have on ebay). I didn't wanna wait either and catch any scratches on it. Got mine for $15 which is a drop in the bucket in my opinion.
Hi @ you all, for me was working http://www.kingroot.net/ to root my phone i have the german version 626g
Houamei said:
Hi @ you all, for me was working http://www.kingroot.net/ to root my phone i have the german version 626g
Click to expand...
Click to collapse
I rather try a root option that requires me to use my PC instead of one that is on the fly. If I don't see a root option that meets those specifications within the next month, I'll probably use the kingroot method u suggested.
urbanman2004 said:
I rather try a root option that requires me to use my PC instead of one that is on the fly. If I don't see a root option that meets those specifications within the next month, I'll probably use the kingroot method u suggested.
Click to expand...
Click to collapse
Kingroot has an pc version too. if you want to root the phone via PC.
Houamei said:
Kingroot has an pc version too. if you want to root the phone via PC.
Click to expand...
Click to collapse
Alright, thanks. I'll look into it then
Kingroot does not work for the 626s. I believe that the difference is that the 626s runs Android 5.1 whereas the other 626 models run Android 4.4...
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
jtrosky said:
Kingroot does not work for the 626s. I believe that the difference is that the 626s runs Android 5.1 whereas the other 626 models run Android 4.4...
Sent from my HP SlateBook 10 x2 PC using XDA Free mobile app
Click to expand...
Click to collapse
I can confirm Kingroot doesnt work for the 626x using android 4.4.4
can't even install the updated apk and have not tried with the pc version yet....
Related
YES YOU READ THAT CORRECTLY
First off, huge props to Bierce and Oostah for all the searching and then providing me the info on how we might be able to enter DIAG mode on your phone while on CM7. All I did was manage to get it to work, and taking a leap of faith by trying to change my prl while using CM7
Something we never thought was possible...
Second, this isn't exactly for the faint of heart. QPST can really mess up your phone if you don't know what you're doing (read as: venture off and mess around with the program). Also, since I literally just did this this evening, there obviously hasn't been extensive testing with it. So "continue at your own risk".
Personally I haven't had issues with it and I've changed my PRL about 5 times to make sure it works. But still, it goes without saying: I'm not responsible if your phone gets FUBAR
What you'll need:
MSL -> (msl reader app)
Diagnostic Drivers (htc) -> google it for now, but I think these are the correct ones you need LINK
QPST -> Get the latest version here
install QPST
Get your MSL
Install the Htc Diagnostic Drivers (if needed)
Connect your phone to your PC
Open 'Terminal Emulator' on your phone and enter the following:
Code:
echo 1 > /dev/qct_diag_enable
This enables Diagnostics Mode, which enables us to use QPST
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open QPST Configuration
Select the "Ports" tab
Click "Add New Port"
Uncheck "Show Serial and USB/QC Diagnostic ports only"
Click on your device and hit OK
Highlight your phone on the "Ports" tab
Open up the "Start Clients" menu
Click on "Service Programming"
QPST Service Programming will open up and a "Phone Selection" window will appear: Click your phone if needed, and press OK
Now select the "Roam" tab and click on "Read from Phone" button
Enter your MSL, OK
Click on the "Browse" button and select the PRL file you want on your phone
Click the "Write to Phone" button next to the "read phone" button
Wait for it to finish writing to the phone. You might (read as most likely) get an error box, click OK on it.
Once all that is done, you can reboot your phone and enjoy the changed PRL without nandroiding, nand-restoring/flashing, etc. etc.
I just want to mention that the first time I did it, I lost my Mobile Data connection (3g) and after a reboot it was stuck on 1x. After another reboot, it was back to normal. But I believe that it was because I tried a verizon PRL that drops my service to almost 0.
End results
Yes, I know the status bars are 2 different colors. I have the Orion theme on my SDcard at the moment so it takes a little while to load up. But I assure you its the exact same CM7 rom and everything.
edit: oops double post >_<
ha you beet me to this kyouko great guide man. if yall are having trouble getting diag drivers to install please use this guide.
http://forum.xda-developers.com/showthread.php?t=114087
and the te method will work on all aosp roms.
thank you. works like a champ.
running cm7 nightly 129 heroc
Nice work man glade to see this working.
Sent from my HERO200 using XDA Premium App
Kyouko > heroc
Kyouko ~ shooter
BANG! from my shooter...
il Duce said:
Kyouko > heroc
Kyouko ~ shooter
BANG! from my shooter...
Click to expand...
Click to collapse
I'm still waiting on the Within (SGSII) to get released for sprint. I wanna check that out before I get an upgrade. Either way, probably wont get a new phone till fall :/
Sent from my HERO200 using XDA App
kyouko said:
I'm still waiting on the Within (SGSII) to get released for sprint. I wanna check that out before I get an upgrade. Either way, probably wont get a new phone till fall :/
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
NICE JOB man i found the same thing was coming to tell you about the
echo 1 > /dev/qct_diag_enable
and to disable it
echo 0 > /dev/qct_diag_disable
it may be echo 1 then > /dev/qct_diag_disable
i will test then edit post
it would be:
Code:
echo 1 > /dev/qct_diag_enable
echo 0 > /dev/qct_diag_enable
to turn diag mode on and off, respectively
/dev/qct_diag_disable doesn't exist
You can check that with terminal emulator...
Code:
su
cd /dev/
ls
Thought I'd mention that I've used this method easily more than 20 times between my phone and another hero with ZERO problems.
I know in the OP it might sound a little scary, the warning is mostly for screwing around with QPST in the areas not talked about.
Sent from my Hero using Tapatalk
When I click ADD NEW PORT, my phone is not showing up.
I am running Windows 7 Professional on my computer. For whatever reason, while trying to install the drivers and HTC sync, I could never get my phone to connect. I tried manually updating the diagnostics drivers to no avail. I fought with it for about an hour before saying forget it(not exact terminology). I am not sure if others have encountered this, but I will post my work around. I searched for a virtual machine solution with no results, so also not sure if its been talked about in other threads.
My job is programming controllers for building automation. I know a few pieces of our software will not work properly with W7. We have to run a virtual machine on our computers. Microsoft has been so kind that if you are running Windows 7 Professional, Enterprise, or Ultimate, you can download, for free, an XP Virtual Machine. I'm going to assume, since what you guys are able to do with phones is over my head, you know what a Virtual machine is.
I apologize about the links, since I am a newbie, I can't post outside links, if you need the links, PM me and I will give them to you.
Here is the link to Microsoft's site where the VM ware is(I could only get IE Explorer to work, I normally use Firefox but it wouldn't work with the microsoft security): Google "XP Mode" The first link should be one to microsoft's website.
Go through the steps and download the xp mode and virtual machine. continue with the installation. With this, I installed Sync 2.0.40 with no problems. No additional drivers to install.
HTC Site: Under the downloads section on the HTC Site for the hero
Hooked up my phone. Everything worked as it should. I've now switched between a few different PRLS. I've been running CM7 and just switched to Jaybob's AOSP 2.3.5.
I'm not sure if this will ever help anybody, but I thought I would at least post it.
Great guide man. This helps alot with changing the prl. I really got tired of flashing back to stock then back to cm7. 2 thumbs up.
Sent from my finger tips using the XDA App
edit: Well i tried this little tutorial and it didn't do crap for me.
Nice guide, but that seems a lot harder than just doing a nandroid backup, flashing a sense rom (fresh in my case), updating PRL/Profile/etc, and restoring from your original backup.
Im stuck on 1x data with the PRL 21081. Should I try updateing to fix this? Also my Wifi says error all the time and wont turn on if that has anything to do with it. Thanks.
After some initial difficulty getting setup (the main issue being the diagnostic drivers (vista drivers) listed in the link didn't work on MY 64 bit win7 setup. I did find an alternate source that worked, I'll link it here if I can track it down...) I was able to get this working, and once setup, it's a breeze. Definitely easier than going back to a sense rom to do it.
It was only the initial setup that was a pain. So, my hero took a couple hours of mucking around to ultimately update the PRL, BUT, took about 5 minutes to update my son's, and the bulk of THAT time was getting msl reader on his phone, and rebooting after the write to phone phase.
Awesome.
hareofthedog said:
After some initial difficulty getting setup (the main issue being the diagnostic drivers (vista drivers) listed in the link didn't work on MY 64 bit win7 setup. I did find an alternate source that worked, I'll link it here if I can track it down...) I was able to get this working, and once setup, it's a breeze. Definitely easier than going back to a sense rom to do it.
It was only the initial setup that was a pain. So, my hero took a couple hours of mucking around to ultimately update the PRL, BUT, took about 5 minutes to update my son's, and the bulk of THAT time was getting msl reader on his phone, and rebooting after the write to phone phase.
Awesome.
Click to expand...
Click to collapse
Yeah, if you can find the link to what worked for you with this process that'd be great. I had the same problem you mentioned when I attempted this with the wife's phone. But I never found the right drivers. I would be eternally grateful.
These are the ones that worked for me, found them here, of course,
http://forum.xda-developers.com/showthread.php?t=801570
hareofthedog said:
These are the ones that worked for me, found them here, of course,
http://forum.xda-developers.com/showthread.php?t=801570
Click to expand...
Click to collapse
Unfortunately this didn't change anything for me. I am trying to update the prl on an evo shift though, so that may be the ultimate factor after all. I may just have to give in and revert her phone back to stock temporarily to update it. I've used QPST many times with updating my Epic, so I'm certainly comfortable with that aspect. I thank you for your assistance nonetheless. Hopefully it will be the determining factor for someone else in a similar position.
Sent from my HP Touchpad using xda premium
will this method only work with cm7??
Open source app development project: Permanent screen off for the Visual Impaired
Short summary
This is an app development project that turns off the Android screen permanently yet keeps the touchscreen and other features active and functional for the visual impaired.
Introduction & Goals of the project
There are many Android users who are blinded. And to them, they access the app mainly using TalkBack or other Screen Reader app. That also means that the screen is basically useless to them. They don't need to look at the screen yet they need to be able to use touchscreen.
This project is to create an app that will turn the screen completely off (100% off) yet let the user use the phone as normal.
Assuming that the blind takes more time than normal user to perform an action, it dramatically saves the device's battery.
The app must be easy to use and tailored to visual impaired user.
The app automatically runs with the device.
The app must be free and advertisement-free.
Background
I am the developer of the project and I recruit the interest of other developers / users as well. I am the developer of Screen Standby app, which this project is based on.
Device requirements
- Running Android 1.5 (Cupcake) or above
- (Optionally) Rooted for best battery-saving. The app works with non-root device though, only rooted device achieves complete dark
Instruction
1) Download the apk and Install the app
2) Run the app at least once
3) Select Enable app from menu
4) If the system asks for Superuser access, select always remember and allow
5) To disable, select "Disable app" from the menu and restart the device.
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NOTE: Please read
1) Always use a screen reader (e.g TalkBack) with the app. In case you want to use your device without the screen
2) This app will permanently switch the device's screen off when it is active. To turns the screen back on, select "Disable app" or uninstall app completely and reboot
3) To uninstall from ADB, go to a shell and type: adb uninstall com.nkahoang.screenoffvisualimpair
Download
Currently the app can be downloaded from attachment section of this post. When it is stable enough, it will be ready to be released on Play Store for free download.
Source code can be downloaded in second post
If you know any Android user who is blinded, let them use the app and report. Any feedback is welcomed
Source code of the app
App's source code can be downloaded from here
Disclaimer: Source code can be used only for non-commercial projects
Great idea. Good luck.
Sent from my GT-I9300 using xda app-developers app
As the guy above me said. G great idea which actually will help some people. But I don't think that many actually blind people are going to find this app unfortunately... You have to put it on Google play and name it in such way that blind people will find it
Sent from my R800i using xda premium
Hello,
While putting it on the Play store is a good idea, there are a few blind folks on XDA like myself who would be happy to give this app some testing beforehand.
Thanks for posting to the eyes-free list, and thanks for developing this app!
correct this is also needs to be on the playstore as screen off or something easy that some of us can find more easily on the playstore . all of us blind people thank you for the app that hav found it but for those who cant can you please turn it into an APK installer or make it easy to install from playstore. as a lot of blind people don't know how to install zip files on android. if you can give me a quick tutorial I can explain to the eyes free list. I am a blind intermediate user of android. I do understand rooting, installing custom roms and gapps and installing apps for rooted devices but some of the rest on the eyes fre are a bit limited here so if you can give them an APK installable file it would be much easier to install rather then a zip package in which they have to figure out what to do with it.
mrk2815 said:
correct this is also needs to be on the playstore as screen off or something easy that some of us can find more easily on the playstore . all of us blind people thank you for the app that hav found it but for those who cant can you please turn it into an APK installer or make it easy to install from playstore. as a lot of blind people don't know how to install zip files on android. if you can give me a quick tutorial I can explain to the eyes free list. I am a blind intermediate user of android. I do understand rooting, installing custom roms and gapps and installing apps for rooted devices but some of the rest on the eyes fre are a bit limited here so if you can give them an APK installable file it would be much easier to install rather then a zip package in which they have to figure out what to do with it.
Click to expand...
Click to collapse
Hi,
I sure will put it on play store once it is stable. The app is currently in development.
The zip file is for the source code of the app. I attached the apk on the very first post:
http://forum.xda-developers.com/attachment.php?attachmentid=1926833&d=1367394050
Regards
Well done OP.
You are a hero for undertaking this venture. I wish you more success.
I still might have a use for this in my Android devices that I'm using as Network Cameras using the IP Webcam app.
But I will have to test it out to see if it acts the way I need it to (I'm not at home yet, but I will try it.)
On Android 2.x I'm able to have a camera app run fine in the background or with the screen off, but on Android 4.0 and newer, the camera doesn't work completely if you turn off the screen or switch to a different app.
I'm wondering, will this app allow me to have the screen completely off (on a rooted device) but still have the camera use all the processor it needs for perfect Network Camera functionality?
Thanks.
HwyXingFrog said:
I still might have a use for this in my Android devices that I'm using as Network Cameras using the IP Webcam app.
But I will have to test it out to see if it acts the way I need it to (I'm not at home yet, but I will try it.)
On Android 2.x I'm able to have a camera app run fine in the background or with the screen off, but on Android 4.0 and newer, the camera doesn't work completely if you turn off the screen or switch to a different app.
I'm wondering, will this app allow me to have the screen completely off (on a rooted device) but still have the camera use all the processor it needs for perfect Network Camera functionality?
Thanks.
Click to expand...
Click to collapse
The camera will continue functioning normally. However, you may want to consider using my other app, Screen Standby # Root, also on XDA to achieve that. This app is tailored specifically to aid the blind in particular.
nkahoang i dont know if you got my email i sent a while back but i was looking for a app like this but be able to close my tablet and plug a keyboard and a mouse into my dock and hook it up to my tv and use my tv as a monitor screens cracked and touchscreen capability are all down the drain, would be great if you could add this feature to this app so i could finally find a use for my tablet again and as always keep up the good work.:good::fingers-crossed:
I have another use that I would like to ask for. Could you integrate Tasker support? I ride a motorcycle and have a bluetooth kit installed on my helmet. I leave my phone in my pocket or a glove box and therefore the screen is of no use to me. Yet if I ask Google Now to navigate somewhere, it opens navigation that keeps the screen on draining battery quickly. This really sucks as I don't have an outlet to plug into while riding. So, if I could setup a profile to activate this app while riding and disable it when I'm done, that could help me out a lot.
hello I was wondering I there has been further development on this app.
Lots of blind users are wondering about eh app development.
Since ther is no info a bit oncerning .
I know tha you develop the screen root stand by primarly but can you also devot e some development ot he app for he blind as well.
thanks for your development efforts
Hello, Now I am using Shades app by the eyes free team at Google. That is an app published to the google play. However after reading the description in the first post I think this app might be capable of saving more of the battery juice. I have just installed it on my SGS2 running CM-10 however if this is already know I would like to ensure this is really more powerfull than the Shades app I was tallking about.
Thanks and greetings
Peter
Just bought one of these from someone on eBay for $95.00 and now to begin the hacking!
Model: SCH-I930
Note: This device is dual CDMA and GSM. It is also SIM unlocked. I believe I have the capability to provision this device for a different CDMA carrier, but it most likely needs manually programmed.
For the nest part I'm assuming that this device only has been turned on and never updated.
OS Version: 8.0.10211.204 (GDR1)
Firmware revision:2218.12.12.4
Hardware revision number:13.22.0.4
Radio software version: 2218.12.12.4
Radio hardware version: 0.0.0.4
Bootloader version: 12.12.20.17
Chip SOC version: 1.5.32
InteropUnlock:
Use app that's attached. Or wait for WOLF's app to update with support for us!
Launch the Native Toast Launcher attached and replace the existing app-id with the following,
Code:
[B]51d4668e-01fa-4b6f-a8af-5170b5d7484c[/B]
This opens the Samsung Registry editor.
Now Install @-W_O_L_F-'s Interop Unlock Helper app, to copy and paste info into the fields shown. (Just skip the step with launching the app.)
Paste the rest as you see as in this screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Updates Available:
SAMSUNG Update for Windows Phone.For
more information on this software update,
visit www.vzw.com/ativodysseysupport
Microsoft Update 8.0.10322.71
Microsoft Update 8.0.10327.77
EDIT: Now I finally got it to show the GDR3 Update, but I'm weary of the SAMSUNG Update as there isn't a ROM available for this device....
This is pretty much it for now. I don't have any other original app-ids yet.
New Update:
Microsoft Update 8.0.10521.155
Native Dialer Codes:
Code:
<Customization OwnerType="Microsoft">
<Component ComponentName="Partner App Support">
<SettingsGroup>
<Setting Name="Partner App Task URI" Value="app://51d4668e-01fa-4b6f-a8af-5170b5d7484c/_default"/>
<Setting Name="Partner App Provisioning File Path" Value="\Windows\System32\Provisioning\mpap_Diagnosis_01.provxml"/>
<Setting Name="Partner Immediate Dial Strings" Value="##634#;##2539#;**33284;##3282#;**367738;**476813580;**87284;##25327#;**7838;**6828378;##72786#;##889#;##433346#;##22745927#;##366633#"/>
</SettingsGroup>
</Component>
</Customization>
NOTE: Most of these codes above are blocked. Start the Native Toast app, use the string below and change to Unblock. (To access these you'll need to type them in the Diagnosis app) This setting switches back to Block when the device is turned off or restarted!
Code:
app://51d4668e-01fa-4b6f-a8af-5170b5d7484c/_default#/WP8Diag;component/1_hidden%20menu/vzwkeyblocksetting.xaml
I don't have a new complete set of dial codes for Diagnosis yet. You can get some of them from the Windows Phone 8 Diagnostic and Hidden Apps thread.
The UpdateHistory.xml file lists each file it downloaded to update. Interesting.
View attachment UpdateHistory.xml.txt
NEW!: Settings for Verizon's Unlimited Data customers!
Use the native toast launcher with the following string:
Code:
app://51d4668e-01fa-4b6f-a8af-5170b5d7484c/_default#/WP8Diag;component/1_hidden%20menu/vzwkeyblocksetting.xaml
Click launch toast and click on the the toast whenever it pops up.
Click unblock, and close both apps.
Open diagnosis again from the app list and dial ##3282#.
Click edit then Data Profile.
Change username, from
<your verizon number>@vzims.com
to
??? (I don't know what the default setting is for device internet vs. tethering yet...)
Hit save.
PROFIT!!!!!
New!: Qualcomm DM Mode
Dial ##366633# from the normal dialer menu (not Diagnosis)
Hit Enable DM Mode
Let the device reboot.
Install drivers for QC RMSerial.
CDMA Workshop is playing nicely!
VolUP+CameraFull = Download Mode
Driver name: USB DOWNLOADER
HWID: USB\VID_045E&PID_062B&REV_0000
Use the driver included with the flasher.
VolUP+VolDown+CameraFull = Recovery Mode?
Says the following:
Press volume down to continue.
Click to expand...
Click to collapse
then
Please wait for a moment.
Click to expand...
Click to collapse
If any other button is pressed or its just left alone, it continues booting.
When you hold voldown, it takes you to the "!" screen.
now it's Interop Unlocked . Can you access to Full FS ?
It should. I had to redo the CSC, (which did a full reset -_-) because I apparently mucked with some of the cellular settings making it think I was roaming when I'm not. Haven't gotten that far. Just installed the three main apps too...
EDIT: Just set it and restarted the phone once. Works like a charm!
I was looking at the Odyssey's listed on ebay myself Besides the benefits of being interop unlocked how do you like the experience compared to your Lumia 928? I like my Lumia well enough as to not want to invest in a second device and just wait and see what, if anything, happens as far as an unlock for the Lumias. I did however see a number of defective Odyssey's listed that are cheap enough that even if the device is beyond repair as far as a working phone it might still be fun to tinker with the hardware...
@thals1992 : great work, your work has been mentioned at an article of WMPoweruser. Did you had to do something extraordinary to the normal procedure of interop-unlocking an normal ATIV S or was the process the same?
bruce142 said:
@thals1992 : great work, your work has been mentioned at an article of WMPoweruser. Did you had to do something extraordinary to the normal procedure of interop-unlocking an normal ATIV S or was the process the same?
Click to expand...
Click to collapse
It's the same since I've updated Interop Unlock Helper.
tonbonz said:
I was looking at the Odyssey's listed on ebay myself Besides the benefits of being interop unlocked how do you like the experience compared to your Lumia 928? I like my Lumia well enough as to not want to invest in a second device and just wait and see what, if anything, happens as far as an unlock for the Lumias. I did however see a number of defective Odyssey's listed that are cheap enough that even if the device is beyond repair as far as a working phone it might still be fun to tinker with the hardware...
Click to expand...
Click to collapse
I bought mine just the phone that included a cheap charger for ~$120.
It doesn't have FM, but you have access to everything inside the cellular settings using the toast launcher on Diagnosis. So you could take this device over to PagePlus (or another MVNO) if you really wanted to. Besides that, its similar to the 822 Nokia has. It has a MicroSD slot, a 3.8 V 7.98 Watts/hour battery, and multiple sockets (snap on style) on the back to attach antennas to if you have weak signal and need something large outdoors. Oh and this isn't super low end WP, so it's got an LED on the back.
I essentially think of it as a Trophy with 4G, but no FM. And settings to change the NAM, MSL, ect. That's only useful for CDMA though. Also be careful, US Cellular also has this device, but I have no clue those are SIM Unlocked.
Sent from my Lumia 928 (RM-860) using Tapatalk
bruce142 said:
@thals1992 : great work, your work has been mentioned at an article of WMPoweruser. Did you had to do something extraordinary to the normal procedure of interop-unlocking an normal ATIV S or was the process the same?
Click to expand...
Click to collapse
Yeah, buying the device and getting the app-id for Diagnosis.
Also, the app attached to the OP is actually for the ATIV S, but we are pasting in ours. Also, its much easier to use his app anyways. I didn't know how long it would take, so I published this as a tutorial
Super Easy!
Sent from my Lumia 928 (RM-860) using Tapatalk
CDMA Workshop works!
Okay, I've played around with the Different USB modes a little more. Apparently each mode has a different PID.
You'll need to get drivers that are attached below. (Also, if you are running on Vista x64 or newer, you need to be running Test Signing mode.)
QC RMNetComposite uses Qualcomm 9001 as the main driver.
MI_00 is Qualcomm HS-USB Diagnostics 9001
MI_01 is Qualcomm HS-USB NMEA 9002 (Couldn't find the exact pid, but close enough.)
MI_02 is a modem, where I had to get an outside driver made by ALCATEL.
MI_03 is Qualcomm Wireless HS-USB Ethernet Adapter 9001 which I had to grab from QISDA Corporation for the H2O.
QC RMSerial uses Qualcomm Winmobile 319B
MI_00 is Qualcomm WinMobile Diagnostics 319A (close, but compatible enough)
MI_01 is a modem, where I had to get an outside driver made by ALCATEL.
MI_02 is Qualcomm WinMobile NMEA 319A
MI_03 is Qualcomm WinMobile Trace 319A
Drivers are available at my SkyDrive (now OneDrive )
EDIT: The drivers are all kindof a mess, because I don't recall which set worked and which set didn't. Most of these drivers both have 32bit and 64bit in them. Let me know if there are issues.
If you got wired tethering working (or even if you didn't, but think it might be usable for that) please share the (link to the) driver you used!
The NMEA device is also interesting. That implies that the phone could be used as a USB-connected GPS, which could be very handy.
I'll probably attach it to the post above or upload it to dev-host. I used a variety of drivers and I don't exactly recall what's what.
EDIT: NMEA doesn't show any output, but that might just mean it needs an app pulling lat+long realtime, which I didn't test yet.
Hmm. NMEA is usually a very simple serial interface, with the GPS (or other location device) pushing information over it in a semi-readable ASCII format pretty much continuously. Maybe something needs to be done driver-side to trigger it, or maybe the phone needs to run something that will push the data... when you connected to the NMEA interface, did the phone display the location services icon in the taskbar?
Hmm, nothing. I tried launching HERE Drive, nothing. I tried using Realterm, nothing happens except TXD freezes on, because its not accepting the data device side or something. I tried using HERE Drive to see if that would work, but to no effect. There's literally no output whatsoever. Might need something else to initialize on the phone. No location symbol appears when connected to usb.
Edit 1: Apparently the Qualcomm Gobi 2000 shows that they use "$GPS_START/$GPS_STOP" to initialize. Still doesn't work when input to either the Diagnostic port nor the modem port.
Edit 2: http://mod-book.ru/files/Gobi2k/Documents/AT_Command_Set_Gobi.pdf shows that it uses AT$$GPS_STOP from official leaked documentation.
Edit 3: Seems we are diving deeper into the chipset than I initally wanted. http://www.qualcomm.com/chipsets/gobi
There's a new update for the OS. Nothing else to report, besides the possibility of using VZWManager for USB tethering.
VZAccess Manager won't work, but I tested with the Modem interface and the Odyssey bluescreens.
(If you'd like to know more, you can search online later for this error: SOC_SUBSYSTEM_FAILURE) :/
New settings?
number to dial
#777
username
[email protected]
password
vzw
I don't thing there is a way to tether lte yet.... unless you use internet sharing over WiFi.
Got an opportunity to trade my 928 for an Odyssey and after playing with the Samsung device for a bit I took it. Honestly the Lumia Black update that was so anticipated left me feeling a little flat and although Nokia puts out great stuff the Odyssey seems way more fluid and vibrant to me. Long story short Interop Unlocked and fully updated,without Dev Preview, and everything seems to be working great. Willing to test and THANK YOU TO EVERYONE THAT MADE THIS POSSIBLE!!! :highfive:
There seems to be an additional key combo for booting, but I'm afraid it doesn't do anything...
Can I update my odyssey ativ with the windows 8.0 to 8.1?
Like many now, I want to avoid Google's services for privacy reasons, and use CM / PA / other ROMs without anything Googly installed.
Thus the Priv is only an option for me if I can completely strip everything Google out of it. Priv is supposed to stand for privacy, but sharing everything with Google isn't very private ....
I have a bad feeling that there'll be no option whatsoever to do this. Also, it looks like the phone uses Google's phone and messaging apps, so I assume core BB services rely on those and therefore Play / Gapps ...
Then of course there's the dark cloud that a heavily locked down bootloader / difficult root access may cast.
Anyone have any thoughts?
Google probably already has all your information, i'm sorry...it's too late
If it lives up to what it is supposed to then it will be completely locked down with no aosp based options. Also as all the stuff will be tied to blackberries servers even if you did manage to unlock it you might find a device that is useless
zelendel said:
Also as all the stuff will be tied to blackberries servers even if you did manage to unlock it you might find a device that is useless
Click to expand...
Click to collapse
Only BBM goes through the BlackBerry servers now, unless you're using it on a BES exchange.
Yeah, I'm in the same boat. I think it's a "wait and see" type of situation where we have to see if someone with the knowhow is able to root it and go from there.
Like Zel said, probably won't get custom roms, due to the advertised features of the device but I'm hoping, at the very least, the phone is successful and other OEMs start taking physical keyboarded devices seriously and make decent phones with them like they did when android was young. Could you imagine if Samsung, for example, made a GS7 variant that took physical keyboards as seriously as the note series takes big screens & wacom pens?
I think Priv will come with 2 OSes loaded, and you are prompted from the first boot to choose your preferred OS. So just choose BB10
Or go with Passport or classic, really good phone
vutranloc said:
I think Priv will come with 2 OSes loaded, and you are prompted from the first boot to choose your preferred OS. So just choose BB10
Or go with Passport or classic, really good phone
Click to expand...
Click to collapse
This will not be an option. This would remove all the security that BB will depend on. I mean BB will most likely even use hardware crypto keys as well as the new security from qualcom that will refuse to boot if it detects system changes.
zelendel said:
This will not be an option. This would remove all the security that BB will depend on. I mean BB will most likely even use hardware crypto keys as well as the new security from qualcom that will refuse to boot if it detects system changes.
Click to expand...
Click to collapse
Well these 2 images show the ortherwise...
- Here the passport have quick toggle labeled "switch to android"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Here the "slider" (priv) have this selection in first booting
vutranloc said:
Well these 2 images show the ortherwise...
- Here the passport have quick toggle labeled "switch to android"
- Here the "slider" (priv) have this selection in first booting
Click to expand...
Click to collapse
That is odd indeed. As this would bypass all the security that BB has worked very hard to come up with. Ill have to look into this more. The only devices that I know that dual boot are Asia based knock offs.
Thanks for the info will dig in and ping a few people about this.
zelendel said:
That is odd indeed. As this would bypass all the security that BB has worked very hard to come up with. Ill have to look into this more. The only devices that I know that dual boot are Asia based knock offs.
Thanks for the info will dig in and ping a few people about this.
Click to expand...
Click to collapse
Sure things no problem
But in fact I think this will do no harm, as the choice is permanent: You get to choose 1, and to stick with it till you factory reset the phone. In some phones (eg, for the gov or firms) you only get BB10 or android, in commercial edition you get both, but only use 1 at a time
I'm pretty sure that OS selection theory was well debunked in the Crackberry forums. People looked at that Passport image, and if you look closely at that switch to Android button, it doesn't quite have the right dimensions or separation from the other setting buttons.
vutranloc said:
I think Priv will come with 2 OSes loaded, and you are prompted from the first boot to choose your preferred OS. So just choose BB10
Or go with Passport or classic, really good phone
Click to expand...
Click to collapse
There is only one OS loaded on the Priv, and that's Android.
The dual boot BB10/Android dream was just that... a dream. It only existed in photoshop, not in the real world.
Phill_UK said:
There is only one OS loaded on the Priv, and that's Android.
The dual boot BB10/Android dream was just that... a dream. It only existed in photoshop, not in the real world.
Click to expand...
Click to collapse
Still I do hope of BB10 on Priv. For my needs BB10 is perfectly fine
Sorry this is absolute fantasy - it's an android phone running 5.1 - Google never has and never will sign off on a dual-boot. There is no dual-boot, no hypervisor - it's a virtually stock android device with a few interesting hardware features, some Blackberry specific software and that's it. BB10 doesn't even support the resolution of the screen and all work beyond security patches has finished on that OS.
vutranloc said:
Well these 2 images show the ortherwise...
- Here the passport have quick toggle labeled "switch to android"
- Here the "slider" (priv) have this selection in first booting
Click to expand...
Click to collapse
You do realize that those are doctored photos right? It was confirm that the switch to android was someone with too much time on their hands with a BES account.
achiquitachaser said:
You do realize that those are doctored photos right? It was confirm that the switch to android was someone with too much time on their hands with a BES account.
Click to expand...
Click to collapse
Still you say it is possible right?
vutranloc said:
Still you say it is possible right?
Click to expand...
Click to collapse
No. No one said BB10/Android dual booting or OS selection was/is/ever will be a thing.
pluto7443 said:
No. No one said BB10/Android dual booting or OS selection was/is/ever will be a thing.
Click to expand...
Click to collapse
Actually the guy above you said it might be possible with bes
Can it be done? Yes. It could be done. The question at hand us will it be done. To be honest I wouldn't give it better then a 5% chance off it happening. If it even does it will be an Asia based knock off running Android and what ever.
vutranloc said:
Actually the guy above you said it might be possible with bes
Click to expand...
Click to collapse
He meant it was someone with BES who managed to make the option appear. Go search crackberry for the various threads on this, it has already been discussed to death.
Android X86 Today Presents:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PhoenixOS v1.0.9 Rooted .iso
Update Sept 10 New Version Available
v1.1.0 Link
Update Aug. 16: Special Edition 1 and 2, UEFI Compatibility, Installation Guide, Mount Windows Partitions
Here is a Bootable rooted .iso for the Phoenix Operating System based on Androidx86 Lollipop. I have included an installer in the zip. This is for running from a live USB with an option to install to harddisk from grub. I'm using Windows 10. I am also assuming that you know how to do some basic functions with your machine such as creating a new partition.
Mount Windows Partitions!
Stick Mount by @Chainfire
Stock, Rooted w/Rufus:
Stock, Unrooted w/Rufus:
Rufus Only:
Installation guide (HTML):
Special Edition 1:
AdAway, JMusic, Terminal Emulator and More......See README in Zip:
Update Aug. 16 Special Edition 2:
Debloated and Standardized!
Everything from Special Edition 1 and more! See README:
To use with Windows machine:
1. Be sure you have Secure/Quickboot disabled in Bios.
2.Use a minimum 8Gb USB thumb drive 3.0 works best but high quality 2.0 will suffice. Formatted fat32. (Should be default)
3. Unpack PhoenixOS_v109_Rufus.zip
4. Run Rufus-2.9.exe
5.Select USB in the first entry.
6.Select iso towards the bottom and navigate to PhoenixOS iso. Rufus will automatically fill in the rest of the settings. Make sure the USB drive is still selected, though. You may change the partition label if you so desire.
7. Select start.
8. Make a bite to eat.
9. When Rufus has finished reboot into your Bios settings.
10. Select USB drive from boot selection, Legacy or UEFI, and boot it.
11. You will be greeted by the Rufus grub menu. Select "Live CD"
12. Boot up will take some time , you will hang at "Initializing System" for a while. If longer than say 10 minutes. Reboot and start at step one, using a better quality USB this time.
14. Have a look around and enjoy. You will only have about 1Gb of internal storage available, also this session will not save, so I generally don't linger too long.
Before we go further it is probably time for the Standard Disclaimer:
This product is meant for educational purposes only. Any resemblance to real persons, living or dead is
purely coincidental. Void where prohibited. Some assembly required. List each check separately by bank
number. Batteries not included. Contents may settle during shipment. Use only as directed. No other
warranty expressed or implied. Do not use while operating a motor vehicle or heavy equipment. Postage will
be paid by addressee. Subject to CAB approval. This is not an offer to sell securities. Apply only to affected
area. May be too intense for some viewers. Do not stamp. Use other side for additional listings. For
recreational use only. Do not disturb. All models over 18 years of age. If condition persists, consult your
physician. No user*serviceable parts inside. Freshest if eaten before date on carton. Subject to change
without notice. Times approximate. Simulated picture. No postage necessary if mailed in the United States.
Please remain seated until the ride has come to a complete stop. Breaking seal constitutes acceptance of
agreement. For off*road use only. As seen on TV. One size fits all. Many suitcases look alike. Contains a
substantial amount of non*tobacco ingredients. Colors may, in time, fade. We have sent the forms which
seem right for you. Slippery when wet. For office use only. Not affiliated with the American Red Cross. Drop
in any mailbox. Edited for television. Keep cool; process promptly. Post office will not deliver without
postage. List was current at time of printing. Return to sender, no forwarding order on file, unable to forward.
Not responsible for direct, indirect, incidental or consequential damages resulting from any defect, error or
failure to perform. At participating locations only. Not the Beatles. Penalty for private use. See label for
sequence. Substantial penalty for early withdrawal. Do not write below this line. Falling rock. Lost ticket pays
maximum rate. Bg260 was here. Your canceled check is your receipt. Add toner. Place stamp here. Avoid
contact with skin. Sanitized for your protection. Be sure each item is properly endorsed. Sign here without
admitting guilt. Slightly higher west of the Mississippi. Employees and their families are not eligible. Beware
of dog. Contestants have been briefed on some questions before the show. Limited time offer, call now to
ensure prompt delivery. You must be present to win. No passes accepted for this engagement. No purchase
necessary. Processed at location stamped in code at top of carton. Shading within a garment may occur.
Use only in a well*ventilated area. Keep away from fire or flames. Replace with same type. Approved for
veterans. Booths for two or more. Check here if tax deductible. Some equipment shown is optional. Price
does not include taxes. No Canadian coins. Not recommended for children. Prerecorded for this time zone.
Reproduction strictly prohibited. No solicitors. No alcohol, dogs or horses. No anchovies unless otherwise
specified. Restaurant package, not for resale. List at least two alternate dates. First pull up, then pull down.
Call toll free number before digging. Driver does not carry cash. Some of the trademarks mentioned in this
product appear for identification purposes only. Objects in mirror may be closer than they appear. Record
additional transactions on back of previous stub. Unix is a registered trademark of AT&T. Do not fold, spindle
or mutilate. No transfers issued until the bus comes to a complete stop. Package sold by weight, not volume.
Your mileage may vary. If the flow controls supplied are not installed, this unit will not operate properly. Keep
out of reach of children. When this set is used with other equipment, if the picture is not stable or the buzz
sound is heard, try to change the mutual position of relevant equipment or take enough distance between
them. This unit not labeled for retail sale. Phenylketonurics: contains phenylalanine. Close cover before
striking. Mind the gap. No merchantability expressed or implied. Parental discretion is advised. Sold as a
novelty item only. Although robust enough for general use, adventures into the esoteric periphery may reveal
unexpected quirks. Not available in stores. May cause abdominal cramping and loose stools. Vitamins A, D,
E, and K have been added. Not designed or intended for use in on*line control of aircraft, air traffic, aircraft
navigation or aircraft communications; or in the design, construction, operation or maintenance of any
nuclear facility. Container may explode if heated. May contain traces of various nuts and seeds.
This notice supercedes all previous notices.
Please don't blame me if you mess up your machine.
To install to Hard Disk:
This is where it can vary. With every machine being slightly different. There is also the potential to "inadvertently" erase something vital. Make sure you have a "Plan B".
1. Prepare a partition to the desired size. format to NTFS "I would say Ext4 but Windows disk manager doesn't have that option". You can use 3rd party software such as Partition Wizard, but it is not necessary. COMMIT THIS DRIVE # TO MEMORY. If you are running Windows only, this will generally be partition 4 or 5 . (Sda4 or Sda5) You can also make a small (300Mb) partition formatted to FAT32 for Grub installation. Windows will NOT let you create a partition of that size natively and you will have to use a third party application.
2. Boot up PhoenixOS USB.
3. Select second option "Installation".
4. Begin Guided installation. VERY IMPORTANT , select the appropriate partition. Here is where formatting Ext4 would help as it will be the only partition formatted as such, plus if unsure you can select do not format. If you would like more than 4Gb of storage, format to Ext4 . If you get it wrong it will format and over-write, possibly your C:\ Partition
5. Have it install Grub for legacy or Grub2 for UEFI, or both. I don't care :laugh:. I could be wrong. I am triple booting with Linux and Windows so Grub2 was already installed. Please post any different findings or opinions as I am limited in my equipment.
6. Choose partition for Grub installation.
7. Install.
8. Reboot, be sure to remove USB when safe.
9. If all went well you will be greeted with Grub menu. you will be able to choose either Windows or PhoenixOS. Enjoy. <----Dual Booting is easy.
10. If you wish to triple boot...It took me a week to figure it out finally had success with Grub2win for Windows or Grub-customizer for Linux. Alas, if you want to triple-boot, you should be able to work it out. Please share any findings as this is a work in progress.
I Hope You Enjoy!!!
I'm always available to answer questions. Unless I'm not, then I won't.:laugh:
Don't forget the "Thanks" button.:good::good:
For more visit visit our new Sub-Forum: Phoenix OS on XDA
Top Tips:
1. The live session does not save.
2. For Playstore: First thing, when booted, open Settings>Accounts>Google and sign in. Then open Playstore, stop the updating of apps with the stop button on update page. Go to Settings scroll to bottom and click on version #. You will get a pop-up "a newer version will be installed". Do not turn off automatic updates. Exit Playstore and wait. You should notice a notification that your apps are updating again. This is good! You should be good to go.
thanks. I found this ISO from you also: https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0
downloaded both, which makes me wonder why one is 600MB and the other 1,5GB
EDIT: [virtualbox] https://www.dropbox.com/s/bdqj6h229narxsn/PhoenixOS_v109_Rufus.zip?dl=0 wont boot for me (no bootable device), https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0 does and start sucessfuly
EDIT2: [virtualbox] https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0 installed so smoothly, and runs very nicely after the first test
Hi,
I just installed it and it's literally the same image as the official one, old play store, can't download/install play store apps, no root, chinese bloatware
am I missing something?
VyktorJonas said:
Hi,
I just installed it and it's literally the same image as the official one, old play store, can't download/install play store apps, no root, chinese bloatware
am I missing something?
Click to expand...
Click to collapse
Sorry, just found out I'm not getting alerts for my own thread. Which one did you download? The second selection is a stock un-rooted .iso. The official version is contained in an executable. Thought I would through the .iso up in case somebody wanted to tinker with it themselves. Not sure why you are having trouble with the Playstore though. Did you give it time to update itself. Lastly I did not remove any bloat. A majority of the pre-installed apps are user and are easily uninstalled, with a few exceptions. It is a very forgiving OS.
capoeiraES said:
thanks. I found this ISO from you also: Discontinued
downloaded both, which makes me wonder why one is 600MB and the other 1,5GB
EDIT: [virtualbox] Discontinued wont boot for me (no bootable device), https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0 does and start sucessfuly
EDIT2: [virtualbox] Discontinued installed so smoothly, and runs very nicely after the first test
Click to expand...
Click to collapse
Which version are you running? I really appreciate the input. If there is something amiss I need to get to the bottom of it,
Also, I am not seeing the difference in download size that you are referring to.
capoeiraES said:
thanks. I found this ISO from you also: https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0
downloaded both, which makes me wonder why one is 600MB and the other 1,5GB
EDIT: [virtualbox] https://www.dropbox.com/s/bdqj6h229narxsn/PhoenixOS_v109_Rufus.zip?dl=0 wont boot for me (no bootable device), https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0 does and start sucessfuly
EDIT2: [virtualbox] https://www.dropbox.com/s/ds8nflx1z1r1bt8/PhoenixOS_v-1-0-9.iso?dl=0 installed so smoothly, and runs very nicely after the first test
Click to expand...
Click to collapse
VyktorJonas said:
Hi,
I just installed it and it's literally the same image as the official one, old play store, can't download/install play store apps, no root, chinese bloatware
am I missing something?
Click to expand...
Click to collapse
Spent the night retesting, on three machines. ASUS Notebook with Intel Processor, HP Notebook with AMD Processor and a old HP Slimline desktop 2010 or something. I only ran in to trouble with the desktop. An incompatability with the mouse drivers, it still booted but I could not do anything. So I guess a newer machine is better. I figured out the difference in the iso size is due to the stock OS uses a system.sfs as opposed to my system.img I think there is a compression difference. In 7Z it shows a packaged size of 600MB. Once installed they are the same size. As far as the bloat, I cannot figure out where the data image is being drawn from. The .iso contains a kernel image, initrd image, ramdisk image and system image. If anybody could shed some light?
Once again I'm very sorry I did not get back sooner. I will check in often now.
Hi,
from what I tested, the Rooted ISO on the OP isn't rooted, but it does have a system.img, which was useful, I had to swap the system.img file with another one I found somewhere else
as to the Play store issue, I managed to fix it by removing and re adding my Google Account in Settings, seems to be a common issue btw
VyktorJonas said:
Hi,
from what I tested, the Rooted ISO (discontinued) on the OP isn't rooted, but it does have a system.img, which was useful, I had to swap the system.img file with another one I found somewhere else
as to the Play store issue, I managed to fix it by removing and re adding my Google Account in Settings, seems to be a common issue btw
Click to expand...
Click to collapse
Good. Are you talking about the first download or the second? I admit I did spend more time on the special edition. I also thought I had instructions for the Playstore posted... they can now be found in post #2. Anyway, thanks for getting back, you really should try the SE. :laugh:
bg260 said:
Good. Are you talking about the first download or the second? I admit I did spend more time on the special edition. I also thought I had instructions for the Playstore posted... they can now be found in post #2. Anyway, thanks for getting back, you really should try the SE. :laugh:
Click to expand...
Click to collapse
first one
edit:
Is there a fix for the s****y wallpaper quality?
Is there a timeline for updates? If not for the future, for past ones, I'd like to see how often it got updated
VyktorJonas said:
first one
edit:
Is there a fix for the s****y wallpaper quality?
Is there a timeline for updates? If not for the future, for past ones, I'd like to see how often it got updated
Click to expand...
Click to collapse
You can adjust the DPI in Settings>Display .don't know if that will help. Plus it doesn't seem to stick through reboots.. Mine are pretty sharp though.
v1.0.9 is current release about a month ago.
www.phoenixos.com/en_US/
www.fosshub.com/Phoenix-OS.html
www.droidx86.gdk.mx/phoenix-os/
The last one is my main stay.
bg260 said:
Which version are you running? I really appreciate the input. If there is something amiss I need to get to the bottom of it,
Also, I am not seeing the difference in download size that you are referring to.
Click to expand...
Click to collapse
I'm running "Unrooted Version .iso Only"
click on your first and second link to see the size diference.
btw: Playstore worked out of the box for me, actualy everything worked out of the box until now
EDIT: resolution I can't change. might be a Virtualbox issue
PhoenixOS in my opinion looks much better, although RemixOS feels better, Phoenix needs to give more of a "real Desktop OS" feel to it, they've been updating it every 2 to 4 weeks, which would mean a new update is right around the corner, with every update they seemed to have improved a lot and added plenty of new features, I'm loving it, it's been dual booting with my Ubuntu Gnome for about two weeks now
also, my cursor doesn't show up either, it's just the touch roung thingy, I'm just hoping it fixes by itself eventually
Remix has a better marketing plan. Joining with XDA. That forum is overly full of nonsense. I'm trying my best to spread the word.
@capoeiraES I figured out that one of the moderators at droidx86 mistakenly linked the wrong .iso. I have removed that feature for now. The .iso itself was 1.6g im thinking about zipping it and reposting. Didn't really think there would be interest in the unrooted version.
bg260 said:
@capoeiraES I figured out that one of the moderators at droidx86 mistakenly linked the wrong .iso. I have removed that feature for now. The .iso itself was 1.6g im thinking about zipping it and reposting. Didn't really think there would be interest in the unrooted version.
Click to expand...
Click to collapse
I just tried your rooted version again. It wont boot for me in virtualbox. I'll download it again
Might have to convert system.img back to system.sfs. I'll see what can be done.
how do I install a driver for my grafics tablet? can I just download the code and compile it in the terminal?
I guess that's what the rooting is for!?
capoeiraES said:
I just tried your rooted version again. It wont boot for me in virtualbox. I'll download it again
Click to expand...
Click to collapse
Got all the System.img converted to System.sfs if you want to try again. Also boots with UEFI now as well. Reposted un-rooted version.
capoeiraES said:
how do I install a driver for my grafics tablet? can I just download the code and compile it in the terminal?
I guess that's what the rooting is for!?
Click to expand...
Click to collapse
I haven't needed any additional drivers. Are you dual-booting your tablet?
Anybody care to comment on JMusic?