[ROM] Color OS v1.2.0i {Full Wipe} - Oppo Find 7 and 7a

Woo hoo, after emailing support, someone had the kind heart to post the original firmware (ROM) online!
Here is a torrent link to the original firmware (BEFORE THE OTA UPDATE):
Click Here.
You'll need the original Oppo recovery to flash this, available here:
Click Here.
For information on how to root the device {Link to another's XDA post):
Click Here.
UPDATE: They made a custom version so you can update via TWRP (torrent link):
Torrent of the TWRP-friendly version.
Almost the same as the Samsung series, you hold the power and volume down button until you see the Oppo logo. It takes a few seconds, but it'll load the recovery environment.
Copied from the developer's forum:
Below are the details for that firmware from the developer.
X9006_12_OTA_INT_002_all_svn6157_wipe.zip
---
Kernel: 3.4.0-s6157
Android: 4.3
Build ID: JLS36C
ColorOS: V1.2.0i
---
OTA: X9006_12.A.02_INT_002_140419
Build Date: 2014-04-19 14:56:05 +0000
Please use the torrent if you can handle it | keep sharing | sharing is caring

Should be able to use TWRP if you change what model phone it's looking for? Something about the 7'a' I seem to recall?
Can't wait for the custom ROMs to start flowing, thanks!

seanpr123 said:
Should be able to use TWRP if you change what model phone it's looking for? Something about the 7'a' I seem to recall?
Can't wait for the custom ROMs to start flowing, thanks!
Click to expand...
Click to collapse
I'll be talking with Dees_Troy and Oppo this weekend about updating TWRP.
It mainly depends on what the FHD Find 7 will report in its build.prop
Oppo's naming conventions are confusing as hell:
Find 7a (marketing) = find7 (kernel defconfig) = Find 7 (kernel comments)
Find 7 (marketing) = find7wx (kernel defconfig and ifdefs) = Find 7S (kernel comments)
OnePlus One (marketing) = find7op (kernel defconfig and ifdefs) = Find 7 (kernel comments - there are so few changes that this device is basically a find7 with a different indicator LED from the kernel perspective)

TWRP Flashable Version
seanpr123 said:
Should be able to use TWRP if you change what model phone it's looking for? Something about the 7'a' I seem to recall?
Can't wait for the custom ROMs to start flowing, thanks!
Click to expand...
Click to collapse
I edited the updater-script file to work with TWRP. If you want to get an official Oppo full ROM or incremental update to work with custom recovery:
-open the .zip archive with WinRAR, 7zip, etc.
-extract the <META-INF> directory
-open the extracted directory and navigate to META-INF\com\google\android\
-open "updater-script" in Notepad++ or similar utility (Notepad not recommended)
-delete the first two lines (they start with "assert" and "getprop" and contain the string "FIND7")
-save the changes
-drag the previously extracted <META-INF> directory back into the window with the open .zip archive (add it to the archive)
-flash with custom recovery
-dance
X9006 ColorOS 2.0.0i beta TWRP flashable:
https://dl.dropboxusercontent.com/u/74339090/X9006ColorOS_V2.0.0i_Beta_full_TWRP.zip
MD5 Checksum: E1DA13CD7681BFE015F87B900ED67151
-Sent from my rooted, bootloader unlocked, overclocked Speak & Spell running Android 5.1 Mango Yogurt Pudding

Doc Ames said:
I edited the updater-script file to work with TWRP. If you want to get an official Oppo full ROM or incremental update to work with custom recovery:
-open the .zip archive with WinRAR, 7zip, etc.
-extract the <META-INF> directory
-open the extracted directory and navigate to META-INF\com\google\android\
-open "updater-script" in Notepad++ or similar utility (Notepad not recommended)
-delete the first two lines (they start with "assert" and "getprop" and contain the string "FIND7")
-save the changes
-drag the previously extracted <META-INF> directory back into the window with the open .zip archive (add it to the archive)
-flash with custom recovery
-dance
X9006 ColorOS 2.0.0i beta TWRP flashable:
https://dl.dropboxusercontent.com/u/74339090/X9006ColorOS_V2.0.0i_Beta_full_TWRP.zip
-Sent from my rooted, bootloader unlocked, overclocked Speak & Spell running Android 5.1 Mango Yogurt Pudding
Click to expand...
Click to collapse
Any chance of a md5 # to check the beta to? I had it fail to completely download a couple times and when it finally did it took a couple hours.
E1DA13CD7681BFE015F87B900ED67151 is what I get.

Chevyguy85 said:
Any chance of a md5 # to check the beta to? I had it fail to completely download a couple times and when it finally did it took a couple hours.
E1DA13CD7681BFE015F87B900ED67151 is what I get.
Click to expand...
Click to collapse
Sorry I forgot to include the MD5. I checked the above MD5 and it matches the original file. I'm new to this and perhaps Dropbox is not the best place to host a file. If someone wants to host it elsewhere I'm fine with that. I've added the MD5 to my post.
-Sent from my Lite-Brite

Doc Ames said:
Sorry I forgot to include the MD5. I checked the above MD5 and it matches the original file. I'm new to this and perhaps Dropbox is not the best place to host a file. If someone wants to host it elsewhere I'm fine with that. I've added the MD5 to my post.
-Sent from my Lite-Brite
Click to expand...
Click to collapse
It's okay. The effort is appreciated. I don't know what people are using to host either. Dropbox has limits which is probably what was happening when I tried to download it.
Tapped out on my beastly OPPO Find 7a

Doc Ames said:
Sorry I forgot to include the MD5. I checked the above MD5 and it matches the original file. I'm new to this and perhaps Dropbox is not the best place to host a file. If someone wants to host it elsewhere I'm fine with that. I've added the MD5 to my post.
Click to expand...
Click to collapse
You are welcome, i mirror it:
http://mirror.lucky.li/android/oppo/x9006/firmware/custom/
@gatekpr
The links are not the official download links, i just mirror everything oppo released and if you all could use torrent it would be nice and i'm not from oppo or a developer from oppo
btw. there can you find other firmware files: http://mirror.lucky.li/android/oppo/x9006/firmware/
X9006_12_OTA_INT_001_all_svn5596_wipe.zip is the real firmware which is preinstalled on every device X9006_12_OTA_INT_002_all_svn6157_wipe.zip is only the first update, thats what you get over the air. You should use the 002, but maybe for some reason you wanna go with the 001.

LkyX said:
You are welcome, i mirror it:
http://mirror.lucky.li/android/oppo/x9006/firmware/custom/
@gatekpr
The links are not the official download links, i just mirror everything oppo released and if you all could use torrent it would be nice and i'm not from oppo or a developer from oppo
btw. there can you find other firmware files: http://mirror.lucky.li/android/oppo/x9006/firmware/
X9006_12_OTA_INT_001_all_svn5596_wipe.zip is the real firmware which is preinstalled on every device X9006_12_OTA_INT_002_all_svn6157_wipe.zip is only the first update, thats what you get over the air. You should use the 002, but maybe for some reason you wanna go with the 001.
Click to expand...
Click to collapse
The 002 does not playing nice with Titanium Backup. If you flash the 001, then the OTA, TB works fine.

ORLY!
farfromovin said:
The 002 does not playing nice with Titanium Backup. If you flash the 001, then the OTA, TB works fine.
Click to expand...
Click to collapse
That's the problem I had, but TB wouldn't restore after the OTA update from the original version. That's why I upgraded to the v2.0.0i. If I have time over the next weekend, I'll try again from the first release and then to the OTA. I need my TB restored data :-\

@gatekpr
My fault, you can also list the .zip file or provide a link to the firmware dir. You don't have to remove the links only because of that i want that more people use torrents. But thank you anyway
And you remove now the 1.2.0 update from 0414 do you don't wanna talk about it?

Hello
Tks for the post
This is the v2.0.0.i beta & not the v1.2.0i than is write. Correct no ?

Edit: never mind.
Sent from my X9006 using XDA Premium 4 mobile app

So was it determined Titanium doesn't play well with 002?
Any work arounds? I've tried everything I can think of...

I installed 001 restored my ti backup and then got the ota without a problem. While people have complained about losing data I did not, you just lose settings. All the apps go forward just fine after the ota. Go up to a few posts and the one fellow has a mirror for the 001 download.

Thanks for reply, but could you check if Titanium can still restore apps+data or did that functionality go away with the 02 update?

It will restore your apps and app data just like any other phone if you back it up that way. I did not check system as I don't restore any system stuff and cant speak to that other than it being a generally bad idea. The 002 update did not delete any app data for me and I think for anyone. People confuse settings and system data with user data a lot. You will lose your system settings and some of the data but this shouldn't be an issue as you install 001, root it, install ti, restore your backup, get the OTA and then you put in your system settings. I don't use any system apps that would store data but I can say that some stuff made it through like themes. If you have something in the built in notes or whatever I would back it up separately just in case.

So you still haven't tried a restore of user app data then right?
Not asking about system apps, just normal user apps and games. For me it would just sit and restore the app forever until you force stop TiBu. Tried all the different app processing styles in the settings and no change.

seanpr123 said:
So you still haven't tried a restore of user app data then right?
Not asking about system apps, just normal user apps and games. For me it would just sit and restore the app forever until you force stop TiBu. Tried all the different app processing styles in the settings and no change.
Click to expand...
Click to collapse
the OTA breaks TiBu restore. I had a similar problem with the 0419 update, but if you flash back to the version before that, or the 2.0 beta, then it can restore just fine.

seanpr123 said:
So you still haven't tried a restore of user app data then right?
Not asking about system apps, just normal user apps and games. For me it would just sit and restore the app forever until you force stop TiBu. Tried all the different app processing styles in the settings and no change.
Click to expand...
Click to collapse
Yes, apps will go just fine, its not like this phone has special software that somehow parses your user app data out of them and deletes it while retaining the app. If you backed up apps includes their data your data it will be there. Done it like ten times now. No not kidding, I've been going back and forth between the 2.0 and 1.2 as I play with different stuff to try and fix the battery drain.. Install 001, root, install ti, restore your apps, get the ota, works every time for me. The only thing the ota does as near as I can tell is delete system settings. I already said it does not hurt your app restore, not sure how I'm failing to communicate that as I've said the apps go back fine several times now. It would not be fine if your data somehow got culled out. That would be a fail. And no, I'm not trying to be a Richard here I'm trying to be clear as I seem to be failing at that and I apologize for not communicating effectively.

Related

Samsung Galaxy Gio GT-S5660M - ArpegGioMod ROM

(Avis aux intéressés, j'ai parti une discussion en français sur Frandroid.)
Hello everyone,
Here's my ArpegGioMod ROM, for the Galaxy Gio GT-S5660M. Current (and final) version is 0.9
(ArpegGioMod has had over 1500 downloads! Thanks!)
Features:
Rooted
Deodexed apps and framework. (Optional)
Working FM radio (remember, your headphones are the antenna!)
No power on sound.
Restored support for the normal Android bootanimation.zip format. Right now it's just running the "base" animation (with the green Android text). I'm open to suggestions/logos/proposals!
CRT screen off animation re-enabled, you do need to turn back animations on in the settings to see it.
ADW Launcher (I just used the "standalone" version and placed it in /system/app/, not the cleanest way, but it works, and leaves you the choice between that and Touchwiz Launcher)
Removed all Bell software, as well as some Samsung apps.
New in 0.6
Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
Car mode.
New in 0.7
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone.
Changed the default browser homepage to Google instead of Bell's.
New in 0.8
Phone will not relock itself to Bell after doing a factory reset without a SIM card in the phone. (Turns out I mixed up some files and uploaded a version with Bell apps left in the CSC folder, along with the unmodified customer.xml. Not an issue, until someone did a factory reset.)
Unsecure kernel. So now, adb remount and push work. adb shell is permanently root.
New in 0.9
CWM installation instead of Odin
Using Phiexz's customized stock ROM kernel, with support for both ext4 and RFS partitions. The kernel also includes different wifi drivers, and they work for me!
Updated superuser apps (3.0.7) and binaries (3.0.3.2). The upgrade of su from 3.0.3 to 3.0.3.2 seems to have fixed whatever caused the crashes.
Reodexed, this seems to provide better performance.
Removed the annoying "Full charge" notification.
Enabled native SIP functionality. (Untested.)
Removed the "Android Tips" widget.
Added the "Roboto" FlipFont apk, found on XDA.
No-frills CPU Control 1.20
Google Application updates:
Android Market 3.4.4
Gmail 2.3.5.2
Google Maps 6.3.0
Google Search 1.3.3.247963
Street View 1.7.1.0
Voice Search 2.1.4
YouTube 2.3.4
To do:
Implement BLN by patching /system/framework/services.jar
Things I will not do. (Or at least, not without significant assistance from those requesting it.)
Additional languages.
Files required to install 0.9:
Galaxy Gio ext4 converter
Backup RFS User Data (Optional)
Restore User Data to ext4 (Optional)
ROM Zip file: ArpegGioMod 0.9 MD5 hash: 010DA7C4542537443D2DD2E9BDBAFC43
Re-odex script (Optional)
Short Version 0.9 Installation instructions:
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Backup User Data Script
(You'll probably want to delete the two tar.gz files remaining on your SD card afterwards.)
As required: format from RFS to ext4.
If you're upgrading from a stock ROM or ArpegGioMod 0.8: Restore User Data Script
Flash ROM zip
Re-odex as required
Detailed Version 0.9 Installation instructions:
(Or, the "this is my first time trying this out and frankly I'm a little overwhelmed with information" version.)
I'm going to start this one with a brand new, freshly out of the box Gio. I will however assume that you already have a working Odin and Android SDK install. Plenty of tutorials out there for both. (See links below for the correct Odin version.)
Copy the zip files to your MicroSD card.
Reboot your phone in Download Mode. (Hold Volume Down + Home + Power. There will be a pink warning screen. Press Volume Up.)
Flash ClockWorkMod Recovery with Odin.
Reboot the phone into Recovery Mode. (adb reboot recovery, or Home + Power)
"install zip from sdcard"
"choose zip from sdcard"
Install the ext4 converter zip.
Install the ROM zip.
Install the Re-odex script zip.
Reboot
Optional: adb shell, then dd if=/dev/block/bml5 of=/sdcard/bml5 bs=4096 to get your unlock code as per Tweakradje's unlock tutorial.
Enjoy!
Version 0.8 Installation instructions:
Un7zip and flash with Odin.
I strongly suggest you do a factory reflash and reset if you're flashing from something other than stock or ArpegGioMod.
Version 0.8: http://www.mediafire.com/?nxp0ce21909c676 7-Zip file MD5 hash: 6CEE73812AF9D30189A5F808CE0A7DEA
(Thanks Koodiifin!)
Tools and additional information:
CWM 5.0.2.7-based recovery, compiled for the 5660 by Phiexz, modified for the 5660M by Peteragent5: http://forum.xda-developers.com/showthread.php?t=1493932
"Supersafe" bml5 unlock method by Tweakradje, originally meant for the GT-I5500, should also work with little or no modifications for the 5660M: http://forum.xda-developers.com/showthread.php?t=828534
My other thread from which all of this started: Samsung Galaxy Gio GT-S5660 and GT-S5660M Partition Mapping This thread contains links to a rooted, but otherwise completely stock ROM backup I made prior to starting my work on ArpegGioMod.
Older Clockworkmod-based recovery, meant for the Europe/Asia 5660, but working fine on the 5660M: http://particle.blurringexistence.net/samsung-gt-s5660/clockworkmod-recovery
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
Goodbye,
Darkshado
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
hardran3 said:
Just installed ArpegGio on my Virgin Mobile 5660M and it seems to be working great. 3G wifi and FM are working, plus I am glad to be rid of a bunch of carrier garbage apps. Thanks Darkshado I can't wait to see a2sd in there. Could I install it the manual way on this FW?
Click to expand...
Click to collapse
If you mean by modifying your boot.img ramdisk, yes. That's what I've been unable to do. I suspect an outdated/incompatible mkbootimg binary, and can't download the source make a new one as of writing this since kernel.org is still down.
If you're feeling adventurous, you could also try flashing an Euro 5660 boot.img. But I can't guarantee there won't be other issues.
OT:
Thanks too Darkshado for all your tips for 5660M owners. I got mine 3 days ago, rooted and unlocked on day 2, flashed your FW on day 3. Reminds me of my days making custom OS for my blackberry
Click to expand...
Click to collapse
You're welcome.
Hi, This is going to be my first flash for my S5660M. I've a small question for it. What mode should I choose in ODIN? Do I need to care about the ops file?
Sorry for my newbie question. Thank you.
You have to rebuild kernel with ext support. To create system.rfs or other *.rfs you have to type in console
Code:
mkfs.ext4 -O ^huge_file system.rfs
or it won`t boot. Of course you need modify initscripts. You can change from rfs to ext4 and it should work.
My problem is that due to the troubles at kernel.org I haven't been able to download the AOSP source yet.
I already suspected it wouldn't work with the stock kernel boot.img before trying.
For the conversion, I used a modified Galaxy Tab ext4 conversion update with the mkfs binaries included. That worked like a charm, CWM mounted the partitions, no questions asked.
I'll have to wait until an official AOSP repo comes back online to take this further.
Goodbye,
Darkshado
Sent from my Nexus S using XDA App
It will work with stock kernel, but you need change build config.
Hi
Just installed your rom this sunday... It work nice and no problem!
Was wondering, is the factory reset from the cwm is better than the one within the phone app? And or is the same?
And keep up the good work it is really appreciated
Thx Dark!
Sent from my GT-S5660M using XDA App
Darkshado said:
Hello everyone,
New in 0.6
[*]Added options to the power button menu: Reboot (Normal), Reboot Recovery Mode and Reboot to Download Mode.
[*]Car mode.
[/LIST]
Goodbye,
Darkshado
Click to expand...
Click to collapse
Nice job, very nice.
Is it duable to create that option in a aditional zipfile.
That you can flash it in recoverymode with a other rom????
You would make me very happy with that.
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Question: has anyone else managed to re-Sim-lock their phone?
It's happened to me inadvertently, twice. Not knowing why on Earth the phone did this, I decided to get to the bottom of things.
The unlock code from bml5 still works, but I find this annoying to say the least.
I found some strings in the CSC files (customer.xml to be exact) that seemed to tell the phone what network to lock itself to.
I managed to make the phone relock itself by going into recovery, wiping user data, and rebooting the phone without a SIM card in. Checking lock status with *#7465625# shows Network Lock [ON]
I turned off the phone, put a foreign SIM back in, unlocked the phone again, and re-wiped user data, leaving the non-Bell SIM in for the first boot. No relock.
I relocked the phone as above. Rebooted into recovery and pushed modified customer.xml files, without the network lock strings, to my /system/csc/ and /system/csc/BMC/system/csc/ directories. No relock!
Those modified CSC files are going to be included in ArpegGioMod from now on.
Goodbye,
Darkshado
Darkshado said:
You have to modify framework-res.apk framework.jar and android.policy.jar for this to work, and it requires editing Smali code.
I did it by loosely following guides meant for the I9000 found here.
You could always push those files from my ROM to give it a try like that, but I wouldn't count on the framework from the 5660M to be fully compatible with the 5660 (which I understand you have from some of your other posts).
Click to expand...
Click to collapse
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Amadeus01 said:
Hi, thx for the reply
Yes i have the 5660 ( no M ).
But i don't have a linux machine........
And i need that to compile those files.
I supose a linux-live dristri doesn't ad up for the job
Click to expand...
Click to collapse
I think a live distro would work fine... Me I installed Vmware player (free) to run a virtual ubuntu machine and it work fine for editing some of the the tar file... so a live distro would even be better i'm sure!
Sent from my GT-S5660M using XDA App
I unlocked with safe bml5 trick and wiped a couple of time but i did not put back a non bell sim since then... So i dont really know...
Did you use some script or some like that in you Rom? Because I got like almost 400-500 more point on antutu benchmark.... Nice
Sent from my GT-S5660M using XDA App
theboo23, Amadeus01: Practically all of my ROM work has been done under Windows so far!
You need:
Java JDK
Android SDK
apktool
Cygwin
A hex editor (I've used Frhed so far)
Notepad++ (Free, open source, tons of features: syntax highlighting and Unix line ending support to name a few)
(Optional) A program that can open FAT format image files such as MagicISO, to extract files from RFS partition images.
(Optional) xUltimate, to simplify deodexing a great deal.
(Optional) 7-Zip
I have installed Ubuntu (on an external USB drive with Wubi and Grub4DOS) to attempt boot.img and kernel modifications, and to build from AOSP/CyanogenMod source.
However, kernel.org, which hosts AOSP repositories, is still down almost three weeks after having been hacked. So those parts of my project have been stalled in the meantime as I hadn't downloaded the source beforehand.
theboo23: There have been multiple reports of deodexing increasing performance, that might explain the points increase on the benchmark. To be frank, I don't bother with them unless I have something really specific to test.
Goodbye,
Darkshado
Darkshado said:
Those modified CSC files are going to be included in ArpegGioMod from now on.
Click to expand...
Click to collapse
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
And a couple of questions: your ROM has only one file/partition in it - system.rfs - and apparently this is the only thing that it replaces, everything else remains stock. One other custom ROM available on this site contains two files in the .tar - system.rfs and boot.img.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
stfn74 said:
By "from now on" I suppose you mean ver 0.7 included which is also on the changelog for it. However, it's exaclty after I flashed 0.7 (from 0.6 and stock before that) that my phone re-locked again and I had to use the unlock code (which I retreived while ago using bml5 method and still keep). I wiped before flashing 0.6 on top of stock, but did now wipe before flashing 0.7 on top of 0.6.
Click to expand...
Click to collapse
I tried a couple more wipes and SIM swaps (T-Mobile USA, Koodo and Telna) with no relock occurring, so I hate to say, but I'm a bit stumped if there's something else than the CSC files causing this.
By the way, I knew already that at one point I will need my unlock code again. Having unlocked 6 or 7 5660Ms in the last week I have noticed that, once unlocked for a network (say, Fido) and you put a different SIM (Chatr), it gets locked again! Not only that, if you put the Fido SIM back, it is still locked. You have to enter the unlock code again, and luckily it's always the same. So, I resorted to writing down the code on the back of the phone under the back plate for further reference
Click to expand...
Click to collapse
I take it you work at a Rogers/Fido kiosk or store right? You're probably going to get more data on this than I ever will. I too wrote my code in the battery door just in case after it relocked a second time.
Q1: will it be safe to flash that other ROM on a 5660M having in mind it only replaces those two files/partitions? I know you already answered this before, just being extra cautious
Click to expand...
Click to collapse
Should be safe, if the boot.img is meant for the Euro 5660, you could encounter some bugs. I haven't tested those boot partitions and kernels.
Q2: if I want to return to ArpegGioMod after that, how do I proceed? Where do I get the boot.img from? Posible answer here: I have made a full backup via CWM of the stock ROM. It contains boot.img. Can I insert it in your .tar and flash and expect to get the same as flashing ArpegGioMod directly on stock?
Click to expand...
Click to collapse
You could just restore that nandroid backup.
Otherwise, tarring the boot.img with Cygwin and flashing with Odin should work. Then flash ArpegGioMod. Or make a single tar file with both partitions in Cygwin.
Here's a "universal" command: tar -H ustar -c amss arm11boot mibib oemsbl qcsbl boot.img recovery.img csc.rfs system.rfs data.rfs efs.rfs > GT-S5660M_MUGKG3.tar
I put it in a text file with the .sh extension, in cygwin/bin/ making it a command that can be invoked directly. (It's actually part of a set of batch files I've made to automate the copy and preparation of ArpegGioMod updates.)
Q3: if I get the system.img (renamed to system.frs) and boot.img from the SWM backup, put them in a .tar and flash, will that give me stock phone?
Click to expand...
Click to collapse
No reason it shouldn't.
Darkshado said:
I take it you work at a Rogers/Fido kiosk or store right?
Click to expand...
Click to collapse
No, I'm just an user, my job has nothing to do with mobile business. It's just Futureshop had a great deal on 5660Ms last week and half of my family and friends got one I was the first to root and unlock mine so... had to do it with everybody else's. I'm playing with custom ROM flashing now and want to make sure I got everything right, because I suspect I will be doing it number of times.
So I'm using the opportunity to say "Thank you!" for your work!
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
chairsz said:
i used this rom with m 5660m and i still got wifi problems. wont turn correctly. im seeing you mention about ops file and boot img modding.dont kno how to do that
Click to expand...
Click to collapse
Did you flashed a 5660 rom? You'll need to flash the stock 5660m rom first. The link is here;
http://forum.xda-developers.com/showthread.php?t=1233719

[ROM] Pre-rooted stock 6.2.2

I've put together a pre-rooted version of the stock 6.2.2 update from (link courtesy of b63). I did this like the 6.2.1 pre-rooted zip, in that it's just the stock update without the bootloader/recovery images and with su/Superuser/busybox added. So as a quick summary:
This will format and replace your /system partition, meaning you will need to reinstall anything that was modified or added there (Market, maps framework, etc). This also means it should be good to use as a fresh ROM - I tested by wiping my /system partition and flashing it and it installed just fine.
It's built to be installed via TWRP, or really any custom recovery should work.
Superuser, the su binary, and busybox are pre-installed and symlinked.
This does not have any modifications intended to block OTA updates. Other than the necessary root binaries it is completely stock.
Installing this will not touch your bootloader or recovery partitions. The updated images for both of those have been removed and the script will not attempt to install them.
Wiping /data shouldn't be necessary if you're on another stock build (wasn't needed for my testing).
If you're already on 6.2.2, this won't root you (you want jcase's thread for that).
I have an "unsecure" boot image version and a "secure" boot image version. Unsecure means adbd is running as root so you get a # (root prompt) immediately when you shell in with adb. Secure means you get a $ (user prompt) when you shell and need to use 'su' to elevate to root.
As with most ROMs and such, a backup is recommended before flashing, flash at your own risk, etc etc. I've tested this on my Fire several times and had no issues, but I can't guarantee 100% that it will work for everyone (though I don't see any reason it won't). If you see errors about the '/misc' partition, don't worry - TWRP is looking for it but the KF doesn't have that partition. It won't affect the install.
Enjoy!
Downloads
Mediafire links:
Pre-rooted stock 6.2.2 - unsecure boot image (md5: eb0139533593edb8d7a4a2aae22e1cd8)
Pre-rooted stock 6.2.2 - secure boot image (md5: cdf032c3543da5805a1b1204247876db)​
Multiupload links (appear down, but I'll leave 'em for now in case they come back)
Pre-rooted stock 6.2.2 - unsecure boot image (md5: eb0139533593edb8d7a4a2aae22e1cd8)
Pre-rooted stock 6.2.2 - secure boot image (md5: cdf032c3543da5805a1b1204247876db)​
Well done, sir. I used your pre-rooted 6.2.1 ROM and was quite pleased to discover that it left my Android Market unscathed and was equally pleased to discover the same on this version. Thank you.
I've been using pre-rooted 6.2.1 ROM, will updating to this one reformat the /system partition and wipe out everything?
ch0mch0m said:
I've been using pre-rooted 6.2.1 ROM, will updating to this one reformat the /system partition and wipe out everything?
Click to expand...
Click to collapse
Yes, it will format /system, even if you're running the 6.2.1 I made previously. It's easiest to just think of it as a separate ROM, not an update to the 6.2.1 one (although of course the only difference is Amazon's updates between 6.2.1 and 6.2.2).
FWIW, I just use Titanium to back up the Market and Google Maps and I keep a copy of the maps framework jar/xml files on my sdcard so I can copy them back over. That and if the Market has updated itself it shouldn't get blown out anyway since the Market update apparently installs itself to /data instead of /system. GoogleServicesFramework should stick around in /data, too, but I back that up as well anyway.
Very awesome, thank you!! I just installed over your rooted stock 6.2.1 with a cache/dvalik wipe and everything works. Market and all my installed apps still work like a charm!
Just a thank you for this. Backed up, Flashed, wiped cache/dalvik and am now running 6.2.2 rooted with everything intact. Swift Key keeps force closing but I'll try reinstalling that.
edit: reinstalled Swift Key and I am back 100%. There is a full screen button in Silk and my books aren't distorted in icon form anymore!
Anyone else gettting force closes on google's gmail app?
Edit: I uninstalled and reinstalled gmail and it works fine now.
Thanks ... Market FC on me after update ... restored it from Titanium seems to work
Thank you. Flashed without incident. I did wipe cache and davik-cache first. Market did not have to be reinstalled and worked perfectly, including a download. I'm now 2 for 2 without getting an OTA and still on the original OneClickRoot method (was that what it was called? Seems so long ago!!)
It was SuperOneClick... me too. And, yeah, I almost don't remember it's been so long ago and I've read too many threads about this and that.
Flashed this, watched some amazon video, turned off the screen, and all of a sudden my kindle restarted and now my prerooted 6.2.2 must have been replaced with the ota because twrp is gone. I don't know how this happened, but basically be careful everybody! That's all I can really say...
Worked like charm. Flashed, updated location files and everything was up and running again in a matter of minutes.
DalekCaan said:
Flashed this, watched some amazon video, turned off the screen, and all of a sudden my kindle restarted and now my prerooted 6.2.2 must have been replaced with the ota because twrp is gone. I don't know how this happened, but basically be careful everybody! That's all I can really say...
Click to expand...
Click to collapse
Any more info? Did you lose root too? Which version did you install, the secure or unsecure?
Just flashed this (unsecured), and deleted otacerts.zip as outlined here:
http://forum.xda-developers.com/showthread.php?t=1451328
We'll see if I end up getting the update anyway...
Anybody still have this file, megaupload link is not working.
Willieumm said:
Anybody still have this file, megaupload link is not working.
Click to expand...
Click to collapse
Try the Deposit Files or FileServe links. Those seem to be working still.
I'm guessing some of the others may have disappeared due to the fallout from the giant Megaupload raid/lawsuit...
eldarerathis said:
Try the Deposit Files or FileServe links. Those seem to be working still.
I'm guessing some of the others may have disappeared due to the fallout from the giant Megaupload raid/lawsuit...
Click to expand...
Click to collapse
Can you point me to those other links? I dont see them in this thread.
Thanks
GM
George M said:
Can you point me to those other links? I dont see them in this thread.
Thanks
GM
Click to expand...
Click to collapse
The Multiupload links seem to be down completely now (actually, Multiupload as a whole is just down for me) so I'm going to re-upload them. I'll try Mediafire this time, see if it survives longer
eldarerathis said:
The Multiupload links seem to be down completely now (actually, Multiupload as a whole is just down for me) so I'm going to re-upload them. I'll try Mediafire this time, see if it survives longer
Click to expand...
Click to collapse
That would be great.
George M said:
That would be great.
Click to expand...
Click to collapse
Try one of these links:
Unsecure boot: http://www.mediafire.com/?gtxrohbc4gmu4m8
Secure boot: http://www.mediafire.com/?ttd8t49zosd910b

[Q] Correct Upgrade Path from 3.2 Gen2 to Custom ROM

Ok, I have decided to go ahead and upgrade my device since I want to maintain root, and Acer has been unable to provide my ANY OTA updates or a copy of firmware and I don't want to ship my device to support just for a firmware upgrade.
My Device Current Pre-Upgrade info:
Flex Version: 05_COM_GEN2
Device info version: 1.0
Model ID: A100(it's an A100-07u-16u the 16GB)
EC Version: 2d010100
Android Version: 3.2
It IS rooted, with Busybox installed but still stock build.prop etc. The only mod I apply regularly is to enable hulu with my script.
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
You should do a factory reset and reroot hc
Then download and install the .009 leak (.12 is an incremental update and does not perform the complete upgrade)
Then run the quick root method for ice found in these forums.
Unlock your boot loader
Flash cwm recovery and install rom manager following my thread on how to.
Then remove the boot.img from the .12 leak and flash through cwm
Hope this helps
Sent from my A500 using XDA App
NoSudo said:
Q: It seems to me they are ALL FULL Firmware installs, meaning Non-Incremental Updates. If so I'm guessing I can go directly to 4.0.3(0.12 build) from 3.2 Gen2, but I have read some mixed info about Gen1 vs Gen2. Im trying to verify I dont need to make and extra upgrade to gen1 first.
Click to expand...
Click to collapse
It is completely safe to go directly from 3.2 Gen2 to .12 ICS Gen1.
NoSudo said:
Q: Im wondering what the best upgrade path would be from my devices current state, to get it upgraded to ICS with CWM(or other recovery mod?)
Click to expand...
Click to collapse
Upgrade it as it is.
NoSudo said:
Q: I am wondering if I am understanding the correct order of things, especially when it comes to the, temp-root to perm-root, /system rw, Busybox reinstall.
Click to expand...
Click to collapse
Just root ICS using this method: http://forum.xda-developers.com/showthread.php?t=1531646, and that's it. Do not re-install busybox.
NoSudo said:
Do I just;
-Do a reset to factory defaults(maybe reroot after?)
-Enable "debug mode" in Settings
(still HC 3.2 Gen2)
-Copy 0.12 to SD card, rename and run update from stock recovery
(if it boot loops do a soft reset to wipe old data?)
-Start ICS
EITHER
-root ICS(mempodroid)
-mount -o remount /dev/block/mmcblk0p3 /system/
(Is this still necessary, to enable the installation of busybox to /system etc?)
-install/re-install Busybox, SuperUser from Market
OR
-root ICS(mempodroid)
-Install Busybox, SuperUser from Market
-mount -o remount /dev/block/mmcblk0p3 /system/
-Re-install Busybox to correct location(maintains root or re-root also?)
OR
-Some other method?
THEN
-ICS installed and rooted
-Unlock bootloader and install CWM(is this the RIGHT method HERE? for the unlock & CWM?
THEN(optional)
-Upgrade to custom ROM
Thanks
Click to expand...
Click to collapse
- Place the update.zip on your external sd card
- Boot into the stock recovery (and it will automatically flash the file)
- It will boot up
- Do a factory reset
- Root using the method linked
- Unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=1557445
- Rename the install_recovery.sh in the "/etc/" or "/system/etc/" directory.
- Flash CWM: http://forum.xda-developers.com/showthread.php?t=1558595
Optional - Flash a custom rom.
Follow what Theonew has proposed. I have a Gen2 and everything went swell. The key is to perform a Factory reset after installing ICS. Then:
Root
Unlock
Install CWM
I followed Masterpker2's Instructions in THIS thread and it all went perfect.
I didn't realize that the file for leak version 12 was an incremental. I just checked and I'm running 09
This being said the steps would probably be:
Flash 09
Update to 12
Root
Unlock
Install CWM
Edit: Don't forget this additional step which was missing from the OP that I linked
Land Master said:
Flash 09
Update to 12
Root
Unlock
Install CWM
Click to expand...
Click to collapse
You do not need to flash .09 before .12.
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
masterpker2 said:
From my inspection of the .zip files it seems .009 has boot loader.blob which is needed to update to the ics boot loader.
I did not see the blob in the .012 leak so it was a safe assumption to upgrade to the .009 leak first.
As with all flashing it is better to be safe than sorry. I have only done it the way I explained it above, but hey, if it works then that is one less step.
Sent from my A500 using XDA App
Click to expand...
Click to collapse
Yep. I agree with that statement. Just curious more than anything. I'm attempting to compile a consolidation thread and obviously if we can save some steps that's important. The more steps involved the more chances for something to go haywire.
Honestly all the different files that have been floating around can be confusing and I'm just attempting to clarify everything. Worst case is I will give various files a try and document my findings before posting results.
BTW... Thanks for your Thread on CWM. It was an unbelievably valuable resource!!
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Gibson.Dubs said:
I just recently flashed my wife's new 3.2.1 gen2 straight to the .012 leak with no issues. I then unlocked boot loader, installed cwm, etc...
Click to expand...
Click to collapse
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Land Master said:
Thanks!
Can you check the MD5 of the file (.012) you used against this:
61db347f9137196b936b6a3aa6c5e5f8
The file I have is named: Acer_AV041_A100_1.012.00_WW_GEN1.zip
Click to expand...
Click to collapse
That is the correct file name and the md5 matches.
61DB347F9137196B936B6A3AA6C5E5F8 *Acer_AV041_A100_1.012.00_WW_GEN1.zip
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
toyface said:
I could have sworn that there was a bootloader I deleted from the zip before flashing 012? Maybe that was 09 ha ha, if you have a look over at the A500 forums the recovery installer app now supports the a100, tested it yesterday, works well
Sent from my A500 using xda premium
Click to expand...
Click to collapse
You probably did. As I said I upgraded from 3.2.1 gen2 straight to ICS .012. I do not even have any of the other leaks downloaded anymore so I am certain.
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
NoSudo said:
Hey Thanks all for the information. It will make me feel allot more comfortable about performing the upgrade. Im sure other folks will be in the same/similar situation and will probably also find the info useful.
I can confirm that the .012 copy I got from Vanche's site has a bootloader.blob in the root of the .zip file. I didn't yet have the .009, just the original .002 and the .012 anyway so I'm glad I don't need .009. I Also confirmed it passed an md5 check 61db347f9137196b936b6a3aa6c5e5f8 Acer_AV041_A100_1.012.00_WW_GEN1.zip.
I'm running all over tomorrow. I should have time in the next few days. I'll post the results after and try to document anything that seems unexpected/note worthy for the directions Land Master is working on.
Click to expand...
Click to collapse
Good Luck NoSudo. FYI, I have posted a link to 009 in my thread. Not that you should need it but it is there now.
This information outlines what I did to upgrade stock HC 3.2 GEN2(rooted) to ICS 4.0.3 .012. Leak(for info on rooting HC look here
Update:
Well today after breakfast I decided to go ahead and upgrade.
1) I made a fresh backup with Titanium and copied it to an external device.
2) I placed the Acer_AV041_A100_1.012.00_WW_GEN1.zip inside a freshly formated(fat32) 4gb micro SD card.
3) Renamed the file to update.zip.
4) Did an MD5 check to ensure the file on the SD was a good file.
5) With the tablet shut down I placed the 4GB micro SD card into the A100
6) I twitched the screen lock to "on", held down the "volume down" button, then while still holding the "volume down" button, I pressed the "power button" for about 3 seconds.
7) Once the "booting into recovery" message in the upper left showed up, I released the still pressed down "volume down" button. As soon as the volume down button is released a graphic appeared with a robot with moving gears, and a progress bar.
Once the progress bar reached full, it poped up a message saying "Android is Updating" another progress bar, and a message saying "optomizing application x of 135" x being a changing number as it progressed.
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
NoSudo said:
After this process completed my login keypad appeared. I was able to login and all my old apps are still here and it all looks nice. So far so good. Im going to poke around a little then whipe the old data and stuff. Currently though it upgraded and kept all my apps, and settings, and seems to be working well.
I'll post another update later after I have messed with it a bit more.
Click to expand...
Click to collapse
When you're ready to root, etc. make sure you do a factory reset first.
Theonew said:
When you're ready to root, etc. make sure you do a factory reset first.
Click to expand...
Click to collapse
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
NoSudo said:
Yep, I'm planning on doing a factory reset and I guess format the internal storage also to be safe. I'm just curious how/what works without doing anything other then the update. So Im messing around with it a little. I also realized I forgot to backup a few documents I need LOL(oops that was close!) I didn't think about the fact that titanium just does my apps, and system. So I'm uploading some stuff to my dropbox at the moment.
Click to expand...
Click to collapse
Only updating is fine. I upgraded to ICS within a few days of the first leak, and everything's been working great.
I found that my camera was not being recognized after upgrading from 3.2 to 4.03(.012). As in I load camera and it pops up a box saying it doesnt see a camera device. I just did a clear cache, clear data in settings, apps, and now it sees the camera and it is working fine. No funky greenness some talked about so far.

[ROM] [NS4G] [AOSP] 4.1.2-JZO54K- Updated 10/13/12

I have compiled Android 4.1.2 for the NS4G from source. Other than reboot power options. this is a AOSP Build. This will be most like the OTA that sprint/google will be issuing.
I will try to answer questions but I don't consider myself a dev so I may not be able to answer all questions.
I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. As with all ROM's, flash at your own risk.
You must flash these gapps for Google backup to work.
CWM flashable rom
http://d-h.st/8Vv
SU.zip
http://d-h.st/uYn
Gapps
http://d-h.st/ztJ
First Build
Wifi Tether and MMS Recieve Broke
Second Build
Fixed MMS Recieve Thanks Burnsra
Third Build.
Fixed Wifi Tether over 3g.
fourth Build
Updated to r4
Tweaked Crespo Overlay
Fifth Build
Fixed build.prop mistake and tethering issue.
Sixth Buid
Added reboot options
Fixed Google Backup (Thanks rasengan82)
Limited SMS to 160 char or less
Major props goes to Burnsra for the mms fix. Rasengan82 for the google backup fix.
+1 to a flashable zip. Would love to try this out but I'm not willing to lose recovery
Sent from my Nexus S 4G using Tapatalk 2
cteneyck said:
I have compiled Android 4.1.1 for the NS4G from source using the newly available proprietary files that were released yesterday. This is a straight AOSP build with no extra's. this will be most like the OTA that sprint/google will be issuing. This is an OTA file and needs to be flashed in fastboot it will wipe your recovery and you will need to reflash. you will also need to find GAPPs and flash that to. If someone would like to take this and make it a flashable zip file for cwm recovery please feel free to do so.
I will try to answer questions but I don't consider myself a dev so I may not be able to answer all questions.
BTW If someone could mirror my file that would be sweet.
http://www.n5cjt.com/downloads/full_crespo4g-ota-eng.build.zip
Click to expand...
Click to collapse
Thanks, man! I am downloading now, and will have a dropbox link shortly. Dunno how long it will work with bandwidth limitations, but it can help alleviate at bit of stress on your end. Cheers!
Where can I get the gapps?
cteneyck said:
I have compiled Android 4.1.1 for the NS4G from source using the newly available proprietary files that were released yesterday. This is a straight AOSP build with no extra's. this will be most like the OTA that sprint/google will be issuing. This is an OTA file and needs to be flashed in fastboot it will wipe your recovery and you will need to reflash. you will also need to find GAPPs and flash that to. If someone would like to take this and make it a flashable zip file for cwm recovery please feel free to do so.
I will try to answer questions but I don't consider myself a dev so I may not be able to answer all questions.
BTW If someone could mirror my file that would be sweet.
To Flash,
1. Boot into bootloader
2. Run fastboot update full_crespo4g-ota-eng.build.zip -w (this will wipe your phone)
3. Flash custom recovery. fastboot flash recover custom-recover.img
4. flash google apps in recovery.
http://www.n5cjt.com/downloads/full_crespo4g-ota-eng.build.zip
Click to expand...
Click to collapse
WHAT actually gets wiped? Sdcard content? Or just system cache and data files?
Anyone else's download getting cut short? My first one got cut at 46 megs, and the other four times I tried was between 9-16 megs.
marleynyc said:
WHAT actually gets wiped? Sdcard content? Or just system cache and data files?
Click to expand...
Click to collapse
Just the phone. SD card stays intact.
AngelosDracul said:
Anyone else's download getting cut short? My first one got cut at 46 megs, and the other four times I tried was between 9-16 megs.
Click to expand...
Click to collapse
My webhost sucks.
AngelosDracul said:
Anyone else's download getting cut short? My first one got cut at 46 megs, and the other four times I tried was between 9-16 megs.
Click to expand...
Click to collapse
Mine did too. Don't mind though, me thinks I'll just wait for a flashable zip. Thank you cteneyck for getting this out so quick though!
marleynyc said:
WHAT actually gets wiped? Sdcard content? Or just system cache and data files?
Click to expand...
Click to collapse
With an OTA zip, this will wipe EVERYTHING! It is like installing a factory image and will format all partitions and flash in all images including boot, system, recovery, radio . . . It will also lock up your bootloader and unroot you.
Or the OP states otherwise so maybe I am wrong . . .
Next Gen. Tech said:
Where can I get the gapps?
Click to expand...
Click to collapse
I used the gapps from the CM10 build
cteneyck said:
My webhost sucks.
Click to expand...
Click to collapse
that sucks, because I cannot get a complete download to mirror. You might wanna reupload it somewhere else. If someone tries to push this to their phone and it is incomplete, it is going to brick 'em.
hlxanthus said:
With an OTA zip, this will wipe EVERYTHING! It is like installing a factory image and will format all partitions and flash in all images including boot, system, recovery, radio . . . It will also lock up your bootloader and unroot you.
Click to expand...
Click to collapse
I don't believe it will wipe the sd card but as with any rom. flash at your own risk.
I am guessing there are to many people trying to download at once. I am interested in taking a look at this myself. Been loving cmX but would like a true aosp build.
AngelosDracul said:
Anyone else's download getting cut short? My first one got cut at 46 megs, and the other four times I tried was between 9-16 megs.
Click to expand...
Click to collapse
Yes the same here got cut short at 1.69 megs and if I can get the post I can do another link on my severs.
Suntar said:
Yes the same here got cut short at 1.69 megs and if I can get the post I can do another link on my severs.
Click to expand...
Click to collapse
First post updated with new link.
Anyone else having DL issues with zip file? Mine is kicking me off the DL at different times. I get 15MB one time and then it closes, and the next maybe 25MB. If anyone out there was able to get through the full 108MB (I think), can you re-up it somewhere else please? Thanks!
=============
I see this has been addressed as I was typing....thanks a lot!!
cteneyck said:
First post updated with new link.
Click to expand...
Click to collapse
Any chance of a link that doesn't require an account or specific installed software to download the zip?
if the bootloader version is the same then it will not wipe SD card data. In this case, since it's not an official release, I'm sure the bootloader version has not changed I would recommend backing up any SD data, just in case...but it should still be there when you reboot.
I'd like to see a flashable zip on a site that isn't premium, and isn't intended for piracy lol
rougegoat said:
Any chance of a link that doesn't require an account or specific installed software to download the zip?
Click to expand...
Click to collapse
I'll have it on my MediaFire account shortly.

[How-To] Install Official I9505 Firmware on T-Mobile M919

**You must already have Root Access before you begin**
I regulary receive requests to assist in updating the T-Mobile M919 to the latest I9505 LTE Firmware. Below is a very easy process for doing it yourself:
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
Instructions:
1. Download the latest Official I9505 LTE Firmware from Sammobile.com.
2. Extract the System.img.ext4 and Cache.img.ext4, e.g. I9505_5.0.1_OB7_Official_Firmware, then place these images onto your device (use either internal or ext-sdcard).
3. Open the FlashFire app and "Agree" to the Terms and Conditions.
4. Press "(+)" twice to bring up the "Actions" menu.
5. Press "Flash firmware package" then locate and select System.img.ext4. FlashFire will scan the .img which may take several minutes to complete. Press "ok" once the scan is complete then press the checkmark to continue.
6. Press "Flash firmware package" again then locate and select Cache.img.ext4. FlashFire will then scan the .img. Press "ok" once the scan is complete then press the checkmark to continue.
7. Press “(+)” once again to bring up “Actions” and select “Wipe.” Under the “Options” menu select all partitions except “Internal storage” then press the checkmark to continue.
8. From the main menu Tap-hold-drag your "Actions" and place them in the following order:
- "Wipe"
- "Flash firmware package"(system.img.ext4)
- "Flash firmware package"(cache.img.ext4)
- "Process Cache" (Use default settings).
- "EverRoot" (Use default settings).
9. Last, press the lightning bolt then "Ok" to begin the flash.
The screen will turn black then display the contents of your system before beginning the flashes. Once complete your device will reboot and pause on the Samsung splash screen for about 3 - 4 minutes before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Notes:
1. You must already have a compatible custom kernel installed. Recommended Kernel: Lolli-Test-TW-07.02.2015 (source: http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/tw-lollipop-kernel-v1-t3024631).
2. After flashing I9505 firmware your wifi password may be forgotten upon reboot. To resolve this issue use ES File Explorer with root access enabled to edit the following build.prop line: ro.securestorage.support=true to "false"
3. You may also continuously receive an annoying security message. You can disable this message by using TiBu to freeze or remove the SecurityLogAgent.apk. Thanks to @Nana Ayeh
Whats inside? Is it lite ? Ooohhhh fiiirrrsssst [emoji13]
flatzki said:
Whats inside? Is it lite ? Ooohhhh fiiirrrsssst [emoji13]
Click to expand...
Click to collapse
Completely stock except for root and ausdim's kernel. Runs well on the M919 and can easily be a daily driver.
Nice! will be curious to see battery life reports on this.
After I'll restore the backup do I get OA7 modem and bootloader on my m919 device (like I odin it) ? Why mot just odin this Rom from the Leak thread ?
xperia_88 said:
After I'll restore the backup do I get OA7 modem and bootloader on my m919 device (like I odin it) ? Why mot just odin this Rom from the Leak thread ?
Click to expand...
Click to collapse
No the leak's modem will not flash on the m919. You can go flash the leak if you prefer.
muniz_ri said:
No the leak's modem will not flash on the m919. You can go flash the leak if you prefer.
Click to expand...
Click to collapse
I just wonder if I'll odin the leak that give me the new modem.
xperia_88 said:
I just wonder if I'll odin the leak that give me the new modem.
Click to expand...
Click to collapse
No, it won't. You can flash the AP file only and get a mostly working ROM except for wifi.
Thanks guys!! DL as we speak. Looks promising!!
Sent from my SGH-M919 using Tapatalk
mrbmg said:
Thanks guys!! DL as we speak. Looks promising!!
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I just noticed that it forgets my wifi pswd upon reboot. I will upload a new backup with the buildprop fix.
Edit: updated
muniz_ri said:
I just noticed that it forgets my wifi pswd upon reboot. I will upload a new backup with the buildprop fix.
Edit: updated
Click to expand...
Click to collapse
what version of twrp did you use?
det0xx said:
what version of twrp did you use?
Click to expand...
Click to collapse
I used 2.8.4.0
The rom is flawless other than the Wi-Fi PW mess up, which by the time I backed up and restored he already fixed. I have to have Wi-Fi calling but I set it up to my liking and the next time I leave I out on business I'm going to restore it. Also there was some security issue that kept wanting me to restart which I'm sure I could have figured out had I played on it a little longer and had service. Awesome job!
Sent from my SGH-M919 using Tapatalk
mrbmg said:
I used 2.8.4.0
The rom is flawless other than the Wi-Fi PW mess up, which by the time I backed up and restored he already fixed. I have to have Wi-Fi calling but I set it up to my liking and the next time I leave I out on business I'm going to restore it. Also there was some security issue that kept wanting me to restart which I'm sure I could have figured out had I played on it a little longer and had service. Awesome job!
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Well not to complain but i followed the instruction and i couldnt get it to work. TWRP told me i failed to choose a partition when i tried to restore. I used 2.8.4.0
Can someone do us others who use PHILZ recovery a huge favor and make a back up on there? if not its okay ill just be patient thanks btw.
No WiFi calling, I assume?
hella356 said:
No WiFi calling, I assume?
Click to expand...
Click to collapse
correct
I am downloading the ROM. I am halfway through. I will post my comments! Thanks a lot. I have really been hungry to taste TW Lollipop on SGS4.
EDIT:
The ROM is now my daily driver. Thank you all for the hardwork. I found a fix for the security notice bug. I installed titanium backup and with root privileges uninstalled security agent log and that was all. There was no annoying security alert afterwards.
Camera works fine except dual shot.
The 's finder in the notification drawer is awesome. Mobile data, hotspot, wifi, great battery life. I will update you if I find anything else. I will be more than glad if we get the leaked update in a flashable zip format to make things much easier.
Nana Ayeh said:
I am downloading the ROM. I am halfway through. I will post my comments! Thanks a lot. I have really been hungry to taste TW Lollipop on SGS4.
EDIT:
The ROM is now my daily driver. Thank you all for the hardwork. I found a fix for the security notice bug. I installed titanium backup and with root privileges uninstalled security agent log and that was all. There was no annoying security alert afterwards.
Camera works fine except dual shot.
The 's finder in the notification drawer is awesome. Mobile data, hotspot, wifi, great battery life. I will update you if I find anything else. I will be more than glad if we get the leaked update in a flashable zip format to make things much easier.
Click to expand...
Click to collapse
I will upload a new version of the backup with SecurityAgentLog removed. Good find, thx.
As for a flashable zip, I prefer backups as they retain samsung factory permissions and selinux contexts better than an updater script. A good updater script can get close but a backup is a mirror image of the Odin flash.
Edit: Updated
muniz_ri said:
I will upload a new version of the backup with SecurityAgentLog removed. Good find, thx.
As for a flashable zip, I prefer backups as they retain samsung factory permissions and selinux contexts better than an updater script. A good updater script can get close but a backup is a mirror image of the Odin flash.
Edit: Updated
Click to expand...
Click to collapse
I can't wait to have that update the SecurityAgentLog removed. I have subscribed to this thread so I will receive an alert once you update it. I have still not had any issues after using it for almost 24 hours. So stable. It's indeed a daily driver. Thank you for your commitment to developing our S4.
EDIT:
I did not see the changelog earlier. Thanks for removing the security violation message.
Sorry for my question...but, am new with kernels, FW, etc on Samsung devices.... I got S4 Tmo...NH7, no root, wifi doesnt work...to flash this Leak Backup first I need to flash Leak Firmware, root (Chanfire o TWRP in Odin), then into recovery restore this backup or with NH7 rootting my devices can I restore the backup? Jej sorry for my english...
great job
dears,
many thanks 4 ur great effort, its real awesome
after install the leak can go back to my previous rom 4.4.4 when i need

Categories

Resources