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.
Related
HOW TO ROOT YOUR HTC EVO
DO NOT USE A RUU FROM SPRINT IF U WANNA MAINTAIN ROOT. WAIT FOR ME OR SOMEONE HERE TO MAKE A ROOT UPDATE.ZIP.
Major thanx for those who helped:
keishou (for the rooted build. without it none of this would be possible)
maejrep (for testing and modding a recovery for the EVO)
Flipz (for hosting the files)
Paul (for his recovery work on the desire and legend)
Amon_RA (for his recovery source on github)
WHAT THIS ROOT METHOD WILL DO:
- wipe all of your data so brace for that. backup or what not
- Allow you to flash custom roms
- Boot into a custom recovery
- Write to system, boot and recovery partitions through recovery
WHAT THIS ROOT METHOD SADLY WONT ENABLE YOU TO DO:
- Write to system or recovery while in android
- Flash a custom recovery that can be booted into by holding vol down and powering on
THINGS YOU WILL NEED:
download files below:
- PC36IMG.zip
- evorecovery
INSTUCTIONS FOR ROOTING:
- Put the PC36IMG.zip on the root of your sdcard
Code:
adb push PC36IMG.zip /sdcard
- Power off the phone
- Hold volume down while powering the phone on. continue to hold volume down until you see the WHITE bootloader screen.
- After a few seconds it will begin to checking for files, and find PC36IMG.zip. while its doing this it will show a blue progress bar while its checking. (this takes 30 - 60 seconds to finish)
- It will then list all the images in the zip and ask you if want to flash. SAY YES
- When its finished it will ask you if you would like to reboot. AGAIN... SAY YES
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
RECOVERY INSTRUCTIONS:
- Extract the evorecovery.zip to your desktop
- plug your phone into a usb port on your desktop
- In a shell:
Code:
adb reboot recovery
- this will reboot your EVO into recovery mode. at this point turn your attention to the directory u extracted the evorecovery.zip to.
Code:
For Windows XP ~~> Run recovery-windows.bat
For Vista and Windows 7 do it as Admin
- in a shell do:
Code:
For Linux ~~> ./recovery-linux.sh
- at this point turn your attention to the phone and navigate to create a Nandriod Backup. you can now flash custom roms, write, and make changes to system.
- to flash a custom rom put the rom on the root of your sdcard. wipe data, dalvic cache and chose the option to flash update.zip from sdcard.
RECOVERY NAVIGATION:
-
Code:
Volume up/down moves through the list and Power selects.
RECOVERY SOURCE:
- http://github.com/jhansche/amonra_bootable_recovery/tree/supersonic
Code:
git clone git://github.com/jhansche/amonra_bootable_recovery.git
git checkout supersonic
Once you have finished and rooted your device. please flash another rooted rom from the forum. Flipz has made a root build of the rom that came on the device. it can be found HERE. you will need to wipe data and dalvic cache before flashing this. And again because i cant stress it enough... DO NOT accept a OTA update from Sprint or use a RUU, or u risk lossing root forever, and ever
HOW TO RETURN BACK TO STOCK BUILD:
-Easy peasy- run the RUU in the first post of this thread. this is the only RUU that after flashing, you will still be able to root using this method. link below:
ROOT SAFE STOCK RUU
Re: {how to root your htc evo} <coming soon to a thread near you>
I love you toast. In a manly, non-homosexual kinda way!!
As soon as root is provided, be sure to understand that I will buy you a beer or two my friend.
Good to see you active on the EVO 4G toast as I liked what you did for the last phone I had (htc hero)... not having root on this EVO phone is a bit of a frustration.
just like i told you before... you pm me your ADDy and ill send you some fresh coffee... i work at Green mountain coffee roasters
being that I'm not surprised about you n all involved getting root..alls I wanna know is if EVO-Godmode is in effect..
btw..use guys are ridiculous!! Mad props
Excellent! :d
O m g w t f b b q
I have a evo ready for testing if needed.
I likewise have a Google I/O Evo. Toast, you may remember me from the CDMA Hero forums, if you want a tester just let me know (a nice, roundabout way of asking for early access to root)
Can't wait to start working on custom roms and kernels for this awesome device!
SUPER!
If beta testers are needed, i have the I/O EVO and can test. please pm.
Donation coming!
toastcfh said:
reserved
HTC Evo 4g is root more details and links coming in the next few days. Just working out the details and making it easy for everyone.
Current status:
Has su permissions
Able to run a custom recovery
Able to write to partitions
Click to expand...
Click to collapse
[email protected] that was quick, I think the next couple of months are going to be fun
Calkulin said:
[email protected] that was quick, I think the next couple of months are going to be fun
Click to expand...
Click to collapse
+1
im excited to see this secret method which is being used to obtain root ... rest is down hill
Re: {how to root your htc evo} <coming soon to a thread near you>
Would it be possible to take an autoroot app like the other group of devs working on it? Or perhaps a batch file? You are the man, toast!
-------------------------------------
Sent via the XDA Tapatalk App
I as well have an I/O unit, and am down to beta test! I will be in a 4G network next week, and would love to test if the Wireless Tether app functions on the 4G network
Calkulin said:
[email protected] that was quick, I think the next couple of months are going to be fun
Click to expand...
Click to collapse
Calkulin, nice to see you. So it seems you'll be getting an Evo! Sweet, I used to use your roms and kitchen on my Diamond. I look forward to see what you, toast, and the rest of the community has in store with the Evo. Glad to see we have full root on the Evo. Next friday can't come soon enough.
sick! cannot wait to seee what you guys can do with this phone.
the screen is too gorgeous to be stuck with the stock ui, so i'm really hoping that since now there's root for this phone it'll get some good custom rom'ing.
Subscribed!
Why reserve a thread for this? Is XDA running low on storage?
Hope to see some magical things happen with all your genius brain powers combined.
Re: {how to root your htc evo} <coming soon to a thread near you>
EVO here too! Please allow me to beta test because I work for VZW and I wanna show them the awesome things this phone will do! Granted, the Droid's will do what this does, but this phone is so awesome lol
Kernel Update Utility 0.9YouTube video"Making kernel flashing a bit easier"
About:
This lightweight tool takes a kernel, and flashes it to your device. You can give it the kernel in zImage or CWM flashable zip format. Some people have come across bootloops when using clockworkmod to flash kernels, hopefully this tool will prove to fit better for the job. It can also push and apply kernel modules. I have now flashed a kernel using this tool more times than I can count, and not a single bootloop or failed flash.
This tool is ideal for people who do not want to mess with command lines, and people who want the job done fast and easy.
System requirements:
Windows XP SP2 or higher
.NET 4.0
HTC Sync (or ADB drivers)
Rooted, ENG S-OFF Desire HD
Changelog:
0.9:
- Added support for Lee's kernels
0.8:
- Added support for Kamma's new kernels
0.7:
- Fixed Windows XP file not found -bug
- Optimized the code further
0.6:
- Most cmd windows hidden
- Better instructions in module pushing
- Out of beta!
0.5a:
- Optimized a lot of code
- Improved SU permissions; fixed modules not getting pushed with phones that do not have root adb by default
- Cleans up /system/lib/modules to ensure cp functionality
0.4:
- It is now possible to choose multiple modules
- It cleans up afterwards
0.3:
- CWM zip file flashing, pushes all modules
- Space in filename -bug fixed
0.2:
- Initial release
Click to expand...
Click to collapse
If you like my work, please consider (or just hit the thanks button ):
Hi,
thanks !!
Please add more selections for ko files:
- tun.ko
- cifs.ko
- other
with friendly greet
starbase64
Yeah, I will
I will also make this work with CWM flashable zips, I am programming that in right now.
Hi,
good news, thanks.
with friendly greet
starbase64
It can now flash zip files that would usually be flashed in clockworkmod. Using my app to flash it should reduce the possibility of a bootloop. Also the space in filename -bug has been fixed.
e: Another update, now for selecting and applying kernel modules. Please leave feedback! Is there something I should change? Any features you would like to see in this tool?
Keep in mind that this tool can also be used for recovering from some bootloops, where kernel itself is not properly flashed. In some situations, however, boot.img corrupts in CWM flash, then you will have to restore a partial nandroid.
thanks.. now i wish there is a tool for pushing ENG hboot and CWM recovery .. where is unrevoked
Well, I can enable my tool to flash a recovery, but because flashing hboot is so risky, I think I will not do that feature..
So, are people interested in a recovery flasher?
So now I can flash the .zip files that before I was flashing with the recovery with this application?
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
jkoljo said:
Yeah, if those files are kernels. This tool has been tested with Apache14's 1.2 and 1.5 GHz OC/UV kernels.
Click to expand...
Click to collapse
Wow it's amazing guy!!! i have tried now, with, before my htc desire hd was going in eternal bootloop with origianl rom and 1,2 kernel now it's ok really tank you!!!
No problem, glad it helped!
Hi,
support for german users here > www.handy-faq.de
with friendly greet
starbase64
Noob question but how can you revert back to original kernal?
Not tried this yet But this is What I been waiting for. How long does the process take?
Thanks
Sent from my Desire HD using XDA App
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Deicist said:
Used this tool to flash the Buzz 1.51GHz Kernel. First off, congrats on such an easy to use tool for noobs like me. It's really simple and straightforward. However, I now have a problem with my wifi not working (just shows 'error' in wifi settings). I'm guessing this is because the module didn't apply properly? I've tried it a couple of times now with the same result...although I fully accept it could be stupidity on my part.
Further info:
I have root (permenant, via visionary+) and S-off (Eng HBoot installed) but not installed clockwork recovery yet.
I start the app, set my DHD to 'charge only', tick 'I understand the risks' and click next.
Browse to the file I downloaded for the Kernel (this one) and click 'next'.
click 'go to fastboot' (phone reboots in fastboot mode) click 'Flash' and something about 'writing zimage' flashes past. Click Next. (phone reboots)
When phone reboots I enter my PIN, unlock the phone and select 'charge only' for the USB connection (this isn't mentioned, but I figure it needs to be connected like this for the adb stuff to work) and press 'apply modules'. Something on my phone requests superuser access (not sure if this is just co-incidence or something the app is doing) so I allow it. Loads of messages flash past on my desktop (I assume this is applying the modules) and the app says 'modules pushed and applied'.
My wifi status shows 'error' so I try a reboot. Still shows error.
Any ideas?
Click to expand...
Click to collapse
Same issue here, does not push the wifi module
Strange, it does push it for me. I'll investigate. It may have something to do with root rights, does bcm4329.ko appear to your sdcard?
Nope, doesn't appear in sdcard.
For further info I tried it with 0.3 as well, same result.
Also, none of the modules get pushed, it's not just the wifi one.
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
jkoljo said:
My app removes the files from sdcard afterwards, so they might not be there anymore when you check it. I have now uploaded a new version with completely new SuperUser access code, also a lot of the code has been optimized.
This version works for me 100%, I just flashed from Apache14's kernel to kamma's kernel and back, wifi worked every time.
Also keep in mind that you should wait for the Android system to fully boot up before trying to push and apply the modules. So wait for "Usb debugging connected" and "Charge only"
Please give feedback!
Click to expand...
Click to collapse
Nope, will not push wifi module, all phone settings are as per instructions
Which rom are you on? Do you have HTC Sync 3.0 on your computer?
Try pushing modules manually as per Apache14's thread first post, if it works then the problem is propably in my tool, if it does not work, the problems is at your end.
HTC Desire S Tutorials/Guides
{
"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"
}
Reviews:
1. GSMArena: http://www.gsmarena.com/htc_desire_s-review-590.php
2. Engadget: http://www.engadget.com/2011/04/10/htc-desire-s-review/
3. Slashgear: http://www.slashgear.com/htc-desire-s-review-28142921/
4. Techradar: http://www.techradar.com/reviews/phones/mo...s-930920/review
5. Phonearena: http://www.phonearena.com/reviews/HTC-Desire-S-Review_id2702
Specifications: (From http://www.gsmarena.com/htc_desire_s-3776.php)
Code:
[B]General:[/B] 2G Network GSM 850 / 900 / 1800 / 1900
[B]3G Network: [/B]HSDPA 900 / 2100
[B]Announced:[/B] 2011, February
[B]Status: [/B] Available. Released 2011, March
[B]Size Dimensions:[/B] 115 x 59.8 x 11.6 mm
[B]Weight:[/B] 130 g
[B]Display Type:[/B] S-LCD capacitive touchscreen, 16M colors
[B]Size:[/B] 480 x 800 pixels, 3.7 inches
- Gorilla Glass display
- Multi-touch input method
- Accelerometer sensor for UI auto-rotate
- Proximity sensor for auto turn-off
- HTC Sense UI
- Touch-sensitive controls
[B]Sound Alert types:[/B] Vibration, MP3, WAV ringtones
[B]Loudspeaker:[/B] Yes
[B]3.5mm jack:[/B] Yes, check quality
[B]Memory Phonebook: [/B]Practically unlimited entries and fields, Photocall
[B]Call records:[/B] Practically unlimited
[B]Internal:[/B] 1.1 GB ROM, 768 MB RAM
[B]Card slot:[/B] microSD, up to 32GB, buy memory
[B]Data GPRS:[/B] Up to 114 kbps[B]
EDGE:[/B] Up to 560 kbps[B]
3G:[/B] HSDPA, 14.4 Mbps; HSUPA, 5.76 Mbps[B]
WLAN:[/B] Wi-Fi 802.11 b/g/n, DLNA, Wi-Fi hotspot
[B]Bluetooth:[/B] Yes, v2.1 with A2DP, EDR
[B]Infrared port:[/B] No[B]
USB:[/B] Yes, microUSB v2.0
[B]Camera:[/B] Primary 5 MP, 2592 x 1944 pixels, autofocus, LED flash, check quality
[B]Features:[/B] Geo-tagging, touch-focus, image stabilization
[B]Video:[/B] Yes, [email protected], check quality
[B]Secondary:[/B] Yes, VGA
[B]Features:[/B]
[B]OS:[/B] Android OS, v2.3 (Gingerbread)
[B]CPU: [/B] 1 GHz Scorpion processor, Adreno 205 GPU, Qualcomm MSM8255 Snapdragon
[B]Messaging: [/B] SMS(threaded view), MMS, Email, Push Email, IM
[B]Browser:[/B] HTML
[B]Radio:[/B] Stereo FM radio with RDS
[B]Games:[/B] Yes
[B]Colors:[/B] Black, Red
[B]GPS: [/B] Yes, with A-GPS support
[B]Java:[/B] Yes, via Java MIDP emulator
- SNS integration
- Digital compass
- Dedicated search key
- Google Search, Maps, Gmail
- YouTube, Google Talk, Picasa integration
- MP3/AAC+/WAV/WMA player
- DivX/XviD/MP4/H.263/H.264/WMV player
- Organizer
- Document viewer
- Voice memo/dial/commands
- Predictive text input
[B]Battery:[/B] Standard battery, Li-Ion 1450 mAh
[B]Stand-by:[/B] Up to 430 h (2G) / Up to 455 h (3G)
[B]Talk time: [/B] Up to 9 h 50 min (2G) / Up to 7 h 10 min (3G)
HTC Desire S Guide for Newcomers to Android:
This guide will guide you throughout your Desire S phone. What's the best app to use it on your phone, some tweaks and more!
http://forum.xda-developers.com/showthread.php?t=1097538
Android Versions/History:
The version history of the Android operating system began with the release of version 1.0 in September 2008. Android is a mobile operating system developed by Google and the Open Handset Alliance. Android has seen a number of updates since its original release. These updates to the base operating system typically fix bugs and add new features. Generally, each version is developed under a code name based on a dessert item. The code names are in alphabetical order (Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, and the future version, Ice Cream Sandwich).
Source/More info: http://en.wikipedia.org/wiki/Android_version_history
Roms/radios/fixes/mods/recoveries and everything related to development:
Please refer to this thread: http://forum.xda-developers.com/showthread.php?t=1146601
The Basics of Unix/Linux command / ADB Shell:
Both guides below explains and teaches the basics of using ADB shell commands which is very useful for those who wants to learn more.
Link1: http://forum.xda-developers.com/showthread.php?t=1160222
Link2: http://forum.xda-developers.com/showthread.php?t=517874
How To: Backup or Restore via Nandroid
Nandroid allows you to create a complete system image of your device and stores it to the SD Card on your phone. Making one is very simple but there are a few prerequisites.
1. A rooted Android phone
2. A custom recovery that supports Nandroid (ie: Amon_RA, ClockworkMod, Etc.)
3. A MicroSD card that has enough space for a system image.
A complete image can range from 75-400 MB.
Please follow this link for instructions: http://forum.xda-developers.com/wiki/index.php?title=How_to_backup_or_recover_via_Nandroid
How To: Check if your phone is S-OFF or S-ON and your HBOOT version
1. Disable Fast Boot. (Setting > Power > uncheck Fast Boot)
2. Turn off your phone.
3. Turn on your phone by pressing the power button and volume down button together.
4. You will see a white screen with "S-OFF" or "S-ON" and your hboot version on top of the screen.
NOTE: If your phone is S-ON, you won't be able to root or flash custom ROMs to your phone. To make it S-OFF, follow the guide below.
How To: S-Off your device with Revolutionary: S-OFF & Recovery Tool (For HBOOT 0.98.0000, 0.98.0002)
Unrevoked and Alpharev present: Revolutionary Tool
Please also read the documentation page for this tool: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Does Revolutionary give me root? No. You will need to flash this zipfile from recovery. (It's better to just skip this.)
S-OFF your phone using Ubuntu:
1. Download Ubuntu 11.04 from the Ubuntu site.
2. Burn image onto DVD/CD or create a USB Stick (I suggest creating USB stick since it loads faster, for me). (Follow instructions provided at the website to create a bootable CD or a USB Stick).
3. Reboot computer. Allow Bootup popup menu (usually F8?).
4. Select DVD/CD-drive or USB Stick to boot Ubuntu.
5. Wait a bit for things to load. Choose "Try Ubuntu".
6. Now, Ubuntu should load up successfully. (see screenshot)
7. Connect phone to your computer and make sure that Debugging Mode is enabled on your phone. Download the tool from http://revolutionary.io/ for Linux (Firefox included with Ubuntu). Keep that browser window open.
8. Extract the downloaded file and put it into the root directory (in Ubuntu, that's Ubuntu/Ubuntu, if I recall correctly).
9. Search for the Terminal (Windows key pops up the search, I think; otherwise, it's the icon on the top left corner of your screen), run Terminal.
10. Type in "sudo ./revolutionary" at Terminal.
11. It'll provide a key. Go back to the browser window where you downloaded Revolutionary tool - there's a form to fill out. Type in the key. It'll generate a second key. Type that key into the Terminal.
12. Make sure it says that everything is successful. It'll ask if you want to flash Clockwork. Type in "Y".
13. Once it shows success, reboot phone.
S-OFF your phone using Windows:
1. Download Revolutionary tool for Windows from http://revolutionary.io/ (Keep the browser open)
2. Extract the zip file to a new folder.
3. Connect phone to your computer and make sure that Debugging Mode is enabled on your phone.
4. Open the new folder and right click on "revolutionary.exe" and select run as administrator.
5. Follow steps from Step 11 above.
WARNING: S-OFF your device will void your phone's warranty. You will need to turn it back to S-ON for warranty. (I don't have a guide to make it back to S-ON right now, so do it as you wish).
How to: S-OFF (Video)
How to: Restore stock ROM and S-On after S-Off
You phone needs warranty? You might need your device back to S-ON mode. Try following this guide to make it S-ON, http://forum.xda-developers.com/showthread.php?t=1187231. I'm not sure if this works 100% all the time because I personally haven't tried this one yet. If this guide works for you, congratulations, if not, try asking around this forum.
How to: Root your device
1. You can achieve root by using Gingerbreak. Follow this link and guide: http://forum.xda-developers.com/showthread.php?t=1044765
2. Or, by using SuperOneClick *recommended* (ROOT ALMOST ALL ANDROID DEVICES): http://forum.xda-developers.com/showthread.php?t=803682
3. Or, you can flash this zipfile from recovery (Source: http://unrevoked.com/rootwiki/doku.php/public/revolutionary).
(You can skip this if you're about to flash a custom ROM since custom ROM are pre-rooted. Unless you want to keep your original ROM, use this to root your device.)
Custom ROMS:
Custom roms can be found in this thread: http://forum.xda-developers.com/showthread.php?t=1146601 or head to the development section.
(Most of these ROMs are pre-rooted, which means that you don't need to root your phone after flashing one of the custom ROM.)
How To: Flash Custom ROMs using Recovery (Method 1)
(You can use your default recovery from Revolutionary tool but I recommend using http://forum.xda-developers.com/showthread.php?t=1377745)
1. Copy your custom ROM "zip" file to your SD card (Root directory).
2. Turn off your phone.
3. Turn on your phone by holding the power button and the volume down button together.
4. Once you see the white screen, choose "Recovery"
5. Make a full wipe/format and clear all cache.
6. Choose "install from sdcard/zip file" and then choose your Custom ROM zip file from your SD card to flash your Custom ROM.
Optional: If you want to use 4EXTRecovery, just flash it like you are flashing your custom ROM(Step 6). Just do it before you flash your new ROM.
How To: Flash Custom ROMs using ROM Manager (Method 2)
(This method might be easier for flashing ROM updates or add-ons)
1. Go to ROM Manager (You can install this software from the Android Market.)
2. If you want to use 4EXTRecovery, please follow steps below, and if you're not using 4EXTRecovery, please skip to step 6)
3. Press your phone's option's button and choose Manual Flash Override.
4. Press OK and choose your phone model.
5. Choose ClockworkMod 3.x (After these steps, your ROM Manager won't ask you to flash new recovery again when flashing new a ROM)
6. Reboot into Recovery and make a full wipe/format and clear all cache then reboot.
7. Now, from your ROM Manager, choose Install ROM from SD Card.
Note: Flashing ROMs can be vary, some custom ROMs may require you to flash some of their own file first. Eg, The LBC Mod ROM requires you to flash "WIPE zip file" before flashing the ROM. Read their instructions carefully to know more.
NOTE: I am not responsible for any faulty or bricked devices after S-OFF or flashing new ROMs. Do it at your own risk.
How To: Flash a ROM in a "Perfect" Way (Method 3 - Recommended)
A great guide from vampire36 for people who encounter the following problems:
1. The ROM you flashed gets stuck on HTC screen (bootloop) while the same ROM works right for others
2. You get the same kernel and radio yet you find your cell to have more battery drain than others
3. Finally some strange force closes and restarts but works perfect for others
So this is basically one of the most perfect way to flash a custom ROM and is a way to help people who face such issues.
Please head to : http://forum.xda-developers.com/showthread.php?t=1257731 to see full instructions and discussions.
How To: Flash Custom ROM (Video)
How to: Flash Radios
1. Download your Radio zip package.
2. Copy your Radio zip package to your SDcard root directory and rename it to PG88IMG.zip.
3. Turn off your phone and turn it back on by pressing volume down and power button together (You need to turn off fastboot under phone settings > power options).
4. Once you're in hboot, the bootloader will ask you if you want to install radio.img, just press yes. (Volume up means "YES", and volume down means "NO")
5. Once the radio flashing is complete press your power button once to reboot device. Done!
Note: You must delete your Radio zip package or rename it to something else when booting your phone after flashing new radio image since the bootloader will always try to flash if a PG88IMG.zip file is on your SDcard.
- Method 2 check here: http://forum.xda-developers.com/showthread.php?t=1178001
How to: Root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
For device with S-ON and a new HBOOT version 2.00.0002. Some ROMs may require you to flash "boot.img" if you're using this method (not needed if you S-OFF your device using "revolutionary" and has older HBOOT), check the ROM thread for info and guidelines.
Please follow this guide: http://forum.xda-developers.com/showthread.php?t=1525100 (Thanks to: n0elite)
How to: Upgrade to new HBOOT version 2.00.2002 / Downgrade to old HBOOT
This is my own guide, I did this on my own phone and it works. This guide is according to those guides made by others(link below), I just made it even more simplified.
1. Download 2.00.2002 hboot.img from http://forum.xda-developers.com/attachment.php?attachmentid=1288640&d=1346184448 (Thanks to Thantos)
2. Copy the downloaded hboot.img to the root of your SD-Card.
3. Reboot into recovery mode.
4. Do a backup of your ROM using nandroid backup in recovery. (Optional, just in case something goes wrong, but I did not do this.)
5. When your phone is in recovery mode state, open up your command prompt (type cmd in run) in windows and type the following commands.
- adb devices
- adb shell
- su
6. You should now see the sign "#" at your command prompt. Now, backup your hboot by typing, "dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img" without quotes.
7. Now, flash your new hboot by entering this "dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18" without the quotes.
8. Your phone should now have the latest hboot. If you reboot to your boot loader, you should see something like this.
*** LOCKED ***
SAGA PVT ENG S-OFF RL
HBOOT-2.00.2002 (PG8810000)
9. Reboot your phone into recovery mode again and "Wipe cache and delvik cache" then restart your phone if you already have a ROM installed or you could flash a new ROM but make sure you make a full format instead.
Others:
Use this guide at your own risks. I have not tested this method yet. Link here:http://forum.xda-developers.com/showthread.php?t=1236890
Simplified version here (Better version): http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
How to: Downgrade to old HBOOT from HBOOT version 2.00.2002 :
Follow this guide: http://forum.xda-developers.com/showthread.php?t=1318919. Thanks to Skanob.
Another one here: http://forum.xda-developers.com/showthread.php?t=1399331. Thanks to mtothearkus
And here if above method doesn't work for you (for recent 2.15.x versions): http://forum.xda-developers.com/showthread.php?t=1443636. Thanks to shadi22.
Note: Check all guides and decide which suits you best.
[Archived] How to: DOWNGRADE Desire S with S-ON (Reason being archived: Guide not needed since revolutionary is able to S-Off HBOOT version 0.98.0002. Unless you really want to, follow guide below.)
To downgrade from HBOOT version from 0.98.0002 to version 0.98.0000: http://forum.xda-developers.com/showthread.php?t=1078497 (Credits to: newrad67)
Warning! I don't recommend this to users who are new to Android since there is a possibility of bricking your device. I will not be responsible if this happens.
NOTE: You may also check sonikz procedure (http://forum.xda-developers.com/showpost.php?p=13780422&postcount=4). I think his procedure is faster. You may use which one is easier for you to follow.
How to: Create/Modify/Porting ROMs
You can try using dsixda's HTC Android Kitchen tool. This tool is only for:
1. Those who are brand new to creating custom ROMs and want an easy place to start learning.
2. Those who just want to modify shipped ROMs or someone else's custom ROMs to their liking.
3. Those who are confused by all those scripts and complex commands required for building and extracting.
Please head to: http://forum.xda-developers.com/showthread.php?p=5626292 for more details and download for this tool.
Note from the developer: This is NOT a tool to automatically turn you into a full-fledged ROM developer. ROM development normally involves work from the ground up and involves time, research and patience. I am just giving the tools to help the average person get things done quickly from an existing base.
- For porting sense to other sense devices tutorial: http://forum.xda-developers.com/showthread.php?t=1222746
- Here's a new guide from proxuser on how to port ROMs to desire S: http://forum.xda-developers.com/showthread.php?t=1563857
Extras:
How to: Fix Broken Screen: Follow this link to replace Desire S screen: http://www.techradar.com/news/phone.../how-to-fix-a-broken-touchscreen-1114324#null
How To: Install Sony's New PlayStation Mobile For Android On Any Rooted Device: http://forum.xda-developers.com/showthread.php?t=1919574
PSP Emulator For Android V 0.4: http://forum.xda-developers.com/showthread.php?t=1970933
How To: Make your Android lag-free: (Seeder 1.1 entropy generator to provide significant lag reduction) http://forum.xda-developers.com/showthread.php?t=1987032
How to: Run Ubuntu within Android on Desire S: http://forum.xda-developers.com/showthread.php?t=1256949 (credits to zacthespack)
Android Partitions Explained: http://www.addictivetips.com/mobile/android-partitions-explained-boot-system-recovery-data-cache-misc/
All About SD-Cards: http://forum.xda-developers.com/showthread.php?t=1947560
FAQs:
1. What's S-OFF and S-ON?
- In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. (Source: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/)
(NOTE: S-OFF is not ROOT, S-OFF your device does not mean that your device is Rooted. They are totally two different things.)
2. How can I backup all my apps and apps' data files before flashing a new ROM and wiping all my datas?
- You will need to root your device first using Gingerbreak(see above). And then, install Titanium Backup and use that to backup all your apps and your apps' data files.
3. I have WiFi death grip/Wifi signal drops when I hold my phone in certain ways.
- There are no 100% right fixes yet for this issue but give it a look here: http://forum.xda-developers.com/showthread.php?t=1175646
4. Is it possible to install 4EXTRecovery/Flashing ROMs/ROOT on Desire S with S-ON?
- No, it is not possible. You must/need "S-OFF" to customize your device.
5. I've just received this system update OTA - 1.47.61.1 or later. If I install it, will I loose my S-OFF and root?
- Yes, you will lose both S-OFF and root once you update because it will update the hboot to 0.98.0002. However, you can try following this guide http://forum.xda-developers.com/showpost.php?p=16110608&postcount=5 to update the OTA but not the hboot. Check this one out also http://forum.xda-developers.com/showthread.php?t=1190992 and http://forum.xda-developers.com/showthread.php?t=1194488 to S-OFF and root if you have updated the OTA.
6. How will I brick my device? and how to prevent it?
- Follow this thread to find out : http://forum.xda-developers.com/showthread.php?t=1226849
7. What is a "Stock ROM" ?
- Stock ROM is basically one that comes straight from HTC with no amendments and probably the one that your phone came with out of the box! -ben_pyett
Click to expand...
Click to collapse
Useful Information for newcomers to Android:
Android Terms, Slang & Definitions: http://forum.xda-developers.com/showthread.php?t=1466228
CPU Governors explained: http://forum.xda-developers.com/showthread.php?t=1663809
[REF]Terminology for the newbies: http://forum.xda-developers.com/showthread.php?t=1394458
[GUIDE]Easy and simple adb and fastboot setup for newbies(Windows Only): http://forum.xda-developers.com/showthread.php?t=1272595
Click to expand...
Click to collapse
Final Notes:
Any Problems or Questions? Please ask around the forum or read the FAQ first, it usually helps. Thanks to those people who has contributed to this thread. Enjoy your phone!
Click the "Thanks" button if you find this thread useful!
WARNING: Please follow those steps carefully, it usually works if you do it properly. However, I am not responsible for any faulty or bricked devices. Do it at your own risk.
include hboot downgrade guide also.
Include the guide to downgrade hboot from version 0.98.0002 to 0.98.0000
http://forum.xda-developers.com/showthread.php?t=1078497
this is very useful but try not to replicate what is in the INDEX sticky thread.
I suggest that you request that this thread is listed in that thread so that its easy to find
Nice
Sent from my HTC Desire S using XDA Premium App
i think this should be made a sticky in the general section
most new comers don't check the development section
kartkk said:
i think this should be made a sticky in the general section
most new comers don't check the development section
Click to expand...
Click to collapse
I agree, general would be a better place for this thread.
In which case PM the moderator, smokestack76
Sent from my HTC Desire S using XDA Premium App
ben_pyett said:
I agree, general would be a better place for this thread.
In which case PM the moderator, smokestack76
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
i made a request
Thanks guys, I will get more stuffs to add here soon... thanks for the downgrading hboot guide suggestion, I will look into that and add it in later...I hope this thread could help out those who are still new, who need more info...
once again, thanks a lot... if you have anymore suggestions or any corrections that I need to make, please tell me.
nodeffect said:
Thanks guys, I will get more stuffs to add here soon... thanks for the downgrading hboot guide suggestion, I will look into that and add it in later...I hope this thread could help out those who are still new, who need more info...
once again, thanks a lot... if you have anymore suggestions or any corrections that I need to make, please tell me.
Click to expand...
Click to collapse
i think you should remove the specs(it makes the guide look complicated & big) & give a link to gsmarena or htc site
I actually like that you added the specs
The only thing you should do is to keep it updated.. thats all
Thanks
Can you please note in the downgrade HBOOT section that RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs. Would save a lot of people asking why they can't downgrade.
Thanks for the support guys. I've added some new guides today. If I made some mistakes and need corrections on those guides, please do inform me. I'm always here to improve it. Thanks!
tigris666 said:
Can you please note in the downgrade HBOOT section that RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs. Would save a lot of people asking why they can't downgrade.
Click to expand...
Click to collapse
Thanks! Added!
*remove this please. sorry for double post*
can you add how to install custom recovery & how to perform a nandroid backup to the guide?
You should also link the downgrade method in post 4 by sonikz. I think it's the easiest and recommended way to do this...
greets
Brilliant. Good job man, very useful
juergen_90 said:
You should also link the downgrade method in post 4 by sonikz. I think it's the easiest and recommended way to do this...
greets
Click to expand...
Click to collapse
yes, I did include the link, please check again thanks
p.s. added a new guide to do nandroid backup and restore. Also another FAQ about s-off and root for the new OTA update.
btw, did I miss something? the http://alpharev.nl/x/beta/ is not working anymore.. it gives me 404 error...
nodeffect said:
yes, I did include the link, please check again thanks
p.s. added a new guide to do nandroid backup and restore. Also another FAQ about s-off and root for the new OTA update.
btw, did I miss something? the http://alpharev.nl/x/beta/ is not working anymore.. it gives me 404 error...
Click to expand...
Click to collapse
new site
& now hboot 0.98.0002 is supported no need to downgrade anymore
This morning I red about Revolutionary: a collaboration between unrevoked and alpharev.
Maybe you can add it to your post
http://revolutionary.io/
I tried the alpharex, but i always get failed t oget root in step 2
Hboot : 0.98.0002, rom stock version 1.47.401.4, android 2.3.3 any thoughts?
cheers
mr.boonet said:
I tried the alpharex, but i always get failed t oget root in step 2
Hboot : 0.98.0002, rom stock version 1.47.401.4, android 2.3.3 any thoughts?
cheers
Click to expand...
Click to collapse
Try using the new revolutionary tool, I've updated the guide(please look back at first post). Hope this helps.
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Getting an error
FAILED(remote: oem unlock is not allowed)
Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...
added to index
Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.
Yes it's normal
Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk
You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.
OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers
You can lock and unlock your bootloader as much as your heart desires without consequence
skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.
TWRP 3.1.0.0 with FIsH for our FLEX 2
Tested on h955 and it's still a BETA
Requirements
Here are the pre-requirements you have to met!
If you can't get them: Close this page and FORGET it (until the day you met those reqs)!
Here are the 2 simple requirements you have to met:
1. root by SuperSU >=v2.76 (greater or equal v2.76)
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
--> for many devices - if not all - this means you HAVE TO downgrade/install LL. It also means that you have to upgrade your SuperSU to this version by e.g. FlashFire if you have a lower version installed!
--> SU by phh is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> Magisk is NOT supported => It needs a modified /boot and this would void the boot signing chain!
--> I will NOT provide downgrading guides there are plenty of them so search and read.
--> I will NOT provide any guides in rooting your device
--> Before you think about downgrading to LL read about ANTI-ROLLBACK protection some devices and may have! Anti-Rollback means you CAN NOT downgrade - it would HARD-BRICK your device (wtf thinking the vendors who we are?? Is this even legal?!)! Check that before!!
2. you have to be able to disable SELinux in your booted Android
--> You do NOT need to set SELinux permanently to permissive. Just CHECK if you COULD get it MANUALLY. If you can get it OK. If not.. you obviously have not full root access but check the forums maybe there is something you can do about this.
--> I will NOT provide any guides enabling SELinux but some lines later you will see how u can execute the very simple check
--> to test this requirement just start the installer of FIsH with --check (see next lines) which will check for all requirements and abort if its not possible
Those above are hard facts so it may NEVER work with MM. Google has changed the way on how the boot chain will be verified and that means changes in /system will void it from now on.
If MM can get fully rooted somehow/somewhen on your device with SuperSU installed and you are able to disable SELinux the method will work there as well.
If you can not meet ALL of the above 2 requirements lay down and cry.
For the others: calm down and read on!
You can simply test those both requirements by downloading the FIsH package and execute the installer with the following test parameter:
./install.sh --check
This way nothing get installed but you will see if it would work on your device or not.
Limitations!
Keep in mind what I said above: FIsH does NOT unlock your bootloader!
That means with TWRP-in-FIsH you can NOT:
Install a custom ROM like CM/Lineage (this will modify boot = SOFT-BRICK)
Install a custom Kernel (this will modify boot = SOFT-BRICK)
Install a custom recovery (this will modify recovery = may SOFT-BRICK)
In short: do nothing which modifies boot or recovery partitions. Those changes will BREAK your boot signing chain.
You can of course flash everything which is modifying /system /data only (e.g. xposed, Audio mods, etc...)
You're able to backup and restore as well of course and doing any other modifications which you may can't while the Android system is running.
Download
READ THE REQUIREMENTS above before proceeding!
Then UNDERSTAND the requirements before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
READ THE LIMITATIONS above before proceeding!
Then UNDERSTAND the limitations before proceeding! <-- omg this is crucial important!!!! Ensure that you really do not skip this step!
... and NEVER ask for ETA's!
if you can say:
Yes! I have read and totally understood the limitations AND the requirements!
then proceed. Otherwise read again until you got it.
Keep in mind that this is a HACK. It may soft-brick your device. you have been warned!
The concept is the same for all models but again no guarantees here for anything.
There is ALWAYS a risk and you should better backup what you do not want to loose before starting downloading this.
Download
Installation (Linux)
You can just install any newer version over an old one.
boot Android and connect USB cable
download the newest version to your PC and open a terminal in that directory
tar xzf TWRP-in-FIsH*.tgz
cd android_FIsH
./install.sh
check the output of that script. you should not see any errors there (hopefully)
Installation (Windows)
use FWUL or be patient.. maybe i or someone else release an installer... maybe...
First run (no PC required)
This FIsH gets installed PERMANENTLY! That means:
You can boot up TWRP the same way as described here again without re-installing.
If you re-install your STOCK image you have to re-install TWRPinFIsH as well.
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH has done it's job well!
This is a good time to do a full backup isn't it ? Manually mount the SYSTEM partition as it gets not auto mounted atm and do a full backup
reboot from here (safely ignore the msg "no OS installed" and reboot anyways) and you should see Android booting (hopefully ... if not see bottom)
Daily Usage (no PC required)
reboot Android
you should now see: LED goes from blue to GREEN
NOW directly when u see this GREEN LED press VOLUME DOWN and do NOT release
wait until the device vibrates and the LED changed to RED. Then release the Volume Down button.
Wait until FIsH completed and TWRP should be shown --> This means FIsH is doing it's job still very well
AGAIN: keep your mind up! You HAVE to ensure that whatever you do and whatever you flash -> NEVER TOUCH BOOT/RECOVERY! If you flash a ZIP ensure first that it do not modify them! Otherwise you WILL softbrick. You have been warned (several times now)
Trouble / Bootloop fix
if you encounter a bootloop (should never happen but who knows) you have 3 choices at least:
Option 1a: (TWRP-Bootloop) Within TWRP open Advanced -> File Manager -> Goto: /system/su.d and click "select" button -> Delete
Option 1b: (TWRP-Bootloop) From your PC: adb shell rm -rf /system/su.d/
Important: Catch the fish log (see next topic)
Option 2 (this works also for a bootloop without twrp): boot into download mode and use LGLaf to get a shell
then:
setenforce 0 <-- if that doesn't work you may have to do a FULL restore to stock
mount -oremount,rw /system
rm -rf /system/su.d/
reboot. You are out of the bootloop.
Important: Catch the fish log (see next topic)
Option 3: Last resort: Reflash STOCK. sorry.. there is always a risk..
Catch the FIsH logs
when in TWRP (or other ramdisk providing adb shell):
adb shell "cat /cache/fish/fish.log"
adb shell "cat /tmp/recovery.log"
OR - when in Android:
adb shell "su -c cat /cache/fish/fish.log"
adb shell "su -c cat /cache/fish/fish.log.old"
adb shell "su -c tar cvzf recoverylogs.tgz /cache/recovery"
adb pull recoverylogs.tgz
Upload the output to https://paste.omnirom.org and paste the link in the IRC channel (see next topic)
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support here only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you will be asked for a server network choose: freenode
Known issues (may never get fixed)
Due to the fact that FIsH is a BRUTAL hijack of the booting process several things may not work as expected.
This will normally not harm anything but you have to know about.
ZIP / ROM flashing:
omg really you wanna hear that again? OK: DON'T TOUCH BOOT / RECOVERY. And you be safe.
When you try to install a ROM it will modify at least BOOT. That means soft-brick!
When you try to install a custom Kernel.. omg really? It will definitively SOFT-BRICK! Maybe you should read the limitations again??
When you try to install a ZIP like xposed, supersu, Vipermod and others ensure that those are not modifying BOOT or RECOVERY partitions. For those mentioned it would be very unlikely but who knows.
FIRMWARE partition:
cannot be mounted - even not manually. You have to live with it.
Double Tap to wakeup (in TWRP):
Unfortunately this cannot work in TWRP-in-FIsH due to the nature of this hijack. You have to live with it.
Credits (without them - no FIsH!!!)
If you feel that someone / you is missing on this list lemme know!
Chainfire for SuperSU! This is the main part of FIsH.
TeamWin for TWRP
@cray_Doze, @dssmex, @Aaahh and @KeiranFTW for their hijack implementations (e.g. https://forum.xda-developers.com/showthread.php?t=2608408, first steps to a G4 hijack)
steadfasterX for the android FIsH !
Here is the h955 device tree for building TWRP with omnirom minimal sources - https://github.com/jarno83/android_device_lge_h955
Here are TWRP logs from backups and restoring if anyone interested - https://github.com/jarno83/twrp_logs
Changelog
29.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA3.zip
Latest FIsH source code and fixes.
3.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL_BETA2.zip
Fixed the RESTORE issue - thanks to SteadfasterX
Used latest FIsH source code.
Went to zip format, now a pit smaller.
2.04.2017 - TWRP-3.1-in-FIsH-v2.0_LGFLEX2_LL.tar.gz
The fishfood is TWRP 3.1.0.0 it uses 15c stock kernel for now. And has a problem with restoring.
What is TESTED
BACKUP and RESTORING /system and /data partitions - OK
Xposed V87 - flashes ok with twrp and works - http://dl-xda.xposed.info/framework/sdk22/arm64/
Tested Device List
H955 running 5.1.1 15c ROM
H950 running 5.1.1 PR ROM - thanks to iDefalt
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Congrats
Have you seen the XDA template for FIsH?
https://forum.xda-developers.com/an...ack-to-boot-want-device-t3578373/post71567825
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Ok, thanks Didn't saw that
So anyone tested it yet ? TWRP booting ?
I have my phone in repair center atm cant test anything.
Yes, I have it on my h955 and twrp boots fine. I tested system backup and restore, now working. Flashed xposed also ?
Sent from my LG-H955 using XDA-Developers Legacy app
/data backuped and restored with success ?
Sent from my LG-H955 using XDA-Developers Legacy app
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
dadaa1 said:
Ok so now what? What is the next step? On road To install custom rom or custom kernel.
Click to expand...
Click to collapse
SteadfasterX is developing some stuff... so maybe on day we will have a possibility to use full custom roms.
But for now we have a custom recovery
If someone is willing to cook something interesting that can work with not touching the boot or recovery partitions... then well I would call it a custom rom
In theory it should work on a H950PR? So I can at least test it
maucvs said:
In theory it should work on a H950PR? So I can at least test it
Click to expand...
Click to collapse
Hi, I think it will work. You'll need to be rooted and You can give it a try ?
Sent from my LG-H955 using XDA-Developers Legacy app
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Seams like the twrp I build is not liking h950
Sent from my LG-H955 using XDA-Developers Legacy app
I'll try to make h950 tree and build a test twrp.
Sent from my LG-H955 using XDA-Developers Legacy app
adds08 said:
It should work..
I already tried this on h950 but there is dead android with red '!' ..
For some reason it wont boot into the fishrecovery and goes to the recovery partition..
Ill try smth when i have time.
Click to expand...
Click to collapse
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
ergo911 said:
Seams like the twrp I build is not liking h950
Click to expand...
Click to collapse
I had a similar issue for the g4 and here it was FIsH because it was too slow for some devices . I will release a new FIsH release which improves speed dramatically asap.
.
Sent from my LG-H815 using XDA Labs
Thanks ?
ergo911 said:
Thanks ?
Click to expand...
Click to collapse
Ok so please use git pull to get the latest updates!
Lemme know if you have any trouble.
.
Sent from my LG-H815 using XDA Labs
ergo911 said:
Can you test this... made a h950 test tree. The twrp boots on my h955 also.
Click to expand...
Click to collapse
Works like a charm on my H950. Thanks! The only issue is TWRP booting time, but it's should be right that, if I understand correctly.
Thank you!