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!
Hey all. I had Hypderdrive installed. I updated it to 21 but had a force close issue. I wiped to reinstall in safestrap and realized that I didn't have the ROM on the device anymore. Whoops. All of a sudden I had no OS and couldn't connect to the phone via USB to put the ROM onto it.
After trying some stuff I got a bit more stuck. I can only reboot into 3 places: 1) Download mode (with volume down) 2) stuck at samsung unlocked icon (no buttons pressed) and 3) default recovery mode (with volume up). I tried with Kies to just install the latest firmware, figuring I'd be happy with lollipop and just go ahead and get a new phone in the near future. That firmware upgrade process fails right when the status bar shows up on the screen. Now rebooting the phone says Software Update Failed.
What are my options via Kies, Odin, or something else to either get back to rooted Hyperdrive or just get the latest firmware up and running? Thanks!
ODIN v3.10
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
This is the SCH-I545 lollipop image:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
And once you go forward..There is NO ROOT or ROMMING!!!
If you want to stay NK1 and ROOT:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
In ODIN, WITH EITHER file select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS CLEAR
Thanks a ton. Haven't gotten it to work yet. I followed your directions and Odin fails with "SW REV. CHECK FAIL : fused : 7, Binary : 6". My guess is that is a mismatch of the bootloader versions? I believe I was on NC5 before, so I tried flashing the No Wipe file from here: http://forum.xda-developers.com/showthread.php?t=2735172 and had no luck.
Any idea what version I should be trying to get it to work? Thanks for the help so far!
No. That means you are on lollipop Bootloader already! You have to flash lollipop
KaosMaster said:
No. That means you are on lollipop Bootloader already! You have to flash lollipop
Click to expand...
Click to collapse
Yup. Learned that while I was thinking about it. Such is life, right? Currently trying to just get OC1 installed via Odin but it keeps failing late in the process with XmitData_Write. If anyone has an idea beyond changing cables and ports (which I'm doing now) then I'm all ears.
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
volantis said:
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
Click to expand...
Click to collapse
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
KaosMaster said:
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
Click to expand...
Click to collapse
Thanks. I finally got it working. I'm not sure exactly what did it. I kept trying various combinations of flashing at CSC or AP and in Download mode and Software Upgrade Failed. I believe the one that actually took was the Sammobile stock OC1 file flashed as AP, but I'm not 100% and not sure that really is what made the difference. I did have all the options checked when it finally took.
After the Odin flash passed it did just boot to a black screen with the LED on solid blue. I went to recovery and did a factory reset and the phone booted up. Maybe that'll help someone else.
Don't have root anymore, but Lollipop seems like a very nice update coming from KK.
Thanks! - but still in trouble.
Spoke too soon!! Yours was the only one that actually loaded with Odin. After that phone will not reboot, just comes on for 2 seconds and then turns off. Any ideas would be greatly appreciated.
I have tried the following firmware versions, except for yours, they all get fused: 7 , binary : 6:
I545_VZW_I545VRUDMI1_I545VZWDMI1_Original
I545_VZW_I545VRUEMJ7_I545VZWEMJ7_Original
VZW-I545VRUFNC5-20140429111807
VZW-I545VRUFNG6-20141021092718
plus several others
--------------
Thanks, bricked my Verizon S4 and tried 5 different firmware files, including the ones from the Samsung site. Yours is the only one that worked.
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
volantis said:
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
Click to expand...
Click to collapse
Sorry, thought I updated the post. I tried again and the second time around it worked all the way through with the file on this thread.
I did a very very very stupid thing...
Hey,
Hundreds of times I did this with no problem. But when your head is away bad thing can happen.
I flashed RETUS 5.1 stock ROM over my XT1527 Latin American carrier (possibly Movistar Argentina) . Flash failed. As it turns out I completely forgot to UNLOCK BOOTLOADER first. So I get the code and try to unlock, but the damn ALLOW OEM UNLOCK setting is turned off.
So here I am with a dead phone and no way to boot back. I can only go to (stock) recovery buth nothing I do there really makes any difference. So far I've downloaded two Latin American stock ROM images with no success (Preflash validation failed). However I am concerned that even if I find the right ROM, it will not boot either because of the downgraded boot.
Any options, ideas? Im stuck....Thanks in advance!
Different reason but same problem...
Dang that sucks mate.
Rsd lite to get back to working phone
Sent from my XT1526 using XDA-Developers mobile app
dbx2r said:
I did a very very very stupid thing...
Hey,
Hundreds of times I did this with no problem. But when your head is away bad thing can happen.
I flashed RETUS 5.1 stock ROM over my XT1527 Latin American carrier (possibly Movistar Argentina) . Flash failed. As it turns out I completely forgot to UNLOCK BOOTLOADER first. So I get the code and try to unlock, but the damn ALLOW OEM UNLOCK setting is turned off.
So here I am with a dead phone and no way to boot back. I can only go to (stock) recovery buth nothing I do there really makes any difference. So far I've downloaded two Latin American stock ROM images with no success (Preflash validation failed). However I am concerned that even if I find the right ROM, it will not boot either because of the downgraded boot.
Any options, ideas? Im stuck....Thanks in advance!
Click to expand...
Click to collapse
If you can find someone with a working version of your phone, and in recovery push settings.db (I think) to the bricked phone and reboot into bootloader. then try OEM unlock
Or if you can find an official ROM for the device from Motorola, might be able to flash back to stock with the original firmware then try unlocking again.
sandix said:
If you can find someone with a working version of your phone, and in recovery push settings.db (I think) to the bricked phone and reboot into bootloader. then try OEM unlock
Or if you can find an official ROM for the device from Motorola, might be able to flash back to stock with the original firmware then try unlocking again.
Click to expand...
Click to collapse
I CAN get an identical phone to do whatever I wish with it. However the bricked phone has the stock recovery. Can I still push the file in that?
I have tried with several stock roms with no success. I can't seem to be able to get the correcto one. How do I figure out the correct CID and stuff? However my concern is that the correct stock firmware is XT1527_SURNIA_TEFLA-MSTCL_5.0.2_LXI22.50-53.8_cid12_subsidy-MOVSTLA_CFC and will not boot due to the bootloader being already updated to 5.1
same problem here with xt1528...
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.
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
moyabrit said:
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
Click to expand...
Click to collapse
use adb and flash androkernel to fix the incorrect kernel that you installed. you can do that by renaming it boot.img and sending the command fastboot flash boot boot.img
i haven't messed with androplus in a while but if you were on marshmallow i believe v34 will work and if you were on the absolute newest marshmallow i think its v35 off the top of my head.
fyi you dont need usb debugging on to use flashtool, you can get into fastboot mode with no rom at all installed.