Related
Hi guys. Thinking of installing the Leedroid ROM on my phone. Currently have Android Revolution HD and as you might know a few hours ago I went through some troubleshooting that had me praying to God Almighty because I'm a bit of a noob and I got really worried. Lol
Anyway, I know how to flash ROM's and Radios but how do I flash kernels and ROM "Extras"?
It was flashing an "Extra" that got me in the problem into the mess in the first place so I just wanted to confirm how to do it properly. Also, is flashing the kernel as simple as flashing a ROM? ie:
-Boot into CWM
-Nandroid Backup
-Wipe All
-Install new ROM
-Make sure it all works
-Back into CWM
-Install kernel zip from SD card
?
Thanks very much guys.
When I installed leedroid I installed rom then straight after the kernal without even rebooting. Worked fine for me.
I'll give it a shot later. But still how do I flash extras? Like a Sense 3.0 lockscreen for Leedroid?
Put it on your ssd and open it up in a file explorer (think leedroid has astro) and just run it and it will install.
If that doesn't work for an extra then boot into CMW and install it via zip, but if I recall correctly that won't work for the lock screen and has to be done via opening it up in a file explorer.
If the addon or kernel you've downloaded is a zip file, the easiest way to be sure it's flashable in CWM is to open it up in 7zip, WinRar, etc. and see what's inside. If there is a folder called "META-INF" then you know it can be flashed by CWM.
Most zips are CWM flashable, but some won't be, especially fonts, bootanimations or splash screens. There are usually instructions in the threads for these, though.
Kernels are often built in to the ROM zip, but if you want to change your kernel I recommend jkoljo's tool:
http://forum.xda-developers.com/showthread.php?t=852357
I'd also suggest doing a nandroid backup after flashing the ROM and making sure it all works, before flashing anything else, especially with some of the addons that are still in development. It just gives you a bit more security if you need to roll back.
(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
hi im a noob when it comes to phones, normally ill take it to a shop who will find one and install it for me, but i feel like trying this myself
are firmware in general like OSs? are kernels included as well or do i have to look for them? can I use any of them from any country? i dont mind resetting internet/MMS since theyre easy. im talking in computer terms to show how noobish i am
since i cant ask questions on the 'minimal by Judas' thread ill ask it here. is the 1.6 download a full OS with hardware stuff included or is it like a patch where i have to install that on top of an already working MG2? im interested in the zero patch since it removes most bloats, is it another OS or a patch on top of the minimal?
if it isnt too troublesome could someone write up a small walkthrough on using the aroma installer?
if you are alredy on MG2, you should have a working kernel for the minimalzero rom. alternatively you can use D-kernel.
as for the firmware itself, it's like an os. the package is a full rom (system installation, so installing it will first wipe your current system and then recreate it from scratch.
stuff like wifi passes and mms are on data tho, so u will keep that
for aosp based roms tho, the kernel needed will be included in the package, and a data wipe is required as well.
Flashing anything should be done by first flashing a temporary CWM via the stock recovery (look for temporary CWM by shaan in the development section) and then flashing zips from the temporary cwm once itl oads.
im still using stock 2.3.6 that came with the phone, would i need to install another firmware before hand?
and could i have some help finding an older version of CWM? weird thing is i rooted my phone but CWM is still not onstalled. ive reset my phone a lot, installed a few XXLD8 with CWM, tried to onstall standalone CWMs but none of them seem to work (failed to verofy whole package thing), tried via rom manager and it gives me the 'failed to verify whole package' thing.l
i even read a tutorial on that but its still not getting me through it
do i need CWM installed before i can upgrade using aroma/odin? can i use TWRP instead of CWM?
1. Follow this http://forum.xda-developers.com/showthread.php?p=43001497
2. Get temp CWM 6 (by Shaaan) then copy to external sdcard.
3. Reboot to recovery(you will be in stock) and chose third option from top (the line has an 'update'in it)
Find the temp CWM (will be named update.zip) and flash.
3. Make sure minimal zero file in in external/internal sd then chose flash zip from sdcard in temp CWM. And follow instructions in judas77's thread
EDIT: in 2: use power button to select
Sent from my GT-I8160 using xda app-developers app
temp CWM is working
what are the requirements for minimal/zero? im following the 'all galaxy ace 2 jelly bean firmwares' and the newest reply i saw was a person who downloaded an MF2 but requiring an MF1. seeing how zero has an MG1 CSC version and mininal has an MG2 does that mean zero is a requirement of minimal or are they both standalones? i also read elsewhere that in order to install an MG youd have ti install earlier firmwares, is that true?
sorry for such noobish questions
You can flash MB4 then MG2 to ensure 624mb ram, if you flash mg2 only most like get only 482mb ram. Follow guide to get 624mb ram on any jb rom if you have only 482mb ram after flashing your desired fw.(mc8,mg2 etc). Minimal 1.6 and minimal zero are standalone roms.
EDIT: CSC does not really matter unless you want to update through kies (what for? Use odin) and you dont need to flash another firmware just for mg2.
Sent from my GT-I8160 using xda app-developers app
thanks for the replies, theyre helping a lot
theoretically if i wanted to skip downloading other firmwares, what files for the MG2 would i have to install manually? even without a complete MG2 i could still get in to download/recovery to install them? ive so far found kernels and the 628MB (from szabys signature), would those be enough?
if i wanted to go down this road that means installing the OS first then the others right, will the order count?
*edit*
about the different CSC versions, i thought other settings would be affected as well, so its just update over kies right
Just find any fw you like (i use mg2, but may not be best either, your choice ) then flash with odin under PDA(remember to extract the .zip to obtain the .md5) different csc dont seem to do any harm for me and i dont think it should
EDIT: you must wait for the whole flashing process in odin to finish(although i have no idea what happens if you dont). Once its booted you can just head to recovery and update to temp CWM then follow instructions to flash minimal
Sent from my GT-I8160 using xda app-developers app
thanks for all the help, im not blaming you since my stupidity did it -.-
ATM i 2/3 bricked it (only download mode)
hoping the staffll keep this open since im on a side questish
If you can access download mode flash md5 again
You can ask in Q & A(new) i go there sometimes, if i can help i will
Sent from my GT-I8160 using xda app-developers app
thanks again, im currently torrenting the MG2 from szabys sig, will try flashing via odin once its done
heres the thread if youre interested http://forum.xda-developers.com/showthread.php?t=2441429
update
i feel like an ass asking how do i use this and that, but in the end i ended up flashing it to stock MG2, hope theres no hard feelings
Nope. Glad your phone works well . Just ask in Q & A next time
EDIT: but you would probably wanna learn how to flash cm10/ 4.2 roms. Stock jb is so hopelessly slow you could downgrade to gb
Sent from my GT-I8160 using xda app-developers app
again thanks for the tip, id probably try CM10.1 B2 i found on bagnzors site (full download thing ~200MB), seeing how i rarely use the things he said arent fixed yet id just jump right in
im currently using zero, do i have to reflash MG2 first or can i install it on top of zero?
littledude072 said:
again thanks for the tip, id probably try CM10.1 B2 i found on bagnzors site (full download thing ~200MB), seeing how i rarely use the things he said arent fixed yet id just jump right in
im currently using zero, do i have to reflash MG2 first or can i install it on top of zero?
Click to expand...
Click to collapse
flashing on top works fine
dont know why i waited almost a year to root but honestly CM10.1 handles like GB (both using under 200MB, whereas 412/zero uses 300, all debloated)
but there are 2 problems i cant solve, it turns on when charging and 'package access helper/fused location' always running, other than those awesome mod
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Making progress but still confused...?
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
BrianN_Cols_OH said:
Hi Guys (and Gals),
I'm sooooo tired. I have a couple of Sprint D700 phones that I am trying to customize and I'm stuck. I've been reading forums and Googling for hours over several days and weeks and I just can't seem to get to the next step. FYI, I'm a software developer by trade, so I'm frustrated that I cannot figure this out.
I'm trying this on a guinea pig phone first (not currently active on an account). So, it has all of the latest Sprint upgrades. Then, I did a factory reset. I was able to gain root access using Framaroot 1.6.1. Then, I downloaded Root Explorer, Terminal Emulator and ROM Manager.
I want to experiment with some Custom ROMs, but everything I do so far is blocked by the existing stock recovery (3e?). From what I've read, I need CWM 5.0.2.7. So, I tried to load that version of CWM via ROM Manager. However, it will not boot to CWM - it keeps going into stock.
Then, I recently read something that the Samsung phones need an updated Kernel in order for the CWM install to work? And if I understand correctly, the only way to do that is via ODIN (which I've also downloaded on my PC)? Or is there a version of recovery manager that has a digital signature that will pass the check by the stock recovery and let it install?
I've tried to find some versions of Kernels and really don't know what to try - a lot of the download links are dead.
I want to hang on to these phones a little longer because I like the size and the qwerty keyboard, so I've refused to give up so far.
I realize that the answers are somewhere in these threads, but I am having trouble sifting through information that is sometimes outdated or has dead links to files. Please help - what do I need to do next?
Thanks so much!
Click to expand...
Click to collapse
Success - Finally got CWM - Ready to play with ROMs
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
BrianN_Cols_OH said:
OK, I have just tried to ODIN a new Kernel. I tried Shadow Kernel v2.0. Everything appeared to work properly in ODIN. However, when I reboot, the phone still goes into the old recovery (not CWM). When I look in the settings, the Baseband and Hardware versions both say "Unknown".
My current build is GINGERBREAD.FC09, Firmware 2.3.6.
What Kernel do I need to flash?
Click to expand...
Click to collapse
BrianN_Cols_OH said:
OK, I finally got to where I needed to be. I'm not sure if I'd ODIN'd incorrectly or what. However, I did a factory reset from the stock recovery. Then, I tried ODIN with Shadow again. This time I did it with ODIN 3.07 instead of 3.09. I don't know if I did something wrong with the 3.09 version - the button names were abbreviated - maybe I hit the wrong selection for "PDA".
This time it booted right into CWM 5.0.2.7. Geez, I'm supposed to be smarter than this.
If anyone is starting this fresh and has this phone with all of the latest OTA updates (no root - stock everything), then I think this is the path to take. For those of you that have read my rantings, thank you for your time. Any comments (including humor at my expense) will be joyfully appreciated.
Click to expand...
Click to collapse
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
More updates...
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
nikon120 said:
Steps to Root FC09
Odin v3.09 doesn't work that well with the D700, as that version no longer has the "PDA" field. Version 3.07 and lower work fine.
Flashing a kernel will not also flash a recovery; unless the kernel dev packaged CWM or TWRP in his zip file. The kernel thread will state if it comes packaged with a recovery.
Typically, all custom roms for the Epic are pre-rooted. So you would only have to download Superuser or SuperSU from the Play store to keep it updated.
Click to expand...
Click to collapse
New issues - need help with CM 10.1...
OK, I've made progress and learned a lot. Essentially restored the bricked phone by going back to stock. Then, I started my process again.
- Used ODIN to flash rooted kernel with CM 5.0.2.7
- Flashed Cyanogenmod 10.1.3
- Flashed correct Gapps (dated 8/12 I think)
Software great, but modem not working. So, then I found the forum for the NS4G modem patches. I've tried several and I did get one to work. But, the latest version of CM 10.1 has SU built-in. When I do the modem repair, it breaks my SU root.
I've tried the nitest kernal (by the way, I like the TWRP recovery better than CM - it). I've tried several of the modem patches.
Do I need to go back to a certain stable version of CM 10? What order to I need to apply things?
Here's what I have on the phone at the moment. It has SU/root but no modem.
- Android 4.2.2
- 3.0.79-JB42-nitest-nr kernel
- CM 10.1-20130526-NIGHTLY-epicmtd (although I've tried several other builds)
I was sooooooo close. Please help? How do I get my modem working AND keep my SU/root?
BrianN_Cols_OH said:
Thanks for that addtional info. I will get rid of my version of ODIN 3.09.
So... I am doing all of this on a "practice" phone - one that is spare and not currently connected to Sprint. It appears that what I did may have wiped the /EFS folder and no, I don't think I backed it up. I didn't back up anything on this phone because it was just a practice phone (the kind of mistake you only make once). So, my phone does not display an IMEI (MEID).
Do you think that restoring a stock image and starting over will help me restore my NV_DATA.BIN info? I have another one of these phones (currently active), but I'm guessing that I cannot just steal the NV_DATA.BIN file from that phone and edit the contents to change the IMEI and MAC Address, etc. That would be too easy.
Is there any way to do a new gen of the NV_DATA info? I will try ODIN back to stock tonight when I'm home, but in the mean time if anyone has any suggestions let me know.
This is quite a learning process. I'm getting much more familiar with how these things work now, so that can only be good.
Click to expand...
Click to collapse
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Modem issues...
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
nikon120 said:
ROM is not dependent on modem. Modem is dependent on kernel patches though.
Be sure you have a compatible kernel for your modem, whether NS4G or Epic modem. Are you using Odin or recovery to flash your modem? I've read in the NS4G modem thread a while ago, that users had to flash the modem multiple times to get it to stick. I'd suggest keep flashing and checking.
Here is SuperSU v1.69 download link. Place on SD card and flash in recovery once you get modem working.
Click to expand...
Click to collapse
More info...
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
BrianN_Cols_OH said:
Thanks for the response. Am I wrong, or are there kernel patches that are part of the CM 10.1 install? So, I do understand what you are saying - that the ROM itself shouldn't break the modem. However, I believe there were some kernel patches in the CM install - maybe I'm totally wrong?
When I did have one of the modem patches working, I tried to separately download SuperSU, but it didn't seem to work. I really liked seeing the SU functionality built in to the ROM (it is available right from the settings menu near the developer options). Is it actually part of the kernel or part of the ROM? When it was broken, it was as if I still had root access but couldn't use it because there wasn't an SU manager. So, I don't know that root was broken so much as the SU piece that seems to manage it.
In any event, I suspect you are right about needing ODIN for the modem. So, what file should I flash as the "modem" in ODIN? I think that is the next thing I should try as I was only doing the modem patch via recovery before.
Also, is there a tuturiol somewhere that would help me understand the entire Android file system? I am a developer by trade, but I'm not super-experienced in the Linux (and Unix) realm. I would like to read up on things like
- how the storage is partitioned
- what files are part of the kernal
- what files are part of the modem
- what files are part of the ROM
- what files are part of the recovery platform
I'm guessing I won't find a CONFIG.SYS and AUTOEXEC.BAT - LOL.
Thanks so much for replying - I'm still learning and hopefully I'll be able to give back to others once I become an expert. I apologize as I am probably asking questions that have been answered, however I've really poured through several forums and there are so many posts that I may have missed just what I needed. Once I've mastered this phone I may move on to my daughter's GS2 and maybe think about a GS3 or GS4 in the future...
Click to expand...
Click to collapse
Modem.bin
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
BrianN_Cols_OH said:
OK, after some further reading, I believe what I need to try next is to load a new modem.bin file using ODIN. I would use "Phone" (not "PDA").
I think I downloaded 2 different modem versions that hopefully have what I need. I can't check them at the moment, but will try one of those tonight. if you have any suggestions as to which modem to use, please let me know (my kernel version is shown previously).
I also found some good info on the Android file system and I understand a little better how the paritions work for kernel, system, storage, cache...
Also, what is this JB Big Mem fix that I've seen in some of the patches?
Click to expand...
Click to collapse
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
BrianN_Cols_OH said:
Actually, the 2 modem/radio files I have are zip files and there is no modem.bin file inside. What exactly do I flash with ODIN?
Click to expand...
Click to collapse
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Thanks!
Great, thanks so much. I will look for the modem files a little later.
nikon120 said:
Yes, use the Phone slot for flashing the modem.bin.
As for the kernel patches, there are swap files that you can flash in recovery that will use the proper blobs for your preferred modem type. Typically, roms will state in the thread title if they are NS4G or not. Always assume the ROM is Epic modem.
BigMem is for capturing video from the camera app.
Give me about 2 hours. I'll reupload all modem files to my devhost account, located in my signature.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
BrianN_Cols_OH said:
Great, thanks so much. I will look for the modem files a little later.
Click to expand...
Click to collapse
Ok, all Epic modems and NS4G modems are reuploaded. I also included the swap files for each. Everything with (Flashable) means to be flashed within recovery. Those swap files are the blob changes I mentioned earlier. This way you can swap modems using recovery, rather than relying on Odin.
Everything in the Odin folder can be placed in the phone slot and flashed as-is. (No need to extract the .bin file from the archive.)
As for the built-in root manager in CM, I'd try reflashing the rom first, and then messing with the modem.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S2 Epic 4G Touch - SPH-D710 (d710)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
First off let me say thank you for bringing this amazing recovery to our phone I just flashed it and everything seems good so far,,i'll let you no if i run into any issues
Well using this recovery on mokee the rom will not boot just goes to a black screen so i guess it has to be built with the mokee stuff if you can give me the issues your having i can get it to work,,unless you can give me the source or let me know how to get it and i can make a build using the mokee trees
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Does this work for touch wiz?
It is only for CM based ROMs under KitKat
AOKP ROMS could or could not load
TW will not
For non working roms, you just have to ask someone to repack it with matching kernel zImage
This recovery is pretty awesome, flashed CM11, Vanir, & Commotio successfully.
My new default recovery. :]
HighxVoltage said:
This recovery is pretty awesome, flashed CM11, Vanir, & Commotio successfully.
My new default recovery. :]
Click to expand...
Click to collapse
What was your install method ? I'd like to try it . Did you just flash it with the cwm you already had ? Next question . After you install it and when you flash another rom does it get over written or can you reinject it each time ? thanks
SuperGoober said:
What was your install method ? I'd like to try it . Did you just flash it with the cwm you already had ? Next question . After you install it and when you flash another rom does it get over written or can you reinject it each time ? thanks
Click to expand...
Click to collapse
Yes. & it does get overwritten, I just flash it after flashing the ROM / Gapps. No biggie though. Haven't found an option to make it stick after flashing a ROM like in TWRP.
Sent from my SPH-D710 using Tapatalk
HighxVoltage said:
Yes. & it does get overwritten, I just flash it after flashing the ROM / Gapps. No biggie though. Haven't found an option to make it stick after flashing a ROM like in TWRP.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I seem to be in a vicious cycle . Recovery flashes fine . When i reboot screen goes black after splash screen . Go back into recovery have to reflash rom but then reflash this and back to black screen on reboot . I don't get what the advantage is if you can't stick it and be able to boot . It would be great if it would stick and boot .
Phil3759 said:
It is only for CM based ROMs under KitKat
AOKP ROMS could or could not load
TW will not
For non working roms, you just have to ask someone to repack it with matching kernel zImage
Click to expand...
Click to collapse
Can you build the recovery using this kernel and vendor files because when CM made there graphics update it caused video issues on our device this kernel and vendor revert that update
https://github.com/mtb3000gt/android_kernel_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710-common
mtb3000gt said:
Can you build the recovery using this kernel and vendor files because when CM made there graphics update it caused video issues on our device this kernel and vendor revert that update
https://github.com/mtb3000gt/android_kernel_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710
https://github.com/mtb3000gt/android_vendor_samsung_d710-common
Click to expand...
Click to collapse
yes, but please, no need to post multiple times
once is enough
do i go to recovery and flash this? i am on android 2.3.6, the current recovery only has 3 menu items to do (flash, wipe and wipe)
my goal is to flash the lastest 4.4.3 rom
When I try to flash philz_touch_6.19.3-d710.tar.md5 with Mobile Odin, I get the error "partition could not be found in file". I've done a hash check on the file.
unknownsoldierx said:
When I try to flash philz_touch_6.19.3-d710.tar.md5 with Mobile Odin, I get the error "partition could not be found in file". I've done a hash check on the file.
Click to expand...
Click to collapse
Did you ever get the right file? If not, let me know. I tried to flash it through Mobile Odin and it dosen't even see the files. The best bet is to boot into recovery, flash Philz, reboot into recovery, flash until tired.
Never did get philz_touch_6.19.3-d710.tar.md5 to work. The zip version flashed fine from StockCWM-EL26. I was hoping to get the tar.md5 to work so I could skip StockCWM-EL26.
Then I learned Philz doesn't work properly for nandroids, Since I need to use StockCWM-EL26 for nandroids anyway, the tar.md5 version of Philz is not needed.
unknownsoldierx said:
Never did get philz_touch_6.19.3-d710.tar.md5 to work. The zip version flashed fine from StockCWM-EL26. I was hoping to get the tar.md5 to work so I could skip StockCWM-EL26.
Then I learned Philz doesn't work properly for nandroids, Since I need to use StockCWM-EL26 for nandroids anyway, the tar.md5 version of Philz is not needed.
Click to expand...
Click to collapse
OK. If your on stock, that should be TouchWiz. I would try to install AGAT's as a regular recovery. All the TW ROMs I flashed, had AGATs already installed. The only time I had to use EL26 or EL29 was to go to a different ROM. Have you tried his repository?
here ya go.
http://www.rwilco12.com/downloads.p... (SPH-D710VMUB)/Kernels/Stock (TW) Kernels/JB
CWM-EL26 has worked fine for me, so I haven't used Agat's, Doesn't matter since I don't keep anything installed. I flash a recovery, flash a rom, to see if things are working well enough to use. After not being able to get text or mms to work reliably, I go back to stock completely. GB28 everything.
If there was a custom recovery with a GB28 kernel, I'd keep that installed.
unknownsoldierx said:
CWM-EL26 has worked fine for me, so I haven't used Agat's, Doesn't matter since I don't keep anything installed. I flash a recovery, flash a rom, to see if things are working well enough to use. After not being able to get text or mms to work reliably, I go back to stock completely. GB28 everything.
If there was a custom recovery with a GB28 kernel, I'd keep that installed.
Click to expand...
Click to collapse
Like these?
GB27 will work flawlessly on Virgin and Boost models
Still having a ton of problems with this recovery. It's the only one I can find that will flash the Liquid Smooth rom for me.
The backup/restore seems to be completely broken. Others have said to use another recovery for that. So I flash a recovery, reboot to that, then flash Philz, then flash KK rom.
Today I flashed Liquid Smooth, had some problems with it so decide to restore a backup. I booted into Philz, used it's convenient "wipe for new rom" to make sure everything was clean for restore. Then I needed to flash the recovery I used to make my backup, but when I tried to do that I just got an error 7. I tried flashing different recoveries, roms, modems. All gave errors.
Saw a tip suggesting to untick the "Don't allow old update-binary " option, but that didn't fix it.
Had to hook it up to the computer and flash a recovery using odin.
This
Phil3759 said:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
download link doesn't work any more.
Can anybody please provide me with an alternative download link?
Thanks!
I found working versions for the SPH-D710 here
I just flashed CM11 with the philz_touch_6.19.3-d710.zip and it worked just fine (I think the lower version did not work ...).