Hi guys, I wanted to try this database system, so I'm expanding upon this thread: http://forum.xda-developers.com/showthread.php?t=2272066
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. Just press Ctrl+L then Pastebin and fill out the information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Code:
sudo apt-get install openjdk-7-jdk dpkg
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUALnightly No You Verizon! Always use the highest revision with the latest date. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful. While the video uses an old version, the procedure is mostly the same.
image
{
"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"
}
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
31July13: initial release
XDA:DevDB Information
CASUAL- NO You Verizon, a Tool/Utility for the Verizon Samsung Galaxy Note II
Contributors
AdamOutler, jrloper, loglud
Version Information
Status: Testing
Current Beta Version: No You Veriz
Beta Release Date: 2013-07-31
Created 2013-07-31
Last Updated 2013-08-02
Very nice work
MY DIRTY LIL NOTE 2
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
all the videos say to use windows 7. can it work with vista?
master0fursinz said:
all the videos say to use windows 7. can it work with vista?
Click to expand...
Click to collapse
yeah, it should work with Vista. @jrloper could tell you more if there are driver issues.
idkwhothatis123 said:
couldnt get the latest nightly to fully load. recog device connection but the do it wouldnt work because the top of the app stayed on loading... please wait.
edit: diff build shows the top, but says disconnected on the bottom. fml
Click to expand...
Click to collapse
I'm also having this problem. Any help Adam?
Edit: This is what you're looking for http://forum.xda-developers.com/showthread.php?t=2272066
Hi,
I'm currently running Windows 8.1 64 bit and my phone is the Samsung Galaxy Note II android version 4.1.2 stock, model SCH-i605, and baseband version i605vramc3. After downloaded the latest nightly build, the .jar file opened and gave the following error in the application:
There was a problem while excuting the command.
C:\Users\Zack\AppData\Local\Temp\CASUALZack-2013-12-26-17.09.35\adbexe devices
Then it repeated this same error every second or so infinitely until the application was closed. It did this whether the phone was connected, disconnected, in USB debugging mode, in download mode, etc. I have tried everything and I continually get this same error with the "Do It' button greyed out and disabled.
Next I downloaded the previous two builds, and I found that the December 13 build did not get this error and actually found my phone. However, after I clicked "Do It" and confirmed the warning, It rebooted my phone into download mode like it is supposed to. My phone then went into download mode like usual. However, the CASUAL program then said:
looking for download mode devices..........................................................
And kept on looking without ever finding my phone, and every minute or so it came up with a prompt asking why it can't find my device. I also found that my phone would not exit this download mode without doing a battery pull.
Next I retried the entire process with both builds using (a) 3 different USB cords, (b) 3 different computers running windows 8.0 and 7, and (c)every possible USB port on each computer. These options all gave the same exact results.
I have tried everything I can think of but it is not working! Has anyone encountered this problem before or do you have any proposed solutions?
Thanks so much!
Zack
Still can't figure it out.
http://pastebin.com/W3W1HwJi
I keep getting a libusb error -12 at the start and then it ends up failing.
Really need help here. Verizon was trying to force update me and I had to turn it off and go back to my old phone till I can get this done.
Thank you Adam!!
BrickeD?
Hi guys.
I am certain I followed all instructions to the letter, but I have ended up rendering my Note 2 pretty much useless. CAUSAL informed that the device would be started in android but then the next thing my phone displayed was:
"System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
Can I restore my device to the previous state?
thanks
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Spy26 said:
Tried the second time around with CASUAL R570 and got error.
http://pastebin.com/Gpss6vtZ
UPDATE: Gave up hopes (for now) of rooting SCH-i605 running KitKat. Flashed stock rom and revived the device.
Click to expand...
Click to collapse
There isn't a root method for ND7 4.4.2. for the i605. Also, the bootloader hasn't been able to be unlocked since MJ9 4.3.
mirror
Hosed my phone... infinite bootloop at sammy logo, couldn't get into recovery had to odin a stock image and start over... Had one hell of a time tracking down the casual jar file.
As of this moment the download link in this thread is bad.
the download link in THIS thread, now points to DevHost but the files are not the ~29MB jar file you expect. It is now a 3.5MB exe file that appears to be "shady as hell". All the other download decoy buttons at Dev-host take you to fake java update downloads and other seriously shady looking corners of the interweb.
Additionally goo.im is on holiday...
As such I have posted this temporary Mirror of the .jar file I had in my archives:
http://tweakedrom.com/Other_Files/Note_2.php
(The jar file MD5 appears to be the same as one the developer posted to Dev-Host.)
Outler, if you want me to take this mirror down just let me know.
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
mjmplus said:
Cannot find the download to casual sch-i605. All download links I can find lead to nowhere.
Click to expand...
Click to collapse
Well you could go to his very own YouTube video and use the links there
Related
BHP090808 PRESENTS
I545 ALL-IN-ONE TOOL ROOT + RECOVERY INSTALLER
**READ READ READ AND READ AGAIN**
DO NOT RUN IF YOU ARE ON NEW ME7 OTA UPDATE!
This tool was created to simplify the rooting and recovery installation on this device. The rooting method used is the same method already posted in this development section. I just put all the resources into a tool and provided easy to follow instructions. The root process is not a one click. You must read instructions in tool window for each step of the rooting process. It is very straightforward and easy to follow, but you must follow the instructions exactly. Once rooting is complete all other steps are one click features including recovery installation.
Make sure you have latest samsung drivers installed. I recommend downloading Samsung Kies, It will automatically download latest drivers for you. Make sure unknown sources is checked and USB Debugging is enabled or the tool will not see your phone. Also make sure you do not have any pw or pattern lock screen enabled. As soon as you start step 1 check your phone screen. You will see a prompt to authorize your computer. Select ALWAYS ALLOW. This is the cause of the majority of errors. Also the usb cable that came with your s4 is recommended. If you are having issues with odin recognizing your phone check drivers and try using a different usb port. If using a desktop I recommend using the rear usb ports. Prep step (#2) removes install-recovery.sh and KNOXAgent.apk from your phone. These have been known to cause unwanted errors.
If when rebooting from recovery you are prompted with a message advising root may have been lost would you like recovery to fix it? I have always chosen NO and had no issues.
I do not offer support on either recovery or any rom you flash after this process. Check their respective threads for any and all information. Links to both recovery threads are included as options in tool.
I've included latest CWM (credit OUDHS & Shabbypenguin) and TWRP (credit Team Win). The rooting method and kernels used were provided by sextape. The step by step root process from open1your1eyes0. The motochopper exploit was created by the legendary djrbliss. Also a big thanks to djrbliss for Loki, without which none of this would be possible. Make sure to find these fine folks and give thanks, money, beer, your first born..... whatever you see fit.
I'd also like to thank niv3d, an21281, CraziiChief and all of my other testers. I'd also like to thank my wife and kids for leaving me alone while I worked on this. Mirrors are ok, just pm me the link to list in the OP.
Hope this makes someones life easier.... Have a nice day!!!!
Instructions:
Download zip file
Unzip on desktop
Connect phone with USB debugging enabled
Click RUN_ME (inside unzipped folder)
Pick option and go!!
Have patience it takes a few for cpu to see phone after reboots and in Odin
dont disconnect phone until process is complete
If stock start with option 1
If already rooted start with option 2 then choose recovery
Download-
I545 All-In-One Tool
https://mega.co.nz/#!I1c1jTBY!GCtdvXRoeXiCRNgjXge3CA9UZ3FIBtHf-m2_kQCr3BI
Mirror-
http://db.tt/1wpdewwY
Dont forget to hit the thanks button and rate thread 5 stars:thumbup:
And if youd like to buy me a beer I wont complain :beer:
Thanks for the beer list::beer:
(Donations Received)
yamaharider
Michael Oconnell
SolemnSinner
Mills23
Eric Lee
Artiepea
JNava420
Footbaggin
Charles Uniman
Updated 5/30
oudhs cwm is now 1.0.3.5
Updated 5/31
Fixed script typos
(Thanks scrosler)
Updated 6/1
Added to prep script
Added additional instruction script
Updated 6/3
Fixed script typos
(Thanks opethfan89)
Updated 7/8
TWRP updated to 2.6.0.0
Great job! This tool simplifies the root process and makes it a breeze for those who are tempted to root and flash! Give it a shot you won't be disappointed!
{
"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"
}
I tested this utility a few hours ago and it works great! Just make sure to follow the directions and give it time to do every step, very easy!
Complete newb question here, and searching didn't turn up much.. Seeing as there is no Bootloader unlock yet, theoretically you should be able to just revert to stock and unroot and no one would know you were ever rooted/ROMd, right?
If I completely missed a post that explained this, sorry.. I searched and didn't see it.
Yep. Just Odin back to stock and you're done.
Sent from my SCH-I605 using Tapatalk 4 Beta
Just used this method to root and install recovery on my new S4 and it worked great! thanks for the tool
You sir, are awesome. So easy. Always nerve racking rooting a new phone but this is cake. Took 5 minutes. A caveman could do it! Thank you!
great tool! worked very well! thanks!
Worked like a dream, thanks a lot!
Tool Updated...
CWM is now 1.0.3.5
Thanks. Success! Ive never seen odin in action, that was cool. Thanks for the easy instructions throughout the process. Very easy.
Sent from my SCH-I545 using Tapatalk 2
Thanks,m just had to trade my phone in due to manf. defect. This'll make re-rooting a lot easier!
Download link broken. Says file is corrupt.
Sent from my Galaxy Nexus using xda premium
USB Debug
New to Galaxy S4 where can I find USB Debug in setting? thx!
kevinniven said:
New to Galaxy S4 where can I find USB Debug in setting? thx!
Click to expand...
Click to collapse
To unlock the Dev Options menu, go to Settings -> About Device and scroll down to the "Build Number." Now, tap on your "Build Number" five times, and you should see a toast notification pop up saying "Developer mode has been enabled." Back out of the About Device menu and you'll see Dev Options back where it belongs, so you can turn on USB Debugging and whatever else you want to.
(taken from http://gs4.wonderhowto.com/how-to/enable-hidden-developer-options-your-samsung-galaxy-s4-0146687/)
Elvis_Marmaduke said:
Thanks,m just had to trade my phone in due to manf. defect. This'll make re-rooting a lot easier!
Click to expand...
Click to collapse
Just curious....what was the defect?
Tar file
All seems to be going ok but not seeing TAR file in Oden?
viceversa said:
Just curious....what was the defect?
Click to expand...
Click to collapse
It was a small thing in the top left corner of the screen, I could only see with the screen off. It looked like glue or a tiny hair under the glass. I was mostly just worried it was going to get worse over time. I didn't even notice it until I was putting a screen protector on (you know how impossible it is to get rid of all that dust). Free replacement through Verizon though because it's a defect.
Hi - I bought a replacement kindle for my mom since the other has a cracked screen. All I want is for it to be a regular Kindle. But right now it has Android on it, and I know nothing about how it was made this way, or how to return it back.
About screen says:
Qualcomm MSM8974
android 4.4.4
Kernel 3.4.0-perf-gbfccc1e
Build from Dec 9 2014
HDX Nexus ROM - v4.0.5 @ggow
Lots of threads talk about root, and various Windows apps and etc. etc. but I don't know where to start, since I don't know what state this device is in.
Can anyone, (ggow?) point the way to getting this put back to normal in clear steps? Thanks so much in advance!!!
Mobial said:
Hi - I bought a replacement kindle for my mom since the other has a cracked screen. All I want is for it to be a regular Kindle. But right now it has Android on it, and I know nothing about how it was made this way, or how to return it back.
About screen says:
Qualcomm MSM8974
android 4.4.4
Kernel 3.4.0-perf-gbfccc1e
Build from Dec 9 2014
HDX Nexus ROM - v4.0.5 @ggow
Lots of threads talk about root, and various Windows apps and etc. etc. but I don't know where to start, since I don't know what state this device is in.
Can anyone, (ggow?) point the way to getting this put back to normal in clear steps? Thanks so much in advance!!!
Click to expand...
Click to collapse
When you reboot the device does it briefly display a screen that shows a crude 'robot' graphic with possible reference to Safestrap?
No, it just says "kindle fire" then switches to swirly dots that resolve to the android logo, then lock screen.
Here is a picture of the apps screen. My daughter was doing some things so I don't know what came on it vs what we added.
{
"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"
}
Thanks!
Mobial said:
No, it just says "kindle fire" then switches to swirly dots that resolve to the android logo, then lock screen.
Here is a picture of the apps screen. My daughter was doing some things so I don't know what came on it vs what we added.
Click to expand...
Click to collapse
Thanks. You can restore FireOS 4.5.5 pretty easily (below). Just make sure this is what you really want. FireOS v4 is great for folks who read Kindle books and thrive in the Amazon ecosystem. It's pretty awful for general web browsing and app selection. FireOS v5 on newer Amazon devices is better but not available for older HDX models.
- download FireOS 4.5.5 (Thor) from this thread. Only use this version; be sure to get the right one
- if you used a PC/Mac to download the image attach (tether) the HDX via USB cable and copy the file to "internal storage"
- detach and power down HDX
- restart HDX by pressing <power>+<vol-up> simultaneously; release both buttons after a few seconds; you should enter TWRP (blue/black screen)
- locate and press wipe button; use slider at bottom to perform a 'factory reset' then return to home screen (this will erase device)
- return to wipe menu, press advanced, tick the system partition (only) and then execute (this will remove custom version of Android); return to home screen
- press install button; locate previously downloaded FireOS zip file and initiate install via buttons at bottom
- reboot device; FireOS should start after 2-3 min
While the above procedure is relatively straightforward it is not without risk. An error could leave the device in an unrecoverable state. If you're unfamiliar with TWRP might want to seek out a friend who has experience in this area. Post back with any immediate questions/concerns.
Thanks so far!
I got the file, and transferred it via my mac. (twrp-thor-13.4.5.5_user_455001320)
When trying to do the final install I had to uncheck the Zip file signature verification, but then I get
"symlink: some symlinks failed".
I'm re-downloading the file you linked me to, which is unlikely to work, but it's something...
Note: I can uncompress the .zip I downloaded on my mac and view the directory structure, so the file itself appears OK.
What can I try next? Thanks for your help!
Mobial said:
Thanks so far!
I got the file, and transferred it via my mac. (twrp-thor-13.4.5.5_user_455001320)
When trying to do the final install I had to uncheck the Zip file signature verification, but then I get
"symlink: some symlinks failed".
I'm re-downloading the file you linked me to, which is unlikely to work, but it's something...
Note: I can uncompress the .zip I downloaded on my mac and view the directory structure, so the file itself appears OK.
What can I try next? Thanks for your help!
Click to expand...
Click to collapse
Take a look at the last few posts in the previously linked thread. A couple other users were having similar problems and offered their solutions. What version of TWRP is currently installed (guessing 2.8.x.x which is fine)?
OK, update –*obviously the redown of that file didn't matter - it was identical.
I obtained "update-kindle-13.4.5.5_user_455004220.bin" from Amazon –
so this time it says "This package is for "thor" products; this is a "cm_thor" - hrmmmm.
Davey126 said:
Take a look at the last few posts in the previously linked thread. A couple other users were having similar problems and offered their solutions. What version of TWRP is currently installed (guessing 2.8.x.x which is fine)?
Click to expand...
Click to collapse
It's v2.8.6.0
Mobial said:
OK, update –*obviously the redown of that file didn't matter - it was identical.
I obtained "update-kindle-13.4.5.5_user_455004220.bin" from Amazon –
so this time it says "This package is for "thor" products; this is a "cm_thor" - hrmmmm.
Click to expand...
Click to collapse
So I will advise (once) not to wander off script. Reread the first bullet in my original post about where to source files. Had you tried the download from Amazon the device would have bricked.
SUCCESS!!!
OK – I got it to work!
Now, FYI, it could have been 1 or 2 things...
1) I saw a post in that thread "Try changing the mount-state for "system" in TWRP, that did the trick for me." --- so I found a place in TWRP to I guess uncheck "system" in the partitions mounted.
2) I also in that process unplugged the Kindle from my computer (it had previously been connected so I could try loading other .zips there" - I think it was some prompting on TWRP that made be do this (can't recall, something like disconnect or something)
Then went back to the install step and chose the ORIGINAL file you provided, and this time there were a few messages about partitions and mounting, etc. in the log, and it installed. After reboot –*it's back to stock.
THANKS SO MUCH!!! Really appreciate it!
Davey126 said:
Take a look at the last few posts in the previously linked thread. A couple other users were having similar problems and offered their solutions. What version of TWRP is currently installed (guessing 2.8.x.x which is fine)?
Click to expand...
Click to collapse
Mobial said:
OK – I got it to work!
Now, FYI, it could have been 1 or 2 things...
1) I saw a post in that thread "Try changing the mount-state for "system" in TWRP, that did the trick for me." --- so I found a place in TWRP to I guess uncheck "system" in the partitions mounted.
2) I also in that process unplugged the Kindle from my computer (it had previously been connected so I could try loading other .zips there" - I think it was some prompting on TWRP that made be do this (can't recall, something like disconnect or something)
Then went back to the install step and chose the ORIGINAL file you provided, and this time there were a few messages about partitions and mounting, etc. in the log, and it installed. After reboot –*it's back to stock.
THANKS SO MUCH!!! Really appreciate it!
Click to expand...
Click to collapse
Great! Glad you were able to get it sorted. A few minor footnotes that won't impact daily usage:
- the device is not totally 'stock' as recovery and possibly other components remain from original owner
- stock/Amazon recovery can not be easily restored (nor would you want to)
- if desired FireOS can be rooted from TWRP (no need for other approaches)
- bootloader can also be unlocked (wider selection of custom ROMs)
- FireOS will not self-update and will remain at 4.5.5 until another compatible
ROM is flashed
- FireOS 4.5.5.x is likely the terminal version for this device; Amazon has no plans to bring FireOS v5 to 3rd gen HDXs
Not Going back to Wipe Screen
Everything goes good till Factory Reset and when factory reset done it goes back to device setup its not going back to wipe menu.nexus rom v4.0.5 @ggow is currently installed but i am trying to move to official Amazon Rom
This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"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"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507
{
"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"
}
A Mobile Version of the Ubuntu Operating System
Ubuntu Touch is made and maintained by the UBports Community. A group of volunteers and passionate people across the world. With Ubuntu Touch we offer a truly unique mobile experience - an alternative to the current most popular operating systems on the market. We believe that everyone is free to use, study, share and improve all software created by the foundation without restrictions. Whenever possible, everything is distributed under free and open source licenses endorsed by the Free Software Foundation, the Open Source Initiative.
For more information check out the UBports website.
Known issues:
Recording video doesn't work
Changing volume in-call doesn't work
Contribute:
As not everything is working fully yet helping hands are welcome!
Follow the project management issue over at the Halium GitHub page:
https://github.com/Halium/projectmanagement/issues/98
Instructions (tested on Ubuntu 18.04):
First make sure to wipe /system & /data from within TWRP. The partitions must be ext4.
Make sure to upgrade your device to the latest stock Android 8.0 before continuing: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Download and install the UBports installer: https://github.com/ubports/ubports-installer/releases
OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.
Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using:
Code:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
Run the UBports installer and follow the on-screen instructions
Reserved for future use
wtf bro i never expected to see ubuntu touch on any device again great news and good work! keep it up!
Too bad my device broke......gotta fix fast lol
I've updated download links and the instructions to enable call functionality. Testers welcome!
Ready for tests! Just need to install Ubuntu with current manual
Have I need to flash stock rom with android 7 or just flash binaries on stock android 8?
New tests to be done, we've recently gotten video decoding to work and I enabled basic camera support.
OP has been updated with the link to the newest images.
Feel free to post issues here if you are not feeling well with GitHub.
Regarding stock ROM or not:
Any system image should work, you can even wipe system as it's not used.
As long as the ODM partition is flashed everything should be good.
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
samijam said:
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
Click to expand...
Click to collapse
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
beidl said:
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Click to expand...
Click to collapse
Sorry for the late reply. I got it to work now. My problem was using an outdated system.img and boot.img. (oops, sorry, my bad!) I had downloaded the newer versions, but had them in the wrong directory. Once I deleted the old and installed the correct versions, I was able to get audio in calls and had the basic camera functionality.
---------- Post added at 16:43 ---------- Previous post was at 16:37 ----------
matiz098 said:
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
Click to expand...
Click to collapse
boot into fastboot and flash the oem:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
then boot into twrp recovery and wipe /system and /data
while in twrp, run the halium-install.sh script (because the computer needs to connect to phone in adb mode, which twrp provides)
following from there, as you see in the first post, you will run "adb reboot bootloader" (but I think I did have to do it manually) which should put you back into fastboot mode where you'll "fastboot flash boot halium-boot.img"
then you should be able to reboot into ubuntu. The first boot takes a little longer.
Are there any screenshots available?
Fajormein said:
Are there any screenshots available?
Click to expand...
Click to collapse
No but you can find some videos on YouTube, just search for "Ubuntu Touch 2019".
The videos might feature different phones but it's the same on the Xperia X.
Is there any way to install it using a windows pc?
Fardin Rehman said:
Is there any way to install it using a windows pc?
Click to expand...
Click to collapse
Not currently.
please make a porting for kugo (x compact) sir
rizky_zulfikar said:
please make a porting for kugo (x compact) sir
Click to expand...
Click to collapse
Someone else is working on that already, but this port is only for the Xperia X (F5121).
In other news:
Installation instructions have been updated, the Xperia X port is now available from the UBports community channel!
Can you make port for XA 2 (H3113)
As I get the question very often: To support the F5122 variant of the Xperia X (or other devices in general) for Ubuntu Touch I need donations to buy the device.
Use the "Donate To Me" button on XDA or head over to https://fredl.me/donate/ for info on how to do so.
In other news: The Xperia X F5121 has gained support for the official UBports installer. You can now flash the device using a fancy GUI.
I hit 2 problems. For some reason neither Emma nor flashtool wants to flash stock rom correctly. Tried to flash ubuntu through stock 8.0 custom rom, phone reboots and black screen. Also there is was an error with something that the file couldn't be sent to the phone
Click to expand...
Click to collapse
Ok, so I did install the stock rom through EMMA fine. I did enable the usb debugging, installed twrp, wiped system & data, made sure they are EXT4. Rebooted to fastboot, installed SW binaries. Opened UBports Installer & proceeded with instructions. I got this error
Code:
Error: systemimage: Error: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"C:\\Users\\domin\\AppData\\Local\\Temp\\1Uo4H80AYPnCivmpnC8M9LLWxLb\\resources\\app.asar.unpacked\\platform-tools\\win\\adb -P 5037 shell mount -a"},"stdout":"","stderr":"mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument"}
Any solutions, did I miss something? I gonna retry without the twrp step, as I am pretty sure the partition format will be EXT4
Guide has been reworked to be more clear and based on comments.
[Part One]
Backup Data
Update phone to latest version
[Part Two]
Download the Firmware for the Zenfone 9 https://www.asus.com/mobile/phones/zenfone/zenfone-9/helpdesk_download/
Download Payload GUI. https://forum.xda-developers.com/attachments/payload-dumper-gui-v2-3-zip.5758127/ (Hermann2306 credit for mentioning)
Extract the Payload Dumper GUI zip file, as well as the UL-ASUS Firmware zip file
Run the Payload Dumper GUI program in the unzipped folder. A file explorer window will pop up; open the unzipped UL-ASUS Firmware folder and select the payload.bin file. Another file explorer window will pop up; select the UL-ASUS Firmware folder if not already selected, then click select folder in the bottom right.
Click Dump on the Payload Dumper GUI Application. The files will be output to the UL-ASUS Firmware folder.
[Part Three]
Download Magisk and install onto phone via APK. https://magiskmanager.com/downloading-magisk-manager/
Plug phone into computer and allow file transfer.
Within the UL-ASUS Firmware folder there will be a boot.img file. Move this file onto the phone.
Open the Magisk application and follow image below, select the boot.img to patch
{
"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"
}
A file will be output with magisk. Move this file back onto the PC, and rename to boot.img
[Part Four]
Unlock Zenfone 9 Bootloader. Asus provides a bootloader unlock tool on their website. Below is the link directly to the apk. https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Install the drivers listed below for the phones recovery mode https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip (Asus Driver Xanker commented. Thank you again)
[Part Five]
Download Minimal ADB and extract files https://androidfilehost.com/?fid=962187416754459552
Move Boot.img file into Minimal ADB extracted folder.
Put Zenfone into recovery mode and connect to PC. Recovery mode can be achieved by turning off the phone and then powering on whilst holding the volume up button. Release when the ASUS logo pops on screen.
Run cmd-here.exe in the Minimal ADB folder; a command window will open
As a test run the command listed below and it should output a device fastboot devices
If that test succeeded run the final command to flash, fastboot flash boot boot.img
The command prompt command didn't run. Said it was not recognized. Is there a specific place the .exe need to be in the directory?
NVM...got it.
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
bighit101 said:
@BreadNoose Thanks for the write-up!!!
I just got the phone 2 days ago and have been trying to follow your steps but without success. I keep having issues with fastboot (I've probably spent 6+ hours on it; I also have a 9-5 job haha). The following are things I've tried:
*Btw, OEM unlock is not showing in Developers options. Download unlock app and I think my OEM is unlocked but in recovery it says "Yes" next to Bootloader thing.
-ADB works fine.
-Download Platform from Google.
-Tried ADB minimal from xda also.
-I tried three laptops, two windows 11 and the other windows 10. None of them recognize fastboot.
- When I go to device manager I see Asus phone listed with that yellow triangle sign and when I try to update the driver it either says drivers up to date or if I manually try to update it says some other error.
- Try different cables.
- I even disabled the driver signature in the restart menu but no success.
-I tried using Asus 8 drivers thinking that would help but nothing.
I wonder if it's just the Asus 9 driver that's the issue? What am I missing???
Any idea?
Thanks for any help you can provide.
Click to expand...
Click to collapse
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
The image version that I just downloaded seems to be at a higher version (WW-32.2030.2030.26 as opposed to WW-32.2004.2004.84 on my phone) and the phone doesn't have that version available (I haven't unlocked the bootloader yet). Should I update locally or download the earlier version of the image instead?
If your phone has the 2004 version installed extract the boot.img from the downloaded 2004 Payload.bin. Or you can update your phone and use the 2030 boot.img.
For me it works with the 2030 version. Root installed, everything ok (AdAway, Postbank (BankingApp)).
If you want to pass SafetyNet just install the magisk module from https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.3.1 and reboot.
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Hermann2306 said:
I dont use wallet, but if installed i can run it and start the setup, no errors.
Maybe try it with the use of denylist.
How to Hide Root from Apps via Magisk DenyList [Android 13]
In this comprehensive guide, we will show you the steps to hide root from apps and games using Magisk Denylist on Android 12.
www.droidwin.com
Click to expand...
Click to collapse
Doesn't work, the guide asks for denying google system apps which doesn't work because they are always off deny list (this is intended behaviour)
For the record, every other payment apps I am using, even the ones that check for safetynet are working. YASNAC returns a both pass basic.
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Hermann2306 said:
Then i am sorry (Im too new to the whole android stuff, still learning)
Just for interest, can you start and configure wallet (error comes first if you want to pay)?
Click to expand...
Click to collapse
Wallet is configurable, it's just that when you save your card details and it starts contacting the bank it would jump to an error saying that the system is modified.
Maybe try this? (I think you have already read/tried it)
[Magisk] Google wallet (pay) with magisk
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do: - Update Magisk to 25.2, Update magisk app to 25.2 as well - Rename Magisk app if you havent already - [ OPTIONAL ]...
forum.xda-developers.com
Does someone rooted a 16GB ram Zenfone 9? My software is 32.2004.2004.74.
Can not find this software at Asus website.
I have rooted the 16gb version (32.2030.2030.26).
Why dont make an update before root?
xanker said:
Had the same Problem, you have to use this driver:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/ASUS_Android_USB_drivers_for_Windows_20160331.zip
Click to expand...
Click to collapse
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
williamcll said:
OK, rooted with no issues, I needed to install the asus drivers and had to reset a second time because the USB stopped working. However, I can't get Google wallet to work despite all other banking apps working as well as passing safetynet.
Click to expand...
Click to collapse
Try this: https://github.com/kdrag0n/safetynet-fix
Veiranx said:
Try this: https://github.com/kdrag0n/safetynet-fix
Click to expand...
Click to collapse
Safetynet fix is running, it's just that it's not enough, still going through the prop fix.
bighit101 said:
OMG!!! Bro you are the MAN! (Sorry im so excited lol).
You literally saved me god knowns how many hours. It was the driver that were the issue. But whats weird is I went to asus site to download drivers before leaving a comment.
I'd really like to buy you a coffee (or adult beverage). Let me know your paypal/venmo.
Thanks again!
Click to expand...
Click to collapse
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
xanker said:
Glad I could help. I already drink enough coffee but you're welcome to donate to a children's charity.
Click to expand...
Click to collapse
Yeah coffee is life!
You're too nice. Will donate in you're name.
Thanks man!!!