Hey guys, im new.
Got a question if you dont mind? (hope this is the right place to post)
I have a Galaxy S2 GT i9100, im on the network 3 in the UK, and the phone is unbranded and unlocked.
i recently flashed the Polish version of the official ICS because i am impatient. (3 released their version 3 days later )
so, i began the process of flashing an older rom, KE7 to be exact, just so Kies can accept my phone to back up and to receive the latest official UK release of 3s ICS. I have successfully flashed and kies recognised my phone, but the version it is suggesting to update to is KI4??
Do i need to update the firmwares previous to ICS before i can actually get ICS?
Any help will be appreciated.
thanks
You need to flash the 3 branded firmware in order to get the recent 3 update. If that's what you did then I don't know what's wrong. If you didn't do that then go get the correct firmware from here...
http://forum.xda-developers.com/showthread.php?t=1113928
Thanks for the reply,
foolishly i never checked what the original firmware was, but i never had a '3' logo on the boot up of the phone, i didnt buy it from '3' either, i got it from an online based contract provider on '3'.
So i just assumed i could reflash a sim free firmware then kies would recognise my number as being a '3' number - or is this not the case?
Do you think i should download the KI4 and see if it recommends a futher update?
Cheers
will do, il report back.
Officially updated through kies to 2.3.4 KI4, but no update to ICS. hmm, not sure what to do next, try another base firmware?
Any suggestions?
If you have an official 3 firmware then it should be offering you the update, as far as I'm aware. I suppose the fact that it came from a non-3 supplier may make a difference.
The alternative is to just download and flash the latest 3 firmware yourself, which you can get here...
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-I9100&r=1
Just scroll to the bottom of the list and you'll see LPQ for 3 customers.
ahh, that was going to be my next question 'would the fact i got it through a third party vendor determin whether i got ics through 3' i cant find a clear answer for this.
so if i take the bloatware on the chin and get ics through odin on 3, would kies recognise this and enable me to back up?
Hi there i recently bought a Samsung galaxy Nexus unlocked, build ITL41F.I9250XEKK9 its an att docomo phone that i bought off amazon.
Anyway when i go to search for updates it says the phone is up to date and there are no new updates and i'm currently running android 4.0.1.
I did seach google, but i really no nothing about roms and flashing devices so i didn't really understand much.
By the way the first time i connected the phone to wifi it updates the phone but it only did this once. The current version is ITL41F don't no what it was before the update.
Can someone help me or give me a guide to how to update my galaxy nexus ITL41F to a new version of ICS. By flashing the device and using an official ICS rom.
Any help greatly appreciated.
any help anyone?
Same problem here
I've got the same problem here. It installs a "system update" periodically but I'm still suck on 4.0.1. My build # and purchase location are the same. Did yours come bootloader unlocked, i.e., do you see the padlock icon when you first turn on the device? Unfortunately I didn't figure out what the padlock icon meant until it was too late to return it to Amazon.
I'm starting to get worried that someone sold me a hacked firmware that is sniffing my passwords...has that ever happened?
To mods, sorry, but I checked the "is this a question" box my mistake, the following is not a question but asking for assistance.
Hello, first off apologies if this has been asked before and thanks in advance for any assistance offered.
The good folks at HTC decided to make a few changes from ICS to JB that have seriously in my view are a downgrade.
So here are the specs:
Current:
HBOOT is now 2.14
ROM: 3.70 (Telstra variant)
I downloaded the RUU_Evita_Telstra_1.89 but get error 140: Wrong bootloader, and I cant find the previous 4.0.4 stock firmware which I think from memory was RUU_Evita_UL_Telstra_WWE_2.70
So after doing some research I found that I need the 1.14 bootloader as the upgrade from ICS to JB changed the bootloader.
Since I have no idea how to change the bootloader I need some help (never had these issues with Samsung galaxy S II, much easier using odin to flash what ever firmware you wanted).
From memory, the previous version firmware was:
- 4.0.4 2.70 (Telstra)
Note: I have not rooted or unlocked the bootloader, I am not into using CFW all I want to use is the stock firmware.
If anyone can provide assistance then thank you very much.
I look forward to reading all replies and all help provided.
Again apologies if this has been brought up before but after 3 days of searching and not finding anything relevant its time to ask for assistance.
Thread still belongs in Q&A moved
Previous version before the Jelly Bean update is 2.40 with hboot 1.14
I think you might be stuck unless the jet application works on the new hboot but even for that to work (I'm not saying it will, I'm not sure if anybody knows yet) you already need to be unlocked with SU and a custom recovery.
Seeing as you're completely stock I think you're more than likely stuck with it - why would you wanna downgrade from Jelly Bean goodness anyways?
Bump to ask what's better in ics then jb for yourself?
I would have to be loco to go back to ics after this smoothness that jb has brought us.
So loco or what?
WR
Sent from my Jelly Bean One XL
WarRaven said:
Bump to ask what's better in ics then jb for yourself?
I would have to be loco to go back to ics after this smoothness that jb has brought us.
So loco or what?
WR
Sent from my Jelly Bean One XL
Click to expand...
Click to collapse
Whats better?
Well I cant use the apps I mentioned in JB, but that is a 3rd party reason, the other main thing is use of MTP over proper USB Mass Storage Mode connection.
HTC have removed the "Connect to PC" option which allowed the One XL to mount as a USB Mass Storage device which which great for the car audio system I use, my Sony deck (touch screen) cant read MTP mode.
So yeah hence why I am asking for assistance to downgrade back to ICS, preferably ICS 4.0.4 2.70 for the One XL also the modem radio is is now worse in both 3G dual band 850/2100 and in 4G 1800 ...
I used to get RSCP -55 HSPA+ at home now I am lucky to get RSCP -105 HSDPA and its not the network as my Galaxy S II (the I9100T variant) with actually the stock I9100 XSA 4.0.4 firmware gets RSCP -55 HSPA+ here.
So yeah While JB is smooth and all that to me its a downgrade in performance hence why I am asking for help to change the bootloader back to HBOOT 1.14 and thus re-instal the RUU_EVITA_UL_Telstra_WWE_2.70 firmware again.
Any help is very much appreciated as HTC have told me to basically they are not going to help.
I cant find where you mentioned apps that do not work. I can understand your issue with the change to USB. Perhaps that can be overcome with a build.prop change?
Eg:
persist.sys.usb.config=mass_storage,adb
Or get a rooted 3.17 and try some of the usb mass storage enabling apps on the Play Store.
Or wait for a dev to make a kernel that will make this work
There was no 2.70 version, it was 2.40 previously with Telstra.
You have all the below available to you.
Perhaps with Jet and some other trickery you could get back to 1.89 then update forwards to 2.40. You would really be one of the first users to try it and may kill your phone. You need to manage the hboot and current software version checks at very least.
1.81.841.1
RUU - RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
1.89.841.9
OTA - http://fotadl.htc.com//OTA_Evita_UL...81.841.1_R_release_266785ap9qro3i4pvkmhv0.zip
RUU - RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32.09.01_10.93a.32.20L_release_266699_signed.exe
2.40.841.4
OTA - http://fotadl.htc.com/OTA_EVITA_UL_...1.89.841.9_release_279477r07a3nyy05j4vcis.zip
RUU - Not leaked
3.17.841.2
OTA - http://fotadl.htc.com/OTA_EVITA_UL_...128.32.34a_release_2997538hizl4svcm80o4g1.zip
RUU - Not leaked
twistedddx said:
I cant find where you mentioned apps that do not work. I can understand your issue with the change to USB. Perhaps that can be overcome with a build.prop change?
Eg:
persist.sys.usb.config=mass_storage,adb
Or get a rooted 3.17 and try some of the usb mass storage enabling apps on the Play Store.
Or wait for a dev to make a kernel that will make this work
There was no 2.70 version, it was 2.40 previously with Telstra.
You have all the below available to you.
Perhaps with Jet and some other trickery you could get back to 1.89 then update forwards to 2.40. You would really be one of the first users to try it and may kill your phone. You need to manage the hboot and current software version checks at very least.
Ah ok, no wonder I could not find RUU_Evita_UL_Telstra_WWE_2.70 ... my mistake, I am not that much into modding my One XL as much as the Galaxy S II, Note I and Note II that I have so I dont pay that much attention to it.
I dont want to root and unlock the One XL as its not mine (company) hence why I need stock ROM, but what annoyed me was HTC not mentioning that several the changes made which to me are a downgrade for what I need to handset for.
I will try to the 2.40 ROM as from the research I have done so far suggests that it should work with HBOOT 2.14 version.
Just another question if I may, so this file is a ZIP file and not an exe file, so in order to install it I will need to use something like clockworkmod?
If so I am not that good at being able to figure that out (again its not like using ODIN for Samsung), I hate to ask but how is that done again?
Again many thanks and as its 2013 here in Sydney happy new year!
2013!
Click to expand...
Click to collapse
You can't use the ota to roll back like this. It does not even help much going forwards versions with your phone locked. You would need the phone to get the download itself.
Ruu would be your only hope, and your 2.14 hboot will not accept the 2.40 Ruu (which is not publically available) as it only has 1.14 hboot.
There is 100% no chance you can downgrade your phone without unlocking it even if the 2.40 Ruu was available, which it isn't.
There is only very minimal chance you can downgrade even after unlocking it.
Ps your OP says you are running 3.70, is that right or is it just 3.17?
twistedddx said:
You can't use the ota to roll back like this. It does not even help much going forwards versions with your phone locked. You would need the phone to get the download itself.
Ruu would be your only hope, and your 2.14 hboot will not accept the 2.40 Ruu (which is not publically available) as it only has 1.14 hboot.
There is 100% no chance you can downgrade your phone without unlocking it even if the 2.40 Ruu was available, which it isn't.
There is only very minimal chance you can downgrade even after unlocking it.
Click to expand...
Click to collapse
Thats what I thought, stupid HTC and Telstra for screwing up, the phone in short is screwed with the JB update, tonight could not get any signal from the network to it whereas with ICS 4.0.4 it worked 100% in the same spot the previous month and again its not the network as my other Andorid devices are working A1.
One XL RSCP -110 UMTS v Galaxy Note RSCP -60 HSPA+, and this is supposed to be a blue tick (means works in regional/rural areas without need for external antenna) handset.
Do you have any idea if and when the public RUU 2.40 will be able to download? then again if it wont work with HB 21.4 then how do I go about changing the HBOOT back to 1.14? Again I have no idea with HTC, they have to make it hard unlike Samsung, hell I would rather make changes to LG Qualcomm based Brew OS and install that firmware using Qualcomm Tools 4.5 or use Phoenix to change firmwares on my spare Nokia N8 then try to figure out how to mod this HTC device.
HTC advised me to go back to the dealer (it was bought online so that rules that out), made a call to Telstra, they said not our problem go to HTC, HTC said go back to dealer, in other words chasing my tail like a dog would going in circles, as a last resort I made a call to a authorized service centre, they said cant be done under warranty but can be done for a price, they want something like *$350 AUD to downgrade it (seriously fonebiz), obviously my company said no and I cant change the handset either as need 4G support.
So you can see why I am trying to find a solution to fixing HTC and Telstra created issues via these forums.
Again any assistance would be greatly appreciated
*the $350 would b e to replace the mainboard with a new mainboard that has 4.0.4 ICS on it already but with a blank IMEI and as such they would flash the NAND NV with the numbers from the replaced mainboard ... also this would also end Warranty for the handset by HTC and only provide warranty by Fonebiz for 3 months on the replaced mainboard ...
As I dont own the handset I cant take that option, which is why I cant root or unlock it to use CFW, believe me if I did I would of done it ages ago, which is why I dont know anything about HTC as my personal handsets are from Samsung (much easier to modd IMHO).
I have uploaded two screen grabs.
ARGHHHH, To many numbers going through my head right now,
According to the Software info:
Version: Android 4.1.1
Sense: Sense 4+
Software Number: 3.17.841.2
HTC SDK API Level: 4.63
All the other numbers don't matter. Just the hboot 2.14 and the build 3.17.
It is unlikely the 2.40 Ruu will leak. Not all always leak. You could ask in places that Ruu leaks are found though. Often they need to be purchased on the black market. Plus the Ruu is useless to you unless you unlock and start forcefully downgrading things.
You are wasting your time unless you unlock, use jet to downgrade the hboot and alter the software build to 1.00.
Or buy a new main board.
Or live with the new update. Use a usb stick for $7 for the radio or Bluetooth or buy a new head unit.
No idea about coverage personally I did not see it decrease because of the update. But it is what it is. If you purchased from Telstra you would have a leg to stand on complaining.
Samsung devices are not all rosey and good. There is a long list of variants of s2 and s3 which you can't do squat with.
Your HTC one xl has options you can try but you are choosing not to do them.
Simply call the complaints dept at Telstra, explain that the latest ota has made the phone useless to you (not support they're useless). They will most likely credit the account or offer to swap you to a different blue tick device, it's a shame they're aren't any good ones
Sent from my HTC One XL using xda app-developers app
The one xl is a blue tick device. The user has supplied their own phone, it was not purchased from Telstra. I doubt they will offer a new handset.
Where do I find JET from?
The handset is from Telstra it was purchased online though Telstra website so there is no dealer, Telstra have said they don't help neither will HTC.
The One XL over the Galaxy Note? The Gnote other than not having 4G radio is simply better and again much easier to flash what ever stock ROM you want, simply use the new updates Check_Fus program find your model and download straight from Samsung server then use either old ODIN or need ODIN and flash what ever firmware or modem you want.
So being where XDA is supposed to be be great at providing technical advice and such I would of thought that people here would be willing and some have to help out and that others Herr with the One XL have been able to downgrade or go back to stock firmware and then help out those who don't know how ...
As for the USB options, putting on a USB KEY/PASSPORT device iss not a viable option at all, if that were the case I would not have brought it up here, I do a lot of driving way to much and am on the road a lot thus I need power and since 4G consumes vast ammounts the old way of USB would charge the handset (much faster than using cigarette lighter plug) also I don't get the static in the audik playback from the aux/lighter connection method.
So again is there anyone who can further help me out or do I simply sell the HTC and go buy another GNote (forget GNote2 no proper USB option and again apps that I use do not work in 4.1.1)
???
I have been trying to help. I have said what you could try to do several times, but you have never attempted to do it.
Comparing a Nexus device with a non-Nexus device when it comes to ease of customizing is pointless. That is the point of Nexus devices, if you wanted one you should have bought one??
If you purchased from Telstra, you have every right to complain to them that an update that they approved has significantly reduced the coverage of your phone without warning. Just claim you purchased the device due to it being blue ticked by Telstra and the range it offered in the areas you are using it in. Demand they offer a way to return your phone to its original coverage via a downgrade or another update.
1)You need to unlock. You have no chance of performing this unofficial software downgrade path without unlocking. If that is unacceptable, sell the phone.
http://www.htcdev.com
2)You likely want to use Jet to attempt to downgrade the hboot back to 1.09. You also get the bonus of supercid allowing using any RUU you want not just Telstra, so the lack of Telstra 2.40 RUU becomes less important, just use HK 2.42 RUU instead.
http://forum.xda-developers.com/showthread.php?t=1982442
3)I believe you also need to fix up another version sitting on another partition that the RUU will check
http://forum.xda-developers.com/showthread.php?t=1671135
4)Flash a RUU
Telstra 1.89 if you like:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32.09.01_10.93a.32.20L_release_266699_signed.exe
Personally I would flash Hong Kong 2.42. It is 4.0.4 and should be able to install with hboot 1.09.
The Hong Kong 2.42 ROM is almost identical to Telstra 2.40.
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.exe
I dont think anyone else has attempted downgrading the hboot 2.14 back to 1.09.
That is why there is no long list of users with previous experiences in doing it. You are the first, once you have got the answer you could tell everyone else how you went.
Good luck.
EDIT: Apparently someone else has tried this, it allowed him to flash 1.81 RUU (would not have been my pick but whatever) and it ended in bricking the phone.
Just a big fat warning
twistedddx said:
I have been trying to help. I have said what you could try to do several times, but you have never attempted to do it.
Comparing a Nexus device with a non-Nexus device when it comes to ease of customizing is pointless. That is the point of Nexus devices, if you wanted one you should have bought one??
If you purchased from Telstra, you have every right to complain to them that an update that they approved has significantly reduced the coverage of your phone without warning. Just claim you purchased the device due to it being blue ticked by Telstra and the range it offered in the areas you are using it in. Demand they offer a way to return your phone to its original coverage via a downgrade or another update.
1)You need to unlock. You have no chance of performing this unofficial software downgrade path without unlocking. If that is unacceptable, sell the phone.
http://www.htcdev.com
2)You likely want to use Jet to attempt to downgrade the hboot back to 1.09. You also get the bonus of supercid allowing using any RUU you want not just Telstra, so the lack of Telstra 2.40 RUU becomes less important, just use HK 2.42 RUU instead.
http://forum.xda-developers.com/showthread.php?t=1982442
3)I believe you also need to fix up another version sitting on another partition that the RUU will check
http://forum.xda-developers.com/showthread.php?t=1671135
4)Flash a RUU
Telstra 1.89 if you like:
RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32.09.01_10.93a.32.20L_release_266699_signed.exe
Personally I would flash Hong Kong 2.42. It is 4.0.4 and should be able to install with hboot 1.09.
The Hong Kong 2.42 ROM is almost identical to Telstra 2.40.
RUU_EVITA_UL_ICS_40_S_hTC_Asia_HK_2.42.708.3_Radio_0.20os.32.09.15_10.113.32.28L_release_286715_signed.exe
I dont think anyone else has attempted downgrading the hboot 2.14 back to 1.09.
That is why there is no long list of users with previous experiences in doing it. You are the first, once you have got the answer you could tell everyone else how you went.
Good luck.
Click to expand...
Click to collapse
I would totally agree with this,take it up with Telstra if they don't come to the party lodge a complaint with the TIO .I have had issues with them with this phone, they replaced the first one because it did not perform to blue tick performance, This one was crap until I unlocked the boot loader and rooted,they offered to send it away and repair it but I told them what I had done to fix it, and they said if it was still no good in the future to let them know and the offer still stands.
After a very heated conversation with HTC they have agreed that they have a made an error in removing "Connect to PC" option thus proper USB Mass Storage Mode, in the future 4.1.2 update it will be returned, so success on that end, for the time being they have emailed me a letter to take to FoneBiz which advises FoneBiz that the One XL is to be reset to stock 4.0.4 2.40 Telstra ICS firmware free of charge to the owner.
It took 2 goes with HTC for HTC to admit they screwed up, as a sign of good faith they are also sending me a new One X+ since i took time to basically verbally belt the crap out them, which I have no intention of using as it will be up on Ebay for sale once it arrives.
So now I have to take One XL to FoneBiz to get it back to the way it was.
You can also thank for getting HTC to reverse a most silly decision of forcing owners to use MTP mode, it will still be there but proper USB Mass Storage mode will return in the next update (when ever that might be).
For the time being I am using my work Telstra SIM in my Galaxy Note and that SIM is being used in the One XL.
I have a galaxy s2 Sch-R760 that I would like to root..the problem is that my original carrier was Appalachian wireless. I went to the website b/c there was a software update for my phone..I download everything and do it step by step..Thinking it worked I turned my phone on and us cellular pops up? Never happen before.. Changed the baseband version to-FL26, build # to-Imm76d.fl26, and android version-4.0.4..
Well the really weird and messed up thing is my wife has the same exact phone. She done the update first. And it worked.Didn't change her carrier or anything..her baseband version went to-gb28,build# jz054kschr760X.gb28. And android version to-4.1.2. How did this happen? I have tried re-downloading the upgrade 2times..done a hard reset more than once.. And I had the phones on a contract.there not currently "hooked" up but will be..but I have wanted to root it forever..can I flash it back to whatnot was before and then root or what? Sorry if this was to much but I can't break it down any more.. Please help
abennett86 said:
I have a galaxy s2 Sch-R760 that I would like to root..the problem is that my original carrier was Appalachian wireless. I went to the website b/c there was a software update for my phone..I download everything and do it step by step..Thinking it worked I turned my phone on and us cellular pops up? Never happen before.. Changed the baseband version to-FL26, build # to-Imm76d.fl26, and android version-4.0.4..
Well the really weird and messed up thing is my wife has the same exact phone. She done the update first. And it worked.Didn't change her carrier or anything..her baseband version went to-gb28,build# jz054kschr760X.gb28. And android version to-4.1.2. How did this happen? I have tried re-downloading the upgrade 2times..done a hard reset more than once.. And I had the phones on a contract.there not currently "hooked" up but will be..but I have wanted to root it forever..can I flash it back to whatnot was before and then root or what? Sorry if this was to much but I can't break it down any more.. Please help
Click to expand...
Click to collapse
Are you talking about the update from Samsung's website?
If you're talking about just upgrading an Over The Air (OTA) Upgrade, it should be able to be done from your "About Phone" settings. It should upgrade your baseband and android version to the proper versions that your carrier and phone manufacturer provide.
If you're talking about rooting and a custom rom, XDA has loads of files and guides to help you with rooting the phone, installing a custom recovery, and learning to flash ROMs and modems and such to your will.
I hope this helps you, but I don't know too much about your carrier.
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Benno81 said:
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Click to expand...
Click to collapse
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Benno81 said:
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Click to expand...
Click to collapse
Are you trying to update via the phone update feature? If so this won't work as rooting disabled the ability Update using ota
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Benno81 said:
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Click to expand...
Click to collapse
From what I can tell you have a g920v variant if the phone Shows Verizon but the sure fire way to know what variant you have is turn the phone off once off hold home-power-volume down, this will take you to download mode but should tell you your variant. You don't need to root a phone to refurbish It, you can flash Stock firmwares via Odin. I really don't know why they would have Rooted It tbh, you'd need to contact them, but I know for sure you can manually download the latest Verizon firmware and the phone should work. Maybe they Rooted it as part of making it network unlocked, o really can't say
Ok I tried that and a bright blue screen came up warning about custom OS then press up volume for download and down volume for reset? I just pressed down as there was no other info on the screen but it does say it's a sm-g920v in the settings as well as the root checker app. Another thing was I did ring samsung support gave them the serial number and IMEI and they said an authorized modification had been done on the phone but could offer no other support as it wasn't an Australian phone. I'll keep trying to get some info out of the company I bought it off and try to sort it out thanks for your help :good: