Related
This is for all users of the HTC J Butterfly (HTL21) that was released in Japan.
For any of the below procedures, read the instructions several times before attempting. Also, please copy/paste any commands in the code boxes so you avoid making typing mistakes.
You can find me on IRC, irc.andirc.net #HTCJButterfly - but it's not a dedicated channel and I'm usually only on in the evenings, JST.
To do this, I assume you have the proper tools set up, are familiar with doing ADB commands, are aware that I (or the other posters) are NOT liable for any damage that you might do to your phone. Proceed at your own risk.
Unlock: Yes (日本語で from fnoji111 / simplified English explanation from samusx)
Here, we will get temproot, change the CID, then unlock the phone through the htcdev website.
Preparation
goroh_kun's root tools
You are able to issue ADB/Fastboot commands to your phone
USB Debugging is ON (Settings -> Developer Options -> check USB Debugging)
Further note, you may want to back up everything on your external SD card, or just use a spare external SD card to do this process.
Temproot
From goroh_kun's root tools, you'll find two files inside: diaggetroot.apk and getroot. Put these two files in a folder where you can run ADB commands.
In a command prompt, run
Code:
adb install diaggetroot.apk
Next, run
Code:
adb push getroot /data/local/tmp/getroot
adb shell chmod 777 /data/local/tmp/getroot
On your phone, run the diaggetroot application, the name might be BreakSuidDiag, wait for the Hello World! message to appear
In the command prompt, run
Code:
adb shell
/dev/sh
You should now see # in the command prompt. If you don't, toggle the Wi-Fi ON/Off and try the /dev/sh command again. If you have #, great. Next!
Modify CID
(Thank you, beaups, for the easier method to change the CID!)
You should have # in the command prompt
run
Code:
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
back into the command prompt, with #, run
Code:
reboot bootloader
With your phone now in the bootloader, run
Code:
fastboot oem readcid
The result should show 11111111!
Unlock
It's probably a good idea to backup any data because this will essentially factory reset your phone.
If you have 11111111, go to htcdev.com
Choose to unlock the bootloader, from the devices pull-down menu, select ALL OTHER SUPPORTED MODELS
Follow all of the directions until you are unlocked
Keep your unlock token somewhere safe!
Custom Recovery and Root: YES
Phone unlocked? Good. Thanks to drewx2, we now have a working custom recovery, and we can get root as well. We'll do this in one go. We will flash the custom recovery, change the theme so that the recovery fits on the screen, then flash SuperSU. Oh, let's flash Busybox as well.
Preparation
drewx2's twrp-htc-dlxj.img
SU_Busybox_Package.zip (optional, if you don't want to install a custom ROM but need root)
Flash TWRP and change the theme
In the command prompt
Code:
adb reboot bootloader
When the phone enters bootloader mode, in the command prompt
Code:
fastboot flash recovery twrp-htc-dlxj.img
Check to make sure that the recovery works. If it does, great!
Follow this guide to change the theme to fit the screen
From here, you can flash a ROM through the custom recovery, like AUrora, and it will already be rooted with SuperSU included. If you don't want to install a custom ROM, you can follow the below instructions to get root/SuperSU on your stock system.
Flash SuperSU and Busybox from TWRP (optional)
Put the SU_Busybox_Package.zip file on your sdcard
From TWRP, tap Install
Find the file and select it
Swipe the white arrow from left to right to install
Tap Reboot System and check to see if SuperSU and Busybox work
Problems/Issues
au Market won't work if Superuser is installed. If you uninstall Superuser, au Market will work, then you can install Superuser again after you finish using au Market. Until this is resolved, this is the way to use both applications together. If you use SuperSU instead of Superuser, then au Market should work.
Custom ROMs: Yes
J Butterfly Stock Rooted ROM 1.15.970.1 (odex)
J Butterfly Stock Rooted ROM 1.15.970.1 (deodex) - Camera will crash if you try and record a video, seeing what can be done to resolve this. Please use the odex'd rom instead if you need to video record.
AUrora v1.0.2 - See Post #2
S-OFF: YES
Please go to http://unlimited.io/ - The DirtyRacun S-OFF method has been released for this phone. You can find this method under the S-OFF Exploits menu.
(Please note that support for S-OFF will not be available on this thread, please ask the developers at the unlimited.io website if you have any troubles or issues with the S-OFF method)
SIM Unlock: Yes
There is a guide written by fnoji111. Because I have not tested this myself, I cannot provide any assistance if you find yourself in trouble. DO THIS PROCEDURE AT YOUR OWN RISK.
SIM Free guide
Custom Kernels: N/A
RUU: N/A
Credits:
goroh_kun, for his root tools
fnoji111, for providing the unlock process
samusx, writing up an explanation of the unlock process
jcase, Dr_Drache, dsb, for their time and advice on random things
beaups, his time, alternative methods, and simpler CID method
drewx2, for providing a working custom recovery (TWRP)
dsb, for helping me get my custom rom working
lyapota for the camera mod
nitsuj17, stat bar mods
UKB (nitsuj17) and CODIS (chingy51o, newtoroot) ROM creators
androidfilehost
zeppelinrox, SuperCharger V6 tweaks
Click to expand...
Click to collapse
AUrora v1.0.2
AUrora ROM v1.0.2
Features
Based on stock DLXJ 1.15.970.1
Android 4.1.1 / Sense 4+
Aroma Installer
SuperCharger V6 tweaks
Deodex
Debloat
Rooted
SuperSU
Busybox
Add 3rd Party Apps
lyapota's camera (shhhhhh!)
Status Bar mods (Clock/Battery)
Download: AUrora v.1.0.2 (English) | AUrora v.1.0.2 (日本語)
Installation
Your device should be unlocked, rooted, with a custom recovery. (see post #1)
Make sure you've made a nandroid backup!
Put AUrora ROM on your internal SD card
In recovery, in this case TWRP, Wipe cache, dalvik cache, factory reset, and system.
Install AUrora ROM
Reboot system
Issues
Although Busybox is installed, it may not work properly. In that case, you can flash this Busybox from recovery. No wipes needed.
Changelog
Code:
v1.0.2
*re-cooked ROM, au Market should work now
*Updated some/system/apps, 2/4/2013
*Updated some /data/apps, 2/4/2013
*V6 SuperCharger [U9RC11] tweaks (100% SuperCharger, Die Hard Launcher, sdcard/3g, Kernel/VM, Zipalign apk/permissions fix on boot)
*Removed a few more HTC/au apps, installable in Aroma
*Added 5 DNA HEX wallpapers (Pink, BW, Blue, Yellow, Orange)
*Created Purple and Red battery percentage mods
*Removed centered clock mods
*Modified Rosie, Landscape and 5x6/8x4 App drawer added (thanks nitsuj17 and dsb9938 for guidance)
*Added 5 DNA wallpapers (Blue/Red Droid DNA Eye, Green/Purple/Red DNA HEX)
*Changed default wallpaper
v.1.0.1
*Edited aroma-config and updater-script to fix the camera mod page not
showing up if Default is chosen in au installation screen in Aroma (thanks samusx)
v1.0.0
*Fixed Video recording (thanks lyapota)
*Added UKB Status Bar Battery/Clock mods to Aroma (thanks nitsuj17!)
*Added lyapota camera mod, choosable in aroma
*Debloat and desense (au Apps/Widgets, HTC Apps/Widgets, Wallpapers,
Lockscreens, etc) with option to install in Aroma
*Added a temporary splash screen
*Added extra 3rd Party apps to install in aroma: Titanium Backup,
ES File Browser, LINE
*Added Aroma Installer
Credits:
goroh_kun, for his root tools
fnoji111, for providing the unlock process, Japanese aroma installer
samusx, writing up an explanation of the unlock process
jcase, Dr_Drache, dsb, for their time and advice on random things
beaups, his time, alternative methods, and simpler CID method
drewx2, for providing a working custom recovery (TWRP)
dsb, for helping me get my custom rom working
lyapota for the camera mod
nitsuj17, stat bar mods
UKB (nitsuj17) and CODIS (chingy51o, newtoroot) ROM creators
androidfilehost
zeppelinrox, SuperCharger V6 tweaks
Click to expand...
Click to collapse
Reserved, just in case.
looking forward...
i am looking forward for some updates on this post...
keep us posted!
thanks.
g.b.a. said:
i am looking forward for some updates on this post...
keep us posted!
thanks.
Click to expand...
Click to collapse
Hopefully there will be lots of good news to share in the new year. If you come across anything, let me know!
I think only j butterfly can not be unlocked as per your info. But, HTC Butterfly which have been released in Singapore & China can be unlocked since they are not locked to any carrier (not tested yet but it is based on other HTC devices experience).
kdahri said:
I think only j butterfly can not be unlocked as per your info. But, HTC Butterfly which have been released in Singapore & China can be unlocked since they are not locked to any carrier (not tested yet but it is based on other HTC devices experience).
Click to expand...
Click to collapse
For the time being, yes, the J Butterfly cannot be unlocked. I'm jealous of the Singapore and China variants being unlocked...unfortunately my carrier here in Japan does not like to unlock phones, based on my experience.
Looks like there is some good news on the horizon.
Seems someone found something.
Take a look.
http://htcsoku.info/au-deluxe-unlock/
au by KDDIから発売されているHTC J butterflyのHTCDevでの開発者アンロックはキャリアの意向により出来ませんが、以前からSnapdragon S4機でなぜか可能になっているCIDブロックの改変でのSuperCID化（本来S-OFFでないと出来ない）により姉妹機で同様にキャリア（Verizon）の意向によって開発者アンロックの提供がされていないDROID DNAのアンロックは可能となっていました。
CIDブロックを改変するためには管理者権限が必要となっており、DROID DNAはcom.htc.usageのexploitにより管理者権限を得た後CIDブロック（mmcblk0p5）を改変し、本体のCIDをSuperCIDに行った後開発者アンロックを実現していました。
しかしHTC J butterflyの出荷時点ではそのcom.htc.usageのexploitは利用できず、管理者権限が得られないためにブロックの記述変更ができないでいましたが、Androidセキュリティ等で著名な@goroh_kunさんの協力によりHTC J butterflyの管理者権限を得る事が出来、CIDブロックの改変を行う事が出来ました！
これでHTC J butterflyのカスタムが広がればいいですね！
方法やブロックの改変方法等は後ほどHTC速報Devで記述予定です。（2012/12/30/2:31時点では記載してません、少々お待ち下さい・・・）
HTC速報Dev – HTC J butterfly 機種個別ページ
http://htcsoku.info/htcsokudev/2012device/deluxe_j/
samusx said:
Looks like there is some good news on the horizon.
Seems someone found something.
Take a look.
http://htcsoku.info/au-deluxe-unlock/
au by KDDIから発売されているHTC J butterflyのHTCDevでの開発者アンロックはキャリアの意向により出来ませんが、以前からSnapdragon S4機でなぜか可能になっているCIDブロックの改変でのSuperCID化（本来S-OFFでないと出来ない）により姉妹機で同様にキャリア（Verizon）の意向によって開発者アンロックの提供がされていないDROID DNAのアンロックは可能となっていました。
CIDブロックを改変するためには管理者権限が必要となっており、DROID DNAはcom.htc.usageのexploitにより管理者権限を得た後CIDブロック（mmcblk0p5）を改変し、本体のCIDをSuperCIDに行った後開発者アンロックを実現していました。
しかしHTC J butterflyの出荷時点ではそのcom.htc.usageのexploitは利用できず、管理者権限が得られないためにブロックの記述変更ができないでいましたが、Androidセキュリティ等で著名な@goroh_kunさんの協力によりHTC J butterflyの管理者権限を得る事が出来、CIDブロックの改変を行う事が出来ました！
これでHTC J butterflyのカスタムが広がればいいですね！
方法やブロックの改変方法等は後ほどHTC速報Devで記述予定です。（2012/12/30/2:31時点では記載してません、少々お待ち下さい・・・）
HTC速報Dev – HTC J butterfly 機種個別ページ
http://htcsoku.info/htcsokudev/2012device/deluxe_j/
Click to expand...
Click to collapse
Yep! I'm fiddling with it right now, but the exact instructions haven't been released just yet, so I haven't been able to unlock...yet. Thanks!
I know this is JAPAN BUTTERFLY but in Taiwan Butterfly Version can be unlocked through HTCDEV and after that rooted using the same method as HTC ONE X.
I tried this method and my phone is unlocked. After the new year, I'll post directions in English.
Sent from my Nexus 7 using xda premium
my J butterfly loses signal after trying the rooting method above. anyone has the stock img of system and radio?
hope someone has pulled them using dd command when they got temproot; I forgot to do it
Sent from my HTC One X using xda app-developers app
tiltyu said:
my J butterfly loses signal after trying the rooting method above. anyone has the stock img of system and radio?
hope someone has pulled them using dd command when they got temproot; I forgot to do it
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Seems to be a coincidence, it seems that the network went down at the same time. It's back up now though. Unlocked and ready to go!
great job!!!
good for you...
and this is a wonderful New Year information...
hope you can share the procedure in English including the necessary processes (backup, data save, etc.)
thanks in advance!
Happy New Year!
The prep for unlocking the phone is simple.
First you need to have the Android SDK installed and ready to go. If you don't know how watch this video and follow the guide.
http://www.youtube.com/watch?v=glGdw2HAumg
This is where to get the android sdk and the written guide.
http://droidmodderx.com/galaxynexus/how-to-set-up-the-sdk-for-galaxy-nexus
Before you start in your Android phone settings click about then click the Phone identity tab. Make a note of your IMEI and MEID number.
The get these two files and put them in the android-sdk-windows/platform-tools folder.
diaggetroot.apk
getroot
These two files can be downloaded here.
https://docs.google.com/file/d/0B8LDObFOpzZqQzducmxjRExXNnM/edit?pli=1
You will a HEX file editor. Just google search for Free HEX editor and you will be able to find one.
This guide was written for Windows users. Sorry I don't use MAC.
STEP 1: Get administration privileges
With the diaggetroot.apk and getroot files put in the android SDK platform-tools folder right click on an empty space in the browser window and open a command prompt window (cmd)
Copy and paste this into the the cmd window and push 'enter'.
adb install diaggetroot.apk
It should push the file to the android system folder.
Then copy and paste these lines and push 'enter' after each.
adb push getroot /data/local/tmp/getroot
adb shell chmod 777 /data/local/tmp/getroot
Now on your android phone itself open your app drawer and open the app we just pushed to the system. It should be called BreakSuidiag or something like that. It will have a generic android icon.
When you open it, you should see a white screen and it will say "hello world".
Back on your PC in the same cmd window as before paste these lines and push 'enter' after each.
adb shell
/dev/sh
You should now see the '#' mark in the cmd window. Thats good.
(If it didn't work, turn your wifi on then off. Then try the two above lines again.)
Now make sure you have an SD card in your J Butterfly. This process will erase your SD card so make sure you have your data backed up.
In the same cmd window copy and paste this line.
dd if=/dev/block/mmcblk0p5 of=/storage/ext_sd/mmcblk0p5ORIG
You should see some writing that says the it made a file or something along those lines.
This will copy a file to your SD card called mmcblk0p5ORIG.
Now in your android options window unmount the SD card. Then remove the card and plug it into your PC and open the mmcblk0p5ORIG file with a HEX editor.
You will see a bunch of numbers that look like this.
Make sure the numbers underlined in orange(IMEI) and blue(MEID) match the numbers that you got from your Phone identity info.
There won't be XXXXXXX in your version, those are added here to protect this users personal phone identity numbers. In your file please do not add X's. Leave the numbers as they are but just make sure they match the numbers you made a note of before.
You only have to make a small edit to this file. The text that reads "KDDI_801" must be set to "11111111" That is 8, 1's that perfectly replace the "KDDI_801". When you are done it will look like this.
Now save that edited file back to the SD card named 'mmcblk0p5MOD' and they you can eject your SD card from your PC and put it back in your J Butterfly.
Now we will write this file to the phones data. Copy and paste these into the cmd window and push 'enter' after each.
dd if=/storage/ext_sd/mmcblk0p5MOD of=/dev/block/mmcblk0p5
reboot bootloader
Your phone should reboot.
After it does copy and paste this and push 'enter'.
fastboot oem readcid
You should see a screen that shows you "11111111" meaning that your new CID number is set.
Now you can follow the HTC dev unlock steps from the link at the top of this post.
Here is the like to the HTC dev unlock page.
http://www.htcdev.com/bootloader/
I hope everyone is able to follow my guide. Good luck.
Good job, samusx.
Sent from my Nexus 7 using xda premium
SharpIS03 said:
Good job, samusx.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the support man. It's the least I could do. If there are any areas that I wasn't clear on, or need improving let me know.
samusx said:
Thanks for the support man. It's the least I could do. If there are any areas that I wasn't clear on, or need improving let me know.
Click to expand...
Click to collapse
Sure thing. I'll take a closer look sometime later. I'll probably update the original post with this information as well.
Sent from my Nexus 7 using xda premium
Sounds like a good plan, add it to the OP.
I found this Chinese forum today. I wonder if it has any useful info.
I can't really understand what they are talking about even using Google Translate.
But maybe someone has some use for this page.
http://www.htcbbs.net/forum-182-1.html
All right, I've updated the OP with the unlock procedure. Credit goes to samusx for writing up the procedure with some explanations. My procedure doesn't really go into explanations. If you've found any errors, let me know.
This thread shall strive to be an all-in-one thread for the phone O+ 8.31z. And to be noob friendly as well. As of now, I have only very limited knowledge so I'll be adding stuff as I go.
Phone Specs:
CPU: MT6572 1GHz Dual-Core
Architecture: ARM Cortex-A7
Clock Speed: 598 MHz - 1.00 GHz-----
GPU Vendor: ARM
GPU Renderer: Mali-400 MP
UBIFS File system
Android: 4.2.2
Kernel Architecture: armv7I
Default Governor: Hotplug
Screen Res: 320x480
Density: 160dpi
RAM: 219MB
Internal Storage: 0.16GB
Sensors: Proximity, Light, 3-axis.
Click to expand...
Click to collapse
For drivers, connect your phone to windows PC, download PDANET (search for it on google) and let it install drivers for your phone.
Preface: TOOLS and THREADS TO BE USED
1. MTK Droid Root and Tools by xda senior member rua1. Press thanks in his thread! Compatible with Windows and Linux(with wine).
2. SP Flash Tool Credits to Khonshu of china.phonearena. I downloaded v3.1344. Here's an xda thread on what you can do with it: Click Me! Troubleshooting SP flash tools: .Click here!
3. Pdanet for Windows drivers
Chapter 1.0.0: HOW TO ENABLE PHONE MODES
Steps:
1.1.0 For MTP mode
1.2.0 For ADB mode
1. Go to Settings>About Phone
2. Click Build number about 6 times, quickly. Developer Options should now appear.
3. Go back to settings then click Developer Options. Here you find so many things you thought didnt exist
4. For now, we only check USB debugging. When a pop-up appears, just click "ok". Done!
1.3.0How to enter recovery mode: (Credits to phcorner.com O+8.52 thread)
Method 1:
1. Remove battery and reinsert.
2. Press Volume Up and power key simultaneously.
3. A blank screen with an android lying down and a red exclamation triangle should appear now.
4. Press Power button once, and the menu will appear.
5. To navigate, Power: Show/Hide options. Vol UP: Confirm. Vol Down: Scroll.
6. When done, reboot system to exit.
Method 2: When you're on a PC,
1. Connect Phone in USB debugging mode.
2. Open cmd (or terminal then change directory to your adb folder) and
Code:
adb reboot recovery
1.4.0 For Phone test mode
1. Press Volume Down and Power simultaneously.
2. Choose among the options.
3. When done, remove battery to exit.
(It seems like reinserting the battery and doing VolDown+Home combo does not do anything else)
1.5.0 For fastboot (aka bootloader) mode
Requirements: Since you want to use fastboot, then you must be on an adb configured computer
1. Open cmd (or terminal then change directory to your adb folder)
2.
Code:
adb reboot bootloader
3. Wait for the phone. Done!
Chapter 2.0.0: ROOTING
Why root?
There are many methods to rooting. I will list what I know might work. I'm 99.9% sure the first one works (given you are not stuck in a bootloop.)
2.1.0 Shuame ROOT GeniusDownloadInfo: This is a one-click PC application. I have used this in Windows 7 32-bit and in lubuntu 13.10 and it works. If your phone is not an MT6572 I'd still recommend that you try this as it can root almost anything! It installs Kinguser as the superuser app.
2.1.1 Requirements for Windows PC: A Windows PC, a USB cable, your phone, and a fully downloaded shuame root genius. No drivers needed as shuame root genius already installs them for you.
2.1.2 Requirements For Linux PC users: A linux PC, a USB cable, your phone, a fully downloaded shuame root genius, WINE, and adb (I might be wrong here, but get this: Since drivers are not really used, we need our phone to be given adb permissions by linux, or else shuame will not be able to recognize your phone. So you will probably need to have adb installed first, just to be sure.)
For info on how to do that, check here: Click Me!
Also, shuame root genius does not display well under wine in my case, but the buttons were clickable anyway so it still works. From here, it's pretty much the same procedures.
2.1.3 Steps:
I made a visual guide here:
And in text, here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open Shuame Root Genius. It will connect to your phone automatically and install drivers for about 3-5 minutes. (No more driver installation on linux PCs)
6. Click "Root it". You should now see your device as rooted. And if you click back, you can unroot. Done!
2.2.0ErootDownload/help threadInfo: Another tool by Chinese developers. I tried it on my lubuntu 13.10 WINE and it worked flawlessly! I'm pretty sure it'll work on a Windows PC as well. It installs superuser by clockworkmod.
2.2.1 Requirements: See 2.1.1 and 2.1.2.
2.2.2 Steps:
Visual guide
Textual guide here:
1. Connect your phone to PC using the USB cable and go to MTP mode. See Chapter 1.1.0 for help
4. Enable USB debugging. See Chapter 1.2.0 for help.
5. Open eroot. It will connect to your phone automatically.
6. Click the root button. It's the only button anyway. When you have rooted successfully, you can click the 解除 button to unroot if you wish. Done!
2.3.0 MTK Droid root and tools
Connect Phone in ADB and MTP mode.Download/Help thread can be found in PrefaceRun MTK Droid Tools. Wait for it to recognize and establish a connection with your phone. This should appear after a minute:
Take note that a blue rectangle on the lower left means you're still not rooted. Press ROOT.
Wait for about three to five minutes. In my case, MTK Droid tools crashed So I didn't see a superuser app.
But I downloaded root checker and sure enough, my phone was rooted. Only the superuser app was missing.
I also opened MTK Droid tools again and saw a green rectangle (which means I am rooted :victory: )
So now, technically, you are rooted. But we still need a superuser app, so I downloaded a superuser app that I liked and updated the binary. I downloaded SuperSU by chainfire from the play store. Done!
or, you could try the superuser button in the root, backup, recovery tab. I didn't try it though
2.4.0 Other stuff you might wanna try or know about if none of these methods worked for you, here: http://forum.xda-developers.com/showthread.php?t=2523814
Chapter 3.0.0: RECOVERY STUFF
3.2.0 How to backup stock recovery
3.3.0 What is clockworkmod recovery?
3.4.0 What is carliv touch recovery?
UPDATE: I think O+ 8.31z was primarily sold for the Philippine Market; as such, I may be in competition with more Philippine based forums such as symbianize and gsmworldfive. Therefore, I think it would be best that I leave the two 8.31z links here and discontinue any plans on improving this thread. Here they are:
http://www.symbianize.com/showthread.php?t=1094034&page=10
^this link contains a SPFT flashable pre-rooted clean stock rom.
http://www.gsmworldfive.com/forum/showthread.php?t=37787
^this link uses the SPFT method too, but the rom here has much more root apps installed already, like swapper, greenify, auto ram cleaner etc. (Oh, stock keyboard was also taken out).
Both confirmed working to bring back a bootlooped 8.31z. I prefer the first one though
Until next time! My dad plans to sell this phone soon so I guess I won't be learning how to make custom roms anytime soon yet... Hope you guys are doing well
Click to expand...
Click to collapse
UPDATE: Since my dad hasn't sold it yet, I'm playing with it again. There is a Filipino facebook group that is dedicated for 8.31z users. I think they have custom roms ported there.
Click to expand...
Click to collapse
Chapter 4.0.0: ADD INIT.D SUPPORT TO STOCK ROM
Check here! http://forum.xda-developers.com/showthread.php?t=1933849
I haven't personally tried any one yet. You are always proceeding at your own risk
Tweak for speed, battery life, and other cool/useful stuff.
Chapter 5.0.0: Speed
There are tons of stuff to speed up your phone, and they're not just limited to one specific phone. So bring in the list.
1. Use Greenify (find it in the play store)
Requirements: Root (optional for auto-hibernation. Highly Recommended.), Android 4.0+
You may greenify stuff like Guardian if you are not using it, or maybe the FB app too. Saves some battery and gives a little free ram for better multitasking.
2. Disable fancy window animations and transitions
Go to settings>developer options and disable the three animation options to animation off.
3. Use a cpu controller like No Frills CPU control (find it in the play store)
Controls how fast or slow you want your CPU to go. Default Governor is hotplug.
For a faster phone, set the governor to performance. It sets the CPU to scale to the max that you set. Use when you are playing heavy games.
For a battery saving phone, set the governor to powersave. It sets the CPU to scale to the min that you set. Use when you only plan to use really light apps.
For a balance between performance and battery save, it's probably best to go back to hotplug since it can turn the second core on or off depending on your usage.
4. Tweaks and Scripts
Info: Tweaks refers to build.prop tweaks. Scripts refer to init.d scripts. So this is a two-part thing. Adding build.prop tweaks, and running init.d scripts. Some do this two-part thing simultaneously in one flasher. Others, separate the tweak part from the script part. The reason they do this is because phones running from stock usually do not support init.d scripts, but only build.prop tweaks.
Our 8.31z cannot support init.d (yet) so for now we will only do the tweak part.
1. Tweak part of [ SCRIPT | TWEAK ] ◢ Project Fluid™ ◣ by Spex. [size="+1"]Recommended.[/size]
Please press thanks in his thread! This is not my work.
Project Fluid has a separable tweak part. I didn't apply all as some are optional. So I just applied it and what happened?
Using Antutu X Benchmark
Before Project Fluid Tweak: 7334
After Project Fluid Tweak: [size="+1"]9264!!![/size]I only selected some of the tweaks (i.e. I didn't use "unlock with volume rocker and other stuff like that) Here's what I added to my build.prop. Feel free to do the same.View attachment 2785183
How to:
1. Open ES explorer (I'm using latest version)
2. Copy the tweaks that you want to add to build prop. Find the tweaks in spex's post or copy my selected tweaks. And thank spex in his thread.
3. Press the menu button on your phone. Click tools. Click on for root explorer and grant root permissions.
4. Click root explorer. Click Mount R/W. Choose R/W for /system and click ok.
5. Navigate to /system and open build.prop with ES note editor. Press the menu button on your phone and click edit.
6. Now paste the tweaks into the build.prop file. Or type them manually
7. Reboot and enjoy!
2. Tweak of Dash-M Script and tweak by myaservip
Please press thanks in his thread! This is not my work.
Dash-M has a tweak part and a script part too. If you want to try Dash-M Tweak, go to his myaservip's thread and download the zip, transfer to the root of your sdcard, go to recovery mode, and flash from there.But personally, Project Fluid's tweaks are more complete. I haven't tried Dash-M script since we haven't added init.d so stay tuned.3. Script and Tweak of ★ [MOD] ◢ PurePerformances™X ◣ | Golden Edition | Scary performances on Android by Jeeko
Please press thanks in his thread! This is not my work.
This is a single inseparable script and tweak in one so we cannot use it yet. Stay tuned.[size="+1"]General reminder: Tweaks and scripts are usually not mix-able. So remove one before trying another.[/size]
Chapter 6.0.0: Cool/Useful Stuff
1. Xposed Framework and Modules.
Our device can definitely benefit from Xposed modules! 4.2 is capable of running these.
2. TouchPal Keyboard
A good replacement to stock keyboard. Contains different keyboard layouts and support for tons of languages! And if you have experienced the keyboard not pressing the right button, this might be a better replacement.
3. Moreto come.
Hi there fellow Filipino! Please continue what you're doing. I can help you in some way in installing CWM-esque recovery tool for our phone. As it is a UBIFS-type system, many have said that it's a tricky job. A lot have failed but some did it successfully like me. I followed this tutorial from here
chinaphonearena.com/forum/Thread-CWM-For-All-MTK-Easy-Magic-CWM-MT6575-MT6515-MT6577-MT6517-MT6589-MT6582-MT6592
Sorry I can't post links yet because this is a new account.
So I was able to boot into recovery, but I stopped there until someone successfully restore our phone from a backup (even if it's just stock ROM)
Cheers! You should try it!
PS. I tried your build.prop and benchmarked afterwards, only to get about 7100+. HOW DID YOU GET TO 9K?! Please indicate if you have a lot of apps and is greenify and that cpu tool the only apps you're using for speed?
After sometime though, my phone got slow, so I deleted the added lines in build.prop and speed went back on. What's happening?
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
zildjosh97 said:
Successfully enabled init.d! I used term-init. It was so easy! Just a matter of minutes. Now, to try some scripts...
Edit: Currently backing up using Carliv Touch Recovery, the MTK compatible CWM recovery tool, before going further. Will try restoring it later. If it is a success, then Chapter 3 is done!
Click to expand...
Click to collapse
Hi! I've been a little busy lately haha. I'll get back to updating this thread in a week or so
Are you new to this stuff? Or have you had previous experience before? Seems like you're going pretty well! I don't know much about this phone of ours yet, maybe you know more than I do
Update: So my O+ phone wasn't sold, and now I plan to use it. Just tested Carliv 2.4 using Yuweng's Auto Magic Installer, and it installed! Restore doesn't work though. And don't advance restore > restore system. You'll get a bootloop haha.
HELP
What is the best CWM or TWRP on my o+8.31z, newbie here. and How? any Help. Thank you for rooting process. as well.
Sory
Sorry if I'm wrong forum, I just want to ask, is there any one can help me to do the rooting of the device Himax H TWO with the following specifications
CPU: MT6735 OCTACORE @ 1.3GHz
GPU: Mali-T720 MP3
Screen : 5.0 inc 720 x 1280 pixels (~294 ppi pixel density)
Android : Marshmellow with lewa os
Karne : 3.18.19
Ram : 2GB
Internal memory : 16GB
I HOPE there that will help me to do the roots and modify twrp for this device
Thankyou fery much
nothing working for MT6572 device (not that O+) for root.. tried all one click or simple root methods nothing working
MTK Droid root and tools waiting for hours and hours and nothing happens it just wont root my mobile idk what to do
Hi XDA ,Hi Friends And Welcome Guest
Before everything Remember that Please hit Thanks when someone helps you out!
Download Android x86:
There are several versions, but I suggest you Download this version :
Android-x86 4.4-r1 live & installation iso
on Aug 8, 2014, by Chih-Wei Huang
Install Android x86:
There are several methods, but I suggest you follow me
Make the system R/W for root access
[HOW-TO] Install Android x86 on any PCs / Laptops / VM
Manage Ext Partition from Windows:
You need to install ext2fsd
Ext2Fsd is an ext2 file system driver for Windows (2k, XP, Vista and Win7). It’s a free software. Anyone can modify or distribute it under GPL2.
Downloads:
View and download Ext2Fsd packages
Express Installation with Ext2Fsd installer:
Double click on Ext2Fsd-version.exe to execute Ext2Fsd installer and follow the setup wizard to install and configure Ext2Fsd.
To uninstall Ext2Fsd, just click “Uninstall Ext2Fsd” in start menu, or use Add/Remove programs in control panel to uninstall. Need restart your computer to get it finished.
Done
if you wanna add something to sd card just follow this path:
X:\android-4.4-r1\data\media\0
Please hit Thanks when someone helps you out!
Edit Grub Bootloader
Follows this path on windows
X:\grub
And find menu.lst
Then open with Notepad or Notepad++ and edit lines.
The example of menu.lst ( don't use for yourself )
HTML:
default=0
timeout=6
splashimage=/grub/android-x86.xpm.gz
root (hd0,4)
title Android-x86 KitKat
kernel /android-4.4-r1/kernel quiet root=/dev/ram0 androidboot.hardware=android_x86 video=-16 SRC=/android-4.4-r1
initrd /android-4.4-r1/initrd.img
title Windows
rootnoverify (hd0,0)
chainloader +1
Install App on Android x86:
Tap the clock on the taskbar, tap the pop out that appears, and then tap Settings.
Scroll down the list and tap Security, then on the right, scroll down and tap Unknown sources.
Tap OK on the prompt that appears.
1. Install Apps From Google Play Store
2. Installing app Using The Conventional Method
Step 1: Use Windows and Copy .apk file to this path
X:\android-4.4-r1\data\media\0
Step 2: Run File manager from Android and install file from this path:
\data\media\0
3. Installing app using Dropbox
Tweaks:
Android Xposed: tweak your phone's UI
[ROOT] Kernel Tweaker | Original Thread
Clean Master Phone Boost
Check Post #2 & #3.
Bug & Issues
Recovery:
CWM - TWRP ???
Flash Gordon????
Not work
If you have any idea pleas help us. :laugh:
Apps - Tools - Utility
Mount internal hard drive:
Automatically mount and dismount USB sticks on various devices like the Galaxy Nexus, Nexus 7 and Nexus 10. The Nexus 4 is not supported - this is an issue with the device, not with StickMount !
[APP][01.07.2014] StickMount v3.10 [ROOT]
Change Language on HW Keyboard:
A non visible soft keyboard (Input Method) intended to be used with hardware Bluetooth and USB keyboards. It automaticly detects Bluetooth keyboards (and in some cases also USB keyboards) and brings up the Input Method dialog. It also supports a lot of different keylayouts for non-US external keyboards.
[Android 1.6+] External Keyboard Helper Pro
Turn Ethernet To Wifi:
If you want an app that needs wifi And you want it to run on ethernet Go here
[MOD][Xposed] Fake Wifi Connection [1.6]
Fake GPS or Mock Locations:
Go Here and check it : [APP][OSS] Fake GPS Path
Rotate everything In landscape Mode:
Rotation manager is a tool that lets you choose which application you want to rotate or which one you don't want to rotate. It is a really simple app designed for the least possible power and RAM consumption.
Download From Here
Duel Boot for Windows:
Easy BCD:
EasyBCD Community Edition allows you to create a multiboot environment in order to run multiple operating systems on the same computer.
The application also features BCD (Boot Configuration Data) Backup/Repair utilities that provide users with the possibility to reset the BCD configuration or recreate and repair boot files.
Download Link
http://www.softpedia.com/get/System/OS-Enhancements/EasyBCD.shtml
Installing Windows After Android-x86
There are two different approaches:
Recovering GRUB after re-installing Windows
Please refer to the Reinstalling GRUB2 guide.
Master Boot Record backup and re-replacement
This method does not work for computers with UEFI boot. In consequence, it won't work for pre-installed Windows8 and some pre-installed Windows7.
Back-up the existing MBR, install Windows, replace your backup overwriting the Windows boot code:
Create an NTFS partition for Windows (using fdisk, GParted or whatever tool you are familiar with)
Backup the MBR e.g. dd if=/dev/sda of=/mbr.bin bs=446 count=1
Install Windows
Boot into a LiveCD
Mount your root partition in the LiveCD
Restore the MBR e.g. dd if=/media/sda/mbr.bin of=/dev/sda bs=446 count=1
Restart and Ubuntu will boot
Setup GRUB to boot Windows
reserved
The Android-x86 4.4-r2 released (the second stable release of kitkat-x86).
http://www.android-x86.org/releases/releasenote-4-4-r2
Stable - Fast
I have made a program to display the percentage of your phone on your computer. Requirements:
[*]Computer that can run bash - Linux WILL work, Mac might.
[*]USB-to-phone cable
[*]ADB enabled on phone
Has been tested on the following:
LG P716 Jelly bean stock- One Works the other doesn't
LG P716 KitKat - Works
LG P500 with CM11 (by mukulsoni)and rooted- Works
Samsung S3 stock - Doesn't work
HTC One S (Thanks LS.xD)
Samsung Galaxy Ace II (Thanks LS.xD)
To run, use
Code:
cd,
to navigate to the folder containing the files then the Terminal folder. After that run
Code:
./BatteryStatus.sh
Your help is greatly appreciated to porting it to Windows/Mac and adding new devices. If you have got screenshots or working devices, feel free to tell me or pm me about these. I will add them to this list.
Secondary mirror: http://www.mediafire.com/download/n2qbb537jpn22p3/batteryStatus.zip (contains both terminal & alpha graphical version)
Warning:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
XDA:DevDB Information
BatteryStatus, Tool/Utility for all devices (see above for details)
Contributors
wilk.gr76
Version Information
Status: Stable
Created 2015-04-02
Last Updated 2015-04-02
wilk.gr76 said:
I have made a program to display the percentage of your phone on your computer. Requirements:
Computer that can run bash
USB-to-phone cable
ADB enabled on phone
Has been tested on the following:
LG P716 Jelly bean stock- One Works the other doesn't
LG P716 KitKat - Works
LG P500 with CM11 and rooted- Works
Samsung S3 stock - Doesn't work
Your help is greatly appreciated to porting it to Windows/Mac and adding new devices. Screenshots are coming soon
XDA:DevDB Information
BatteryStatus, Tool/Utility for all devices (see above for details)
Contributors
wilk.gr76
Version Information
Status: Stable
Created 2015-04-02
Last Updated 2015-04-02
Click to expand...
Click to collapse
I'll give other linux versions a try later this day helping you to figure out on which linux environments it works. Read out the battery level (with terminal) works on both of my phones, so you could add them to the supported list as found in my signature.
On 32bit Linux Mint KDE: CMD + GUI (find all libs but crashes) work with both phones. So the error occured as the 32bit libs can't be handled correctly on a 64bit os for GTK even with multiarch activated.
LS.xD said:
I'll give other linux versions a try later this day helping you to figure out on which linux environments it works. Read out the battery level (with terminal) works on both of my phones, so you could add them to the supported list as found in my signature.
On 32bit Linux Mint KDE: CMD + GUI (find all libs but crashes) work with both phones. So the error occured as the 32bit libs can't be handled correctly on a 64bit os for GTK even with multiarch activated.
Click to expand...
Click to collapse
The graphics is done through Zenity. I just checked, Zenity has problems running on 64-bit systems. You might want to try installing zenity like this:
Code:
sudo apt-get install zenity:i386
and then changing the code in the .sh file from ./zenity to zenity. Might work, might not. My computers are all 32-bit.
wilk.gr76 said:
The graphics is done through Zenity. I just checked, Zenity has problems running on 64-bit systems. You might want to try installing zenity like this:
Code:
sudo apt-get install zenity:i386
and then changing the code in the .sh file from ./zenity to zenity. Might work, might not. My computers are all 32-bit.
Click to expand...
Click to collapse
I'dgive it a try, but you actually removed the GUI version and I have it not stored. The screensgots are attached.
EDIT: Zenity:386 can't be installed on my 64bit system due to not resolveable dependencies.
LS.xD said:
I'dgive it a try, but you actually removed the GUI version and I have it not stored. The screensgots are attached.
Click to expand...
Click to collapse
Just changed it. You can use the mediafire link or the in the downloads tab, graphical.zip
Thanks for the screenshots!
UPDATE: As Microsoft will support BASH in the Anniversary (a.k.a. Redstone I) update, it will be compatible with all 3 'big' platforms. Yay!
**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
GrapheneOS is an open source privacy and security focused mobile OS with Android app compatibility. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. Currently it is based on AOSP.
Link: (Mod Edit: Link removed)
Important information:
1. This ROM does NOT include Gapps or Google Play Service and hasn't Signature Spoofing Support. If you rely on the mentioned things this Rom isn't for you.
2. I take the official releases, modify the install script and include a pre-patched Magisk boot image. I'm not in contact with the GrapheneOS dev which is the reason why i mark this ROM as Unofficial.
3. Due of point two: Please don't ask questions on the official channels as reddit. Leave comments etc here on this thread.
4. You need a unlocked bootloader to flash this rom and must have adb+fastboot installed on your computer. If this is not the case download it from here: https://developer.android.com/studio/releases/platform-tools
I plan to make unofficial releases when new official builds are available.
Features:
AOSP 10
Built-in Firewall
Built-in local backup function (it's not working on all Apps; some doesn't support it)
Improved MAC Randomization
Hardened Kernel
Expanded Permissions (sensors)
Force calls to 4G only
Bugs
- Receiving text over verizon sim doesn't work reliable. Thx @wolfu11 for reporting.
Download: (Mod Edit: Link removed)
Installation:
Notice 1: The First-time installation will wipe your data. Backup first (i recommend this too when you follow the update instructions to be safe)
Notice 2: I recommend to have the newest stock firmware before the First-time installation
First-time installation:
1. Download the zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all_first_install.bat for Windows or flash-all_first_install.sh for Linux
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Install the Magisk Manager App
10. Be happy with a rooted GrapheneOS
Update:
Notice: I assume that fastboot+adb is still installed on your computer.
1. Download the newest zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all.bat for Windows or flash-all.sh for Linux
If your computer asks you to overwrite the current files in the plattform-tools folder, confirm it.
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Start the system once. This need a few more time than the first installation cause the data partition remains. Be patient.
6. Install the Magisk Manager App
7. Be happy with a rooted GrapheneOS
Sources:
https://github.com/GrapheneOS
https://grapheneos.org/releases
https://github.com/GrapheneOS/kernel_google_coral
https://github.com/GrapheneOS/device_google_coral-kernel
All Credits go to:
- The GrapheneOS team
- wolfu11 for reporting the verizon bug and testing the windows scripts
- and topjohnwu for his amazing Magisk
Created: 09.08.2020
Based on: Android 10
Updated: 21.08.2020
Current Version: 2020.08.07.01
Changelog from 09.08.2020
New Release: 2020.08.03.22
SHA3-512 Hash for Complete zip:
Code:
773c67b8571927c6f884a98ee67a10f96c3a759e34f925f7a8aaab7c19a4ca6b1ff53bb6dc500b4fe7c306b73853189a1c559889df6d9b4f2e8a90258d3d26c9
SHA3-512 Hash for Unpatched boot.img:
Code:
9b584f6941d37f60a7ed17ec4108b7bf484c3cbf1b63f2be6af1e59f452ed1d06e1b64704785d6ca3b38a3c09c8f29657f88c757bda993df509ef001d9842f00
Changes:
full 2020-08-01 security patch level
full 2020-08-05 security patch level
rebased onto QQ3A.200805.001 release
fix secondary stack hardening when a non-page-size multiple stack size is specified
fix picking up previous build date when doing incremental builds
Vanadium: update Chromium base to 84.0.4147.89
Vanadium: update Chromium base to 84.0.4147.105
Vanadium: update Chromium base to 84.0.4147.111
Vanadium: remove Chromium logo in chrome://version
kernel (Pixel 4, Pixel 4 XL): read-only data expansion
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. I patched the boot.img which come with GrapheneOS in the zip with Magisk and then replaced the original GrapheneOS boot.img in the zip with the patched version.
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
dhacke said:
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. It isn't needed anymore to flash Magisk separately from the zip. I replaced the stock boot.img in the zip with the pre-patched one.
Click to expand...
Click to collapse
Just a heads up - you really aren't meant to pre-patch a boot image for Coral/Flame, as you are only meant to patch the boot image from your own individual device, as per the man topjohnwu himself
See: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
Can you supply the unpatched boot img?
Thank you
wolfu11 said:
Can you supply the unpatched boot img?
Thank you
Click to expand...
Click to collapse
Done. Look here: (Mod Edit: Link removed)
I added an SHA3-512 Hash for file checking,too (see changelog from 11.08.2020).
Changelog from 15.08.2020
New Release: 2020.08.07.01
SHA3-512 Hash for Complete zip:
Code:
f3a2b088e0ec503296d5a2527a3766951cb2a3ccd1955ced14d304222e76ed3f341dd9d84b6e186a534eddac335065b756c1fdc89d0f1db3985314424e7f9eea
SHA3-512 Hash for unpatched boot image:
Code:
11abb901511ce8e39911bc951be4b1a349158c5d8389e74766942159c0f83aa9730ed39d8c8ae6c3cc66be559e3c165b5d4f35e0962d20a7be0b1532673a0287
Changes:
SELinux policy: fix executing apk libraries as executables for third party applications
Installation Notices:
From 2020.08.03.22 => No wipe needed. Just take the update scripts and let the right one running (see OP).
From Stock Rom => Use the install_first scripts. Be aware: This will wipe your data
Apart from that i recommend to make a backup first always (to be safe).
Wireguard Kernel integration
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
[email protected] said:
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
Click to expand...
Click to collapse
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
dhacke said:
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
Click to expand...
Click to collapse
Just need to add this to local_manifest for WG support
If unfamiliar with local_manifest, it's located in /.repo/local_manifests/ - it'll be the only file in that dir, often it's called room service.xml but it could be something like graphene_manifest.xml. Either way, it'll be the only file there and it'll be an XML - add those lines above to it and sync and you should have WireGuard support.
<remote name="zx2c4" fetch=https://git.zx2c4.com/>
<project remote="zx2c4" name="android_kernel_wireguard" path="kernel/wireguard" revision="master" sync-s="true" />
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
wolfu11 said:
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
Click to expand...
Click to collapse
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
dhacke said:
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
Click to expand...
Click to collapse
I will try it when I get home today thank you
wolfu11 said:
I will try it when I get home today thank you
Click to expand...
Click to collapse
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
wolfu11 said:
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
Click to expand...
Click to collapse
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
wolfu11 said:
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
Click to expand...
Click to collapse
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
dhacke said:
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
Click to expand...
Click to collapse
That script worked thanks
wolfu11 said:
That script worked thanks
Click to expand...
Click to collapse
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
dhacke said:
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
Click to expand...
Click to collapse
No problem i'm happy to test. unfortunately the still is an issue with texting on verizon which is what i use this phone on. the texts send but receiving them is not reliable. I tested on an att sim and it didn't have an issue so it's something on verizon's end.