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.
Related
Asthead says the phone is stuck efter trying root.
And now I want to flash stock firmware with odin.
Have tested a lot diffrent version of odin and several firmware, always say same thing, FAIL.
Help please.
Its a nordic countries, where can I find the orginal firmware GB or ICS?
Are the phone bricked?
Zam1000 said:
Asthead says the phone is stuck efter trying root.
And now I want to flash stock firmware with odin.
Have tested a lot diffrent version of odin and several firmware, always say same thing, FAIL.
Help please.
Its a nordic countries, where can I find the orginal firmware GB or ICS?
Are the phone bricked?
Click to expand...
Click to collapse
First of all, this is not a Development thread. At all.
Secondly, this thing has been talked many times, also in xda, with many threads of people with this problem. You should have just searched.
That said, can you post a screenshot of the Odin error?
If you can boot the phone into Download mode, it's more likely not bricked. I (and many others) use to have that problem when rooting it. It will probably be solved using another (older) version of Odin.
Check this thread with info on your same problem: http://forum.xda-developers.com/showthread.php?p=30694326
Good luck.
Hi All Below I occidentally posted in the Galxy SI900 instead of here< I got the usual replies but was grateful all the same. Maybe someone might help before I revert to stock...
Hi all, I know this has been done and dusted but I am having problems with connecting to kies after rooting. I am running standard jelly bean 4.1.2 and is an Australian GT-I9100. I installed the siyah kernal root system and now all I get on kies is "connecting" Windows 7 recognises and I can access the phone via explorer on the PC. The phone after a while comes up with a message that there is no compatible software on the PC, install kies...
I have tried all the so called fixes including formatting the internal SD and memory. The only thing I did before it stopped connecting was the root and running Triangle away (paid version). I have enabled / disabled USB debugging. The only things I haven't tried is a factory reset which I don't really want to do as I am always sceptical that the backup apps will work after to restore everything.
Any help appreciated
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?p=45907982#post45907982
Hope someone can help...
Regards Ismael
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
jiseuo said:
Did you try another PC or reinstall Kies? To know if the problem is in the phone or in PC?
Click to expand...
Click to collapse
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
IsmaelJones said:
Yes, Kies definitely sees the phone as it comes up with GTI9100 loading on the left top and in the centre it just sits saying connecting. I think the phone is not seeing kies as the message on my phone always comes up only when trying to connect to kies.
I have tried 3 computers/laptops same result. Different USB cables original plus other really high end ones also. No Joy. Looks like if I want to connect to kies I must revert back to stock kernal as the firmware I never changed it is the OTA from samsung 4.1.2 and rooted the S2 only...
Also Not knowing Samsung but in the about on my Motorola Tablet/phone even when rooted when you try to check for updates they say none available, the samsung actually says "Your device has been modified, no updates available"...
Click to expand...
Click to collapse
Now I am not using KIES, because I use AOSP ROM (4.3 Slimbean), but in past, when i was using STOCK ROM (XWLSN, XWLSS) I used "PhilZ-cwm6 - Safe Stock Based Kernel" http://forum.xda-developers.com/showthread.php?t=1877270 to root my phone.
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
jiseuo said:
If I remember correctly, KIES was working with PhillZ, but it is few months ago ...
So you can try PhillZ and see If it will work.(If do not need any special feature from syiah kernel of course)
Click to expand...
Click to collapse
Okay had a look at this, thanks. I do have a question though, my Kernel (PDA) is XWLSH, I have downloaded the 2 files but I am wondering how to install? Do I use my CW recovery or do I have to revert back to stock? A little confusing as he dowsn't really give instructions and I am pretty much an amateur when it comes to some of these things? Also I am running JB 4.1.2 he only mentions ICS 4.0.4? Help appreciated here...
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
IsmaelJones said:
Actually just re-read the post and I think I know now what to do. Correct me if I am wrong but the 2 files I downloaded are for 2 different methods of installing, the Zip file via SD card and the MD5 file by odin. Is this correct?
Click to expand...
Click to collapse
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
jiseuo said:
Yes. ZIP is for flashing from recovery and tar.md5 is for flashing from ODIN.
Maybe the best way will be to reflash your whole stock firmware to get correct previous state before you started flashing syiah. You can get it on Sammobile.com - (simple registration needed) and then use PhilZ recomended method - flash ZIP from stock recovery
What is your Country / operator, Try this http://www.sammobile.com/firmwares/2/ to find right and latest oficial firmware for your country / operator version for your phone.
edit: For XWLSH it may be GT-I9100LKJXSA - unbranded australia version, or GT-I9100LKJOPS - Australia OPTUS operator customized version.
Click to expand...
Click to collapse
Hi Again, solved the problem... definitely the siyah root was the culprit. I used mobile Odin to install the stock kernel, once done checked and could connect in kies and was still rooted missing busybox only. After that I again used mobile odin to install philZ, again no problems and all seems fine now. Everything working.
Thanks a million for helping and also many thanks to mobile odin developers as this is a far better tool than most and saves connecting to the PC Odin. Also seems a lot safer...
:good:
Hi there. I am trying to flash a stock rom to my gs5 900a with heimdall on my mac. the device is detected but i cant seem to download the pitfile it says claimed interface error. I think its because i system wiped my phone with safestrap when i was trying to intall a custim rom. anyhow I am softbrick state now. i cant get passed samsung galaxy window with the lock. myphone was also unlocked to use metropcs and it was also rooted. any information out there could that would help would be appreacited. thank you very much.
Leandrozx said:
Hi there. I am trying to flash a stock rom to my gs5 900a with heimdall on my mac. the device is detected but i cant seem to download the pitfile it says claimed interface error. I think its because i system wiped my phone with safestrap when i was trying to intall a custim rom. anyhow I am softbrick state now. i cant get passed samsung galaxy window with the lock. myphone was also unlocked to use metropcs and it was also rooted. any information out there could that would help would be appreacited. thank you very much.
Click to expand...
Click to collapse
The pit file isn't the cause of that particular error. It's a problem with the drivers installed by Kies, which interfere with Heimdall. More info can be found here:
http://blog.scott.wallace.sh/2012/03/getting-heimdall-to-work-on-your-mac.html
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!
Hi all,
I am a newbie and don't know much. So please bear with me.
I was trying to root my Galaxy S5(SM-G900H) by using the tutorial given on http://forum.xda-developers.com/showthread.php?t=2696537 but the process did not go as planned as keep struck on recovery.img on odin3.10 so I googled and found that changing USB port will help so I take out the battery changed the port and try again but this time I soft-bricked the phone as odin struck on cache.img and now when i try to start my phone I get Firmware upgrade encountered. So now I again googled and found about unified toolkit and install it on my windows 10 ,now when i choose option 6 (i.e. flash stock boot image to your device) it says waiting for usb debugging to be enabled ,now I remember I turn USB debugging on but it is still struck here. Now what should I do? My parents gave this phone just a week ago and I am in deep trouble.
P.S.-I am only able go into the download mode not recovery mode.
Boot into Download Mode and use Odin to install the original firmware. Might require a factory reset after if still bootlooping. Here is a link to 6.0.1 from Sri Lanka https://mega.nz/#!YMAFhR4a!pZmf7OEWgzDzET1FLGsAOQ5XyVlvE8y4pJfB8KDNbMI . Any region firmware should work for the F model. If you want your specific one then check sammobile.com. I just linked to the other because it is a much faster download.
Problem encountred while installing original firmware
I tried to use Odin to install original firmware , I started the process but Odin got struck on sboot.bin (Also I read somewhere that whole process does not take more than 10 minutes). So please help me.
Which firmware did you try?
You might be able to use Kies to recover your device as well.
es0tericcha0s said:
Which firmware did you try?
You might be able to use Kies to recover your device as well.
Click to expand...
Click to collapse
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
ratcoder said:
I downloaded it from http://www.teamandroiders.com/samsung-galaxy-s5-sm-g900h-stock-rom-firmware/ with PDA: I9500XXUBOL2. I want to know one more thing as I am in India so should I use INU or INS?
Click to expand...
Click to collapse
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
es0tericcha0s said:
Oh geez...no wonder it isn't working. i9500 = S4. Really gotta be careful with that kind of thing.
INU is for unlocked from the factory
INS is for phones from a carrier
Either one should work. As mentioned, with the G900h, any firmware should work that is for that model, no matter the region. Use the one I posted and change the language or grab the one for India from sammobile.com though it'll take an hour or 2.
Edit: I see that it was just mislabeled as i9500, but the download says g900h after all.
Were you on 5.1.1 or 5.0 before you started this process?
Click to expand...
Click to collapse
Well I downloaded another one from http://firmwarefile.com/samsung-sm-g900h the second one, before it all started I was on 5.0 and the link you give does not work anymore. Anyway I tried with the firmware with upper link. And Odin is struck with sboot.bin for more than an hour. And have no idea what's going on? So what should I do?
Also someone suggested to use Pit. Should I use it?
No, don't use the pit. Try the newer firmware for 6.0
es0tericcha0s said:
No, don't use the pit. Try the newer firmware for 6.0
Click to expand...
Click to collapse
So I downloaded the 3rd link from http://firmwarefile.com/samsung-sm-g900h for newer version and try Odin 11.2 with it. I try two times to flash the firmware first time it struck on sboot.bin and second time it just showed fails(I used Odin with administrative rights this time) .Please see the attached images. Please tell me what should I do now. I want to repair it ASAP.
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
es0tericcha0s said:
Not sure. This is pretty standard stuff. Have used Odin 1000 times and haven't had that much trouble with it. Sorry.
Click to expand...
Click to collapse
I think I should mention that the firmware I used was INS not INU and if you have a genuine link for version 6 for INU with fast download speed, please share it (different than sammobile because it has only fast speed only for premium users). Should I use PIT or try something else than Odin. Anything that might help please tell me. I have got this phone just a week ago and my parents are not gonna give me a new one so please help me.
I keep encountering sboot.bin error ,maybe there is a way to resolve it?
I'd just try to load TWRP and a custom rom at this point.
es0tericcha0s said:
I'd just try to load TWRP and a custom rom at this point.
Click to expand...
Click to collapse
Actually I have no idea what TWRP is so any link or anything that can help without ruining the situtation.
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
es0tericcha0s said:
http://forum.xda-developers.com/galaxy-s5/development/rom-t3224562
Click to expand...
Click to collapse
I want to know one more thing on the above link there is a custom firmware and there is a custom ROM with bootloader and all. So should I flash custom firmware or use the instructions given on thread to flash custom ROM?
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
es0tericcha0s said:
The custom rom does not include bootloader and modem. You will need to flash via Odin if you were not on the same firmware as the software is based off of. I would flash them anyway, to be safe. You can skip the root part as it is not need. Follow the instruction in post 2 for stock rom users minus the root part. Make sure to boot directly back into TWRP recovery before it attempts to boot. You can load rom on SD card and any additional add-ons you want. Plenty of youtube guides on how to use Odin to flash TWRP and such.
Click to expand...
Click to collapse
Finally seen some progress, thank you very much. I successfully flashed TWRP recovery, but I got a couple of questions. Firstly I should flash ROM from recovery mode and then go to download mode to flash boot-loader and Modem files right? Should I flash ROM from SD card? And if this custom ROM causes problem is there a way to get to stock ROM? And is this custom ROM rooted or I have to root it via CF-Auto root or try anything else?
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
es0tericcha0s said:
Rom might work without bootloader and modem. Just depends on your previous firmware. I would try and flash it though as it was recommended. Rom flash from SD card or internal. Either way should work. You will be able to go back to stock if you can find a firmware that works. It is already rooted.
Click to expand...
Click to collapse
Thank you very much.phone is working again with custom ROM.just one more thing if I upgrade from custom ROM what will happen?
:good::highfive::victory:
It should work to reflash the original firmware through Odin. Just get the one that matches your baseband version.