Develop Bugs

[Q] Unable to flash Stock ROM

I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks

Is it supposed to use T999 firmware?

Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium

re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL

Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?

Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.

newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.

Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.

tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414

newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!

How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7

Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app

Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done

Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app

You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium

Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app

No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium

ZV8 to ZVA Modified OTA (Flash in TWRP)

Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
(Added 10:50 CST)
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

Awesome! Testing this now, I'll post my own results too.
Sent from my LG-LS980 using xda app-developers app

One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.

garwynn said:
Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
Click to expand...
Click to collapse
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!

Any chance this will for stock based ROMs?
Sent from my LG-LS980 using xda app-developers app

@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
If you have debloated the ROM, it probably won't work. I ended up flashing the TOT (pure stock) to get it to flash.
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

youdug said:
@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.
Click to expand...
Click to collapse
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.

garwynn said:
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.
Click to expand...
Click to collapse
im not sure if ill need it but might as well grab it just in case before i start.
thanks man.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
Sorry, didn't clarify the second. I tried stock odex ROM and didn't work. That's why I went the TOT route.

Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
i flashed testupdate 2 no problems here

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
What rom were you on?
latoso said:
i flashed testupdate 2 no problems here
Click to expand...
Click to collapse
and what rom were you on?

mrrogers1 said:
What rom were you on?
and what rom were you on?
Click to expand...
Click to collapse
i was on stock rom

latoso said:
i was on stock rom
Click to expand...
Click to collapse
Stock rooted with just TWRP or Stock rooted Odex or Deodex that @youdug provided here >>> http://forum.xda-developers.com/showthread.php?t=2560115?

latoso said:
i was on stock rom
Click to expand...
Click to collapse
All stock with twrp right?
Sent from my LG-LS980 using xda premium

mchlbenner said:
All stock with twrp right?
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
yes stock rom with twrp

Flashed from stock rom with TWRP 2.6.3.3 using testupdate.zip with no issues. Did not need to use update 2.

If someone that has NOT ran this yet could, please post or PM me their build.prop from the stock + TWRP rom before doing the update?
Thanks:good::good:

garwynn said:
One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.
Click to expand...
Click to collapse
RIP @dougie187
:victory:

I guess my Note 2 is bricked?

Well I give up... I have finally done something that I can not fix. I can normally google and find my own answers and I never have to ask anyone but this time is different.
I have the I317 Note 2, Everything was fine, I was running a stock rom earlier this week and the phone started acting funny. So I though screw it, Ill just go back to stock. So i downloaded.KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user_low_ship.tar and used Odin to flash the stock firmware. I DID do a full wipe before I went back to stock. It worked fine for 2 days. It kept wanting to download an update. So it did. When it restarted from the update that the phone downloaded it got stuck on the Samsung screen.
I thought no big deal, I will just reflash the stock firmware and start again... FAIL same thing happened. It wont get past the Samsung screen even after leaving it on that screen for a hour. So then I tried to get into recovery... it wont let me.Then I reinstalled the stock rom and waited for boot, then I flashed CWM and tried to get in to recovery that way. No luck.
I feel like I need to do a wipe and start all over but I cant figure out how to do a full wipe without recovery. There has got to be something easy that I am missing but I cant figure it out. I will keep on searching with hope that someone tells me what I am doing wrong or what to do.
THANKS

If its still able to go into download mode and odin recognizes the device your good just be patient and download the correct firmware.
Sent from my SAMSUNG-SGH-I317 using xda premium

There are some issues with the OTA update from LJ2 to MH3, which it appears you still have sitting on your phone. You can try booting recovery and clearing cache - that should get rid of the OTA file.
The thread below has some information on how to update from LJ2 up through MH3 and then MK6. It's intended for those who already have the MK6 bootloader - if you don't already have that or want that, you'll want to stop at MH3 and consider your options.
http://forum.xda-developers.com/showthread.php?t=2618447

Do you know did I use the correct firmware? I have had to run Odin a couple of times before but its a no go this time... I can not get into recovery. Even if I run Odin now with TWRP and restart it still wont let me into recovery... Can I use Odin to to a full wipe?

Were you on 4.3 previously? Via OTA?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

yes I did upgrade to 4.3 when it came available then I went to a custom rom. Then full wiped and downloaded what I thought was a stock rom and here I am.
Are you saying I need to download the 4.3 stock firmware and that is my issue. What i downloaded was from September 2013

For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Trust in Odin it never fails.
Sent from my SAMSUNG-SGH-I317 using xda premium

Zen Arcade said:
For a (hopefully) quick solution, see post #2 here, specifically the param/tz file:
http://forum.xda-developers.com/showthread.php?t=2618447
That should get your access to recovery back and allow the mh3 ota to complete.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
WOW that worked!! I just got my phone into Recovery for the first time in over 24hrs now! I did a full wipe and now I am going to try and reinstall the factory rom that I have. Unless you tell me something different...
Thank you very much, I dont understand it but so happy to have a different screen!

Which factory rom? Where are you ultimately looking to get to?

100% back up and running! Thank you again

Zen Arcade said:
Which factory rom? Where are you ultimately looking to get to?
Click to expand...
Click to collapse
One that would work.... LOL I really dont have a preference other then I did not care for 4.3 I ended up with 4.1.1 and I couldn't be more happy. If they ever get 4.4 I would try that.
Its funny 4yrs ago I had the Sprint Evo. I changed roms more often then I changed shirts it seamed. I never had the issues or anything like what I ran into yesterday. I was so careless just trying every rom that was released. Because of that I will always remember the EVO as my favorite phone.

Those were simpler times...
I assume you want root and know how to get it.
Since you have the mk6 bootloader you will need to avoid odin flashing any packages that contain bootloaders in the future. See my mk6 thread for details.
If you want to get to 4.1.2 there are rooted cwm packages for ma4, mc3, and mh3 available. Wherever you end up, I recommend freezing the AT&T Software Update apk from within Titanium Backup or equivalent to ensure that you don't get a forced ota update at some point in the future.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] DN3 rom for sprint note 2?

i was wondering if the DN3 rom is ported for sprint note 2?
http://forum.xda-developers.com/showthread.php?t=2504016
the link up there is the original if not can i use this method
http://forum.xda-developers.com/showthread.php?t=2086394
for it?

Ditto Note 3 featuresAir Command
Smart Scroll
Smart Pause
Signature Lock
Writting Buddy (Direct Pen Input)
One Hand Operation in All Screens
S5 Toolbox feature
S5 Power Saving Mode
S5 Ultra Power Saving Mode
S5 Lockscreen Effects
S5 System UI
S5 Launcher with Magazine & Pullup app
S5 WallpaperNote 3
IconsNote 3
MyFilesNote 3
SNoteNote 3
ScrapBookNote 3
SketchBookDual Settings (Note3 & S5) with search feature
Popup menu in many note 3 apps.
Quick Glance
Air GesturePen
Window Manager from @xperiacle
Other note 3 apps like contacts,msg etc.
Note 3 Multiwindow style
Possible to use the same app in both multiwindows
DN3 Exclusive feature called AnyApp allows you to choose custom app instead of S Finder in Air Command.and many more things that we might forget... see it yourself today.
MultiCSC thanks to @sotmax and @joeldroid
Sent from my SPH-L900 using Xparent Skyblue Tapatalk 2

sooooooooo??? is it ported?

THORMUNZ said:
sooooooooo??? is it ported?
Click to expand...
Click to collapse
From all the all roms I have seen, its not available yet...
And as for the patch I was thinking of trying it but im afraid of bricking my phone. You can flash that rom as long as the rom doesnt install two files( which are carrier related). I just cant remember what files. Just read in that thread and look for those files. when u download the rom use root explorer and check that the rom doesnt have them in there.
Let me know how it goes ?

coolwater22 said:
From all the all roms I have seen, its not available yet...
And as for the patch I was thinking of trying it but im afraid of bricking my phone. You can flash that rom as long as the rom doesnt install two files( which are carrier related). I just cant remember what files. Just read in that thread and look for those files. when u download the rom use root explorer and check that the rom doesnt have them in there.
Let me know how it goes ?
Click to expand...
Click to collapse
omg i want this rom so bad 2. some one help us!!!!

drbubbles123 said:
omg i want this rom so bad 2. some one help us!!!!
Click to expand...
Click to collapse
coolwater22 said:
From all the all roms I have seen, its not available yet...
And as for the patch I was thinking of trying it but im afraid of bricking my phone. You can flash that rom as long as the rom doesnt install two files( which are carrier related). I just cant remember what files. Just read in that thread and look for those files. when u download the rom use root explorer and check that the rom doesnt have them in there.
Let me know how it goes ?
Click to expand...
Click to collapse
I tried but never got past boot screen. Op states it needs the knox bootloader and firmware/radio. I will keep trying but it has not been an easy port.
Sent from my SPH-L900 using XDA Premium 4 mobile app

drbubbles123 said:
omg i want this rom so bad 2. some one help us!!!!
Click to expand...
Click to collapse
You're not alone. That makes two of us. Errrr
jlmancuso said:
I tried but never got past boot screen. Op states it needs the knox bootloader and firmware/radio. I will keep trying but it has not been an easy port.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you could get this working. Omg I would love you forever and ever. And ever. ?

+10!!

jlmancuso said:
I tried but never got past boot screen. Op states it needs the knox bootloader and firmware/radio. I will keep trying but it has not been an easy port.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So to confirm, you tried the patch at http://forum.xda-developers.com/showthread.php?t=2086394 and you got stuck on the flashing Samsung logo? Me being the noob that I am, I (stupidly) decided to simply go ahead and flash the N7100 version on my L900 following the instructions for the N7100 (original) varient. It of course bricked me, never got anything beyond the flashing Samsung logo, just does that forever until I pulled the battery.
However, by attempting to flash it I seem to have created other problems and here's where I'm stumped. I am now unable to restore my TWRP Nandroid I made of my stock rooted MK4 before flashing, restoring that results in getting stuck at the flashing Samsung logo (again). It doesn't matter what options I restore in TWRP (System, Boot, Data, etc) it has the same result: the flashing Samsung logo forever and ever and ever. I read somewhere that 4.4 (the DN3 ROM) messes with partitions because it enables multi user support...could that have anything to do with it? The only way I have been able to get my device back working is flashing stock unrooted MD4 TAR through Odin. I'd really rather not start from scratch though on my settings and everything though, and the only backup I have is that Nandroid, no Titaniums or anything else. Can you help me restore the Nandroid or is it a lost cause?

sweyers said:
So to confirm, you tried the patch at http://forum.xda-developers.com/showthread.php?t=2086394 and you got stuck on the flashing Samsung logo? Me being the noob that I am, I (stupidly) decided to simply go ahead and flash the N7100 version on my L900 following the instructions for the N7100 (original) varient. It of course bricked me, never got anything beyond the flashing Samsung logo, just does that forever until I pulled the battery.
However, by attempting to flash it I seem to have created other problems and here's where I'm stumped. I am now unable to restore my TWRP Nandroid I made of my stock rooted MK4 before flashing, restoring that results in getting stuck at the flashing Samsung logo (again). It doesn't matter what options I restore in TWRP (System, Boot, Data, etc) it has the same result: the flashing Samsung logo forever and ever and ever. I read somewhere that 4.4 (the DN3 ROM) messes with partitions because it enables multi user support...could that have anything to do with it? The only way I have been able to get my device back working is flashing stock unrooted MD4 TAR through Odin. I'd really rather not start from scratch though on my settings and everything though, and the only backup I have is that Nandroid, no Titaniums or anything else. Can you help me restore the Nandroid or is it a lost cause?
Click to expand...
Click to collapse
You will have to do odin back to stock. Then odin a recovery and restore your nandroid.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Did you guys see this? haven't tried it, but fyi:
https://www.youtube.com/watch?v=zJ3ViFtAAFk

jlmancuso said:
You will have to do odin back to stock. Then odin a recovery and restore your nandroid.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that...still results in flashing Samsung logo hang up when I restore the Nandroid with TWRP . I really haven't the slightest clue why this is happening, as my phone is currently running stock unrooted MK4 flashed from ODIN just fine.

sweyers said:
Did that...still results in flashing Samsung logo hang up when I restore the Nandroid with TWRP . I really haven't the slightest clue why this is happening, as my phone is currently running stock unrooted MK4 flashed from ODIN just fine.
Click to expand...
Click to collapse
I see your problem. Twrp does not backup or restore 4.3 properly. You need to use Philz 6.07.9
Sent from my SPH-L900 using XDA Premium 4 mobile app

I'm working with eteam to port dn3 4.4.2 kitkat to AT&T tmobile and 7105, we are almost there. It's running solid. I may then consider porting it to vzw and sprint
Sent from my iPad using Tapatalk

Be patient. It's coming.
Sent from my GT-N7105 using Tapatalk

mtech5 said:
Be patient. It's coming.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Lol I thought that was directed at me for a sec lol
Sent from my iPad using Tapatalk

eZdubzitmk4 said:
I'm working with eteam to port dn3 4.4.2 kitkat to AT&T tmobile and 7105, we are almost there. It's running solid. I may then consider porting it to vzw and sprint
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Please please port it to sprint note 2. Ive been eager to try this rom. But like they say patience is a virtue. so I cant do anything but wait...keep it up guys

jlmancuso said:
I see your problem. Twrp does not backup or restore 4.3 properly. You need to use Philz 6.07.9
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I haven't installed Philz recovery yet, but considering my Nandroid was made with TWRP will Philz even see it? The only reason I ask is because IIRC Philz is based off of TWRP, no? What I'm getting at here is that I'm pretty sure Nandroids from different recoveries, for example CWM and TWRP are completely incompatible right?
If I can't restore the backup I made from TWRP in Philz am I dead in the water? If so, I guess I learned my lesson, that is to have a contingency plan such as Titaniums in place (particularly for settings). I guess I really didn't expect a Nandroid to just fail spectacularly...if TWRP really is completely borked up with backup/restore on 4.3 it would be nice if they had a warning somewhere in the recovery or on their site. I would think that would be kind of important to know before you try to use a backup made using their recovery...

sweyers said:
Well I haven't installed Philz recovery yet, but considering my Nandroid was made with TWRP will Philz even see it? The only reason I ask is because IIRC Philz is based off of TWRP, no? What I'm getting at here is that I'm pretty sure Nandroids from different recoveries, for example CWM and TWRP are completely incompatible right?
If I can't restore the backup I made from TWRP in Philz am I dead in the water? If so, I guess I learned my lesson, that is to have a contingency plan such as Titaniums in place (particularly for settings). I guess I really didn't expect a Nandroid to just fail spectacularly...if TWRP really is completely borked up with backup/restore on 4.3 it would be nice if they had a warning somewhere in the recovery or on their site. I would think that would be kind of important to know before you try to use a backup made using their recovery...
Click to expand...
Click to collapse
Okay lets cover the backup types first. Philz will backup/restore in both twrp and cwm format but you have to select the option. Now about your backup it will still be no good since it was created with twrp.

jlmancuso said:
Okay lets cover the backup types first. Philz will backup/restore in both twrp and cwm format but you have to select the option. Now about your backup it will still be no good since it was created with twrp.
Click to expand...
Click to collapse
now that we have 4.4.2 there shouldn't be a reason we cant get this rom ported

Wifi will not turn on

I am currently running the MOAR note 5 hybrid rom. I flashed the custom marshmallow rom on the front page, and now I can not connect to wifi. I have tried flashing several different modems and firmwares. Any tips?

pakman5391 said:
I am currently running the MOAR note 5 hybrid rom. I flashed the custom marshmallow rom on the front page, and now I can not connect to wifi. I have tried flashing several different modems and firmwares. Any tips?
Click to expand...
Click to collapse
If you're saying you flashed the leaked MM tar, your bootloader changed.
You must go back to the OK1 bootloader or stock tar before flashing lollipop ROM or restoring a backup. I'd suggest going with OK1 stock tar if you didn't have a TWRP backup for Moar.
Sent from my SM-N910P using Tapatalk

This fixed it! Thank you so much!

samep said:
If you're saying you flashed the leaked MM tar, your bootloader changed.
You must go back to the OK1 bootloader or stock tar before flashing lollipop ROM or restoring a backup. I'd suggest going with OK1 stock tar if you didn't have a TWRP backup for Moar.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Are there instructions posted somewhere about how to do this? I'm new to the Note 4 and an still figuring things out.

rodohmes said:
Are there instructions posted somewhere about how to do this? I'm new to the Note 4 and an still figuring things out.
Click to expand...
Click to collapse
What are you trying to do and why?
If you've tried reverting from Lollipop to Marshmallow or vice versa without using full stock tar in Odin; i.e., restoring a TWRP backup, the bootloader would need to need to reverted to match the original ROM base, else Wi-Fi doesn't connect and the camera doesn't focus. Freeza has a thread with the dedicated Odin tars in development forum.
Are you asking how to Odin flash?
Sent from my SM-N910P using Tapatalk

samep said:
What are you trying to do and why?
If you've tried reverting from Lollipop to Marshmallow or vice versa without using full stock tar in Odin; i.e., restoring a TWRP backup, the bootloader would need to need to reverted to match the original ROM base, else Wi-Fi doesn't connect and the camera doesn't focus. Freeza has a thread with the dedicated Odin tars in development forum.
Are you asking how to Odin flash?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. My Sprint Note 4 was updated to Marshmallow before I unlocked the bootloader & rooted. I'd like to try out this ROM & cm13, but have read that I'll need to downgrade my modem & bootloader (maybe other things, not sure). I'm not sure how to do that.

rodohmes said:
Thanks for the reply. My Sprint Note 4 was updated to Marshmallow before I unlocked the bootloader & rooted. I'd like to try out this ROM & cm13, but have read that I'll need to downgrade my modem & bootloader (maybe other things, not sure). I'm not sure how to do that.
Click to expand...
Click to collapse
OK, you know how to use Odin then. Download the files from thread, check the md5's and use the AP slot in Odin.
http://www.youtube.com/watch?v=37qh7uZ9R-Y&feature=youtube_gdata_player
In case you forgot, the illustrative version starts around 4 minute mark. Maybe it's just me but before I volume up, I get Odin ready and connect USB.
Sent from my SM-N910P using Tapatalk

samep said:
OK, you know how to use Odin then. Download the files from thread, check the md5's and use the AP slot in Odin.
&feature=youtube_gdata_player
In case you forgot, the illustrative version starts around 4 minute mark. Maybe it's just me but before I volume up, I get Odin ready and connect USB.
Click to expand...
Click to collapse
Do I need to revert everything back to 5.1.1 LP?
Or just certain things? I was able to find the tar, but not sure how to do only certain items.
I'm thinking I'm going to just wait it out till they're able to get everything working on the newest firmware. I'm used to HTC and all this tar, OK1, Odin, etc stuff is really foreign to me at this point, haha.

rodohmes said:
Do I need to revert everything back to 5.1.1 LP?
Or just certain things? I was able to find the tar, but not sure how to do only certain items.
I'm thinking I'm going to just wait it out till they're able to get everything working on the newest firmware. I'm used to HTC and all this tar, OK1, Odin, etc stuff is really foreign to me at this point, haha.
Click to expand...
Click to collapse
The point of the tars freeza shared was to not have to revert everything but you still can. Freeza's method is convenient where TWRP backups for 5.1 and 6.0 exist to restore but moving to CM should be easier to.
It's not so difficult, just different than what you're accustomed to. I suppose you already know that OEM and CM are very different and since data isn't compatible, you should wipe data and internal but have your backups, keep sakes and flash items on extSdCard to avoid loss.
To answer your question, you'd flash the ROM, then flash the Odin tars. One tar per Odin session; let the phone auto reboot. Only other tool you really need besides Odin on PC is the Samsung driver installed. You find that at Samsung support for Note 4; download and install the .exe file.
Sent from my SM-N910P using Tapatalk

samep said:
The point of the tars freeza shared was to not have to revert everything but you still can. Freeza's method is convenient where TWRP backups for 5.1 and 6.0 exist to restore but moving to CM should be easier to.
It's not so difficult, just different than what you're accustomed to. I suppose you already know that OEM and CM are very different and since data isn't compatible, you should wipe data and internal but have your backups, keep sakes and flash items on extSdCard to avoid loss.
To answer your question, you'd flash the ROM, then flash the Odin tars. One tar per Odin session; let the phone auto reboot. Only other tool you really need besides Odin on PC is the Samsung driver installed. You find that at Samsung support for Note 4; download and install the .exe file.
Click to expand...
Click to collapse
I may venture into this then. Would I have the same wifi & camera issues if I tried to run a cm12.1 ROM? I'm guessing so...

rodohmes said:
I may venture into this then. Would I have the same wifi & camera issues if I tried to run a cm12.1 ROM? I'm guessing so...
Click to expand...
Click to collapse
I think so.
Sent from my SM-N910P using Tapatalk

samep said:
I think so.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah, just tried it but no dice. Thanks for your help. :thumbup:

samep said:
What are you trying to do and why?
If you've tried reverting from Lollipop to Marshmallow or vice versa without using full stock tar in Odin; i.e., restoring a TWRP backup, the bootloader would need to need to reverted to match the original ROM base, else Wi-Fi doesn't connect and the camera doesn't focus. Freeza has a thread with the dedicated Odin tars in development forum.
Are you asking how to Odin flash?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
thank u Bro for guide me and save me:good::good: