Database Users

[Shell Script] Setup a build environment for AOSP in a snap.

If you are like me you are tired of reformatting to have to type in a long mess of stuff just to use adb well I have simplified it in a small sh file. It installs all the applications according to Android's website. I even updated the application names to the ones which Ubuntu 11.10 64-bit recognizes. It's an initial release feel free to modify.
Extract all files to your HOME dir, edit the username in phones.rules and execute in terminal
Find the most recent version on github (Link in my Signature)
Download initial release here : https://github.com/elginsk8r/build_env/zipball/master

elginsk8r said:
If you are like me you are tired of reformatting to have to type in a long mess of stuff just to use adb well I have simplified it in a small sh file. It installs all the applications according to Android's website. I even updated the application names to the ones which Ubuntu 11.10 64-bit recognizes. It's an initial release feel free to modify.
Extract all files to your HOME dir, edit the username in phones.rules and execute in terminal
Find the most recent version on github (Link in my Signature)
Download initial release here : megaupload dot com ?d=QJ1VLJIL[/url]
Click to expand...
Click to collapse
gr8 idea how to run it on windows7??

doomhammer07 said:
gr8 idea how to run it on windows7??
Click to expand...
Click to collapse
You can't compile on windows, you need a linux distro or mac to do so!

cdesai said:
You can't compile on windows, you need a linux distro or mac to do so!
Click to expand...
Click to collapse
Or a Linux distro running as a VirtualBox VM under Windows.

a change to your script...line 14
cd ~/sdk/tools
should be changed to
cd ~/android-sdk-linux/tools
anyone could probably figure it out but for those in need and confused..

Can someone repost this script? Some sort of FBI warning on megaupload atm.

I'll reupload when I get home tonight with updated version
Sent from my HTC Glacier using XDA

link has been updated. Thanks JKILO for pointing that out I must have overlooked that one.

hey there!
is there a possibility to get this script anywhere?
the link to github is dead and i can't find it elsewhere...
would be really cool!
greetz n thx,
sUsH

[Q] What about the Alcatel OT Fire C (4019X)?

Hello!
I've been trying to see if there's any root exploits, ROMs, whatever for this phone. Is it Hamachi (4012) compatible? Or is it another species? It does seem there's not much about it.

The only thing I've found is this mail thread.
comments DOT gmane DOT org / gmane DOT comp DOT mozilla DOT devel DOT b2g / 12487
The Fire C is a Jelly Bean based one. Start from there.
If I can successfully flash mine will post results. Wish me luck.
resetreboot said:
Hello!
I've been trying to see if there's any root exploits, ROMs, whatever for this phone. Is it Hamachi (4012) compatible? Or is it another species? It does seem there's not much about it.
Click to expand...
Click to collapse

mancvso said:
The only thing I've found is this mail thread.
comments DOT gmane DOT org / gmane DOT comp DOT mozilla DOT devel DOT b2g / 12487
The Fire C is a Jelly Bean based one. Start from there.
If I can successfully flash mine will post results. Wish me luck.
Click to expand...
Click to collapse
Nope. Bricked phone.
Anyone knows how to use this files?
forum DOT gsmhosting DOT com / vbb / f272 / flash-file-request-alcatel-4019x-1883599

Where did you find these files? Can you point me to them?
Maybe I can make something out of it. The MTK Droid Tools is totally unable of dumping anything from this phone and it's supposedly designed for these kind of phones (the chipset is a MediaTek).
If only I could snatch the boot image...! But the /dev/ block devices do not make any sense to me, otherwise I'd have at least something to go back when I screw the boot loader.

The URL is in the post above, just replace " DOT " with "." and delete spaces.
Anyway, the direct link is
mediafireDOTcom/?t6x77dxpb9bucbf
Which one is boot, system, userdata? Do you have the original file sizes?
I've tried with various Hamachi (4012X) boot.img but none of them works.
PD: I cannot post links.

I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.

Wonderful! This is really useful info.
Now we can try to couple it with the FFOS SDK and try to get root and maybe upgrade to 2.0...
D'loading so I can start hacking...

resetreboot said:
Wonderful! This is really useful info.
Now we can try to couple it with the FFOS SDK and try to get root and maybe upgrade to 2.0...
D'loading so I can start hacking...
Click to expand...
Click to collapse
Please do so! An upgrade to 2.x is crucial even for copy/pasting text.

mancvso said:
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Click to expand...
Click to collapse
Great news, remember you can type *#3228# to know what are all these filenames in your device.
I have a 4019M (sold unlocked in this country) and I am interested on this, however I don't have experience flashing yet, as this is my first smartphone. If you need to do some tests from here for this particular device to get root and upgrades, feel free to ask!
This device is qualcomm based and gonk is jelly bean based, if I recall correctly.

Some news, they finally uploaded this month 4019X / 4019A GPL compliance sources into sourceforge · net / projects / alcatel / files /

Some progress to get a proper factory image
When using One Touch Update, I tried to figure what happens with the factory image download from the vendor. It downloads a bunch of 64 KiB files stored in a downloaded/ subdir of the programfiles application folder. They are downloaded via TCP, not using HTTP. Once the download is complete, out1.data and out2.data are generated, I guess all these files get somewhat assembled into these. They are placed in the programfiles application folder too, 203 MiB each. They look like a couple of Android sparse image files, according to header magic numbers. These files should be copypasted somewhere before ending the flash operation and closing the application, otherwise they will be deleted. Maybe these files contain interesting stuff :good:. There is also a log file showing addresses where is flashing and sizes of the images of the factory flashing operation.
Maybe some USB sniffing is worth, but not tested.

4019X Brick
Hi guys.
I have a 4019X bricked becasuse i tried to install a wrong system.img.
Can you upload again the factory flash images? The mediafire link is broken.
I made a backup of the original system with adb pull /system /system as mozilla´s recommend in the Firefox OS build prerequisites.
But i dont know how to compile to restore my phone. I tried this:
ANDROIDFS_DIR=<path to system backup> ./config.sh tarako
ANDROIDFS_DIR=<path to system backup> ./build.sh
but always fail.
If you dont know, can you tell me how to use the source code of alcatel to unbrik my phone:
sourceforge.net ... OT_FF_4019X_20150408.tar.xz
Thanks

Backup of the stock One Touch Fire C files
https://www.dropbox.com/s/nzn6g4qhh585ho4/4019X-2[X=A,B,C,D]TBHU1.rar?dl=0
Please keep us informed on any progress, now that Firefox has freed itself.

can u tell me if this rom has portuguese language? i need 4019x android or firefox with portuguese language? or anyway to add language?
best regards

mancvso said:
I managed to fix my phone!!
In the folder above (Mediafire)
boot.img is B1TC000112R0.mbn
recovery.img is R1TC000112R0.mbn
system.img Y1TC000112R0.mbn
Be sure to explicitly start in fastboot mode (Power+Volume down)
As a side note, if load recovery.img in boot.img the phone will start in that mode. I've had to do that to make it boot (and them flash boot.img)
Good luck. Pass it on.
Click to expand...
Click to collapse
Hi! I can not fix my Alcatel OT- 4019A yet. ¿could you please help me with that?
I don't know exactly what do with that archives.
Thanks!

Gsmfanatic said:
can u tell me if this rom has portuguese language? i need 4019x android or firefox with portuguese language? or anyway to add language?
best regards
Click to expand...
Click to collapse
The firmware doesn't have the Portuguese language, flashed it myself ...

[Utility] Android Image Kitchen & Flasher APK

Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis

atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
Click to expand...
Click to collapse
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk

Yes, you can try

tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.

Well I use in my apk AIK.mobile tools proposed by osm0sis.

atoxyd said:
Well I use in my apk AIK.mobile tools proposed by osm0sis.
Click to expand...
Click to collapse
https://github.com/osm0sis/AnyKernel2/ ?
from http://forum.xda-developers.com/showthread.php?t=2670512

bigsupersquid said:
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.
Click to expand...
Click to collapse
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.

atoxyd said:
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.
Click to expand...
Click to collapse
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.

nero curin said:
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk
Click to expand...
Click to collapse
Hi, did my apk work for you?

atoxyd said:
Hi, did my apk work for you?
Click to expand...
Click to collapse
only unpacking and repacking,didnt help on my device but yet again nothing else helps me compile kernel for this idol 3 so i guess this app works just not for me, bad luck :/
Sent from my 6045X using Tapatalk

Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay

atoxyd said:
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay
Click to expand...
Click to collapse
The scope of my tools is for Google's Android image standard as defined in the bootimg.h header from AOSP/CM. My tool forks have the widest support available for images which are standards compliant, supporting all commonly used ramdisk compression formats.
Supporting Sony's ELF, MTK's labeled and Samsung's headerless image formats along with the standard images (not to mention Samsung's and others' various deviations based on the standard header) and having the script/app differentiate between them would be a very large and difficult undertaking indeed. If that's your plan then I wish you the best of luck in your efforts.

hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well

atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis
Click to expand...
Click to collapse
Thank you for adding the appropriate credit back to your post. Patching, cross-compiling and scripting has taken significant work. :good:
The only other thing that I'd ask is that you do not use the name of Android Image Kitchen or AIK in the title of your app. I'd like to suggest maybe "Image Editor and Flasher" as a snappy alternative?

bigsupersquid said:
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well
Click to expand...
Click to collapse
Thank you my friend , you are the only one who supported me , and from the beginning.

atoxyd said:
Thank you my friend , you are the only one who supported me , and from the beginning.
Click to expand...
Click to collapse
it's a useful project, definitely worth a little testing and feedback.
besides, i remember what a pain it was getting my xda account eligible for posting the project i was all gung-ho about sharing (optimus v boot from sd card if i remember correctly)
sharing is cool, but a lot of the feedback tends to be annoying when there's no logs or other usable information, just "it's broken" or "can you implement for me on device XYZ."

bigsupersquid said:
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
Click to expand...
Click to collapse
Did you have an unlocked bootloader ?

nothing changed on the device, unlocked and still s-on, I'm not sure what went wrong the first try.
PEBKAC error probably
(problem exists between keyboard and chair)

I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.

atoxyd said:
I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.
Click to expand...
Click to collapse
Please use a different name for your app as I have requested.

[Root] Phoenix OS x86/x64 v2.0.6 (26 May) Rooted Images

Hey guys, today I downloaded the updated Phoenix OS and decided to root it. I'm kindly sharing my image for anyone who would like to download it:
Instructions:
Install Phoenix OS v2.0.6 and do not restart your computer
Download the correct system rooted.7z file provided in the Download section and extract it
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS. Complete the setup wizard
Install the latest version of SuperSU. Since Phoenix OS v2.0.6 comes with Play Store already, sign in with your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.145.32bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNZGhVNTFpSHRtUnc
Phoenix OS x64 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.144.64bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNdVBMOGtDY3RSdEk
Download Phoenix OS v2.0.6 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6010
History:
Uploaded original Phoenix OS system.img (for backup)
Uploaded Phoenix OS executable installers (for backup mirroring purposes)
Added x86 version of the rooted image
Compressed the system.img file so that it's faster for you to download!

[Request][Root] Phoenix OS x86 v2.0.6
Hey first of all finally i found the way to root Phoenix OS but there is a problem i have x86 bit version of Phoenix OS so i was hoping you could help out so could you kindly provide a rooted Phoenix OS x86 bit system.img please or tell me the method to root it i would appreciate the help.
And by the way i have a question i have a 64-bit operating system but when i installed Phoenix OS it said it is recommended to install the x86 bit version so i installed the x86 bit version so should i use the 64 or 86 bit version ????
Well the x86 bit version works fine but some glitches can be seen and it gets stuck if i leave it inactive for some time.

farazmajid56 said:
Hey first of all finally i found the way to root Phoenix OS but there is a problem i have x86 bit version of Phoenix OS so i was hoping you could help out so could you kindly provide a rooted Phoenix OS x86 bit system.img please or tell me the method to root it i would appreciate the help.
And by the way i have a question i have a 64-bit operating system but when i installed Phoenix OS it said it is recommended to install the x86 bit version so i installed the x86 bit version so should i use the 64 or 86 bit version ????
Well the x86 bit version works fine but some glitches can be seen and it gets stuck if i leave it inactive for some time.
Click to expand...
Click to collapse
Hey, I can work on getting the x86 version of the rooted image for you The method which I used could be found here.
Also, that suggestion sounds incorrect. What OS exactly are you running? Tell me more about your computer specs (CPU, Windows version, and especially how much RAM you have). If you have 4GB of RAM or more, I would go for the x64 version of Phoenix OS. Try it out and let us know if it works better for you, though there might not be much difference in performance. If I remember correctly, my Phoenix OS also causes my screen to go black after it's been sitting inactively for a while. I think it's a common issue with Phoenix OS.

meanhacker said:
Hey, I can work on getting the x86 version of the rooted image for you The method which I used could be found here.
Also, that suggestion sounds incorrect. What OS exactly are you running? Tell me more about your computer specs (CPU, Windows version, and especially how much RAM you have). If you have 4GB of RAM or more, I would go for the x64 version of Phoenix OS. Try it out and let us know if it works better for you, though there might not be much difference in performance. If I remember correctly, my Phoenix OS also causes my screen to go black after it's been sitting inactive for a while. I think it's a common issue with Phoenix OS.
Click to expand...
Click to collapse
The specs of my PC are
CPU: Core 2 Duo 2.4 Ghz (64-bit Architecture)
RAM: 6 GB
GPU: NVIDIA GeForce 8400 GS with 1 GB VRAM
Operating System: Windows 7 Ultimate 64-bit
I forgot to tell you i am dual booting Windows 7 Ultimate (64-bit) with Phoenix OS (86-bit)
Check these for more info
https://ibb.co/m7AFVv
https://ibb.co/h9khAv
https://ibb.co/kkgB3F
https://ibb.co/eVsJiF
https://ibb.co/hqJDHa
The inactive black screen bug of Phoenix OS has to do something with the lock screen in android which auto locks screen if inactive for some time.

Thanks for the extensive info. It looks like your computer should be able to run the 64-bit version of Phoenix OS just fine. Why don't you give it a try? Also, I posted the x86 version of the rooted image if you still need it.
farazmajid56 said:
The inactive black screen bug of Phoenix OS has to do something with the lock screen in android which auto locks screen if inactive for some time.
Click to expand...
Click to collapse
Good point, I will try to fix it. I'm assuming this issue can be eliminated by disabling the screen lock timeout timer.

meanhacker said:
Thanks for the extensive info. It looks like your computer should be able to run the 64-bit version of Phoenix OS just fine. Why don't you give it a try? Also, I posted the x86 version of the rooted image if you still need it.
Good point, I will try to fix it. I'm assuming this issue can be eliminated by disabling the screen lock timeout timer.
Click to expand...
Click to collapse
Precisely and by the way Thanks

farazmajid56 said:
Precisely and by the way Thanks
Click to expand...
Click to collapse
You got it! Let me know if you need anything else :good:

Root is working fine, but the one app that won't install successfully for me is Google Plus. It claims my "device isn't compatible with this version" which is weird, given that it worked in previous versions of Phoenix OS. Any thoughts on this? Chinese localization or something maybe?
Edit: I can't even install it if I download it from APKMirror btw.

The Wrath of Kahn said:
Root is working fine, but the one app that won't install successfully for me is Google Plus. It claims my "device isn't compatible with this version" which is weird, given that it worked in previous versions of Phoenix OS. Any thoughts on this? Chinese localization or something maybe?
Edit: I can't even install it if I download it from APKMirror btw.
Click to expand...
Click to collapse
Hmm thanks for bringing it up. I haven't tried the app on Phoenix OS. Does it work on the original non-rooted version of Phoenix? Give it a try and let us know.

I've noticed that there are several apps that don't work for some reason. Some of the apps I use often give me an Error 501 when trying to install from anywhere. I've tried everything and still haven't gotten them to work. Hopefully more compatibility is coming soon.

meanhacker said:
Hmm thanks for bringing it up. I haven't tried the app on Phoenix OS. Does it work on the original non-rooted version of Phoenix? Give it a try and let us know.
Click to expand...
Click to collapse
Yea, it doesn't work in the non-rooted version either. Probably a build.prop issue with whatever the device is being identified as. I tried to modify it several ways, but couldn't get it working. It worked in previous versions, so I'm hoping they'll correct it soon. I'll report it in the official forums too.

Hi
After installing the PhoenixOS, the Windows Boot Manager(the blue screen one) did not appear when booting,it will boot into the windows 10 directly and I cant select to boot into the Phoenix OS.So I need to press the F12 button everytime i power on my laptop to choose whether i want to boot into windows or phoenix OS via the bios boot manager.Is there any solution to make my Phoenix detectable by Windows Boot Manager?

kirito990701 said:
Hi
After installing the PhoenixOS, the Windows Boot Manager(the blue screen one) did not appear when booting,it will boot into the windows 10 directly and I cant select to boot into the Phoenix OS.So I need to press the F12 button everytime i power on my laptop to choose whether i want to boot into windows or phoenix OS via the bios boot manager.Is there any solution to make my Phoenix detectable by Windows Boot Manager?
Click to expand...
Click to collapse
Chances are, Windows Boot Manager got moved up in the boot sequence. Using EasyUEFI, you can move the Phoenix OS entry back up so it starts booting:
Download and install EasyUEFI.
Open it, click OK, click Manage EFI Boot Option and post what you see here. This is your boot order. If Windows Boot Manager is above Phoenix OS, that means that Windows is being loaded using its default boot loader. What you're trying to do is use the Phoenix OS GRUB loader.
Click on Phoenix OS and click the green up arrow until the Phoenix OS entry is at the very top.
Restart the computer and see if it boots to the GRUB loader.
If it doesn't work, let's investigate what's inside your EFI partition.
First, open command prompt as admin (press start, type in cmd, press Ctrl+Shift+Enter, then press yes). Type in:
Code:
mountvol X: /s
Then type in:
Code:
cd X:\EFI\Boot
And then type in
Code:
dir
and press enter. It should list all the files in that boot directory. Post here on the forum what you see. You can use the command
Code:
dir >>C:\xda-efi-output.txt
to output to a text file and then it would make it easier for you to post it here. The file is located on the root of the C:\ drive. Open it and copy-paste what's inside on the forum, preferably inside code or hide tags to keep it neat. Assuming it's there, you can type in
Code:
grub.cfg
which will open the file with your default text editor. Feel free to post what's inside your grub file.

meanhacker said:
Hey guys, today I downloaded the updated Phoenix OS and decided to root it. I'm kindly sharing my image for anyone who would like to download it:
Instructions:
Install Phoenix OS v2.0.6 and do not restart your computer
Download the correct system rooted.7z file provided in the Download section and extract it
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS. Complete the setup wizard
Install the latest version of SuperSU. Since Phoenix OS v2.0.6 comes with Play Store already, sign in with your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.145.32bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNZGhVNTFpSHRtUnc
Phoenix OS x64 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.144.64bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNdVBMOGtDY3RSdEk
Download Phoenix OS v2.0.6 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6010
History:
Uploaded original Phoenix OS system.img (for backup)
Uploaded Phoenix OS executable installers (for backup mirroring purposes)
Added x86 version of the rooted image
Compressed the system.img file so that it's faster for you to download!
Click to expand...
Click to collapse
Hi Successfully Installed Phoenix os with rooted Image, updated superSu app using Playstore, but I am unable to access to root i.e unable to check log using Log cat apk,

nanianji99 said:
Hi Successfully Installed Phoenix os with rooted Image, updated superSu app using Playstore, but I am unable to access to root i.e unable to check log using Log cat apk,
Click to expand...
Click to collapse
Hey, I don't know what the problem could be. Do other root apps work? Maybe try using another logcat app

meanhacker said:
Chances are, Windows Boot Manager got moved up in the boot sequence. Using EasyUEFI, you can move the Phoenix OS entry back up so it starts booting:
Download and install EasyUEFI.
Open it, click OK, click Manage EFI Boot Option and post what you see here. This is your boot order. If Windows Boot Manager is above Phoenix OS, that means that Windows is being loaded using its default boot loader. What you're trying to do is use the Phoenix OS GRUB loader.
Click on Phoenix OS and click the green up arrow until the Phoenix OS entry is at the very top.
Restart the computer and see if it boots to the GRUB loader.
If it doesn't work, let's investigate what's inside your EFI partition.
First, open command prompt as admin (press start, type in cmd, press Ctrl+Shift+Enter, then press yes). Type in:
Code:
mountvol X: /s
Then type in:
Code:
cd X:\EFI\Boot
And then type in
Code:
dir
and press enter. It should list all the files in that boot directory. Post here on the forum what you see. You can use the command
Code:
dir >>C:\xda-efi-output.txt
to output to a text file and then it would make it easier for you to post it here. The file is located on the root of the C:\ drive. Open it and copy-paste what's inside on the forum, preferably inside code or hide tags to keep it neat. Assuming it's there, you can type in
Code:
grub.cfg
which will open the file with your default text editor. Feel free to post what's inside your grub file.
Click to expand...
Click to collapse
Sorry but i cant find the PhoenixOS from the EasyUEFI entries list...
Here is the text file

Phoenix OS x86/x64 v2.0.7
hi .... good new ... new release is out today as:
Phoenix OS x86/x64 v2.0.7

kirito990701 said:
Sorry but i cant find the PhoenixOS from the EasyUEFI entries list...
Here is the text file
Click to expand...
Click to collapse
The solution is to add it yourself.
When in EasyUEFI:
1. click the add button.
2. From type list select Linux/Other.
3. Add a Description (this is what it will be called in the UEFI menu).
4. Select your efi partition (the FAT32 one with the light dot).
5. Click Browse
6. Select \EFI\PhoenixOS\bootx64.efi and click OK.
7. Click OK
8. Use arrows to reorder list to your needs.
And that text file you put up seems to be nothing to do with your EFI. It's a list of your windows directory.

TNTPro said:
The solution is to add it yourself.
When in EasyUEFI:
1. click the add button.
2. From type list select Linux/Other.
3. Add a Description (this is what it will be called in the UEFI menu).
4. Select your efi partition (the FAT32 one with the light dot).
5. Click Browse
6. Select \EFI\PhoenixOS\bootx64.efi and click OK.
7. Click OK
8. Use arrows to reorder list to your needs.
And that text file you put up seems to be nothing to do with your EFI. It's a list of your windows directory.
Click to expand...
Click to collapse
Thank you so much to reply this. And again...after the phoenix os is added into the list and moved to the uppest side...I tried to restart my laptop but it still boots into windows without the system selection screen. After that I checked the list in EastUEFI and the phoenix os was missing again from the list :silly:

kirito990701 said:
Thank you so much to reply this. And again...after the phoenix os is added into the list and moved to the uppest side...I tried to restart my laptop but it still boots into windows without the system selection screen. After that I checked the list in EastUEFI and the phoenix os was missing again from the list :silly:
Click to expand...
Click to collapse
What kind of laptop do you have? It sounds like your bootloader is locker. Try going into BIOS and disabling "Secure Boot" or whatever is available from your motherboard. Also, since you couldn't find the Phoenix OS entry, maybe you should try reinstalling Phoenix OS.

[TOOLS] Necessary tools for building the Pixel 2 (XL) Kernel

THIS IS NOT A "HOW TO BUILD A KERNEL" POST
The Pixel 2, unlike other phones I've worked with, requires two extra tools: dtc (Device Tree Compiler) and mkdtimg.
Yes, dtc is available in the main repos for most linux distros, but the Pixel 2 kernel requires the AOSP modified version of dtc.
First, grab the Pixel 2 + XL Unified kernel source (wahoo) from https://android.googlesource.com/kernel/msm/+/android-msm-wahoo-4.4-oreo-dr1
Then download wahoo-kernel-tools.zip file attatched to this post and unzip it. Make sure that the 2 files in the bin folder are available in your path (possibly by moving them to ~/bin) and symlink or move the libc++.so into an included library directory, such as /lib, /usr/lib, or /usr/local/lib.
These specific binaries were compiled on Arch Linux by me, so they may not work on every system. To build binaries compatible with your system, sync any android oreo source (AOSP, Lineage, Carbon, etc.) and run "make dtc mkdtimage -jX" instead of "make bacon" or your normal command. The binaries will be located in out/host/linux-x86/.
This is tested and working with the stock google 4.9 toolchain and the initial source as of Oct 23rd, 2017.

frap129 said:
THIS IS NOT A "HOW TO BUILD A KERNEL" POST
The Pixel 2, unlike other phones I've worked with, requires two extra tools: dtc (Device Tree Compiler) and mkdtimg.
Yes, dtc is available in the main repos for most linux distros, but the Pixel 2 kernel requires the AOSP modified version of dtc.
First, grab the Pixel 2 + XL Unified kernel source (wahoo) from https://android.googlesource.com/kernel/msm/+/android-msm-wahoo-4.4-oreo-dr1
Then download wahoo-kernel-tools.zip file attatched to this post and unzip it. Make sure that the 2 files in the bin folder are available in your path (possibly by moving them to ~/bin) and symlink or move the libc++.so into an included library directory, such as /lib, /usr/lib, or /usr/local/lib.
These specific binaries were compiled on Arch Linux by me, so they may not work on every system. To build binaries compatible with your system, sync any android oreo source (AOSP, Lineage, Carbon, etc.) and run "make dtc mkdtimage -jX" instead of "make bacon" or your normal command. The binaries will be located in out/host/linux-x86/.
This is tested and working with the stock google 4.9 toolchain and the initial source as of Oct 23rd, 2017.
Click to expand...
Click to collapse
Thanks for the files dude, you saved me some serious time since I don't need to sync AOSP

DespairFactor said:
Thanks for the files dude, you saved me some serious time since I don't need to sync AOSP
Click to expand...
Click to collapse
No problemo, I figured I'd post this since my fastboot is being retarded and I can't do much else

Forgive me for being a noob, but would these new requirements for the Pixel 2 cause existing tools used to pack/unpack the boot image fail or at least partially fail? I'm wondering if this is why we can't get Magisk to work
edit: to be clear, when I unpack the boot.img file all I see are kernel and ramdisk. When I unpack the boot.img from the Pixel 1 XL, I see those same 2 files along with devicetree.dtb and kernelimage

skaforey said:
Forgive me for being a noob, but would these new requirements for the Pixel 2 cause existing tools used to pack/unpack the boot image fail or at least partially fail? I'm wondering if this is why we can't get Magisk to work
edit: to be clear, when I unpack the boot.img file all I see are kernel and ramdisk. When I unpack the boot.img from the Pixel 1 XL, I see those same 2 files along with devicetree.dtb and kernelimage
Click to expand...
Click to collapse
Maybe? It doesn't seem like how the boot image is packed has been changed, just how the actual kernel image is put together.

nathanchance said:
Maybe? It doesn't seem like how the boot image is packed has been changed, just how the actual kernel image is put together.
Click to expand...
Click to collapse
Strange. Thanks for the response though. In the Magisk thread here, someone has posted a boot image that was simply unpacked/repacked (no changes) and we can't get it to boot. I don't want to derail this thread any further though.

skaforey said:
Forgive me for being a noob, but would these new requirements for the Pixel 2 cause existing tools used to pack/unpack the boot image fail or at least partially fail? I'm wondering if this is why we can't get Magisk to work
edit: to be clear, when I unpack the boot.img file all I see are kernel and ramdisk. When I unpack the boot.img from the Pixel 1 XL, I see those same 2 files along with devicetree.dtb and kernelimage
Click to expand...
Click to collapse
skaforey said:
Strange. Thanks for the response though. In the Magisk thread here, someone has posted a boot image that was simply unpacked/repacked (no changes) and we can't get it to boot. I don't want to derail this thread any further though.
Click to expand...
Click to collapse
No they don't, these just build the dtb/dtbo. The magisk issue is with patching sepolicy likely.

frap129 said:
No problemo, I figured I'd post this since my fastboot is being retarded and I can't do much else
Click to expand...
Click to collapse
Did you try to flash a factory image and get stuck in the bootloader? If so, extract 'image-walleye-[build number].zip' and flash each image manually. fastboot -w update doesn't work for some reason. After you flash all the images, do fastboot format userdata, and you should be back to normal. Took me a couple hours to figure this out.

ryanbg said:
Did you try to flash a factory image and get stuck in the bootloader? If so, extract 'image-walleye-[build number].zip' and flash each image manually. fastboot -w update doesn't work for some reason. After you flash each image, do fastboot format userdata, and you should be back to normal. Took me a couple hours to figure this out.
Click to expand...
Click to collapse
Thanks! I don't get stuck in the bootloader, but it won't let me flash boot images. Fastboot either hangs or spits out "remote: error: max size not reported"