Related
[SIZE=+3]Consolidated HTC RUU, Leak, and OTA Downloads[/SIZE]
[SIZE=+2]Here we have in one place links to (almost) every HTC Eris RUU Installer, OTA, and PB00IMG.ZIP downloads.[/SIZE] (You can also find some archaic stuff at shipped-roms.com)
The Eris is getting long in the tooth - grab copies for your personal archive. Mostly this stuff is useful only if you have needs for older components (bootloaders, radios, etc) or need to assist someone with a Cupcake (1.5) phone.
Note that the "rom.zip" (== PB00IMG.ZIP) files from MR1 and MR2 are made available for folks desiring easy access to Cupcake (1.5) components - e.g. the 1.47.0000 S-ON bootloader.
[SIZE=+1]Last Revised: 2011-03-04 (March 2011 OTA) [/SIZE]
[SIZE=+1]Eris HTC/VZW/Leak Historical Timeline:[/SIZE]
Code:
[B] # Date Remark Software #[/B]
01 2009-11-06 Eris Drop Day [B][COLOR=blue][ 1.12.605.1 ][/COLOR][/B]
02 2009-12-09 1st Eris [B][COLOR=green]OTA[/COLOR][/B] (equiv to MR1 [B][COLOR=orange]RUU[/COLOR][/B]) [B][COLOR=blue][ 1.16.605.1 ][/COLOR][/B]
03 2009-12-10 MR1 [B][COLOR=orange]RUU[/COLOR][/B] Available on PCD [B][COLOR=blue][ 1.16.605.1 ][/COLOR][/B]
04 2010-01-07 MR2 [B][COLOR=orange]RUU[/COLOR][/B] Available on PCD [B][COLOR=blue][ 1.17.605.1 ][/COLOR][/B]
05 2010-01-08 2nd Eris [B][COLOR=green]OTA[/COLOR][/B] (equiv to MR2 [B][COLOR=orange]RUU[/COLOR][/B]) [B][COLOR=blue][ 1.17.605.1 ][/COLOR][/B]
06 2010-03-03 HTC "Leak-V1" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.26.605.2 ][/COLOR][/B]
07 2010-03-14 HTC "Root" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.19.605.1 ][/COLOR][/B]*
08 2010-03-23 HTC "Leak-V2" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.26.605.4 ][/COLOR][/B]
09 2010-04-29 HTC "Leak-V3" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.36.605.1 ][/COLOR][/B]
10 2010-05-11 3rd Eris [B][COLOR=green]OTA[/COLOR][/B] (1.5 -> 2.1 upgrade) [B][COLOR=blue][ 2.36.605.1 ][/COLOR][/B]
11 2010-06-05 MR3 [B][COLOR=orange]RUU[/COLOR][/B] leaked [B][COLOR=blue][ 2.36.605.1 ][/COLOR][/B]
12 2010-07-15 4th Eris [B][COLOR=green]OTA[/COLOR][/B] [B][COLOR=blue][ 2.37.605.4 ][/COLOR][/B]
12b 2010-07-?? 4th Eris [B][COLOR=green]OTA[/COLOR][/B] (1.5 -> 2.1 upgrade) [B][COLOR=blue][ 2.37.605.4 ][/COLOR][/B]
13 2011-03-02 5th Eris [B][COLOR=green]OTA[/COLOR][/B] [B][COLOR=blue][ 2.41.605.6 ][/COLOR][/B]
* Note that even though the "Root ROM" was leaked chronologically later, it is a much older version of Android 2.1 than any of the "Leak" ROMs.
[SIZE=+1]2/13/2012 - NOTE: All file have been re-hosted to shipped-roms.com. <<==== Please use this link to find your download. Check the file name carefully, and verify the MD5 signature after you download.[/SIZE]
[SIZE=+3]Software Releases (by version) ==========================[/SIZE]
[ 1.16.605.1 ] a.k.a. "MR1" - (Cupcake/1.5)
RUU: RUU_Desire_C_Verizon_WWE_1.16.605.1.release_signed_with_driver.exe
119,334,520 bytes; MD5 signature: 3bafe8b5231e8a75f32256f2abaacda1
PB00IMG.ZIP: Eris_MR1_v1.16.605.1_PB00IMG.ZIP
102,346,348 bytes; MD5 signature: db04a87fb1084744a1c5d08148ecb631
OTA: not captured (to my knowledge)
[ 1.17.605.1 ] a.k.a. "MR2" - (Cupcake/1.5)
RUU: RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed_with_driver.exe
119,320,610 bytes; MD5 signature: 8b10da4a49f762584d806ac398368d39
PB00IMG.ZIP: Eris_MR2_v1.17.605.1_PB00IMG.ZIP
102,328,473 bytes; MD5 signature: 9e9ad31f01bbcb05157443287f4f38dd
OTA: see item #05 below in OTA section
[ 2.19.605.1 ] a.k.a. "Root ROM" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip
107,427,740 bytes; MD5 signature: 63eacc5ede3b179f95dc22d8ef585f94
OTA: n/a
[ 2.26.605.2 ] a.k.a. "Leak-V1" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_LeakV1_v2.26.605.2_PB00IMG.ZIP
108,854,573 bytes; MD5 signature: bd6b08d32948022c865c79dcc61ae449
OTA: n/a
[ 2.26.605.4 ] a.k.a. "Leak-V2" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_LeakV2_v2.26.605.4_PB00IMG.ZIP
108,819,939 bytes; MD5 signature: 6e3a2bb96432276b0af51ba6e7e1820c
OTA: n/a
[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU) - (Eclair/2.1)
RUU: RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
130,323,038 bytes; MD5 signature: 74035b1685b279b1aa4f17fafdbec78b
PB00IMG.ZIP: Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
109,946,224 bytes; MD5 signature: 1c0b0182356242a9d673a661e7458587
OTA: see item #10 below in OTA section
[ 2.37.605.4 ] "4th OTA" - July 2010 - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: n/a
OTA: see items #12 and #12b below in OTA section
[ 2.41.605.6 ] "5th OTA" - March 2011 - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: n/a
OTA: see item #13 below in OTA section
[SIZE=+3]OTAs =====================[/SIZE]
OTA files may be renamed to "update.zip", placed on the SD card root folder, and then applied to phones with older stock software using the recovery boot. Note that all Eris OTAs were NOT FULL UPGRADES, BUT RATHER PATCH UPGRADES - afaik, they will only work correctly when applied to a very specific HTC software version already on the phone; including the "stock" recovery boot** for that software version. They will not work correctly with Amon_RA or Clockwork recovery.
Note there was a period of time when Google's servers were hosting two separate "July 2010 (2.37.605.4)" OTA upgrades: one of them upgraded existing 2.1 handsets @ v2.36.605.1, and the other upgraded existing Cupcake 1.5 handsets @ 1.17.605.1. Please read carefully.
#02 [ Converts 1.??.???.? -> 1.16.605.1 ] - 1st Eris OTA
Not captured
#05 [ Converts 1.16.605.1 -> 1.17.605.1 ] - 2nd Eris OTA
desirec-ota-104882.7b1e5cca.zip
4,820,882 bytes; MD5 signature: f6bd240c726874e3922767979ecc6b32
#10 [ Converts 1.17.605.1 -> 2.36.605.1 ] - 3rd Eris OTA
OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip
81,504,835 bytes ; MD5 signature: 9a3a82e4b5afb4e885b41d28085b9adc
OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip[/URL]
#12 [ Converts 2.36.605.1 -> 2.37.605.4 ] - 4th Eris OTA
OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
13,437,426 bytes; MD5 signature: 6c509776a039149c392940025a13cff9
#12b [ Converts 1.17.605.1 -> 2.37.605.4 ] - (if you were stuck on 1.5, 3rd OTA)
06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip
79,318,831 bytes ; MD5 signature: d480a50f3fc450d7bc13cb277820c688
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
14,011,520 bytes ; MD5 signature: 503008da4ff106e95efb5700382bce49
** In the Cupcake (1.5) releases, you get past the stock recovery splash screen by pressing the Home (softkey) and End button simultaneously; in the Eclair (2.1) releases, get past the stock recovery boot splash screen by pressing Vol-Up and End simultaneously (a 2nd time if you powered up a 1.49.xxxx bootloader phone with the same sequence).
I performed MD5 checksums against all of these, and cross-checked prior references to insure everything is correct; if you find any reproducible discrepancies or MD5 mismatches when downloading please notify me via this thread.
bftb0
Revision History:
2011-01-13 added detail about key sequences for stock recovery menu access
2011-03-04 added March 2011 OTA
2012-02-13 re-hosted all files to shipped-roms.com
reserved for later use (i hope not, though).
This is great, thanks.
Thanks for taking the time to document all of this!
Awesome. I have a friend with a rooted Eris, upgrading to the Moto Droid. I have a HTC Incredible. If the process is similar I should be able to flash "Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP" by renaming it to "PB00IMG.ZIP" through the bootloader right? And then be able to apply the other ota's by naming them "Update.zip" through the stock recovery?
First the "OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip" and then "ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip".
Hopefully I'm on the right track.
I've run RUU's on my Incredible via PB31IMG.zip through hboot, and I assume the process is the same on the Eris.
BrettApple said:
Awesome. I have a friend with a rooted Eris, upgrading to the Moto Droid. I have a HTC Incredible. If the process is similar I should be able to flash "Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP" by renaming it to "PB00IMG.ZIP" through the bootloader right? And then be able to apply the other ota's by naming them "Update.zip" through the stock recovery?
First the "OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip" and then "ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip".
Hopefully I'm on the right track.
I've run RUU's on my Incredible via PB31IMG.zip through hboot, and I assume the process is the same on the Eris.
Click to expand...
Click to collapse
I infer that you are intending to return an Eris to stock condition. If so, the process you describe will work. Also, you could use the FlashBack21_v2 ROM to achieve the same thing in one pass. The primary difference between the two methods is that the former flashes the bootloader, whereas the latter leaves it unmolested.
cheers
Hopefully someone can help - In the wake of MultiUpload's voluntary shutdown, I cannot seem to find the OTA files listed above ANYWHERE. My wife recently bought a used Eris and set it up just the way she likes it, AND THEN we saw that it was still running Android 1.5. I want to get her upgraded without losing her existing configuration so I'm hoping to apply each of the OTAs in order to migrate her to 2.1.
Does anybody know of another location for these OTA downloads, or would be willing to share with me directly? Google, ISOHunt and Usenet have failed me miserably. Thanks.
If its not too late, tied to multiuploads were deposifiles.com , wupload.com and others. Now its shutdown here in the U.S but not intl, so when I went to my multiupload account all these mirrors were showing at the bottom listed. All I did was redirect from original host(MPLD) to depositfls.com, links are different but files are the same.
To do this only the account holder would be able too, I did it for my channel and 100's of files that I had but had to be done 1 after another.
Today I can't even open multiupload from chrome, good thing got it out when we did.
Sent from my PC36100 using xda premium
Yeah, I tried using a non-US VPN tunnel to circumvent any blocks and searched via various non-US search engines, and still no luck.
http://shipped-roms.com/index.php?category=android&model=Desire
Have fun
Those are the RUUs, which would wipe out my wife's configurations. I need the OTAs. Thanks though.
dtrammell said:
Those are the RUUs, which would wipe out my wife's configurations. I need the OTAs. Thanks though.
Click to expand...
Click to collapse
Saw this just now. It's late, and I haven't been keeping up with the whole mega/multi-upload drama.
Who wants to host the files? I'm not too interested in saving a single phone from a wipe and reconfiguration ... but if I thought the files would have a more stable home for a while (something open to the public), that's a different matter.
(Or, suggest an alternative to multiupload/depositfiles/ etc)
Let me know (here) if you can't send a PM.
bftb0
bftb0 said:
Who wants to host the files? I'm not too interested in saving a single phone from a wipe and reconfiguration ... but if I thought the files would have a more stable home for a while (something open to the public), that's a different matter.
Click to expand...
Click to collapse
How big are the files? If less than a gig I'd be willing to host them in my dropbox public folder and provide the direct links here.
dtrammell said:
How big are the files? If less than a gig I'd be willing to host them in my dropbox public folder and provide the direct links here.
Click to expand...
Click to collapse
Just the files listed in the OP are about 1.1 GB.
I have to find something similar for the FlashBack ROMs and a few utilities, so I'm poking around and PM'ing to see if I can find someone willing to host 2 GB of files. (I'd like to put all this re-hosting stuff to bed in one go.) Also, I'm trying submissions to shipped-roms.com - we'll see if that works.
Send me a PM with an e-mail address that can accept 100+ MB files. Also, please state which cupcake version the phone is on - 1.17.605.1? 1.16.605.1? Earlier?
bftb0
@dtrammell
update - have a look again in
http://www.shipped-roms.com/index.php?category=android&model=Desire
IF you are on the 1.17.605.1 release of Cupcake, your upgrade to the last factory release is
first
06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip
and second
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
(If you are on 1.16.605.1, you need to do this three times, starting first with "desirec-ota-104882.7b1e5cca.zip").
The way this is done is to rename each (in turn) to "update.zip" on the root folder of your SD card**, boot the phone into the factory recovery <2e> menu, and choose the "update.zip" menu item. Note that the key sequences for getting past the (factory) recovery splash screen differ depending on the which version of the recovery is on the phone - read the details in the OP, as you will find this key sequence to change between the first and second application of this method.
** as always, please verify MD5 signatures of the file after it has been transferred to your SD card. scary alien's "AFV" (Android File Verifier) app may be used for this if you like.
bftb0
DISCLAIMER: For anybody else who is reading this, using the stock recovery boot to perform upgrades via the OTA files only works for exact, specific versions of HTC FACTORY ROMs. Do not attempt with custom dev ROMs, or even the wrong initial version of HTC factory ROMs. The OTAs are PATCH KITS which only work on specific factory HTC ROMs - they are not "full ROM" upgrades.
Get a minus.com account. You'll get 50gb free. When you make your account add me and we both get 10gb free.
Sent from my Sabotaged Droid Incredible 2.
bftb0 said:
@dtrammell
update - have a look again in
http://www.shipped-roms.com/index.php?category=android&model=Desire
Click to expand...
Click to collapse
That's awesome, thanks a ton! I'll get downloading right now.
DISCLAIMER: You will be flashing your phone at your own risk. You are solely responsible for anything you do to your phone, so make sure you are well informed and well prepared before deciding to flash or install anything on your device.
The purpose of this thread is to provide a 'reference site' for anything related to ROMs and kernels, be it original stock, modified stock or custom images for the Samsung Galaxy S III Japanese versions, starting with model SC-03E.
All comments and feedback are welcome and appreciated.
Reminders:
After flashing a new ROM image, it is highly recommended to perform a cache wipe and factory reset. Please avoid posting about problems repeatedly which can be easily solved by this procedure.
If you find that someone has been helpful in assisting you, then please do not shy away from hitting the THANKS button below their post; this is the preferred action instead of creating a new post just to show your gratitude
BEFORE ASKING HOW TO DO SOMETHING, READ THIS GUIDE
Some questions are being asked over and over again in this thread without bothering to read through it or looking for the answer here in the OP. Especially for the 'lazy' ones among us, we'll attempt to make a new and fresh, additional, reference pointer right here at the top of the very first post. Please consider taking a look at @lparryU's guide BEFORE posting your next question.
"How-to: Root, Unlock, Enable Osaifu Keitai/Felica, CWM, cook & flash custom ROM for SC-03E"
PIT File
Use this PIT file when flashing with Odin, and ONLY if you have scr*wed up your default partitioning scheme due to specifying an incorrect one during a previous flash. Normally there is NO NEED to specify a PIT file when flashing with Odin!
m3.pit (SC-03E)
Factory Firmware (stock)
samsung-updates.com and www.sammobile.com host some of the stock images.
Due to hotfile.com's demise, and my limited storage and bandwidth resources in my mediafire subscription, stock images will be available on demand only. Sorry for the inconvenience.
Pre Rooted stock ROMs
(Flashing the following ROM components will trigger the custom binary counter)
All the rooters contain a sample debloat script as well. it is located in the file /preload/Proxyme/debloat.sample. If your /sdcard already has an older debloat script in /sdcard/Proxyme/debloat.sh, it will not be overwritten by the rooter (in case you made changes to it for an older rom). So to be sure of using the most recent script for the targeted version of the firmware check the version in the /preload/Proxyme location. As a reminder, you can execute the debloat script (or any other one) from within Proxyme WITHOUT enabling SU, because it will always run in an environment with elevated privileges.
Jelly Bean 4.3
SC03EOMUBNH2 (Proxyme) (Build Date 2014-08-19)
This zip archive contains an Odin flashable file. It is not the complete stock image, so you MUST have OMUBNH2 already running on your phone or you will need to download it from the above reference sites, which carry complete stock firmware images, and flash it before continuing with this file. Instructions are included.
mediafire
uploaded.net
torrent, mirror2
(Flashing these ROMs will NOT trigger the custom binary counter)
Jelly Bean 4.3
XXUENE4 GT-I9305 Based (Proxyme) (Build Date 2014-05-16)
This image will clear data/cache implicitly upon initial boot, so backup your stuff before flashing
This one includes the Samsung Chinese IME with support for full screen handwriting and the QUERTY layout with extra row of numerical keys at the top
torrent, mirror1, mirror2
mega.co.nz
uploaded.net
SC03EOMUBND2 (Proxyme) (Build Date 2014-04-02)
This image will not clear data, but please consider wiping data/cache manually before posting about issues not related to Proxyme
mega.co.nz
torrent, mirror1, mirror2
(Unpack the .tar.md5 file from any one of the following (multipart) zip archive and flash with Odin)
SC03EOMUBND2_PROXYME20140419.z01
SC03EOMUBND2_PROXYME20140419.zip
Jelly Bean 4.1.2
MI4 GT-I9305(TGY) Based (Build Date 2013-09-26)
Rooting instructions are displayed in RootInfo app
Wipe Data/Cache if you are experiencing problems.
Display Languages: English(UK/US), Chinese(Trad/Simpl) and Korean
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg;zh_CN)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
MR8 GT-I9305(TNL) Based (Build Date 2013-09-26)
Rooting instructions are displayed in RootInfo app
Wipe Data/Cache if you are experiencing problems.
Display Languages: (en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU;sk_SK; sl_SI; uk_UA; uz_UZ; az_AZ; hy_AM; ka_GE; es_US; pt_BR; ar_AE;zh_CN;zh_TW;ja_JP)
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
MG3 GT-I9305(SFR) Based (Build Date 2013-07-31)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
Data and cache are wiped, so backup your data prior to flashing with Odin.
Display Languages: (en_GB;en_US;en_AU;en_IE;en_NZ;en_ZA;ko_KR;de_AT;de_CH;de_DE;fr_FR;fr_CH;bg_BG;cs_CZ;da_DK;el_GR;es_ES;et_EE;fi_FI;ga_IE;hr_HR;hu_HU;is_IS;it_IT;lt_LT;lv_LV;mk_MK;nb_NO;nl_NL;nl_BE;pl_PL;pt_PT;ro_RO;sr_RS;sv_SE;tr_TR;ca_ES;eu_ES;gl_ES;kk_KZ;ru_RU;sk_SK; sl_SI; uk_UA; uz_UZ;az_AZ; hy_AM; ka_GE;es_US; pt_BR; ar_AE)
Input: Samsung Chinese IME (English/Chinese-TW/Chinese-HK/Chinese/Korean), Standard Samsung IME (en_GB;en_US;az;ca;cs;da;de;et;es;eu;el;fr;gl;ka;hr;it;is;kk;lv;lt;hu;nb;nl;pl;pt;ru;ro;fi;sr;sk;sl;sv;tr;uk;ko;hy;bg)
mediafire (unpack tar.md5 file from this multipart zip archive and flash with Odin)
Jelly Bean 4.1.1
SC03EOMAMJ4 ( 2013-10-18 )
Depending on what's running on your phone currently, you may have to consider performing a manual factory reset and wipe the cache and data partitions.
Rooting Instructions:
Default state is - not rooted - Proxyme has been included in this rom,
Proxyme offers live su binary control, and without the need to 'root' the phone, you have...
- SSH server with virtually unlimited user accounts, configurable with specific UID, GID, home directory and shell,
- execution of scripts with elevated privileges (sample debloating script included),
- tag along scripts for root ON and root OFF actions,
- busybox switch
(Unpack the .tar.md5 file from any one of the following zip archive and flash with Odin)
torrent - full stock root ready (Proxyme)
Uploaded.net - full stock root ready (Proxyme)
MF1 (Build Date 2013-06-10)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
mediafire (unpack tar.md5 file from this multi-part zip archive and flash with Odin)
MC3 (Build Date 2013-03-18)
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
MB1 (Build Date 2013-02-08)
To toggle root/unroot, boot the phone and then press VolumeUp/VolumeDown/Power simultaneously for a brief moment.
This toggle only works if you enable Settings->Developer Options->USB Debugging
Chainfire's SuperSU has been included for your convenience.
hotfile - link dead (unpack tar.md5 file from this zip archive and flash with Odin)
.
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
MA6 (Build Date 2013-01-24)
Courtesy aki0306...
http://forum.xda-developers.com/showpost.php?p=38739961&postcount=8
Custom ROMs
(Flashing these ROMs COULD (and usually will) trigger the custom counter)
Probam Rom
Go to this post... and this post... Courtesy @sasbudi
Slimbean 4.3 NTT Docomo SC-03E
Go to this post... Courtesy @majidkhan
Carbon 4.2.2 for NTT Docomo SC-03E
http://forum.xda-developers.com/showpost.php?p=45164630&postcount=550 Courtesy @majidkhan
PACman (Paranoid AOKP CyanogenMod) 4.2.2
http://forum.xda-developers.com/showpost.php?p=43996579&postcount=489 Courtesy @Edgrr000
CyanogenMod
Instructions for flashing CM10.1 Courtesy @lparryU
Getting CM10 to work on SC-03E with Osaifu-keitai... Courtesy @FlyingFlipFlop and @lparryU
http://forum.xda-developers.com/showpost.php?p=42076531&postcount=313
http://forum.xda-developers.com/showpost.php?p=42076531&postcount=302
http://forum.xda-developers.com/showpost.php?p=42094976&postcount=303
rXTREME.v10.0
Link to post Courtesy @Edgrr000
KBC Developers github wiki
Contains everything everyone in here needs, Samsung custom kernel, with visible hidden partition for using triangle away on stock rooted,
and having all Japanese things working too. And the cm10.1 links. Its in Japanese but easily translated. (courtesy of @Robobob1221)
https://github.com/kbc-developers/release/wiki
Paranoid Android (GT-I9305)
Link to post Courtesy @Edgrr000
Misc
How to Convert ROMs for the SC-03E By @DroidZombie
Japanized Rom Tool By @LeathSeraph
http://lt.imobile.com.cn/forum.php?mod=viewthread&tid=10282917
Hints & Tips
Follow this trail...
SC-03E Hints & Tips
Hints & Tips
Guides.. with several links and specifically for unlocking your phone with the proper ROM (has the LK5 modem which is the go to for unlocking and working with other carriers), and instructions to do just about everything you need to get done with this phone
How to Convert ROMs for the SC-03E (By @DroidZombie)
Instructions for flashing CyanogenMod ROMs (By @lparryU)
Unlocking
Unlocking Guide - Courtesy of XDA member @majin
Yet Another Unlocking Guide
Custom Binary Counter
.Reset Guide .By @majin
Tethering
Tethering Guide By @majin
How to change Tethering preset APN By @majin
Change Roaming Status
Reference post By @majin
Proxyme Rooting
Proxyme Guide
Fixing Lost IMEI
How to repair your SC-03E's IMEI number and restore its network connection
Miscellaneous
SC-03E Dial Pad Codes
SC-03E Docomo S3 LTE - Just Another Unlocking Guide
This (sim) unlocking guide has been primarily inspired by the very comprehensive guide initially written and posted by @majin in his post.
WARNING: This unlock procedure will automatically wipe the phone's cache and data partitions, effectively performing a factory reset; you are strongly advised to backup your data prior to executing this guide.
Prerequisites:
Windows PC running Odin3 in an administrator account (tested with Odin3 v3.07)
USB cable to connect phone to PC (preferably original cable for reliability)
Internet access to download firmware image(s)
Google account to access Play Store
The following list outlines the required steps in order to successfully unlock your SC-03E:
If you have data on the phone, which is of any importance to you, then I highly recommend that you make appropriate backups first
If present, remove the sim card and sdcard (there's no need to have a Docomo sim card for this procedure to work)
Download this stock firmware image, which is based on MB1 and includes the appropriate modem component to assist in wiping the NV stored network locking data structures. In addition, this firmware image is root-ready; meaning that you can toggle root mode by pressing VolumeUp/VolumeDown/Power button combination briefly to switch modes.
Initiate Odin Download mode on the SC-03E (Turn the phone off, then simultaneously press VolumeDown/Home/Power buttons until the Download Mode splash screen appears and requires you to press VolumeUp to continue or VolumeDown to cancel if you find yourself suddenly struck by an overwhelming feeling of stage-fright)
Unpack the SC03EOMAMB1_LK5MDM.tar.md5 firmware image from the above-mentioned/downloaded zip archive and flash the file with Odin3 (specify the image file in Odin's PDA section)
As soon as Odin completes the flashing process, it will instruct the phone to reset; be patient while the phone starts up, because it will require more time to setup and configure itself after a factory reset.
If you have reached this step, then we're assuming the phone has booted successfully and you are presented with the configuration wizard. You need to at least enter your Google account credentials in order to access the Play Store.
Install the (free) ServiceMode Shortcut app (author: KABASOFT) from the Play Store.
Another (paid) option is the ShowServiceMode For Galaxy LTE app (author: Jaken's Laboratory).
Start the service mode app and tap the ServiceMode option, which will in turn fire up the ServiceMode main menu
Select [1]UMTS->[1]DEBUG SCREEN->[8]PHONE CONTROL->[6]NETWORK LOCK->[3]PERSO SHA256 OFF
Now use the phone's android menu soft button to select Back in the popup menu to return to the NETWORK LOCK menu
Tap [4]NW LOCK NV DATA INITIALLIZ and wait for about a minute before returning to the NETWORK LOCK menu; when you tap this option again, it should state PERSO_NV_INIT is SUCCESSFUL
You may now power off the phone to insert a sim card from your favorite telco operator and restart the phone
From this point onward, it is possible to flash any other firmware image without affecting the unlocked state
Enjoy!
SC-03E Dial Pad Codes
This list is most probably not complete. Please post or send a PM if you know about codes not listed here, your input will be highly appreciated!
*#0*# ........................... Hardware Testing
*#06# .......................... Show IMEI number
*#0011# ....................... GSM Status Information
*#0228# ....................... Battery Status
*#0782# ....................... RTCTimeRead (Show Time)
*#1111# ....................... ServiceMode - READ FTA SW VERSION
*#1234# ....................... Show Software Version
*#2222# ....................... ServiceMode - READ FTA HW VERSION
*#2663# ....................... Touch Screen/Key Firmware Update
*#7284# ....................... PhoneUtil - UART & USB Configuration
*#7353# ....................... Quick Test
*#7594# ....................... Factory Mode - Shutdown Configuration
*#9090# ....................... ServiceMode - DIAG CONFIG
*#9900# ....................... SysDump
*#34971539# ................ Camera Firmware Check
IMEI Repair Procedure
How to repair your SC-03E's IMEI number and restore its network connection.
Keywords: IMEI: null/null Unknown + Baseband: Unknown + no connection with QPST + no IMEI backup + phone signal lost
Disclaimer
This procedure is intended to be applied in a last resort scenario only. You must check thoroughly what the actual cause is for your phone having lost its imei number. It may very well be merely due to an incompatibility issue between the baseband code and the efs version, and thus easily fixed by flashing a proper modem component. Writing to partitions in your phone's internal storage device, re-partitioning it, flashing with the Odin tool or operating the QPST Qualcomm engineering tool carries many risks, which include hard-bricking the phone. You are solely responsible for anything you do to your phone and by carrying out the steps detailed in this procedure, you are agreeing to accept all responsibility for any and all outcome of the procedure, even if you end up with an expensive door-stop.
Try This First
Before panicking and diving into this procedure to perform all of its steps, note that your specific problem/case might not require such an extensive procedure. There could very well be a much simpler solution for your case, so I strongly advise you to put some effort into diagnosing your problem properly (best as you can given the resources you have at your disposal) BEFORE continuing.
I will be adding topics to this section based on the feedback we get, which will hopefully help everyone to improve diagnostics and find out if there are quicker/better way to solve any specific case.
BASEBAND UNKNOWN (Courtesy of @majin)
About the devices with "BASEBAND UNKNOWN" not recognized by QSPT, for first users should try with one of these:
1) enter *#9090# and check if "[2] DM/DUN over HSIC (*)" is selected, then to try to use QSPT to fix/restore the IMEI/EFS-folder, (if users have some old working backup too).
3) Try to use EFS Professional Suite to restore the right permissions on the NV files.
4) Use "Qualcomm NV Tools" (included in "EFS Professional Suite") to write directly their IMEI and to do some other test.
If they can't anything of that, then they really need to make all the "Chinese steps".
Click to expand...
Click to collapse
Introduction
This procedure is based on the following two posts, which are identical content-wise, and may be from the same individual. Credit goes to user xt890612 of forum site bbs.shendu.com and user softbank_1001 of forum site bbs.91dongji.com. Special thanks to xda member @majin for the find/input/feedback and having tested the procedure on his SC-03E.
- bbs.91dongji.com
- bbs.shendu.com
The issues we will attempt to resolve are:
IMEI corrupt or 0
Baseband Unknown status
QPST does not recognize the phone
What to Expect
If the procedure has been followed correctly and applied successfully, then take note of the following points.
IMEI restored
Network connection restored
Device serial number not the same as your original one (we will try to resolve this in the future)
No SIM network lock (Do not apply this procedure if you only want to SIM unlock a device with no issues)
You should be feeling happy, so please lookup the sources mentioned above and thank them
Preparations & Prerequisites
You will need the following tools and files, so please check each item in the list below and make sure you have them ready before commencing with the first step of the procedure.
An SC-03E which can at the very least boot into Odin Download Mode (soft-bricked). If the bootloader is corrupt, you will need some kind of JTAG service to revive the phone, because this procedure will not help your case.
Windows PC
Odin v3 (preferably Odin3 v3.09 or v3.07) - Google is your best friend
Google QPST.2.7.378.zip and download this Qualcomm engineering tool. Install it on the PC.
ADB tool/program. ADB, Android Debug Bridge, is included with Google’s Android SDK.
Hex editor. Google 'Hex editor' and download your preferred or favourite variant. Try HexEdit.exe.
Download SC-03E_IMEI-REPAIR.ZIP (mirror, torrent) and unpack the files in this archive to a work directory
Download one of the pre-rooted or root ready rom images, which are still functional/bootable on your phone, from the OP/reference post (this item is only required if your phone does not boot into Android at all, even after resetting it, and is not rooted)
Step 1 - Flash a Bootable Rooted ROM Image
If your phone currently has firmware, which boots properly and can give you root access, then skip this step. If not, then use Odin to flash the rooted image you have downloaded earlier. Consider resetting the phone afterwards by entering recovery mode to clear data and cache.
Step 2 - Enable USB Debugging
Enable USB debugging by setting the checkmark in the following option in settings:
Settings->Developer options->USB Debugging
Step 3 - Connect the Phone
If necessary, wait for all PC drivers to install and initialize.
Step 4 - Prepare Phone Internal Storage
Copy all 15 mmcblk* files, which were unpacked from the SC-03E_IMEI-REPAIR.ZIP zip archive earlier, to the phone's internal sd card after connecting it to the PC. The files must be located in the root of folder /sdcard.
It is important that you consider verifying data integrity of the mmcblk* files you have copied to the phone. Root Browser is recommended and can assist in this process. The following list consists of the MD5 checksums generated for the files in the SC-03E_IMEI-REPAIR.ZIP zip archive.
b5cfa9d6c8febd618f91ac2843d50a1c *mmcblk0p1
30fd6dfc09a70c8bcf345dc8c9e2781a *mmcblk0p10
c71fb4dfba643299159b97c6065fdb54 *mmcblk0p11
95557d70252c9b0af3f95a2244cd93ab *mmcblk0p12
e35b35efb73dd8320bdae08ec463372c *mmcblk0p13
31bc9037b092df1abbcf7550938d553d *mmcblk0p14
96995b58d4cbf6aaa9041b4f00c7f6ae *mmcblk0p15
b5cfa9d6c8febd618f91ac2843d50a1c *mmcblk0p2
dbad1316e91f5dcf0b89ad3e456f3bf8 *mmcblk0p3
713a67b9605c02f6cdd0346dfa1cab1e *mmcblk0p4
130715b90924c2394e1acd758059dd90 *mmcblk0p5
4029a1de061c375547aa3096a14562dc *mmcblk0p6
67bb0d7fbec2e250c5e2bd75dd9816f3 *mmcblk0p7
9e4a4230f51545ffd352cb7988f4bc9f *mmcblk0p8
edc27dbf0cc8b29df3ba31e21b552a98 *mmcblk0p9
4459508535b3c064f6afc6d1c6119b9e *sc03e.qcn
Step 5 - ADB
Now open a cmd window and start the ADB tool by typing the following command at the cmd prompt, followed by the enter key. In many cases, you will first have to cd (change directory) to the directory where the adb.exe program is located (hint, if you've installed the Android SDK, look for the location where it was installed and search its subdirectories for adb.exe):
>adb shell
If the shell in the adb session starts successfully, the following prompt is presented:
[email protected]:/ $
Type su followed by the enter key to get root access. If the $ sign in the prompt does not change in a # sign, then you have no access to root and you should revert back to step 1 to make sure you have a rooted firmware image on the phone.
[email protected]:/ $su <enter>
[email protected]:/ #
Step 6 - Restore Partitions
This step must be taken with great caution. You will be directly writing to partitions in the internal storage device and a mistake can end in disaster. Copy the following lines, each terminated by the enter key to initiate the command. Note that the lines with mmcblk0p10 to p14 can take a long (5 minutes or more) time to complete, so be patient.
dd if=/sdcard/mmcblk0p1 of=/dev/block/mmcblk0p1 <enter>
dd if=/sdcard/mmcblk0p2 of=/dev/block/mmcblk0p2 <enter>
dd if=/sdcard/mmcblk0p3 of=/dev/block/mmcblk0p3 <enter>
dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 <enter>
dd if=/sdcard/mmcblk0p5 of=/dev/block/mmcblk0p5 <enter>
dd if=/sdcard/mmcblk0p6 of=/dev/block/mmcblk0p6 <enter>
dd if=/sdcard/mmcblk0p7 of=/dev/block/mmcblk0p7 <enter>
dd if=/sdcard/mmcblk0p8 of=/dev/block/mmcblk0p8 <enter>
dd if=/sdcard/mmcblk0p9 of=/dev/block/mmcblk0p9 <enter>
dd if=/sdcard/mmcblk0p10 of=/dev/block/mmcblk0p10 <enter>
dd if=/sdcard/mmcblk0p11 of=/dev/block/mmcblk0p11 <enter>
dd if=/sdcard/mmcblk0p12 of=/dev/block/mmcblk0p12 <enter>
dd if=/sdcard/mmcblk0p13 of=/dev/block/mmcblk0p13 <enter>
dd if=/sdcard/mmcblk0p14 of=/dev/block/mmcblk0p14 <enter>
dd if=/sdcard/mmcblk0p15 of=/dev/block/mmcblk0p15 <enter>
Close the cmd window and restart the phone. If the phone does not boot into Android (could be bootlooping due to incompatible data elements), then perform a reset in recovery mode by wiping data and cache.
At this point you should confirm that the baseband has been restored in settings.
Step 7 - Restoring IMEI
Get ready to make changes to the sc03e.qcn file, which was unpacked from the
SC-03E_IMEI-REPAIR.ZIP zip archive earlier, using the hex editor.
Load the sc03e.qcn file in a hex editor and search for the following hexadecimal byte value sequence:
08 0A 21 43 65 87 09 21 43
The file contains two instances of the sequence as is shown above. Both sequences must be changed to your IMEI number and the way it is done is outlined below.
Note that when searching for the above sequence, in most hex editors you are supposed to also specify the search type, whether it be a text search or byte (binary search. You want the latter type.
Start with looking up your device's IMEI number. It is printed on the label in the battery compartment and on a label or sticker on the original box, if you still have it. The IMEI number consists of 15 digits, so please write it on a sheet of paper in order to help you visually 'construct' a hexadecimal sequence, which in turn can be used to update both instances of the abovementioned sequence in the file. This sequence has three fixed nibble values, which must remain unchanged in the final sequence. The following sample shows x's in the sequence which represent the part to be initialised to your IMEI number. The fixed (constant) parts are the 08 and the A in xA.
08 xA xx xx xx xx xx xx xx
In order to correctly fit your 15 digit IMEI number into the sequence, use the following guide to construct it. Here, we use the dummy IMEI number 012345678901234 for reference only.
...0..12.34.56.78.90.12.34 (IMEI number to convert)
08.0A.21.43.65.87.09.21.43 (byte sequence to be constructed)
As you can see, the first digit of the IMEI number is paired with the A of the second byte in the sequence; it is placed left of the A, thus becoming the most significant nibble of the byte. The remaining digits are paired to form 7 groups in order, where each pair's digits are swapped as is shown above.
When you have finished changing the two instances of the search sequence to reflect your IMEI number, save the sc03e.qcn file, exit from the hex editor and move on to the next step.
Step 8 - Restore Configuration From QCN File
Enter the following string in the stock phone dialpad:
*#7284#
{
"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"
}
Immediately after entering the trailing # sign, as is shown in the above image, the service mode screen shown in the next image will appear.
Tap on the Qualcomm USB Settings button to display the list of USB options you can choose from. This is shown in the next image.
Select the RNDIS + DM + MODEM option followed by tapping the OK button to return to the previous screen. Now use the back button to return to the dialpad.
Next, enter the following string in the stock phone dialpad to enter the DIAG CONFIG service mode screen:
*#9090#
Immediately after entering the trailing # sign, as is shown in the above image, the service mode screen shown in the next image will appear.
Select the [2]DM/DUN over HSIC (*) option. Note that the phone will immediately reboot as soon as you tap on this option in order for it to take effect.
Let's start the QPST Configuration program in Windows and select the Ports tab to add the new port, which has been assigned to the phone's USB communication protocol. Make sure to select the port with label USB/QC Diagnostic before clicking on the OK button.
If the port has been correctly initialised and selected, SURF9615 (0) should be displayed in the Phone column of the Ports tab, as is shown in the image below.
Finally, select the Start Clients menu and navigate to the QPST Software Download item to start its corresponding program.
In the QPST Software Download program, select the Restore tab and then specify the path to the qcn file which you have edited earlier. Hit the Start button to start uploading the new configuration file to the phone. After the upload is done, reboot the phone and check the IMEI number to verify everything went ok.
Finalizing
Enter the following string in the stock phone dialpad:
*#7284#
The service mode screen appears, so again, tap on the Qualcomm USB Settings button to display the list of USB options you can choose from. To restore the default USB settings, select the RNDIS + DM + MODEM option followed by tapping the OK button to return to the previous screen. Now use the back button to return to the dialpad, or hit the home button to continue using the phone normally.
That's it...enjoy your phone!
Notes & Feedback
Serial Number (Courtesy of @majin)
About the wrong Serial Number, [between step 6 and 7] if users have still on board the Chinese Rooted ROM (or if they flashed any other correct Rooted ROM), they can easily edit the file "\efs\FactoryApp\serial_no" by the phone itself (status is 1000:0000 rwxr--r-- 744)
Then they can flash any other favorite ROM [anyway, to make all easier, I suggest some 4.1 ROM, same as the Chinese one.]
Click to expand...
Click to collapse
hey i cant posting outside url
error message
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
aki0306 said:
hey i cant posting outside url
error message
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Click to expand...
Click to collapse
8 more posts to go and you're in. Why don't you head over to this thread and see if you can contribute or give feedback to any of the queries from other members. Once you get into a dialog or discussion, you'll hit that magic 10 easy.
Your message to davidcsv was also relayed to that thread, and it would help to introduce yourself to the group and gain some 'trust' wrt your firmware images.
---------- Post added 5th March 2013 at 12:46 AM ---------- Previous post was 4th March 2013 at 11:58 PM ----------
MB1 Root Rom JB4.1.1
MA6 Root Rom JB4.1.1
MC3 Root Rom Android File Host JB4.1.1
★MC3 Rom no need rename but need flash stock MC3 Rom before flash root Rom
how to flash
flash from odin
1.flash stock rom
ex if u wanna flash MB1 root, u have to flash MB1 stock Rom before flash Root Rom
2.into recovery, wipe/factory reset
3.unzip Root Rom and rename file
★you guys have to rename file when unzip root Rom★
ex SC03E-ROOTED-system_MB1.tar.md5
↓
SC03E-ROOTED-system.tar.md5
4.Flash Root Rom from odin
5.boot
6.installe Supersu or Superuser on play store
cation MB1 & MA6 Root Rom is "same name of file"
thx for kbc-developers
hv fun guys!!!!
---------- Post added at 12:51 AM ---------- Previous post was at 12:46 AM ----------
Custom Rom Link
jump to china forum
this Rom on MA6 Rom
damn.. didn't know this thread existed.
I will link this to the first post in my thread and have it closed.
if you could close my thread so all the talk can go here, it would be much more beneficial/easy to keep track of things.
---------- Post added at 02:01 PM ---------- Previous post was at 01:46 PM ----------
I can confirm that the root method worked for MB1...
LETS GET THE PARTY STARTED! Seriously, I am having a drink afterwork!
lol,trying with my phone.
update result soon.
my phone is rooted now.
but still waiting for custom one that removed needless app.
"Get PIT for mapping" <-------is this dangerous?
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
skylinerxz said:
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
Click to expand...
Click to collapse
I was just going to ask this...
didoka_702 said:
lol,trying with my phone.
update result soon.
my phone is rooted now.
but still waiting for custom one that removed needless app.
"Get PIT for mapping" <-------is this dangerous?
Click to expand...
Click to collapse
Get PIT for mapping is harmless, because the flashing process with Odin is just getting the current partitioning configuration as is stored in the phone. Just stay away from the PIT options in Odin (PC).
Why don't you just remove unwanted system apps with Titanium Backup?
skylinerxz said:
Thank you aki0306..
Already rooted my phone..
Is there any ways to install cwm on sc03e?
Click to expand...
Click to collapse
Do you mean one of the CWM recovery flavors or the Android builds (like for example CM 10.x)?
davidcsv said:
Do you mean one of the CWM recovery flavors or the Android builds (like for example CM 10.x)?
Click to expand...
Click to collapse
i would like CM10.x ! + CWM recovery flavors!
you got a lab rat available for this!
davidcsv said:
Get PIT for mapping is harmless, because the flashing process with Odin is just getting the current partitioning configuration as is stored in the phone. Just stay away from the PIT options in Odin (PC).
Why don't you just remove unwanted system apps with Titanium Backup?
Click to expand...
Click to collapse
sorry.already did that with tianium backup but still not edit my post.
IparryU said:
i would like CM10.x ! + CWM recovery flavors!
you got a lab rat available for this!
Click to expand...
Click to collapse
Who wants to try CWM Touch recovery? It is embedded in the latest upload of the MB1 stock root ready firmware image. The links are available in the original post in the pre-rooted stock ROMs section.
The procedure is as usual, flash with Odin (PC). Then, when your phone has booted into Samsung's stock Android, at any moment press VolumeUp/VolumeDown/Power at the same time and only briefly. This should root the phone (install su binary) and install the CWM Touch recovery... I say 'should' because I have only been able to test this procedure on my Korean version of the S3; in this case, CWM's recovery has been adapted for the SC-03E. There's no visual or audio confirmation when you've pressed those three buttons, so check with your favorite root-requiring app or with the included SuperSU app.
IF rooting works with this image, then the difference with the one presented by aki0306/kbc-developers is that theirs will always root the phone during startup; meaning you have the convenience of always starting up in a rooted environment. This mechanism will only root it when you need it (three button press detailed above); I'm still assuming that when you reboot, each time su (root) is removed by Docomo's security measures in the boot environment... if you want no root then reboot. As soon as someone can confirm whether this new mechanism works, I can turn it into a toggle kind of switch, so you can root and unroot without having to restart the phone.
davidcsv said:
Who wants to try CWM Touch recovery? It is embedded in the latest upload of the MB1 stock root ready firmware image. The links are available in the original post in the pre-rooted stock ROMs section.
The procedure is as usual, flash with Odin (PC). Then, when your phone has booted into Samsung's stock Android, at any moment press VolumeUp/VolumeDown/Power at the same time and only briefly. This should root the phone (install su binary) and install the CWM Touch recovery... I say 'should' because I have only been able to test this procedure on my Korean version of the S3; in this case, CWM's recovery has been adapted for the SC-03E. There's no visual or audio confirmation when you've pressed those three buttons, so check with your favorite root-requiring app or with the included SuperSU app.
IF rooting works with this image, then the difference with the one presented by aki0306/kbc-developers is that theirs will always root the phone during startup; meaning you have the convenience of always starting up in a rooted environment. This mechanism will only root it when you need it (three button press detailed above); I'm still assuming that when you reboot, each time su (root) is removed by Docomo's security measures in the boot environment... if you want no root then reboot. As soon as someone can confirm whether this new mechanism works, I can turn it into a toggle kind of switch, so you can root and unroot without having to restart the phone.
Click to expand...
Click to collapse
just finish custom my phone today @@
ill try this one tomorrow
and i have already backed up my phone with
+back all user data and app with titanium back up
+back up efs folder using root explorer
+back up QCN file using EFS pro by this thread
any process i need to do after this?
didoka_702 said:
just finish custom my phone today @@
ill try this one tomorrow
and i have already backed up my phone with
+back all user data and app with titanium back up
+back up efs folder using root explorer
+back up QCN file using EFS pro by this thread
any process i need to do after this?
Click to expand...
Click to collapse
That should cover it
I use Whatsapp, so I always make a seperate backup of its database folder as well (folder /mnt/sdcard/WhatsApp)... it contains the message history and all the media that's been sent over.
so i test this one recently and here is MY result (i usually hold up down volume first and then press power button)
+first time:check with Supersu.it said cannot install SuperSU cause of SU binary is not installed.
+restart and try again,this time i installed Titanium back up.and its said that the phone isnt rooted
+restart and try again,no worked
+and at the 5th 6th time everytime i try to press volume up down power to install Su binary,the phone restart.
//so its my result.anyone esle?
//and couldnt get to recovery mode :| now i back to aki rom till the new one came out.
Introduction:
This is the information thread for all known OTA's for Google Glass
Click to expand...
Click to collapse
File List:
Latest:
XRW85 → XRX13B
See Google Glass # Official ROMs - XDA Wiki for a list of files
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a stock AND unmodified rom
Can I flash this if I'm rooted?
Only if you have not modified any files
Click to expand...
Click to collapse
Credits:
Kroo: XRR02 → XRR35 update
Ytwytw:
XRR02/XRR35 → XRR64B
XRR64B → XRR88
XRR88 → XRS36
aeroevan
XRV15C → XRV16
XRV16 → XRV22
XRV27 → XRV34
XRV39 → XRV49
XRV67 → XRV70D
winner00:
XRV22 → XRV27
XRV34 → XRV39
Psymin: XRV49 → XRV60B
jtxdriggers: XRV60B → XRV67
hedsick
XRV70D → XRV72
XRV72 → XRV87
XRV85B → XRW14B
XRW14B → XRW45C
XRW45C → XRW66
XRW66 → XRW85
XRW85 → XRX13B
Click to expand...
Click to collapse
Changelog:
Oct 24, 2014: Added XRW85 → XRX13B
Sep 29, 2014: Added XRW85
Sep 11, 2014: Added XRW45C → XRW66
Sep 11, 2014: Changed Page Layout to match my other pages
May 8, 2013: Initial Page
Click to expand...
Click to collapse
2char
Interested as well.
Sent from my XT907 using xda premium
Has anyone tested it or reviewed it??
Thanks to Kroo on #googleglass via freenode, we found the update delta for "XE5" (XRR35)
c17357b01ac6.signed-glass_1-665738-from-625737.c17357b0.zip
Going to remake op into list of currently available files officially from goog, in the meanwhile "XE6" is rolling out now/soon
------------------------------------------------------------------------------------------
Rewriting OP, quoting for history
TheManii said:
Though there is no public dump of XRR02 "XE4", XRR35 "XE5" is rolling out.
(Someone did dump and give a copy to android police to look at, but as of this post I'm not aware of anyone releasing one publicly)
If anyone that owns a glass and has time, could you do the following?
Dump XRR02
Find the update url for XRR35
While the former requires a device that hasnt updated, the latter should be able to be performed on any gGlass, regardless of current rom.
----------------------------------------------------------------------------------------------------------------------
I cant tell you how to do the former, if it was a standard android device you would (preferably) root and dump:
The kernel image
Bootloader
Baseband (if it was a phone/had a modem)
/system
1/2/3 need root, 4 does not.
----------------------------------------------------------------------------------------------------------------------
To do the latter:
If you have already updated
Root your device
Make a backup of build.prop
Open up build.prop
edit the following lines:
Code:
ro.build.date.utc=1364970747
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR02/625737:user/release-keys
Check for updates
post/send me your adb logcat
I do not have access to one (or even know anyone that does) so I cant be any more specific then that.
Click to expand...
Click to collapse
"XE7" is rolling out now
"XE8" is rolling out now, need someone with a glass unit to assist in finding the update urls
TheManii said:
"XE8" is rolling out now, need someone with a glass unit to assist in finding the update urls
Click to expand...
Click to collapse
I've got glass and haven't updated to XE8 yet - how can I find the update URL?
Sent from Frost⁴ using XDA Premium
aSquard said:
I've got glass and haven't updated to XE8 yet - how can I find the update URL?
Click to expand...
Click to collapse
It actually doesnt matter what rom you're on specifically.
You'll need to be rooted for the following steps, I would advise caution if you're not rooted and havn't rooted your glass previously.
I don't have a glass and I can't be responsible if it breaks during the rooting process.
If you're on "XE7" already:
If you did not already download the ota (which is hard to estimate since it will download automatically):
run a logcat
wait until it appears in the logcat
---------------------------------------------------------------------------
A more reliable method:
wait for the prompt to update to "XE8"
check /cache, there will be a file, it should be obvious to spot
---------------------------------------------------------------------------
If you're on XE4-6 (or want to also assist in getting the update urls for those)
Make a backup of build.prop if needed
open build.prop
edit the following 2 lines: (the values to change them to is at the end of this post)
ro.build.date.utc=
ro.build.fingerprint=
Reboot
wait for prompt
check /cache for filename
"XE4"
Code:
ro.build.date.utc=1364970747
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR02/625737:user/release-keys
"XE5"
Code:
ro.build.date.utc=1367809146
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR35/665738:user/release-keys
"XE6"
Code:
ro.build.date.utc=1370295186
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR64B/696124:user/release-keys
"XE7"
Code:
ro.build.date.utc=1372372324
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR88/726688:user/release-keys
XE9 is out now, still would like a volunteer to help find the rest of the glass OTAs
XE10 is out now
TheManii said:
XE10 is out now
Click to expand...
Click to collapse
i tried updating with the X10 image thru the fastboot flash = boot, recovery , system, (and now i get boot loop on the GLASS screen )
Any help of a ADB expert
XE11 is out now
XE12.1 and XE16 are rolling out now,
reminder: still looking for a volunteer with a glass to find the ota urls.
Requirements:
Be on a stock rom
Rooted
Edit: found the urls for XE12 -> 12.1 -> 16, but still many more missing
Mine tried to update but failed at clockwork. I managed to pull the 12.1.zip from cache but it looks like you got that already... can I go from EX12 to 16? or do i have to apply 12.1 first (which I cant seem to install)?
Since there's no direct ota available for 12 -> 16, you'll need to go through 12 -> 12.1 -> 16
I'm not sure how to get it to install. Clockwork gives me a status 7 failure
Did you modify files in /system?
If you did and cant undo the changes, flashing the factory image should make it so you can ota.
Disclaimer: I do not own a glass, but the steps shouldnt be any different from a nexus device.
I did but I also tried flashing the stock images (boot, system, userdata and recovery) but couldn't figure out how to flash it with the stock recovery.
I have my Glass rooted, but I do not know what to use to flash the zip files. Also, if 12.1 isn't rooted yet, how do you install the XE16 update? Thank you.
All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name ROM Droid Mini/Maxx/Ultra L!te FW 4-21 ML
Tagline Faster Lighter Economical
SYSTEM Firmware SU4-21 Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- tzdata 2015e
- icudt51l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps VZW & MOTO
- replaced by sound WirelessChargingStarted
- old gapps for long work phone
- uppdate apps Chrome, LatinIME, Skip, TouchLess, MotCamera, MotGallery, Migrate
- tetering work
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/Droid
for Loked Device
Install for QDLoad9008
Root, Xposed, BusyBox is PreInstalled
- Root SuperSU v2.46
- XPosed 2.6.1
- BusyBox v30
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_4_4_4_VZW_SU6-7_BL_V30.BA_Stock.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_Part1.bat. Parts XX of system.
*** You can also run a file if you are sure that your phone can work 4-5 hours with the screen RUN_Rus_VZW_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_Part**.bat. Parts XX of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
installed application Xposed 2.6.1
Xposed launched clicked install, reboot your phone
I see that the application is launched is set app_process 58 (pre-installed in the system) and XPosedBridge.jar 54 version (made with the application)
then uploaded GravityBox [KK], a check mark, the next reboot, and everything works
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Droid/4.4.4 SU4-21
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Droid Mini/Maxx/Ultra L!te FW 4-21 ML, ROM for the Motorola Droid Ultra
Contributors
CrashXXL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Android 4.4.4 SU6-7 (Flash on RSDLite)
Version Information
Status: Stable
Current Stable Version: 1.02
Stable Release Date: 2015-09-01
Current Beta Version: 0.01
Beta Release Date: 2015-08-15
Created 2015-10-08
Last Updated 2015-10-08
Reserved
Reserved
Update Available
Log
- Launcher with a mesh 4 * 5 with no search string
- Smart Action Moto return ... The assistant working all options
for blocked Patch_SmartAction_Launcher.4x5.NoBar.rar https://yadi.sk/d/kxbxpTnziSg35/Droid
for unlocked MotLauncher.4x5.NoBar.zip https://yadi.sk/d/jp8ykQqFindY8/Droid and SmartActions.zip https://yadi.sk/d/jp8ykQqFindY8/SmartActions
Reserved
I'm a bit confused here. A few months ago I used your set of steps to upgrade to SU6-7 with permanent root (even though I still have locked bootloader). Does this new set of steps allow downgrading to SU4-21 and then the ability to use Sunshine to unlock bootloader? Thanks!
Can I do Write Protection with this ROM?
OscarBrito16 said:
Can I do Write Protection with this ROM?
Click to expand...
Click to collapse
Write protection is still enabled so the root is limited as far as what you can do with it.
classic757 said:
Write protection is still enabled so the root is limited as far as what you can do with it.
Click to expand...
Click to collapse
I mean to install a custom recovery or flash a custom rom!
No, you would not be able to install a custom recovery with method. Unless you have su4-21 or lower your bootloader is locked and at this time there isn't a method to unlock it.
Also you can't downgrade to an older su version, once you have su5-24 or above the qfuse is blown.
As said above you can achieve root, but since the system is still write protected root access is limited. The other option is to perm root your device, and try safestrap, I hope I'm allowed to post that in the thread, sorry if I'm not.
Sent from my XT1080 using XDA mobile app
OscarBrito16 said:
I mean to install a custom recovery or flash a custom rom!
Click to expand...
Click to collapse
Without write protection disabled you cannot install custom recovery or flash custom roms.
Also, if you are on 4.4.4 there is no full root available at this time.
any chance to implement/add Czech language on this ROM?
dcoaster said:
I'm a bit confused here. A few months ago I used your set of steps to upgrade to SU6-7 with permanent root (even though I still have locked bootloader). Does this new set of steps allow downgrading to SU4-21 and then the ability to use Sunshine to unlock bootloader? Thanks!
Click to expand...
Click to collapse
I have the same concerns. Are we supposed to downgrade to the SU4-21???Will this grant us the ability to use Sunshine and unlock our bootloaders?? I thought it wasn't possible to downgrade??? Please I'm lost here I want to do this but I'm am unsure of the outcome?
You can add any language, but it takes a lot of time.
can you tell me how to do it?
- unpack apk
- transtale xml value-en to value-cz
- pack
- install on update from twrp
- check work
@CrashXXL
how can I add the gesture of jedi to my phone? what files do I need to take from your rom?
I do not want to take the whole rom, would be great if i could only take a few files and push the diff to my phone
Can i use this to flash it right over my rooted SU6-7 (rooted with your method months ago, Crash) or do i need to re-flash original stock (without root)?
will my phone be still rooted if i factory reset it..?
I guess this contains only Russian and/or English language, am i right?
Einheit-101 said:
I guess this contains only Russian and/or English language, am i right?
Click to expand...
Click to collapse
no, localization saved and added 2 more Russian and Ukrainian
Yeah, so no German
FF is utility to provide links on official ROMs from Huawei's HiCloud.
There is no magic. Huawei posts builded ROMs onto HiCloud, then post links on own consumer sites or pushes OTAs.
Lack of FF is that it uses database of known paths. And if Huawei posted new ROM in new path - FF will not know there is this ROM.
But... we have community
If you have notification of new ROM in phone's system update and you know that this ROM cannot be founded in FF yet, please add it or provide full path to it
To provide full path you need:
1. Download Packet Capture from Play Store: https://play.google.com/store/apps/details?id=app.greyshirts.sslcapture
2. Install it and setup
3. Run and press start button with symbol 1
4. Choose "System update" in list
5. Go to System Update and check for new ROM
6. If it found something return to Packet Capture
7. See all packets and find long text like this:
/tds/data/files/p3/s15/G1751/g1750/v100023/f1/full/changelog.xml
It is full path to changelog, but it might be path to update.zip there...
FF wants values after G and g
In this example value for G = 1751
value for g = 1750
8. Post these values here or in Firmware Finder's topic: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
To manually add founded ROM to FF you need do additional steps (not neccessary, but it will be complete work)
1. Run FF for PC
2. Fill G range (example - from 1751 to 1751)
3. Fill g range (example - from 1750 to 1750)
4. Check v range for fresh values. In example v value = 100023. For scan you need range what including this value (95000 - 102000 is good range)
5. f range - value after f in path from step 7 (f1) . In some cases there was f2 or f3.
6. Press add and app will add settings to scan
7. Press start and app will scan entire range. FF will generate queries to HiCloud. When site returns good answer - FF explore link and add to local DB
8. Watch "Found firmwares" screen and send firmwares to FF server
Your contribution will be appreciated.