Develop Bugs

[SYSTEM DUMP] I317 - ATT Note II

Hey guys, here is a bone stock system dump for the i317 note for anyone that wants/needs it for whatever purpose. This was acquired from an out of the box AT&T Note II with only Chainfire's initial kernel allowing root adb shell. Before anything I dd'd each partition, here is the system partition (7zipped to cut the size down to 1/3 of the full img). Hope it helps in some way to anyone that needs to dd back a working att i317 system or anyone that wants to start hacking away at it If you need/want any other partition just let me know and I'll upload it. Again this is bone stock dd of mmcblk0p13 before root, so if you mess up you can use adb to dd it back, or convert it to tar (which I'll do in the next day or so if neccisary). Thank BLOWNCO for hosting Hope it helps
http://www.blownco.com/th3g1z/p13.7z

Hey guys,
I'm not sure if you know about DAGr8, but however does, I believe he got his phone, because this is what I found... http://www.blownco.com/DAGr8/
I'm not sure if this is a ROM, but I'll test it!

ilikov said:
Hey guys,
I'm not sure if you know about DAGr8, but however does, I believe he got his phone, because this is what I found... http://www.blownco.com/DAGr8/
I'm not sure if this is a ROM, but I'll test it!
Click to expand...
Click to collapse
not anymore

Hey bradah blownco does that mean will be having a smooth watery liquid rom here shortly much alohas
Sent from my SAMSUNG-SGH-I317 using Xparent Red Tapatalk 2

How do you convert to tar file ? Would I be able to use that with odin then ? Sorry , I am a noob to the Androids way of life. Thanks

Thanks, great to have for reverting back to stock if a warranty situation comes up. Maybe a MOD can move this to the dev section if applicable?

Wait... so how do you install this?

This is a bit by bit img of the system partition of the att note. So you don't exactly install it. Basically you can adb into your phone and use the dd command to write it back to the system partition (mmcblk0p13). My first attempt at making it a tar to use with ODIN failed I will try an alternative method tonight when I'm off work.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

th3g1z said:
This is a bit by bit img of the system partition of the att note. So you don't exactly install it. Basically you can adb into your phone and use the dd command to write it back to the system partition (mmcblk0p13). My first attempt at making it a tar to use with ODIN failed I will try an alternative method tonight when I'm off work.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Thanks th3g1z for all that your doing . :good: On that stack dump img file , would I just put it on my sd card and then go through the CWM Recovery mode on the phone and install zip from external sd card ?

th3g1z said:
This is a bit by bit img of the system partition of the att note. So you don't exactly install it. Basically you can adb into your phone and use the dd command to write it back to the system partition (mmcblk0p13). My first attempt at making it a tar to use with ODIN failed I will try an alternative method tonight when I'm off work.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for trying bro. I am new to android moving from iphone to android and Stuck at CWM recovery. I try to unroot my phone from SU and now cant remove CWM recovery console. My phone works fine but this is the problem. Below is detail explanation of my issue. If you get lucky with any other method to restore system dump back to galaxy note 2 at&t please do let me know.
I have galaxy note 2 i317 AT&T version. I have unrooted my phone but still have CWM recovery left. How I can remove that. I am new to this. I was able to retrive firmware for my device from samsung open source site but not sure how to deploy or flash back to my i317 model using odin.
I was able to download Samsung galaxy note 2 at&t firmware from opensource samsung com but dont know how to deploy or flash to my phone using ODIN. If someone can please advice on some steps or tutorial I will really really appricate.
I just want my phone to be normal the way it was before

th3g1z said:
This is a bit by bit img of the system partition of the att note. So you don't exactly install it. Basically you can adb into your phone and use the dd command to write it back to the system partition (mmcblk0p13). My first attempt at making it a tar to use with ODIN failed I will try an alternative method tonight when I'm off work.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Th3g1z any luck on that if yes please post instructions thanks lot

I apologize I didn't get to today. It seems you are stuck with CWM and would like to have the stock recovery back? If that is the case, use chain fires cf auto root. This will root your system as well as restore the stock recovery. If you then want a un rooted system, open supersu and use the option to fully unroot. I will try another tarball tomorrow. It appears I need to tar with -H ustar and then convert it to md5 and then hopefully that will do the trick. Ran out of time trying today but I will give it another go tomorrow. I'd rather test it before it fully before posting to minimize any soft bricking, however for anyone able to get to recovery or able to adb as root you can simply use dd to write the img back to system (mmcblk0p13)
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Any chance of someone turning this into a tar file so I can Odin back to stock please?

Bump for the greatness
A stock .tar from this would be very handy and welcome if available. Thanks for the initial system dump OP

Nexus 7 OTA Error

Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions

SwiftLeeO said:
Well, I used a factory reset tool to reset my rom back to stock. However, when I try to do a system update, it goes all the way to the end and says Error. Note that I can get into my tablet before I launch the update, but afterwards it just boots into recovery and I have to hard reset and reset my device using the aforementioned factory reset tool. Basically all I want to know is if it has anything to do with me recovering from the tool, or are OTA's iffy? I bought the device yesterday and I love it. I rooted it, unlocked the bootloader, etc. So yes it is modified. However It is not in anyway bricked. I just want to know if it's possible to do an official OTA from System Update, or do I have to use the one provided on the Index of the Nexus 7 Flo forum? Thanks for any help. Like I said, It's not bricked, I'm not complaining. Just a few questions
Click to expand...
Click to collapse
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.

charesa39 said:
Well, without much detail about the error, it's hard to help. Are you just stock rooted with stock recovery? If so, you should be able to take an OTA no problem, although you'd lose root. But you can always flash supersu to get it back. Did you install a custom recovery to root? Or did you use a toolkit? Lots of questions. If you have a custom recovery, you'd have to fastboot flash the stock recovery from the factory image. If you still have the stock recovery and are just stock rooted, you've probably modified the system in some way. In that case, you can just fastboot flash the stock system image.
Click to expand...
Click to collapse
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.

SwiftLeeO said:
Stock Rooted with Stock Recovery. It downloads the OTA no issue, but when in download mode, it gets to the very end and says Error!. I used CFAutoRoot for rooting. I used fastboot to unlock the bootloader and install custom recovery.
Click to expand...
Click to collapse
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app

charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Exactly what I was wondering!

charesa39 said:
Wait. So do you currently have stock recovery or a custom recovery?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Stock.

SwiftLeeO said:
Stock.
Click to expand...
Click to collapse
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app

charesa39 said:
Since you have stock recovery, there's probably an app that modified your system that's not allowing it to install the update because it detects a change in one of your system files. Fastboot flash the system image from the stock factory image. Then, it should update.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You wouldn't happen to have one of those lying around would you? The img file I mean.

SwiftLeeO said:
You wouldn't happen to have one of those lying around would you? The img file I mean.
Click to expand...
Click to collapse
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app

charesa39 said:
I'm assuming you're on 4.3 since you're trying to update? Either way, you can find the factory images here: https://developers.google.com/android/nexus/images.
Just download the the one for the version you're currently running on your N7. MAKE SURE YOU DOWNLOAD THE CORRECT ONE. Then, just extract the files from the tar.gz file. There's another zip file in that tar.gz file. Extract that one, and there's a system.img file. Fastboot flash it in the bootloader.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help

SwiftLeeO said:
Thanks for the help
Click to expand...
Click to collapse
Anytime. :thumbup:
Sent from my Nexus 7 using xda app-developers app

Regain root from mobile

In an attempt to unroot and return to stock for 4.4 OTA I flashed stock firmware and unrooted my device in the process, so far so good.
I reboot my phone after to initiate the OTA but of course I can't download the OTA because my device status is still custom and without root I can't triangle away or do anything.
I'm still trying to figure out how to get root back onto my phone from my phone since I don't have access to a computer where I'm at. I'm basically just screwed and also stuck on MDL baseband with a MK2 build running 4.3 stock so I'm getting no downloads at all. XDA the app itself too 10min to download
Any insight would be greatly appreciated...I knew I should have just waited until I I had access to a pc but I jumped the gun of course. I've been looking around a lot and the only methods of rooting I've found require or use a pc.
Sent from my SGH-M919 using xda app-developers app

JORDVN said:
In an attempt to unroot and return to stock for 4.4 OTA I flashed stock firmware and unrooted my device in the process, so far so good.
I reboot my phone after to initiate the OTA but of course I can't download the OTA because my device status is still custom and without root I can't triangle away or do anything.
I'm still trying to figure out how to get root back onto my phone from my phone since I don't have access to a computer where I'm at. I'm basically just screwed and also stuck on MDL baseband with a MK2 build running 4.3 stock so I'm getting no downloads at all. XDA the app itself too 10min to download
Any insight would be greatly appreciated...I knew I should have just waited until I I had access to a pc but I jumped the gun of course. I've been looking around a lot and the only methods of rooting I've found require or use a pc.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
A stock firmware package makes the phone all stock. MDL baseband on an MK2 build means you didn't flash a stock firmware. Which 'stock' firmware did you flash?
As to root, did this 'stock' firmware also flash recovery? if it didn't you can download the recovery flashable supersu zip from chainfire's website into the phone and do it that way. Otherwise, I don't think there is a way to get root access from the OS itself, unless you find an exploit that grants su access so you can make system writable and push supersu.

qxps said:
A stock firmware package makes the phone all stock. MDL baseband on an MK2 build means you didn't flash a stock firmware. Which 'stock' firmware did you flash?
As to root, did this 'stock' firmware also flash recovery? if it didn't you can download the recovery flashable supersu zip from chainfire's website into the phone and do it that way. Otherwise, I don't think there is a way to get root access from the OS itself, unless you find an exploit that grants su access so you can make system writable and push supersu.
Click to expand...
Click to collapse
I'm can't remember where I got this firmware from but, it was from a thread within the general section which stated it was stock so I'm just unsure on that part. I will try to root using your information given. This did return to stock recovery as well but when I try to flash anything through it I get a signature verification failure. I've never had this happen where baseband and build didn't match after returning to a stock firmware. My guess is that I just used something I shouldn't have. Thanks for the help.
Sent from my SGH-M919 using xda app-developers app

After downloading the supersu and attempting to flash it through stock recovery, I'm still getting signature verification failure then the device reboots.
Sent from my SGH-M919 using xda app-developers app

JORDVN said:
After downloading the supersu and attempting to flash it through stock recovery, I'm still getting signature verification failure then the device reboots.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, rooting or installing custom recovery needs to be done through a computer. As of this moment, there are no root exploits that can be done via the phone itself. I'm sorry.

JORDVN said:
After downloading the supersu and attempting to flash it through stock recovery, I'm still getting signature verification failure then the device reboots.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
That's because you need a custom recovery, it's why I asked whether the firmware you flashed replaced recovery or not.
As vigz said, you need a computer to at least flash cf root with odin.

qxps said:
That's because you need a custom recovery, it's why I asked whether the firmware you flashed replaced recovery or not.
As vigz said, you need a computer to at least flash cf root with odin.
Click to expand...
Click to collapse
Okay I've pretty much come to that conclusion after continuously searching with no solid method. I'll just have to deal with the baseband problem for now until I get back home. Wifi toggle doesn't work at all either. Is that a baseband problem, correct?
Sent from my SGH-M919 using xda app-developers app

Vigz said:
Unfortunately, rooting or installing custom recovery needs to be done through a computer. As of this moment, there are no root exploits that can be done via the phone itself. I'm sorry.
Click to expand...
Click to collapse
Thanks for the insight, I'll have to make due with what I have for now
Sent from my SGH-M919 using xda app-developers app

[Q] Questions on stock 4.3

I've been searching and reading for last couple days and haven't been able to find a definite answer. I'm using note 2 i317 at&t with stock 4.3 out of the box. I've been able to root it and get past Knox successfully. My question is can I install a custom recovery using stock 4.3? I'm wanting to use xposed framework and I want to be able to make a backup and have recovery optons. I've heard it may not be possible on 4.3 due to possible locked bootloader and the Knox thing. Any help is appreciated.

Just flash your custom recovery using Odin...
The Knox bootloader is generation #1...and does not prevent the flashing of custom recoveries or kernel images. .
Edit:...custom recoveries will trip the Knox counter...and void the device warranty. ..
Once you have a custom recovery. ..you can create your full nandroid backup...
Then you'll be able to do anything you want with roms etc....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Thanks I appreciate it. So if I do happen to get into trouble will I be able to just use my backup to restore things or use Odin to flash back to the stock 4.3 rom?
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app

jaybeerange said:
Thanks I appreciate it. So if I do happen to get into trouble will I be able to just use my backup to restore things or use Odin to flash back to the stock 4.3 rom?
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Not exactly. ..
Once you root...or flash a custom recovery. ..you will trip the Knox counter...(bootloader flag)
Effectively. ..that will void warranty...
However. ..This flag will not effect using your nandroid backup to restore the device if you should need it... (store that backup on your PC for safety)...
But if you don't care about warranty. ..then a revert to stock 4.3 is quite easy...minus the tripped bootloader flag....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

OK sounds good. Thanks for all the helpful info. I did a lot of flashing long time ago on my old cappy but haven't really messed with anything this new. I appreciate it.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app

i'm on stock 4.3 with root access... yet ES file manager will not let me copy files to the system/app folder. Root checker says i have root access. terminal emulator shows # when i type su.
when i turn on root explorer in ES file manager - i get test failed. feature can not run on my device. any help?

Dont you need to change to read/write?

I have one more question on the 4.3 boot loader thing. Am I able to flash Roms that are based on an earlier android version like 4.2.2 since I am on official 4.3 boot loader? I was looking at flashing a ported miui v5 ROM but I'm pretty sure its 4.2 based.

rangercaptain said:
Dont you need to change to read/write?
Click to expand...
Click to collapse
when i check the properties of the System/app folder with ES file explorer... it says yes to both readable and writable.

Sry if I seem like I'm thread jacking but just wanted to clarify something. So with the AT&T note 2 on the stock ota 4.3 we can still install a custom recovery and flash custom roms and kernels or does it have to be 4.3 touchwiz based roms? If so can someone tell me the steps to do so?
The only reason I'm asking is I have both an att not 2 and a Verizon both on 4.3 and with the Verizon note 2 I had to use safestrap to flash a custom rom but can't flash kernels (so I'm not really new to flashing and all but new to the att scene and wanted to make sure bc I was told that with a locked bootloader I couldn't flash roms and a custom recovery and don't want to break my phone)
Thanks (also I only had an att note 2 is so I can get 4g lte on straight talk but I like having the note 3 features)
Again thanks for the help as of right now my att note 2 is a paper weight and if I can flash any custom rom on stock 4.3 it'd be great bc at least I wouldn't have wasted my money haha
Sent from my SCH-I605 using XDA Free mobile app

ArmStrongDickPunch said:
Sry if I seem like I'm thread jacking but just wanted to clarify something. So with the AT&T note 2 on the stock ota 4.3 we can still install a custom recovery and flash custom roms and kernels or does it have to be 4.3 touchwiz based roms? If so can someone tell me the steps to do so?
The only reason I'm asking is I have both an att not 2 and a Verizon both on 4.3 and with the Verizon note 2 I had to use safestrap to flash a custom rom but can't flash kernels (so I'm not really new to flashing and all but new to the att scene and wanted to make sure bc I was told that with a locked bootloader I couldn't flash roms and a custom recovery and don't want to break my phone)
Thanks (also I only had an att note 2 is so I can get 4g lte on straight talk but I like having the note 3 features)
Again thanks for the help as of right now my att note 2 is a paper weight and if I can flash any custom rom on stock 4.3 it'd be great bc at least I wouldn't have wasted my money haha
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I have the att note 2 and it came with stock 4.3 and I'm now running ezkat 4.4.2 with agni kernel. So yes you can run roms and kernels. Only thing I'm not 100% sure on is if you can downgrade to 4.2 or 4.1. Here is the link to the room I'm running. It's great and has a lot of note 3 features and some s5 features.
http://forum.xda-developers.com/showthread.php?t=2747733

jaybeerange said:
I have the att note 2 and it came with stock 4.3 and I'm now running ezkat 4.4.2 with agni kernel. So yes you can run roms and kernels. Only thing I'm not 100% sure on is if you can downgrade to 4.2 or 4.1. Here is the link to the room I'm running. It's great and has a lot of note 3 features and some s5 features.
http://forum.xda-developers.com/showthread.php?t=2747733
Click to expand...
Click to collapse
OK how would I go about installing the custom recovery (also what did u use to root? And just saying I'm more familiar with the Verizon note 2 so that why i have some noobish questions lol) I'd rather not try downgrading
Could you please give me step by step instructions since i can't find any on how to install a custom recovery on stock 4.3?
Thanks
Sent from my SCH-I605 using XDA Free mobile app

ArmStrongDickPunch said:
OK how would I go about installing the custom recovery (also what did u use to root? And just saying I'm more familiar with the Verizon note 2 so that why i have some noobish questions lol) I'd rather not try downgrading
Could you please give me step by step instructions since i can't find any on how to install a custom recovery on stock 4.3?
Thanks
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
Here is a link that shows you step by step to root(this is how I did it) also you will probably need to do the tutorial at the bottom of the page for the Knox security. http://www.droidviews.com/root-att-galaxy-note-2-sgh-i317-on-android-4-3-ucubmk6-firmware/
And here is recovery I recommend http://forum.xda-developers.com/showthread.php?t=2159652

jaybeerange said:
Here is a link that shows you step by step to root(this is how I did it) also you will probably need to do the tutorial at the bottom of the page for the Knox security. http://www.droidviews.com/root-att-galaxy-note-2-sgh-i317-on-android-4-3-ucubmk6-firmware/
And here is recovery I recommend http://forum.xda-developers.com/showthread.php?t=2159652
Click to expand...
Click to collapse
Ok I'll just use saferoot to root since I used it before
http://forum.xda-developers.com/showthread.php?p=48392009
My question is though is how do I install the recovery (I'll read more into it but how did u do it so I don't brick the phone) and also how can we flash custom roms and kernels if it's on stock 4.3 with the locked bootloader? Or is it not locked?
Sent from my SCH-I605 using XDA Free mobile app

ArmStrongDickPunch said:
Ok I'll just use saferoot to root since I used it before
http://forum.xda-developers.com/showthread.php?p=48392009
My question is though is how do I install the recovery (I'll read more into it but how did u do it so I don't brick the phone) and also how can we flash custom roms and kernels if it's on stock 4.3 with the locked bootloader? Or is it not locked?
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I just used Odin and flashed phils cwm file. You can get it in either a flashable zip or and Odin flashable file. The bootloader not really locked from what I understand it just won't let you replace it with an earlier version. Basically no problems flashing roms and kernels and such. You just have to kill the Knox security deal with super su

jaybeerange said:
I just used Odin and flashed phils cwm file. You can get it in either a flashable zip or and Odin flashable file. The bootloader not really locked from what I understand it just won't let you replace it with an earlier version. Basically no problems flashing roms and kernels and such. You just have to kill the Knox security deal with super su
Click to expand...
Click to collapse
Ok I've never used Odin before does it say how to use Odin to flash the recovery? And thanks for ur help
Sent from my SCH-I605 using XDA Free mobile app

ArmStrongDickPunch said:
Ok I've never used Odin before does it say how to use Odin to flash the recovery? And thanks for ur help
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
I think it does. Basically load up Odin have your phone in download mode and put the recovery file into pda slot make sure Odin recognizes your phone and hit start.

jaybeerange said:
I think it does. Basically load up Odin have your phone in download mode and put the recovery file into pda slot make sure Odin recognizes your phone and hit start.
Click to expand...
Click to collapse
Ok sounds good I'll give it a try tomorrow I'll post any questions or how it goes. Thanks
Sent from my SCH-I605 using XDA Free mobile app

Deleted

jaybeerange said:
I think it does. Basically load up Odin have your phone in download mode and put the recovery file into pda slot make sure Odin recognizes your phone and hit start.
Click to expand...
Click to collapse
What version of Odin did you use or should I use? And can you send me a download link? And I just put the recovery file into pda slot and flash that's it?
Sent from my SCH-I605 using XDA Free mobile app

Soft Bricked? Stuck at boot screen.

Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Basically I do have common sense and and I'm pretty knowledgeable when it comes to working with phones but this problem I have is different.
I purchased this phone(I747) already bricked thinking I can fix since I have before. It goes to cwm 6.0.3.4 and boots to Odin. Last known os was cm but don't know what version. Not even clear what bootloader it's but when trying to boot up there's the blue cm Android guy.
So here's what I tried so far to fix my problem.
1. Tried to flash the mjb restore posted somewhere on here. Flashed with no errors but when I reboot still the blue Android.
2. Wipe and formatted the proper things and tried flashing a couple of roms but all gave me error 7.
3. Tried flashing a different recovery thru Odin, all passed but non stuck. Can't get rid of my current recovery.
4. Tried to Odin 4.3 firmware but that failed.
Kinda running out of ideas on what to try next, can someone help me figure out what I'm doing wrong or what's the problem?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?

BWolf56 said:
What did you try to flash? Status 7 means you don't have the right device for what you were trying to flash or that your build.prop was modified by the previous owner to another device name.
I believe you'll need to flash a ROM matching the current device name and work from there.
Although, I find it odd that flashing with Odin doesn't work. Have you tried flashing stock?
Click to expand...
Click to collapse
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
Yep I tried stock 4.1.1 and 4.3 thru Odin and failed. I tried installing a new recovery thru the current recovery using a zip file and it went thru with no errors but reboot and nothing has changed. Something when flashing the restore and the bootloader.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.

BWolf56 said:
You can try flashing another/updated recovery through Odin. But until you find out what device your build.prop is setup to, you won't be able to flash a ROM through recovery.
Click to expand...
Click to collapse
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
I tried every recovery for this phone that's up to date so yeah I don't know what else to do. And how can I figure that out? The build.prop part?
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's in your System folder. Should be able to navigate to it using your recovery.

BWolf56 said:
It's in your System folder. Should be able to navigate to it using your recovery.
Click to expand...
Click to collapse
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?

donutkidd said:
Will it still be there even if I formatted the system? If so what are the adb commands so I can pull it and post it?
Click to expand...
Click to collapse
Hopefully it is. And I duno about the command, you'll have to look that one up (or perhaps someone here knows it).

If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk

Ok I will try that when I get home.
Sent from my SM-N900T using XDA Premium 4 mobile app

DocHoliday77 said:
If you formatted /system, its gone and shouldn't matter. But imo you should never format system manually. Otherwise you end up with nothing to boot or troubleshoot if things go wrong.
From your recovery, find where you can use the terminal emulator and enter
getprop ro.boot loader
This is what firmware you need to be flashing via odin.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Ok I did the getprop ro.bootloader command and it's I747UCDLK3. I have already tried the lk3 Odin but let me try to re download a fresh copy of it.
Sent from my SM-N900T using XDA Premium 4 mobile app

No dice, I even downloaded a 4.1.1 lk3 rom. It flashed and said successful so I rebooted and back to the blue Android. Is it possible NY partitions or whatever are corrupt and if so anyway to fix it?
Sent from my SM-N900T using XDA Premium 4 mobile app

I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.

DocHoliday77 said:
I'm kinda at a loss. Wondering if its a partition not flashed by Odin that's been corrupted...
No idea if this'll help or not, but download this.
http://www.androidfilehost.com/?fid=23060877489996938
(It is a 16gb model right?)
Now flash firmware in Odin in like usual, but check the repartition checkbox, then click the PIT button and browse to and select the file I just linked. Verify.
Click start and cross fingers.
Another thing you can try...flash twrp with Odin, but uncheck auto reboot. After it says PASS, pull the battery. Put it back in and boot recovery. Hopefully it'll stick now.
Now you can try flashing some roms again, and use the built in file manager to look for any issues/anomalies.
I'm not sure what version LK3 is, but it sounds kinda old, so you may want to look for a 4.1.1 rom to start with. That shouldn't give you any status 7 errors. Or if you want to flash newer roms you'll need to edit the asserts in the updater script.
Click to expand...
Click to collapse
I honestly think I tried what you suggested already but just to triple check I will do so again in the morning and report back with hopefully good news.
Sent from my SM-N900T using XDA Premium 4 mobile app

@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?

DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
No, nothing for 4.1.1 (LK3).
I don't think that's his issue though. Last time I saw that issue was on the S1 (Captivate) and the solution was to use Heimdall.
If the repartition doesn't work though, I'm not exactly sure what will.

DocHoliday77 said:
@BWolf56
Do you guys have a recovery flashable package for the 4.1.1 or 4.1.2 firmware? (I'm guessing that's what LK3 is.)
If so maybe flashing that would help?
Click to expand...
Click to collapse
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.

donutkidd said:
I was just reading what you said in this post - > ([Q] Can't flash stock rom through Odin, phone only boots in download mode. Help!) and it does sound awfully like my situation being that nothing sticks after flashing.
Click to expand...
Click to collapse
Do you have the actual link to that thread? Search is derping on me.

BWolf56 said:
Do you have the actual link to that thread? Search is derping on me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app

donutkidd said:
http://forum.xda-developers.com/showthread.php?t=2415409
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ouff that's one bad issue, it can take a while to figure out which partition got messed up. And sadly, I can't be much help there :/