Related
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.
Hello guys,
I received my razr HD (925) today. It was already updated to 4.1.2.
Coming from my galaxy s2, where obtaining root is pretty easy I followed the first of your guides here - but failed at reading correctly:
I tried the "all in one tool" to get back to ICS to obtain root using the rootkeeper.
Something went wrong, the SW remained 4.1.2, but I had no radio signal any more (only verizon version I read lateron)
Now I managed to flash a france 4.1.1 s/w using RSD 6.1.4 - still having no root but can use it again, at least.
Is there any chance to get my (newer) original version back? At best rooted?
robinkrumm said:
Hello guys,
I received my razr HD (925) today. It was already updated to 4.1.2.
Coming from my galaxy s2, where obtaining root is pretty easy I followed the first of your guides here - but failed at reading correctly:
I tried the "all in one tool" to get back to ICS to obtain root using the rootkeeper.
Something went wrong, the SW remained 4.1.2, but I had no radio signal any more (only verizon version I read lateron)
Now I managed to flash a france 4.1.1 s/w using RSD 6.1.4 - still having no root but can use it again, at least.
Is there any chance to get my (newer) original version back? At best rooted?
Click to expand...
Click to collapse
Maybe I should add, that it looks like my main problem is to find the up to date SW that was installed.....
Maybe I should send be back to my provider, get a new one and then do a dump / image and upload that BEFORE I "brick" it again =)
I would try to hard reset it and then try Matt's tool to go to back to 4.0.4 again.
Sent from my RAZR HD using xda app-developers app
Reflash ur rom or downgrade to ics http://forum.xda-developers.com/showthread.php?p=36345060
[XT925] Downgrade to ICS stock rom ! Root any JB rom !
U can also reflash ur modem
Sent from my RAZR HD using xda app-developers app
Get the Droid Razr Utility
Then:
1. Use option 1 to go back to ICS
2. Go to settings - about phone and take the 6mb update.
3. Root using the utility
4. Install voodoo ota rootkeeper either from the utility or Google play
5. Open voodoo and protect root
6. Temporarily unroot.
7. Take the JB OTA
8 Open voodoo and restore root.
Use this method for XT925
http://forum.xda-developers.com/showthread.php?p=36345060
The extide method is for VERIZON PHONE ONLY XT926
@extide
that was what I was doing - and what was not working.
---
To the other guys:
THanks, I'm going to unlock the bootloader then. Unfortunately it looks like some things have been changed in the factory delivered 4.1.2 so that not even safestrap is working any more.
With a locked bootloader the revert to ICS is not working.
Why you don t want unlock the bootloader ?
Sent from my XT925 using xda premium
o2qc418 said:
Why you don t want unlock the bootloader ?
Sent from my XT925 using xda premium
Click to expand...
Click to collapse
There are two reasons right now:
- I'm from germany and here we have seperate restrictions for warranty and guarantee (one is forced by law, the other is provided by motorola).
Motorola is not doing to repair unlocked Razr HDs
- My phone is new and I'm not sure whether I'm going to keep the Razr HD - unlocked it might be a problem to give it back to my dealer during the "test month" he offered.
(I still have my Galaxy S2 and had LOTZ of fun with new custom roms, trying different combinations, getting all the newest stuff ported right after it has been leaked anywhere for any modell - and on the other hand, there is not even the source to get my retail software back because no one shared it)
robinkrumm said:
There are two reasons right now:
- I'm from germany and here we have seperate restrictions for warranty and guarantee (one is forced by law, the other is provided by motorola).
Motorola is not doing to repair unlocked Razr HDs
- My phone is new and I'm not sure whether I'm going to keep the Razr HD - unlocked it might be a problem to give it back to my dealer during the "test month" he offered.
(I still have my Galaxy S2 and had LOTZ of fun with new custom roms, trying different combinations, getting all the newest stuff ported right after it has been leaked anywhere for any modell - and on the other hand, there is not even the source to get my retail software back because no one shared it)
Click to expand...
Click to collapse
If you don't want unlock the bootloader ... you can't get back !
( flash the original logo ... the dealer see nothing ... )
sorry no others solutions !
Man i got same proble here! need help!
EDIT: I sended mine back, he was blocked in AP fastboot. hope they can do something...
Hi, i'm kinda new to Rooting HTC Devices, but not to rooting android devices in general. I was wondering if it was safe to take the OTA Update to get the Latest Firmware / Radios Etc, and then Install Viper One 2.5.0. I haven't touched the Firmware at all and i heard from Team Venom that you had to update your firmware and so far i haven't found any RUU's that work properly and whenever i try to flash Viper One 2.4.0, i get VERY long boot screens and sometimes it hangs on the HTC Logo, like the post suggested. Is there any way of safely doing this to a Verizon Phone without loosing S-OFF, Root or an Unlocked Bootloader? Considering they said:
Notice: at the time of writing, both T-Mobile US and Verizon’s 4.4.3 Updates were not available yet, but announced.
Click to expand...
Click to collapse
which i think its not true since people are already running 4.4.3 and Viper One Running on the latest Firmware, and they also said
While the Verizon and T-Mobile US guys need to wait (with “method #1″), the TmoUS folks could head over to my thread (linked above) and set their phones to S-OFF and flash an international firmware as a shortcut (it should be ok, not sure on the impact, maybe losing some WiFi calling functionality which can be restored by flashing TmoUS Firmware once it becomes available), going by “method #2″. However, Verizon: do NOT flash an international GSM firmware! You would regret it badly! Same goes for Sprint by the way. No INT firmware for you ever!
Click to expand...
Click to collapse
Yet on the Verizon Post on Xda, they point you directly to it like i'm supposed to do that, and when i try "Method 2" which is also on their Website's Post that Links you to their Special Firmware Thread here , They Say:
I will cover GSM PHONES ONLY - no cdma / sprint firmware except when i wish to do otherwise.
Click to expand...
Click to collapse
which makes no sense considering they basically told me to go there from linking me in their Verizon Thread. I mean i'm totally confused how your supposed to flash the newest Firmware and it doesn't help that NO ONE has a tutorial online for this. I'm sorry if i'm coming off as a noob, but Normally Verizon OTA Updates have a tendency to Break Root and Lock the Bootloader and i don't know if this is any different.
My Device:
Verizon HTC One M8 (M8_WLV)
4.4.2, 1.55.605.2 Stock Sense
Rooted, S-OFF, Bootloader Unlocked
It's really easy to apply the radio and firmware. Just follow the instructions here
http://forum.xda-developers.com/showthread.php?t=2824882
Also you are correct that taking the ota directly will cause you to lose root. Once you have applied the firmware you should be good with the ROM
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
leprkon said:
Hey guys,
My dad has a SM-G930A 6.0.1 unlocked running on T-Mobile. It is starting to show it's age (battery drain, apps not running like they should, etc.) and is still stuck on 6.0.1.. From my understanding, it should be possible to flash to SM-G930T, however I am a bit lost as to where to begin the process to do so. I tired going straight to 8.0 by flashing the SM-G930T 8.0 firmware files but this didn't work (I didn't think it would work, but it was worth a try). With that said, would it be better for me to just stick to updating to SM-G930A 7.0 via the guides posted, or is there a way for me to Flash the SM-930T 8.0 firmware? Thanks in advance.
Click to expand...
Click to collapse
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
cooltt said:
Wow you guys really get screwed over there in the US with cell phones. It's a pain in the a** to do anything with your phones.
Anyway I'm guessing the phone was originally AT&T right? And now it's unlocked to any carrier.
If you just want to update the phone to the latest firmware then just flash AT&T Oreo. It won't affect the SIM it will still work as before.
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Make sure you back up all the things you want to keep before flashing
Click to expand...
Click to collapse
Thanks for the reply! I appreciate the direction. You are right, US phones are a pain. And yes, the phone was originally an AT&T phone, but was unlocked.
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
cooltt said:
If you want to flash any other firmware including T Mobile then you'll need to unlock the bootloader on the device and that's a whole different ball game. With plenty of guides on how to online.
Click to expand...
Click to collapse
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
leprkon said:
As for unlocking the bootloader, I've found different sources that say that unlocking the bootloader on this particular phone is not possible with this particular phone. I did read something about an engineering bootloader being used to get around a locked bootloader for rooting. Could this be used for flashing as well?
Click to expand...
Click to collapse
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Beanvee7 said:
That's not entirely true. Using Odin you can flash any USA firmware onto any other USA device, no bootloader unlocking required.
It's very common for people to flash G930U over their G930V/T/A/P devices to remove bloatware
It's unstable and only lets the device charge up to 80%, your best bet woulld just be a full flash with Odin
This guide is a bit dated but it's the best one out there. Just make sure you google the latest Odin and use all 4 firmware files when flashing https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Click to expand...
Click to collapse
Thanks for the reply! I had tried flashing the 8.0 G930T variant last night with the latest version of Odin and the PrinceComsy version and got a Model Mismatch error. I read that the modified Odin3 v3.13.1_3B_PatcheD would let me flash the firmware and ignore the Model Mismatch error. However, I didn't go through with it because I was not sure if I would brick my phone and instead erred on the side of caution and made my post here. Would I be safe to flash the files from SM-G930T_1_20180625111401_xf3965l42p_fac onto my current device?
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Beanvee7 said:
If your firmware files are from a trusted source like sammobile, updato or samfirmtool then it should be fine
Odin3 v3.13.1_3B_PatcheD seems to have positive feedback here on XDA so should be fine too https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Thanks for the assist! Everything worked like a charm!
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Great glad it all worked out
leprkon said:
Thanks for the assist! Everything worked like a charm!
Click to expand...
Click to collapse
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Thanks
[email protected] said:
Greetings-
I apologize for jumping in an already created thread, but I think I am in the same situation, and like to verify with you both before I use the advice please. I have a SM-G930T that I just purchased, and really like to run a custom rom. But I understand I can not because I have Android 8 on it. I know how to use Odin, and have the latest version plus you guys talked about it here. I have also already downloaded the stock rom from sammobile site. What are my options? Is there a rom I can flash the phone with using Odin that would provide better performance, less G..bage, and more battery life? Is there a way for me to root the phone? I really need an app that requires the phone to be rooted.
Ok, so flash any unbranded Stock Rom for your device using this version of Odin which has been specifically modified to flash US devices. https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572 PatcheD.zip is the file you want to download.
Then when you have checked the phone is working ok on undrnaded firmware you can go ahead and root the device using this method which is again for US Qualcomm devices. https://www.****************/2018/0...on-galaxy-s7-and-s7-edge-on-android-8-0-oreo/
Take you time and read instructions.
Click to expand...
Click to collapse
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
[email protected] said:
Can I get unbranded stock firmware from sammobile? I understand the generic meaning of it, but I need more information on how to get them and what I need to know to work with them.
Click to expand...
Click to collapse
If I understand it correctly there is no unbranded firmware for the US, its all network specific but you can flash unbranded UK firmware and it will work fine, UK BTU is the one you want from sammobile.
Load into the modified version of Odin and flash.
This is what I found, and downloading.
[email protected] said:
This is what I found, and downloading.
Click to expand...
Click to collapse
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
cooltt said:
Yes that's the right one but like the beanvee and i have said there is a specific way to flash this stock then root the device.
You also need Samsung USB drivers installed so your pc can talk to your device, there's plenty of guides around how to flash with Odin and what you need to do beforehand, the only difference with you is the version of Odin your using and then the method of rooting afterwards.
Click to expand...
Click to collapse
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
[email protected] said:
Thanks. I have used Odin before, and I already downloaded the patchD version of Odin from the link. Thank you so much. I'll keep you posted on how it turns out. I still do not have a verified version of a custom recovery for this. Do you guys know of any? I found this link but the link to the suggested twrp does not work. I think it is this one. But I can not be sure. The original link points to a slightly different url.
Click to expand...
Click to collapse
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
cooltt said:
Nope do not use that TWRP, it will flash TWRP but not boot it and you'll be stuck on Samsung logo forever.
There is still no way to unlock a Qualcomm snapdragon bootloader and i'm not sure anyone is working on it anymore.
All it means is you need to flash custom Roms via Odin or possibly the inbuilt S7 recovery, you just need to check the ROM is in a format which can be flashed that way.
With regards to finding a TWRP solution you'll have to do some serious searching on google and read everything.
There are already several de-bloated stock Roms on the forum if thats what you want to do. Root and custom recovery TWRP are two different things though, you get rooted so your good to go?
Click to expand...
Click to collapse
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
[email protected] said:
Yes root is my main goal, and you are right the debloated roms will work just fine. I can do w/o twrp. Just double checking here; since I am flashing the UK rom, and I believe one of the comments on this thread was how US images are locked tighter, would not I be able to find a UK version of TWRP for my phone? Just checking.
Click to expand...
Click to collapse
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
cooltt said:
Now pull up a chair and listen closely.....99% of the American devices (including yours) have an extremely uncooperative Qualcommm Snapdragon cpu at it's heart and thus refuses point blank to play ball. The online community have done a fantastic job creating the modifications you are now using. The rest of the world (i'm happy to say) enjoy the S7 with an extreamly cooperative Exynos cpu at it's heart. It just loves to be fiddled with, it's a whore of a chip, constantly on the go with all kinds of neat tricks.
Anyhoo... my point is, the software has to be compatible with the hardware you catch my drift? All the cool little programs are written with a specific piece of hardware in mind, unfortunately for you guys Qualcomm is the ice queen.
Click to expand...
Click to collapse
Thank you so much. You guys are amazingly patient, and informative. Thank you for educating me, and helping me achieve my goal.
I have tried a few times but can not flash the files. I have attached screenshots, and followed the instructions here. Do you see anything I should be doing differently?
I initially thought the code came as one tar file, which I could flash, but it was a zip file, which I had to unpack.
I need advice an method's an or people opinion on even rooting this phone. If it's worth it please help me enjoy my new phone even more
Im trying to build a custom firmware and running out of hard drive space doing it lol. Im trying to test differnt versions of firmwares on this sucker. the end goal is to get the radios flashed over to a firmware that is compatible with Qlink. anyone wanna help? <3
sketchscarz said:
Im trying to build a custom firmware and running out of hard drive space doing it lol. Im trying to test differnt versions of firmwares on this sucker. the end goal is to get the radios flashed over to a firmware that is compatible with Qlink. anyone wanna help? <3
Click to expand...
Click to collapse
i would be willing to help, i have alot of disk space + pc resources.
I found an (a01q) (SM-A015M) guide here: https://forum.xda-developers.com/t/how-to-root-samsung-a01-a015f-ds.4147191/page-2#post-85246899. As it reflects in the SM-S111DL adb shell, as a01q. Can someone verify if this is a variant? Should we be flashing parts of the (a01q) (SM-A015M) firmware to the SM-S111DL?
Also have we tried flashing different CSC's to verify if the OEM Unlock option appears in devops? also check to see on each csc is you can just natively run fastboot oem unlock in the bootloader.
I had trouble doing a carrier switch, so we just went back to Straight Talk, and gave the device back. Waiting for a knockoff unlocked s22 ultra from alibaba so my frend can move to qlink. So he has it for now. I dont want to risk bricking it and him not have a phone.
However, I thoroughly went through that device and the ramparts, investigating information about the device. so im hare to help and once we get the replacement device for him then ill try again on that device.
1. try different firmwares to verify if the OEM unlock function appears. It'll most likely be early versions of the firmware.
2. Verify the device variants and see if parts of their builds are congruent with 111DL
3. test each flash and attempt to enable fastboot
This is a lower end device but with a debloat and bl unlock i think it would be worth at least a little time.
I have crap tons of tools that will save you time.
Can we set up a sharepoint?