Develop Bugs

[Q] Unable to flash custom roms!

Hi, let me first begin if there is any problem with my threads. And I want to thank XDA for letting me ask this question, im pretty much a noob from the start..
So, I recently got a replacement S4 (surprisingly from a faulty device on swappa that had warranty) and it was already updated with 4.3 MK2, I have used chainfire's CF-Auto Root and have gotten root and also have installed a custom recovery (CWM.) My problem lies when I want to flash a Custom 4.3 Rom. I have downloaded HyperDrive RSL12 (Mostly because of the note 3 features) and the required files for it. But when I go into recovery and try to flash the rom, the recovery would take a couple of minutes to do something and then say that I can't flash this rom (I saw something under the line of "bad" but I have tried again and again to redownload the rom, so I honestly don't think thats the issue) but this happens to all of the roms I want to install, and I'm not sure if it has something with the KNOX bootloader that came with the phone, but honestly, any help I get is much appreciated! I would gladly give more info to who will help me and I would do almost everything to either install custom rom or 4.2.2 stock!

Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app

Android_Monsters said:
Sounds like your not rooted
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hmm.....i mean that is a possibility, i'll try rerooting again, but say if the problem doesn't lie in rooting, what other problem would be associated this?

I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app

You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???

baseballfanz said:
You can't install stock 4.2.2 since you've updated to the mk2 bootloader (or any room base on 4.2.2). Did you check the md5 of the download file?
☞ Sent from here☜???
Click to expand...
Click to collapse
I'll be honest,I have no knowledge about md5 in general, but normally would the mk2 bootloader prevent me from installing a modified stock 4.3 rom or a 4.3 custom rom in general?

Android_Monsters said:
I'd try a different ROM. That one was first for the international version I believe.
Also, you could try a different recovery. Twrp or Philz. Or just a different version of cwm. Which is what I use.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...

LancerEvoDrifter said:
For that rom, I was told I could use that rom for the t-mobile variant, but i had to download the compatible pack for that model, and I Have tried TWRP through Goo Manager, but still no luck...
Click to expand...
Click to collapse
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.

lordcheeto03 said:
What version of TWRP are you using? It may just be me, but I spent all last night trying to flash Hyperdrive, Wicked, AND WarpDrive 4.3 and kept having all sorts of problems. Baseband being reported as unknown, no service, phone app FCing, Settings->About Phone->Status would crash settings, WiFi wouldn't connect for anything in the world. I literally spent about 5 hours wiping, flashing, and wiping again. I couldn't even restore an old backup of HyperDrive I had. I started thinking, I recently updated TWRP to 2.6.3.1 and everything was working fine before. I reverted back to 2.6.3.0 and I could restore my backup; I could now flash the 4.3 TW ROMs and get the correct Baseband to report, it all worked right.
TL;DR
Try using an older version of TWRP.
Click to expand...
Click to collapse
I think I was using the newest version of TWRP. I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?

LancerEvoDrifter said:
I don't think I have a previous version of TWRP, should I look it up on google for more info about older builds?
Click to expand...
Click to collapse
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.

lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."

LancerEvoDrifter said:
I have flash TWRP ver 2.5.0.2, but I been getting a error message saying this. BTW, this is what the log says when I try to flash the ROM
"Updating partition details...
Running boot script...
Finished running boot script.
E: Unable to open zip file.
Error flashing zip '/external_sd/Hyperdrive RLS12 S4 Final (1).zip'
Updating partition details..."
Click to expand...
Click to collapse
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.

lordcheeto03 said:
Are you able to browse through the zip file on either your computer or a file browser on your phone? If you can't look through the directories within the zip, you have a bad download and will need to re-download it.
Click to expand...
Click to collapse
yea, usually when I have a bad download, Winrar would tell me the archive had a unexpected end, but that is not the case in this situation, the file has worked on my dad's s4, but i guess the problem lies in my own device

Tried to delete but don't know how
---------- Post added at 10:13 PM ---------- Previous post was at 10:10 PM ----------
lordcheeto03 said:
You can go to http://techerrata.com/browse/twrp2/jfltetmo and download previous versions of TWRP. The .img files are flashed by using the dd command in a terminal emulator and the .tar files are flashed in Odin.
Some people aren't as lucky with TWRP as I have been; I've never had a real problem with any of the versions I've used. Some people have only really been able to use 2.5.0.2, so I would say to give that version a shot.
Click to expand...
Click to collapse
Thanks for the info about using 2.5.0.2. I was finally to install a custom 4.2.2 ROM without a status 7 error.
David

AT&T Galaxy SIII Downgrade from CM11?

I'm trying to downgrade my i747 from CM11 back to stock AT&T firmware but I'm unable to. I've done hours of searching and reading posts, coming up with dead ends.. I'm hoping someone can point me in the right direction.
I can't seem to find an official original AT&T image, I did find a "rooted leaked" image.. but when I try to flash it with Oden it fails and the phone says "SW New Check Fail: Fused 2 > binary 0"
I ran the triangle away, tried a few different roms... I can re-image CM but not anything older. Is there a thread that explains where I can find the proper AT&T stock rom and roll back from CM11?

If you have the stock 4.3 bootloader, you cannot use Odin to flash a stock AT&T 4.3 ROM because AT&T never made a flashable 4.3 ROM available. AT&T only made 4.3 available as an OTA update to an existing ROM.

Thanks, so what are my options if any? I installed the CM11 through their http://get.cm site so I'm not sure what exactly they're doing but the end result is I have CM11, ODIN for the updater, and CWM. Can I downgrade to an older version then and just perform carrier updates to 4.3? If not is it safe to flash some other third party ROM? Or am I stuck on CM11?
-Keith

Boot into download mode and let us know what it says on the screen. This will help us determine if you have the 4.3 bootloader on your phone.

Download mode says:
ODIN MODE
Product Name: SGH-I747
Custom Binary Download: Yes (1 Counts)
Current Binary: Custom
System Status: Official
Qualcom Secureboot: Enable
Warranty Bit: 1
Bootloader AP SWREV: 2

audit13 said:
Boot into download mode and let us know what it says on the screen. This will help us determine if you have the 4.3 bootloader on your phone.
Click to expand...
Click to collapse
I'm thinking of trying the approach that I found here:
http://forum.xda-developers.com/showthread.php?t=2658486
Unless any reason's why I shouldn't, it seems people have been successful with that pseudo 'stock' build.

Based on your download info screen, you have the 4.3 bootloader and the link you provided would be a good choice.
If you didn't have the 4.3 bootloader, you could have flashed a stock 4.1.1 ROM via Odin. With a 4.3 bootloader, you cannot use Odin.

I tried that link but the flash failed..
format() expects 3 args, got 5
E:Error in /external_sd/ATT_i747_UCUEMJB_StockRestore_CWM_2282014.zip
(Status 7)
Installation Aborted.
Ugh..

Status 7 errors can be caused by using an outdated recovery.

I have 6.0.4.7 installed and downloaded the ZIP that says it's for that version but I keep getting the same error.

Maybe the ROM download is corrupt?

kelkin said:
I have 6.0.4.7 installed and downloaded the ZIP that says it's for that version but I keep getting the same error.
Click to expand...
Click to collapse
Did you verify the MD5 of the zip you downloaded? I haven't seen any other report of this not working as it is the definitive solution for returning to stock 4.3.It's possible your download wasn't complete or, as Audit suggested, the zip was corrupted in some way.

I downloaded a different recovery as suggested and was able to flash that way. I'm finally back on the pseudo-stock AT&T firmware and aside from one strange popup everything seems to be working great. Thanks for the help everyone,
-Keith

Larry2999 said:
Did you verify the MD5 of the zip you downloaded? I haven't seen any other report of this not working as it is the definitive solution for returning to stock 4.3.It's possible your download wasn't complete or, as Audit suggested, the zip was corrupted in some way.
Click to expand...
Click to collapse
kelkin said:
I downloaded a different recovery as suggested and was able to flash that way. I'm finally back on the pseudo-stock AT&T firmware and aside from one strange popup everything seems to be working great. Thanks for the help everyone,
-Keith
Click to expand...
Click to collapse
Hey guys I am in pretty the same situation but I can't any other recovery to stick. I can flash and get the pass but it always boots back into cwm 6.0.3.6. Any ideas?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Hey guys I am in pretty the same situation but I can't any other recovery to stick. I can flash and get the pass but it always boots back into cwm 6.0.3.6. Any ideas?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you flashing via Odin or from CWM? Philz Touch can be flashed from either (i.e. the zip for flashing from an SD card and tar for Odin).

audit13 said:
Are you flashing via Odin or from CWM? Philz Touch can be flashed from either (i.e. the zip for flashing from an SD card and tar for Odin).
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2824065
This is currently where im at and what I've tried.
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2824065
This is currently where im at and what I've tried.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I assume you can boot into download mode so use the latest tar version of Philz to flash recovery. Philz is based off the latest CWM.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Place the file in the PDA box, don't check anything except F.reset. Flash the file, once you see reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery.

audit13 said:
I assume you can boot into download mode so use the latest tar version of Philz to flash recovery. Philz is based off the latest CWM.
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Place the file in the PDA box, don't check anything except F.reset. Flash the file, once you see reset in the status window, remove USB cable, remove battery, replace battery, boot into recovery.
Click to expand...
Click to collapse
I tried this as well.
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
I tried this as well.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're able to flash and you still don't have the right recovery? What do you see in the recovery screen? Is it the stock recovery?

audit13 said:
You're able to flash and you still don't have the right recovery? What do you see in the recovery screen? Is it the stock recovery?
Click to expand...
Click to collapse
No it's cwm 6.0.3.6, I tried every possible way, I think, of flashing a new recovery but it keeps loading back to this.

BRICKED... help?

Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.

Syst3m Deadlock said:
Hey all, I need some help. I bricked my phone, and I can only get into download mode and recovery. Flashing through odin fails each time, and so does flashing through recovery. Gives me a status 7 error. Ive made sure I'm downloading all the proper files, but Im stumped here. My phone also isnt recognized in Kies. Ive uninstalled and reinstalled the drivers multiple times now. Im too nervous to go to an AT&T store because theyll see I voided my warranty from the recovery (using philz recovery).
Anyone got any clue on what Im doing wrong? Any help would be much appreciated.
Click to expand...
Click to collapse
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.

BWolf56 said:
EDIT: In your sig, it says you have an S2? this is the S3 section.
What happened exactly to soft-brick?
The software you're flashing with Odin might not be good, try another one. Also, since you can get in recovery, you can try clean flashing the ROM you had running previous to the brick.
Click to expand...
Click to collapse
I have an S3 now, just havent updated my sig.
And I was trying to root. I was on the latest stock 4.4.2 and flashed the wrong file by mistake. Forgot what it was. So now I cant flash any files in recovery or odin. It just fails each and every time. I know all these files cant be bad
So root wasnt successful and now I cant even revert back to stock

Kies interferes with odin. Uninstall it from your computer and try odin again.

DocHoliday77 said:
Kies interferes with odin. Uninstall it from your computer and try odin again.
Click to expand...
Click to collapse
Still didnt work. Odin let me install a recovery file, but it just wont let me install files to restore back to stock. Same with recovery, I'm still getting the status 7 error. It doesnt make any sense. Ive downloaded and redownloaded from different places, so I highly doubt that all these files are bad

Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?

audit13 said:
Are you running the latest Philz? Sometimes, the status 7 error occurs with an outdated recovery. Have you tried flashing a custom ROM with TWRP?
Click to expand...
Click to collapse
I'm running 6.0.5 - no I haven't tried TWRP

What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.

DocHoliday77 said:
What rom were you running before? What do you want to be running now?
And what is your current firmware/bootloader version? Not sure about philz recovery, but status 7 errors usually occur when you dont have the required firmware build.
Also, at least for the T999, cm roms updater-scripts are outdated. So if we have the newest available, it still gives the status 7 errors because the new builds haven't been added. Just thought I'd mention this in case you're updated to the new kk firmware and are trying to flash a cm rom.
Click to expand...
Click to collapse
I was running official 4.4 unrooted. I'm trying to install Likewise S5.

Install terminal emulator from the play store and enter this:
getprop ro.bootloader
If it returns I747UCUEMJB you should be ok to flash likewise and something else is preventing it. If its anyway but that, you probably need to update your base firmware/bootloaders first.
If you're still unable to boot anything, the build should be shown on the Download Mode screen. You can probably reflash your previous rom and boot to that for right now though.

I was able to get a custom ROM installed, but now I have no reception. Im guessing the bootloader needs to be updated. So I tried updating it via odin. That failed. I also tried flashing it in recovery and still got a status 7 error. Im at my whits end here

You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.

DocHoliday77 said:
You probably need to flash your modem. Run the Terminal Emulator command I posted before, and if it returns I747UCUEMJB, flash the MJB modem. If it returns anything else, flash the modem that matches, but let us know first just to be on the safe side.
Click to expand...
Click to collapse
Terminal Emulator tells me my bootloader is 1747UCUFNE4

Syst3m Deadlock said:
Terminal Emulator tells me my bootloader is 1747UCUFNE4
Click to expand...
Click to collapse
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.

BWolf56 said:
So yeah, you need the 1747UCUFNE4 baseband. Look in Settings/About Phone to know which one you have before going and flashing it.
Click to expand...
Click to collapse
I cant seem to find the 1747UCUFNE4 baseband,

Syst3m Deadlock said:
I cant seem to find the 1747UCUFNE4 baseband,
Click to expand...
Click to collapse
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4

BWolf56 said:
Did you check which one you have atm?
And here, from Doc http://forum.xda-developers.com/showpost.php?p=53626873&postcount=4
Click to expand...
Click to collapse
Thanks a bunch, it worked!!!

[Q] only 1 ROM

I hit the wrong button the other day while trying to reflash stock to my S3 and wiped the system folder. the brain had farted and forgotten about the lock out. only had a older version of TWRP so was only able to install Cyanogen 10.0.0.0 and now I can't flash anything else. not a newer version. not a different ROM. everything else fails. I think the error message said something about a boot loader.
it works but CM 10.0.0.0 just isn't working for me (I HAVE to have a camera for work).
any recommendations or suggestions would be greatly appreciated.
Da Captain Quack

Captain Quack said:
I hit the wrong button the other day while trying to reflash stock to my S3 and wiped the system folder. the brain had farted and forgotten about the lock out. only had a older version of TWRP so was only able to install Cyanogen 10.0.0.0 and now I can't flash anything else. not a newer version. not a different ROM. everything else fails. I think the error message said something about a boot loader.
it works but CM 10.0.0.0 just isn't working for me (I HAVE to have a camera for work).
any recommendations or suggestions would be greatly appreciated.
Da Captain Quack
Click to expand...
Click to collapse
Odin is your friend....

6th_Hokage said:
Odin is your friend....
Click to expand...
Click to collapse
yes it is. but no mater what I do Odin puts stock (or any other ROM) on and then it's boot loop until I reflash CM 10.0.0.0
I can change recovery using Odin but not the ROM.

Captain Quack said:
yes it is. but no mater what I do Odin puts stock (or any other ROM) on and then it's boot loop until I reflash CM 10.0.0.0
I can change recovery using Odin but not the ROM.
Click to expand...
Click to collapse
Use Philz recovery, do all the wipes including internal SD (not external) and flash whatever ROM you want. TWRP doesn't play as nicely on this phone as Philz.
Sent from my LG-V700

mattzeller said:
Use Philz recovery, do all the wipes including internal SD (not external) and flash whatever ROM you want. TWRP doesn't play as nicely on this phone as Philz.
Sent from my LG-V700
Click to expand...
Click to collapse
what I get back is
Using Legacy property enviornment for update-binary...
please upograde to latest binary
assert failed: getpro(ro.bootloader*) == "L710VPBLJ7" ||
last bit over and over. tried a newer CM. tried a differnt ROM. nothing. did all the wipes. only thing that would install is CM 10.0.0

Captain Quack said:
what I get back is
Using Legacy property enviornment for update-binary...
please upograde to latest binary
assert failed: getpro(ro.bootloader*) == "L710VPBLJ7" ||
last bit over and over. tried a newer CM. tried a differnt ROM. nothing. did all the wipes. only thing that would install is CM 10.0.0
Click to expand...
Click to collapse
what carrier do you currently have? and did you try to Odin all possible .tar rom files?

6th_Hokage said:
what carrier do you currently have? and did you try to Odin all possible .tar rom files?
Click to expand...
Click to collapse
Sprint is my carrier. I tried the ROMs I have. Boot-stock-dnd8-SPHl710. that won't work because of the lockout I'm told. all of the other ROMs I have are zip files. real damn confusing trying to figure out which is what. I've just spent half an hour looking and as near as I can tell all ROMs come out in .zip not .tar. I am confused and befuddled.
I don't really care what ROM to much. but CM trashes my camera and I have to have it for work.
I really do appreciate your help.

Captain Quack said:
Sprint is my carrier. I tried the ROMs I have. Boot-stock-dnd8-SPHl710. that won't work because of the lockout I'm told. all of the other ROMs I have are zip files. real damn confusing trying to figure out which is what. I've just spent half an hour looking and as near as I can tell all ROMs come out in .zip not .tar. I am confused and befuddled.
I don't really care what ROM to much. but CM trashes my camera and I have to have it for work.
I really do appreciate your help.
Click to expand...
Click to collapse
try the NJ2stock.tar in Odin and see what happens hopefully this one works for you

Captain Quack said:
what I get back is
Using Legacy property enviornment for update-binary...
please upograde to latest binary
assert failed: getpro(ro.bootloader*) == "L710VPBLJ7" ||
last bit over and over. tried a newer CM. tried a differnt ROM. nothing. did all the wipes. only thing that would install is CM 10.0.0
Click to expand...
Click to collapse
That is a JB ROM. You would have to edit out the asserts before it will flash. But instead of doing that try using Odin to flash stock NJ2. Once you have stock on there, you should flash the last official release of Philz, then flash a ROM, try WickedS5.
Follow this thread to flash NJ2: http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
Philz Recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
WickedS5 thread: http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-wicked-s5-xperience-t2983340
Sent from my LG-V700

mattzeller said:
That is a JB ROM. You would have to edit out the asserts before it will flash. But instead of doing that try using Odin to flash stock NJ2. Once you have stock on there, you should flash the last official release of Philz, then flash a ROM, try WickedS5.
Follow this thread to flash NJ2: http://forum.xda-developers.com/gal.../stock-l710vpudnj2-pc-odin-flashable-t3007847
Philz Recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/philz_touch_6.48.4-d2lte.tar.md5
WickedS5 thread: http://forum.xda-developers.com/galaxy-s3-sprint/development/rom-wicked-s5-xperience-t2983340
Sent from my LG-V700
Click to expand...
Click to collapse
YES! saying you rock is an understatment!!! thank you thank you thank you!!!

Captain Quack said:
YES! saying you rock is an understatment!!! thank you thank you thank you!!!
Click to expand...
Click to collapse
So I take it you're back up and running?

mattzeller said:
So I take it you're back up and running?
Click to expand...
Click to collapse
a bobble or two but yes. back up and running. now the camera works too lol. one quick question. is it safe to flash other ROMs from this point on? I flashed Philz recovery instead of TWRP

Captain Quack said:
a bobble or two but yes. back up and running. now the camera works too lol. one quick question. is it safe to flash other ROMs from this point on? I flashed Philz recovery instead of TWRP
Click to expand...
Click to collapse
I find Philz works better than TWRP on our devices anyway. Feel free to flash ROMs from Philz. Just don't try to Odin anything lower than your current baseband, or you will brick your device.

mattzeller said:
I find Philz works better than TWRP on our devices anyway. Feel free to flash ROMs from Philz. Just don't try to Odin anything lower than your current baseband, or you will brick your device.
Click to expand...
Click to collapse
thanks. it's a bummer I can't give you about 10 thanks clicks
off to look at other ROMS. CM doesn't seem to like the camera from what I see so it will be something else

Captain Quack said:
thanks. it's a bummer I can't give you about 10 thanks clicks
off to look at other ROMS. CM doesn't seem to like the camera from what I see so it will be something else
Click to expand...
Click to collapse
I'm glad I could be of some help to get you back up and going.

Captain Quack said:
YES! saying you rock is an understatment!!! thank you thank you thank you!!!
Click to expand...
Click to collapse
what was it that worked so people know if they have a similar issue for what ever reason?

6th_Hokage said:
what was it that worked so people know if they have a similar issue for what ever reason?
Click to expand...
Click to collapse
using Odin instead of recovery and ROM (listed below) did the trick to get back to stock. http://www.mediafire.com/download/jjg72biz2dzm6qb/L710VPUDNJ2_L710SPRDNJ2_SPR.zip

Signal and data and failing

I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk

HUCCG said:
I loaded CM-13.0 nightly and have Been updating as the updates come but when I go to make a call it takes forever to go through and start ringing and sometimes it r just hangs up. The data keeps going from LTE to nothing and no SIM . I can't get mms either. Can someone tell me what to do.thanks.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?

wmzed said:
Same thing is happening to me. I've tried using OctOs M and now I am on PacRom 6.0.1 and I am having the same "No sim card" error. I can text and call, but no Data whatsoever.
Have you tried changing your APN settings for your network on your phone?
Click to expand...
Click to collapse
are you on the latest baseband for your phone?

ratchetrizzo said:
are you on the latest baseband for your phone?
Click to expand...
Click to collapse
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?

wmzed said:
My stock OS Is 4.1.2 and is running Baseband UVAMB7. Do I need to go for the higher updates for the LTE to work?
Click to expand...
Click to collapse
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.

ratchetrizzo said:
I think you need to be on UVUBOH1.
https://forum.xda-developers.com/showthread.php?t=1949687 has the list of FW and it looks like you are using a super super old baseband.
Click to expand...
Click to collapse
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"

wmzed said:
Do I need to use ODIN for this? I tried installing UVUBOH1 with TWRP, but I get an error when I installing it:
"could not find 'META-INF/com/google/android/update-binary' in the zip file"
Click to expand...
Click to collapse
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here

ratchetrizzo said:
Yes, download https://www.androidfilehost.com/?fid=24052804347821137
NOTE, if you click on "UVUBOH1" and not the androidfilehost link in the FW thread, it links you to the wrong FW and you'll flash UVUBNC1! Make sure you click the androidfilehost link underneath UVUB0H1.
Then flash it with odin.
Afterwards let it reboot and upgrade, then odin TWRP back and either restore a nandroid or flash the rom of your choosing
Oh also, if you're still on 4.1 and on a touchwiz rom, you may want to factory unlock it before you upgrade.. Just because you can. Follow the unlock thread on here
Click to expand...
Click to collapse
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.

wmzed said:
Thank you so much! I will try this out soon and respond with the results! And I had already unlocked my device :. I had to root and use the RegionLock app to unlock it, as the *#197328640# menu option did not work for me.
Click to expand...
Click to collapse
how did you make out?

ratchetrizzo said:
how did you make out?
Click to expand...
Click to collapse
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.

wmzed said:
Was quite a bit of trouble at first . I managed to download and flash the software. flashed TWRP via odin.
Then through TWRP, I rooted by using the Knox remover zip (as i was on official 4.3, my service signal did shoot up to normal again!). Installed SuperSU.
Now when I try to flash any ROM via TWRP it gives errors such as "Status 7", or error reading MD5 when I try to backup software.
Click to expand...
Click to collapse
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower

ratchetrizzo said:
Make sure twrp is up to date for d2tmo, and make sure the rom you are flashing is 4.3 or later. I'm pretty sure that once you're on the latest 4.3 rom you can't flash anything lower
Click to expand...
Click to collapse
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.

wmzed said:
Got the latest TWRP running, but still the same issue trying to flash OctOS M, PACROM 5.0.1, etc.
Click to expand...
Click to collapse
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem

ratchetrizzo said:
That's strange, I'm using 3.0.2.0 and the latest 999L baseband and I haven't had any issues with flashing.
I'm Using the MM pac rom but I've tried CM14.1 nightly builds with no problem
Click to expand...
Click to collapse
I have finally managed to figure it out. You need to completely format the entire ROM currently installed from your phone. Once that is done, you can add any ROM to install properly. I'm running well on OctOS-N 3/17/2017 build.
Thanks all for your help.