Related
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.
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.
{
"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.
{
"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"
}
[SIZE=+7]LG v10 Resource [/SIZE]
Hey everyone!!
First and foremost, you have to understand no one is responsible for what happens to your device. No one is responsible for exploding your device and no one is responsible if you cannot get WiFi or your alarm does not go off. You take full responsibility for the well being of your device to keep it nourish with wonderful Roms, Themes, Mods and of course, to keep it functioning as you wish for it to be.
This thread will be updated on regular basis. Mostly, on a weekly basis. If you see a thread you feel should be added here (Even from other variants that works with OUR phone), Please send me a quick PM HERE Or mention me with @mgbotoe and I will come running
Special "Thank you" to @scloutkst for looking out for good guides/mods for entry. Real help to everyone coming in!
[SIZE=+2]General XDA Threads[/size]
Forum Rules | New Users Guide | XDA Tour | Report Posts | Our Moderators
[SIZE=+2][INDEX][/SIZE]Click on a Link below for More Info
Manufacturer's Device Home Page
Basic Device Information
Android Terminology
Questions and Answers, Troubleshooting
Device Tools, Recovery, Bootloader, Root/Un-root/Un-brick methods
Custom ROMs
Kernels & Radios
MODS, GUIDES, and Misc
Please look for a similar INDEX thread when visiting another device forum.
If you would like to create an [INDEX] please Click Here.
A special thanks to everyone who contributed to the production of this INDEX
Please note: This is and will be, an ongoing WIP
ANDROID TERMINOLOGYThanks to @benjamingwynn with his great quick DefinitionsADB - "Android Debug Bridge" a system that can be accessed using a computer where you can manage the device from. You need the Android SDK to use it.
AOSP - "Android open source project" a project by Google Inc. to give android to developers and manufactures for free.
APK - "Android Package" an Android application
Bloatware - Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted. Usually, these are apps are sponsored by a company and included by a carrier for profit
CDMA/GSM - A type of network communication between phones and carriers. GSM phones normally are included with SIM Cards that authorize them onto the network. CDMA have this authorization built in and do not need a sim card.
Custom recovery - A modified version of stock recoveries that allow you to do more things in the recovery mode.
Cyanogenmod (CM) - A free open-source project based on the AOSP. It is a modded version of the Android firmware
Dalvik-Cache - Holds all of the pre-compiled .dex files created from installed apps. These files are static and do not change unless the app is updated.
Deodexed - Where ODEX files are moved into the actual applications modded) version of the Android firmware.
Developer - A man or woman who has created (developed) software.
Firmware - a piece of software to make hardware function correctly. This can refer to Radio Firmware, but is normally used as another name for ROM.
Governor - A system embedded into the kernel to automatically change the current working CPU frequency depending on the workload. It would only go up to what it is overclocked (or underclocked) to, this is called the maximum frequency. It would not drop below the minimum frequency.
KANG - The process of creating a code based of someone else's code.
Kernel - An important part of all operating systems that handles the CPU and other vital components. A modded kernel may be used for overclocking.
Logcat - A logging system built into the ADB
Mod - A modification to a part of the phones software. It is also POSSIBLE to mod the phones hardware but is not recommended.
OTA - "Over the air" a term used to indicate software that was sent to phones directly through the internet to their phones.
Open-source - (not to be confussed with free) A peice of software that is free to edit, use, distribute and share with no charge.
Overclock - To exceed the default maximum CPU speed. This could make a phone more powerful but may cause damage. Although no damaged has been reported so far it could still drain battery life.
Radio Firmware - A type of software that allows correct communication with the radio and the operating system. A newer firmware would normally improve battery life and call quality. The radio firmware only applies to the CDMA/GSM radio.
Radio - (not to be confused with Radio Firmware) A piece of hardware that allows communication. There are 3 main radios in your phone. Bluetooth, WiFi and GSM/CDMA.
ROM -
1. A modified version of the Android operating system operating system.
2. Read Only Memory, a place where information is stored and can not be destroyed, modified or written to.
Stock - An unchanged version of something. Example: I just flashed stock sense.
Underclock - To change your phones maximum frequency to LOWER than the default to attempt to extend the phones lifespan and battery.
WIP - "Work In Progress"
Zipalligned - An archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
INTL - International
Odex - Files that are collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application.
Recovery Mode - A special environment that you can boot into for troubleshooting and upgrading purposes
Tools, Recovery, Bootloader, Root
Informations about tools, recovery, bootloader, root, unroot or unbricking your device. Please make sure to give the OP a proper Thankyou button for their hardwork.
[Tools]
By: @ted77usa, One click toolkit for T-mobile
KlicKiT
[All Varient]
By: @Chainfire, Include Latest, Stable SuperSu
SuperSu Download
[LG-H901]
Recovery
By: @KAsp3rd, Installing TWRP for T-mobile
TWRP
[LG-H960A]
Recovery
By: @rudi666, Installing TWRP for LG-H960A
TWRP
Root
By: @KAsp3rd, Rooting for T-mobile
Root
Bootloader
By: @TheJesus, Unlocking T-Mobile Bootloader
Bootloader Unlock
Stock Files
By: @TheJesus, Boot, System, and Recovery .img Files for T-Mobile
H90110CStock .img Files
By: @mikeyinid, Flashable zip for T-Mobile
H90110CFlashable Zip
Unbrick
Discussion of Unbrick Make Sure to Read First Two Pages
Custom Roms
Custom roms for the various v10. Currently, they are only available for T-Mobile
By: @bdorr1105, come with 3minit
GreezePop
By: @Rydah805, Only stock with no modification
Stock Deodexed, 10C
By: @sonofskywalker3, More on how to build your own rom
Blackhole
By: @tattedup, comes with theme and selected mods
No-NaMe ROM!!
KERNELS
Original and kernels found in our designated forum. Make sure to press the OP Thanks button to show your appreciation.
LG-F600
By: @wolfgart, Kernel Source for the three F600 Variants
Kernel Source [S/K/L]
MODS, GUIDES, and Misc
Mods, Guides, and Random threads to make customizing your phone a whole lot easier. From setting up ADB to changing Icons. Please give the OP a Thankyou button for their hard work.
GUIDES
By: @scloutkst, changing cellular DNS service
Override DNS (a DNS changer)
By: @jedthehumanoid, enabling themes for ATT devices
LG Theme for ATT
By: @danarama, The know all about ADB, Fastboot and Setting it
Set Up Adb and Fastboot Setup
By: @sonofskywalker3, Installing Xposed on T-Mobile
Xposed
By: @mgbotoe Changing LG UI Icons
LG UI Icon Change
By: @gerry_753, Changing Stock LG UI Icons with Icon Packs
LG UI with Icon Packs
By: @Swizzle82, Enabling Multi-users
Multi-User
By: @Bootup, Enabling Apps Ops (Permission Manager) w/o Root
Apps Ops
By: @sharky481232, OP also comes with tool to debloat ATT WITHOUT Root
Debloat List
MODs
By: @ZDeuce2, Speed up slow wifi
Wifi Fix
By: @PUERTO_RUK, Google stock dialer for the v10
Google Dialer / Contact
By: @DucatiMon, Provided HTC apps
HTC Apps on V10
By: @razz1, Adjust displays sharpness
Vsharp
By: @tattedup, Second Screen Fix for Xpose
Second Screen Fix
By: @mth7386, volume boost mod to incread headphone
Volume Boost
By: @P_Toti, Call Rec l Lockscreen l Notifications l MUCH MORE
TweaksBox
By: @Swizzle82, brings signal and battery icons to extended status bar for T-Mobile H90110C.
Extented Status Bar
By: @Apptuners, Change short cut keys WITHOUT Root
Key Plus
Topic of Interest
Discussion]Unlocking Sim Through T-mobile
[Discussion]Music Apps with DAC
[Discussion]Camera Shots!
[Discussion]Xposed Mods that Work
[Discussion]Pros and Cons of V10
[Discussion]Cases
[Discussion]CM 12
[Discussion]Wireless Charging
[Discussion]T-Mobile V10 On ATT Network
[Discussion]Knock on Issues?
Thank you for the detailed index but the the installing exposed link isn't working.
StaticMaal said:
Thank you for the detailed index but the the installing exposed link isn't working.
Click to expand...
Click to collapse
Fixed
I see all the files & mods are T-Mobile variant. Anything for AT&T?
Nevermind. As usual AT&T has locked the bootloader
@blue5055 if you are interested in unlocking your bootloader, you can try the tmobile tutorial one. I can tell you this, I do not think it is unlocked so it wont do anything. The reasons most of the mods are for tmobile is cause they require root...and since tmobile is the only one with root at the moment, the mods are labeled as such. If ATT acquire root than I will add. But if anything not labeled for tmobile it will work for you [which will be all non root at this point].
I am only collecting what is around the forum, sadly I am not the one making the mods and files.
Subscribed. Thanks.
Update:
Added Unbrick section
Updated Mods section along with guides
Also added in Discussion of interest
Thank You!!
Beautiful!!! ...and thanks for the thread too, very useful and well put together.
Added second screen fC with xpose. Give the OP a thank you @tattedup
http://forum.xda-developers.com/lg-v10/general/xposed-fixes-screen-t3246515
And thank you @Kilokk
Just wanted to post a heads up, and maybe it can be added to the op, but flashing the xposed Uninstaller zip file will hard brick your device. It happened to mine and luckily I was able to get it replaced. But I was unable to even boot to fastboot or download mode.
I was just curious if there is a step by step on how to root this device. I'm coming back to an LG device so any help will be appreciated. Thanks in advance.
tymansdaddy said:
I was just curious if there is a step by step on how to root this device. I'm coming back to an LG device so any help will be appreciated. Thanks in advance.
Click to expand...
Click to collapse
POST#3 where it says "Tools, Recovery, Bootloader, Root" It's near the top of that portion of the guide... LOL it's the 3rd topic on that post. :silly:
root method
There isn't a link on the root section, just a link to the root developers profile. I actually need INSTRUCTIONS not needing to know who's responsible for initially rooting the device.
Kilokk said:
POST#3 where it says "Tools, Recovery, Bootloader, Root" It's near the top of that portion of the guide... LOL it's the 3rd topic on that post. :silly:
Click to expand...
Click to collapse
tymansdaddy said:
There isn't a link on the root section, just a link to the root developers profile. I actually need INSTRUCTIONS not needing to know who's responsible for initially rooting the device.
Click to expand...
Click to collapse
The link is for the TWRP thread. It will show you how to unlock bootloader, install custom recovery (TWRP) and then install SuperSU thereby giving you root... and this is for T-Mobile only at this time as far as i know
It's what I followed to get root
edit: there is a separate link (same post) for unlocking bootloader... that needs to be done first, then do the TWRP link to install recovery and SuperSU
tymansdaddy said:
There isn't a link on the root section, just a link to the root developers profile. I actually need INSTRUCTIONS not needing to know who's responsible for initially rooting the device.
Click to expand...
Click to collapse
There is a look towards rooting the tmobile v10, under where it states root. The confusion was I forgot to change TWRP to ROOT...it is there now.
Hi,
I'm currently waiting for buy the Xperia XZ. I check some of XDA's thread and with Sony's smartphone I'm still afraid. So I want to know if there is a thread gathering all the detailled step to root, install TWRP, flash latest firmware, install custom ROM etc... ?
Thanks a lot
[Guide] Here is the DHGE guide for rooting SONY devices 2019-04
Changelog at the bottom of this post.
nathan30 said:
if there is a thread gathering all the detailed step to root, install TWRP, flash latest firmware, install custom ROM etc... ?
Click to expand...
Click to collapse
No - but you can find all you need to know here in this forum or in the devices-fora later than Z3+ or SONY-cross-device.
https://forum.xda-developers.com/crossdevice-dev/sony
Good introductory (written for devices before Z3+):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
It is still valid but the 2015 and newer devices are not rootable anymore as described thanks to DM-Verity.
For rooting the current device you have to open the bootloader.
Any claims to the contrary found "on the web" are only tricks to have you install "interesting" software on a Windows PC.
Do you want root?
A classic post to help you decide
No:
wait for the OTA-updates from SONY (over the air - prosaic?)
don't like waiting or want to downgrade: get Flashtool http://www.flashtool.net
it comes with Xperifirm that finds you the latest ROM
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Unfortunately Xperifirm only finds the latest ROM (the only available on SONYs servers) so you better keep your downloads (>2 GBytes each) or find an older ROM in case you need it (xda has a search function). Here you'll find some ROM-versions: https://xpericheck.com
since my Xperia XZ/XZ1 I occasionally have problems with Flashtool that it requires a FSC-script which does not come with it or can not easily be copied from a similar device.
Now I use Newflasher https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426 by @munjeni. This is a command line tool that for me unfortunately only works under Windows (have JDK issues under Debian).
You unpack the ROM (ftf-file) and place the newflasher.exe in the directory where you unpacked to. Then you start the device in flash mode (power on while holding the volume down key) and run the tool from the command line as administrator/root.
If you do not delete userdata.sin you will initiate the equivalent of a factory reset (aka loose all your data and settings!). For an upgrade within the same Andoid version I always delete userdata.sin before newflashing.
Yes:
As stated above, you need to unlock the bootloader to modify the system software on your device. Fortunately SONY gives (for non-carrier-locked) devices the option to unlock the bootloader.
Check if unlocking is allowed: in the service menu (dial *#*#7378423#*#* or *#*#SERVICE#*#* ) check under "Service Info"->"Configuration" the line "Bootloader unlock allowed:"
If you read anything other than "Yes" Stop here!
No: flashing another SONY Rom ("Customized CountryX") does not help you.
Hint: there is an app "SONY service menu" in the app-repository (F-Droid or Google).
OK - you can Now it is your last chance to save your device keys or "backup the trim area partition"
You should do this if you ever want to return to a SONY "blessed" state. e.g claiming service in countries where warranty is not for devices with unlocked bootloader or you want to sell it.
There are some device specific kernels out there whose authors state that they mitigate all DRM issues once the TA is restored. I guess you need these kernels otherwise restoring the TA locks up your device ...
Otherwise do not bother with restoring the TA-partition. Doing so after the next steps will soft brick your device.
Now you have to prepare your PC with some drivers in order to start the backup process:
Go to SONY's developver world http://developer.sonymobile.com
Under "Downloads" you will find the drivers for the XZ or any other device http://developer.sonymobile.com/downloads/drivers/xperia-xz/
These drivers are for Windows, do not bother if you are running a free operating system.
To get fastboot running you might additionally have to find the "fastboot_driver" in the download area. Put the content of the ZIP-file into the directory where you you unzipped the device driver and install it via right-clicking on the file android_winusb.inf.
Install these drivers if you are a Windows user. Under Windows 8 and newer there could be problems with installing "non signed" drivers.
Do a web/xda search to circumvent this security measure of Microsoft or do click on reboot while holding the shift-key and figure it out yourself.
http://www.flashtool.net/win8drivers.php
When you are installing: You also need to install the programs adb and fastboot.
https://forum.xda-developers.com/showthread.php?t=2317790
If you are running a free operating system: search for adb/fastboot or Android SDK in your repository and install these.
Running Linux it helps to insert the udev-rule mentioned in http://www.flashtool.net/lininstall.php otherwise you have to run esp. fastboot with root-privileges (not recommended, although the udev rule saves no punches ...)
On Android on your SONY device you have to be root to save a partition - catch 22 :crying: ...
https://en.wikipedia.org/wiki/Catch-22
Don't fear the ... / catch: For Android Marshmallow ROMs, e.g. up to version 39.0.A.3.30 of the Xperia XZ ROM, exists an exploit of the copy on write function in the Linux kernel that gets you root privileges temporarily.
On newer devices where there is no Marshmallow ROM with a vulnerable kernel available you are out of luck until another exploit is found.
Follow https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Hint: In post #21 is described how to restore the TA (read the last sentence! -> you have to flash a stock ROM after restore).
If it does not work the first time let the tarnished bovine do its stride several times more.
Or: Repeat the process until success.
If you are already on Nougat you must downgrade the system ROM (see above) to use the exploit and backup the TA-partition.
The latest exploit that is available for devices that came out with Oreo uses a different exploit.
Search for this exploit in the specific forum or on "Sony Cross Device". If you are already on Pie you have to download an Oreo ROM for your device.
This is similar to the procedure described above that has the Xperia XZ in mind.
TA-partiton backed up?
Now the non-reversible part:
Under http://developer.sonymobile.com/unlockbootloader/ you request an unlock code.
READ, READ what SONY have written there!
- You will lose some DRM functionality: https://forum.xda-developers.com/z3-compact/general/loss-drm-keys-t2890936
- Your device will factory reset. You have a backup?
You can get the IMEI-number from the original package of your phone (if you have good eye sight and nobody swapped the boxes) or pull a tab from the side of the phone (you do not want to do that) or print a screen shot of the relevant page of your service menu or head into settings->about device->status->IMEI-Info.
You follow SONY's instructions to unlock the bootloader and hold your breath as after a long reboot everything on your device is wiped. On the newer devices you get an ugly warning "the device can't be trusted anymore".
NEVER EVER enable the MyXperia software from now on!
On some devices this in combination with an unlocked bootloader will hard brick your device.
Here was a link to fxpblog where they destroyed two devices.
Hey, you have been warned. With the TA-backup you always can return to the chicken den.
Become a "developer"
- Tap seven times on the build number of your device. (settings->device info)
- then enable "OEM unlocking" (new for the 2016 and later devices like XZ) and "USB-debugging"
You have read the SONY advice?
Next decision: Root stock ROM or go Custom Rom?
I am VERY happy with LineageOS on a Tablet Z and other devices in my household. I liked the Resurrection Remix ROM on my SAMSUNG phone.
Your mileage may vary: Testing a ROM and reversing will cost you with a proper backup minimum 4-5 hours.
If you choose a custom ROM:
- read the thread to get a hunch if you really want to install it (get over the off topic noob questions and annoying full quotes)
- Follow the instructions of the first page of the ROM-thread to install it. If you can not do this: stop or be prepared for searching and learning.
From February 2017 until May 2017 I had eXistenZ N on my Xperia XZ and like the UI tuning modifications. This "ROM" does not come pre-rooted it is a patch for the stock ROM (match the versions exactly!) that enhances the settings/look.
On SONY devices I recommend rooting stock ROMs.
Shortcut: Pie users can proceed to step 7 here
Having a custom kernel might still be advantageous for you.
You need a custom (or modified stock) kernel (aka boot image) with DM-Verity and SONY-RIC OFF.
This kernel has to be in sync with your ROM. Flashing an unsuitable kernel (e.g. MM-kernel on N-Roms) will result in a boot loop aka "soft brick".
You even can bake one yourself (no easy task) if you find/adapt the sources for your device. -> first stop SONY developer world
This is might be easy! THANKS to the efforts of @AndroPlus, @janjan and others.
You have to look into the device specific fora to find a proper kernel for your ROM-version.
They have also included many patches to improve battery life, mitigate some (e.g. camera) issues from the loss of the device keys ...
Download the kernel and recovery for your device and ROM-version and follow the kernel makers' instructions.
On devices where there is no custom kernel, you can try patching the stock kernel to switch off RIC and DM-verity. In reality behind the scenes it is a bit more than just patching (=modifying) the kernel. You also get some updated init-scripts and as a end result a new boot.img
Very useful is [PoC][Work in progress] Trim Area Proof Of Concept developed by @munjeni
These scripts not only prepare a stock kernel for rooting but also put your TA backup from above to such a use that you regain the DRM-features lost by opening the bootloader! So you do not need a custom kernel with partial DRM-fixes!
For Oreo it is more complicated (it might be easier to search for a suitable boot.img aka kernel and I have not tested it on Pie but see next step):
@serajr enhanced a script specifically for Xperia X Performance, XZ and XZs
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
Under Linux I had to set the executable attributes on the shell scripts and binaries (chmod +x).
You get the required kernel.elf via the tools menu in Flashtool. Dump "kernel.sin".
I started applying the scripts to the Stock ROM in May 2017 since eXistenZ ROM lagged a bit behind in security patches and Android version:
- flashed stock ROM via Flashtool or Newflasher
- prepared a patched boot image with PoC and my kernel...sin and TA.img and answered all questions with "yes" (hit return each time)
Code:
./ta_poc kernel.sin TA.img ramdisk
I am on Debian as operating system.
On Windows you just run the provided batch files and follow the instructions here and in the thread for the scripts.
- flashed the resulting boot image with fastboot flash boot boot.img and test it works. Service menu/Security: keys provided YEAH
- flash recovery and from there root with SuperSU and flash Titanium Backup
- restored my apps with their data via Titanium Backup
==============
Some hints:
==============
Most of these commands emit useful info on the command line - read it, post their error messages if you are stuck.
Version numbers of the software used speeds diagnosis of problems. Often a good advice: "Use latest version."
adb reboot bootloader or switching OFF the device and then pressing the "volume up" button while plugging the USB cable gets you into fastboot mode. You see a black screen and the blue LED light.
I normally do not flash the kernel-ZIP-file via recovery but unpack it and flash this: fastboot flash boot boot.img
To get into recovery mode:
Switch OFF your device. Press the "power" button shortly to switch ON and hold "volume down" button more than 5 seconds (or when you see the yellow LED light on some devices).
Or: adb reboot recovery
If you can not get into recovery (e.g. AndroPlus has no kernel for your latest SONY ROM):
fastboot boot TWRP_latest_version.img
I use an SD card (content there survives factory resets) and there a directory "for_recovery" well stocked with the zip-files I intend to flash. In TWRP you can tell the file manager on what storage (internal, SD-card, USB ...) it will find the flashable ZIP-files. The default is "internal".
Pressing the Power button and "volume up" for about five seconds gives you a hard reset.
Good if you are totally struck - just flash a SONY ROM for your device with Flashtool and all the wipe boxes checked or use Newflasher (overwrites most partitions including your data).
If you like to read about the haarrrdddd way:
https://forum.xda-developers.com/z4-tablet/help/enybody-root-t3154926
The first rooting of a DM-Verity secured device in 2015. Thanks to SONY for releasing source code and binaries.
Rooting - aaahh, finally
Flash the latest Magisk (up to late 2017 I used SuperSU which still works) from recovery.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
https://www.chainfire.eu/ Find the latest SuperSU from there. You will not find it there any more since Chainfire has sold the rights to the utility. I endorse Magisk since that is open sourced on GitHub.
No: flashing a custom kernel and recovery does not root your device.
For Android Pie users: On my Xperia XZ1 I can skip step 6 completely!
Just install/upgrade to the latest Pie ROM and flash Magisk and install the Magisk app.
Bonus: Debloat the device
https://forum.xda-developers.com/search/forum/2522?query=debloat
Nowadays I use a debloat script written by @serajr for my devices https://forum.xda-developers.com/xperia-xz2/development/oreo-debloat-script-v1-0-t3798979,.
I edit (comment out) the debloat_list.sh in order to keep "com.google.android.apps.maps" and "com.sonymobile.email" which I both use.
mine (you screened my script?):
flash the attached ZIP-file
View attachment xtrm_debloat.flashable_ew_2016-12.zip
found in https://forum.xda-developers.com/xperia-z5/general/discussion-bloat-sony-xperia-z5-t3518860 probably original work by @ganeshbiyer
=============================================================
With opened bootloader you will not get OTA updates any more!
You have to check with the Xperifirm program if there are newer ROMs for your device.
I have not had any problems with installing e.g. a Swiss ROM over a Central Europe. There could be some worries when switching continents.
Download the desired ROM via Xperifirm and follow the instructions of Flashtool to flash the device (over USB update = OUU :laugh.
Accept the use of the FSC script.
Repeat the steps 5 to 6(7) for any other/newer SONY ROMs you flash followed by step 4 (if necessary).
If a wipe is needed I prefer the full wipe in TWRP compared to checking the boxes in Flashtool.
Or use Newflasher without flashing userdata.sin (just delete the file) in case of an upgrade.
=============================================================
CHANGES to this Guide
2019-04-23 updated for Pie, endorsed Newflasher, added link to serjars debloat script, link ckecks
2018-02-28 clarified getting kernel.elf for self patching, some typos, link ckecks
2018-01-31 link for better suited ta_poc added, toned down AndroPlus endorsement, added Magisk
2017-06-25 added link to xpericheck (find older ROMs), added hint for restoring TA for those TLDR-guys
2017-06-02 added procedure for patching stock kernel as alternative to custom kernels
2017-02-05 added recommendation for eXistenZ N ROM
2017-01-25 new URL for SuperSU, typos
2017-01-18 corrected the advice for booting into TWRP
2017-01-17 added info on fastboot driver for Windows users
DHGE said:
No - but you can find anything here or in the devices-fora later than Z3+ or SONY-cross-device.
https://forum.xda-developers.com/crossdevice-dev/sony
Good introductory (written for devices before Z3+):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
It is still valid but the 2015 and newer devices are not rootable anymore (as described) thanks to DM-Verity.
For rooting the current device you have to open the bootloader.
Any claims to the contrary found "on the web" are only tricks to have you install "interesting" software on a Windows PC.
Do you want root?
No:
wait for the OTA-updates from SONY
don't like waiting or want to downgrade: get flashtool http://www.flashtool.net
it comes with Xperifirm (at least for my linux machines) that finds you the latest ROM
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
Unfortunately it does not find many older ROMs anymore so you better keep your downloads (>2 GBytes each) or find an older ROM in case you need it (xda has a search function).
Yes:
As stated above, you need to unlock the bootloader to modify the system software on your device. Fortunately SONY gives (for non-carrier-locked) devices the option to unlock the bootloader.
Check if unlocking is allowed: in the service menu (dial *#*#7378423#*#* or *#*#SERVICE#*#* ) check under "Service Info"->"Configuration" the line "Bootloader unlock allowed:"
If you read anything other than "Yes" Stop here!
No: flashing another SONY Rom ("Customized CountryX") does not help you.
Hint: there is an app "SONY service menu" in the app-repository (F-Droid or Google).
OK - you can Now it is your last chance to save your device keys or "backup the trim area partition"
You should do this if you ever want to return to a SONY "blessed" state. e.g claiming service in countries where warranty is not for devices with unlocked bootloader or you want to sell it.
Otherwise do not bother with restoring the TA-partition. Doing so after the next steps will soft brick your device.
Go to SONY's developver world http://developer.sonymobile.com
Under drivers you find the drivers for the XZ under "Downloads" http://developer.sonymobile.com/downloads/drivers/xperia-xz/
These drivers are for Windows (which version?), do not bother if you are running a free operating system.
Install these drivers if you are a Windows user. Under Windows 8+ there could be problems with installing "non signed" drivers. Do a web/xda search to circumvent this security measure of Microsoft. http://www.flashtool.net/win8drivers.php
When you are installing: You also need to install the programs adb and fastboot.
https://forum.xda-developers.com/showthread.php?t=2317790
If you are running a free operating system: search for adb/fastboot or Android SDK in your repository and install these.
Running Linux it helps to insert the udev-rule mentioned in http://www.flashtool.net/lininstall.php otherwise you have to run esp. fastboot with root-privileges (not recommended, although the udev rule saves no punches ...)
You have to be root to save a partition - catch 22 :crying: ...
For Android Marshmallow ROMs, precisely up to version 39.0.A.3.30, exists an exploit of the copy on write function in the Linux kernel that gets you root privileges temporarily.
Follow https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
If you are already on Nougat you must downgrade the system ROM (see above) to use the exploit and backup the TA-partition.
TA-partiton backed up?
Now the non-reversible part:
Under http://developer.sonymobile.com/unlockbootloader/ you request an unlock code.
READ, READ what SONY have written there!
- You will lose some DRM functionality: https://forum.xda-developers.com/z3-compact/general/loss-drm-keys-t2890936
- Your device will factory reset. You have a backup?
You can get the IMEI-number from the original package of your phone (if you have good eye sight and nobody swapped the boxes) or pull a tab from the side of the phone (you do not want to do that) or print a screen shot of the relevant page of your service menu or head into settings->about device->status->IMEI-Info.
You follow SONY's instructions to unlock the bootloader and hold your breath as after a long reboot everything on your device is wiped. On the newer devices you get an ugly warning "the device can't be trusted anymore".
Hey, you have been warned. With the TA-backup you always can return to the chicken den.
Become a "developer"
- Tap seven times on the build number of your device. (settings->device info)
- then enable "OEM unlocking" (new for the 2016 devices like XZ) and "USB-debugging"
You have read the SONY advice?
Next decision: Root stock ROM or go Custom Rom?
Well - my opinion - for the newer SONY devices I have not found a recommendable custom ROM yet. I am VERY happy with a generic CyanogenMod on a tablet Z in my household. Do not ask me about the sad story of CyanogenMod as of late 2016...
Your mileage may vary: testing a ROM and reversing will cost you with a proper backup minimum 4-5 hours.
If you choose a custom ROM:
- read the thread to get a hunch if you really want to install it (get over the off topic newbie questions)
- Follow the instructions of the first page of the ROM-thread to install it. If you can not do this stop or be prepared for searching and learning.
On SONY devices I recommend rooting stock ROMs.
You need a custom kernel (aka boot image) with DM-Verity and SONY-RIC OFF.
This kernel has to be in sync with your ROM. Flashing an unsuitable kernel (e.g. MM-kernel on N-Roms) will result in a boot loop aka "soft brck".
You even can bake one yourself (no easy task) if you find/adapt the sources for your device. -> first stop SONY developer world
This is easy! THANKS to @AndroPlus
AndroPlus has also included many patches to improve battery life, mitigate some (e.g. camera) issues from the loss of the device keys ...
https://forum.xda-developers.com/xperia-xz/development/kernel-andropluskernel-v01-t3475240
AndroPlus has kernels for other devices too. Look into the specific device forum for a custom kernel,
Download the kernel and recovery for your device and ROM-version and follow AndroPlus' instructions.
Some hints: (most of these commands emit useful info on the command line - read it, post it if you are stuck)
adb reboot bootloader or switching OFF the device and then pressing the "volume up" button while plugging the USB cable (hooked to your PC! we need DC power for all this) gets you into fastboot mode. You see a black screen and the blue LED light.
I normally unpack the kernel-ZIP-file and flash this: fastboot flash boot boot.img
You get into recovery mode on booting by pressing the "volume up" button when you see the yellow LED light.
If you can not get into recovery (e.g. AndroPlus has no kernel for your latest SONY ROM):
fastboot boot TWRP_latest_version
I use an SD card (content there survives factory resets) and there a directory "for_recovery" well stocked with the zip-files I intend to flash.
Pressing the Power button and "volume up" for about five seconds gives you a hard reset.
If you like to read about the hard way:
https://forum.xda-developers.com/z4-tablet/help/enybody-root-t3154926
The first rooting of a DM-Verity secured device in 2015. Thanks to SONY for releasing source code and binaries.
Rooting - aaahh, finally
Flash the latest SuperSU from recovery.
https://download.chainfire.eu/1019/SuperSU
No: flashing AndroPlus or TWRP does not root your device. You'll have to flash Chainfire's ZIP-file!
Bonus: Debloat the device
https://forum.xda-developers.com/search/forum/2522?query=debloat
mine (you screened my script?):
flash the attached ZIP-file
View attachment 4000189
With opened bootloader you will not get OTA (over the air - prosaic?) updates any more!
You have to check with Xperifirm if there are newer ROMs for your device.
I have not had any problems with installing e.g. a Swiss ROM over a Central Europe. There could be some worries when switching continents.
Download the desired ROM via Xperifirm and follow the instructions of flashtool to flash the device. Accept the use of the FSC script.
Repeat the steps 5 to 6(7) for SONY ROMs followed by step 4 (if necessary).
If a wipe is needed I prefer the full wipe in TWRP compared to checking the boxes in FlashTool.
Click to expand...
Click to collapse
Woaw, thanks a lot for your awesome answer !
I receive my phone today, I'll follow your instructions
@DHGE your guide is well put, and I've not had any problems so far (I used a slightly different version of the Xperia ROM since the version you specified didn't show up, but it worked just fine, is sitting on Android 6.0, and I have the TA backed up).
I've obtained the unlock code from Sony's developer site, but I've still yet to get their email with the instructions on where to shove the code. Its been about two or three hours now, and it was sent to a Gmail address (which has received other mail since). I tried generating a new code to make sure the email was right (it was), and it spat out the same unlock code, so I'm guessing its just based off of the IMEI.
Question is: what does one do with the unlock code? I can't imagine the instructions would be different for each person and am not sure how long it may take Sony to email the Gmail account...
k2trf said:
What does one do with the unlock code?
Click to expand...
Click to collapse
Follow the steps on SONY's website where you obtained the unlock code.
Look at the big link at the right bottom after all the warnings...
Somehow I missed that completely, and just latched onto it saying to wait for the instructions via email. Honestly, I don't even know why they think it necessary. Anyone playing with unlock codes damn sure better be familiar with ADB and fastboot already, or be learning as they go. >_>
Hi,
there something I can do to roll back if I didn't backed up my TA partition?
thanks
bigkekko said:
Hi,
there something I can do to roll back if I didn't backed up my TA partition?
thanks
Click to expand...
Click to collapse
Roll back to recover TA? Unfortunately not.