Database Develop

Flashable Linux and Android

This thread is about installing Android natively on your Vogue so it completely replaces Windows Mobile.
[size +1]Important: This thread is now out of date, if you want to flash Android, use the new "norootfs" NBHs.[/size]
There are 2 installation methods:
If you are already running android from your sd card then use method 2, if you want a fresh install of android 1.5 from a windows machine use method 1.
For both methods, you must have a HardSPL installed, if you have flashed a custom wince rom before then you will, otherwise read one of the other threads on XDA about how to do this.
Method 1:
------------------------------------------------------------------
download the following:
http://www.mediafire.com/?zldjhfnkzk2
Unzip it and follow the instructions in README-ANDROID.txt.
All you have to do is copy the androidinstall.tar file to your sd card and run ROMUpdateUtility.exe on your PC.
Now Donate:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
You will also need a new rootfs:
http://it029000.massey.ac.nz/vogue/files/rootfs.zip
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
There are 3 ways to flash a rom.
1. Use ROMUpdateUtility under windows (this may not work on these roms, i haven't tried it). Rename the nbh file to RUU_signed.nbh.
2. Use HTCFlasher under Linux, this is what I have been doing and although a bit quirky, it does work. A binary that fixes a few things with HTCFlasher is on the website.
3. Rename the nbh file to VOGUIMG.NBH, put it on an SD card and boot the phone while holding down the power and camera keys.
When it starts, it should be running from nand. The tmp and cache dirs are still mounted from sd, so you do need the sd card in there but it's not really used much.
If something goes wrong or you haven't copied the correct files, press volume up while it is booting (after the two vibrates preferably). It will display a message saying that its in recovery mode. You should be able to plug the phone into a computer and the sd card will appear as a usb drive. You can also connect using adb.
There are a few limitations, rootfs must be less than 13M, system must be less than about 90M and data must be less than about 128M. This means unless you use a very stripped down system with apps2sd, hero probably won't work.
I've put a linux adb binary on the files page that fixes the annoying history 'feature' too.
Remember, this will completely wipe windows mobile and all your data from the phone. Run android from SD first to make sure you like it and don't want to be able to easily go back to windows mobile.
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted

Woot!
Doing this now =)

dzo said:
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Click to expand...
Click to collapse
I'm paypaling 5 bucks right now.... and I dont have a Vogue, I have a kaiser, but hey, $5 is long overdue for all the work you've done for the kernel... if NAND support hits the kaiser, I'll probably throw another $5-10 your way.
*paypaled - I normally dont do this kind of stuff, but its the holiday season, the MSM Android project has made SO much progress cause of DZO, if everyone just donated $5-10, it would at least be a nice gesture for all the work he's done*

I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?

After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.

Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?

If I understand correctly, theres "NO" build in here, you play with builds in your DS, and when you are ready and like one..you just use that system.sqsh data.img rootfs (provided) and..the nbh, all in the root of the sd card. And it will flash the nand with your files! So..thats it!
Nice one dzo, hoping for you to get to kaiser

Hey Martin, I can't even use these flashable images, but if it weren't for you I wouldn't even be running Android via haret, plus you've answered so many of my questions and I've never donated. So, since you're actually now, I'll donate $10.

flashing from windows
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.

gswarriorfan said:
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
Click to expand...
Click to collapse
nothing that hasnt already worked works there is no change...
dj13241 said:
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Click to expand...
Click to collapse
yea camera + power + reset hole
Shidell said:
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
Click to expand...
Click to collapse
i can answer a few
1 nothing that wasnt already working this isnt a build!!!, this is a way for VOGUE users to be able to put a working build "data.img and system.sqsh" they already have working on their phone and to be able to get rid of android
2 this isnt a build
3 320x240 shows more on screen 320x428 and 320x480 show more on screen but it is a little blurry
4 you will require adb drivers located on http://code.google.com/p/vogue-android and as far as i know they work on vista 32 and win 7 32 bit and there are different ones also located at vogue-android for win 7 64b
there are adb drivers for linux in the android SDK located here http://developer.android.com/sdk/1.6_r1/index.html make sure you download 1.6r1 though! 1.5r3 doesnt work for our devices in linux
5 just reflash any wm rom (that works with vogue of course)
mrkite38 said:
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
Click to expand...
Click to collapse
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice

Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?

Ahhh ok I get it now. I'll still donate when I get it up and running. Thanks!

OMFG!!!! dzo you are something else!!!
I just got my Vogue a few weeks back and I am surprised on how well Android runs on this thing (I have a Raphael as well, but no comparison to this)
Having a flashable rom to a WM device... unbelievable...
Kudos for your work man!!!!
I guess the question on a lot of people's minds right now is this... how do you go back to WM?

you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Click to expand...
Click to collapse
I tried that and it came back in bootloader with 'RUUNBH' in the upper right corner. Then I added the task3 and it booted normally. Who knows, maybe I did something else funny.
I used htcflasher on my newly-reloaded ubuntu laptop, but I wasn't able to get it to work under windows. So I thought that maybe flashing from windows was ok, but it just needed a kick through mtty to get going.
What do those two bootloader commands do? Not that it really matters since dzo says the newest version should work from windows anyway...

egzthunder1 said:
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
Click to expand...
Click to collapse
Boot back to bootloader and flash it! Did that myself last night.

Also, how do we make a smaller data.img? I keep getting 256MB versions.

scizzle said:
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Click to expand...
Click to collapse
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot

Thanks you so much dzo. i got this working, now im going through all my android files on my computer to find a build that i like, and wanna keep as my main build, but one thing, does the data really have to be less than 128mb? because almost all my android builds are alot bigger which is annoying.
but other than that it worked like a charm. thanks so much.
p.s. once i get some $$ (the 15th of december [my payday]) and find a permanent build i'll send some donations for you hard work.

dzo said:
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Click to expand...
Click to collapse
Legend! Thank you. I will try it as soon as I can figure out the data.img haha.

scizzle said:
Also, how do we make a smaller data.img? I keep getting 256MB versions.
Click to expand...
Click to collapse
jamezelle said:
i used the following commands to make a new data img
Code:
dd if=/dev/zero of=~/data.img bs=1048576 count=128
mke2fs -F ~/data.img
to make a blank 128 mb data.img file in my home folder
Click to expand...
Click to collapse
- I can now confirm that flashing the nbh with the ruu works from Windows.
- dzo, I have a panel type 3 us sprint vogue. everything booted up fine, the buttons work, but the touchscreen isn't. Will post logcat / dmesg in a bit.
edit: uploaded zip w/ logcat and dmesg

[DEV] Ubuntu on Nexus S (natively)

Ok, so following on from the MeeGo thread, I have Ubuntu booting on the Nexus S using the same method and same kernel.
The Ubuntu image used is the HD2 Ubuntu image (v 0.3), loaded from a file on the internal memory (again, no flashing required - you can thank me later).
The touchscreen isn't yet working, but that's my kernel at fault. Will fix that with the MeeGo stuff.
If you want to try this yourself, first grab yourself a copy of Ubuntu for HD2, and take just the rootfs.ext2 file and drag it to your Nexus S (put it in a folder called 'ubuntu' - lowercase is important!).
Then use fastboot to boot the following image (or flash it to recovery partition if you're daring and know how dangerous that can be):
http://dl.dropbox.com/u/8657343/bootUbuntu.img
You will need to do one minor edit once the device is booted; you will see the screen output is very weird; ADB push the following file to /etc/X11/xorg.conf, and then reboot Ubuntu:
http://dl.dropbox.com/u/8657343/xorg.conf
If you're in any way interested, please click the thanks button! Otherwise, enjoy!

nice!
the next thing we'll need after getting the touch screen working
is to have a calling app daemon, and make sure internet works on both 3G and WiFi

nice, look same at Ubuntu Netbook Edition

What about Galaxy S?

Njcki said:
What about Galaxy S?
Click to expand...
Click to collapse
In theory the same stuff should work; I don't have a Galaxy S to test on or I'd try it. I don't know anything about the Galaxy S' bootloader, or how much the kernel would differ (I'm guessing not at all, since this is a stock Samsung kernel from the Android kernel source)

I did an article on my site http://www.android-ita.com/dev-port-di-ubuntu-sul-nexus-s/
Maybe some italian devs, will help you

Thanks for this, gonna have a play now
Why is it dangerous to flash the boot image to recovery? Isn't fastboot lower level than recovery, or have I got that wrong?

nice, thanks. trying this as soon as my wife gets off my phone.

Oh my god.. You are awesome good sir. Will give it a run when touch is up and running!

I'd love it to be run from Android....i dont want it natively, just to test it...booting for example from an android app

I would love to know if this will work on Epic 4G. I'm going to give it a shot to see what happens.

Great job
Could you give us the sources of your kernel ? Is it patched ?

Tyruiop said:
Great job
Could you give us the sources of your kernel ? Is it patched ?
Click to expand...
Click to collapse
There are no changes to the kernel at all so far. I changed the config file to enable VTs, that's it.

Ok, thank you, I'll try to build one myself

can this method be used to install android 2.3 on a phone running android 2.1,
especilly in the case when upgrading is difficult because of kernel and locked bootloader (like motorola devices) ? excuse me if it is a silly question, i'm not a coder.

would it be possible to make an app that re-boots into fastboot and runs the fastboot command. since we dont always have a comp available to run fasboot which makes this useless if your not at home, or have a laptop (in which case you dont need ubuntu on a phone)

works on Nexus One right now ?
--> ok I'm trying

It blocks on X screen of my nexus one.. before the classic bootanimation.zip
Someone have any idea about that ?

Ok, so I've got wifi working . Here is my solution. A little bit crappy but... hey... it's a start ! Also, I tried compiling the kernel with the module built in and it wont boot, and I don't know why ?
Howto get wifi :
1) Boot Ubuntu following stroughtonsmith indications
2) Download http://tyruiop.org/~tyruiop/wifi_nexuss_ubuntu.tar.bz2
3) push the vendor directory at the root. The path must remain (/vendor/firmware etc...) and the bcm4329.ko file wherever you want.
4) reboot under ubuntu
5) *optional, only if ifconfig -a doesn't show eth0* type insmod /path/to/bcm4329.ko
6) Type "ifconfig -a". An eth0 interface should appear. It's wireless. You can configure it with wpa_supplicant without a problem .

Uhm.. with Nexus One, Ubuntu blocks on X SCREEN (before the classic bootanimation).. Maybe something that I do is wrong ?
- Download HD2 Ubuntu
- mkdir ubuntu/
- put in ubuntu/ the fs on the archive I downloader
- put ubuntu/ in the SDCARD
- adb reboot bootloader
- fastboot boot bootUbuntu.img
Is it correct ?

[Guide] How to fix black screen of death after dirty flashing lollipop

On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode. Now your lock screen's gone, and you can normally boot your phone. If you're doing this on recovery, you should mount /data partition to locate the file.
There could be some other problems because your phone still thinks that you haven't initiallized it, so you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664

FreakyTux said:
On threads of lollipop flashing, There are quite lots of people asking about the black screen issue, but not really clear solution's out there.
These are the symptoms:
1. After booting, you get black screen with just upper notification bar and back button below
2. If you turn on the screen after a few second, you see the normal screen but only for a fraction of second.
3. You can hear some notification sound, but notification bar still says "no notification" (or something, well I'm not using english ui )
4. no response on cancel button
The reason is that, you've set a lock screen before, but your phone thinks you've never performed initial setup, so your phone gets confused and doesn't know what to do.
You can solve this by deleting /data/system/gesture.key (for gesture lock) or /data/system/password.key (for password lock) on recovery mode.
after that, you should manually run initial setup by "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity" on normal boot, to avoid several problems.
I hope this helps!
credit : @nighthammer http://forum.xda-developers.com/showpost.php?p=56715651&postcount=7664
Click to expand...
Click to collapse
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.

perdid0 said:
This would be sweet except for some reason I hadn't accepted the adb authorization request on my device before I went all darkscreen duck.
wipe it is.
Click to expand...
Click to collapse
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.

FreakyTux said:
You can delete the file via recovery, with file explorer or adb.
Since you have to unlock the bootloader to flash a factory image, you can flash a recovery image any time if you need one.
Click to expand...
Click to collapse
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!

perdid0 said:
i cannot find that file in the location you specified. any other suggestions for locating it?!
---------- Post added at 09:23 AM ---------- Previous post was at 09:16 AM ----------
actually.......i found it!!!! same place you said!!! deleted both .key files and rebooted.......the screen was gone allowing me to accept the adb autorization and run the setupwizard!!! woot woot.....thanks a billion!!
Click to expand...
Click to collapse
I'm glad that it helped!:highfive:

Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !

jordanl68 said:
Hey man, thank you for your post !
I delated the file you said, but i didn't understand what should I do then ? Does it work if I don't do that adb setup (that I don't know what it is..)
Thank you for your help !
Click to expand...
Click to collapse
Check the help threads for Nexus devices, there are "how-to" ADB & fastboot guides just everywhere. It works for all Nexus devices just the same way.
tetakpatalked from Nexus 7 flo

Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.

HELP! BLACK SCREEN ISSUE (Lollipop)
I flashed cm12 on my Galaxy Grand 2,but everytime i push the power button to unlock the screen,All i get is a black screen.I can hear touch sounds and responses and the harware buttons light up,but that's it.The black only goes on rebooting and I have to reboot my phone everytime I unlock it.Please Help?

Better Explanation
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture

akastixx said:
Please add this to your post. I had the black screen, but I never had a password set up. The black screen was happening because before I flashed an update, I had a system profile set to bypass the lockscreen. Once I put it back on the default profile (which you can do from the notification bar) everything was fine.
Click to expand...
Click to collapse
I don't understand what you're saying. I've never seen "system profile set to bypass the lockscreen". could you tell me more specifically?
Aman_Arora said:
To make this guide appear better , and make it more easy doing etc etc..
Add this instead of a line method (well explained)
Download Aroma File Manager
Place it in your scdard directory
Boot in recovery
Mount Data
Go to Install and flash this zip..
Navigate to /data/system
Now delete password.key if a normal password or
gesture.key if a gesture
Click to expand...
Click to collapse
Thanks for your help. that's also a great workaround, but you know, it was nexus 5 that I was working on. If you were to place the file on the device, you would have to use adb anyway.

how can you do anything while screen is black? You just do not have any options displayed. I mean I am a layman

As everyone involved seems to be new to rooting, judging from the number of posts , tell them to READ READ READ . There is something called running before you can walk.

A clean install avoids the BS to begin with ...

Doesn't work with Nougat 7.1.1 (Dark ROM)
Does anyone know what if this solution works with Nougat 7.1.1 (Dark ROM)? I couldn't find the given files under /data/system, but I've found one as gatekeeper.password.key. However, if I delete it and reboot, I still get black screen.
Also, trying to run the setup wizard using ADB gives me a "SecurityException: Permission Denial: starting intent { ... } from null ( ... ) not exported from uid 10020".
Any ideas?

[rom][android m][preview 2] nexus 5

For all those complaining insufficient information to flash Preview 2 of Android M to your nexus 5, here is the comprehensive guide to flashing the preview.
Install ADB and Fastboot to your computer
Follow this link http://forum.xda-developers.com/showthread.php?t=2588979&__utma=248941774.236267929.1403796127.1403796127.1403796127.1&__utmb=248941774.4.10.1403796127&__utmc=248941774&__utmx=-&__utmz=248941774.1403796127.1.1.utmcsr=google%7Cutmccn=%28organic%29%7Cutmcmd=organic%7Cutmctr=%28not%20provided%29&__utmv=-&__utmk=25906750
For MAC/linux
Follow this link
http://forum.xda-developers.com/showthread.php?t=2564453
Remember to head into settings > developer options and enable USB Debugging first.
download Android M Developer Preview from Google website for your specific device http://developer.android.com/preview/download.html
unzip these files to a folder you can access Desktop preferably
If your Nexus is not bootloader unlocked you should do that first.
Open a Terminal in the adb folder and type the command below then hit enter.
adb reboot bootloader
In Fastboot type:
fastboot oem unlock
Then hit enter. Follow the on-screen instructions and choose to erase the device. Wait a minute or so for it to unlock. This removes everything on your device.
If your bootloader is already unlocked, reember to wipe data before flashing. Do this by using these commands in cmd or terminal
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot reboot
How to Flash the Image
Now open the folder containing the unzipped Android M System Image file you downloaded. Type cmd in the address bar. Type the following commands posted below and hit enter. On a Mac you can open Terminal in the folder by enabling terminal shortcuts in settings. This is key for Mac users. Head to System Preferences and select Keyboard > Shortcuts > Services. Find “New Terminal at Folder” in the settings and click the box. Now when you’re in Finder, just right-click a folder and you’re shown the open to open Terminal.
Once in terminal simply copy and paste the commands below to install the Android M beta to your Nexus 5, Nexus 6, Nexus 9, or even the Nexus Player.
flash-all.bat
This will flash all of the needed files. If you are on a Mac or other computer you will need to type;
sudo ./flash-all.sh
This will push all of the files and update your device to the just released Android M developer preview beta. The files will start pushing and installing and your Nexus device may reboot and you will see an Android figure and then a moving Android logo. The logo screen may stay for a long time. Don’t unplug the device. This may last 10 minutes or longer.
It’s worth noting that some users may experience a “missing system.img” error and the installation will be aborted. This is because the way you’re trying to flash the update. Instructions on how to get around this can be found right here. Essentially users will need to unzip the update.zip folder and move all the images to the original folder we mentioned above, then manually flash them one by one, vs the flash-all command mentioned above. Only do this if you run into issues.
If you run into bootloop, follow this guide http://forum.xda-developers.com/google-nexus-5/help/bootloop-android-m-preview-2-t3154608/post61802470#post61802470
ENJOY!
Credits: Cory Gunther http://www.gottabemobile.com/2015/05/28/install-android-m-beta-download/

Thanks for the work for us.

I was able to install M2... but i am having trouble getting it rooted.. please help.. seems to be in bootloop.

Jaws4God said:
I was able to install M2... but i am having trouble getting it rooted.. please help.. seems to be in bootloop.
Click to expand...
Click to collapse
Manual here http://forum.xda-developers.com/google-nexus-5/development/rom-android-m-t3121186

@buildsaurabh
Thanks for the PM.
It is kinda convincing that this guide is more elaborate and a safe way to do this...even if it is the same result at the end.
I hope this helps others.
Thread open again

thanks for the guide, but this is not a rom just a tutorial hence the thread title should be changed accordingly.

Not to be that guy,
#1 do we really need another tutorial on how to flash your nexus?
#2 not a ROM its a tutorial
#3 the development section is not the place for this.
Plus there's already a dedicated android M thread.
Sent from my Nexus 5 using XDA Free mobile app

is anyone having issues with video playback? with despair 1.8 it would play audio with no video.. with elementalx.. it would play video but distorted.. anyone else having this issue?

buildsaurabh said:
[rom][android m][preview 2] nexus 5
Click to expand...
Click to collapse
This isn't a ROM, it's a guide so moved to General.
OP, please change the title to reflect this. Its misleading.

Looks like a "hit count" thread to me
Sent from my Nexus 5 xda-dev app

[TOOL] crosshAtchDB: Pixel 3 XL Flash Tool

I'm trying to create an application to make flashing files on our pixel devices easier.
Features:
Install ADB
Unlock bootloader
Reboot to bootloader
Download and install factory images
Download and install TWRP
Download Magisk
Easy to use GUI
Enjoy! :good:
Credit to Dees_Troy and bigbiff for TWRP image.
Feel free to modify and hack away at the source.
WARNING: I am not responsible for anything that goes wrong using this tool, it works fine on my windows 10 machine, and tested on windows 7. However, make sure you know what these tools are doing beforehand.
New update!
Beta Release
What's New?:
All new base being built.
Better .exe support (requires installing the app)
Console interface for now.
Removed some features that were broken in the old app, will add them back one-by-one, but this time, not until they work 100%.
Usage:
Just follow the prompts on screen.
Allows picking the files for booting TWRP or pushing files via ADB.
Install:
Easy method (requires install): https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshAtchDB-2.3-win32.msi
Install the app with the provided .msi, choose where you want to install it. Open the folder where you installed it and run the crosshatchdbbeta.exe.
Build/Run from source:
Requires:
source .py file: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshatchbeta.py
cxfreeze config: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/setup.py
To run from source, just install Python on your PC, then from cmd window run : "pip install requests".
Then just double click on the crosshatchdbbeta.py file.
To build the .exe:
You need both files from above.
Install Python
python -m pip install cx_Freeze --upgrade
With setup.py and crosshatchdbbeta.py in the same directory, run "python setup.py build"
This is a very minimal release, I will continue to fix any bugs and add features once they are working better.

Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
**Didn't want to waste thread space so I'm editing this to reply** - Thank you so much for the response below! Very helpful! I'm up and running and really appreciate the tool and the help!

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
No problem, quick usage guide to make sure it goes smooth.
Enable OEM unlock in developer options, also enable ADB debugging.
Plug in your phone, run crosshatchdb.
Select option 9, this will auto download and extract adb to your c: drive.
Select option 1 to check for ADB devices, check the box on the dialog that pops up on your phone.
All set. You can download magisk directly to your phone or push it from your PC.
Reboot bootloader option 2, from here you can unlock the bootloader(formats your phone btw).
Setup your phone, enable ADB debugging again and your free to reboot bootloader and download/boot TWRP to flash magisk.(use TWRP img not zip)
Hopefully these instructions are not too confusing, it is pretty easy once you do it once, and the tool really does make the next time you do it faster.
Tested on a windows 7 virtual machine and my own personal windows 10 machine.

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
The time to unlock a Google purchased Pixel isn't the issue. The factory reset just sucks if you run stock for any time before doing it.

Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Click to expand...
Click to collapse
Good idea, should be easy to pipe logcat output to a text file.
ADB sideload can be added as well, next update will probably be when TWRP ADB is fixed, or sooner depending how long that takes.
Already thinking of ways to make the current version of this script more automated, but I like to err on the side of explicit is better than implicit.
Thanks for the ideas.

Can this install TWRP ?

Zorachus said:
Can this install TWRP ?
Click to expand...
Click to collapse
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Click to expand...
Click to collapse
This.
It is a good option of you want an easy way to just boot TWRP in 1 button, if you don't want to install a custom recovery like TWRP.

New update coming soon, decided that command line didn't work very well for this purpose...
Also working on making all of the actions smoother.

New update released, let me know if you have any issues or feature requests, still waiting for TWRP to be fully functional before adding ADB sideload options.
CMD window still wants to hang out for now, you can minimize it though if needed.

can you add a (check for update)

Maty360414 said:
can you add a (check for update)
Click to expand...
Click to collapse
Yes, that is on the list for next update.
When TWRP is more reliable I will probably add options for copying TWRP backups to your PC as well.
Still need to get rid of the cmd window and cut down on having to open browser windows or file selection dialogs, just to get it feeling less clunky.

I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!

quinejh said:
I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!
Click to expand...
Click to collapse
Glad to hear it helped out, working on some new updates to make the UI even better.
Trying to make all of the download links update automatically too, just working on some web scraping again ?
It's a nice little tool if something gets messed up, also for new users to get up and running.

New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.

boostedduece said:
New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.
Click to expand...
Click to collapse
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?

frewys said:
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?
Click to expand...
Click to collapse
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.

boostedduece said:
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.
Click to expand...
Click to collapse
Right
So it doesn't automate the process the same as for xl?

frewys said:
Right
So it doesn't automate the process the same as for xl?
Click to expand...
Click to collapse
It will still install ADB and allow you to run reboot bootloader, boot TWRP, factory reset, ADB logcat, unlock bootloader.
But the only extra part that is manual would be extracting the factory image into the c:\crosshatch_stuff\platform-tools folder.