Database Users

ATT SM900MJ5 rooting experience

After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.

thanks for this...a lot people saying rooting is easy, but I don't think it is (at least compare to other devices)

Post video of process I'm curious to see this working as well as files needed, I have an AT&T note 3 and want to install T-mobile Rom.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Vi3tDroidz said:
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
Click to expand...
Click to collapse
You can root it using KINGO, but you can not do sim unlock using REGIONAL UNLOCK trick.

Vi3tDroidz said:
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
Click to expand...
Click to collapse
Could you please send me a PM or hit me up on hangouts? [email protected] I have some questions I need to ask you
Sent from my SM-N900A
{
"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"
}

Did this trip the Knox counter?
Sent from my SAMSUNG-SM-N900A using xda app-developers app

+1
Sent from my Nexus 10 using Tapatalk

15341 69996854
why not using kingo root?

Vi3tDroidz said:
After attempting to root my ATT Note3 I have learn a few things. Hopefully my experience will help out some of you, and give new ideas to dev team.
1. ODIN. I realize the updated odin looks diff than the previous software. Firmware on Note3 has so much info that it needed to seperate everything. Plus Sammie might think that this will makes it harder to root the phone. I think they just made it easier
Here are my reason. After I got my phone stuck on bootload. It seem almost impossible to get the stock MJ5 firmware for the ATT. I spent so many hours on trying all kind of method on XDA forum. nothing seems to work out. At this point, I had nothing else to loose but my phone. So I decided give another manufacture firmware a shot. I downloaded TMobile stock firmware. Open ODIN, and loaded all the require MD5 into their perspective place. Hit start, and able to get my phone to loaded again. I had to use T-mobile sim card. Don't know what happen, but apperently, as long that you have all the correct data, ODIN will do the rest. I wanted to test this out further, so I download kitkat for tmobile. (i had to use one click.exe) because the other files doesn't have the MD5. I ran the ODIN that came with the file, but this time I use the Kitkat for ATT instead of TMOBILE. One click.exe install the ATT kitkat on my phone just fine. And now, after 2 days of downloading, and reading rooting article from XDA, droidview, etc. I think we can flash any rom using ODIN as long that you have all 5 MD5 files.Hope this help. I think i'm just lucky.
Click to expand...
Click to collapse
I don't quite understand your claim on rooting - from what you describe you have just returned to stock UNROOTED firmware.
It would have been VERY interesting what bootloader you had while on TMobile ROM - the original locked MJ5 from AT&T or some TMobile (unlocked) bootloader.
And you are now on KitKat AT&T version, so maybe no downgrade will be possible.

s205702 said:
why not using kingo root?
Click to expand...
Click to collapse
I wouldn't use Kingo because we don't really know how they achieve root, and install SU on your phone. From my experience with Kingo when I softbrick the note 3. In my opinion, I think Kingo was the main source for softbrick. At the time, everything on my phone seems to check out ok. (recovery booting, safestrap, and chainfire SU) yet the phone wouldn't boot. So I think with unstable root access will affect your SU, and in my case it couldn't load safestrap, or finish the rest of the boot. My other reason is" I've heard Kingo sent ur call data to China". If I don't let my own apps collect info w/o my knowledge. I'm sure as hell, not gonna let an app send my data without me knowing.

lildoggs said:
Did this trip the Knox counter?
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
My knox still at 0x0. Like I said, for inexperience rooter like myself. I recommended using Odin for all you trouble since it verify your tar.md5 when you load it for flashing. Heimdall is also a good way of doing things, if you're good with ADB, and understand Linux. I use Odin whenever I can, unless the developer for a Roms, theme, install, etc require a different method.
We take risk when we root our phone, but that doesn't mean you can't choose the process that will minimize your risk. "Rooting is like having safe sex" . You take that .01% risk with a condom and look at all those babies in adoption. The same goes with your phone, and I can tell you there quite alot of Brickster out looking for help.

Vi3tDroidz said:
My knox still at 0x0. Like I said, for inexperience rooter like myself. I recommended using Odin for all you trouble since it verify your tar.md5 when you load it for flashing. Heimdall is also a good way of doing things, if you're good with ADB, and understand Linux. I use Odin whenever I can, unless the developer for a Roms, theme, install, etc require a different method.
We take risk when we root our phone, but that doesn't mean you can't choose the process that will minimize your risk. "Rooting is like having safe sex" . You take that .01% risk with a condom and look at all those babies in adoption. The same goes with your phone, and I can tell you there quite alot of Brickster out looking for help.
Click to expand...
Click to collapse
Damn this sounds mighty tempting. Can you post a tutorial or a video in detail on how you managed to put a tmodile rom without tripping the Knox counter? Everyone will thank you for it.
Sent from my SAMSUNG-SM-N900A using Tapatalk

s205702 said:
why not using kingo root?
Click to expand...
Click to collapse
I've had my brand new Note 3 for 5 days now. I rooted with Kingo...with no problems and then used safestrap for recovery. Sure when it comes to rooting there is always a risk but for anyone to say Kingo can't be used. .. that isn't true. I did my own research and used it
Sent from my SM-N900A using xda app-developers app

Yeah this needs some investigation if theres a way to load tmo stock firmware theres a chance u got an unlocked bootloader that would be a huge bounty for u and happy day for att note 3 users
Sent from my SM-N900A using xda app-developers app

[Q] I'm stuck in CWM recovery mode

Hello,
Yesterday an update came up on my screen, I clicked "Install Now"
The phone restarted into CWM.
I am rooted ofcourse, and I'm really scared for my phone,
Is there anything to be done?

Which phone do you have?
Your phone is rooted, do you have a stock or custom ROM?
You should provide a little more information so people can help you.
Sent from my HTC One X+ using xda app-developers app

LG G2 D802 T-mobile version
umm...I had stock firmware,
Just now i installed CyanogenMod, and still im going back to recovery...

btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,

iMetalliX said:
LG G2 D802 T-mobile version
umm...I had stock firmware,
Just now i installed CyanogenMod, and still im going back to recovery...
Click to expand...
Click to collapse
You should try to reverse back to stock.
http://forum.xda-developers.com/showthread.php?t=2432476
I've found that on the forums for LG G2's.
Verstuurd vanaf mijn HTC One X+ met Tapatalk
---------- Post added at 08:00 AM ---------- Previous post was at 07:54 AM ----------
iMetalliX said:
btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,
Click to expand...
Click to collapse
The only thing you probably have to worry about is the data on your device since it is possible you have to wipe it. No worries on bricked device.
Verstuurd vanaf mijn HTC One X+ met Tapatalk

iMetalliX said:
btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,
Click to expand...
Click to collapse
No. But it looks like you flashed a borked file. Maybe the CM you installed has a wrong MD5, or you might have flashed a CM that's for a different G2. Either way, you can either push a new ROM zip into your phone to flash, or KDZ back to stock like the guy above me said. Good luck!
And don't worry, your phone is completely fine. But this should be a lesson to always perform a backup before ANY ROM flashing.

mackster248 said:
No. But it looks like you flashed a borked file. Maybe the CM you installed has a wrong MD5, or you might have flashed a CM that's for a different G2. Either way, you can either push a new ROM zip into your phone to flash, or KDZ back to stock like the guy above me said. Good luck!
And don't worry, your phone is completely fine. But this should be a lesson to always perform a backup before ANY ROM flashing.
Click to expand...
Click to collapse
Thank you mate )
umm..i'm going back to stock, and the MD5 was ok, and yes, im a noob

Lg g2 d80220a
iMetalliX said:
btw, if i have recovery up and working, i shouldn't be madly worried...shoud i?,,
Click to expand...
Click to collapse
What I'd like to know is how did you get CWM in the first place? I've tried for a couple of hours with ROM Manager and the D802 is not supported even though it claims it is. All I get is the red triangle on top of the green android bot and what looks like 2.x CWM. Not sure since I'm new. But it only has about 5 options. No MOUNT, NO ADVANCED, Looks unsuitable for flashing a ROM. I saw this version the very first time I flashed a phone and I soft bricked the phone. It was a Nexus 4. I recovered but I'm not taking any chances and messing with that again. The only way I recovered was using Wugfresh. I need something like Wugfresh for my D802 where I can take those risk. I'm angry because I can't flash anything now. I've got 327 apps to get installed. No one wants to do that manually. It is really inconceivable that this phone which is still arguably the best in the world after 6 months is not supported the way it should be with recovery. Any help in getting CWM working would be greatly appreciated.

notanymore said:
What I'd like to know is how did you get CWM in the first place? I've tried for a couple of hours with ROM Manager and the D802 is not supported even though it claims it is. All I get is the red triangle on top of the green android bot and what looks like 2.x CWM. Not sure since I'm new. But it only has about 5 options. No MOUNT, NO ADVANCED, Looks unsuitable for flashing a ROM. I saw this version the very first time I flashed a phone and I soft bricked the phone. It was a Nexus 4. I recovered but I'm not taking any chances and messing with that again. The only way I recovered was using Wugfresh. I need something like Wugfresh for my D802 where I can take those risk. I'm angry because I can't flash anything now. I've got 327 apps to get installed. No one wants to do that manually. It is really inconceivable that this phone which is still arguably the best in the world after 6 months is not supported the way it should be with recovery. Any help in getting CWM working would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried philz http://forum.xda-developers.com/showthread.php?t=2554053
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Lg g2 d80220a
XxZombiePikachu said:
Have you tried philz http://forum.xda-developers.com/showthread.php?t=2554053
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
That won't work because you can't even get to the menus to install the zip. That the whole problem. You can't really do anything because it basically hangs up with the red triangle. With the number of people having this problem and how great a phone this is you'd figure this problem would not even exist. Here's a screen shot of the problem everybody is having.

notanymore said:
That won't work because you can't even get to the menus to install the zip. That the whole problem. You can't really do anything because it basically hangs up with the red triangle. With the number of people having this problem and how great a phone this is you'd figure this problem would not even exist. Here's a screen shot of the problem everybody is having.
Click to expand...
Click to collapse
okay so that's the stock recovery, by any chance are you on kitkat because it says d80220a?

iMetalliX, can you still flash a .zip file?, if you can I know this would work for you, just translate the thread and OTG flash the small zip file. This happened to me yesterday, and piece of cake.

me having the same problem (stock recovery)
cant flash anything (E:footer is wrong ) (E:signature verification faild)
and now when flashing new Philz recovery ( assert faild : run_program (`/temp/loki.sh`) ==0 E:error in /temp/update.zip status 7
since 2 days trying to get out of it but i cant lol

same thing happened to me but i managed to install twrp now my problem is im stocked at lg logo. I have no back up nor any rom downloaded. i have kdz file saved on my g2 but i cant copy it to the computer since it cant be detected or if it has a way please please let me know. Pls help me out of it, i miss my phone. Thank you.

Lg g2 d80220a
XxZombiePikachu said:
okay so that's the stock recovery, by any chance are you on kitkat because it says d80220a?
Click to expand...
Click to collapse
Yeah I made the foolish mistake of upgrading to kitkat. I knew it as soon as I hit yes button to upgrade. Too late.
---------- Post added at 08:37 AM ---------- Previous post was at 08:24 AM ----------
pmorales said:
iMetalliX, can you still flash a .zip file?, if you can I know this would work for you, just translate the thread and OTG flash the small zip file. This happened to me yesterday, and piece of cake.
Click to expand...
Click to collapse
I'm new so don't know much. My understanding is you can't flash anything without being in recovery, right? Look at busted25's post. I'm not risking anything that is not concrete. Much as I like to tinker around I accomplish nothing if I end up with a brick. On my Nexus I could risk everything and because I had Wugfresh. No such thing. I'm going to look at he LG software suite and see if can backup the phone enough to restore it should i soft brick or something

notanymore said:
Yeah I made the foolish mistake of upgrading to kitkat. I knew it as soon as I hit yes button to upgrade. Too late.
Click to expand...
Click to collapse
Well that's why you can't get recovery, kit Kat does not have ability for recovery and who knows if it ever will
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

notanymore said:
Yeah I made the foolish mistake of upgrading to kitkat. I knew it as soon as I hit yes button to upgrade. Too late.
---------- Post added at 08:37 AM ---------- Previous post was at 08:24 AM ----------
I'm new so don't know much. My understanding is you can't flash anything without being in recovery, right? Look at busted25's post. I'm not risking anything that is not concrete. Much as I like to tinker around I accomplish nothing if I end up with a brick. On my Nexus I could risk everything and because I had Wugfresh. No such thing. I'm going to look at he LG software suite and see if can backup the phone enough to restore it should i soft brick or something
Click to expand...
Click to collapse
Yesterday I just write but I forgot to include the thread to be translated for the instructions and the .zip file to be OTG flashed, here it is, sorry
http://www.htcmania.com/showthread.php?t=746320

Lg g2 d80220a
XxZombiePikachu said:
Well that's why you can't get recovery, kit Kat does not have ability for recovery and who knows if it ever will
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
What?! Are you sure about that? If true that is really foul. What, do they think we are Apple fans or something? If we didn't want recovery we would have bought Apple. I hope that is not true. Why would they do such think knowing you can't flash if you they do that. I'm addicted to custom roms...LOL! I need my fix now!!
---------- Post added at 08:50 PM ---------- Previous post was at 08:44 PM ----------
pmorales said:
Yesterday I just write but I forgot to include the thread to be translated for the instructions and the .zip file to be OTG flashed, here it is, sorry
It is in Spanish. Just trying working with that on your beautiful phone as a noobie...hahahaha! Thanks though.
Click to expand...
Click to collapse

notanymore said:
What?! Are you sure about that? If true that is really foul. What, do they think we are Apple fans or something? If we didn't want recovery we would have bought Apple. I hope that is not true. Why would they do such think knowing you can't flash if you they do that. I'm addicted to custom roms...LOL! I need my fix now!!
Click to expand...
Click to collapse
Well the exploit we were using to install recovery/Loki was patched in kk so currently if you want recovery it's the same procedure for all devices downgrade to 4.2(first firmware available) root install recovery and depending on your device I can link you a modified kk that uses the aboot from 4.2 plus modified kk kernel to boot to kk while retaining root/recovery
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Lg g2 d80220a
XxZombiePikachu said:
Well the exploit we were using to install recovery/Loki was patched in kk so currently if you want recovery it's the same procedure for all devices downgrade to 4.2(first firmware available) root install recovery and depending on your device I can link you a modified kk that uses the aboot from 4.2 plus modified kk kernel to boot to kk while retaining root/recovery
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I don't know if I have the skills to pull that off. I could wind up like busted25 and all the others who bricked. I think my best option might be to sell it very cheap quickly and order a new one and never upgrade. I'll take the hit. Phone is less than a week old. One thing I'm not understanding though is I'm seeing only kitkat custom roms for this phone out there. That's why I thought it was ok to upgrade. I didn't see any 4.2.2. Everybody who flashed the custom roms must have been fairly or very skilled.One thing that made me upset is ROM Manager advertised recovery for this phone that was bogus. I even paid for the touch version and got nothing and no email reply

Another upgrade

Guys, my phone just told me there's another upgrade for the lg g2 D803 variant....Anybody seen this yet?
I'm wondering what the upgrade is, seeing it's 1.5 gb.
It's gonna take me to D803B20G. Not sure if the current rooting and autorec recovery method will work on this new firmware, sceptical about installing it......

rodpgfx said:
Guys, my phone just told me there's another upgrade for the lg g2 D803 variant....Anybody seen this yet?
I'm wondering what the upgrade is, seeing it's 1.5 gb.
It's gonna take me to D803B20G. Not sure if the current rooting and autorec recovery method will work on this new firmware, sceptical about installing it......
Click to expand...
Click to collapse
1. wrong place to post this.
2. general rule of thumb - if you like having root and recovery, NEVER take an OTA from the manufacturer EVER, until it's confirmed that it doens't block root / recovery /bootloader exploits (like the 4.4 ot'as blocked loki)

jakew02 said:
1. wrong place to post this.
jakew02 said:
Sorry, I wasn't sure where to put as there is no folder for 803 variant.....
Click to expand...
Click to collapse
Click to expand...
Click to collapse

jakew02 said:
1. wrong place to post this.
Click to expand...
Click to collapse
Sorry, I never seen a folder for the D803 variant so I wasn't sure where to put this.... Should it have gone in Q&A?

rodpgfx said:
Sorry, I never seen a folder for the D803 variant so I wasn't sure where to put this.... Should it have gone in Q&A?
Click to expand...
Click to collapse
Q&A if you're asking a question about it, General if you wanted to let people know about it..

yes probably in q&a or general maybe, like stated above please dont install on your phone if youre rooted with a non stock recovery otherwise you will mess up your phone big time! really not sure if its possible but if you can, switch off firmware updates as they are not compatible with the custom recoveries and whichever rom you are using will update soon enough anyway if your on stock rom the same applies if you have a custom recovery

martindar said:
yes probably in q&a or general maybe, like stated above please dont install on your phone if youre rooted with a non stock recovery otherwise you will mess up your phone big time! really not sure if its possible but if you can, switch off firmware updates as they are not compatible with the custom recoveries and whichever rom you are using will update soon enough anyway if your on stock rom the same applies if you have a custom recovery
Click to expand...
Click to collapse
I have stock Rom rooted and twrp recovery that's all.

Avoid the update.
However it has the knock knock code addon. Or, as far as I've heard, that's the only new update LG had planned for the LG G2.
Do not install it. If you REALLY want to try it, make a backup, store it on your PC, OTA. If you lose root, you can revert to stock, get a recovery, put your backup back on your phone and restore.....but that's honestly a lot of work just to possibly get the knock knock code. (I know turning on is knock on, but for the "code" you knock more than once minimum, so I call it knock knock).
You can also force supersu to keep root, but last time I tried that for an OTA I got stuck in a bootloop.
TL;DR: Might be knock on/knock knock code. Not sure what else. You can backup and try to OTA, but no one can be certain what will happen. Expect to lose root. You can force SuperSu to keep root, but you may bootloop.
I'd just wait for more info.

rodpgfx said:
I have stock Rom rooted and twrp recovery that's all.
Click to expand...
Click to collapse
twrp recovery is a custom recovery, so never update.

I'm pretty sure there is an app in /system that you can freeze to stop push updates. Sadly, that is the only info I have. It may have been carrier specific and I haven't been on stock since the first week I had the phone. Haha.

Guys I already know all what you just said......I've done this loads of times. Just wondering if I can uninstall custom recovery without re-installing stock firmware?
I know I can take my chance and try the OTA but not without recovery gone first.
It's a lot of work to just flash stock firmware, install update and if there's no big change, flash stock again.....
Thats why i was wondering if the only option is flash stock to get rid of recovery

martindar said:
twrp recovery is a custom rom so never update
Click to expand...
Click to collapse
Twrp is not a Rom it's a recovery. Hence the "recovery"
Sent from my VS980 4G using XDA Premium 4 mobile app

Esteway.619 said:
Twrp is not a Rom it's a recovery. Hence the "recovery"
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, yeah I didn't want to say anything. He should read up before doing anything with his phone.

rodpgfx said:
Guys I already know all what you just said......I've done this loads of times. Just wondering if I can uninstall custom recovery without re-installing stock firmware?
I know I can take my chance and try the OTA but not without recovery gone first.
It's a lot of work to just flash stock firmware, install update and if there's no big change, flash stock again.....
Thats why i was wondering if the only option is flash stock to get rid of recovery
Click to expand...
Click to collapse
I think its possible, (but it should be really hard to do so) but the easiest way is to flash a .kdz file And you should not take the chance to update when you have recovery, it just isn't worth it. Anyways I would just have sticked with a custom rom which gets updated regulary..or flashed a kdz and get back to stock.
Btw can the good judger @Judge Joseph Dredd move the thread to q and a section? I think that it is even more help to get there

OP Moved out of the Development Threads, since this does not belong there....Please read the Forum Rules on posting.

the n00b's guide to kitkat on the fascinate

So, due to recent events (probably really young kids spamming the threads of various dead or no-longer-maintained ROMs) I have decided to make this guide. for everyone.
THIS IS THE ROM YOU SHOULD BE USING: http://www.androidfilehost.com/?fid=23501681358542421
Unofficial CyanogenMod 11, compiled by @Unjustified Dev. dated june 4th, 2014.
Now, flashing this ROM is actually kinda difficult. We don't have an active official CM maintainer anymore and TWRP bricks people's phones. So here is the best method of flashing it. (disclaimer: if you're on the stock Samsung ROM, flash cm10.1 and refer to this guide if necessary. this is a clickable link.)
Now, after flashing cm10.1, follow these steps to flash cm11:
1. make a nandroid backup
2. wipe data/factory reset
3. flash cm11. you will probably get an error (probably along the lines of set_metadata_recursive). this is okay. reboot recovery. (advanced options in the main menu)
4. you might see some different bootlogos. this is a good sign. hopefully you'll see a clockworkmod version 6+. this is also a good sign.
5. repeat steps 2 and 3 and then flash whatever google apps package you want. the official one actually isn't bad. http://goo.im/gapps
After all of that, you should be good. If you do get bricked, fear not, you can always use Odin to flash the stock firmware again and use this guide if necessary: click here for the guide of wonderfulness
I dont actually own this phone anymore, so asking for help will probably get you nowhere. I'm sure Android L or whatever might be easier for us to work with unless the recovery devs have higher requirements for their stuff.

I was asking for a working link the other day for an old ROM.. Oh well, I am not a young kid though..This is what it will say when your successful. I rom'd a few times tonight on my kids phone and had no problems flashing through 4.2.2 to 4.4.2 ..
{
"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"
}

dee3 said:
I was asking for a working link the other day for an old ROM.. Oh well, I am not a young kid though..
Click to expand...
Click to collapse
nah man you're cool i was referring to a certain username inspired by a certain automobile distributor. of expensive, fast cars.
also that cm11 theme you have there is absolutely ridiculous. you know what it's called?

Fuster cluck its on my 6yo sons phone. He really likes all the flashy colors
---------- Post added at 06:23 PM ---------- Previous post was at 06:12 PM ----------
And thanks for the guide and the heads up last week on the cm11 stability. Its been a good ROM so far except I noticed I couldn't install the last update of minecraft PE 0.9.5 on my kids phone as he has had it since 4.2.2 running without issue. I tried to install the the zip on my phone too, got the files from apkgalaxy where I've been getting most paid apps for a while now. Only this ROM will not let minecraft install.. Weird.. when I didn't have this issue on DU 4.4.2, hellybean 4.2.2 , or avatar 4.2.2. And I also notice each time I download a zip from apkgalaxy as soon as I hit the download button, internet explorer and chrome both have issues closing out.. But I haven't noticed anything that would make me not want the ROM as its nice.

Is "flashify" the way to go now ? Or our tried and true method ? Just wondering .
Sent from my SCH-I500 using XDA Free mobile app

I used flashify to flash a kernel that wouldn't flash in recovery. Than I also got another phone that was on cwm 4.0.6.1 a 4.2.2 build I believe to flash through ROM manager when I kept getting can't mount errors when entering cwm recovery. I used the rom manager to push TWRP than got it onto the 4.4.2 unjust 6/04 build its on now after a few cm11 flashes. So there are a few ways to go about it at least for me I've used a couple different ways when I didn't have my laptop handy and would screw up or get errors. Google always fixes my problems as dumb as I am too this all after 4+years of rooting. Still learning..

icemanwbs said:
Is "flashify" the way to go now ? Or our tried and true method ? Just wondering .
Sent from my SCH-I500 using XDA Free mobile app
Click to expand...
Click to collapse
haven't tried flashify, plus i dont have this phone anymore, i upgraded to the s4. locked bootloader ;__;

Well, after many attempts I've only been able to get cm9 up and running. Tried first to Odin back to stock and then 10.1 ( using both droidstyles and the noob guide to kit Kat ) , also tried TWRP , without success. No idea what went wrong.
Sent from my SCH-I500 using XDA Free mobile app

Hmm. Try and get ROM manager pro .apk to flash a cm11

dee3 said:
Hmm. Try and get ROM manager pro .apk to flash a cm11
Click to expand...
Click to collapse
rom manager doesnt work on this phone.

icemanwbs said:
Well, after many attempts I've only been able to get cm9 up and running. Tried first to Odin back to stock and then 10.1 ( using both droidstyles and the noob guide to kit Kat ) , also tried TWRP , without success. No idea what went wrong.
Sent from my SCH-I500 using XDA Free mobile app
Click to expand...
Click to collapse
ok so when you flash cm11 using the cm10.1 clockworkmod image, it will give you an error. after that you have to reboot recovery and flash cm11 again
you have to flash it twice, especially when using clockworkmod. twrp i heard you can just flash once but you have to have a really recent version of twrp (2.6.3.0) and not only is that hard to come by for this phone but it can brick your phone.. i know that the cm11 kernel hhp made bricked my phone before, and i flashed that before cm11.. idk i probably wasnt supposed to

How doesn't ROM manager premium work on this phone? You know I'm dumb to all this so I take your advice serious on these things. I am asking because I used it to push TWRP when I kept getting constant can't mount errors when trying to flash the cm11 build on my sons phone when he was on a cwm 4.0.6.1 4.2.2 build I believe, and I couldn't flash a twrp rom without the can't mount . it got me through to the 6/04 unjust 4.4.2 after some unknown flashing around . I know I didn't follow a guide since I had errors and googled my can't mount errors
Last night/this morning I reflashed his phone down to the slimroms 4.2.2 7/08 build though due to mine craft not installing on cm11 4.4.2. I had no problems going from the 4.4.2 back to a 4.2.2 . I usually don't have problems that cause me to have to re Odin eh03 but when I started rooting I usually would Odin. Now its been all from recovery or the flashify and ROM manager I've used when rooting. No PC needed

dee3 said:
How doesn't ROM manager premium work on this phone? You know I'm dumb to all this so I take your advice serious on these things. I am asking because I used it to push TWRP when I kept getting constant can't mount errors when trying to flash the cm11 build on my sons phone when he was on a cwm 4.0.6.1 4.2.2 build I believe, and I couldn't flash a twrp rom without the can't mount . it got me through to the 6/04 unjust 4.4.2 after some unknown flashing around . I know I didn't follow a guide since I had errors and googled my can't mount errors
Last night/this morning I reflashed his phone down to the slimroms 4.2.2 7/08 build though due to mine craft not installing on cm11 4.4.2. I had no problems going from the 4.4.2 back to a 4.2.2 . I usually don't have problems that cause me to have to re Odin eh03 but when I started rooting I usually would Odin. Now its been all from recovery or the flashify and ROM manager I've used when rooting. No PC needed
Click to expand...
Click to collapse
well i think why the "rom manager doesnt really work" statement goes around is that people would try to flash cwm through rom manager and it would actually brick their phones. that didnt happen to me but i did try it and the recovery couldnt mount anything aka it was a bad recovery. but if it worked for you, hey, that's actually pretty cool. might not work for everyone though

OK maybe I've been out of the flashing loop to long lol. I am a recovering flash addict , I tried many if not all of the cool newest roms using droidstyles guide. Guessing now I just need the most recent files for cm10 and cm11.
Sent from my SCH-I500 using XDA Free mobile app

Thanks, skeptic. 5 days and no regrets with CM11. I've had some phantom keys, but stable so far. Looks like Unjust could get a substantial donation

Still no luck. Can't get the cm10.1 to install today. Keeps aborting. Frustrating to say the least.
Sent from my SCH-I500 using XDA Free mobile app

Damn. That is frustrating for sure. Its been a week and no luck, I can't help any more then I've read here and a few other fascinate forums. That's weird mine flashed to the CM11 without those errors on two devices mine and my sons. I took his from the 4.4.2 cm11 back down to a 4.2.2 ROM so he could play minecraft without using a computer/odin or usb for anything. I'm sure someone will help get it though.

Where do I get a stock ROM? I've tried many links but haven't been able to find one that works.

icemanwbs said:
Still no luck. Can't get the cm10.1 to install today. Keeps aborting. Frustrating to say the least.
Sent from my SCH-I500 using XDA Free mobile app
Click to expand...
Click to collapse
Have you ever thought that maybe we need the error to help you?
Im going to take a guess that its trying to read the build.prop and you wiped.
If so, then you need to remove the build.prop asserts from the updater-script
It shoudl be the first few lines.

Lgrootnoob said:
Have you ever thought that maybe we need the error to help you?
Im going to take a guess that its trying to read the build.prop and you wiped.
If so, then you need to remove the build.prop asserts from the updater-script
It shoudl be the first few lines.
Click to expand...
Click to collapse
he ended up fixing it :good:
i think he odin'd stock, then went to cm10.1, then to kitkat possibly using my method

Questions about Safestrap...

Hello all, I'm very new to Android so please go easy on me… Not too long ago I installed Safestrap on my S5 Verizon. The main reason I did this was to be able to have image backups and maybe try some custom roms. But I have a couple of questions: I followed the youtube video from Root Junky on installing Safestrap and backing up the stock ROM. Everything "seems" to be working ok but what I don't understand is when I boot off the rom slot 1 and then go into Safestrap via the app icon, I don't have "reboot to recovery" enabled. Its grayed out. Why is that? Should it be that way? Second question i have: I'm getting prompted that a new version of OS software is available for my phone. I've tried doing the update but it errors out and doesn't get installed. Should I be able to update to the new OS with Safestrap installed? The state my phone is in right now in Safestrap is: State: installed, Safe system: Not active. To my limited knowledge i think this is because I'm booted off the stock rom. But if Im booted off the stock rom, shouldn't I be able to update the OS??
Sorry if these are newb questions but Im just trying to get a better understanding of how the phone is setup. I understand the concept of the rom slots but still confused over whats going on in the above explanation.
Thanks in advance.

NSDroider said:
Hello all, I'm very new to Android so please go easy on me… Not too long ago I installed Safestrap on my S5 Verizon. The main reason I did this was to be able to have image backups and maybe try some custom roms. But I have a couple of questions: I followed the youtube video from Root Junky on installing Safestrap and backing up the stock ROM. Everything "seems" to be working ok but what I don't understand is when I boot off the rom slot 1 and then go into Safestrap via the app icon, I don't have "reboot to recovery" enabled. Its grayed out. Why is that? Should it be that way? Second question i have: I'm getting prompted that a new version of OS software is available for my phone. I've tried doing the update but it errors out and doesn't get installed. Should I be able to update to the new OS with Safestrap installed? The state my phone is in right now in Safestrap is: State: installed, Safe system: Not active. To my limited knowledge i think this is because I'm booted off the stock rom. But if Im booted off the stock rom, shouldn't I be able to update the OS??
Sorry if these are newb questions but Im just trying to get a better understanding of how the phone is setup. I understand the concept of the rom slots but still confused over whats going on in the above explanation.
Thanks in advance.
Click to expand...
Click to collapse
Here is good explanation http://galaxynote3root.com/galaxy-n...-custom-rom-using-safestrap-on-galaxy-note-3/. Its not for the S5 specificaly but thats not relevant.

Thanks, but nothing in there answers my questions. Anyone else please?

NSDroider said:
Thanks, but nothing in there answers my questions. Anyone else please?
Click to expand...
Click to collapse
Then might i suggest you search yourself too answer your question instead of waiting for others

Thanks for the advice. The reason for my post is due to not finding an answer. Hoping to hear from someone with experience.

NSDroider said:
when I boot off the rom slot 1 and then go into Safestrap via the app icon, I don't have "reboot to recovery" enabled. Its grayed out. Why is that? Should it be that way?
Click to expand...
Click to collapse
Yes this is normal. Hashcode warns against installing safestrap while on a ROM slot. See Post 2 in the safestrap thread.. First bullet point: "If you install Safestrap on a rom-slot it will show "not installed". *DO NOT INSTALL SAFESTRAP ON A ROM-SLOT*"
NSDroider said:
Second question i have: I'm getting prompted that a new version of OS software is available for my phone. I've tried doing the update but it errors out and doesn't get installed. Should I be able to update to the new OS with Safestrap installed? The state my phone is in right now in Safestrap is: State: installed, Safe system: Not active. To my limited knowledge i think this is because I'm booted off the stock rom. But if Im booted off the stock rom, shouldn't I be able to update the OS??
Click to expand...
Click to collapse
No and no. Because your system is modified, you will never be able to install the OTA that Verizon pushed out. Instead, I would follow and install the stock-rooted NE9 rom by BeansTown106. Follow the instructions in post 2
NSDroider said:
Sorry if these are newb questions but Im just trying to get a better understanding of how the phone is setup. I understand the concept of the rom slots but still confused over whats going on in the above explanation.
Click to expand...
Click to collapse
No problem. We were all noobs at one time. Asking questions is how we all learned :good:

@MrHyde03, thanks for the quick reply. How would I avoid installing safestrap in a rom slot? I want to correct what I might've done wrong but pretty sure I followed the video to a tee. Maybe it's worth me installing safestrap over before doing anything else? Thanks.

NSDroider said:
@MrHyde03, thanks for the quick reply. How would I avoid installing safestrap in a rom slot? I want to correct what I might've done wrong but pretty sure I followed the video to a tee. Maybe it's worth me installing safestrap over before doing anything else? Thanks.
Click to expand...
Click to collapse
Well you would have installed the Safestrap APK from the stock slot originally, then proceeded to install Safestrap recovery. But it sounds like, from what I read in your first post, that you also installed the Safestrap APK on the ROM slot. THis shouldn't be done. Only the stock slot should have anything to do with Safestrap.
But in reality, just about everyone is recommending NOT using rom slots and just sticking with the stock to install new ROMs as there are still bugs that hashcode hasn't worked out yet.

Is there any way for me to check where it's actually installed? Not sure why I would've installed it in the rom slot or even if I knew I was doing it ?
Just searched for the file and see its here:
Is that the wrong place for it?
{
"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"
}

NSDroider said:
Is there any way for me to check where it's actually installed? Not sure why I would've installed it in the rom slot or even if I knew I was doing it ?
Just searched for the file and see its here:
Is that the wrong place for it?
Click to expand...
Click to collapse
Well that actually doesn't matter. That's just the APK file from when you downloaded it. Is it in your app drawer?
From ROM slot 1, Go to Settings > Applications > Application Manager > Downloaded and see if it's in the list.

Yes its in my app drawer. I guess that's what I don't understand. When u say "from rom slot 1" do u mean activate rom slot 1 from recovery and then Got to settings>...?

I checked the above after activating rom slot 1 and yes Safestrap is listed there. It's also listed there if I activate the stock rom. So I guess that means it's in both places? If that's the case what would I need to do to?

NSDroider said:
I checked the above after activating rom slot 1 and yes Safestrap is listed there. It's also listed there if I activate the stock rom. So I guess that means it's in both places? If that's the case what would I need to do to?
Click to expand...
Click to collapse
Ok. Then you have safestrap installer app installed on a ROM slot, which won't work. The only place you should have the app installed is the stock slot. If you run the safestrap app from the stock slot, you can reboot directly into safestrap and all of that.
I recommend you uninstall the safestrap app from rom slot 1 as per hashcodes recommendation and only use the app from the stock slot.

MrHyde03 said:
Ok. Then you have safestrap installer app installed on a ROM slot, which won't work. The only place you should have the app installed is the stock slot. If you run the safestrap app from the stock slot, you can reboot directly into safestrap and all of that.
I recommend you uninstall the safestrap app from rom slot 1 as per hashcodes recommendation and only use the app from the stock slot.
Click to expand...
Click to collapse
Thanks, that helped. I removed Safestrap from rom slot 1. I know you recommended flashing the rom from Beanstown but I don't feel totally comfortable doing that just yet. Would you know of any way to stop Samsung verizon auto update from being asked? I know it's included in his rom but maybe you know of a hack outside of using that?
Thanks again.

Flashing a new rom isn't that bad, especially a stock one and with safestrap. You can try it on a rom slot. Otherwise I think there's a module in xposed framework that will disable the alert, among other things you should check out. There's a whole forum here on XDA about it.
Sent from my SM-G900V using XDA Free mobile app

Will do. Thanks again for your help.

NSDroider said:
Thanks, that helped. I removed Safestrap from rom slot 1. I know you recommended flashing the rom from Beanstown but I don't feel totally comfortable doing that just yet. Would you know of any way to stop Samsung verizon auto update from being asked? I know it's included in his rom but maybe you know of a hack outside of using that?
Thanks again.
Click to expand...
Click to collapse
You could try freezing security updates...
You should really read this
http://forum.xda-developers.com/showthread.php?t=2784860
[HOW TO] [GUIDE] [Q&A] - Verizon Samsung Galaxy S5 ROOT & Then Some
It has just about everything in there
http://bit.ly/1brshoa

Great thx. I froze SDM 1.0 per the post. Let's see if that does it.

That's for the ota the one for the security updates from Samsung is the one in the picture SPD v2
http://bit.ly/1brshoa

Ok but why do I need to freeze that one? And do u mean "security policy updates"?