Develop Bugs

[GUIDE] Using ODIN to flash your Epic 4G Touch (windows only)

PREREQUISITES:
ODIN v1.85 (included at the bottom) [WINDOWS ONLY]
Samsung KIES (for the drivers needed)
Samsung Epic 4G Touch (I know - should be obvious.....) and USB cable
Your brain and eyes to read this ENTIRE thing BEFORE you do anything
INITIAL SETUP:
Install Samsung KIES
Connect your Epic 4G Touch to a Windows computer. (Sorry ODIN uses Windows only...)
Wait for Windows to initialize your phone with the drivers
Unzip the Odin3 v1.85.zip file to it's own directory
Disconnect Epic 4G Touch from your computer
ODIN STARTUP
Open up odin3 v1.85.exe and you'll see this screen
Turn your E4GT off (again should be obvious) and unplug if plugged in
Put your E4GT into download mode by holding down Volume-Down first and then hold down the Power button until you see this screen:
{
"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"
}
Press Volume-Up to continue or Volume-Dn to restart
Volume-Up gets you this screen:
You're now in Download Mode and ready to continue.
ODIN OPTIONS:
Here is the ODIN screen:
Connect your E4GT to your computer.
The top left box should light up like this:
If it doesn't, close out of ODIN, unplug your phone, take the battery out, put it back in, restart computer, and repeat the ODIN STARTUP steps above.
PIT Button: This is for the partition structure when flashing an entire ROM
BOOTLOADER Button: This is for uploading a new bootloader (we don't have, and have never used this - IGNORE!)
PDA Button: This is for flashing kernels and ROMs (in .tar format)
PHONE Button: This is for the phone's RADIO/MODEM ONLY!!!!!!
CSC Button: Not sure - don't use.
DO NOT USE PHONE FOR ANYTHING BUT A RADIO/MODEM - YOU WILL DEFINITELY NOT BE ABLE TO USE YOUR PHONE FOR CALLS, AND YOU MAY POSSIBLY BRICK IT - YOU'VE BEEN WARNED
This concludes the basics on what ODIN is and how to use it. For the items to flash you'll find them on this site.
DISCLAIMER: YOU, AND YOU ALONE, ARE RESPONSIBLE FOR YOUR ACTIONS IN USING ANYTHING ON THIS SITE. DO NOT COME CRYING IF YOU MESS UP YOUR DEVICE.
Noteworthy posts:
Yet Again said:
I'm not going to blame you for anything...I'm a retard, and WAY tired. I just flashed the root kernel over "phone" in Odin! Do you know where I can find the stock radio/modem to reflash it right? Anything you can do to help would be great!
Click to expand...
Click to collapse
Stock Modem EG12.bin - flash this using PHONE in ODIN

Awesome! I could have used this when I started on my GTab 10.1.
This will help a lot of folks. I'm very impressed by you and the other devs in this community thus far. You guys rock hard and I hope everyone realizes it.

For Linux/MacOS users - Heimdall is an open source cross-platform replacement for Odin - http://www.glassechidna.com.au/products/heimdall/
However it can't automatically flash Odin tar files - you need to manually extract the tar and flash each individual component.

Entropy512 said:
For Linux/MacOS users - Heimdall is an open source cross-platform replacement for Odin - http://www.glassechidna.com.au/products/heimdall/
However it can't automatically flash Odin tar files - you need to manually extract the tar and flash each individual component.
Click to expand...
Click to collapse
Yep - was going to (sometime) put together a guide on Heimdall as well - but there are some out there

ok, I have tried the above directions. Kies installed. Odin installed. phone in d/l mode. Odin found phone. chose the tar file and started. It keeps getting stuck at zimage or setup connection.
I have uninstalled Kies thinking that maybe it was locking up the port and restarted. Still have the same "stall" condition. Any ideas? I really want to root and am stuck!
edit: I was using a usb cable through a usb hub. I switched to the cable that came with it directly to my pc and it worked fine. Guess Odin is picky.

jerdog said:
Yep - was going to (sometime) put together a guide on Heimdall as well - but there are some out there
Click to expand...
Click to collapse
I have googled the subject and can't find a guide on flashing using Heimdall in Ubuntu. I came from the Evo so I'm not familiar with Samsung's way of doing things.
Sent from my SPH-D710 using xda premium

firemedic624 said:
I have googled the subject and can't find a guide on flashing using Heimdall in Ubuntu. I came from the Evo so I'm not familiar with Samsung's way of doing things.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Heimdall rocks, here u go bud:
http://forum.xda-developers.com/showthread.php?t=1277000

Stupid question but can Kies software be uninstalled and just keep the Samsung USB drivers, would that still work?
dja2k

dja2k said:
Stupid question but can Kies software be uninstalled and just keep the Samsung USB drivers, would that still work?
dja2k
Click to expand...
Click to collapse
Could but better to use Kies for newer Samsung devices.

zedomax said:
Could but better to use Kies for newer Samsung devices.
Click to expand...
Click to collapse
I meant why keep Kies installed if you don't plan on using it and only needed the Samsung drivers installed to use Odin.
dja2k

Thanks for the guide you worthless pimple on the face of humanity. I couldn't soft brick or perma brick my new phone because the guide was too easy to follow.
You suck..... now I can't post...
"You're stupid guide bricked my new phone arsehole"

thebadfrog said:
Thanks for the guide you worthless pimple on the face of humanity. I couldn't soft brick or perma brick my new phone because the guide was too easy to follow.
You suck..... now I can't post...
"You're stupid guide bricked my new phone arsehole"
Click to expand...
Click to collapse
I am sorry to have given you an excuse to actually be productive with a device. I suggest you place it in a jell-o mold and freeze it as the one device you didn't brick - but then you'd have bricked it - thus fulfilling your original desire to brick. Now go pass one through your intestines.

jerdog said:
I am sorry to have given you an excuse to actually be productive with a device. I suggest you place it in a jell-o mold and freeze it as the one device you didn't brick - but then you'd have bricked it - thus fulfilling your original desire to brick. Now go pass one through your intestines.
Click to expand...
Click to collapse
I'm not going to blame you for anything...I'm a retard, and WAY tired. I just flashed the root kernel over "phone" in Odin! Do you know where I can find the stock radio/modem to reflash it right? Anything you can do to help would be great!

Yet Again said:
I'm not going to blame you for anything...I'm a retard, and WAY tired. I just flashed the root kernel over "phone" in Odin! Do you know where I can find the stock radio/modem to reflash it right? Anything you can do to help would be great!
Click to expand...
Click to collapse
Updated the OP:
Stock Modem EG12.bin - flash this using PHONE in ODIN

LOL...I'm SOOO thrilled you used my post as the "Noteworthy Post" example. A grand tip to the rest of the community, DO NOT attempt flashing/modding/rooting/hacking (as an amateur) when you are semi-drunk and half asleep. And THANK YOU to the OP for supplying the stock Modem, although, the scare of almost bricking my phone sobered me up enough to use the search function on the forum.
End of story!

anyone got a link to all the stock files for odin??

i cant get to odin.....instead it gives me android system recoverry. #manual mode# looks almost like clockwork mod but cant install using clk roms...

HELP
jerdog said:
Updated the OP:
Stock Modem EG30.bin - flash this using PHONE in ODIN
Click to expand...
Click to collapse
this is the real EG30 modem? not EG12? because I'm at EG31 and i've been trying to get back EG30 modem to try the EK02 modem.

exconvictriddick said:
this is the real EG30 modem? not EG12? because I'm at EG31 and i've been trying to get back EG30 modem to try the EK02 modem.
Click to expand...
Click to collapse
This is EG12, I wish Jerdog would update the link because it is going to confuse people.

kingsway8605 said:
This is EG12, I wish Jerdog would update the link because it is going to confuse people.
Click to expand...
Click to collapse
Just updated - my apologies.

Tutorial: How to use KIES Emergency Firmware Recovery (EFR)

Edit Nov 28 2013: GN3 Owners PLEASE READ!
As of the new update the ATT Galaxy note 3(possibly all carriers) IS NOT compatable with KIES EFR!
This includes KIES 2.XX and KIES 3! What does this mean?
If you took the MJ5 update you will no longer be able to use the KIES Emergency Firmware Updater.
Please complain to Samsung, locking the bootloader is one thing but no EFR??
Would you get on ship with no life boats or life preservers??
Seriously uncool of Samsung to do this.
-end of edit
/rant
So its come to my attention a lot of new guys are getting stuck soft brick, bootloop, borked recovery etc.
So .... I made this tutorial for everyone.
Please: dont flame or post useless comments.
Its great for you Odin is easy, but I made this for people who want a hassle free easy way to recover their phone.
This is also imo the fastest and easiest way back to true stock w/o a "modified"
Some people have reported a flash count of 1 but idk I always went back to 0.
If you are new, have no rooting, rom flashing or w/e experience, imo you should NOT be using odin until you have completely read up on it. I mean hey some of you super geniuses have no probs but when I see posters who have no clue about usb drivers or even how to use kies, im confused why you would want to venture to odin? 500 $ is a very expensive brick.
Ok so unsure about odin or just new and now you just borked your brand new phone?
First things first:
Can you get into dl mode.
Dont worry about recovery mode because it doesnt matter for this. This works with corrupted recovery as well.
For now lets just say download mode is achieved one way only:
Press : vol down power and home key all at the same time. Release quickly when you see the screen come up. Takes practice some times.
:thumbup: This method will remove "modified" status from your phone! :thumbup:
:beer:
Ok ready? You want step by step you got it.
If this doesnt work you are doing it wrong, so try again. Even with Odin you may have to try several times, its the nature of android.
If you can get into DL mode you CAN 100% recover your device.
If it doesnt work or you get an error, you are doing this wrong. I am pretty sure this is for ALL Samsung phones but I can only confirm this for my gs3 and note2.
Keep in mind: I corrupted my recovery on my gs3 several times and this still worked. I will assume the same for my note 2.
Download kies from samsung.com
Follow the prompts but no need to install the stupid codecs.
When you are done, (dont forget hit "yes" to dl current usb drivers)
ON your computer "run as administrator" the kies icon.
make sure you are connected to the internet.
Kies will automatically check for updates and proper usb drivers.
No need to install "myfree codecs" hit no on that.
every thing else hit yes
Step one:
Run kies as administrator as I said And do all the usb updates, kies updates
but leave the codec thing alone.
Step by step instructions just follow the pics in order:
1.Kies opens asks about update
{
"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"
}
2.
3.Dont worry about this
4. Now in top left corner hit "tools" tab. Ignore everything else
5. After clicking tools tab click the emergency fimrware recover choice as described below
6. For now ignore this button. YOu might need it later but ignore it for now
7.
8.Well last step. Hit emergency recovery ( the "ok" button wont be there )
this will probably take 20 to 30 min total. The EFR will let you know if its succesfull or fail.
IF it fails try using the method I said to ignore. Its the same thing just an extra step of in putting your phones exact model number.
Heres some xtra links: (Thanks to Bajanman for finding these btw!)
http://www.sammobile.com/firmwares/1/
http://www.sammobile.com/kies/
http://m.samsung.com/us/support/

Nice help guide for noobs.
Good guide freak :thumbup:
Might want to go back and check some of your words tho. Lot of them misspelled... lol
Side note: All my years with Sammy I've never used Kies with any of my phone's!!
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

yeah yeah yeah

Nice tut freakboy i just hope I dont need to use it someday I subscribed anyways who know flashing games always full of surprises.
Sent from my SAMSUNG-SGH-I317 using xda premium

Please HELP
i have an at&t galaxy note 2 was rooted got OTA update now no signal and when i go to mobile networks (under settings) it says insert sim card so i am trying to do it your way and i have updated everything (drivers and kies) and when i try to connect to kies it says my device isn't supported by kies and there is no phone model in the white box to use the "emergency recovery using recovery code" is there a place to get this code?
Please help

Well first off there shouldnt be a need to use the kies efr with just an ota.
You can select your phone model manually.
Can I ask...did you install a recovery and make a bu after you rooted ?
im not familiar with these newer ota probs, I remember on my dx ota was no biggie due to rootkeeper. Its strange that a stock rooted phone gets borked with an ota.
Can you get into recovery?
Can you get into dl mode?
Im subscribed to this thread so ill try n help out
Edit: are you using this method because you are unfamiliar with odin?

i did install CWM recovery
i don't remember making a back up but i am sure i did
i can NOT get to recovery
i can get to dl mode
i am familiar with odin but i am on my work computer as i don't have internet at home at the moment so i cant run searches as it trips the big brother software here and i would get in trouble the phone seems to work fine other then it doesn't recognize the sim card and no recovery mode
but if i could find a stock rom i could just flash with odin

That may also be your problem.
Are you running kies as admin?
Sorry if these sound like stupid questions.
But 8f you dont have admin privies kies may not work.
Regardless there is a drop down for you to manually choose your phone.
You do have usb debugging?
A corrupted recovery should not affect your ability to use kies.
Your jobs software could be blocking it.

Also you do realise you cannot take ota with custom recovery?
Thats why your phone is borked.

i do realize it now lol but i didnt even think about it when it happened
yes running kies as admin
no to usb debugging don't event remember how to get to usb debugging but if it is in settings under mobile networks i cant get there it just says insert sim card

Justvto be sure this is an sgh-i317 correct?
Try doing the upgrade first that may give you the code.
First make sure you have usb debugging
Home>Settings> developers options> make sure usb debugging is checked.
Also since it sounds like your recovery is corrupted do not do a factory reset.

Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.

+1
Sent from my SGH-I317M using xda premium

freakboy13 said:
Ok so try this:
Make sure you have latest drivers from samsung for YOUR device.
Make sure kies is the latest version.
Make sure antivirus is off orvput kies in the whitelist/allowed.
Turning off is better.
Go to dl mode on phone .
Sincevkies is already running go to thetop menu :
tools> emergency firmware recovery
You should get a drop down list of devices. If this is an att phone and not another carrier model ported to att, you should choose sgh-i317 (att galaxy note 2). You shouldnt need a number thats only if you try to upgrade and it fails ( as I mentioned you may want to try upgrade first to trick the que to give you a number)
Post back.
Click to expand...
Click to collapse
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much

mrnewspaper said:
thanks so much for all your help there is no drop down box on my version of kies however i found stock firmware some where else and it is working now again thanks so much
Click to expand...
Click to collapse
Nice job! Isnt it great figuring things out yourself?
Love hearing happy endings!
Now... go into recovery and :
Make a backup/boot img .
:thumbup:

Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?

activepassive said:
Hello,
I am trying to fix my Korean Note 1. It is not being listed in the list of devices. I have it in D/L mode but it isn't listed. Can I use the code and, if so, what is the right code?
Click to expand...
Click to collapse
Hmmm not that familiar with note 1 or international version but ill assume its the same?
If you are not listed in the database you may want to try using odin.
The code needs to be generated by kies.
Is kies recognizing your phone?
I may be mistakwn but isnt their a kies for your country or some thing like that?
Have you submited this question in your forum?
Edit: I found this I hope it helps you!
http://forum.xda-developers.com/showthread.php?t=1740367
sent from my T.A.R.T.I.S
(Time And Relative Tarts In Space)

so this will restore my phone to stock and will instal stock recovery and reset my flash counter and modified status? no need for tiangle away and unroot??

i tried doing exactly what was in the OP and it's now stuck at 0% at restoring. It's given me an error message a few times before and i tried again but it still stays at 0%. I tried doing it with the button you said not to click and running as admin.
Now i've got two problems, one is the phone not getting out of this mode and 2 is it not even giving me an error message meaning i can't try again since it's still busy restoring.
What can i do now? Should i just pull the plug out of it and try again? Will this not break anything?
What should i do now OP?
further info:
model: galaxy S3 GT-19300
i've had it rooted using CF-root and i did a firmware update to trigger emergency recovery mode.
I got into emergency recovery mode on purpose but expected to get out of it...
---------- Post added at 08:03 PM ---------- Previous post was at 07:10 PM ----------
Hooray! it's now actually installing it and i didn't mistake it for downloading this time. I switched USB ports and now it works apparently.
Also something people that do this in the future should know: if you unplug the cable, it just gives you the error message saying that it couldn't find it which shouldn't cause any trouble. BUT only do this once it is stuck at 0%.

Possibly stupid question..
Having rooted the Note 2 att with mr skips toolbox, I then noticed a few days later the modified status.. So due to concern for warranty being voided, I'd like to return to stock: ( Heres the stupid question part).. I did install stock recovery via same toolbox, But How do I tell if it is stock vs twrp? I dont see where/how to check if it succeeded. Next- Why wont factory reset work to clear the flash counter, modified status to normal with full wipe? and as much as I admire mr Cortex method to full wipe ( 10 min process..) is that repetitive process of wiping, triangle away,unroot, reroot etc..necessary? I had a rooted samsung epic 4g touch before this note 2 and All I did to return phone to stock firmware for trade in was factory reset! yes- it was Not jellybean, was Gingerbread android.
Perhaps someone or some devs can explain this bit of mystery to me, and perhaps others... who are in search of a more direct and straightforward reset without complicating the steps. I will probably reroot and run a custom rom after warranty runs out.. but for now..stock again.

"Your device has been modified"

Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?

cyanide911 said:
Here's the deal. I bought this Note 2 off a friend's friend so I can't *really* be sure what went on with this. It's under warranty still though.
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available". Here's what I tried:
1. Factory reset: Made no difference
2. There's no SD card so it can't be anything to do with the SD card (as reported in some other similar threads)
3. Flash counter is ZERO
4. Phone is unrooted.
So I don't really know what to do now. I'd flash 4.1.2 with odin but my dad is using it and he wants to do it the 'legitimate way' whatever that means.
Anyway, so do we have a 'fix' for this? If not, am I safe to go to the Samsung service center with this since the flash counter is 0 so they can't say that I've modified it?
Click to expand...
Click to collapse
Humour yourself, reset again, see if it helps.
Another thing you can try doing, which I've read somewhere:
Go into Settings
App Manager
Clear data for SysScope and Enterprise SyssSope
Click to expand...
Click to collapse
If not, the other way is to flash stock firmware using odin.
Once you've flashed stock, root and use triangle away to set it back to zero then unroot by going into SuperSU and choosing "Unroot"
There are loads of threads on here if you get stuck during any steps/
Though you might to leave it before flashing firmware, your warranty is pretty useless.
When you really need to claim then you should go ahead, but until then, there really isn't much use until an update comes out.

Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.

cyanide911 said:
I'm not able to update it via the in build software updater because it says "Your device has been modified. Software updates are not available".
Click to expand...
Click to collapse
I am also little bit curious about it.
I bet it shows that Samsung somehow detected that we have modified device (root,flash, Odin...) - and prevents us from legitime update. But still dont know if I am right - also have the same notification about "modified device" since root.
I hope that in Kies there is somehow to repair device(like Sony Ericsson suite has) and this tool was able to reflash device even with unlocked bootloader

kies.
tools.
firmware upgrade and initialisation.

You must try root your device with stock recovery ery stock kernel stock rom and xposed framework
SYSCOPE MODULE
Sent from my GT-N7100 using xda premium

I experience almost the same thing,. I got my note2 from my service provider,. i had never rooted the phone since its still under warranty, however, there are times when i try to check for an update it warns me that i cant do OTA because my device has been modified. and on the status itself it says modified. Restarting my phone fixes this, the status goes back to "normal". It's just irritating to know that it says its modified although for a fact i know I never did. It's hard enough to resist the itch to root then the phone slaps you in the face making this kind of jokes on me.. looks like its teasing me (because this is the only mobile phone I had that I refused to root/flash for the meantime).. lol

I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
{
"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"
}

Nameless21 said:
Download Samsung kies.
http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP
Connect your note 2 to your pc and open kies.
It will tell you if an update is available.
this will remove all modifications.
This is the legitimate way.
Click to expand...
Click to collapse
Second that. Just finished "clean up"...
---------- Post added at 07:12 PM ---------- Previous post was at 07:08 PM ----------
cyanide911 said:
I'm not able to update via Kies either. So I guess updating via Odin and then resetting the counter is my only possible path left?
I just want a device that can be updated via OTA updates, nothing else. I don't want to root or install any custom ROM or Kernel.
Click to expand...
Click to collapse
I didn't see XXX before. As you're on 4.1.1 you may use CSC changer without root. But definitelly change your CSC (best if you pick CSC for the country where you are). There's a list of CSC's in the forum, search and change. Then reflash ROM via KIES and it'll be clean

It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).

cyanide911 said:
It seems I'm unable to change my CSC. Whatever I try to set it to via the play store CSC changer app, it remains the same (as you can see in the Kies screenshot in my previous post).
Click to expand...
Click to collapse
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium

aspot72 said:
Well... The XXX is Unknown CSC. Go to sammobile.com and try to find firmware for your country. If not available, then try international version (BTU or XEU). Do hard reset and flash with Odin 3.0.4. After flashing do hard reset again and you should be OK.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yeah just downloaded the INU firmware, I'll go ahead with it. One more thing that I noticed in this whole process.
My phone's IMEI behind it's battery is different to the IMEI it displays inside the phone. After some brief googling, it seems it's either improper flashing or maybe an unofficial mainboard installed am I right?

When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.

dr.ketan said:
When there is CSC is XXX even after flashing Full ROM with wipe, there is little chances of EFS messed up. Again as you said your IMEI is different on device setting and on back of device under battery, there are two chances
- Motherboard is changed by unauthorised person but still not illegal way.
- Illegally tempered IMEI.
In case of first option I think flashing ROM with wipe may solve issue and you may get future update, but in case of corrupt EFS, you always need to flash with odin
and in case of last scenario (Tempered IMEI), your device may get banned from service.
Another thing, as per last screen shot if you still have 4.1.1 then you should flash 4.1.2 as soon as possible, otherwise your device may gets bricked anytime without any reason.
Click to expand...
Click to collapse
Okay this is getting extremely strange. I flashed the latest 4.1.2 ROM for INU from Sammobile via ODIN. Everything works well except, well, the phone! I can't make any calls or texts or even receive any. If someone else calls me, my phone rings at their end but nothing happens at my end. Nothing at all. If I try to make any calls it says "Not registered on network".
I tried fiddling around in mobile networks in the settings, but nothing makes it work.
What the hell? I can't help but think this is something related to that IMEI number thing.

Very suggestive of your IMEI get banned.
Can you tell me first 5-7 digit of IMEI you seeing in device setting?
(Don't put full imei on public forum)
If your imei in setting is starting with
00499 then it is generic.
Sent from my GT-N7100 using xda premium

Hmm, I used this patch after rooting and installing busybox:
http://forum.xda-developers.com/showthread.php?t=1918601
And now everything seems to be working fine. And now my device status is back to 'Modified' haha.
So what does all this mean? My IMEI number being different in the phone and behind the phone? And I don't even know what that patch above 'fixed', but it fixed my network issue.
None of the two IMEI numbers above are starting with generic type IMEI...

That's good
I said earlier your imei changed due to unauthorized mobo replacement, samsung ppl replace old imei if they change mobo.
So in that case it is repaired by unauthorized person (which can just cause problem in warranty) but not unofficially.
If still your csc is unknown then flash same rom with CSC tab in odin instead of PDA (which may factory reset, so make backup of your imp data)
Still it remain xxx in kies, then may be efs is corrupted and only previous backup is savior.
Sent from my GT-N7100 using xda premium

your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.

your device has been modified
Hi, I have successfully installed cynogen mod 10.1 nightly. And I again restored my original 4.1.2 but now when I trying to check OTA update it says "your system has been modified, software update is not available. Please please please help me.

Firmware for SM-T807P

Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.

Yes sammobile doesnt have firmware yet for snapdragon version

I just found out this tablet just came out to sprint. Which caused cf auto root to fail. Which could also mean it isn't on Sam mobile yet.

Is this a common thing? Does sammobile rarely get them for the Snapdragon variants?

Not sure, when the tab s wifi one came out there was already roms for them.

BDA_Rival said:
Would anyone happen to know where I can get the firmware for the Sprint variant of the Galaxy tab S 10.5? I have the "Firmware Upgrade Encountered an Error issue" after attempting to root with CF Auto Root. Kies 3 says it doesn't support the tablet, Sammobile doesn't have it and im pretty sure I don't want to contact Samsung quite yet. Thanks in advance.
Click to expand...
Click to collapse
well...since u have already tried the worse thing possible which is to flash a fule meant for an exynos device on a qualcom chipset then u might as well try this suggestion since it cant really make things worse at this point & just MIGHT actually work. Instead of using the our cfautoroot attempt to use the tab pro SM-T525 cfautoroot (link below)...i just saw that someone suggested that in another thread but dont know if u have had chance to try it yet. Also....as @edan1979 suggested chainfire is pretty good about creating new root packages if u can get him the files that he requests. If u do get this thing rooted with the file below then please pos back because i have a few files i need from your device if its not too much trouble...thx in advacnce
http://download.chainfire.eu/393/CF-Root/CF-Auto-Root/CF-Auto-Root-picassolte-picassoltexx-smt525.zip
^TAB 10.1 LTE SM-T525 CFAUTOROOT (same chipset except for screen...just might be the magic fix)
on a related note....i have aso been searching for the new qualcom/carrier branded firmware files & culdnt find them on sammobile either so if someone finds the one for sprint or the att/verizon version (SM-T707) then please let me know.
@DUHAsianSKILLZ
Just to be clear...i saw in the other thread that u said the wifi root method worked so i'm wondering what version of the device do u actually own?
@BDA_Rival
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet

I dont even care about root at this point, id rather have my tablet boot up to the stock OS. And I'd rather not fully brick it.

@THEDEVIOUS1 in the other thread I didn't know he had a sprint LTE tab s. I own a WiFi version of the tab s 10.5 inch. Sorry for any confusion.

THEDEVIOUS1 said:
Thats actually why i suggested trying the other method...at this point your tablet could POTENTIALLY already be bricked & flashing the file i suggested is not only harmless but COULD even bring your tab back from the dead because theres no telling how long it will be before the firmware files are available. Worse case u can return it to sprint & say it failed during an over the air upgrade...i would definitely try the link i added NOT for the root but as an attempt to revive the tablet
Click to expand...
Click to collapse
so i tried this because why not, already went to a service center and they acted like theyve never seen my issue. before i tried this, i had the binary status saying custom and the kox counter said 0. i flashed this, it was successful finally and my knox counter is at 1 which is fine. it tries to boot up unlike before but restarts saying "Could not normal boot" but i atleast see the splash screen. one question i guess i have is what would happen if i flashed the firmware for th the sm-t525? not that im seriously contemplating but if its the closest, chipset wise, would it work? i dont really care about cellular signal and if i brick it, im probably better off calling sprint with a completely bricked tablet that they wouldnt know was once rooted than one that says custom binary and the knox counter set off.

Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also

THEDEVIOUS1 said:
Well at least that's an improvement...the Odin firmware file will most likely NOT flash due to security checks so the only real hope u have right now is to try the 525 cwm or twrp and & see if it will boot into recovery. If it actually works then u could attempt one of their custom roms (would probably remove the boot.mg first) or maybe even cm11 for the tab pro (would have to delete the assert lines in the updater script so it would even flash). U can also try the a qualcom note 3 custom recovery (if they work will probably have resolution issues) or the 10.1 note 2014 ones which has the same chipset and resolution also
Click to expand...
Click to collapse
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?

BDA_Rival said:
do radios matter though? would it brick because im flashing a verizon rom and those use different radios, or would it be better to flash a wifi rom? i dont really care if i have mobile data, i only use wifi. if i flash a 525 twrp, it wouldnt disable odin mode, would it?
Click to expand...
Click to collapse
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username

THEDEVIOUS1 said:
I'm assuming Odin mode & download mode are the same thing so the answer is yes IF it works u would be able to do the key combination and boot directly into recovery from Odin mode...I would NOT flash the radio although it shouldn't harm anything but what we really want right now is to leave as much of the original file system in place as possible & the only thing that technically should be different at this point is the recovery partition. The wifi versions are exynos devices so NO do NOT flash those because that's how we ended up here in the first place...just follow my last reply & since I don't like to waste posts if u respond needing more help just check back here for a mention of your username
Click to expand...
Click to collapse
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Edit: Got into recovery by holding home button, volume up button, and power but it says "Recovery booting, Recovery is not SEANDROID ENFORCING", not too sure what that means. heres the weird part. after it shows that, the screen starts turning gold within a matter of 15 seconds.
{
"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"
}
Ever seen that before?

BDA_Rival said:
so im not sure i understood the last part of your message about wasting posts but i figured youd want to hear this. So i download the TWRP for the SM-P905 (note pro 12.2) and after i flashed it through odin, the tablet restarted and booted all the way up. I dont get how the hell this worked but flashing TWRP fixed my OS not booting. I also went to settings to check my device status and it says custom. i want to install super su but i dont know if TWRP stuck for sure or not and i cant get TWRP to boot, it keeps taking me to download mode. any ideas? id like to make a back up in case something dumb happens.
Click to expand...
Click to collapse
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
@BDA_Rival
U edited your post before I could finish my reply but long story short just leave recovery alone for right now...what u are seeing is most likely due to the different types of screens between the 12.2 & 10.5 so the display driver is causing that problem. No problem on the assistance...that's were all supposed to be here for
Just thought I'd throw this out there since u seem to be able to find your way back home now but maybe if u try the cfautoroot for the P905 12.2 note pro then MAYBE that will root it...just thinking out loud though
http://forum.xda-developers.com/showthread.php?t=1980683&page=24
^NOTE PRO 12.2 LTE P905 CFAUTOROOT (see post #235...just in case u get the guts to try it again good luck)

THEDEVIOUS1 said:
Sorry but the last part wasn't that serious...I just don't like to run my post count up. ok...that's great news which confirms what I thought since all the cf root really does is flash an altered stock recovery, install root then flash stock back. So...what I would try at this point is to go ahead & install supersu & hope that it detects the su file (it technically should) & if/when it requests u to upgrade the file choose NORMAL method NOT twrp/cwm which will attempt to finalize the root WITHOUT needing to boot into twrp. I would try to avoid that because even if it stuck there may be problems with the fact that it is from another device and will potentially screw the partitions up worse.....I know this is not the best bet for a backup but I would avoid recovery until u can find the proper Sprint Odin firmware for your device & instead just useb titanium to backup up your apps, system settings, & whatever else u can with it for the time being. At this point I would just be satisfied with the fact that u now have a working device & wait to do anything further until u get the correct software to fully fix it...well I'm glad u were able to get it going and IF u in fact have real root then can i get a HUGE favor? I need the keyguard.apk as well the framework-res.apk & twframework-res.apk with the corresponding odex files of course (i wouldn't mind having systemui & both framework jars if possible also)...if u can't do it , don't know how or it's just too much trouble then don't worry about it but i just thought I'd ask since I've been trying to find snap versions these files
Click to expand...
Click to collapse
so i tried root checker, it said no root, i tried installing super su, said no root as well. i guess even though my device status says custom, im not actually rooted i went ahead and tried that CF Autoroot you suggested earlier in Odin and it gave me a boot loop so i flashed TWRP again and now its booting all the way. still says im not rooted so i just dont think its gonna work. If it did, i would have gotten that stuff for you for all your help. thanks for helping out.

About those root files

Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell..maybe kernel wizards like @arter97 would like to take a look at them and see if he can find something useful
Any questions feel free to ask

Sunderwear said:
Hello. I'm just making this post to clear up some things and rumors about the posts going around about root firmware etc for newer ATT Galaxy phones like the s6, s6 edge, s6 edge + and the Note 5...
First of all these files have been around for some time now and only very few people in the unlocking/imei repair scene had them (including me) and just a few days ago someone decided to leak them and well they are now being offered for sale etc etc...Anyways these are what is called "engineering" kernel boot images with insecure adbd enabled meaning that it gives you root shell access.
Now the software that we use for our "unlocking" purposes only require this access to perform the operations that we want. However with all the new security Samsung has implemented, these kernels are by no means full root options. For example trying to use apps that require root (Titanium, Root checker) won't work and updating the SU binary under supersu app will send the phone on a bootloop because of SELINUX etc etc and as you know the only way to get around that is by flashing a custom kernel but ATT models having a locked bootloader this is not an option.
TL,DR : These files will only grant you "half assed" root that most people won't be able to take advantage of because it is all run over adb shell.
Any questions feel free to ask
Click to expand...
Click to collapse
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?

all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0

ohap said:
all root files https://www.dropbox.com/s/gkxk32f778odlxu/AT&T_Root_Files.rar?dl=0
Click to expand...
Click to collapse
how can we use that boot img with is associated with the N920AUCE2APB2 firmware, which no one has.
edit: turns out that the N920AUCE2APB2 firmware is based on the MashMallow (6.0.1) link below for proof . so i guess it wouldn't work on 5.1.1
img link
http://www.phone-probe.com/wp-conte...63_10205787832278168_2060735319_n-169x300.jpg

Would it be possible to use the ENG kernel to manually install the superuser binary and push the superuser apk to system? Or would that cause the same bootloops also?

We need a working recovery odin file first.

jellybear456 said:
Very informative, pretty much everything I needed to know. If you can't use root apps then I'm sure a lot of users will disregard the files, myself included as I only would like to use said apps. Thanks for the info?
Click to expand...
Click to collapse
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both.
{
"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"
}
Sent from my Nexus 6P using XDA-Developers mobile app

Michael3214 said:
As not much has been said in the thread, yes after Odin flashing the ENG kernel for our device and flashing a root script we can use rooted apps. @metalcated posted a script that does push SuperSU into system/. This was originally posted in the atat GS6 forum. It's a potentially complicated process and if your phone shuts off, battery dies or you hard reboot you will be stuck in a bootloop, hotbooting works fine for Xposed. Will this method be practical for everyone probably not, but considering we were told the device was unrootable........
Read thru his thread, then read it again, seriously do this. And if you still want to try, backup everything you can just in case you need to reflash via Odin to recover from a bootloop. Here were my steps.
1.Updated to newest firmware @Sunderwear posted PB2 (BL/AP/CP/CSC) this will wipe your device. In the pics provided I did try a couple firmware combinations after flashing PB2. I wouldn't suggest this but to each their own.
2.Metalcateds thread is here:
http://forum.xda-developers.com/att-galaxy-s6/general/root-5-1-1-qa-oj7-root-snag-t3334546
3. The only file I downloaded and used was this one:
https://www.androidfilehost.com/?fid=24438995911977129
(G920a5.1.1.root.metalcated-v4.zip)
4.Save it and extract it on your PC
5. Verify Samsung drivers and adb are installed
6.***ENABLE USB DEBUGGING*** this is an important step.
7. Plug device into PC open file and run root script. It'll prompt you to press enter a couple of times and reboot the phone. Just follow the on-screen instructions.
8. After it reboots you have root access.
Root apps that work for me: Titanium backup/root explorer/build.prop editor/no frills.
I was able to delete all Knox apps and debloat the heck of the stock ROM. At no point did my device freeze, reboot on its own.
None of this is my work, I just figured out how to get it going on our device. If you want to try it out and your successful thank @metalcated and everyone listed in the thread as they did all the work..
A couple people reported their Knox warranty tripped to 1. So i felt I needed to check if this tripped my own Knox counter. So I'm bootlooped for now but my Knox is 0 !!!! @TechNyne66 and @jrtran I'm posting the instructions on how to do this if you decide to try this method I originally pm'd to you both. View attachment 3705507
View attachment 3705513View attachment 3705514View attachment 3705515
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Wow that's great information and great news. Thanks! I'm going to give this all a few reads and possibly give it a shot. I'll be sure to inform anyone if I try it and have success. A long process, but I don't mind if I can successfully gain root access and use root apps that may make my battery life a bit better. Thanks again!

@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks

If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.

I'm sure somebody much smarter than me has tried already, but could we push a script to set SELinux to permissive upon boot?
http://forum.xda-developers.com/ver...ipt-permissive-selinux-stock-kernels-t2854364

XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Without access to a pc its a bad spot to be caught in. I ran the "root-Boot.cmd" to recover from the bootloop. The phone hangs on the splash screen for 45 seconds then finishes booting back into android.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
---------- Post added 4th April 2016 at 12:05 AM ---------- Previous post was 3rd April 2016 at 11:57 PM ----------
jrtran said:
@Michael3214 I tried and it works good on G920A, G925A, G928A and N920A. If you have stock firmware for N920A (PB2), please post it. Thanks
Click to expand...
Click to collapse
Here's the link to the firmware.
http://forum.xda-developers.com/showthread.php?t=3331843
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app

I have OGG firmware restore and can try different methods if needed. I've tried a few with no success. But am able to recover from bad flashes. Willing to test anything that doesn't flash recovery or kernel.

XRange said:
If it goes in boot loop. Do u think it's really worth the effort. Personally I think it needs little more work. Least it's going in right direction. Maybe they get boot loop fixed. Even if it trips Knox it . That be fine with me.
Rocking Samsung Galaxy Universal Park Themes.
Click to expand...
Click to collapse
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?

2Tone23 said:
Excuse my ignorance if this strikes anyone as a noob question... If my device bootloops I obviously cannot go into download mode... My question is twofold: 1: Is my only recourse to flash firmware via Odin?.. And if so... 2: Will my computer/Odin recognize my phone while it is in bootloop?
Click to expand...
Click to collapse
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.

TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?

can we use this just to debloat and be good?

blane3298 said:
can we use this just to debloat and be good?
Click to expand...
Click to collapse
Yes about all root is good for anyways.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
jellybear456 said:
And this works if you're caught in a bootloop, correct? Also, the I have the files for AOJ1 not APB2. there shouldn't be an issue restoring through odin from APB2 to the older AOJ1 because it's still lollipop, right?
Click to expand...
Click to collapse
Doesn't matter just don't downgrade firmware or flash anything but AP in odin.

have you tried this yet?

TechNyne66 said:
Hold volume up and down + power + home tell your phone resets, then volume down + power + home to boot download mode.
Click to expand...
Click to collapse
Thanks for your response... I just want to be clear, while in bootloop I can put my phone into download mode by the usual means?