Related
Hi Guys,
I'm sorry for the perhaps inane question, but I can't seem to get this to work:
I need to flash back to a branded t-mobile UK rom, as my phone has stopped recognising the sim card (sim works in other devices, working sims don't work in the s2) and I need to send it back to t-mobile for a warranty repair...
I never went too far into customization, and always stayed with official roms - just the more updated ones.
Anyway, now I try to flash back using these roms (http://forum.xda-developers.com/showthread.php?t=1113928), and it won't work... Hangs right at the last minute of the download:
Code:
<ID:0/018> Now Writing.. Please wait about 2 minutes
<ID:0/018>
<ID:0/018> Receive Response form LOKE
<ID:0/018> Complete(Write) operation failed.
That's the last thing I see...
I'm about to try the last of the 3 roms, but not holding out too much hope.
So, my questions are:
Will having an unbranded but official rom still invalidate the warranty?
How can I get one of these roms to work?!
Any help would be hugely appreciated.
Cheers,
Mike
Incidentally, I have tried and tried this, and searched for anyone solving the same problem (eg. http://forum.xda-developers.com/showthread.php?t=1369452), but to no avail.
And I'm still trying, somewhat desparately! I can flash some roms to get the phone booting - but none recognise the sim card (which makes me think it's a hardware problem, not software).
Again, your help would be hugely appreciated!
MikeAshelby said:
So, my questions are:
Will having an unbranded but official rom still invalidate the warranty?
How can I get one of these roms to work?!
Click to expand...
Click to collapse
If the ROM you're using is a Stock ROM despite being unbranded, there shouldn't be any problem. I recently send my HTC Desire with a Stock ROM to Vodafone support and didn't said nothing about it not being a Vodafone ROM.
As for the ROMs, try to flash the same PDA version as the ROM installed to see if it works without problem.
It does sound like a hardware problem.
I'd flash T-Mobile UK BOKG2 Firmware via Odin, reset the counter with a USB jig and send it back to T-Mobile.
T-Mobile UK
BOKG2
Firmware info: PDA:BOKG2|PHONE:BOKG1|CSC:TMUKF1
Thanks AzureusPT: I'd definitely argue that there shouldn't be a problem with there being a Stock rom on there.
I'm not 100% sure what you mean by flashing the "same PDA version as the Rom installed"; could you elaborate? The last ROM I managed to get working was XWKI4 - and that was wicked (save for the lack of sim!).
Spannaa: I can't get any of those firmwares (http://forum.xda-developers.com/showthread.php?t=1113928) working via Odin... Am I being a complete noob?
When I flash these roms, the phone reboots, then gets stuck at the boot animation. I did notice that when it's installing it says something about being unable to write to 'system/csc/TMU' or something similar; could that have something to do with it? If so, is there anything I should be doing to make that work?!
Not sure what you're doing wrong but, after rooting my sgs2 using CF-Root, I checked I could get back to stock by flashing the above firmware via Odin (following the instructions here).
OK. I'll take you through my process, and see what you think!
I download the pair of files (firmware and kernel).
I extract these zips into a directory.
I open ODIN3 v1.85.
I put the kernel in PDA
I put the firmware in CSC (I have tried a few combinations of these)
I hit start.
Now, sometimes it gets stuck at the end of the copying process (just before the reboot). If I reboot manually it tries to install.
Other times it appears to install properly (ODIN says PASS! though the phone does have an error as above (unable to write to 'system/csc/TMU' or something similar).
Then it gets stuck on the boot animation.
It works fine with these firmwares: http://forum.xda-developers.com/showthread.php?t=1075278, but they're not branded to t-mobile.
I'm worried that if I send it off they will say I've voided the warranty by installing non-t-mobile firmware. I've always stuck with official firmwares to be on the safe side - but now I seem stuck with unbranded ones.
Any thoughts?
I am so sorry... I'm a complete idiot.
I seem to have completely missed the very top sticky on this forum: http://forum.xda-developers.com/showthread.php?t=1108499
This is the one that's helped. I'm now back on branded ROM, and all is well. Thank you one and all for your help and patience... please don't flame me!
One more question. How do I know if I need to use USB jig? As far as my phone goes I don't have the yellow triangle, and it says "Custom Binary: No" on the boot loader when flashing a rom... I've only ever installed official roms (no custom roms) - so does this mean I'm safe warranty-wise?
If I need USB jig, can this be done via software, or do I need the dongle?
MikeAshelby said:
I extract these zips into a directory.
I open ODIN3 v1.85.
I put the kernel in PDA
I put the firmware in CSC (I have tried a few combinations of these)
Click to expand...
Click to collapse
**** man what are you doing???? Firmware and kernal both get flashed in the PDA section. So you can only flash 1 at a time. First firmware then kernal if required.
The firmware should already have a kernal built in.
Try again.
Edit: While I was posting it seems you got it sorted.
Sent from my GT-I9100 using xda premium
Thanks sxi200... Like you say, I got it sorted, but that's good to know for next time!
So the firmware has the kernel built in, so that doesn't need flashing - unless all I've done is root with an unofficial kernel - correct?
Any thoughts on the USB Jig thing?
MikeAshelby said:
Thanks sxi200... Like you say, I got it sorted, but that's good to know for next time!
So the firmware has the kernel built in, so that doesn't need flashing - unless all I've done is root with an unofficial kernel - correct?
Any thoughts on the USB Jig thing?
Click to expand...
Click to collapse
Yep. You only really need to flash a kernal when you want a custom one like cf root, speedmod, siyah etc. These can add things like root, cwm recovery for custom rom flashing, overclocking ability etc.
As for usb / download mode jig its mainly used to remove the yellow triangle and binary counter which show after flashing unofficial kernals in Odin. Its also an easy quick way to get into download mode. I bought one off eBay for $2 delivered.
Sent from my GT-I9100 using xda premium
MikeAshelby said:
Any thoughts on the USB Jig thing?
Click to expand...
Click to collapse
In download mode, if there's no yellow triangle and it says
Custom Binary Download: No
Current Binary: Samsung Official
then you don't need the USB Jig.
Thank you guys! I really appreciate that! I can go back to the t-mobile shop with my head held high!
I really appreciate all your help!
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
BCityModz said:
So i have never had so many problems with a phone, but this would be the first one a customer tried doing on their own.
So he downloaded the latest file from sammobile for his SCH-i605. he used odin to flash and was stuck in boot loop. I have tried many different methods to try and get his phone working. I have tried all of the alternate method files to no avail. the current file i have flashed is the VRAMC3 restore out of all the files i have tried this is 1 of very few that make it through the write. All the others fail on sboot. It currently sits on the unauthorized verizon blah blah blah. Its had no recovery since he brought it over and havent been able to get recovery back. All i have access to is download mode, some firmwares give me the kies screen talking about an error but cant get it seen in kies versions 2 and 3.
If you need any other info just ask, if i know the answer i will give it. He has no clue as to what OS he was on or even what the ROM that was on there.
Click to expand...
Click to collapse
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
mattnmag said:
If the person tried to ODIN flash the latest firmware version for the SCH-I605, then it would have been VRUFND7 4.4.2 Kit Kat. (Unfortunately... once you install 4.3 or 4.4.2 on our Note 2's, both of those firmwares lock the bootloader with no current do it yourself method to unlock it. You can't successfully flash a prior Android version onto the phone after you upgrade past 4.1.2 either because of the locked bootloader).
Check out Droidstyle's Restore Guide here: http://forum.xda-developers.com/showthread.php?p=34891181. You will probably need to flash the pit file with the firmware to get it to Odin flash successfully. You can grab the SCH-I605 16gb Pit file from the guide.
Even though Droidstyle's guide is a little old, it is still the same steps for restoring to 4.4.2, so if you follow the guide (section 1b), it should help you fix the phone.
He doesn't have a link for the 4.4.2 firmware, but you can grab it from Sammobile. It looks like the Sammobile site is currently down for maintenance, but the link is here: http://www.sammobile.com/firmwares/download/30950/I605VRUFND7_I605VZWFND7_VZW.zip/
If you're using an older ODIN, then I would probably try to use a newer Odin version like 3.0.9 or 3.10.0. Make sure you run it with Administrative privileges and disable antivirus programs.
Good luck!
Click to expand...
Click to collapse
Ive tried that one as well and almost all the files in that thread. When he flashed the 4.4.2 firmware the phone wouldnt boot all it did was flash the Note 2 screen. Ive used the pit file as well with no luck. Using the top file on the link fails almost instantly, VRAMC3 writes and passes but will not boot, shows the unauthorized firmware screen.
I'm wondering if he flashed a firmware onto the phone that was from a different carrier like ATT or something. If so, he may have messed up the phone so bad that it might need jtag to repair it.
You've probably already tried all the normal Odin tips like using a different usb cable, different ports on the computer (usb 2.0 port is recommended), etc... so I won't go over all those.
I've never tried it and don't know if I'd recommend it, but I recall reading some threads a while back where someone discussed trying the Nand Erase function in Odin.... (again.... I'm not saying to do that... but you may want to research it to see if it might be an option if nothing else works).
I've also read where people say that they've used Cygwin to create custom tar files... then they ODIN installed each of the separate partition files (e.g. recovery, boot, modem, system, etc...), onto their Samsung device.
I'm not knowledgeable enough to offer guidance with Cygwin and I'm not sure if either of these ideas would work, but I just thought I'd throw them out there for the sake of brainstorming for ideas. Maybe someone will respond to your request who has more knowledge and ideas.
I wish you luck with getting it fixed.
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
logannixon.la said:
I was simply messing around with my old Verizon GN2, because I need a phone to use in the absence of my htc one M9. I went to flash the "stock" version of the bootloader (the bootloaderbaseline2.tar) before I went in to do any real damage and the phone rejected it. The phone screen read the error message "wrong magic string" and the odin display reported that it dropped out after sboot.bin. Just curious whether you guys and your wisdom would have any insight in the matter? I would really prefer not to have to go out and buy another phone.
Also, woohoo for a first post on the forums.
Cordially,
Nixon
Click to expand...
Click to collapse
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
bigmike35 said:
Are you flashing the full firmware or just bootloader? What options did you have checked and where (in what slot, PDA?) did you put the file to run it? What version are you on, 4.4.2; 4.3? Have you unlocked it before?
Click to expand...
Click to collapse
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
logannixon.la said:
I had this phone rooted before, but it wasn't playing well with what my sister wanted it for. So, I flashed a stock image and it rebooted into its stock form. That was two ish years ago. The bootloader was never unlocked. When I brought it back out to begin tinkering, a lot of guides said to flash the stock bootloader (the bootloaderbaseline2 file) and to repartition it before going ahead with something like CASUAL. Considering my sister used it as a daily driver for quite a while, it was probably on 4.3 or whatever the last update Verizon handed out was. I do remember checking to see whether or not it had any available updates and it said it was completely up to date. When I set it up to repartition and flash the BB2 file, it was in the bootloader slot. The Odin flash then failed at the sboot.bin output and the phone proceeded to slide into the good old "connect to Kies" screen. I tried several attempts to get the BB2 file to stick (putting it in all the slots and trying it without partition and auto reboot), but all were to no avail. I have since flashed multiple firmwares in the PDA slot with only the root66_vzw_stock_system.tar.md5 version completing. However, it now displays the "Device firmware is not from verizon. Please bring it into a Verizon store for help." I know the verizon reps will be useless, so I asked you beautiful people.
The only odin boxes that I played with were the top three.
Also, thanks for responding. I appreciate it.
Nixon
Click to expand...
Click to collapse
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
bigmike35 said:
So it it on 4.4.2 then since all updates are up to date? If that is the case, you can only root using towel root. You can downgrade to 4.3 or 4.2.1 but you would need to send it in ($75) i believe or try the method here that is posted. If it is still on 4.3 i believe you can flash the 4.2.1 firmware and then run root running casual (disable firewall and antim virus else wont complete). Then find Beanstown thread and download the zip for the updated wifi/bootloader for 4.3 with ND7 radio (zip somewhere as well) to upgrade completely to newest radio/images (so it would be a 4.2.1 or 4.3 stock with complete root and unlocked). Then install TWRP and roms
Click to expand...
Click to collapse
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
logannixon.la said:
So, for the moment, is there any way to get it back to stock? I was trying to go the custom recovery route in the beginning, but I now just need a phone that works. I'm pretty sure it's the bootloader firmware that is preventing the device from booting completely. Thanks for all your help.
Nixon
Click to expand...
Click to collapse
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
bigmike35 said:
You can see if you can flash the full Verizon firmware. Should be able to find it here or on Samsungs website.
Click to expand...
Click to collapse
So the stock Verizon firmware will repair the broken bootloader? I'll give it a go. Thanks for the info.
Just a quick update. I flashed the stock firmware for 4.4.2 and everything went over swimmingly. The phone now boots all the way into the Verizon boot splash screen. It then sits there and will not progress. I've tried wiping cache and factory resetting, but it still hangs on the Verizon splash screen. Any pointers?
Thanks again,
Nixon
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
logannixon.la said:
Another side update. It's still held up on the Verizon boot splash screen, but the led is now pulsing. *Shrugs in confusion
Nixon
Click to expand...
Click to collapse
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
bigmike35 said:
Ya i have had that issue before, but I did what you did is to wipe cache, data, factory and that normal let me get a full boot in.
Click to expand...
Click to collapse
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
logannixon.la said:
Yeah, I've tried the factory reset and wipe cache, it still gets caught in the Verizon boot loop. I'm not particularly sure what that else to do. The 4.4.2 stock md5 is the only one that will stick in Odin.
Click to expand...
Click to collapse
are you flashing it with the PIT file as well?
bigmike35 said:
are you flashing it with the PIT file as well?
Click to expand...
Click to collapse
I think I tried with and without, but I'll give it a shot.
logannixon.la said:
I think I tried with and without, but I'll give it a shot.
Click to expand...
Click to collapse
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
bigmike35 said:
Ya put that in the PIT tab and firmware in PDA. When it finished, does it say complete or done (box turns green, near top left?)
Also, maybe try another firmware/version?
Click to expand...
Click to collapse
I tried the pit to no avail. Currently wiping again just for fun. Not sure if it helps, but the system recovery screen reads this
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.
Hi all
Just want to say I've been using XDA for a very long time, back to the OG Droid days, and wanted to say thanks right off the bat to those who are more skilled than I and for the help posted.
I recently aquired a sch-I545. The phone is in excellent condition, the only issue was that it was missing the IMEI, it's on the phone sticker, just not software. The baseband is also unknown. I knew this when buying it, that's how I got it so cheap. I figured that the guy had tried to flash it, and just didn't want to own up to it.
However, I have hit a wall. I've tried flash a stock rom on it so that I could root it and gain access to the EFS folder and see if I could modify anything. When I did, even though there was an EFS folder there was nothing to modify. I then heard about flashing a modem.bin to see about correcting the baseband and possibly the IMEI. Though I was rooted I didn't have a custom recovery, as of yet. I went to install TWRP via Odin and it starts the NAND write and then Fails.
So at my wits end I took it to a local shop, hoping that they might have better experience with this and I got the phone back today, with the Software Update Failed screen. I asked what was up, and was told that since someone tried to flash it, they erased the IMEI and they couldn't correct it. Asked why they gave me the phone back with the screen and was told that they too tried to flash with ODIN and it failed.
Luckily I didn't have to pay anything, but I think they just borked things up to and didn't want to own up to it lol.
SO....here's my question.
Can I flash a stock, or rooted ROM to this puppy that already has an IMEI and Baseband, and then Modify the IMEI to the correct one that is stickered on the phone? If I can, what search parameters should I look for? And is there a particular version of ODIN I need to use?
If I can't flash a ROM that already has a baseband and IMEI, how can I go about correcting this issue if ODIN doesn't want to write a custom recovery?
Thanks
You'll need Odin software and the correct factory image for the phone. There are a couple different builds so make sure to get the right one. If it's an MDK device and has never taken an OTA you're in luck. It can get TWRP on it after following the process. If it's later than MDK no TWRP. Search here and you'll find a thread explaining how to do it all.
Is there any way to tell if it's MDK after I flash the correct factory image? I have no clue if the person before updated via OTA.