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.
Return to Contents Page - doubleshot Developers Reference
THESE ARE NOT ROMs. ...and this thread is not aimed at users.
These are the base of what could be a ROM some day if someone wants to make them into such.
Provided as-is with no promise of support or usability ( but you know we're here for that if you need it, and they worked fine on my device )
HTC Software Versions: (March 2012)
1.28.531.9 - Retail Launch
1.55.531.3 - OTA
1.63.531.2 - OTA
--------
Okay, yesterday I tore open the 1.63.531.2 software package and started seeing what I could see.
While I was playing with it I made another round of insecure boot images ( find here )
...one thing led to another and then here I sat with 3 de-odexed system images and corresponding insecure boot.img files I had made, and a sunrise that was surprising because I hadn't realized it had set yet from the day before...
Anyways, I had fun with this project and hopefully having these here will encourage people to start tinkering with their own ROM creations.
These base system.img files are the same system.img files generated when you make a clockworkmod backup - so no goofy headers or signed stuff to worry about, just the image file.
You can unyaffs it like normal to get at the contents of the image.
If you are on windows, avabox is a fantastic set of tools with a full yaffs setup in it, as well as the easiest smali/backsmali process i've found. Top notch tool and one I use frequently when on windows.
I actually did the de-odexing itself with xUltimate - it went ahead and did it all in one automatic batch process for each software version when I got to that part, instead of me manually doing it with avabox or other backsmali tools. (Nice!!)
Even so, it still took most of the night to set up and then process each software version and de-odex it, so i'm providing them here for people to just grab and start working on.
So, to answer that question of "where do I start?" for getting into developing, here is a pretty good place:
HTC 1.63.531.2 Software Version
The new OTA software version that started on the 19th and was paused (again...) on the 20th of march is the 1.63.531.2 software version, our newest.
De-odex system.img 1.63.531.2
doubleshot_1-63-531-2_de-odexed_system.img
Download Link
MD5: 40f11628907899aebe5809808f56f2ae
Size: 697.75 MB
Insecure boot.img 1.63.531.2
doubleshot_1-63-531-2_insecure_boot.img
Download Link
MD5: 1939ec22b1414cb7b4e42f07f1d6b025
Size: 3.36 MB
----
HTC 1.55.531.3 Software Version
De-odex system.img 1.55.531.3
doubleshot_1-55-531-3_de-odexed_system.img
Download Link
MD5: 154a793b92d69970554170832f6efca6
Size: 691.8 MB
Insecure boot.img 1.55.531.3
doubleshot_1-55-531-3_insecure_boot.img
Download Link
MD5: 3e07acc5debd7f9f469d31486aa7c87d
Size: 3.36 MB
----
HTC 1.28.531.9 / .10 Software Version
HTC 1.28.531.10 kernel source
De-odex system.img 1.28.531.9
doubleshot_1-28-531-9_deodexed_system.img
Download Link
MD5: 7a250cc5d6783c9392c826a01beb7b03
Size: 682.62 MB
Insecure boot.img 1.28.531.9
doubleshot_1-28-531-9_insecure_boot.img
Download Link
MD5: b83a232372f6d8e440446f255aaea617
Size: 3.28 MB
----
Other versions of the boot.img found here. Also shows what code was changed to make it insecure.
If you lose the modules needed to make wifi work with the boot image, these are stock boot images and can get those modules from here if they are lost from system:
Stock WiFi Modules
--------
Mirrors welcome, just please make sure to include a link in this thread if you do ( I will copy it to first posting for others reference) and just make sure to link to the thread and not the mirrors direct elsewhere please?
Good places to go next from here would be:
- Edify Script Tutorial - Replacing the Google Market
- Edify Scripting Notes
- Flashable zip template
- doubleshot Developers Reference
...and start to learn how to set up the stuff you make so you can deploy it to a device.
Happy devving!
Blue6IX said:
I actually did the de-odexing itself with xUltimate - it went ahead and did it all in one automatic batch process for each software version when I got to that part, instead of me manually doing it with avabox or other backsmali tools. (Nice!!)
Click to expand...
Click to collapse
This angers me that you got this to work when it didn't work for me at all. Great rage.
Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have is, "Why did you release this - why wouldn't I just use <insert name here>'s stock rom?" It's simple: every other rom in this forum (at this time) has been modified from the original stock rom - whether they've added root, de-odexed it, debloated it, or otherwise. Because the Unadulterated rom is 100% stock (with stock kernel), it is possible for other developers to flash this rom and use it as a platform for attempting to find a root method for the MF3 users out there already. Plus, I like to make my own modifications from a stock base.
UPDATE (8-1-13): a root method has been found for MF3. See thread here. This ROM's purpose has been fulfilled, but your are still welcome to use it, of course!
UPDATE: The MF3 Odin files have been uploaded by @Shockndrop over in his thread here. Remember that the Odin files will flash your bootloader to MF3 (if you allow them), so be careful out there.
Rest assured, this rom will not update your bootloaders, it will not break your custom recovery, and it won't flash your modems. Like most roms, it will simply replace your /system and flash a Kernel. It's also scripted to wipe cache and dalvik for you. It will not wipe your /data partition - you might want to do so if you run into problems, especially when coming from other roms.
Next, you might ask, "How can you say this is 100% stock? How did you construct it?" I'll hide nothing from you - you can build it yourself if you'd like. Here's how I did it:
Rooted with motochopper
Installed TWRP 2.6.0.0
Wiped data & cache
Odin to MDL stock
Allow one full reboot:
Boot script runs (installs CSC - this is REQUIRED for the MF3 update to patch correctly)
Clears up any SysScope flags, etc. that may have persisted from previous rom or root.
"Temporary Root" using motochopper:
Code:
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
adb shell rm /data/local/tmp/pwn
NOTE: Possible outcomes of temporary root:
Failure
Success, motochopper exploit hangs, device spontaneously reboots
Success, immediate return to prompt, but adb shell is still not root (indicated by $ prompt)
Success, immediate return to prompt, adb shell is root (indicated by # prompt)
Repeat as needed (usually only twice or so?)
NOTE: Don't both trying to run su. It isn't installed. We're just relying on motochopper to give us a temporary adb root shell.
From adb root shell, installed TWRP recovery:
Code:
dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
Rebooted, checked to be sure system status is still Official. Note that at this point, we've got a 100% stock MDL rom, without root, but with a custom recovery. Woot.
Rebooted into TWRP, installed custom-neutered OTA update (mf3-sys-only.zip), which only does the following:
Verifies all system files
Removes "unneeded" files (as determined by AT&T, not me)
Patches files
Copies new files
Sets permissions
Patches build.prop
Wiped data & cache for good measure
Booted phone, verified ROM works okay, system status = official. Rebooted, checked Odin Mode:
Code:
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
Booted back to TWRP to begin pulling dumps
... Now, on to the good stuff!
ROM Install Instructions:
Download mf3-stock-rom.zip and place it on your internal sdcard.
Make a nandroid backup of your existing system, data, cache, and anything else you deem important (everything!).
Flash/install the zip using your favorite custom recovery. This part should take several minutes - the file is huge!
Optionally, flash any additional Add-ons that you want (e.g. SuperSU for root)
Optionally, flash a custom kernel (use instructions from the kernel's author!). Note that some custom kernels will need you to flash Loki-Doki. The included kernel does not require Loki patching! It is 100% stock, and your system will accept it as-is.
Optionally, wipe /data. You can skip this, but if you get a ton of force-closes or extreme problems, this would be one of the first troubleshooting steps.
Reboot, and enjoy!
Click to expand...
Click to collapse
Important Recommendation:
You are advised to disable the OTA update applications! If AT&T/Samsung release a new OTA update (beyond MF3), it is theoretically possible to download and install it while using this rom! Accepting such an update could do just as much damage as the original MF3 update did. You can easily disable OTA updates from a root ADB shell using the following commands:
Code:
pm disable com.wssyncmldm
pm disable com.LocalFota
pm disable com.sec.android.fwupgrade
You could also use Titanium Backup Pro to accomplish the same thing. I will later look into the possibility of disabling these using a flashable Add-on zip that otherwise keeps your system as stock as possible.
Known Bugs:
If you do not flash a custom kernel, you will lose WiFi. The WiFi in the MF3 Kernel is expecting the MF3 bootloaders, which we aren't flashing. Therefore it breaks.
If you happen to have the MF3 modem/baseband installed, your WiFi might work, but your sound may stop working completely. This is also a result of not having MF3 bootloaders. A custom Kernel should fix this too.
If you use the "remove-SysScope" Add-on, be careful of any other mods that may poke around with SecSettings.apk - these are rare, but there's some risk of conflict here.
With the custom kernel I installed, I frequently received the "The device has detected an application attempting..." message. This can be pinpointed to the KNOX agent, and can be fixed a different ways (your choice!):
I found this post to be very helpful.
You can also try using the command pm disable com.sec.knox.seandroid from a root ADB shell. This just freezes the app. Personally, I used this method.
@jeboo also mentioned that the KNOXAgent.apk can be patched using smali/baksmali. Check out his post about it.
Also with the kernel I installed, there was a bug regarding updating the camera firmware. I was forced to restore the stock kernel temporarily, open the camera app to update the camera firmware, and then re-flash the custom kernel. The original MF3 kernel is included in the Add-ons.
Any other bugs are likely straight from AT&T/Samsung, otherwise they could be from your custom kernel, if you flashed one.
Be sure to make good backups of everything, and be prepared to use Odin back to stock. One member has reported that after flashing away from this rom to any other rom/kernel, their SIM card would not work until they used Odin to return to stock. After Odin, it worked fine.
It seems most custom kernels are expecting you to have an MDL baseband. Some people are reporting strange issues (such as problems with video streaming) when using MF3 modems and their choice of custom kernels. Check out File #11 for various modems, NON-HLOS modems, and kernels.
Custom Kernels:
Here's a list of custom kernels that are known-working with this rom. Please feel free to test and report other working kernels, and I will gladly add them to the list!
@jeboo's Kernel - built for @shoman94's SHOstock rom. Available in post #3 of their thread.
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me. It appears that the kernels in their thread require Loki-Doki to be flashed after flashing the kernels. However, the one that I downloaded came from here: http://d-h.st/WVs and it was pre-patched for the I337.
@Jamison904's Infamous Kernel works really well, it seems. It also has BusyBox v1.19.3. I'm currently using v4.0, but there are newer versions available on his Dev-Host folder. These are for the M919, so flash Loki-Doki afterwards if you're on I337!
Downloads:
I've provided the rom in several different formats. When I last tested the odin-flashable tarballs, they did not work for me (due to signatures, etc). However, I'm still providing these for a few XDA members who will be testing them out on their semi-bricked devices. Additionally, someone might be able to get these signed somehow, and I'll leave this hanging out there as an invitation.
File #1 - mf3-stock-rom.zip - CWM/TWRP-Flashable ROM .zip file - created by hand (you are welcome to dissect it if you'd like - take a look inside the updater-script)
Files #2-#7 (individual image files and odin-flashables):
File #2 - system.img.ext4 - EXT4 format copy of the System partition - pulled using make_ext4fs in TWRP:
Used fdisk to obtain partition size:
Code:
# fdisk -l /dev/block/mmcblk0p16
Disk /dev/block/mmcblk0p16: 2894 MB, 2894069760 bytes
4 heads, 16 sectors/track, 88320 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p16 doesn't contain a valid partition table
Dumped the partition:
Code:
# make_ext4fs -s -l 2894069760 -a system /sdcard/system.img.ext4 /system
Creating filesystem with parameters:
Size: 2894069760
Block size: 4096
Blocks per group: 32768
Inodes per group: 8032
Inode size: 256
Journal blocks: 11040
Label:
Blocks: 706560
Block groups: 22
Reserved block group size: 175
Created filesystem with 3192/176704 inodes and 584765/706560 blocks
File #3 - system.img - Binary copy of the System Partition - pulled using dd:
This was much easier to create:
Code:
# dd if=/dev/block/mmcblk0p16 of=/sdcard/system.img bs=4096
File #4 - boot.img - Kernel - pulled from the OTA update file
File #5 - mf3-sys-boot.tar.md5 - "Odin-flashable" tarball - created without any modification:
Using a Linux PC or Cygwin, executed the following:
Code:
$ tar -H ustar -c system.img.ext4 boot.img > mf3-sys-boot.tar
$ md5sum -t mf3-sys-boot.tar >> mf3-sys-boot.tar
$ mv mf3-sys-boot.tar mf3-sys-boot.tar.md5
File #6 - mf3-sys-boot-sgs4ext4fs.tar.md5 - "Odin-flashable" tarball - "bloated" with Chainfire's sgs4ext4fs
Using a Linux PC (I used Ubuntu 13.04 64bit - couldn't get the win32 version to process the file entirely):
Code:
$ mv ./sgs4ext4fs.linux.amd64 ./sgs4ext4fs
$ sudo chmod 755 ./sgs4ext4fs
$ mv system.img.ext4 system.img.ext4.orig
$ ./sgs4ext4fs --bloat system.img.ext4.orig system.img.ext4
Optionally, you can use the "--list" option to view the file before and after the bloating. Once complete, pack it up in a tarball again.
File #7 - mf3-factoryfs.tar.md5 - "Odin-flashable" tarball - created using the system.img instead:
Using a Linux PC or Cygwin, executed the following:
Code:
$ mv system.img factoryfs.img
$ tar -H ustar -c factoryfs.img boot.img > mf3-factoryfs.tar
$ md5sum -t mf3-factoryfs.tar >> mf3-factoryfs.tar
$ mv mf3-factoryfs.tar mf3-factoryfs.tar.md5
Files #8-#11 (Add-ons!):
File #8 - UPDATE-SuperSU-v1.41.zip - ROOT! Flash this to root your new MF3 rom!
Original is found on Chainfire's website.
File #9 - remove-SysScope.zip - Want to stay "Official", even though you rooted? Flash this! It will remove SysScope and customize your SecSettings.apk to not check for SysScope anymore. Must be flashed before first boot, otherwise you'll just be stuck with a "custom" status until you remove it by some other means.
File #10 - mf3-kernel-only.zip - Want to quickly flash back to the MF3 stock Kernel again? Flash this. No need to use Loki-Doki after flashing this - the I337 will accept this just fine and boot.
File #11 - all-kernel-modem-apnhlos.zip - My personal collection of flashable .zip's of all available versions of the stock kernel, stock modem, and stock NON-HLOS modem for the I337 - including MDB, MDL, MF3. Unzip this file first, and flash individual partitions/versions in whatever combination you want.
Disclaimers, etc.:
I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other devices, I can't guarantee anything!
You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.
If you appreciate my work, please use the THANKS button below to let me know!
reserved...
First .. ..... Hey guess u got ur phone up and running huh ?
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
as expected...
Aou said:
"I337UCUAMF3 Unadulterated"
This rom is a 100% pure, untouched copy of the System and Kernel that came with the MF3 OTA update. The first question that many will have
.......
[*]I have only tested this with my AT&T Galaxy S4 (I337). While you are welcome to try this with other device, I can't guarantee anything!
[*]You are free to use this ROM, whole or in part, as a base for any other rom, mod, or otherwise. I do not gain profit from this, and the original rom was of course made by AT&T and Samsung. All I'm providing is a way to install it safely and easily. If you do use this rom as a base, please mention my name in your credits/thanks (thank you!).
[*]I cannot be held liable for any damage you do to your own devices due to not following instructions or cataclysmic events beyond my control. Like any other rom, you assume all risks by flashing it to your device.[/list]
If you appreciate my work, please use the THANKS button below to let me know!
Click to expand...
Click to collapse
The result was what was expected.
Keeping my fingers crossed for other solutions...
iB4STiD said:
First .. ..... Hey guess u got ur phone up and running huh ?
Click to expand...
Click to collapse
Nope! Ended up needing to replace it, unfortunately. The original is a 100% hard brick. It won't even take the MF3 firmware via JTAG.
jeboo said:
Nice post man! I still have hope for your recovery process
Here's another way to remove that annoying message without killing the entire APK:
http://forum.xda-developers.com/showthread.php?p=41794748#post41794748
Click to expand...
Click to collapse
Awesome - thanks! I'll add that to the list of options. Also, thanks again for your awesome Kernel. v1.4 is exactly what I need for my phone.
SaltyFoam said:
The result was what was expected.
Keeping my fingers crossed for other solutions...
Click to expand...
Click to collapse
This is really unfortunate, but somewhat expected (as you've said). Have you tried the Odin-flooding again (even with the MDL or MF3 Recovery) yet? That was a very interesting accidental discovery you made. I'm going to have to try that myself too! It might have been a fluke, but still worth investigating.
As an update: The last file (mf3-factoryfs.tar.md5) has finished uploading, so I'm adding the link to the OP now.
FINALLY, someone else that respects untouched firmware. Glad to see this.
The odin flooding is not working at this point.
apparently one of the features of the new odin mode (aboot?) is that once it gets the 'failed auth' it stops responding to further pushes. It does not even allow the connection to be setup until a power down and restart.
As you can see in the other thread I submitted a warranty claim and they are replacing the device: as I have no backup device and a family that needs to get in touch with me (i.e. my wife and mother scolding me for not having a phone) I ran out of time...
I still have a few days with the old device before the replacement arrives...
I any case I am off to work.
If anyone wants to help create a flashable-zip that would disable the OTA updates without touching /system, I'm working on it here:
http://forum.xda-developers.com/showthread.php?t=2379517
I just need someone to write something up in a bash script that will make modifications to a file in /data. Should work without rooting the system.
Jah0n said:
FINALLY, someone else that respects untouched firmware. Glad to see this.
Click to expand...
Click to collapse
One thing I've seen in many "stock" roms is: "Completely stock, except for this.... and this.... and this mod I made here.... and this...."
-_-
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
mocsab said:
I was curious - wanted to see what a true stock would feel like after all this time I have been rooted and using custom roms - anyway -I flashed this - everything seemed to work ok - but after restoring a nandroid - I lost data completely - I tried flashing a new rom and I got an error when trying to set it up saying that I needed to install my SIM - I tried to go into settings to add my APN and that error about the SIM came up again and would not let me add APN.
I could not get data to work on any nandroid or new flash and I ended up using odin to flash back to stock and then re-rooted.
I don't know if it was related to this rom -but it seems to be the only thing that could have caused it - unless you have an idea?
Click to expand...
Click to collapse
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Jah0n said:
We should really team up on something sometime. I just created a hybrid stock UCUAMF3 kernel with the international (i9505) newest XXUBMGA image ROM. I removed the bloat but kept everything that is needed for all the settings to function. It runs so smooth, I'm not sure I want to go back to Google Edition... To release, or not to release. Okay, I'm done rambling. Great work so far from what I see here. Keep em clean!
Click to expand...
Click to collapse
Awesome! If the kernel turns out alright, we could add it to the list in the OP.
Aou said:
It sounds like the other rom you flashed did not have a kernel. Easiest way to check is to open the zip file and check for a "boot.img" - that's the kernel (not the bootloader).
That's strange that your nandroid would not backup Data - did you check that option when you made the backup?
Click to expand...
Click to collapse
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
mocsab said:
The other rom had a kernel, but it doesn't matter because I flashed a different kernel with the other rom - the kernel was not the problem. If it didn't have a kernel, the rom never would have booted in the first place.
The problem is that mobile data did not work - at all. PLUS When I tried to add manually add an APN - it told me that I needed to add my SIM CARD. My SIm Card was fine - I never uninstalled it -
I have flashed and restored hundreds of roms and never had this happen before.
Something happened when I flashed your rom - that wiped out something related to my sim card.
I don't know what that would be - but as a result of flashing this rom - it happened. Just to verify, I redownloaded the rom - flashed it - and the same thing happened the 2nd time.
The phone booted fine and started the setup process - wifi worked fine - but the data bars showed NO DATA. I tried to manually add an APN and I got the same SIM CARD ERROR -so - when I tried to restore a nandroid - I got the same SIM CARD ERROR- I tried flashing a new rom - and got the same error - - the ONLY way I could fix it was to use ODIN and return to stock.
SO - Not sure why I seem to be the only one this has happened to - luck of the draw or something -
Click to expand...
Click to collapse
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Aou said:
Makes a lot more sense now - thought you meant your data partition. >_<
And by another rom not having a kernel, it's still possible for roms to not include a kernel and work - the kernel lies in a separate partition and would remain untouched if the new rom didn't flash this.
I'll add this situation to the bugs list - thank you for the report!
Click to expand...
Click to collapse
The kernel lies in a separate partition but twrp wipes it away by default so you'd have to unmount the boot partition
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Is boot.img a compressed file?
jortex said:
Is boot.img a compressed file?
Click to expand...
Click to collapse
I did not compress it at all. However it is not a full 10MB either. It's the exact file that came from the MF3 update package. The way that the OTA update .zip installs it is by doing this:
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
If you need a full 10MB partition dump (i.e. using dd or a nandroid), I can upload those if you need them for any reason.
UPDATE: I just did a binary comparison of the boot.img that came from the OTA .zip (the one I uploaded), and a nandroid backup I made. It was 100% identical, except the nandroid was padded with zeros at the end (a couple megabytes of zeros...)
Added another kernel to the list:
@Jamison904's Bioshock Kernel - available on the Infamous Development Website. This kernel is working great for me - no issues to report at this time. It also includes BusyBox v1.19.3, which was particularly useful for me.
Hi
Here is the way i used to flash the firmware, i advise to backup all your data before the flash.
All the files here are provided without any waranty.
Flash at your own risks.
Remember that go back to 4.3 is impossible after this procedure.
You may too void your knox counter when you attempt to root your device...
Click the pictures to open the root of the Mirror and find others goodies.
- Flash The Firmware :
First: Set the reactivation lock setting of your phone to OFF.
Be sure the battery of the phone is full.
- Uninstall Kies if you have it on your computer to avoid conflicts.
- Download PC Odin and Install / update the drivers from Samsung[/URL], that's all you need.
- Best and safe way is to use the original stock usb3 cable and make the job on a portable computer with his own power supply (battery connected).
1 - Download the latest repacked rom in this folder and extract it.
This is pure stock rom with only Multi-CSC OXXEND2 added.
Currently, this rom contain 19 Country Codes:
BGL, CYO, ERO, MSR, ORX, PHE, ROM, SEB, SEE, SIO, TEB, TOP, TPH, TRA, TSR, TWO, XEF, XEH, XSK
As it have a small sized hidden partition there is no need of any PIT File. More safe in my opinion.
If you need another CSC, maybe one of then is yours:
The Multi-CSC VFGENA4, 19 Country Codes:
ATL, CNX, CYV, MOB, MTL, OMN, PRO, SIM, SWC, TCL, TOP, VD2, VDC, VDF, VDH, VDI, VGR, VOD, XFV
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OLBEND1, 10 Country Codes:
GLB, MM1, SIN, SMA, STH, THL, XME, XSP, XTC, XTE (Asia)
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OXAEND1, 5 Country Codes:
BTU, DBT, ITV, XEF, XEO
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OJVENB2, 3 Country Codes:
KSA, XFM, XSI
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ITVEND1, 1 Country Code:
ITV (Italy)
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ZZHENE3, 1 Country Code:
TGY (Hong Kong) - The attached modem ZHUENE2 is here.
As it have a small sized hidden partition there is no need of any PIT File.
The CSC VNZDMJ4, 1 Country Code:
VNZ (New Zealand)
The csc parts are from 4.3 rom but are confirmed working fine.
As it have a small sized hidden partition there is no need of any PIT File.
Three others CSC for specifics operators in France.
As they have a small sized hidden partition there is no need of any PIT File.
Check at the bottom of this post for French thread.
Just grab the one you want and put it in CSC in PC ODIN during the same flash process and it first flash the CSC inclued in the firmware, and then overwrite the CSC with the one you added.
2 - Download CF Auto Root for KitKat from Chainfire ODIN version.
Extract the tar.md5 file inside the zip to use with pc odin.
3 - Download the custom recovery PhilZ Touch ODIN version.
I advise to apply this unlock procedure before anything to avoid flash errors:
-> You need Triangle Away from Chainfire with a root acces granted.
Free version is avaible but consider to support the dev for his great job...
a/ Install the app on your phone.
b/ Run Triangle Away and Reset Flash Counter - Follow exactly what the program ask.
At the time to choose the way to reboot after the reset is done in recovery, choose reboot in download mode and then start the flash process immediatly.
4 - In download mode flash the file that you had previously downloaded N9005-hlte_PDA-xxxxxxx_CSC-xxxxxxx_MODEMS-xxxxxxx_REPACK.tar.md5 with PC Odin in AP.
Do not forget to check/enable the Phone Bootloader Update option in pc odin. (seems working nevertheless without this option ticked)
Leave all others one by default.
Make sure re-partition is NOT ticked.
If you have an error (size error - Your phone may mismatch with this rom, another Samsung lock...) as odin fail at the end of the flash process.
- Shutdown the phone, disconnect the battery, disconnect the phone from your computer and wait a minute, return to download mode.
- Download and flash the file wich contain the CSC that you want.
5 - Auto self-reboot, let the stock recovery do his work completly (the green android man).
If you don't want to install root and a custom recovery, you can stop here.
6 - Go back download mode, flash the PhilZ Touch recovery with pc odin in AP.
7 - Again, in download flash, CF Auto Root with pc odin in AP, let the installation process terminate.
Note: If you were previously rooted, jump this step and download, If not yet done, SuperSu to update by flashing the file in custom recovery..
In this case, re-flash CF Auto Root will loose all your settings of SuperSu...
8 - Download the fix for the ExtSdCard issue and flash it in custom recovery.
This is a Google security restriction, unnecessary to wait for a fix from Google, just from developpers of apps. Quick way is to apply this fix.
9 - Don't forget BusyBox which should be usefull too.
- About Mobile Odin :
As Mobile Odin seems to be unable to update the bootloader, don't use this one to avoid brick issues when operate with a different rom version than you have.
If you are already on the same firmware, you can use Mobile Odin to re-flash the rom or any other single part:
- Copy the file on your phone.
- Open this file in Mobile Odin.
- Enable EverRoot and Inject Superuser (SuperSu) in case of a system flashing.
- Choose to reboot in Recovery when you flash System and Cache partitions. If not, you may have problems regarding the CSC.
- Start Flashing.
- Do not skip md5 check to gain a little time. (For the life of your phone...)
- Issues :
All theses solutions were tested by me and worked for me, but without any other warranty.
The CSC region code or version are invisibles, the CSC folder is missing in system/.
The stock samsung keyboard crash often once booted.
You need another CSC (warning, you wil loose all your datas and settings, change for another CSC perform a wipe of the phone)
- Check here for the file you need, download and extract it.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_CSC_xxxxxxx_RECOVERY-xxxxxxx_REPACK.tar.md5 with pc odin in CSC.
The Modem is not updated.
Download and extract the .tar.md5 modem file.
-> Apply the Unlock Procedure.
- Flash the file that you had previously downloaded N9005-hlte_MODEMS_xxxxxxx_REPACK.tar.md5 with pc odin in CP.
- Reboot normally.
The Bootloader is not updated.
You can check by using this app.
-> Download and extract the .tar.md5 bootloader file.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_BL_xxxxxxx_REPACK.tar.md5 with pc odin in BL and check/enable the Phone Bootloader Update option.
- Reboot normally.
Flash player doesn't work anymore.
-> Install Firefox last up to date version and the original latest apk from adobe, nothing else to do.
-> If you prefer Dolphin, download the special version of adobe flash player, more here.
Maybe someone make an xposed module later, it should be a dream...
This fix seems working with this rom (bootloop efs corrupted related).
Not personally affected, just tested the flash.
Download here too.
After all this procedure, you should be fine, upgraded and with all yours datas and settings...
At this state, i just made a wipe of the cache and dalvik cache with phil'z recovery.
- Tune :
- Enable Init.d Support.
- To simply restore the sound at the (de)connection of the charger, you can install this app.
- If you want an imaged battery, you can use RECOVERY - SystemUI N9005 xxxxxxx MOD tkari4-Version by tkari4 based on the guide from parkhyb.
Basically revert to the old 4.3 style for battery and network icons.
{
"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"
}
Just Flash the mod with any custom recovery.
To revert back to the original situation, just flash in custom recovery the file RECOVERY - SystemUI xxxxxxx ODEX STOCK. (STOCK ODEX version)
You can use my blue battery mod. (I reworked a little the graphics for a better scale.) Just extract the .rar archive and install normally the apk Inside, you need too a working Xposed Framework installed.
You can find other Xposed compatibles battery Mods here.
Just reboot once installed.
Many Thanks to tkari4 for keeping alive his mod. :good:
- The repacks i made still works fine.
The rom repacks are made by me with this tool.
Many thanks and credits to all the persons who made this possible.
Notes:
As i do not have the time to download/extract all the roms, if someone needs another CSC repack for him or just to share, please post here with a link for the extracted CSC files only (cache.img.ext4 - hidden.img.ext4) related and with all the details (region, full code name, original rom it come from ... )
To unpack a .tar.md5 file, simply rename it as .tar and extract the content with any good archive software.
I will centralize here.
All others requests in any another form will be ignored, thanks for understanding.
To keep as simply and clear as possible, i will maintain on the Mirror and on thread only the latest updated rom, so if you put elsewhere any link from here, it may be broken in the time, the only ones which would be permanent is the one of the folder and the one of this thread. If you Mirror any file, thanks to keep credits.
Keep a local copy of the downloaded files if you think you will need then later as the content should be updated here.
I maintain the updates only for multi-csc repacks and keep others ones in the mirror, if you need one of theses mono-csc wich is not updated with the latest recovery avaible, simply ask here...
French users, clone thread is here.
Just press thanks if i helped.
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
polish_pat said:
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
Click to expand...
Click to collapse
Yes, every day i do.
And i saw no thread that talk about merging two différents roms to make a new one for a specific country, centralize all the majors tools with direct download links for correct versions to avoid confusions between JB & KK, that i often saw, and attached xda threads, and too provide others files needed at the same place for my device (n9005)
Maybe i had read the forum more often than you think...
Sincerly.
Perhaps you should look again
http://forum.xda-developers.com/showthread.php?t=2617932
http://forum.xda-developers.com/showthread.php?t=2631395
http://forum.xda-developers.com/showthread.php?t=2614787
http://forum.xda-developers.com/showthread.php?t=2618633
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
I made also my Rom N9005XXUENA7_OXXENA5_XXUENA2_ NoBootloader whit this TOOL from A.S._id Dev. Thanks @A.S._id
Only this files:
boot.img
cache.img.ext4 -->from NA6 (OXX)
hidden.img.ext4 -->from NA6 (OXX)
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4
Whitout Bootloader (5 files). Work well whit BL XXUENA6 and no Knox appl's.
At first boot, after enter whit my language, I have my csc TPH automatic, alright.
It's very good this [TOOL] TAR.MD5 PACKAGER and easy to make changes whit.
Anyway, thanks by Your work.
Best Regards
Valente
=======================================================================================
polish_pat said:
Did you search the forum before posting?
Click to expand...
Click to collapse
polish_pat said:
Perhaps you should look again
Click to expand...
Click to collapse
Hi Dear @polish_pat
Please, we have a MODERATION to see all Member's work. Not censure this Member. He have rights like You.
Thank You
polish_pat said:
Perhaps you should look again
....................
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
Click to expand...
Click to collapse
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Le [email protected] said:
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Click to expand...
Click to collapse
i made a thread a month ago, when it was relevant and nobody else did it.
Le [email protected] said:
Hi,
Set the reactivation lock setting of your phone to OFF.:
Click to expand...
Click to collapse
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
johnvicencio said:
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
Click to expand...
Click to collapse
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Le [email protected] said:
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Click to expand...
Click to collapse
I see thank you. That doesn't exist on T-Mobile USA at least not on 4.3.
1 - Download the official Poland rom...
2 - Download any NA7 rom...
To this step's We have here a MIRROR on MEGA Host.
Updated the op with a link to the repacked rom and refreshed the guide.
So it is more easy and simple, i think.
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Pierre118 said:
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Click to expand...
Click to collapse
Op Updated
No need to repack the whole firmware as all which is needed is Inside.
I am currently upload the rom to mirror it ...
Just made a new repack for the multi-csc.
Just flashed over the NA7 rom by following my guide and all went fine.
No full wipes.
Just made a wipe in dalvik cache and cache in recovery once done.
Great and complete Guide. Useful this ALL IN ONE PLACE. Bookmarked.
Thanks
I QUOTE from my THREAD next useful posts by @letama and @Le [email protected]
After this question to a member that not managed to flash the Bootloader NB3:
ValenteL said:
What Rom have You installed? If You have flashed the XXUENB3 why You are in NA6 BL?
Click to expand...
Click to collapse
letama said:
There is a catch in going from NA6 to NB3, it seems bootloader flashing is ignored now in NA6 BL if your rom status is custom. Solution is triangle away, reflash na6 stock, then make sure that you status is official before flashing NB3.
Click to expand...
Click to collapse
Le [email protected] said:
I was on NA7 BL previously flashed over NA6 BL without any problem.
Followed your trick and flashed my own made NB3 flashable file.
I did not any reflash, just reseted with triangle away.
And it worked, i am now on NB3 BL.
Updated my thread too..
Thanks.
Click to expand...
Click to collapse
letama said:
Thanks, good to know that reflashing pure stock is not mandatory, so the bootloader checks custom status flag only and not the whole firmware. Great, will save time for next one .
Click to expand...
Click to collapse
Updated the OP with a new version of Flash Player i found on xda wich work with Firefox too now.
Hi @Le [email protected]
Only for this time: Do not forget to check/enable the Phone Bootloader Update option in pc odin.
I don't understand why, if we flash a complete Rom whit a new bootloader. We not update the bootloader installed. Why You have this opinion now?
Thank You
Hi ValenteL
I saw (here or on other frenchs forums, no links to provide, forgot then) twice posts of somes personnes who don't have checked the option and have updated their bootloader and others one who don't had bootloader update and got soft brick issues as the rest was updated (JellyBean to Kitkat essentially)
It is usually advised here to check this option.
I not personnally took the risk to bypass this option in pc odin and always used it, so i can not confirm if it is important, effective or not.
There is this option in pc odin, i think too this is not for nothing at all.
For all this reasons, i prefer advise to enable this option when flashing a new rom, and it cost nothing to do.
Personnaly, i think it is important to do when using multi-files roms as the first Poland Leaked KitKat, but the bootloader update must be done automatically when flashing a single file rom which contain Inside all the needed parts.
Of course we can have problems when the knox is trigerred or the status of the rom is to custom, then somes parts seems to be 'jumped' when flashing. I feel this fact is increasing in the time.
When i bought my note 3, Under JellyBean, in France, i updated the rom with the latest version of JellyBean avaible on sam mobile for my country (XEF) and had no issue after the flash.
I got problem when i starded to flashed KitKat from others countries as the XEF one is not yet avaible and as i am a little an impatient flash-addict.
I wonder sometimes if i could have all this problems if were more patient and waiting for an upated version for my country.
At this time i identified three parts wich seems locked (not a secret).
CSC -> Ok, Samsung do not want i flash from another country, new policy from Samsung to lock by geographics sectors.
Modem -> Ok, region lock again.
Bootloader -> Why ? Does samsung want to block customs rom such CM, roots and others sames things? And knox related certainly too.
Samsung want to control and limit me a lot, to make more money with me.
Me, i want to be able to do ALL what i want with the device i bought, this is mine, as i can do with my Note 1.
There is a lot of chances that samsung never see again my money...
Time to bed here.
Sincerly
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
---------- Post added at 09:22 PM ---------- Previous post was at 08:36 PM ----------
Pierre118 said:
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
Click to expand...
Click to collapse
Never mind, Mega had a problem. Download is ok now.
I want to avoid configuring the system from scratch and thus need to recover the official boot image for PPIS29.65-51-5 for the European version (reteu), which has been available since few days ago.
Does anyone know where to find it?
Stockrom[1] only has the Brazilian version (retbr) and lolinet[2] only has versions up to PPIS29.65-51-3. The Telegram Moto Updates Tracker[3] shows the update, but the download does not work and the older MotoOTA script[4] does not work neither (or I am entering incorrect information) and the newer MotoOTA script[5] needs the build guid, which I do not seem to be able to get from fastboot or TWRP.
If you have a matching model and version, could you please get the boot image[6] and put it somewhere?
[1]: stockrom.net/2020/06/xt2019-2-retbr-9pie-ppis29-65-51-5.html
[2]: mirrors.lolinet.com/firmware/moto/doha/official/RETEU/
[3]: t.me/s/motoupdatestracker?q=%23doha+Retail+Euro+PPIS29.65-51-5
[4]: motoota.lolinet.com
[5]: motoota.lolinet.com/guid.php
[6]: android.stackexchange.com/a/190102
Update
I learned that the former most recent version [7] can be used to find out the guid inside of oem.img inside of that zip file:
ro.mot.build.guid=7d7b4268f01b080
Using that information [5] can be used to download Motorola's OTA zip file. However, that zip file seems to be some kind of patch format (only 72 MB instead of the typical 1.9 GB) not including a (complete) boot.img. As I do not know the file format, I can't patch the new boot.img myself.
[7]: mirrors.lolinet.com/firmware/moto/doha/official/RETEU/XT2019-1_DOHA_RETEU_9.0_PPIS29.65-51-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip