Related
For all those who are struggling to extract the contents of the '.abi' file for P552w and P565, here is a good news !!
I found these tools somewhere on a non-English forum, while searching for the decryption tools.
It is a command-line tool that directly works on the '.abi' file, and produces the '.nb0' file.
Part02.nb0 is the OS Image and Part03.nb0 is the ExtROM.
Let me know if you face any difficulties. I have used it on my P565 and successfully dumped the ROM (using imgfs tools on the the OS image). Working on the kitchen now....
Hoping for someone to come up with a kitchen for P552w/P565 soon...lol
cheers,
We also have decrypted P565's rom,and now the problem is how to encrypt the rom.Do you found any tools to encrypt it?
gerry86 said:
We also have decrypted P565's rom,and now the problem is how to encrypt the rom.Do you found any tools to encrypt it?
Click to expand...
Click to collapse
Well, decryption and encryption are both resolved. The only issue is to find where the IMGFS checksum is stored, and update the new checksum there. The '.abi' ROM Header is encrypted using some complicated encrption( not XOR ), and I have not been successful in decoding it as of now.
I see you're all experts here. Maybe you can help me.
I just want to know if it is possible to upgrade my italian ROM with an english one (P552w)?
If not I guess I can throw away my Asus while I don't speak Italian
Thanks for your help,
VanGog said:
I see you're all experts here. Maybe you can help me.
I just want to know if it is possible to upgrade my italian ROM with an english one (P552w)?
If not I guess I can throw away my Asus while I don't speak Italian
Thanks for your help,
Click to expand...
Click to collapse
Sure buddy, no need to throw it away...
Just follow these simple steps :
1. Ensure that your Storage card capacity does not exceed 2GB and is not corrupt.
2. Connect the device using activesync and wait till the connection is established.
3. Go to file explorer on your PC and enable the option to display hidden files and folders.
3. Take your English ROM ( .exe file) and execute it from your PC.
4. Press 'next' till you see the error message that the ROM is not meant for your device. Wait !!
5. While this message is still being displayed, go to the folder which contains your ROM ( .exe file). You will see a file called 'tmp_rom.abi'. Rename this file to 'GM5.abi'.
6. Now close the error message screen.
7. Copy 'GM5.abi' to your Storage card.
8. Now Press the "Navipad down"+ "Reset" buttons and keep them pressed until you see the reboot screen.
9. That's it. The ROM flashing process will begin automatically.
10. Do not press any button till the ROM flashing is in progress. The device wil reboot automatically.
Enjoy your new English ROM.
Disclaimer : Hope you are aware about the risks associated with the ROM flashing process.
First of all, thanks rishi for your help, but in my case something doesn't work.
I get to the boot screen where it says that it can not find the file (but it is on the card).
I followed all the steps (including 1GB storage card) but always the same, no success.
Is it possible that this is because of my Asus which was I suppose unlocked before I bought it. It has an Italian mobile provider logo on boot screen?
Do you have any other solution for my problrm?
Thanks again for your effort,
Van Gog
Found a solution!!!!
The name of *.abi file must be the same as the name of an *.exe file!
WOW!
Thanks a lot, you saved my Asus!!
Greetings,
VanGog
It should be GM2_name.abi and don't forget to clear hidden attribute.
For me it works also on 4GB card.
rishi, you said that "decryption and encryption are both resolved", is it using the same tool? I cannot say I got it...
weiqiix,
You may use this tool: http://forum.xda-developers.com/showthread.php?t=511158
Thank you very much, I'll test it right now.
Then I could even understand what (and how) to do with those *.nb0 files,
and who knows, I could understand my p552w's internals
If anyone can fix the camera and video problem that will be perfect!
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
edit update after flashed JME instead of JM4 (long story short):
"i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/show...91&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/show...&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly."
cant be updated? er, i was from jk2 to jm4. did you applied oclf? if you did, try undo it b4 anything.
Hi fastcx, thanks for replying and sharing your experience. I did some further reading in some singapore forum saying have to run the kies patch (http://forum.xda-developers.com/showthread.php?t=835628) and spoof firmware version in order to update. i have yet to try due to somewhere in the same forum also said that once updated:
1. cant go back version
2. z4root wont work (which i am already using)
may i know have you rooted your SGT? need more solid info before taking the route to update the firmware as already using SGT as my primary device. I havent OCLF yet
rooted, since day 1, after every update (jj1>jj2>jk2) able to root with z4root till jm4 which requires SOC(SuperOneClick). To use kies, switch back to samsung default launcher b4 u connect using kies. I do not have any issue there. Another note is that after root, i always go back to /system/app to check n remove any apps that I do not need using adb shell.
The interface changed, to darker color, dlna client really working now, oclf performance improvement might not be obvious this time around. I suspect they really optimized it, everything is more stable now. Over protective I would say, cause any previous flashlight apps isnt going to sustain the led light for over 2sec. Default browser is a wee bit smoother now.
SuperOneClick is very easy to use anyway, so give it a try, oclf is useful only when u have over 400mb apps + loads of sms & contacts..anything related to I/O will have improvement.
The worse case scenario is just if kies still do not allow u to update, just use odin..what did you do previously? How do you update previously?
VNPython said:
Reference http://www.samfirmware.com/WEBPROTECT-p1000.htm
Saw under the Asia Firmware 'P1000DXJM4 ## ODIN 1.7 | P1.PIT | Version 2.2 | 2010 December' is available and to be cautious, i seek seniors' opinion before i go ahead and flash mine ^^
Any recommendation on how to proceed is appreciated, esp with ODIN (dont know what it is even read so much about this word)!
I already backup with TB
edit: Connect to Kies and says 'This device's version cannot be updated.' Stating PDA: JK2 / Phone: JJ2 / CSC: JJ2. now even more confused
Click to expand...
Click to collapse
Yeah... I'm in your case.
Thinking does it would be updated or not???
1. cant go back version
2. z4root wont work (which i am already using)
Click to expand...
Click to collapse
Just look at inside of tar file, and according to the Chainfire's Warning, the three files:
* boot.bin
* Sbl.bin
* zImage > 7,000K
So, this firmware would be has the protected boot loader. It would give us a lot of trouble in the future of updating and downgrading.
I think, this firmware can be updated with the help from Roto, eliminate the three files above and just take the PDA part.
I was using CSC: XEV (Vietnam) then to SIN (Singtel) and feel good and when Nov'10 update came, updated via Kies wihtout any trouble. When Dec'10 update came, tried with SIN resulted unable to update, switch back to XEV also resulted unable to update. I havent try XSO which the singapore forum stated successful for those with that CSC.
So i have to try to switch to XSO and report in later. be it protected boot loader or not, as long as we want stable and more 'juice' to service our daily SGT needs, no choice but to follow. I do believe as days goes, seniors like Roto alike will crack the nut for us to appreciate further.
on other note, my default email (not gmail) app seem got problem whenever you click reply or forward any email will result in force close. do not know if this bug related to after i switch from SIN to XEV (to try update) then switch back to SIN and follow up by restore using TB.
anyone has similar force close on the default email app?
backing up with TB now should we (those yet to update jm4) wait for Roto to do his magic for this update?
edit: tried with XSO and also unable to update... that really puzzle me.
edit 2: unroot with z4root and try still unable to update... now looking at ODIN route
perhaps odin route is the best solution for your case, but from jk2 > jm4 not sure if pit file is needed? repartitioning needs it tho, perhaps its good that u do back up of everything, let us know ur flashing result. Odin will definitely able to do the job
oh no... T_T somehow i downloaded P1000JVJL1 (Arabic) by mistake and Odin 1.7 with Auto Reboot & F. Reset Time, selecting the mistaken Arabic firmware (PDA) and flash it without any problem (JVJL1 / JXJK3 / JVJK4) and able to reboot itself.
After notice the wrong firmware, downloaded the right one (P1000DXJM4) from samfirmware.com and using Odin 1.7. Repeating the above steps but the phone briefly flash and came back the 'download mode' and nothing happened although Odin stated passed without any error.
I able to hold the power to shutoff and turn on again and the screen shows the samsung logo screen and stay flashing the word 'samsung' with 1 then 2 quick vibrate (like force close) and didnt boot into the main screen!
what should i do next?? is it bricked?? T_T
edit: the downloaded filename is 'P1000DXJM4_P1000DXJM2_P1000OLBJM1_HOME.tar' and anyone know if correct one?
edit 2: now i am downloading DXJK2 and see if i am able to revert the flash of JM4 T_T
edit 3: is over T_T saw the (phone .. ! .. pc icon)
This is due to dbdata.rfs missing. Please refer to the guide of flashing JMC/D/E series.
BTW, I have a problem is Camera Faulty error when start the camera app. Somebody mentioned that the LCD density can't set too small, but I have reverted it back to default 240, the problem still there. Any clue about it?
Sent from my GT-P1000 using XDA App
thanks dahuzi, i wonder if i choose to flash eu rom by Roto, would his rooted bring my tab back to operation? appreciate any help to bring back my tab.
i am able to bring my (phone .. ! .. pc icon) to the download mode. flashing anything before JM4 wont work anymore (fail at odin 1.7 and 1.3) and i am able to go back to hard reset option (holding vol up and power up). now i need to get the TB backup from the int SD before i try anything new. possible to retrieve in download mode?
edit: where to find the dbdata.rfs for this JM4? can anyother dbdata.rfs from other firmware able to fill it in? help ~ T_T
Hi VNPython,
Your case is complecated one, take it easy and read the thread from Chainfire "WARNING! Do not flash ... ", in there, a lot people has solved with different path.
Be patient, Bro. At that moment, your TAB is not Brick yet, but be careful because it's on the way of the End.
Wish you luck.
Take care.
ha.. i hope to win this war ^^ and learning the way of android!!
edit: just a quick question - does TB backup all user and app data in internal SD or External SD? i got bunch of files in my ext SD folder '.android_secure' and inside have files like 'com.keramidas.TitaniumBackup-1.asec' can any senior confirm is a valid TB backup files and can be used to restore my user & app data? many thanks!
TB (TitaniumBackup) file in the internal SD (in my case is the default), please double check.
Please give us your detail of winning as I'm scare of Samsung flash. My history is, 4 years ago, I bricked my Omnia phone Samsung after I flashed the rom from SIN to AUS. And, this's my second device on Samsung but this is Android and I want to learn the new OS.
Take care, Bro.
hey guess what? i managed to get a file for dbdata.rfs from Roto and got the tab back live but missing PDA and CSC field (checking with *#1234#). tried the reset to get the pda and csc back but failed.
learned quite a few things along the way and will update this thread after completing my mission to update my tab to JM4.
windows seem cant extract and tar file for android tar files. i tried to extract jm4 files and add dbdata.rfs into it but when flashing, it fail.
worst come to worst, flash the JVJL1 to get the working tab again
i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
fastcx said:
try using winrar to do the add on of dbdata.rfs, anyway, good luck next time, double check what you downloading
Click to expand...
Click to collapse
Wow... another Maitre!!! What's your winrar???
Look and read:
.....i hope Mr. Roto could let me know what software to install on windows that able to 'untar' and 'tar' properly with android (linux) files. tried 7z and winrar both cant untar without error.
Click to expand...
Click to collapse
Thanks
sorry for the late update as yesterday too late to post anything after able to get my tab back to life! the learning curve is nice and not stressing since many time i see the icon of (phone .. ! .. pc) yet i am able to bring the download (digging) icon back again always.
i will write down the event by event of recovery as reference:
1. flash the JVJL1 (no problem on reboot) by mistake then flash JM4 (missing dbdata.rfs) tar file downloaded from samfirmware.com and failed to reboot due to the missing file.
2. did some silly step and resulted in (phone .. ! .. pc) icon
3. run odin 1.7 and plug the usb and odin show is connected with tab
4. flash JM4 (yes with missing dbdata.rfs) and able to bring the tab back to download mode but unable to reboot into tab
5. flash Roto's dbdata.rfs file (http://forum.xda-developers.com/showpost.php?p=9305891&postcount=1) and able to reboot right after but missing pda & csc info (*#1234#)
6. tried the hard reset (http://forum.xda-developers.com/showpost.php?p=9482192&postcount=106) but no help
7. download Roto's pre-rooted JME 3 files as mentioned (http://forum.xda-developers.com/showthread.php?t=895827) and finally boot the tab with full *#1234# details.
* So if you see the (phone .. ! .. pc) icon dont panic. like KChauJen said, able to solve with enough reading. i listed my route to recovery as reference to give you positive hope to retry.
TB's backup in Internal SD and before flashing JME, i copied the TB folder to my hdd during the missing pda & csc boot and did a backup on JME reboot, copy paste back to TB folder under internal sd and the restore work flawlessly.
after 1 days usage, the trouble found is email app still being force close whenever you reply or forward any email. any senior have similar force close on original email app?
KChauJen said:
Wow... another Maitre!!! What's your winrar???
Look and read:
Thanks
Click to expand...
Click to collapse
My bad. How polite of you.
Back to topic, VNPython everything there is a first time it's good info here. Perhaps you can edit your 1st post with info from your last post?
EDIT: 1 thing though, do you have any issue regarding using samsung apps?
samsung app can use, checked my CSC and its KOR. Apps: Vlingo words to action, Vietnamese Dictionary application & blinkx Beat. didnt try any of them. just *#272*IMEI# and there's no SIN or XEV or XSO or Asian Sales Code in the Roto JME (EU) multiCSC. maybe will try to download multicsc with asian sale code.
* on the email app force close, i delete the email account and re-setup them, and the force close is gone. could be due to TB's restore? anyway, is solved ^^
I wonder will i be able to flash DXJM4 if there is a full tar file?
VNPython said:
....
I wonder will i be able to flash DXJM4 if there is a full tar file?
Click to expand...
Click to collapse
Please consider it carefully, Bro.
What I looked inside of the tar file, and according to Chainfire's Warning, it has the protected boot.
If we can eleminate the three files:
* Boot.bin
* Spl.bin
* zImage
and put back to the tar file with the encrypted code by Samsung (maybe we can ask Roto) then we can flash this modified firmware JM4.
FYI.
(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.
WHAT IS THE USE OF .pit FILE?
.pit FILE IS USED TO DIRECT THE PARTITION OF THE WHOLE ANDROID SYSTEM..JUST LIKE WE ARE DOING GRUB IN PC...HERE ALSO WE NEED TO PARTITION THE SYSTEM FOR FLASHING THE FIRMWARE PROPERLY.. AND HERE THE .PIT IS USED
1. Get your phone into download mode..
2. connect to computer. Make sure that usb drivers installed and you have the firmware.tar file.
3. Now open odin 3.10
4. click on PIT and select ZEROLTE_USA_TMO.pit
5. Make sure that partition is tick
6. click on PDA and select firmware.tar file
7. Now start button and wait...You are done
link:
https://drive.google.com/folderview...tmV3YxMTB4WGpSZU5ReEI1WjZtUXM&usp=sharing_eid
Mhhh could be useful great job Op
The link doesn't work for me, could you reupload it? Also does this contain data about your /data partition? If so this might be specific to your model (16/32/64 GB)
update the file
update the file
SHATTAH said:
update the file
Click to expand...
Click to collapse
Just requested permission for the file.
SHATTAH said:
WHAT IS THE USE OF .pit FILE?
.pit FILE IS USED TO DIRECT THE PARTITION OF THE WHOLE ANDROID SYSTEM..JUST LIKE WE ARE DOING GRUB IN PC...HERE ALSO WE NEED TO PARTITION THE SYSTEM FOR FLASHING THE FIRMWARE PROPERLY.. AND HERE THE .PIT IS USED
1. Get your phone into download mode..
2. connect to computer. Make sure that usb drivers installed and you have the firmware.tar file.
3. Now open odin 3.10
4. click on PIT and select ZEROLTE_USA_TMO.pit
5. Make sure that partition is tick
6. click on PDA and select firmware.tar file
7. Now start button and wait...You are done
link:
https://drive.google.com/folderview...tmV3YxMTB4WGpSZU5ReEI1WjZtUXM&usp=sharing_eid
Click to expand...
Click to collapse
Can you please explain how you got the pit file? from what I understand you cannot simply dump the pit anymore unless I missed something.
requested access to this as well-- can you post somewhere other than Google Drive as people cant get to this file?!
can you please grant my request to download the file? I have a soft bricked phone and I really need the Pit file. thanks so much
looking a pit file for latest firmware 5.1.1 G925TUVU2COF6 does anyone have?
onlineunlocks said:
looking a pit file for latest firmware 5.1.1 G925TUVU2COF6 does anyone have?
Click to expand...
Click to collapse
According to: http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
Requirement: To be able to use any of the methods described below [to extract the PIT file], you must have root privilege on your Galaxy device. Both the methods have been tested on the Samsung Galaxy S5.
Click to expand...
Click to collapse
This means that, unless someone gets it directly from Samsung somehow (leak, release, or otherwise), you'll need to wait for root on the 5.1.1 stock ROM.
I don't know a whole lot about the PIT file, and why someone would ever need it (apart from screwing around so much that you overwrite your partition information on the device... which would be hard for the average user to accidentally do).
Have you tried Samsung Smart-Switch? I don't know if it's capable, but it might download the PIT info from the internet before restoring stock firmware on a 100% borked device.
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
onlineunlocks said:
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
Click to expand...
Click to collapse
Let us know if this worked. I need to restore back to 5.0.2 also from 5.1.1. Thanks
will not work to restore to 5.0.2 from what I know and might also damage it,so do not recommend to try that
onlineunlocks said:
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
Click to expand...
Click to collapse
I'm in the same situation.
Have you found a solution?
Aou said:
According to: http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
This means that, unless someone gets it directly from Samsung somehow (leak, release, or otherwise), you'll need to wait for root on the 5.1.1 stock ROM.
I don't know a whole lot about the PIT file, and why someone would ever need it (apart from screwing around so much that you overwrite your partition information on the device... which would be hard for the average user to accidentally do).
Have you tried Samsung Smart-Switch? I don't know if it's capable, but it might download the PIT info from the internet before restoring stock firmware on a 100% borked device.
Click to expand...
Click to collapse
is this gonna fix my phone if efs is not mounted??? me and my buddy have no idea how he broke his phone.
Hello precious s4 mini users!
Some of you may have had their devices hard bricked badly though there is this other type of hard brick where your boot loader is corrupted and there fore your cpu tries to boot from your sd card. when you connect your phone to your pc and the PC reads it as qshush_dload, Ill try to answer here if not then keep searching! I might post a topic to these stuff in the future.
This post is intended for s4 mini versions only so far how since I can not include all debrick files in one post... yet
How to solve qshush_dload: (For SIII I belive, Debrick files there won't work with s4 mini)
Link: http://forum.xda-developers.com/showthread.php?t=2600869&page=1
Another guild: (Same thing) http://forum.xda-developers.com/showthread.php?t=2439367&page=1
Debrick files:
I9192: http://www.4shared.com/rar/uWAOH4eNba/I9192UBUCOC2_I9192ZTOCOC1_ZTO_.html (assume 4.2.2 (or is it kitkat?) JELLY BEANS) by @IronRoo by Wilton
(4.4.2 KITKAT) http://www.mediafire.com/file/y10dy...+s4+mini+I9192+4.4.2+KitKat+(rip+phone..).zip
I9190: Not found yet.. (try the others)
I9195: Some were on the forum, please link here when you find it
Thats if the files are actually different*
Please make for both the 4.2.2 and the 4.4.2 at minimum!!! (again if files do differ) (If you have any thoughts on how to improve this, do tell)
For all three models, so far just afew exist yet but if you can make one your own or find it some were on the web please PM me and Ill be including it here!
How to extract Debrick file:
DocHoliday77 said:
Now you can create the image file needed for this De-Brick method.
Download this: T999_Partial_Sys_Dump_for_debrick.zip
Flash it in your preferred recovery (CWM or TWRP) and it will create the dump file needed for this debrick method from KAsp3rd!
Once you have flashed it you will find a file called debrick.img on your internal sdcard. It should be 128MB in size. (if you zip it, it will be much smaller!) Upload this to your preferred file host (I recommend Dev-Host), and PM the link to KAsp3rd.
Now it is waaaayyy too easy for anyone to reasonably say no!
Click to expand...
Click to collapse
Really hope that works* Please try it and upload the debrick files folks!
Guide to:
Get odin and flash CWM to your device then flash the root zip (search Your device model how to root) and flash root by booting into recovery then going to install zip then go to the zip files CWM by booting through recovery (search button combination for (your device model) to recovery) and do the same thing you did to the rooted zip file by the file above.
install es file explorer and go into / data / media, if it was not made or no files exist there, make a Media file, (enable root explorer) if you can not make a media file check if face book messanger has and make one, DO NOT DELETE THE OTHER ONE by system, just cap the M. and repeat.
If you think you can contribute to this in any way that would be fantastic!
Please read: For those of who who care about credit: I own none of it. I was directed by @IronRoo and kept going through all these pages, This is just all in one topic to help y'all!
Pls help i have a samsung galaxy s4 mini (19190) 4.2.2 jellybean version
I need an debrick image file for 4.2.2 jellybean galaxy s4 mini (19190) pls my phone is dead for over a year now (HardBricked). Thnx