Hi,
This is an odin .tar prepared with the stock AT&T Kernel, System, and Recovery.
Flash it from odin using the same instructions as my root thread
After flashing, you may need to boot into recovery by powering off, holding vol up + vol down, and holding power until you get into recovery. Then perform a factory reset, this should get you up and running after most brickery.
Note that this is a large file (~450MB), please spare my web host if you don't particularly need it
Download .rar here
Below are stock kernel-only odin tars:
AT&T stock kernel-only odin pda tar
TELUS stock kernel-only odin pda tar
Bell stock kernel-only odin pda tar
Rogers stock kernel-only odin pda tar
Don't forget the donate link in my signature if you find this useful
Absolutely amazing work man. Awesome.
You're the man. Already brought root, overclock, and odin back to stock. You make me want to sell my infuse and upgrade soooo bad. I just played with the note in store today and can't wait. Keep up the great work! Glad to see hard working devs on this device.
Man, you never fail to amaze me... r u single? Lol j/p but awesome work!
sent from AT&T Samsung Galaxy Note Dual Core 1.83 GHz
I wonder that sometimes myself maxjivi. lol
Upload complete!
Da_G said:
Hi,
This is an odin .tar prepared with the stock AT&T Kernel, System, and Recovery.
Flash it from odin using the same instructions as my root thread
After flashing, you may need to boot into recovery by powering off, holding vol up + vol down, and holding power until you get into recovery. Then perform a factory reset, this should get you up and running after most brickery.
Note that this is a large file (~800mb), please spare my web host if you don't particularly need it
(link pending, uploading)
Don't forget the donate link in my signature if you find this useful
Click to expand...
Click to collapse
dude you are amazing, i did pushed the thank you button but i still want to say thank you for the times and effort that you put in all this work.
any word on when we can try to flash the proper modem on this phone to get it to work on T-MOBILE.
Been on android awhile but not heavily in the development realm. Does using this root prevent OTA updates? I'm happy with performance so far but hate the ATT garbage. At the same time, I'd like to have the official OTA ICS upgrade when its released. Thanks.
Sent from my SAMSUNG-SGH-I717 using xda premium
Going by past experience, rooting does prevent OTA updates in some cases, but restoring to stock via odin first should take care of that when the time comes.
We will also presumably have the official ICS upgrade available as a signed odin tar that won't trigger the flash counter.
I presume this will not work with the rogers galaxy note?
I am willing to provide files from my device if necessary.
Sent from my SGH-I717R using XDA App
No, (it would, but it would leave you with an AT&T system)
We have the rogers kernel, but not /system or recovery currently. (although recovery is similar enough to not really matter)
Is there anything i could do to help? Files to provide from my note? (i717R)
Sent from my SGH-I717R using XDA App
From adb inside booted ROM:
(note system.img will be 1GB, compress it before upload)
Code:
adb shell dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
adb shell dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
If you have installed my rooted recovery or kernel, don't bother pulling those images as they will have been overwritten. Currently we have everything for AT&T, Rogers kernel, and TELUS kernel. Need Rogers system/recovery, bell kernel/recovery, and telus system/recovery to build stock archives for those.
I posted the telus kernel in another one of your threads
Thanks！
From wm6.5 to Android now, we have to be crazy mobile phone maker！
Our steps are basically the same！
Da_G said:
From adb inside booted ROM:
(note system.img will be 1GB, compress it before upload)
Code:
adb shell dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
adb shell dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
adb shell dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
adb pull /sdcard/boot.img
If you have installed my rooted recovery or kernel, don't bother pulling those images as they will have been overwritten. Currently we have everything for AT&T, Rogers kernel, and TELUS kernel. Need Rogers system/recovery, bell kernel/recovery, and telus system/recovery to build stock archives for those.
Click to expand...
Click to collapse
I haven't installed/ran your rooted recovery/kernel but I know I require ROOT in order to complete the above commands... how can I accomplish this?
Edit: nevemind
No root required just the recovery
sent from AT&T Samsung Galaxy Note Dual Core 1.83 GHz
I attempted to pull the system and recovery with the above commands but i get cannot open for read: permission denied
With that being said therefore there will be nothing to pull.
NOTE: (pardon the pun) my device is obviously not rooted.
Sent from my SGH-I717R using XDA App
I've already flashed the modded recovery for my Rogers i717 to get the radio, so no go there. I could flash the root kernel and get a system image, but I have no idea where to host it.
not the fastest mirror but doing what i can to help out its off my home server so be kind
ftp://www.slimeinside.me/Samsung/AT&T Galaxy Note/Stock odin rar/pda-odin-att-stock.rar
Wow! Gr8 Da_G! Now i have goodies to make Infected Custom Rom Make that Cwm recovery as told in Pm! N i'll b on my work as i promised Good Luck!
Related
i want to use the MODEM.BIN of my provider's ROM in the cognition 1.31 ROM.
how can i extract it from the provider ROM and then flash it to the cognition?
is there a way to get to it from root explorer and just replace it or i need to extract from the provider ROM and flash to cognition?
what is actually the path of the MODEM.BIN in the sgs 2?
i tried looking for it manually but i couldn't find it.
Sent from my GT-I9100 using XDA Premium App
Unzip extract modem.bin.
Flash modem via Odin as phone.
JJEgan said:
Sent from my GT-I9100 using XDA Premium App
Unzip extract modem.bin.
Flash modem via Odin as phone.
Click to expand...
Click to collapse
im not sure you quite got it.
i need to extract the modem file out of a ROM that i will install on my sgs 2 that's is the official ROM of my service provider.
and i dont know how to find it inside the phone
I've got it right? You do have an official ROM, you wonna take modem.bin out, save it, then install another custom rom and flash it back then? Right?
Ivan_Belarus said:
I've got it right? You do have an official ROM, you wonna take modem.bin out, save it, then install another custom rom and flash it back then? Right?
Click to expand...
Click to collapse
exactly!
got any idea how can i do that?
Nope, as I know it's impossible - modem.bin is an image to flash hardware part and you cannot take it out. Even CWM doesnt backup and restore modem.bin.
It's like a new firmware for modem - you can flash it, but you cannot restore it back.
And what is your reason to do that?
im know that if ill ba able to change this modem my battery will improve dramatically.
how do i know that?
the service provider ROM is 2.3.3 and full of things that make your battery drain.
mine is cognition 1.3.1 and very slim with almost no battery drain apps and juice defender and setcpu on(which saves a lot of battery).
now i compared mine with a regular one that has their official ROM and i get maybe 2 hours more on regular use. also there's a big problem with all radio waves and reception.
now if you look at this:http://www.villainrom.co.uk/forum/s...II-Shipped-Radio-Collection?p=42051#post42051
pulser somehow extracted modems so people would be able to flash it. i wonder how he did it
As I C, he extracted modems from flash packages and reuse them in other reassembled packages then. It's pretty easy.
Ok, it is NOT IMPOSSIBLE. You just need to be rooted.
With root, run adb and use:
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Click to expand...
Click to collapse
Electroz said:
Ok, it is NOT IMPOSSIBLE. You just need to be rooted.
With root, run adb and use:
Click to expand...
Click to collapse
Yep, it works well! I don't need it, but tried successfully. Good job,man. I didn't know.
Electroz said:
Ok, it is NOT IMPOSSIBLE. You just need to be rooted.
With root, run adb and use:
Click to expand...
Click to collapse
now i just need to learn how to use adb
well its worth it, ill get going to it.
btw, if i did that command from (CMD)adb shell, what happens then?
or its much more complicated than this to extract it.
thanks anyway
You would need to do:
adb shell
su
dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
exit
exit
Click to expand...
Click to collapse
your modem.bin file will then be on your internal phone storage.
Electroz said:
You would need to do:
your modem.bin file will then be on your internal phone storage.
Click to expand...
Click to collapse
my friend. thank you so much... i really appreciate it but if you can 2 more question.
using this way in adb is the basic?its just like any other command over there?
technically if i know all the commands-does it means using adb is this?
and you got any idea how to push the modem file into cmw zip?
eeebbr said:
my friend. thank you so much... i really appreciate it but if you can 2 more question.
using this way in adb is the basic?its just like any other command over there?
technically if i know all the commands-does it means using adb is this?
and you got any idea how to push the modem file into cmw zip?
Click to expand...
Click to collapse
It would be easier to just use 7zip (or similar) tar compress the modem.bin (-> moden.tar) file so you can use ODIN to update your radio on the ROM of your choice. Once you have modem.tar - add that to the PDA field on ODIN and START. Of course all of the prequisites are required. Reboot your phone to download mode, ensure you have working USB drivers, etc.
Google search will reveal all you need to know about creating the file you can flash from recovery. Honestly I think it is way easier to just do this through ODIN. Good luck.
eeebbr said:
my friend. thank you so much... i really appreciate it but if you can 2 more question.
using this way in adb is the basic?its just like any other command over there?
technically if i know all the commands-does it means using adb is this?
and you got any idea how to push the modem file into cmw zip?
Click to expand...
Click to collapse
You may flash it with Odin
Generally, all files are to be added to tar must be zipped with following commands:
tar -H ustar -с modem.bin > modem.tar
Then, if you'd prefer to have md5 signed file do the following
md5sum -t modem.tar >>modem.tar
mv modem.tar modem.tar.md5
That's all, then you may flash it with Odin as phone part
Extract modem from file put modem in Phone flash via Odin .
Worked ten times today .
jje
This is interesting thanks so If I root my phone and then still with provider ROM installed I can extract the modem.bin file and use it another ROM as well?
What are the pre-requisites in ODIN you mention when flashing it?
eeebbr said:
im know that if ill ba able to change this modem my battery will improve dramatically.
how do i know that?
the service provider ROM is 2.3.3 and full of things that make your battery drain.
mine is cognition 1.3.1 and very slim with almost no battery drain apps and juice defender and setcpu on(which saves a lot of battery).
now i compared mine with a regular one that has their official ROM and i get maybe 2 hours more on regular use. also there's a big problem with all radio waves and reception.
now if you look at this:http://www.villainrom.co.uk/forum/s...II-Shipped-Radio-Collection?p=42051#post42051
pulser somehow extracted modems so people would be able to flash it. i wonder how he did it
Click to expand...
Click to collapse
Dear,
modem.bin is the combine file,when we flash it, it is extract to the hardware of device. you can't fine modem.bin from the phone but if you want to get it, use mtk droidtool for backup. this software gives you modem.bin but you can't flash it via odin. you can flash via sp flashtool with scatter file.
Try mtk droidtools software but it was made for MTK android devices may be it work for you.
but it confirm you can get modem.bin only way of backup which create complete backup. but you can find modem.img from phone.
system/etc/firmware/modem.img
Why are you necroing a 2.5 yr old thread ?
What I did was even simpler. I just unpacked the modem.bin file from zipped samsung image.
Multiupload links removed - MU seems to be gone forever. I will repost an unrooted UCKH7 package in the next week along with a modem package - Until then, use the rooted package and then remove:
/system/xbin/su
/system/bin/su
/system/app/Superuser.apk
And then reboot
I have uploaded Heimdall/Odin flashable kernel ,rooted system, and modem images to dev-host. This should be sufficient to unbrick most hosed-up phones, as long as you didn't flash a bad .pit. Note that after flashing this, you might need to wipe data depending on what ROM you were coming from. If you bootloop or things behave wacky, enter 3e recovery (stock kernel means stock recovery) and do a Wipe Data/Factory Reset. If you are reverting from UCKK6 back to UCKH7 you MUST perform this step or wifi will not work. If you're coming from a 100% stock ROM and only using this to gain root, you should be able to keep all your data and not need to wipe.
The kernel is 100% bone stock, the system image is stock except that it is pre-rooted (su binary and Superuser.apk)
I am including the modem in a separate package since that goes in a separate modem slot, and I don't want to reupload a 200+ MB file if I don't have to.
The kernel + rooted UCKH7 system package is here: http://dev-host.org/UWm
Kernel + cache + rooted UCKK6 system package: http://dev-host.org/8LA
Download, extract the package using 7-Zip, which can be downloaded from http://www.7-zip.org/download.html, then either:
1) (Tested on Linux, should work on MacOS) - Extract the tar and flash the components with heimdall from the commandline as follows:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
for the kernel + system package, and:
Code:
heimdall flash --modem modem.bin
for the modem package
I've never had good results with the Heimdall Frontend GUI.
2) (Tested by Jivy26 for kernel + system, untested for modem) - Flash the .tar in Odin. I'm a Linux user, so I have only tested this with Heimdall so far.
Kernel + system package goes in PDA slot I believe, modem package in Phone slot.
If you are wondering why I used 7-Zip to compress the archive:
7-Zip provides better compression ratios than Zip
7-Zip is open source unlike RAR
If it were a zip file, some doofus would probably think it was CWM-flashable and complain that it didn't flash.
Also - great thanks goes to Jivy26 for providing a stock /system dump. Without that it would not have been possible to make the system image or get a kernel dump.
Coming in the next few days - stock unrooted /system package.
Also just added - a param.lfs backup from my device. This is NOT contained in an Odin-flashable .tar file yet, I'll work on cleaning up my packages when I'm feeling better. I came down with a nasty cold a few days ago.
UPDATE:
creepyncrawly has written an EXCELLENT step-by-step guide for flashing this with Odin. The guide is at:
http://forum.xda-developers.com/showthread.php?t=1313659
In addition, he posted an Odin-flashable tar package for just the stock kernel, for those who want to do a ! removal. I have mirrored the file (I don't trust Dropbox for long-term hosting) at http://www.multiupload.com/MD7SMMNG24 - his original post is at http://forum.xda-developers.com/showpost.php?p=18535109&postcount=174
Awesome, thanks. Downloading now.
*If it were a zip file, some doofus would probably think it was CWM-flashable and complain that it didn't flash.*
LOL! Enough said right there. Thanks Ent!
Worked great with odin, thanks.
If one was to add the correct pit file to your package would that fix a bad pit flash, as well as fix if one had messed up partitions?
They would be useful for flashing back from cm7 wouldn't it? Or am I completely off?
Sent from my SAMSUNG-SGH-I777 using XDA App
dayv said:
If one was to add the correct pit file to your package would that fix a bad pit flash, as well as fix if one had messed up partitions?
They would be useful for flashing back from cm7 wouldn't it? Or am I completely off?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Flashed from CM7 using just the PDA
jivy26 said:
Flashed from CM7 using just the PDA
Click to expand...
Click to collapse
Was that without or with a .pit file?
Sent from my SAMSUNG-SGH-I777 using XDA App
With a good .pit file, yes it could recover from a bad .pit flash.
As far as going back/forth to CM7 - I believe that differences in architecture between the original GS and the GSII (mainly no FSR/RFS proprietary modules) make going to/from CM7 much less painful.
dayv said:
Was that without or with a .pit file?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Yes without a .pit file
thank you for all your work and for educating me. I will make sure and hit the thanks button next time I'm on a PC.
Wish we could hit thanks button from xda app.
Sent from my SAMSUNG-SGH-I777 using XDA App
Flashed w/ Odin...stuck in a boot loop. Any other suggestion? I had CM7 on there but had no sound when making calls. Tried to go back to stock...SOL.
Had the phone 9 hours and haven't been able to make a single call yet.
Drew489 said:
Flashed w/ Odin...stuck in a boot loop. Any other suggestion? I had CM7 on there but had no sound when making calls. Tried to go back to stock...SOL.
Had the phone 9 hours and haven't been able to make a single call yet.
Click to expand...
Click to collapse
Enter recovery (this kernel has stock 3e recovery) and wipe data/factory reset.
Power off (may need to battery pull), then:
Hold VolUp+VolDn
Push Power until the screen turns on
Let go of Power, keep holding VolUp+VolDn until you're in recovery
Entropy512 said:
Enter recovery (this kernel has stock 3e recovery) and wipe data/factory reset.
Power off (may need to battery pull), then:
Hold VolUp+VolDn
Push Power until the screen turns on
Let go of Power, keep holding VolUp+VolDn until you're in recovery
Click to expand...
Click to collapse
thank you!!! worked
Thanks for the Kernel work!
Will it hurt anything if I'm already rooted and SU'd with other kernel method or should I factory reset? Also out of curiousity will sgs kernel flasher work?
not rooted
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
drawde40599 said:
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
Click to expand...
Click to collapse
+1 thanks
10char
Not able to access the download site, could you please attache here?
mjgspr95 said:
Thanks for the Kernel work!
Will it hurt anything if I'm already rooted and SU'd with other kernel method or should I factory reset? Also out of curiousity will sgs kernel flasher work?
Click to expand...
Click to collapse
No, shouldn't hurt anything. Should only need to wipe if coming from a significantly different ROM such as CM7 or an I9100 ROM.
drawde40599 said:
do u have a version for odin without the root ? im looking for 100% stock out the box rom ? (future warranty purposes ) thanks
Click to expand...
Click to collapse
Yes, but I figured this would be more popular and uploading one of these takes an hour. I'll put up the unrooted stock in a day or two as I'm doing kernel work. However it's easy enough to unroot, just remove the two following files:
Code:
/system/app/Superuser.apk
/system/xbin/su
keeploading said:
Not able to access the download site, could you please attache here?
Click to expand...
Click to collapse
It's WAY larger than XDA's attachment limit, sorry, no can do.
You end up getting the phone Entropy? Thanks for this btw.
Hey kids! Don't know if anyone here knows me, but I am an ex avid Captivate user. But I've been out of the game for so long (exploring webOS and BBOS7) that I am very behind. Anyone kidn enough to post a link to the newest Odin? Also, what slot do .tar files go into? The first one, PDA?
EDIT: Opened the file, definitely PDA Still, anyone have a good link to a working Odin? I remember at one time some Odin versions worked really badly, and I used the original 1.00 but I heard there is a 2 and I'd prefer to use that with this new phone.
I made this because the existing rom (package_us2.3.5.tar.md5) being distributed around the fourms isn't working right for devices like mine.
Your phone should be rooted prior to doing this.
Make sure you have the same device info as mine before proceeding. I will not be responsible if you decide to flash this to a device that does not match my own. You have been warned.
DOWNLOAD HERE: http://www.sendspace.com/file/1y2ogi
This is for the Samsung Galaxy Player 4.0 (USA) (YP-G1CWYXAA)
Model Number: YP-G1
Firmware Version: 2.3.5
Kernel version: 2.6.35.7-G1UEKI8-CL562400 [email protected] #2
Build number: GINGERBREAD.UEKI8
Steps for flashing.
1.) Attach USB Cable and Put your device in Downloading mode (Hold Power + Vol Down)
2.) Download and run Odin 1.85
3.) Click on the button marked PDA and select the file named "yp-g1cwyxaa.tar" that you downloaded from the link above.
4.) Make sure that ONLY "Auto Reboot" and "F. Reset Time" are checked. (NO OTHER OPTION SHOULD BE CHECKED!!)
5.) Click on "Start" and wait for the process to finish. The process should take about a minute or two and finish with a green box saying "PASS!"
6.) When it has successfully finished, the device itself should reset. At this time you may unplug your USB cable.
7.) OPTIONAL: Press menu button > Settings > Privacy > Factory data reset (This will reboot your device, enter recovery mode, wipe all settings and reset everything to defaults, and then reboot your device once more automatically.)
8.) Enjoy your 100% working Samsung Galaxy Player 4.0 (YP-G1CWYXAA)
This is my first time doing something like this. I hope this works for all of you. Let me know if you have problems. Feel free to click the "Thanks" button if it works for you. =)
BTW. What would be the proper term for what I have created? Is this a "Stock ROM", "Recovery ROM", "Stock Firmware" I have heard it called many things.
I downloaded and installed your stock rom and it worked perfectly. The clock works find and the widgets that weren't working before are now working.
The only step I skipped was step 7 because I wanted to keep my apps/data. And I'm certainly following step 8.
Thanks a lot for your effort Kwipper (and the thanks button was clicked).
I am happy to see that this is working. I am actually quite surprised with myself that I was able to do this. About 10 days ago, I didn't even have an android device, or know anything about the platform. =)
Don't be so modest. You've solved a problem that I've had for over a month now.
I'm curious how you did this. Did you use adb from your PC to run the 'dd' command? I ran the 'dd' command using the Terminal Emulator app. Maybe this is why my factory.rfs didn't work.
I did a bit of searching around the fourms and came across this post.
http://forum.xda-developers.com/showpost.php?p=15804185&postcount=15
Then I used a program called Cygwin. Used it to navigate over to where my files were stored and typed in these commands.
tar -H ustar -c factoryfs.rfs zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Then I flashed it using odin.
I also noticed that if you were using the previous "package_us2.3.5.tar.md5" file to restore from, the MD5 of my file would not match up, and Odin would give off an error. So I removed the .MD5 from the extension of my filename and it worked.
I was wondering. Do you think I should include the .pit file as well? Mabye as a separate download?
Kwipper said:
I was wondering. Do you think I should include the .pit file as well? Mabye as a separate download?
Click to expand...
Click to collapse
They are all right here: http://forum.xda-developers.com/showthread.php?p=20259805
Important: if you are going to flash this ROM, make sure you do NOT choose repartition in Odin with the PIT file. This only contains the /system and the kernel, so repartioning the whole device will make your device unable to boot past recovery. Still waiting for a full stock recovery ROM with all the partitions and can use the PIT file...
Kwipper said:
...
BTW. What would be the proper term for what I have created? Is this a "Stock ROM", "Recovery ROM", "Stock Firmware" I have heard it called many things.
Click to expand...
Click to collapse
If I understand correctly, your ROM is rooted. If that's correct, you don't want to call that "STOCK ROM". Stock ROM usually refers to something exactly as it is shipped by manufacturer. I may call it "STOCK+ROOT" to indicate that things like superuser are already injected into the ROM.
EDIT: Reading your post again. I don't know why I had an impression that your ROM is rooted I suppose you did a dump using dd via adb shell, then it should be a STOCK ROM.
Hmmm... Is there anyway to confirm if it's rooted or not? I suppose that if I remove the root and then reflash it using odin, it should remain unrooted right?
WT Ho said:
If I understand correctly, your ROM is rooted. If that's correct, you don't want to call that "STOCK ROM". Stock ROM usually refers to something exactly as it is shipped by manufacturer. I may call it "STOCK+ROOT" to indicate that things like superuser are already injected into the ROM.
EDIT: Reading your post again. I don't know why I had an impression that your ROM is rooted I suppose you did a dump using dd via adb shell, then it should be a STOCK ROM.
Click to expand...
Click to collapse
You know, I managed to dump other files as well. I wonder if I should include them as well? Here are the files I managed to extract.
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
recovery.bin
Sbl.bin
zImage
yp-g1.pit
Kwipper said:
You know, I managed to dump other files as well. I wonder if I should include them as well? Here are the files I managed to extract.
boot.bin
cache.rfs
dbdata.rfs
factoryfs.rfs
param.lfs
recovery.bin
Sbl.bin
zImage
yp-g1.pit
Click to expand...
Click to collapse
Those files are very useful as well, particularly for someone who badly damaged their device's file system. e.g. the Froyo ROM here has everything (except pit file), but the Gingerbread only has zImage and factory.rfs.
Although they are useful, many stock roms only include zImage and factoryfs.rfs. One reason that I can think of is RISK. The more partitions you flash, the more likely you screw up in the process.
Actually, you can post both versions for people to choose.
WT Ho said:
Those files are very useful as well, particularly for someone who badly damaged their device's file system. e.g. the Froyo ROM here has everything (except pit file), but the Gingerbread only has zImage and factory.rfs.
Although they are useful, many stock roms only include zImage and factoryfs.rfs. One reason that I can think of is RISK. The more partitions you flash, the more likely you screw up in the process.
Actually, you can post both versions for people to choose.
Click to expand...
Click to collapse
Yeah, just imagine what it would be like to have your computer crash while you were flashing the bootloader!
Can you make a backup of that?
so i can test if it works, cause my device is bricked at the moment.
Woah there, careful what you post! unless you do a factory reset before dumping, the cache.rfs, dbdata.rfs, and data.rfs should NOT be included in a rom as they contain all your personal information!
I know... For that i need a clear one...
Sorry, but there is no other way i found out.
I know that there is all Private Data on it...
But for me, my device is bricked with an completly empty /data folder.
All other folders include the normal content.
Thanks,
if someone can post it.
Mike Leitner
Tecardo said:
I know... For that i need a clear one...
Sorry, but there is no other way i found out.
I know that there is all Private Data on it...
But for me, my device is bricked with an completly empty /data folder.
All other folders include the normal content.
Thanks,
if someone can post it.
Mike Leitner
Click to expand...
Click to collapse
I don't think you need data partition. In normal operation, you can format the /data partition clean and the system will recreate your new settings there.
For those of you that have used this, can you confirm that this removes root? I going to guess it does.
It's not really a problem since you can use super one click again, but I just wanted to be sure.
Thanks again for doing this, Kwipper.
hey i need to flash factoryrfs form odin. but im not sure how, any help?
minimeofctown said:
hey i need to flash factoryrfs form odin. but im not sure how, any help?
Click to expand...
Click to collapse
Tar it and then flash it with Odin just like how you flash a ROM.
Use terminal (or cygwin for Windows) :
cd (directory of factoryfs.rfs)
tar -H ustar -c factory.rfs > something.tar
Can you make such a ROM? I really think, it will work for me…
I don't know the Problem so i feed to flash the hole ROM
Yesterday, I started having problems on CM9 with my touchscreen not responding (couldn't unlock my phone, capacitive buttons still worked). Neither rebooting nor factory reset helped, so I figured I would Odin back to stock JFD and see if that would help.
Fired up Odin, loaded the PIT and JFD tar, selected repartition, flash finished successfully and then... nothing. My phone would boot to the Vibrant screen and sit there; can't even get into recovery (download mode still works fine). Tried messing around with different files (JDF, JI6, KB5, Eugene's Froyo) with no joy.
Decided on a whim to try flashing the boot.img through Heimdall and behold, I can now get to recovery! However, attempting to flash a ROM does not work; my phone will continually boot into recovery no matter what I flash (cm7.2, cm9, ICS Passion).
TL;DR: Odin to stock = phone stuck at Vibrant screen; flash cm9 boot.img = only boot to recovery
I've never run into a problem like this from flashing or using Odin before. Any ideas on how to fix this?
1) Did you try Odining again after the boot.img flash?
2) Try heimdalling with the files. Unzip the tar and add the partitions for each file in the Flash tab.
Just tried using Heimdall to do the full flash (de-compressed the JFD.tar file) and it's still a no go. And yes, I had tried using Odin after flashing the boot.img. I also thought I might be able to recover by nandroid backup from stock, but that didn't work (got a boot recover error)
Can you get at dmesg with adb shell?
Code:
adb shell dmesg
I cannot connect through adb when I flash stock, but when I use the CM9 boot.img I get the following from dmesg, see attached
Download mode doesn't work on CM9. Downgrade to CM7, and there should be an option in the recovery menu to go into download mode. If not, you should still be able to do it while it attempts to reboot back into recovery mode; just do the button press to do it. But, I'd try flashing CM7 multiple times in a row to see if it can actually boot up.
whatiznt said:
Download mode doesn't work on CM9. Downgrade to CM7, and there should be an option in the recovery menu to go into download mode. If not, you should still be able to do it while it attempts to reboot back into recovery mode; just do the button press to do it. But, I'd try flashing CM7 multiple times in a row to see if it can actually boot up.
Click to expand...
Click to collapse
Download mode does work while you have CM9 installed. And there's no option to boot to download from CWM recovery afaik.
whatiznt said:
Download mode doesn't work on CM9. Downgrade to CM7, and there should be an option in the recovery menu to go into download mode. If not, you should still be able to do it while it attempts to reboot back into recovery mode; just do the button press to do it. But, I'd try flashing CM7 multiple times in a row to see if it can actually boot up.
Click to expand...
Click to collapse
I can get into download mode just fine from CM9, but screwed up my phone when attempting to Odin back to stock. Also, I tries flashing CM7.2 a few time without success. Good thought, though; it's saved me before.
If it helps, when I flash cm7, the boot logo changes, it just continues to boot into recovery. Might it have to do with cm needing mtd whereas I've flashed back to bml? Is there any way to force mtd formatting from the cm kernel?
Can you get to JFD and get it to boot up completely? I think that you should do that first to make sure your partitions are as they should first. Then once you do that, I suggest flashing a simple CM7.1 stable and get that to boot you completely. If at any point something goes haywire, we will have a better chance at diagnosis and able to rule out some things here and there.
Codes to check your partitions either through ADB or terminal app.
Code:
Su
Df busybox -h
If you need ANY files like CM7 or bootloaders or a GB bootloader enhanced JFD package PM me and ill send them to you. Won't be until later on tonight though.
Woodrube said:
Can you get to JFD and get it to boot up completely? I think that you should do that first to make sure your partitions are as they should first. Then once you do that, I suggest flashing a simple CM7.1 stable and get that to boot you completely. If at any point something goes haywire, we will have a better chance at diagnosis and able to rule out some things here and there.
Codes to check your partitions either through ADB or terminal app.
Code:
Su
Df busybox -h
If you need ANY files like CM7 or bootloaders or a GB bootloader enhanced JFD package PM me and ill send them to you. Won't be until later on tonight though.
Click to expand...
Click to collapse
Unfortunately, I cannot get into any form of stock (even recovery). If I use a CM kernel, it then will boot into recovery, and only recovery. I was on stock bootloader, but I flashed it again this morning, just to be sure.
Here's the output from my df (I believe you meant 'busybox df -h'...)
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 173016 32 172984 0% /dev
/dev/block/mtdblock3 81920 2528 79392 3% /cache
/dev/block/mtdblock2 192000 138676 53324 72% /system
/dev/block/mtdblock6 176128 4864 171264 3% /datadata
/dev/block/mmcblk0p1 14086752 99936 13986816 1% /sdcard
/dev/block/mmcblk0p2 1935192 1555788 379404 80% /data
Yes, you are correct about the code. Sorry about that. I was on the bus on my way home from work and mistyped.
What I think that you need to do is Odin back JFD and let it boot up. It will have the Froyo Bl's and stock recovery. From what I am reading, you are trying to run a "Stock" ROM wiht a CM9 kernel and that can't happen. The kernels are not cross-OS compatible. We want to get you booted up to a running ROM without messing with boot.imgs or somehow corrrupting your data.
Here is what I would do. Odin to JFD (not a 2.2 "stock") and then get it to boot up. Then flash CM7 and get it to boot up, again without messing with CWR or boot.imgs. Then we can go from there. After that we can go to an ICS variant.
From what I can see, your /data partition is still in tact, which means that you have NOT been hit with the Encryption Bug. This is good, but I suspect that if you keep messing with the boot.imgs, different versions of CWR or mis-matching kernels to ROMs, then you are flirting with disaster. First things first. Get to full Stock 2.1 and then go from there.
Woodrube said:
Yes, you are correct about the code. Sorry about that. I was on the bus on my way home from work and mistyped.
What I think that you need to do is Odin back JFD and let it boot up. It will have the Froyo Bl's and stock recovery. From what I am reading, you are trying to run a "Stock" ROM wiht a CM9 kernel and that can't happen. The kernels are not cross-OS compatible. We want to get you booted up to a running ROM without messing with boot.imgs or somehow corrrupting your data.
Here is what I would do. Odin to JFD (not a 2.2 "stock") and then get it to boot up. Then flash CM7 and get it to boot up, again without messing with CWR or boot.imgs. Then we can go from there. After that we can go to an ICS variant.
From what I can see, your /data partition is still in tact, which means that you have NOT been hit with the Encryption Bug. This is good, but I suspect that if you keep messing with the boot.imgs, different versions of CWR or mis-matching kernels to ROMs, then you are flirting with disaster. First things first. Get to full Stock 2.1 and then go from there.
Click to expand...
Click to collapse
He can't get stock to boot though.
Ok then. I thought that I had read that he was flashing a CM7 ROM with a CM9 kernel. There are two similar threads going on about something like this and I might have mixed up some of the posts.
I'll work on the other guy for the time being and check in here every once in awhile. Thanks FE!
Well, good news! I stopped by T-Mobile and they were (somehow) able to get my phone to boot! The first guy looked at it and couldn't get anything done and couldn't help me much since my phone's out of warranty, but another employee picked it up and got it working; said she "just pushed buttons" until it started, mainly did a "master reset" until it continued booting. Tried flashing CM7 and it worked. Think I might try going back to stock to see if I run into the issue again, but kinda don't want to risk it.
By the way, FaultException, while I (kind of) have your attention, have you had anyone else report issues with their touchscreen all of a sudden not responding in CM9? It seemed to happen rarely for me until right before I had this problem...
I've had something similar happen. Like the screen only wanting to go on dim and maybe one time it couldn't be touched. A reboot should clear it up though.
Sent from my SGH-T959 using xda premium
Download mode doesn't work on my vibrant? Tried hundreds of times from CM9.
Sent from my iPad using Tapatalk HD
whatiznt said:
Download mode doesn't work on my vibrant? Tried hundreds of times from CM9.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
How are you trying? Powered off + Hold volume keys + Plug in USB?
FaultException said:
How are you trying? Powered off + Hold volume keys + Plug in USB?
Click to expand...
Click to collapse
Every single method, not once working.
- From my iPad!
whatiznt said:
Every single method, not once working.
- From my iPad!
Click to expand...
Click to collapse
Well adb reboot download doesn't work. Plugging it in while holding both volume keys while it's off works for me.
So you've just gotten/inherited an I-777 and you need to get rid of the 2 year old UI and OS ASAP, but all the other guide threads are just as old and filled with old info, what to do?
DISCLAIMER: I am not responsible for phone bricks and the like. You follow this information at your own risk. This is just information I'm writing down as I update my wife's old bone stock phone
BACKUP your data from both cards, you are likely to lose the internal SD data in this operation
Let's get started:
Root the phone:
Go here: Framaroot.
Download the .apk, and put it on your phone.
Be sure to 1. Have install from unknown sources on. 2. Enable USB debugging.
Install the .apk and run it.
Choose SuperSU and then click on Aragorn (should automatically be detected).
Reboot the phone (power cycle is probably the only option in stock).
Congrats! You're now rooted!
Install a kernel
Go here: Mobile Odin.
Grab two apks; Mobile Odin Lite and the Flash kernel for i-777. (Flash kernel is many posts down from the top)
Extract the .apk from the Flash kernel .zip file, and plop both .apks on your phone.
Install the .apks
Go here: ShoStock and click on the 'older kernels + a tar version'
Download the .tar
Plop the .tar on your phone
EDIT: At this point you may want to also grab a rom and any other files you may need if you only have the internal sd available because you'll lose USB mount access past this point. So go ahead and transfer those files to the phone.
Open Mobile Odin Lite and select the .tar file
Flash it, the device will instantly reboot after flash.
The device won't fully boot now, but don't worry! Hold down POWER, VOL UP and VOL DOWN until the phone cycles and the logo appears, then let go of the buttons and you should be in CWM recovery which came with the jeboo kernel you flashed.
Install a ROM
You will have to wipe/factory reset first from the CWM menus.
Flash your rom, regardless, follow the instructions in the OP of the ROM thread you're interested in.
I flashed ShoStock first since it's likely more like an OTA update to bring partitions up to date before flashing anything else.
Be sure to hit THANKS on the posts you visit from this guide.
Nice to see an updated guide.
For your fifth step of Kernel install, you lead users to a jeboo kernel, which is great if they plan to go ShoStock. I believe that the Jeboo kernel is a mic swap kernel, and may not be suitable for other very popular and common ROMS for the I777 (any AOSP or stock samsung, or COOKED).
Therefore I suggest adding such a note, and providing a link to at least one of the Siyah(based) Kernels.
These are available in several versions, and in .tar or .img format; both of which can be flashed via mobile ODIN (extract the .zip, flash the boot.img)
if flashing to an ICS Rom:SiyahKernel S2-v5.0.1
If flashing to a JB Rom: AJK BOSS (newest available)
Edit: props to @othermark for compiling this simple updated means to root & rom on the i777
cyril279 said:
Nice to see an updated guide.
For your fifth step of Kernel install, you lead users to a jeboo kernel, which is great if they plan to go ShoStock. I believe that the Jeboo kernel is a mic swap kernel, and may not be suitable for other very popular and common ROMS for the I777 (any AOSP or stock samsung, or COOKED).
Click to expand...
Click to collapse
Most, if not all, roms here will come with the appropriate kernel which will be flashed during the ROM install. They would have to reflash the jeboo kernel to get something incompatible. This is just to get them something that 1. has CWM and 2. is a .tar they can flash with Mobile Odin Lite.
That said, sometimes you have to flash a compatible kernel before you flash a particular ROM.
othermark said:
...This is just to get them something that 1. has CWM and 2. is a .tar they can flash with Mobile Odin Lite...
Click to expand...
Click to collapse
Mobile Odin Lite (and Pro) will recognize and flash a zImage. So one can pull the zImage from any CWM flashable zip and use it.
cyril279 said:
Nice to see an updated guide.
For your fifth step of Kernel install, you lead users to a jeboo kernel, which is great if they plan to go ShoStock. I believe that the Jeboo kernel is a mic swap kernel, and may not be suitable for other very popular and common ROMS for the I777 (any AOSP or stock samsung, or COOKED).
Therefore I suggest adding such a note, and providing a link to at least one of the Siyah(based) Kernels.
These are available in several versions, and in .tar or .img format; both of which can be flashed via mobile ODIN (extract the .zip, flash the boot.img)
if flashing to an ICS Rom:SiyahKernel S2-v5.0.1
If flashing to a JB Rom: AJK BOSS (newest available)
Edit: props to @othermark for compiling this simple updated means to root & rom on the i777
Click to expand...
Click to collapse
So if i wanted to Do Cyanogen Mod(10.2), would it be okay to use the jeboo tar? Or should i download AJK, unzip it, and install the boot.img instead of the jeboo .tar?
TreatnHerRight said:
So if i wanted to Do Cyanogen Mod(10.2), would it be okay to use the jeboo tar? Or should i download AJK, unzip it, and install the boot.img instead of the jeboo .tar?
Click to expand...
Click to collapse
It should not matter which version of CWM recovery you use, so Jebo will be fine. When you install it, your system may not boot up, but just turn the phone off, then use the button combination for recovery mode.
Edit: boot.img is a partition file that Mobile Odin will recognize, the same as zImage, so you can use it to install AJK if you prefer. Again, it shouldn't matter which one you use.
TreatnHerRight said:
So if i wanted to Do Cyanogen Mod(10.2), would it be okay to use the jeboo tar? Or should i download AJK, unzip it, and install the boot.img instead of the jeboo .tar?
Click to expand...
Click to collapse
I can't vouch for the jeboo approach, but I expect that it works.
I did use this guide with the latest ajk-extracted boot.IMG as you describe, and it works as well.
Fyi: If you're using mobile Odin pro, you don't need the i777- kernel download, the pro version does it for you.
9. Open Mobile Odin Lite and select the .tar file
What do i click at this point(To Flash the .tar)? I opened Mobile ODIN Lite, now do i click Kernel, System, Data, Cache...., or Open file...?
Just wanna make sure.
Also:
cyril279 said:
I can't vouch for the jeboo approach, but I expect that it works.
I did use this guide with the latest ajk-extracted boot.IMG as you describe, and it works as well.
Fyi: If you're using mobile Odin pro, you don't need the i777- kernel download, the pro version does it for you.
Click to expand...
Click to collapse
To Do The Boot.IMG Which Would i click?
Select [kernel], navigate to and select the boot.img.
Then scroll down to the bottom of mobile Odin and select [flash firmware]
cyril279 said:
Select [kernel], navigate to and select the boot.img.
Then scroll down to the bottom of mobile Odin and select [flash firmware]
Click to expand...
Click to collapse
Used This Guide, Followed Everything Until the .tar File, i Instead flashed the AJK boot.IMG file. It Successfully Brought up CMW Recovery. When Attempting to Flash Cyanogen Mod or Paranoid Android I Got Error Status 7 (getprop("ro.product.device") == "SGH-I777 || getprop("ro.build.product") == "SGH-I777") Same Error for Both.
Steps i took to Fix.
Opened Unzipped Cyanogen Mod.
Open Build.prop and Rename SGH-I777 to i777 In those Two Spots (ro.build.product and ro.product.device)
Opened Updater-Script and Removed the First 2(or 3) Lines Referencing the SGH-i777
Then Re zipped them using this method - [UltimateGUIDE][How-to]Create your Own Custom ROM an easy way
Flashed in Recovery and it Successfully Worked. (Tested it With the Cyanogen Mod Zip Only, Got Error Previously With Both CM and PA Zips)
Me Attempting To Help Anyone Else In This Situation.
nice, do you guys know if it's possible to use this phone without a data plan on att? i recently upgraded my phone and wanted to give this one to my dad, he can use it to watch youtube videos and videochat with my grandmother via wifi at home, there was a thread i read on how to unlock the phone and it had an option for network lock, is that what i need to do? any help is very much appreciated
baoweezie said:
nice, do you guys know if it's possible to use this phone without a data plan on att? i recently upgraded my phone and wanted to give this one to my dad, he can use it to watch youtube videos and videochat with my grandmother via wifi at home, there was a thread i read on how to unlock the phone and it had an option for network lock, is that what i need to do? any help is very much appreciated
Click to expand...
Click to collapse
I don't really understand... You simply take the Sim card out and put the thing in airplane mode.
I did that with mine and the battery lasts a week. BTW you can turn on WiFi while in airplane mode. You can also uncheck "use data" in the mobile network settings.
There's nothing complicated to do.
Sent from my Nexus 4 using xda app-developers app
Yes I know about airplane mode but im trying to have him use this phone as a actual phone that can make calls but didn't want att to tack on an additional data plan to it because he never uses any data while out and about. Basically I want to use this phone on my dads line without having to add a monthly data plan.
He was using a T-Mobile phone that I unlocked for him before and they didn't add the data plan on cause att doesn't recognise T-Mobile imei, I could be wrong but if I can change something in the phones build prop to make it seem like a non att branded phone, would it not be detected as a smartphone and not trigger the data add on?
Sent from my SGH-I337 using xda app-developers app
baoweezie said:
nice, do you guys know if it's possible to use this phone without a data plan on att? i recently upgraded my phone and wanted to give this one to my dad, he can use it to watch youtube videos and videochat with my grandmother via wifi at home, there was a thread i read on how to unlock the phone and it had an option for network lock, is that what i need to do? any help is very much appreciated
Click to expand...
Click to collapse
This question, and it's resulting discussion are better suited in a separate thread. That helps to both get you views and answers that are more focused on your issue, as well as keeping this [GUIDE] thread clean and on-topic.
-Cyril
Nevermind, I figured it out.
The key combo to get into my recovery is Vol Up + Vol Down + Power
Is not clear for me in conclusion how obtain CWM in the i777 rooted??
pepe100 said:
Is not clear for me in conclusion how obtain CWM in the i777 rooted??
Click to expand...
Click to collapse
This has been answered for you already, several times. CWM is included in our kernels - you DO NOT flash it separately. Just pick a kernel that matches the android version you're on (ICS, JB etc.), flash it and it'll install CWM for you!
Sent from the i777
OK bro thanks for your concrete answer.
Sent from my SGH-I777 using xda app-developers app
i cant find the 'older kernels + a tar version' in shos thread .. pls help me !
nathan_42594 said:
i cant find the 'older kernels + a tar version' in shos thread .. pls help me !
Click to expand...
Click to collapse
It's in post #3.
jeboo said:
** OLD VERSION DOWNLOADS INCLUDING A TAR VERSION **
Code:
http://d-h.st/users/jeboo/?fld_id=9729
In a bind and need a tar version, just extract zImage from the zip and do: tar -H ustar -c zImage >> jeboo_kernel.tar
Click to expand...
Click to collapse