I see things are still fairly alive for this phone. I have a quick question about updating. I just powered my phone back on tonight after it being off for several years due to upgrades and what not. Long story short, my intent was to only use it as a means to port a Magic Jack number to Google Voice via a pay-as-you-go service.
Currently, I have a Net10 Wireless sim in the phone, and my MJ# has been ported successfully to this provider and the phone works. Of course I brain-farted and checked for software updates, and the phone successfully connected to the AT&T servers and downloaded an update (I haven't installed it though). As far as I can remember, all I did to this phone back in the day was to root it, I don't think I installed any CFW. Here's a photo of the about screen, anyone have any insight? From what I've gathered it's factory ATT firmware.
I guess my question is, do I allow the firmware update to continue? Will it even succeed if my phone is rooted? Is it even worth it to update? I may keep the phone on Net10, at least for a bit, but I may still just finish porting the number to GV and be done with it...fewer phones to carry around and all.
Thanks guys!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Raven2k360 said:
I see things are still fairly alive for this phone. I have a quick question about updating. I just powered my phone back on tonight after it being off for several years due to upgrades and what not. Long story short, my intent was to only use it as a means to port a Magic Jack number to Google Voice via a pay-as-you-go service.
Currently, I have a Net10 Wireless sim in the phone, and my MJ# has been ported successfully to this provider and the phone works. Of course I brain-farted and checked for software updates, and the phone successfully connected to the AT&T servers and downloaded an update (I haven't installed it though). As far as I can remember, all I did to this phone back in the day was to root it, I don't think I installed any CFW. Here's a photo of the about screen, anyone have any insight? From what I've gathered it's factory ATT firmware.
I guess my question is, do I allow the firmware update to continue? Will it even succeed if my phone is rooted? Is it even worth it to update? I may keep the phone on Net10, at least for a bit, but I may still just finish porting the number to GV and be done with it...fewer phones to carry around and all.
Thanks guys!
View attachment 4778717
Click to expand...
Click to collapse
Do NOT update! You are on the MDB bootloader which can take advantage of the loki exploit and allow you to run TWRP custom recovery and ROMs once rooted. If you update the exploit gets patched and you are stuck with root and safe strap recovery which can boot only touch wiz ROMs. Use the towel root app to root, then follow my guide to get a custom recovery here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
I know it says MDL bootloader, but MDB and MDL are pretty much the same. Both can use loki. If you want, you can update to MDL but don't update past that or else you'll lose the magic that is loki doki.
Related
I can find several how-to's about moving from rooted 4.4.2 to 4.4.4 and stay rooted. But none of them work. Either I can get 4.4.4 to run, but can't root it (towel root won't do 4.4.4, I know that), or I can root 4.4.2, but applying an NI2 kernel leaves me staring at the Sammy S5 splash screen. No Sammy animation, no VZW red screen of boredom, nothing. I tried wiping cache and doing an FDR. No change. What am I doing wrong???
Tried CF Auto Root?
It'll trip KNOX, but if you're not bothered, it should work
The certainly is an option. Noway this S5 will ever see the inside of a VZW store.
I am, however, baffled as to why following the how-to's utterly fails. I have an extensive collection of flashable files, thanks to how-to's that say "use these files from Sammobile", and the ones that have them coming androidfilehost, and on and on. Worse, I have no idea if, for example, all of the NCG files are really the same thing with a different name or not. Meaning I'm really doing the same series of steps with only the names changed. Odin never says FAIL!, finds the device, it validates the md5 checksum, does its magic, and says PASS!. NTL, the phone either bootloops or otherwise doesn't do what it should. At the moment, wiping cache and doing a reset doesn't clear the problem (the S5 stops at the power-up splash and doesn't do so much as the Samsung animation).
Either all of the how-to's are bogus, which seems unlikely, the files listed below are all somehow defective but have good MD5 checksums (also unlikely), or there is something really odd about my phone. The only thing I can think of is I'm doing all of this without an SD installed. I can't see how that would be a problem. I can't imagine the SIM is a bad actor (I do get the right phone number after doing an FDR, BTW). So what's up?
Because things are so wonky, I'm a little uncomfortable with trying CF Auto Root, only to find I managed to brick the phone because of whatever weirdness seems to lurk somewhere in this project.
For laughs and grins, here's the collection to date:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ahh, your S5 is on Verizon ?
Bootloaders are locked on those phones, so you won't be able to root or custom recovery using ODIN
Towelroot for 4.4.2 ROMs prior to June 2014 will work
This is, indeed, an SM-G900V from VZW. The how-to's (links follow) are for the same device. Odin works, to the point where 4.4.4 and 5.0 are functional. Even the WiFI problem, discussed earlier, takes "only" an FDR to put it right. Towelroot works for 4.4.2. What doesn't work is carrying rooting forward to 4.4.4 or, ideally, 5.0 (sure would be nice to extend to 5.1).
http://forum.xda-developers.com/showpost.php?p=55495211&postcount=1
http://www.droidviews.com/update-verizon-galaxy-s5-android-5-0-lollipop-retain-root/
http://androidbiits.com/root-verizon-samsung-galaxy-s5-sm-g900v-android-4-4-4-kitkat/
http://forum.xda-developers.com/ver.../safely-upgrade-root-4-4-4-nha-volte-t2879348 [ADDED]
Again, either all of these items are bogus, I'm doing something wrong, or the phone is not 100% healthy.
Success! I've at least left 4.4.2 behind for rooted 4.4.4. This is the how-to I followed:
http://forum.xda-developers.com/showpost.php?p=55495211&postcount=1
As best I can tell, the moment of actually rooting has the phone thinking it's running 4.4.2, thanks to the kernel, but it's somewhat in the 4.4.4 world, too. At least that's my ill-informed guess about how/why this hack works.
Of course, now it's on to trying to retain root under 5.0. At least, should 5.0 tank, I now know how to get back to a rooted 4.4.4.
I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?
I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.
I also don't want to pay an arm and a leg for the firmware.
Any help is appreciated!
I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be great.
ssconceptz said:
I have been able to get a PF2 firmware as well, I place it in the AP area (PDA) and once connected, hit Start and the thing keeps failing, just like it did with PC2. When I do the Pl1 version though it actually goes all the way through, what gives?
View attachment 3969966
Any help would be great.
Click to expand...
Click to collapse
Did you try emergency recovery with smart switch?
ssconceptz said:
I tried looking everywhere but I have a Galaxy S6 Edge+ which took an OTA and got into a boot loop, nothing helps at all. I tried to ODIN Pl1 version I found but it won't get past the application optimization part with the gears before it shuts off and restarts again. I also found the PC2 version, but it won't even flash for me, that version fails, maybe because it's older than Pl1?
I just need to locate the latest file and associated PIT that I can flash on the Verizon device. I think the partitions are possibly jacked up.
I also don't want to pay an arm and a leg for the firmware.
Any help is appreciated!
Click to expand...
Click to collapse
What's the version that you've got by ota? Just flash that version(must be latest in case), try to boot if it doesnt; boot into stock recovery; wipe cache/dalvik, factory reset(I dont remember which options were there). The fact is; bootloaders of latest firmwares are lock up which means you can't downgrade even previous one you've been using. Custom roms would helpful to get rid of that bootloop but don't know if its available for Verizon devices. Good luck.
Hey!
With the new root / unlock that I managed to get on my F800L, I was wondering if anyone thinks it would be possible to get the US996 ("unlocked") ROM working on my phone? (note: it's a spare that i got for free, so I'm happy to try, even if it means I might brick it)
I'll be honest, I have no idea what I'm doing, but I've already started trying, and I thought I'd managed to do it, until the phone started rebooting on me.
To start, I downloaded the US996 deODEXd ROM from here, and installed it, via TWRP. After that, I wiped data, and advance wiped dalvik/data/cache, before installing SuperSU. I then re-wiped dalvik & cache (I was basically re-doing step 4 onwards in the twrp+ section of me2151's Dirtysanta unlock and root guide, from what I could remember...) After that, I rebooted to bootloader, flashed the boot2.img from that guide, and rebooted.
...and it started up fine, and I got to the setup wizard (where it now tells me that it's a US996, instead of F800L).
The problem starts here. If I rush through the wizard, I can complete it and get into the operating system, and I can see what the problem is (if not, it reboots and I have to start the wizard again). There's an "android is upgrading" progress bar in the notification menu. Once that completes, the phone reboots. Apart from that, it seems like everything else works............... as far as I can tell, because the phone reboots after 15 seconds or so, and it gets quicker each time I reboot... although if I go into fastboot, and wipe userdata, I can start from the wizard, again.
I've managed to get a 4G (LTE) Signal, made a short call to check it worked & wifi seems to be working. I managed to turn developer options, and adb debugging on, too, so I can reboot into recovery. (I tried re-flashing supersu, like in the guide, to see if it did anyhting, but no (I don't know if it should, but like i said, I have no idea what I'm doing)).
Anyone have any ideas that I could try? Or is it likely not going to work, and I'm an idiot for trying? (it's cool, I know, I embrace it)
I'm assuming that if there's a way to stop it from trying to upgrade, permanently, then it might stop rebooting? but, obviously... I have no idea what I'm doing, so if there's a way to do that, I don't know how.
Thanks!
Update: Managed to install stock H918 onto my F800L and it works perfectly. Same method as above.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi, Is it working perfectly yet?
I want to try also on my F800L..
Dear ad,
How to root/unlocked the F800L variant?
I want to try also on my F800L.
Thanks!
I'm wondering if this will work on my Sprint 997
Could someone post detailed steps on how to do this? I have the F800L version and would like to flash a US rom on it. Mainly because my vaoicemail doesn't work, some of LG's apps ignore the system language and still show Korean, etc..
any news???? can i install a custom rom based on h918 variant on my f800l????
is it fully functional?, can u make a tutorial step by step please, there was so very few topic about F800l variant, it would be awesome if u could help.
Does this work on a f800k?
Sent from my LG-F800K using Tapatalk
I have do step by step in the instrustion dirty santa to unlock/root my f800l but i stuck at the step type id in terminal on phone, nothing to show, i repeat from step 1 for many times but it too, please help me. Sorry for my bad English
JvvB126 said:
Update: Managed to install stock H918 onto my F800L and it works perfectly. Same method as above.
Screenshot:
Click to expand...
Click to collapse
Please help me how to do it
Is F800K possible?
I have a FRP locked SM-G935T. I thought I was experienced enough to kind of breeze through the whole process without much thought to it and I made a small but critical error.
I saw, on the phone, that Android was 8.0 and the firmware version was something like G935Txxx5xxx so I did some basic Googling anbd found a combo file named something like combo_file_G935Txxx5xxx and I downloaded and flashed.
I soon came to the Factory Binary Mode, just like I was hoping would happen and then I tried to apply FRP Unlock with Z3X Box and SamsungToolPro and the program finished with no error.
I returned to my firmware download page so that I could download the latest firmware compatible with my firmware version. MUCH to my shock and utter horror there was no Android 8.0 firmwware.
Now, I realise there is one option: I can wait and hope they release the Android 8.0 firmware to the public. soon.
Another option that occured to me is that I might be possible to install a custom ROM and maybe even ROOTaccess. I can find peace with this as an alternative to Stock firmware.
I tried to flash the Qualcomm version of the latest TWRP Recovery and the process failed. Now, when I try to start Recovery Mode it errors with a
SBL Error!
rdk_init!
skip print_summary_to_lcd...
SBL ERROR
UPLOAD MODE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I can provide any further information I would be glad to do that. If more info needed please give me instruction as to how to provide the info needed.
Thanks, as always, all my love and appreciation!!!
SM G935T Android 8.0.0 Available
firmware for your device available at the following web address:
https://updato.com/firmware-archive-select-model?exact=1&q=SM-G935T
Android 8.0.0 released June 29, 2018 for USA T-Mobile. Hope it will work for your device. Just make sure you unlock OEM in your Developer's Option as well as USB debugging. Tapping Build Number 7 times activates your Developer's option.
Good day
Hello All!
Need some assistance here. I bought a used non-rooted stock VZW SM-G975U.
I attempted to flash U1 firmware that I downloaded from FirmwareFiles, but forgot to use the Patched Odin. (Oops, I am a bit of an Android Noob). End goal was to be able to use the phone with US Cellular since they require an SM-975U1, which I still don’t know if flashing will fix....
I received a “256 warning” and it failed to flash, or so I thought.
Now, the phone boots fine, but I am unable to get the device to be recognized - in any fashion - with W7 or W10, tried multiple computers, factory reset, multiple cables, new drivers etc. I have spent days on this...
I recently, today, allowed a brand new VZW pushed OTA update, but it still won’t recognize on any of my PC’s.
Did I soft-brick this phone?
How can I fix without a USB connection and not being rooted?
Thanks so much.
You cannot flash any firmware without know the info of your device first. I recommend u install an info app for Samsung devices (Phone INFO ★SAM★) and share with us some pictures to know if u have a Franki.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I couldn't get the screenshots to properly upload, since I am still a new member without 10 posts. However, I have the "Phone INFO ★SAM★" App installed now.
Product Code: SM2G975UZWAVZW
Firmwares CSC Code: XAA
Active CSC Code: VZW
Available CSC Codes: ATT, BST, CCT, CHA, GCF, SPR, TMB, TMK, USC, VMU, VZW, XAA, XAS
CSC Country: USA/US
Bootloader Version: G975USQU2BSGJ
PDA Version: G975USQU2BSGJ
CSC Version: G975UOYN2BSGJ
Baseband Version: G975USQU2BSGJ
Firmware Status: Official
Kernel Version: 4.14.78-16507756 64-bit
Let me know if there is anything else that I need to provide. I am curious if the OTA update would have updated or "rebuilt" the Kernel, I was hopeful that it would, and fix my problem.
Thanks!
(For those who don't know, G975U is the model number of all of the US carrier versions of the Galaxy S10+. The G975U1 is the model number of the same device, but sold by Samsung SIM unlocked and with no carrier bloatware. Firmware is 100% interchangeable among any of those models.)
Well, seems all is ok there. You can try:
1. Install the latest drivers for Samsung (in ur PC).
2. Factory reset ur device.
3. Download, install and apply the last update via WIFI.
4. Active the developer options -> HOW?
5. Tick there "USB Debugging" and conect it to ur PC (to see if it recognize your device).
6. ... if not... I dunno what to do more. Sorry.
*Patched ODIN: HERE
Thank you, Joku.
I have went through all of those steps, no luck. I’ve tried three different Win10 machines, and did a fresh install of Win10, still no luck. As a last resort, I fresh installed Win7 on a computer, still can’t get any recognition at the PC or the phone, only charge.
I also took the phone up to a PC repair shop to rule out me from being the problem, the tech plugged it into his PC and said, “strange, normally android phones prompt you with a notification to choose the type of transfer or charge when connected to a PC”.
I bought the phone used, not sure where to go from here.
The phone itself seems to work great, other than I can’t get it to connect to my PC. I don’t understand what’s happening.
Maybe the USB port is bad?
Did you try putting your phone in download mode and seeing if your computer recognizes the S10+?
Did you perform a factory reset from the phone settings or while the phone was booted into recovery mode?
Hey jhs,
Thanks, I did try both of these things, no luck.
I am going to take the phone to a service center, something else must be going on.