Related
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Mini How To
How to install recovery and custom ROMs
Changelog and Downloads
2011-02-11
IMPORTANT NOTE: I have not tested this ROM as I not own U8150 anymore
FILENAME: U8150V100R001C191B822_021211_094422.zip
MD5: 110c084c71729aca1ea8361dcb5fe5f5
* Reverted back to Launcher2
* Added Apps2SD
* Add couple apps I think is useful: wifi analyzer, android terminal, alogcat, cache cleaner-ng. (these can be easily uninstalled)
* Built with latest kitchen 0.120
* Removed Gingerbread keyboard and Google Goggles
2011-01-15
FILENAME: U8150V100R001C191B822_011511_221843.zip / Mirror
MD5: 357e5efb21d3272bb0820c0e14cfe913
* Added Boot Animation - Android Scribble 2.0 no flare
* Added Gingerbread Keyboard - Renamed Gingerbread Keyboard - updated 2010-12-28
* Unlocked Market - thanks xxhp for the package
* Added Google Goggles and AdFree
2011-01-09
This ROM should have overall better performance(hopefully)
Note:
Do a wipe of data and must clear dalvik-cache because of JIT being enabled (under 'wipe' in AmonRA Recovery 1.6.2 ROM)
FILENAME: U8150V100R001C191B822_010911_182214.zip
MD5: d8fae03567ebfa1602a116cc9e5aa587
* Added more ring tones from CM rom
* Ring delay fix
* CDRom symlink fix
* Fixed proximity delay (phone come off of the "black screen" faster)
* Turned Automatic brightness ON
* Now wifi will scan once every 1 minutes when not around a known location.
Help minimize battery drain.
* Added JIT
* Set Setup Wizard to run 'Optional'
2011-01-05 Initial Release
FILENAME: U8150V100R001C191B822_010511_014603.zip
MD5: 059fe7693164b1031a63fce373d57717
* Rooted (Superuser.apk + su)
* BusyBox installed
* /system/framework is deodexed
* /system/app is deodexed
* twitter/facebook/documents2go moved to /data/app
* swapped out Launcher 2 for Zeam Launcher
* Apps like Gmail, Maps, Vending etc updated.
If you like my work please make a donation via the Donate to me button on the left
Enjoy
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
hachoo said:
Thanks for the update quail!
Do you have the AUS version of the Ideos? If so, who'd you get yours from?
Also, can we use this thread as a ROM request? (i.e. overclocking ability, gingerbread development)
Click to expand...
Click to collapse
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
[How to] install recovery and custom ROMs
I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
Part 1 Installing Recovery ROM
Please refer to this post before flashing Recovery ROM - AmonRA Recovery 1.6.2 and BLUE Screen
The custom recovery allows you to do all sorts of lovely things such as installing ROM update zips (for the forthcoming custom ROMs), wiping various parts of the device, backing up and restoring and much more.
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
Downloads
AmonRA Recovery 1.6.2 - DOWNLOAD (MediaFire Pro) / MIRROR (CoBlitz / ROMraid) - MD5: 65d4dcbbedb956a9f88dd1981fb31ef8
How to install - Windows, Linux and OSX
Download the recovery image of your choice above and extract the zip file
Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
WINDOWS - double click 'install-recovery-windows.bat'
MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-mac.sh' followed by './install-recovery-mac.sh'
LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-recovery-linux.sh' followed by './install-recovery-linux.sh'
Part 2 Installing Custom ROM
Note: When using the Custom Recovery image use the Trackball to move up / down and press to select. Use the volume down button to go back.
Download a Custom ROM of your choice and place the ENTIRE ZIP (Do not extract it) onto the root of your SD card. By "Root" I mean do not place the file in any subfolders
Enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
From Custom Recover Main menu and select the 'Backup/Restore' option. Choose a 'Nand backup' and let it run it's course
Return to the Custom Recover Main menu and select the 'Wipe' option. Choose the First option 'Wipe data/factory reset' and confirm. <- this is optional after installing one of my ROMs. I personally have not bothered with it with my ROMs
Return to the Custom Recover Main menu and select the 'Flash zip from sdcard'. Select the custom rom you wish to flash, confirm and wait.
Part 3 Restoring back to original ROM
Note: Upgrade operations will erase the user data.
Find and Download ROM from Link provided on WiKi that you want to install
Copy the entire dload folder (with UPDATE.APP in it) to the root directory of the MICRO SD card.
Make sure your handset is power off. Insert the MICRO SD card into the handset. Pressing the END key and VOLUME UP key, and then press the POWER key to power on the phone and enter the Software Upgrade Mode.
You can see process bar start from 0 on the screen. (this take a few minutes)
Then the handset will restart automatically. Then it is OK.
Reference:
Part 1 info taken from here
quail said:
Yes I have the AU version and I bought a Crazy Johns pack with 4GB micro HCSD carded included from Aus. Post for 159AUD. I was luck and go one that was not locked to any network.
Yes you can use the thread for ROM requests, I personally will be ignoring requests for OCing, as there is a very nice little app called setCPU which works great on the U8150.
Click to expand...
Click to collapse
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Trekker56 said:
Thanks. But can you plz post a guide or give a link on how to install the modified ROM in IDEOS for noobs like me
Click to expand...
Click to collapse
Sorry I did think to add a how to install recovery/custom ROM how to, well there is one now.
Thanks
hachoo said:
I got the same deal!
Have you played around with the kernel at all? I'm not experienced in programming etc. but apparantly to OC the IDEOS U8150 more than 600mhz (setcpu does this automatically), it needs a kernel hack like other phones do.
Click to expand...
Click to collapse
I have played around with Linux Kernels in the past just not the Android kernel yet... but I am sure it not that hard to patch it and recompile.
I am happy with the 600MHz that setCPU unlocks it too.
quail said:
You can enter recovery mode - turn it off, then press the power button while holding the 'volume up' and 'send' (green).
[*] Put your device in bootloader mode - turn it off, then press the power button while holding the 'Volume Down' and 'End (Red)' keys
Click to expand...
Click to collapse
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
tankknat said:
The Main thinkg about these two parts here, when i enter recovery mode i get a blue screen is that right... nothing BUT a blue screen.
When i try to enter the bootloader mode it stays on the IDEOS logo, the first one when you turn it on...
Also im guessing it has to be plugged into the usb at all times for these.
Click to expand...
Click to collapse
You should not be getting a blue screen, you sure your using the correct key combination?
Yes you need the USB cable plugged in to use the bootloader. Yes the bootloader is ment to just sit at the IDEOS logo
yeah im 100% sure i used the correct key combo for the restore recovery mode, and sweet as for the bootloader, just wasnt 100% sure on that one.
Thank you OP for the info here, I used them to flash the recovery and I'm going to flash your ROM.
Having a Desire from the very first day I'm not new to these things, but this little boy is in my hands since this afternoon and it's amazing that you came with this just in time.
Will report back in a while with impressions.
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
quail said:
What package did you download? I forgot to test one my builds and aborted installation on me, but I have fixed it and already put up a work version. Please try the newer version
Click to expand...
Click to collapse
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
@ngel said:
Hi, I flashed "U8150V100R001C191B822_010711_042603", the one I guess is the newest (despite the "2010" typo on the first post ).
Is there a newer one?
Click to expand...
Click to collapse
thanks, fixed the typo.
ATM there is no newer version.
@ngel said:
OK, here I am. Just attempted to flash the ROM (after a full wipe), but it fails with an "Installation aborted." message just after the ISO symlink one. Looking at the update script, I guess there was a problem while flashing the BOOT partition.
Rebooting into the OS result in the new (rooted) ROM, but something is missing: the build.prop is likely the old one (I still see the old build string) and I have only 118 MB of free NAND space.
Coming from the Vodafone Italy ROM.
Any hint?
Click to expand...
Click to collapse
Another thing I am not sure what the diff is between the Italian ROM and the Australian ROM. I wonder if you phone is not fully compatible with the Australian ROM?
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
First version working
I had the same problems as @ngel using the newer version. Fail with the iso symlink.
Used the first version you posted up and that worked without a problem.
Zeam Launching is really snappy. Or I just haven't bogged down my phone with a whole bunch of crap yet.
Thanks for your work I bought my Ideos through 2 Degrees in New Zealand.
Request:
I quite like the look of the black notification bar and green icons. Would you be able to theme this rom with those? Also could you include the gingerbread keyboard. I know I can install it separately but would be cool to have Touch Pal and the original keyboard removed and replaced with the gingerbread one.
tankknat said:
ARGH, ok not good...
booted up to flash my loving ideos and i think i killed it...
'Firemware update step 1/2
Unpacking
[=============] (thats a progress bar
!
update failed
and all my buttons are blinking...
Click to expand...
Click to collapse
Did you power on your unit holding the 'volume up' and 'red' key?
First things first, let me give credit where credit is due!
ZergRush - For creating his script to root the echo; and also giving Saridnour the Tools to create is "Kyocera Echo 1-Click" root method.
Saridnour - For his committed work to Hear the Echo (Our Kyocera Echo Website) and creating the recovery image from scratch pretty much!
KyoceraEchoHax - For Advertising the site and helping us to obtain over 200 members in one month (and growing)
Me - For bringing all these random people together
-------------------------------------------------------------------------------------------------
Okay, now to the good stuff
Here is Saridnour's OneClick Root for the Kyocera EchoHERE
The main problem poeple have is the fact that they use USB tethering! YOUR TETHERING MUST BE OFF or this will not work. tethering uses the ADB servers making it unusable while it is active. TURN TETHER OFF!!
Instructions from Saridnour:
Tool will do it all.. You just need to install the Kyocera Echo drivers from their site (links on the tool)
Let me know if you find issue or bugs. I did this pretty quick and hacked out most of it sitting at TacoTime for dinner last night. lol. The FC's drove me nuts until today and think this should be stable for everyone now. No FC's for me in some time. I did the online update as well without issues, but don't reccomend it just yet although the tool can revert you right back if need be.
Usage:
1- Extract files to your computer, open it, and click Rootme.
Thats about it. Follow the steps and you should be golden. And yes.. These will be the driods you were looking for!
-------------------------------------------------------------------------------------------------
Next is Saridnour FULLY FUNCTIONAL recovery image, it has been tested by multiple people and this is the official release! you can get it HERE
Post from Saridnour on the Original Site:
Well at long last, the Recovery Image is now complete and ready for public Release!
.
Thanks to all the donators, beta testers and those who helped this along the way. I will update this as needed to help the install process and give thanks where needed. I was very rushed getting this up as I wanted it out on Halloween.. the ultimate echo treat!! But we all know what happens when we rush..
BUT the file was done and tested prior to so its just the presentation that was rushed
.
A BIG thank you to Na’ven Enigma for sharing some of her websites bandwidth and hosting the files. She wanted to make sure everyone was able to get instant access to the recovery. Please give her a BIG thank you!
.
.
Only known issue is that you cannot mount the device as a usb drive to copy files. This is a common issue with CWM and should have little to no impact as our echo has removable Micro SD cards.
.
.
To install:
-Follow the directions given in the script (IE: Install the drivers from Kyocera for the Echo, Install the driver that is launched from the script (it's not part of the standard echo drivers)
.
- Make sure it is booted to the os and that debug is turned on: (phone settings -> applications -> development -> USB debugging)
.
- Extract the archive to a folder (IE : the Desktop of your computer)
.
- Run the script “SAR_Recovery.bat” (From within the folder noted above ON YOUR PC)
.
- Follow the prompts given, read what it is asking/telling you and take that action (very short and simple)
.
- Exit from the script and you should be done with the upgrade.
.
- Install from the marketplace “Quick Boot” (free) to allow you to boot into recovery as there are no hardware keys known at this time. You can also use ADB if you can’t access the OS, just send this command: ADB reboot recovery.
.
- Backup your device, Find a rom and have FUN!'
.
.
If you can't boot the OS prior to install:
If you can only see the Kyocera bootloader screen and not boot the OS you need to do this another way. Its still easy and you will just need to follows the steps above up to running the script and install the included driver (or from withint the folder you extracted, install the driver) and then connect your device in bootloader mode (Kyocera screen with yellow light on) and from the pc, ope a command prompt, change to the directory that you extraced the files and type this command " Fastboot devices" it should return ??? meaning it can see your device. IF NOT YOU DO NOT HAVE the drivers loaded, are not in bootloader mode, or your usb is not connected [Bad canle/port/etc]). Once it can see your device type "Fastboot flash recovery recovery.img" and it will install CWM. You will then need to run "fastboot boot recovery.img" to boot into recovery. From there you can install your new rom from HTE.
.
.
Note: The whole process takes less than 5 min. If it hangs, has an issue or you are unsure what it did. Give it another couple minutes, pull the plug, reboot and try again. You can not hurt your phone running this as if the install fails or currupts the recovery image, you only need to reboot to the os and the bootloader to correct the issue and this is what this script does to begin with
.
Don’t forget to donate if you find this of use!
.
Enjoy
-------------------------------------------------------------------------------------------------
Now I will ask you all a favor.
So in the last month or so our site (Hear the Echo) has gone from 20 members in the first week to 200+ 3 weeks later. This is great and horrible at the same time. Our bandwidth cannot support 200 people (it wasn't expected to grow so fast). So I please ask you all to donate to HTE and Saridnour. I ask for HTE because we need to expand our Bandwidth because the site has had a minimum of 2-8 members joining DAILY and we cannot hold on much longer (we have about 5 MB left until the site shuts down for the rest of this week, the bandwidth restarts at the beginning of the next month). So PLEASE donate to us. Also, I say Saridnour because I would not be posting right now if it wasnt for his committment and effort for the site. Thank you Saridnour SO MUCH MAN!
Thanks for reading everyone,
Ognimnella (AKA BFG SgtRecon on HTE)
# Bump #
Sent from my PG86100 using XDA App
Great job guys!! I tried to donate, but HTE came up Error and Sardinuor showed the paypal donate, but cannot complete the process. Please check the donation links....
opm said:
Great job guys!! I tried to donate, but HTE came up Error and Sardinuor showed the paypal donate, but cannot complete the process. Please check the donation links....
Click to expand...
Click to collapse
Hey thank you so much for the support, just click the HTE name again and it should be functional! And I will get in contact with Saridnour very soon about finding someway to link his paypal also, again thank you so much
My brother had root with Android 2.2 (z4root method), but the 2.3.4 update caused his phone to not boot up and he got a replacement. Knowing what I know now, I could of used fastboot to flash the recovery.img...
So I'm gonna go try this! Instead of using "Saridnours" method, couldn't we just use this?
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update] - xda-developers
Anyways, I'm gonna try this. So now I can update my old video! lol
http://www.youtube.com/watch?v=cG2DtNAHZR8&hd=1
That if the base of saridnours one click root!
disturb3d1 said:
My brother had root with Android 2.2 (z4root method), but the 2.3.4 update caused his phone to not boot up and he got a replacement. Knowing what I know now, I could of used fastboot to flash the recovery.img...
So I'm gonna go try this! Instead of using "Saridnours" method, couldn't we just use this?
Revolutionary - zergRush local root 2.2/2.3 [22-10: Samsung/SE update] - xda-developers
Anyways, I'm gonna try this. So now I can update my old video! lol
http://www.youtube.com/watch?v=cG2DtNAHZR8&hd=1
Click to expand...
Click to collapse
Sent from my PG86100 using XDA App
AWESOME
Had a few issues with the drivers at first.. But I stepped away, cleared my mind, and tried again and all worked wonderfully! My Echo is now running like a dream!
THANK YOU ognimnella, and Saridnour!! I will donate when I have a little cash to spare!
Kyocera Echo
These are cool phones ! Rock Solid Gorilla glass no scratch surface and can be used as brass knuckles Thanks for root . Now we need some cool roms .Mine is stuck on 2.2.1 stock and will not take the gingerbread update . it would be nice if someone could capture that update and make it our first full flashed rom . You can pick up an echo CHEAP on Ebay . Got mine for 84 bucks and its super fast snapdragon processor and loads of program memory make it a cool toy . STill i had hopes of using it as a Donor Reciever but no luck with Paid Cdma . Hope SOme developers grap these sweet phones .
Android Sooner Single Fastboot Interface wrong platform??
I get "Android Sooner Single Fastboot Interface is the wrong driver for this platform" So what is the right one for the echo. Also when i try fastboot devices I don't get the ??? just another blank space. My device shows up as "Unidentified device or unknown device too. I feel this is the last thing preventing me from un-bricking my phone so if anybody has any can help me i would greatly appreciate it.
I used SAR recovery and i get all the way to the point where I'm in bootloader mode, the amber light is on, and I'm waiting on devices. So I'm out of ideas.
Peezly said:
I get "Android Sooner Single Fastboot Interface is the wrong driver for this platform" So what is the right one for the echo. Also when i try fastboot devices I don't get the ??? just another blank space. My device shows up as "Unidentified device or unknown device too. I feel this is the last thing preventing me from un-bricking my phone so if anybody has any can help me i would greatly appreciate it.
I used SAR recovery and i get all the way to the point where I'm in bootloader mode, the amber light is on, and I'm waiting on devices. So I'm out of ideas.
Click to expand...
Click to collapse
Its been so long since I had this phone idek man. See if you can find saridnour and ask for his help
Sent from my HTC Evo 3D using XDA
I wish that somebody will find the way to flash echo to boostmobile.
Sent from my not Echo using Tapatalk 2 Beta-6
are there any custom ROM
---------- Post added at 01:46 PM ---------- Previous post was at 01:46 PM ----------
could we get a forum?
jamcar said:
are there any custom ROM
---------- Post added at 01:46 PM ---------- Previous post was at 01:46 PM ----------
could we get a forum?
Click to expand...
Click to collapse
Google it
Sent from my PC36100 using Tapatalk 2 Beta-6
Hi, my echo stuck on kyocera logo screen. It was working fine. I tried to update the latest version of android and when it installing it stopped.. then here I am stuck at kyocera logo.. any help?
zerotechservice said:
Hi, my echo stuck on kyocera logo screen. It was working fine. I tried to update the latest version of android and when it installing it stopped.. then here I am stuck at kyocera logo.. any help?
Click to expand...
Click to collapse
Do u know how to use adb and fastboot.?
Sent from my PG86100 using XDA
i got into the HTE part. what next? i have alot of option. I choose reboot echo now.
Now still stuck on kyocera logo
I'm trying but...
I am having to go through cmd to do this and I get as far as "Fastboot Devices" and it says "acess denied". What am I doing wrong?
after installing drivers it stuck on *wating device* have same on both pc, have change usb ports and restar pc, same thing
how can i flash recovery by adb?
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.
updated4/4/2017 (Still does not work on stock 5.0) - Removed due to it still not booting stock 5.0, and ALSO now breaks booting unpatched.
twrp 3.1 is broken
twrp 2.7 is broken
twrp 3.0.1 works
some/most custom roms work
Most official/stock do not.
EFIDROID - Official link
Developer: m11kkaa
DO NOT BUG THE AUTHOR ABOUT BUGS/FEATURES, THIS IS UNOFFICIAL.
Most custom roms appear to boot
Install:
assumes on stock firmware (Custom roms must report the DEVICEID as hlte, hltetmo, hltespr or hltevzw. Ask your Rom maintainer to correct it or visit post #51)
assumes root and bootloader unlocked
For now "efidroid" on playstore is not configured for our device, so we will do this using our own server:
Download "EFIDROID" from the playstore
Download "TerminalEmulator" from the playstore (or use adb shell)
Download "SimpleHTTPServer" from the playstore
NEW UNTESTED - Removed
OLD Download EFIDROID_SERVER_FILES from View attachment EFIDROID_SERVER_FILES.zip
Open and extract the "device" and "ota" folder to the INTERNAL storage of your phone
Open SimpleHTTPServer (do not change default settings)
Open Terminal Emulator and enter: (make sure you didn't forget any spaces)
su
setprop efidroid.server_url "http://localhost:12345"
Now open efidroid, it should automatically connect. Now press the menu key in the top left corner and press install, then press the big install button.
Now create your slot, and reboot.
Use the vol +/- to navigate up or down, use the power button to select an option
Long press power button on internal rom/recovery to boot without efidroid
Reinstalling/Updating:
Download the new OTAPACKAGE file and extract to INTERNALSD, replace old device/ota folders
Clear EFIDROIDMANAGER cache/data
Run the SETPROP command (don't forget su)
Turn on SimpleHTTPserver
Open efidroid and click uninstall, and then click install (Or click reinstall)
MAKE SURE YOUR BUILD DATE NOW MATCHES THE UPDATED BUILD DATE
Uninstall:
if you hit the uninstall button, the app copies the contents of the UEFIESP back to the real partitions and deletes the partition_*.img files. It does not delete the UEFIESP directory or any of the multiboot directories because they may contain other important files.
flashing boot+recovery outside of EFIDroid's control(e.g. using stock's fastboot/odin flash, or using unpatched boot) is pretty much the same as uninstalling efidroid without deleting the partition_*img files.
All that means that you don't have to worry about any of that if you restores your boot+recovery partitions(either through the app or manually). If you want to free up some space you can delete the UEFIESP directory using a root file manager.
Bugs/Issues:
REPORT ERRORS/BUG ON GITHUB
"can't find tagloader for type -1" - your recovery/rom is not supported (like twrp 3)
Report errors: https://github.com/efidroid/projectmanagement/issues
What you must include:
Exact steps to reproduce the error
Give the exact error shown on screen
If its storage related:
Give the output of "cat /proc/1/mountinfo"
EMERGENCY :
If you find yourself frustrated and just wanting things back the way they were:
Download odin
Download twrp (get the md5/tar version for odin)
Turn off phone (pull battery)
boot to download mode by holding vol down and home and power
Start up odin and press the AP button and browse for the TWRP file. Press start to flash.
Reboot phone into twrp recovery (vol up + home + power), and restore your boot/recovery partitions.
EFIDROID has now been effectively disabled[/HIDE]
Help and info:
If you are familiar with adding touchscreen support please visit us!
Join us on Slack : http://join-efidroid.rhcloud.com/
Once joined: https://efidroid.slack.com/
EFIDROID G+ page : https://plus.google.com/communities/...43671219382368
[/CENTER]
Works on N9005 LTE ?
It looks pretty cool but I've got limited knowledge. My N9005 is on phronesis rom v4.1, IdleKernel v6.6.5 and all partitions converted to F2FS, will it work on this format as well :/
As long as it is a note 3 on msm8974 (sorry exynos) it should work.
File system support should be trivial. I used that same FS myself
Is this an actual GRUB loader for android?
If so am ashuming this means it's possible for UNIX install
i.e. Arch Linux as OS.......
Hmmm.... Windows RT on Note 3... ^^
What about ACPI? We might need this for WinRT
With all due respect, I think you've posted a how to post bit earlier. I'm a flashaholic & the wait for the zip is killing me
I didn't think the day would come.
As a pleb, I will follow this thread with great interest.
djmalik420 said:
With all due respect, I think you've posted a how to post bit earlier. I'm a flashaholic & the wait for the zip is killing me
Click to expand...
Click to collapse
lololol
Wonder if this is ever going to work Great concept though.
Fake ¿ ???
Only what i see its a bootanimation, in the Video from a "older and other"
The OP account is suspended so I guess something fishy is going on.
Guess we will wait and see
oh come on now. I got suspended for being rude to a well respected member of xda. And its not fake... Really? Anyways... I took my ban as a break and just started back with m1cha on getting the uefi part to work with the screen.
A few pointers: You still need devs to port each os, like windows, true linux ect.
This is just a multiboot. So many devices lack that, some had safestrap, or kexec ect, but all those methods had quirks or special rules, or depended on android. This loads before even the kernel.
Also, it will have many tools that a typical recovery has, so you may not even need to reboot into recovery to setup partitions, also aroma was ported, so maybe even installing roms/kernels too.
Also, there will be an efidroid server "store" where you can get tools and apps to run in efidroid. So devs can extend functionality. Also there will be an android installer to make everything easier.
Just think of this as a pimped out safestrap.
SaschaElble said:
oh come on now. I got suspended for being rude to a well respected member of xda. And its not fake... Really? Anyways... I took my ban as a break and just started back with m1cha on getting the uefi part to work with the screen.
A few pointers: You still need devs to port each os, like windows, true linux ect.
This is just a multiboot. So many devices lack that, some had safestrap, or kexec ect, but all those methods had quirks or special rules, or depended on android. This loads before even the kernel.
Also, it will have many tools that a typical recovery has, so you may not even need to reboot into recovery to setup partitions, also aroma was ported, so maybe even installing roms/kernels too.
Also, there will be an efidroid server "store" where you can get tools and apps to run in efidroid. So devs can extend functionality. Also there will be an android installer to make everything easier.
Just think of this as a pimped out safestrap.
Click to expand...
Click to collapse
It doesn't matter what negative comments you get because "Criticism Is The Key To Innovation" it's my personal quotation ...I've been visiting this thread since day one at minimum of three times a day hopping that you would have uploaded the zip...Make it quick buddy & keep up the good work :good:
We need a samsung expert. Getting the display to work in uefi is troublesome. DTSI and gcdb display experience is needed.
SaschaElble said:
We need a samsung expert. Getting the display to work in uefi is troublesome. DTSI and gcdb display experience is needed.
Click to expand...
Click to collapse
as far as my knowledge is concerned, Master @darkera13 is kinda expert you're looking for...I don't personally know him or his skills but people around note 3 forums praise his work very much
Is this Note 3 specific?
This is kinda an off topic question, but, just a few days ago i wanted to try Remix OS out in my PC, but noticed that there is no direct EFI support...just thinking if this thread would be any benefit for PC UEFI users trying to boot Android x86 directly through efi file.
sorry for the question, might be my knowledge limitation on the field...
Using a x64 cpu and grub or refind you can boot RemixOS, they have a uefi image on their site. (Thats what they said) Basically you really don't need efidroid for this, as it would only make it more complicated.
grub is exactly my problem...
thanks a lot for clarifying
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!