HI,
I was given i9300 today to flash it some custom firmware. I could tell phone was previously tinkered with, as there was "Custom" firmware information in "System information", as well as vanilla Update OTA attempt would fail. Other than that the firmware looked completely stock being at aged 4.1.x version, so I assumed it must have been rooted at most.
I checked under battery and after confirming it was indeed i9300, I heimdall'ed TWRP recovery and then installed CM 11 official nightly firmware.
Unfortunately, phone was soft bricked, hanging at Galaxy white on black logo.
I went into Download Mode and surprisingly it says there PRODUCT NAME: SHV-E210L. There is no way this is Korean version of the phone, but apparently some custom firmware was flashed, including bootloader I think (Download Mode is in Korean) and partition table with RADIO-VIA partition that is characteristic to Korean S3.
However, I didn't want to tinker with repartitioning yet having read that Download Mode is actually loaded from one of the partitions (BOOT, BOOTLOADER?). Also the firmware looked completely stock Samsung-ish so I don't get why would anyone want to flash Korean partition table?
Can anyone please advise what to do here? I tried flashing system/cache/hidden from both stock Korean and International firmware, but to no avail. I didn't want to tinker with other partitions yet.
I am a programmer familiar with linux and dd/gparted/gdisk tools, so I can perform low-level operations. I was thinking about manually removing the extra RADIO-VIA partition and realigning other partitions to match original i9300 partition table.
Either someone has flashed e210 bootloader or the phone has been faked to look like an i9300, most probably the second.
There is no cure, unless you can get e210 firmware to flash. You can't convert e210 to an i9300.
OK, but what if this physically is indeed a i9300 - is it possible at all that it would run just fine with E210L bootloader?
Either way, I am pushing E210L firmware now with Odin (repartitioning disabled).
EDIT. SOLVED. Flashing E210L firmware with Odin worked fine. I.e. this is a faked i9300 phone. I haven't seen something like this ever before . Thanks for help, anyway.
I9300 is worth more than an e210, or any of the north American models, that's why people fake the firmware to read i9300 and doctor the sticker. Bootloader can't be faked so that's the only easy to be sure.
cromki said:
OK, but what if this physically is indeed a i9300 - is it possible at all that it would run just fine with E210L bootloader?
Either way, I am pushing E210L firmware now with Odin (repartitioning disabled).
EDIT. SOLVED. Flashing E210L firmware with Odin worked fine. I.e. this is a faked i9300 phone. I haven't seen something like this ever before . Thanks for help, anyway.
Click to expand...
Click to collapse
Good
cromki said:
OK, but what if this physically is indeed a i9300 - is it possible at all that it would run just fine with E210L bootloader?
Either way, I am pushing E210L firmware now with Odin (repartitioning disabled).
EDIT. SOLVED. Flashing E210L firmware with Odin worked fine. I.e. this is a faked i9300 phone. I haven't seen something like this ever before . Thanks for help, anyway.
Click to expand...
Click to collapse
Hi Cromki,
Just found out my girlfriend has the same korean version galaxy s3 shv-e210l as you. Have been trying to install multiple roms without any succes before i read your thread. Please tell me where you found the galaxy s3 shv-e210l firmware / rom so i can get it to work again.
Thnx a lot!
Related
Well it's regarding rooting.
I heard it opens up a world of opportunity with your smartphone, and some apps I really want are only available vain rooted phones. I have the Samsung galaxy s3 international version. It was originally from Australia if that matters at all. It is on 4.0.4. Anyways, being a noob to android more or less, and being a bit apprehensive (because I have no warranty and I cannot obtain another phone easily) I was wondering basically how risky it is to brick your phone in a) the process of rooting your phone. Is it common? If it does get bricked is it reversable by a restore or simply gone? Also after rooting, is there any upkeep or management I need to do to make sure my rooted phone does not screw up? And lastly. What is the safest and easiest way to root the international quad core gs3 on ics. Thank you to everyone for your time
mysticgorilla said:
Well it's regarding rooting.
I heard it opens up a world of opportunity with your smartphone, and some apps I really want are only available vain rooted phones. I have the Samsung galaxy s3 international version. It was originally from Australia if that matters at all. It is on 4.0.4. Anyways, being a noob to android more or less, and being a bit apprehensive (because I have no warranty and I cannot obtain another phone easily) I was wondering basically how risky it is to brick your phone in a) the process of rooting your phone. Is it common? If it does get bricked is it reversable by a restore or simply gone? Also after rooting, is there any upkeep or management I need to do to make sure my rooted phone does not screw up? And lastly. What is the safest and easiest way to root the international quad core gs3 on ics. Thank you to everyone for your time
Click to expand...
Click to collapse
Well, most you could pick up be reading a bit, everything is already explained around here but since i was in your shoes very recently:
- there's always a risk. You need to be aware of that. That said, most cases that actually go wrong it's usually user's fault who failed to follow instructions closely. So read them. And read some more. And then read again just to make sure. And then i'd read again.
I used this very recent method from chainfire (salute and donate to the man if you like and can, he deserves it) to root my 4.0.4 international GT-I9300 S3:
http://forum.xda-developers.com/showthread.php?t=1957273
Triangled away next and everything worked like a charm. This preserves everything as stock as possible just adding root to your phone.
- from what i can tell, as long as you don't do anything that messes with the bootloader, you can always recover from a procedure gone wrong. Just disconnect, remove battery, insert and try again. Rebooting the computer or changing usb ports usually helps too (on odin).
- after rooting successfully, the very first thing you should do is backup your /efs folder. This is easy, just pick up root explorer or some other file manager that allows exploring you root (/), go up in your folders until you get to / look for the efs folder and just copy it (NOT MOVE) elsewhere (sd card, external sd, your computer preferably, whatever, just have that safe). This will come in handy in case you lose your imei at some point. Just restore this folder's contents and you're good to go. If that happens and you don't have a backup, it's a f'ing pain you can do well without.
- anything else root related is just common sense. Since you have the potential to screw up your entire phone with root permissions (this is why you don't have them in the first place), if an app pops up asking for root permissions, be sure what it is before allowing. If you're not sure, you can always deny first and allow later in the superuser app.
- you can also look into backing up with nandroid. You can think of this as an image of your entire phone. With this you can restore your phone to the same state it was when you did it. Useful when something went wrong and your phone doesn't boot anymore or you just wanted to try new roms with the option of coming back to what you had before. Not sure how you do it on the S3 still, but it usually requires a modified recovery like CWM. The method to root above doesn't install one though, it preserves what you had. Check this instead if you're interested:
http://forum.xda-developers.com/showthread.php?t=1695238
Cheers dude, i'm sure everything will go well for you too.
Chance of a brick about .0001 % rising to 100% for those that are to lazy to read follow instructions .
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Thankyou very much to everyone who has read and replied to this. 3 more minor questions. Is there a way to first update my phone to jellybean 4.1 via Odin or something like that? Or is this possible after root, because I don't want to stay on ics. Also what exactly happens if I update while rooted. Does it wipe or unroot my phone or the like? Also should my phone be in use debugging, and lastly what does it mean to unlock my bootloaders? That was more than 3 questions sorry thanks again
mysticgorilla said:
Thankyou very much to everyone who has read and replied to this. 3 more minor questions. Is there a way to first update my phone to jellybean 4.1 via Odin or something like that? Or is this possible after root, because I don't want to stay on ics. Also what exactly happens if I update while rooted. Does it wipe or unroot my phone or the like? Also should my phone be in use debugging, and lastly what does it mean to unlock my bootloaders? That was more than 3 questions sorry thanks again
Click to expand...
Click to collapse
1) You don't need to root to update to JB.
Just download any ROM you want from http://samsung-updates.com/device/?id=GT-I9300 (I recommend the UK unbranded ROM, BTU) then use Odin3 to flash it to your devices. Search the forums for specific instructions on this procedure. I'll just tell that it takes no more than 2-3 minutes.
2) If you're going to root, I suggest you do it beforehand, by flashing a kernel like Siyah (in ICS), and then proceed to flashing the stock JB ROM, HOWEVER, instead of using Odin3, you will use MobileOdion (available from Play Store), because that way you'll have a fully rooted and stock device.
3) Using step 2 above, it will not wipe not unroot your phone. It is safe and retains all your settings. That is the beauty of MobileOdin. There is a free version.
If you root and THEN install via Odin (PC), then you'll lose root, but not your settings.
In either case, you only wipe the device IF YOU WANT TO.
So, the best option is to:
a) Install SiyahKernel using Odin3 (PC)
b) Download the JB BTU ROM from http://samsung-updates.com/device/?id=GT-I9300
c) Extract the .md5 from the ZIP file and move it to the device's ext. sd card
d) Install MobileOdin in the device
e) Use MobileOdin to flash the .md5 you moved to it in step (c)
f) install TriangleAway (download from XDA) and run it to reset binary counter (which got incremented in step [a] )
Results: rooted, JB, stock, all settins retained, no binary counter increment
Simonetti2011 I have been searching the internet here in New Zealand and that has been the best answer I have found so far!
I do have a slight question thought. I live in New Zealand and have the GT-I9300T model of the GS3 and I'm wanting to install the international unbranded rom for that I can get updates faster (here in NZ it takes months and months to get updates)
I downloaded the International UK unbranded firmware 4.0.4 and was going to flash that rom onto my phone then upgrade to jelly bean via kies but have since relised I should just download the jellybean UK firmware straight away. Do you by any chance havea link to the firmware that I would need, I noticed there were a few different versions.
Also about the CSC, would I need to do any changes?
Many many thanks in advance, Sorry for hijacking this thread, just figured I was on the same pages as the OP
prawln said:
Simonetti2011 I have been searching the internet here in New Zealand and that has been the best answer I have found so far!
I do have a slight question thought. I live in New Zealand and have the GT-I9300T model of the GS3 and I'm wanting to install the international unbranded rom for that I can get updates faster (here in NZ it takes months and months to get updates)
I downloaded the International UK unbranded firmware 4.0.4 and was going to flash that rom onto my phone then upgrade to jelly bean via kies but have since relised I should just download the jellybean UK firmware straight away. Do you by any chance havea link to the firmware that I would need, I noticed there were a few different versions.
Also about the CSC, would I need to do any changes?
Many many thanks in advance, Sorry for hijacking this thread, just figured I was on the same pages as the OP
Click to expand...
Click to collapse
Thanks!
The 9300T and the 9300 are NOT the same device, therefore they use different firmware (ROM). The ROMs for the 9300T are here: http://samsung-updates.com/device/?id=GT-I9300T
I don't think there is a 9300T ROM for the UK, since the model released there is the 9300 (non-T).
It seems that either Samsung-updates hasn't indexed any ROMs for your model or they haven't been released.
About CSC: just don't worry about it... download and flash any ROM you want for your specific model and don't worry. If you don't like it, just download and flash another one.
Thanks heaps for that!
I actually just tried the UK unbranded rom that was for the i9300 on my i9300T and suprisingly everything seems to work ok so far (phone calls, txting, 3g etc)
Thankyou to everyone!
Thank you for your responses to my post regarding rooting my s3. They were very helpful. i succesfully rooted via chainfire cf auto root for the I9300 model without problem. Just one last question, I have been searching around a bit and some people are saying that flashing the jellybean firmware via odin, is not a perfect copy.. i mean some say they have been experiencing very minor problems here and there. So, if i update to the uk firmware on jelly bean via odin or mobile odin, and i experience some problems, can i still get the official ota update or jellybean 4.1 via kies when it is released? Thanks again for your help. Im pretty new to this android stuff
Hi guys n girls,
I am sort of new to the Ace section here. I am doing a re-vamp of my mum's phone and said I would spruce it up a little. Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
2). I am unable to get any detection with EFS pro and it returns no PIT file?
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
First off, wrong section.
Jarmezrocks said:
Shame there is no decent CM 9 versions that I can get working because of lack of RAM....the only one listed (no disrespect to the dev - thanks for making it available on such a low spec device!) but it doesn't work with my Optus GT S5830V (5830I) for some reason?
Click to expand...
Click to collapse
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Jarmezrocks said:
Anyway to my point, I have downloaded several versions of the stock firmware from Sammobile. The odd thing is that I cannot extract that firmware at all. Every archive program I have sees it as either being not an archive; corrupt or fails to extract it? So I am unable to make my own 4 part Odin recovery package. Making my own will save time; at the moment I have to flash the 4 part Odin (return to stock) package, then reboot into download mode again and then flash the stock firmware?
Click to expand...
Click to collapse
Jarmezrocks said:
3). All attempts to extract the stock Optus firmware package fail. I have removed the .MD5 file extension (only needed for preserving file naming conventions anyway - i.e. If you rename any .tar.md5 firmware package, in order to be able to flash it you need only to remove the .md5 from the end and leaving it as .tar and the firmware will flash without error. I digress.....What does someone suggest for me to being able to make my own firmware package based on stock?
Click to expand...
Click to collapse
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Jarmezrocks said:
3 things I noted.
1). The device is not detected by the so called Odin specific for Ace and variants that uses an Ops type PIT file? The device is plugged in and all drivers upto date....it' just plain doesn't see it? It is however detected and flashable (albeit without an .ops file) using the 4 part package on Odin 3.07 made for my Galaxy S3?
Click to expand...
Click to collapse
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Jarmezrocks said:
2). I am unable to get any detection with EFS pro and it returns no PIT file?
Click to expand...
Click to collapse
I don't know about this.
NightRaven49 said:
First off, wrong section.
Click to expand...
Click to collapse
Why? I was not actually asking for support as such, just sharing what I learnt/noticed.
NightRaven49 said:
1) We don't have a stable CM9 because our devs don't have the source code for all the drivers, not lack of RAM.
2) Have you formatted your system's partitions to the EXT4 filesystem? CM requires an EXT4 filesystem to operate.
Click to expand...
Click to collapse
Yes I am aware of that. I actually did attempt to flash the CM9 developer package several times all without result.
I tried many methods, firstly the conventional method and then several other unconventional methods. I first flashed CWM recovery 6.0.0.x (something around there) and that was ok but it could not detect the partitions....naturally I was on the standard firmware!
So I then flashed Thunder kernel which allowed recovery to see and mount all the partitions as well as prepare for a CM firmware flash. As I knew that CM required EXT4 I was prepared and flashed Rio's Ext4-RFS conversion script via Aroma in recovery. This worked very well. Only issue was that in doing so it corrupts the system partition and then I am unable to mount it anymore to flash CM.
Returning to stock or even attempting a nandroid restore from this point forward was fruitless as you can imagine. I tried several other combinations before retiring the idea. These included full system wipe after flashing CWM recovery (I figured maybe having data on the partitions its self could be interferring with the EXT conversion scripts? Everything seemed fine and ran correctly as expected only no system mounting.
I tried another method of flashing a ROM that included a kernel with it based on CM7 in the hopes that migrating to CM9 would be easier; this was not the case.
I picked a CM7 ROM that had a conversion script built in for BML to MTD. After returning to stock base via Odin I proceeded to flash recovery 6.0.0.x again, then I immediately flashed CM7 in the hope that I would kill two birds with 1 stone and have CM do its conversion on the fly as well as install (alleviating the need for mounting system after migrating to Ext4). This ROM installed without fault. All was well until I rebooted expecting to boot into CM7....this wasn't the case, I received bootloops like crazy. Naturally I booted into recovery (the ROM had downgraded me to version 5.x CWM recovery - that is fine anyway); I proceeded by clearing the caches and performing a factory reset (note This usually a good thing to do anyway regardless if you came from a clean reset factory firmware or not).
After doing this and rebooting the device reboots continuously as it did prior. I again decided to re-install the same zip as I am aware with changing to CM on many other devices it can sometimes require flashing 2-3 (and sometimes even 4) times for a firmware update to stick. Again still no response and forever bootloops. I decided at this point that if I was to waste the time and effort in Odin'ing back to stock AND THEN flashing my standard firmware that I should try another CM ROM.
I had CM9 available and even though half hour prior I was unable to mount the the system partition, I thought maybe that CM7 had been flashed first so if CM9 can see and mount partitions (like it should have originally) then I could flash CM9 in a hope that it might wipe out what ever was causing all the issues with bootloops.
CM9 installed correctly, however again I could not boot the device at all! I had read a post from a forum member's guide saying that if I got some of these issues that I should flash back to base and try it again. I did this another 3-4,5 times at least, various combinations of wiping base firmware, not wiping base firmware, wiping CM7; not wiping CM7......Always the end result = bootloops.
As you can imagine it was rather annoying if I was returning to base firmware (if I wanted to be stock carrier branded again I needed to flash twice, once to return to stock and again to flash Optus firmware.
Overall I was unable to get any firmware booting besides that which was provided as an Odin package AKA stock firmware. If I flashed a custom recovery over stock firmware I was unable to boot again. Oddly enough I found a standalone version of CWM recovery version 5 that was not CM specific and I performed a backup as it was able to see the stock partitions without throwing errors.
I then opted to do a conversion to EXT4 again and hoped that I could just restore my nandroid backup of the stock partitions like recommended in may of the guides for Galaxy Ace.
Unfortunately again I was unable to boot and the partitions become unmountable leading to yet again flashing back to base unbranded, then flashing stock carrier branded firmware (this has the correct modem for the carrier and region).
At this point I retired the idea of custom firmware. I will later root the device and just leave it on 2.3.7 and do internal/external SDcard swap and flash a theme and maybe a few compatible APKs from newer stock firmwares (at least ICS) to achieve the functionality I was hoping to have by flashing and using ICS. I found the best and most simplest way of achieving this was through Moto-Chopper Root method and adb, most of the documented ways of achieving root on the Ace don't work for the S5830V for some reason. So I will stick with what works.
NightRaven49 said:
The tar.md5 file has to split into the PDA, CSC, Modem and PIT files using Odinatrix. Search for it.
Click to expand...
Click to collapse
Thanks for the tip. :good: I have downloaded this ready now, so I will investigate how this goes? It looks very similar to a application I already use TAR.MD5_PACKAGER however I see it has an option for extracting from .tar.md5 files that have malformed header information. So that sounds like it should do the trick!:fingers-crossed: Do you think that this is maybe intensional as a means of stopping people like us from building custom firmware packages?
I mean the .tar.md5 package flashes perfectly as it should do which is very surprising seeming .md5 signature is very easily broken when you rename the file and you have not even opened it. That was what lead me to flashing it in the first place, I mean I figured that if the .tar.md5 was so corrupt as I believed it was, then the worst that can happen will be Odin will spit an error message and not proceed i.e. it won't even attempt to flash the said firmware!
Myself if I download any firmware that doesn't flash and fails due to md5 error, I immediately open it up and inspect it and unless it was extremely difficult to obtain (I have waited close to 30 hours once for an old firmware package to download from the only source I could find - but regardless if it was damaged or not I only wanted the old bootloader so I could integrate it into a new firmware package so the passing md5 was relatively unimportant), I would just re-download it again.
The fact that ALL of these packages for S5830I are like this (regardless of what browser or means I downloaded the package) and the fact that they DO in fact flash like normal packages, and the phone returns to 100% factory condition; tells me that this does look like a means of discouraging custom firmware developers? hmmm
NightRaven49 said:
The Odin specific for Ace you stated above might be for GT-S5830. For the variants running the Broadcom BCM21553 the Odin version to use is v1.84. Odin v3.07 is more like a universal Odin that works on most devices.
Click to expand...
Click to collapse
The device is actually a S5830V...the V devices are relatively undocumented, but they are essentially just the same as the more common i/M variants. I did my homework first with this, and I can most certainly attest that it is NOT the S5830. I wouldn't attempt flashing S5830 firmware, also S5830i firmware boots and functions as normal and has signal albeit not so strong when the modem is not for our carrier and/or region, but function none the less.
NightRaven49 said:
I don't know about this.
Click to expand...
Click to collapse
Well give the fact that I had performed so many download of firmware that I initially believed to be corrupt I was unable to extract the PIT (or in the case of the generic Ace OPS file) from the firmwares.
Being the fact that there was little known about the S5830V I was unsure if to proceed of not? There are few reports on the device and most of them were of owners bricking their device, only 1 report I know of where a V owner claimed he flashed S5830i firmware without a hitch, again he was not from Australia where I am from, so I was flying blind and scared I was going to brick the device.
At the very least if I had a PIT file I could analyse it and could manually make image backup of the EFS/IMEI partition straight after rooting the phone. I have looked already at scripts that scan the whole emmc and I hit a snag when the kernel I am using is not insecure i.e. adb cannot run as root. I have root and confirmed with root checker app but terminal emulator and/or command line are unable to obtain root
Anyway to shed some light for you EFS Pro is a means of doing this that works on most Samsung devices....just not the Ace as far as I can tell.
Yes I am already aware that there is Galaxy Toolbox and I had actually gone ahead and done all that already,but an incident more recently where I had a device I was repairing with a wiped IMEI and it actually refused to boot. This becomes a hassle when restoring the IMEI cause in order to have Galaxy Toolbox you need to be booted and rooted. I wasted a whole day repairing the IMEI. So pretty much the message here is what good is Galaxy Toolbox to me restoring the IMEI if it can't boot? NONE!
I contacted the developer weeks ago and explained my situation and he is still yet to respond. I explained that I had a V variant of the Ace and wanted to ensure I had all bases covered. I requested information on how I could open the IMEI manually outside of the Galaxy Toolbox in the case that it would not boot (as this was how I restored the other device last week and it worked), unfortunately I am still yet to hear a response form him? Slack.
When I obtain this information I will share it here on XDA in the hopes that people in Australia with this variant will search and find some info on it. This is also why I am making this post here so detailed for folks like me who have been searching fruitlessly for answers.
My thoughts are that maybe there is something still not 100% the same between the i and the V because all custom firmwares I tried made for the S5830i never worked?
There is maybe an issue with how they are scripting their installs that is causing issues, but it is worrying enough that flashing so far has lead to partitions becoming corrupted very easily. I have had this before with my own phone more recently because a dev made a simple mistake in an updater script that called an explicit partition by mounting point ID and not by a more generic mounting point like "/system", "system" which lead to lost IMEI and bricked phone.
I am not blaming the dev though because it is easy to assume that a even though the mounting was non-specific for my device and the partition being called was not actually the EFS, it should not have corrupted my EFS....but that is not true, so a discovery was made and a lesson learned from all this. I managed to revive my device and it lived to fight another day, but simple mistakes made in ignorance or lack of information can still be costly mistakes. Need I say more.
I will report back when I have got a proper partition map for the S5830V and all will be happy days
I don't feel like quoting anymore, but I do spot some anomalies.
1) ...we don't have CWM 6.0.0.x. Are you sure you used the 5830i CWM, not the 5830?
2) I was referring to some other version of Odin when you said the Odin version specific to Ace. Which version were you using then?
3) I don't see how rio's multi-formatter can render the system partitions unmountable. In that case try lopicl.00's EXT4 formatter. Go search for it. After formatting flash Biel's Specific Basic kernel.
also you were asking a question, so naturally this should be in Q&A.
Hello World,
I've previously worked a little with roms on my HTCs. But this is the first time I try to bootload a Samsung. Which clearly doesn't go that well for me.
However, I followed this guide: http://forum.xda-developers.com/showthread.php?t=1974114
But after flashing the Stock VRBMB1 Factory Image, I cant access Recovery anymore. It just gives me the Samsung Logo and the GT-I9300, which makes me kinda stuck. What should I do?
Oh, and I can access Download mode.
You bricked your phone by flashing a firmware meant for a different S3 model, try Odin with an i9300 firmware from sammobile but you may have a hard brick after booting it with the wrong kernel installed.
boomboomer said:
You bricked your phone by flashing a firmware meant for a different S3 model, try Odin with an i9300 firmware from sammobile but you may have a hard brick after booting it with the wrong kernel installed.
Click to expand...
Click to collapse
It reboots fine, and everything in Stock os works. But I cant seem to find any International files anywhere?
You aren't looking, search sammobile for i9300.
I want to do a factory reset on my Samsung Galaxy J7 2016 (J710FXXU6CSK1),not previously flashed, however I need to use a password when factory resetting through Settings, which I cannot recover, even after confirming using my email adress. My best bet is to wipe everything, and manually install the firmware through Odin. I did not find the firmware for the exact version I currently have, however I am currently downloading a similar version through updato (J710FXXU6CSK2) . Now,this version is localised for India, and I live in Europe. Would installing this version risk bricking my phone? A barely usable device is better than an unusable device.
I'd like to mention that I have searched for the same issue on XDA , and I have not found anything so far, at least concerning this device/model. Secondly, even though I am not completely new to flashing with Odin(I managed to save a bricked Samsung Galaxy Core II a few months ago),I'm still unfamiliar with how to use Odin,and don't really remember exactly what I did the last time.
1)I heard that specific versions of Odin work on specific models. Is that true? I have "Odin3 v3.13.1_3B_PatcheD.exe" downloaded,will that work for my device?
2)Once(if) I have the firmware downloaded and everything connected ,where should I "put" the firmware on Odin?(It is in the AP box if Iremember correctly, though I could be completely wrong, please correct me if I am)
3)Will I be asked to enter the same password I mentioned earlier if I do it manually?(Through the android boot menu)
4)If I am required to enter a password, is there any way I could bypass it?
5)I know I could have searched for this last question on my own, but if anyone could be kind enough to link me to an Odin tutorial, I would really appreciate it! Last time, I had to gather small bits of how it worked from many different sources.
------------------ said:
I want to do a factory reset on my Samsung Galaxy J7 2016 (J710FXXU6CSK1),not previously flashed, however I need to use a password when factory resetting through Settings, which I cannot recover, even after confirming using my email adress. My best bet is to wipe everything, and manually install the firmware through Odin. I did not find the firmware for the exact version I currently have, however I am currently downloading a similar version through updato (J710FXXU6CSK2) . Now,this version is localised for India, and I live in Europe. Would installing this version risk bricking my phone? A barely usable device is better than an unusable device.
I'd like to mention that I have searched for the same issue on XDA , and I have not found anything so far, at least concerning this device/model. Secondly, even though I am not completely new to flashing with Odin(I managed to save a bricked Samsung Galaxy Core II a few months ago),I'm still unfamiliar with how to use Odin,and don't really remember exactly what I did the last time.
1)I heard that specific versions of Odin work on specific models. Is that true? I have "Odin3 v3.13.1_3B_PatcheD.exe" downloaded,will that work for my device?
2)Once(if) I have the firmware downloaded and everything connected ,where should I "put" the firmware on Odin?(It is in the AP box if Iremember correctly, though I could be completely wrong, please correct me if I am)
3)Will I be asked to enter the same password I mentioned earlier if I do it manually?(Through the android boot menu)
4)If I am required to enter a password, is there any way I could bypass it?
5)I know I could have searched for this last question on my own, but if anyone could be kind enough to link me to an Odin tutorial, I would really appreciate it! Last time, I had to gather small bits of how it worked from many different sources.
Click to expand...
Click to collapse
Hi,
If your device is working correctly i suggest to do a factory reset from recovery menu instead of flashing again. thats simple, no password required. https://www.verizon.com/support/kno...old the Volume,Select Wipe data/factory reset.
you have to flash firmware specific to country. you can find a specific firmmware here - https://samfw.com/firmware/SM-J710FN
Even if you flash a different firmware, you may not get network, but that can be corrected by flashing a correct firmware again.
you have to extract the firmware downloaded and specify files in odin. https://www.youtube.com/watch?v=p6gyc5wsuE0&ab_channel=GSM-ABC
How to turn Samsung Galaxy s2 GTI9100t or other versions into I9100( installed I9100 stock rom)?
Warrning, your warrenty is now void, I am not responsible for bricked device, etc.
First, confirm that it's hardware specs are SAME with I9100! (Expect with or without NFC, ✓I9100P, XI9100G XI9105 as different CPU)
Secondly, do a backup and root it, then install Odin on your computer and prepare a
data cable.*
Thirdly, download stock partition file (.pit) and stock I9100 ROM(.tar.md5 or .zip) on your computer. And also install Odin and Samsung USB driver. Link https://stockromfiles.com/samsung-galaxy-s2-gt-i9100-stock-rom/
i9100-stock.pit | by bmaupin for Galaxy S2
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Forthly, reboot your device into download mode*, and connect it with your computer.
Fifth, in Odin, click PDA, select the ROM; click Repartition, select the .pit file. Don't untick any of them.
Six, click start and begin to flash your device with .pit and ROM together. After that, it will rebooted.
Go and check about phone to see if it shows I9100.
If it shows, then you are successfully transferred it into I9100! You can flash other custom ROMs for I9100 on your phone without boot certification error!
In conclusion, the important parts are 1.SAME specs 2. Flash stock ROM with stock .pit together
What is the difference between the I9100 and the I9100T?
Does anyone know? I am in australia and have a vodafone branded galaxy s 2 and it states that it is a GTI9100T, I know others with other providers and they have GTI9100. Also I have a different kernel it is KF2. Does anyone have any idea?? Sent...
forum.xda-developers.com
Are you sure you read the entire thread with understanding?
ze7zez said:
What is the difference between the I9100 and the I9100T?
Does anyone know? I am in australia and have a vodafone branded galaxy s 2 and it states that it is a GTI9100T, I know others with other providers and they have GTI9100. Also I have a different kernel it is KF2. Does anyone have any idea?? Sent...
forum.xda-developers.com
Are you sure you read the entire thread with understanding?
Click to expand...
Click to collapse
Yes, I understood. But I discovered that from few months ago and that it's possible. As I finally installed some ROM for I9100 only, on my I9100t like Lineageos 15.1 or twrp
And also, the network lock is gone.
I think the .pit file helped with me so I can install I9100 rom without any errors