[Q] flashing radios - Sprint LG G2

At the moment I have a bone stock phone. I know how to go back to ZV8, and root and install a custom recovery. I am familiar with flashing a rom and then the gapps. My issue is this.
Every time I try to install a rom where I have to flash a new radio, it will boot up successfully, but I wont have any data what so ever. No phone calls, no texts. Nothing. WiFi works like a mofo, but that's it. I have a couple of questions I am sure someone will be able to answer. If root and install TWRP, do I have to flash the radio and rom and gapps in a certain order? I have tried radio, rom, gapps rebooted...no signal. I tried Rom gapps radio rebooted and still no signal. So I went back to my trusty ol ZV8 tot file. Then I let the phone get the OTAs to get to ZVC and then I rooted, but then FreeGee can't install TWRP, so I am back to stock unrooted ZV8. I would really appreciate any help in this area. Thanks guys.
*EDIT* under about phone it always says Baseband is Unknown

Nevermind guys, I resolved it. The issue was easily resolved. I went back to ZV8 this morning at work, and took the sprint OTAs to bring me to ZVC, then rooted with iorooot, and and then installed the Autorec.apk and it updated my kernal and installed TWRP to ZVC. I was exhausted last night and my brain wasn't working.

Related

[Q] Need ZV7 or ZV8 radio modem for sprint g2

Does anyone have a flash able zip?.
I had a zva rom working great with the zva modem. Not sure how it happened but I installed xposed and a few modules. For whatever reason it rebooted into a loop. I got haco into recovery re flashed the rom, other roms, zva again to no avail. I can get the phone to boot but no radios work, not even wifi. And of course after a couple minutes it turns off and loops again.
Does any one have a flash able zv7 zip? And question: if my backup is on a zv8 radio, does it have to be on zv8 when I restore? Thanks for the help!

[Q] Help!! ROM flashing problems

Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks

[Q] i317 still on 4.1.2... :( SOLVED!

my work requires encryption. i was on slimkatv22 at the time and had to encrypt. as encryption kept failing, i went back to stock. way back to stock.
so i'm running
JZO54K.I317UCAMH3 ROM
TEAMWIN Recovery
I317UCUCNE5 Bootloader
with Root and Busybox installed.
everytime i try to update via device update, it downloads, reboots and runs TWRP, I decrypt using password, reboots and the update fails with "Update Interrupted" message.
Is there a way to update ROM and keep encryption?
You can't OTA stock ROMs without stock recovery.
xBkKx said:
You can't OTA stock ROMs without stock recovery.
Click to expand...
Click to collapse
Thanks for your response. I tried updating ROM via ODIN and was not successful. Always got stuck in boot logo after i flashed new ROM.
Is there a stock recovery I should flash over TWRP to try?
Thanks for your help.
I have never used encryption so I can't really help if there are specifics around that. What exactly are you trying to install through Odin? If it's the firmware such as THIS it should overwrite the custom recovery with the stock one. If the stock ROM isn't booting you might have to boot into recovery and factory reset/wipe dalvik cache. This is my first Samsung phone so if nothing helps someone else who'd like to offer their assistance would probably be more knowledgeable.
I was going back to stock, which I guess, was mostly successful. however, I've not been able to install new ROM, namely 4.4.2 I317UCUCNE5. so if I install from your link, that should overwrite custom recovery and allow me to upgrade to 4.4.2 ROM either OTA or via Odin?
Maybe? Using the OTA always tells me there isn't an update (cause I'm on T-Mobile I guess?) and I haven't seen any files to update to Kitkat firmware through Odin
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
miserly said:
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
Click to expand...
Click to collapse
haven't had time to try. tbutbut i noticed that foxfi doesn't work even though i'm rooted. i searched for tether and doesn't seem to be a working solution for a free app.
SOLVED
finally got around to following the directions from dicksteele and voila! i'm on 4.4.2!
thanks all!
m

[Q] Is Stock Flash an Option After OTA Upgrade to UCUFNE4??

OK. Long story of how I got here but I have CWM 6.04.7.
I had been running CM11 with UCUEMJB radio and whatever bootloader was on it initially.
I need Airwatch for work. On CM11 Airwatch with xPosed/Rootcloak would still detect root. So I went stock. My intention was to test the rooted stock rom to see if it would work with Rootcloak and Airwatch. After two OTAs to get to KK, I made a backup in CWM.
Rooted. Installed xPosed, Rootcloack and Airwatch. Airwatch saw that I have root so I went back to CWM to flash my backup.
Backup 'works'. I now have no phone functions nor IMEI. I spent a few hours trying to fix that with NV Tools and EFS Professional to no avail. 'SPC check failed' or something to that effect with NV Tools. EFS Professional requires a rooted phone. Circular issue here. alright. Flash CM11 back on. Everything works.
Great, right? Well, I still need to get back to stock and I have no image that I can flash to my knowledge. My backup has something broken/missing and everyone says that once you go UCUEMJB+ OTA a downgrade will brick.
TLDR - I need someone to tell me that it is ok to flash the factory image again. If that is not ok, I need a clean, unrooted UCUFNE4 full image to flash.
Thanks in advance!

is this what a soft brick is?

Okay so have a I747 AT&T Galaxy S3. Had CM13 running fine on NE4 baseband. Decided to upgrade baseband and flashed NJ1 then NJ2, rebooted and everything was fine.
Well then I decided to check out a different ROM, and tried installing these via recovery and then I get stuck on that AT&T splash screen:
d2att_I747UCUFNJ2.zip (didn't work) so then d2att_I747UCUFNJ2_Deodex_Rooted_KnoxFree_Debloated.zip
I thought I was able to install those since I just upgraded my baseband, but my phone did not like it!
I also noticed that in download mode, in red there was a "warranty bit: 1", not sure if that's relevant?
So I can still get into download and recovery, but any restoring CM13 from backups or return to stock results in a bootloop. How can I get CM13 back?
Can I flash back to stock with Odin and start over to fix this? Is this the file I should use?= I747UCDLK3_I747ATTDLK3_ATT.zip or this one?= I747UCUEMJB.zip
Or will those brick my device since I'm quite certain I'm on NJ2 firmware?
OR should i try reinstalling a certain CM version with certain gapps?
What can I do? I'm really freaking out here, everything I have is on 2fa! Please help!
Was the bootloader updated when the baseband was updated?
turns out im just an idiot and installed the wrong gapps.

Categories

Resources