Related
I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
1)after you download it just extract the file in a new folder
2) Then goto that folder and u will "ROMUpdateUtility" double click on that.
3) just follow the instructions that appears on your computer screen after.
I'm thinking he probably doesn't have WinRAR.
loll thenn ill add another step:
4) download WINRAR and extract the files.
then follow my other other steps.
Do the CDMA Roms require a HARDSPL to flash them? I want to flash a CMDA NSFAN Rom to my friends Vogue and I dont see an stickies for flashing a CDMA rom. I normally spend most of my time in the Kaiser/Raphael Forums.
Any help is greatly appreciated.
Thanks,
Daniel
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
atomixpaintball said:
So I just did a ton of research on the web because the wiki is useless and might as well not exist.
I am using a Sprint HTC Touch with the official Sprint WM6.1 ROM from HTC.
So after my research, this is what I got (Please correct me if I am wrong):
1. Run 2.31.Coke and unlock the phone via USB/ActiveSync
2. Download NSFAN's latest Sprint WM6.1 Rom and extract to desktop
3. Rename ROMFILE.nbh to voguimg.nbh
4. Copy voguimg.nbh to MicroSD card that has been formatted to FAT32
5. Insert MicroSD card in phone, and enter bootloader via holding down the Power/Camera/Reset buttons all together.
6. Flash ROM
7. Hard Reset Phone
8. Enjoy
So to the everyday flasher here on the Vogue forum, are these steps correct? And if so, why dont you take the time to update the wiki so people dont have to ask the same repetitive question 1000 times?
I just cant believe that this forum has zero ROM flashing stickies, or and updated wiki.
Either way, any help would be greatly appreciated.
Thanks again,
Daniel
Click to expand...
Click to collapse
You are correct, but you do not need to do steps 3 thru 5. After you extract the ROM on your desktop simply doubleclick the RUU utility and it will update your ROM. (you must still be connected via USB to computer) If you want to flash from your storage card instead then do steps 3 thru 7.
I have a bell phone,
and the color screen says .36 and Security Unlocked.
do i have to unlock the phone still ?
its a bell phone, and it was like that when i got it.
does this mean its unlocked?
latinjig said:
I have downloaded the RAR file, but after taking a look at it I can see that it is not like any ROM updates provided by Bell. Can anyon some instruction or point me to another thread that explains this??
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=3680838&postcount=2
Detroit Doug
By the way, who needs WinRAR when you can get 7-Zip, the best all-around file compression/decompression tool around! And it's free. Opens almost anything out there all in one program.
http://7-zip.org/
hey..
i just had a quick question.. is it possible to switch back to the original BELL rom after you upgrade to NFS rom? i know a lot you might think why would you even wanna do that? But I was just wondering just incase..
Absolutely very easy just flash it like the instruction of a stock rom would require you too
(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado
Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado
Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!
steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425
I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)
Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?
steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...
ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..
waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.
Trying to figure out how to open up my OTA update.zip and get stuff out of it, all compression/uncompression programs I have fail. It seems like a topic that should have been discussed somewhere but I'm not finding anything useful in search (one thread said to use a tool to "repair" the zip first but that it didn't seem to be the complete filesystem he was expecting so I don't think that's the solution for me).
What I have is the update.zip pulled from the /data/fota folder. I also have some uncompressed blahblah.tmp file from trying to get the update from Kies instead, if that's any easier to extract data from.
The goal is to pull out the stock recovery and other pieces.
Device: Samsung Galaxy Tab3 8" SM-T310 on stock 4.2.2
I need to debrick my s3 previously running on 4.4.2 OB3. is anyone running OB3 on s3 I747M (not the I747)?
I have the instructions ready. so first, root your phone. If you don't want to root your phone, good bye because I don't need you. Ill get to the next step once someone is willing to help.
I have the OB1 how you make a debrick? do you have a tutorial? i can help u
dragoonmx said:
I have the OB1 how you make a debrick? do you have a tutorial? i can help u
Click to expand...
Click to collapse
ok. so, first, install busybox from the playstore. then, download terminal emulater, as well.
MhikeiMPC12 said:
ok. so, first, install busybox from the playstore. then, download terminal emulater, as well.
Click to expand...
Click to collapse
Done, what's next...
go into terminal app, type the following:
"su"
It will ask you for root access. type Grant.
"busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=70"
It will create a backup.bin in the root of /sdcard. ipload that file here. if the file type isnt supported, put it in a .zip then upload it using your pc. if you dont have a pc, just rename the end part of the file (.bin) to (.zip) and upload it here.
@dragoonmx
did he died?
Lets forget him. Do you have OB1?
MhikeiMPC12 said:
Lets forget him. Do you have OB1?
Click to expand...
Click to collapse
Hey, im in cm12.1, i need rom stock?
Thank goodness you are back! here is the link for stock:
http://dl.sammobile.com/PV9dRCQlOD0...1tcQExaUQ../I747MVLUFOB3_I747MOYAFOB3_RWC.zip
MhikeiMPC12 said:
Thank goodness you are back! here is the link for stock:
http://dl.sammobile.com/PV9dRCQlOD0...1tcQExaUQ../I747MVLUFOB3_I747MOYAFOB3_RWC.zip
Click to expand...
Click to collapse
could you link me a full tutorial for the debrick?
OK download Odin v3.07 search it in Google. then, open Odin, and extract all the files to the desktop.
Before continuing, make sure to backup all of your files because it will be deleted. The file you downloaded before, open it with winrar, then extract the files inside, to the desktop. Open Odin. Get your phone and turn it off. Once its off, hold vol down + home button + power button until you get the prompt to go to download mode. click vol up and it should say "Downloading...". Connect the phone to the computer, and Odin should recognise it. go to the AP slot, click it, and navigate to the file you extracted. Wait for Odin to recognise the file. After, click start, and don't disconnect it until it says "PASS" on the screen, or the phone boots up completely in the set-up. Its recommended that you eject the SD card in your phone (if you have one). Also, make sure only F reset time, and auto reboot are checked.
MhikeiMPC12 said:
OK download Odin v3.07 search it in Google. then, open Odin, and extract all the files to the desktop.
Before continuing, make sure to backup all of your files because it will be deleted. The file you downloaded before, open it with winrar, then extract the files inside, to the desktop. Open Odin. Get your phone and turn it off. Once its off, hold vol down + home button + power button until you get the prompt to go to download mode. click vol up and it should say "Downloading...". Connect the phone to the computer, and Odin should recognise it. go to the AP slot, click it, and navigate to the file you extracted. Wait for Odin to recognise the file. After, click start, and don't disconnect it until it says "PASS" on the screen, or the phone boots up completely in the set-up. Its recommended that you eject the SD card in your phone (if you have one). Also, make sure only F reset time, and auto reboot are checked.
Click to expand...
Click to collapse
Lol, for the debrick
Sorry bro I'm on 4.1.1 Stock and Rooted. Can't do OTAs.
dragoonmx said:
Lol, for the debrick
Click to expand...
Click to collapse
Just do what i told you to do earlier. read the other comments. the commands are over there
Hey man! Sorry I haven't been able to respond recently. Sent you a pm, but basically I've been in and out of town a lot the last few days!
Got a couple items that makes the process of creating a debrick.img very easy! Started out with a simple script and it evolved from there!
This one will create a 128mb debrick.img on your internal sdcard. (/sdcard/debrick.img)
Download this and flash in TWRP: https://www.androidfilehost.com/?fid=23196940996969297
That's It! Now just zip and upload!
(ignore the T999 in the filename
It will work on the I747 too)
This next one is slightly more difficult to use, but still easy if you just follow the instructions included in the zip file.
It includes options to create 128mb, 256mb and 512mb images. You should only need the 128mb one but we were using this for testing and troubleshooting when new firmwares were released.
Do NOT flash in recovery. Unzip and follow the included instructions. It will create the debrick.img and then will zip it for you using 7zip.
https://www.androidfilehost.com/?fid=23196940996969297
The first is the easiest and probably all you need. Just included the second in case anyone wants to try it or the first method doesn't produce a working image. (Doesn't fix a brick)
Hope it helps!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Hey man! Sorry I haven't been able to respond recently. Sent you a pm, but basically I've been in and out of town a lot the last few days!
Got a couple items that makes the process of creating a debrick.img very easy! Started out with a simple script and it evolved from there!
This one will create a 128mb debrick.img on your internal sdcard. (/sdcard/debrick.img)
Download this and flash in TWRP: https://www.androidfilehost.com/?fid=23196940996969297
That's It! Now just zip and upload!
(ignore the T999 in the filename
It will work on the I747 too)
This next one is slightly more difficult to use, but still easy if you just follow the instructions included in the zip file.
It includes options to create 128mb, 256mb and 512mb images. You should only need the 128mb one but we were using this for testing and troubleshooting when new firmwares were released.
Do NOT flash in recovery. Unzip and follow the included instructions. It will create the debrick.img and then will zip it for you using 7zip.
https://www.androidfilehost.com/?fid=23196940996969297
The first is the easiest and probably all you need. Just included the second in case anyone wants to try it or the first method doesn't produce a working image. (Doesn't fix a brick)
Hope it helps!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
@DocHoliday77 , any chance in hades this would work for atthtcm8 ? i know are completely different beasts , but figured couldnt hurt (too much.lol) to ask.
p.s. not bricked. just to have as 911-just-n-freakin-case.
"all i can really do is stay out of my own way and let the will of heaven be done"
DocHoliday77 said:
Hey man! Sorry I haven't been able to respond recently. Sent you a pm, but basically I've been in and out of town a lot the last few days!
Got a couple items that makes the process of creating a debrick.img very easy! Started out with a simple script and it evolved from there!
This one will create a 128mb debrick.img on your internal sdcard. (/sdcard/debrick.img)
Download this and flash in TWRP: https://www.androidfilehost.com/?fid=23196940996969297
That's It! Now just zip and upload!
(ignore the T999 in the filename
It will work on the I747 too)
This next one is slightly more difficult to use, but still easy if you just follow the instructions included in the zip file.
It includes options to create 128mb, 256mb and 512mb images. You should only need the 128mb one but we were using this for testing and troubleshooting when new firmwares were released.
Do NOT flash in recovery. Unzip and follow the included instructions. It will create the debrick.img and then will zip it for you using 7zip.
https://www.androidfilehost.com/?fid=23196940996969297
The first is the easiest and probably all you need. Just included the second in case anyone wants to try it or the first method doesn't produce a working image. (Doesn't fix a brick)
Hope it helps!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
So, with this i can create de img, instead of using terminal, codes, etc ?
MhikeiMPC12 said:
I need to debrick my s3 running on 4.4.2 OB1. is anyone running OB1 on s3 I747M?
I have the instructions ready. so first, root your phone. If you don't want to root your phone, good bye because I don't need you. Ill get to the next step once someone is willing to help.
Click to expand...
Click to collapse
Hi, this is the debrick link for the OB1, i747M
https://mega.nz/#!M9ly3DZB!I58rC4SG33Y7k8SWfoKHYwQssasHmwxBPELYQ5bGvv4
dragoonmx said:
Hi, this is the debrick link for the OB1, i747M
https://mega.nz/#!M9ly3DZB!I58rC4SG33Y7k8SWfoKHYwQssasHmwxBPELYQ5bGvv4
Click to expand...
Click to collapse
Ok thanks so much!
Here goes nothing...
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
remember i have not .zip file in media folder
Mr Hassan said:
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
Click to expand...
Click to collapse
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
-spektor- said:
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
Click to expand...
Click to collapse
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Mr Hassan said:
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Click to expand...
Click to collapse
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
-spektor- said:
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
Click to expand...
Click to collapse
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Mr Hassan said:
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Click to expand...
Click to collapse
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
-spektor- said:
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
Click to expand...
Click to collapse
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Mr Hassan said:
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Click to expand...
Click to collapse
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could help it deals with modifying samsung rom and flashing it. If you want to read more on it here's the link: http://android.stackexchange.com/questions/85703/modifying-samsung-rom-and-flashing-it-on-a-device if you wanted to remove apps or add custom apps to your phone you would modify system file.
But what I thought was important was this;
(I did not write this thread)
< "You should be able to use an archive program on PC and recompress to .tar, .gz, and others. Dont forget to re-sign the archive. Keep a copy of your untouched ROM until you have the modified ROM tested and running.
The ROMs are signed with a signature. When repacking if they don't get signed they will fail in flashing. This link will help explain it.
So basically after downloading the firmware you have to rename it so you can extract the files, change them as you need, recompress them again and re-sign them, so you can flash them using Odin." >
This thread was dealing with modifying CM rom;
< "There are multiple solutions available:
Re-Zip the Image
Advantage: You do it once, and can use the resulting image for multiple devices. That's what I did with CM7.2 for my Milestone 2. Easy enough to do:
create a temporary (empty) folder
unzip the zip file to it
remove unwanted *.apk files from /system/apps (be careful of what you remove, of course)
zip up the directory contents again
Using a graphical ZIP manager (like WinZip or the like), steps would be even easier:
open the zip file with the archive manager
remove the unwanted .apk files
if the ZIP manager requires it, save the manipulated zip
Manually cleanup after flashing, using the shell
This is what ce4 recommended in the comments. It requires you using a terminal emulator on your device:
Flash the image as-is
remove superfluous stuff from the system partition by hand (like rm /system/big/junk/example.mp4)
Manually cleanup after flashing, using other tools
Almost the same as the previous method, but a bit more user-friendly. Disadvantage: this won't do for superflous ringtones and the like:
Flash the image as-is
Use a tool like Titanium Backup or Root Uninstaller to remove unwanted system apps" >
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
-spektor- said:
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
Click to expand...
Click to collapse
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Mr Hassan said:
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Click to expand...
Click to collapse
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
-spektor- said:
.
Click to expand...
Click to collapse
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Mr Hassan said:
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Click to expand...
Click to collapse
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
Ok apps done
Bulid done
Now final thing need . repack in ext4 format
I'll check these things tomorrow
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
brother did you found anything for repack ext4 img?
Mr Hassan said:
brother did you found anything for repack ext4 img?
Click to expand...
Click to collapse
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
-spektor- said:
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
yes but its for linux , and for window 99% unsuccessfully rates , have you try in window ? this ?
now i,m in next step if you have the time so kindly share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719
Hmmmmm ? I think you want to change the boot animation (white Verizon logo red background? ) if so your gonna need to either need to flash a pre-made zip with Flashfire (can't seem to get it to apply from twrp) or your gonna need to manually copy into the appropriate directory (mount system directory r/w copy then change permissions of the file you copied to 644 and reboot) presumably with a root explorer though doable from terminal
---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------
-spektor- said:
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
Click to expand...
Click to collapse
Try flashing with flasfire enabling the option mount system r/w and use common paths (probably not necessary but won't hurt) I have had difficulty getting anything other than ROM and gapps to apply from twrp but flashfire seems to work . I'm thinking its due to the fact that flashfire flashes after boot loader and then resets prior to os load.