Related
I'm confused now. So I bought this phone used it, rooted it, used da_g's kernel, flashed the UCLA modem and used stockmod rom. now i need to get it back to stock.
i removed the sd card, then did the ODIN instructions and went into download mode and flashed it 'back to stock.' after reboot all my stuff is still on there; so i went into privacy and formatted erased everything. rebooted now i'm at my screen and i went to about, android version 2.3.5, baseband version i727ucla3, kernel 2.6.35.11, build number GINGERBREAD.UCKJ2.
why is my baseband version still at ucla3? i thought flashing the ODIN stock it would set everything back to stock. basically i want to give this to a family member but i want it in the condition that it truly is stock and they can run updates just fine. i ran the 'software update' to try to get the OTA for 2.3.6 but it said 'Current software is up to date' -- isn't the newest 2.3.6.. is my baseband preventing the update. is my kernel back to stock? can i ODIN 2.3.6 stock straight to the device?
also why cant i get back into the 'download mode' i saw previously, all i get when i hold vol up and down is an 'android recovery 3e' what is that.. if i can't get download mode how can i ODIN? im thinking i need to CWM this guy to flash the old baseband then do the process over again to get stock rom and stock kernel... help!
thanks in advance.
Download 'root check free' and see what it says. Also make sure the superuser app is uninstalled
haroonie said:
I'm confused now. So I bought this phone used it, rooted it, used da_g's kernel, flashed the UCLA modem and used stockmod rom. now i need to get it back to stock.
i removed the sd card, then did the ODIN instructions and went into download mode and flashed it 'back to stock.' after reboot all my stuff is still on there; so i went into privacy and formatted erased everything. rebooted now i'm at my screen and i went to about, android version 2.3.5, baseband version i727ucla3, kernel 2.6.35.11, build number GINGERBREAD.UCKJ2.
why is my baseband version still at ucla3? i thought flashing the ODIN stock it would set everything back to stock. basically i want to give this to a family member but i want it in the condition that it truly is stock and they can run updates just fine. i ran the 'software update' to try to get the OTA for 2.3.6 but it said 'Current software is up to date' -- isn't the newest 2.3.6.. is my baseband preventing the update. is my kernel back to stock? can i ODIN 2.3.6 stock straight to the device?
also why cant i get back into the 'download mode' i saw previously, all i get when i hold vol up and down is an 'android recovery 3e' what is that.. if i can't get download mode how can i ODIN? im thinking i need to CWM this guy to flash the old baseband then do the process over again to get stock rom and stock kernel... help!
thanks in advance.
Click to expand...
Click to collapse
My best advice for you is to do more reading before you really mess something up. If you don't know the difference between 3e recovery -vs- CWM you haven't read nearly enough to do what you want to do. I am not telling you this to be a smart-a*s, but because I don't want to see you brick your phone. And, almost everyhting you have asked has been discussed in detail.
The modem / radio (baseband) lives on its own little partician so you will probably need to flash the radio you want by itself (while you still have CWM). You can find the different radio zips in the "Radio" thread in the "Dev" section.
But you will first need CWM back. You will need to be rooted to have CWM and you can get CWM (after root) by using ROM manager to download it or you can ODIN CWM if you use Copperhed's root method.
Once you are rooted and have CWM installed, you can flash whichever modem / radio you want. Then, go to K0nane's "Return to stock" thread and follow the directions completely! Read the entire thread first...JUST DO IT!
Once you are back to stock and have the modem you want, use ODIN to install the 3e recovery (original Samsung revovery) back to your phone. There is a thread that has the 3e recovery .TAR but you will have to do a search to find it.
THEN...you will be back to stock. Of course the AT&T 2.3.6 updates have been pulled (again, discussed in many threads) so you probably won't get the OTA update anyway. But it won't hurt to check. Again, read everything before you do anything and if you still have questions after reading everything...ask before you jump.
Good luck.
android recovery 3e is recovery mode. Holding the volume keys + power button is how you get into recovery, not download mode. To get into download mode:
1 - power off the phone.
2 - plug in your USB cable into your computer/laptop (but not the phone yet)
3 - now hold down the volume keys and plug in the usb cable to the phone while still holding down the volume keys. The phone will vibrate and you can release the volume keys once you see that you're in download mode. I can't remember, but it might actually just be the volume down key and not both.
If that still doesnt work, try taking out the battery and then reinserting it after you power off the phone. Then try again.
scott14719 said:
My best advice for you is to do more reading before you really mess something up.
Click to expand...
Click to collapse
m4570d0n said:
android recovery 3e is recovery mode. Holding the volume keys + power button is how you get into recovery, not download mode. To get into download mode:
Click to expand...
Click to collapse
Thanks for the help, very informative and you basically confirmed what i was thinking. i come from the iOS world where the firmware files when restored it was back to stock, contained the os/modem fw and kernel; plus wiped everything so that just added to the confusion!
so here's how i think it works - your post says the modem, kernel, OS & recovery all live on separate partitions and since some aren't contained in K0nane's stock ODIN; i need to be sure to flash each to be considered "fully stock." if you do K0nane's stock ODIN (does not contain modem, but has orig 3e recovery, kernel, OS) and it is incompatible with the existing modem; you could be in deep sh*t or a brick. also if you flash stock ODIN, you loose the ability to flash kernel or modem because you're now unrooted and without cwm to do that...
two questions - where in android can i see if i'm truly on stock kernel because can't the build string be spoofed? if i restore my cwm backup from post-root-stock state, does that restore / contain modem or kernel?
TIA again.
haroonie said:
Thanks for the help, very informative and you basically confirmed what i was thinking. i come from the iOS world where the firmware files when restored it was back to stock, contained the os/modem fw and kernel; plus wiped everything so that just added to the confusion!
so here's how i think it works - your post says the modem, kernel, OS & recovery all live on separate partitions and since some aren't contained in K0nane's stock ODIN; i need to be sure to flash each to be considered "fully stock." if you do K0nane's stock ODIN (does not contain modem, but has orig 3e recovery, kernel, OS) and it is incompatible with the existing modem; you could be in deep sh*t or a brick. also if you flash stock ODIN, you loose the ability to flash kernel or modem because you're now unrooted and without cwm to do that...
two questions - where in android can i see if i'm truly on stock kernel because can't the build string be spoofed? if i restore my cwm backup from post-root-stock state, does that restore / contain modem or kernel?
TIA again.
Click to expand...
Click to collapse
OK, I see K0nane's thread has the .TAR stock (Odin flash) and apparently already has the 3e recovery included so if you use K0nane's .TAR, you should not have to re-root or install CWM after the flash. So the only reason you would need to re-root and install CWM is if the modem still remains unchanged.
If the modem (radio) is still wrong after the "return to stock .TAR Odin flash, you will need to do what I wrote above (ie. re-root and install CWM) then flash the correct radio through CWM, then re-odin the return to stock .TAR. Others have reported that they were able to get the OTA update (when it was available) using this method. Maybe a .TAR (ODIN flashable modem) exists, but I'm not sure if I've read anything about anyone trying it if it does. If it does, and it works, you can use ODIN to flash the radio as well.
Yes, the modem itself does live on a different partician. Some custom ROMS include the modem and a script for installing it, but usually mention this up front. If the modem doesn't change after a ROM flash, it must be flashed seperately. I've never seen a phone bricked because of a modem mismatch with a ROM (as long as it is an AT&T (I727) skyrocket ROM and modem). But there may be issues with lost data connectivity or APNs.
But you are on the right path, just make sure you read everything and you will be fine.
As far as spoofing the build, I guess the only way to be sure if it is 100% stock is if you restore a nandroid (if you made one) and then ODIN 3e recovery. Or if you use Kies to reurn to stock.
scott14719 said:
But you are on the right path, just make sure you read everything and you will be fine.
As far as spoofing the build, I guess the only way to be sure if it is 100% stock is if you restore a nandroid (if you made one) and then ODIN 3e recovery. Or if you use Kies to reurn to stock.
Click to expand...
Click to collapse
Thanks for the details man, really appreciate it. I read through the threads you suggested and they helped, but no mention of modem. After my initial k0nane stock flash, modem was incorrect so i did the below steps and everything looks good. Still no OTA, but thats fine because it may be because of other reasons (2.3.6 pulled).
You mentioned 100% stock if i have my nandroid, but i would still have to 'un-root' my device afterwards. (i could then just goto settings > privacy > factory data reset would delete everything including the root then?) i am under the impression you needed to be rooted to create a nandroid so you would be restoring to the rooted state. is it true if you restore a nandroid you restore all partitions including the modem and kernel then?
Here's how i finally went back to stock when my device was not rooted but had a different modem.
0. DO NOT ODIN WITH RE-PARTITION OPTION ON, UN-CHECK THIS!
1. re-rooted with superoneclick SuperOneClickv2.3.3-ShortFuse.zip
2. odin to enable cwm SkyrocketCWMrecovery.tar
3. use cwm to flash modem to stock ATTKJ2 Radio_RIL__I727ATTKJ2.zip
4. use cwm to wipe data/factory reset
5. odin k0nane's stock SGH-I727-UCKJ2-k0nane.tar
6. verify in about section modem, kernel and software versions.
7. Voila!
Hello everybody. This is my second post and obviously I'm a noob. I own the Samsung Galaxy R I9103 and would love to root it. I have been researching the probable options for the last few days and here's what I have come up with. I really need help in deciding which way to go about rooting my phone.
Option 1. The hard old way - Flashing the Superuser.zip package through ODIN PDA
http://androidadvices.com/root-samsung-galaxy-i9103-tutorial/
The rooting package included in this method probably also includes the CWM(ClockworkMod) recoveryconfused
A simpler explanation of this old school method will be much appreciated.
I'm a bit skeptical about this method as this method probably comes with the famous yellow triangle and I really don't know how to get rid of it.(enlighten me).
Option 2. Flash CWM through ODIN --> Backup through CWM --> Flash Superuser.zip through CWM
http://forum.xda-developers.com/showthread.php?t=1406880
Are the ODIN, CWM and Superuser packages mentioned in this method the latest ones for the Galaxy R or are there new ones available?
Are there any complications that might arise by using this method(known issues?)?
Option 3: Flashing CWM through ODIN --> Flashing a rooted custom kernel through CWM
http://forum.xda-developers.com/showthread.php?t=1418895
Here the dev has been generous in providing 2 options: 1. Zip package Flashabe through CWM recovery
2. ODIN flashable package.
Which one should I go for?
This kernel provides OverClocking options. Is OC only available through custom kernels or can SetCPU help in overclocking if I go for option 2? If I go for option 2 to root my phone will I be able to later flash a custom rooted ROM like the one above without any complications?
Okay, here are a few important questions:
Option 1 seems tedious, so probably ruled out. I'm confused between option 2 and 3. What is the best, easiest and safest(data loss) way to go about?
Will any of the above methods wipe out the phone storage contacts, notes, settings, apps etc? Please provide a few tips about backup as well(Stock ROM or kernel backup through CWM? for later restoration). Any suggestions will be really helpful..TIA
option 1 doesn't exist!!!!!
There's no way to flash zips via Odin, only tar /tar.md5
The best way is to flash CWM via Odin (doesn't increase download counter) and then flash superuser.zip via CWM. So I guess option nr 2. It's the safest!
If you flash custom kernel via Odin, you'll get yellow triangle and your download counter will increase. Via CWM you can flash anything without that risk. Rooting won't cause your data/settings loss. The only way to create a backup of your system, data, cache is nandroid backup on CWM.
Never mind...
E107946 said:
Never mind...
Click to expand...
Click to collapse
Download Counter is Samsung's technique to keep a check on the number of times custom firmware had been flashed on the phone.
But there's a work around & it can be reset before giving to Samsung to service center for warranty claims.
Hope this helps.
I have a Samsung Galaxy Tab 2 7.0 (US Wifi+IR) P3113 [ROM Build Number: IMM76D.P3113UEBLH2] which is still 100% stock. I plan on installing a custom rom, but first I want to make a complete backup of everything.
I know I need to use a custom recovery (I plan on using ClockworkMod) and flash the custom rom. I don't have any problems with that part.
I also have all of my data already backed up. I plan on doing a full factory reset before installing anything anyway.
My main issue is that I want to backup the original stock ROM and all other partitions/images before making any permanent changes.
Since the device doesn't support fastboot I can't just "fastboot boot cwm-recovery.img" to do a temporary boot to backup the stock rom and recovery. All the instructions I've seen indicate I must first flash a new recovery image then boot the device from that. This would cause me to not have a backup of the stock recovery image.
I didn't see any backup options in Heimdall or ODIN either. No luck with Check Fus either.
Is there a way to backup the stock recovery image without flashing anything to the device first?
I have looked at sammobile at the P3113 firmwares, but I can't be sure those apply to my version (US WiFi + *IR blaster*) or would have the stock recovery image. Samsung Kies doesn't seem to have any updates or downloadable firmware for my tablet (it still has the ROM it came with out of the box) that I could extract the stock recovery for my P3113 (US WiFi+IR) from either.
I'd like a backup of everything so I could revert to 100% stock if needed. I also want to be sure I have the original recovery image and not some other version from a "stock rom" downloaded from the Internet.
rbeede said:
I have a Samsung Galaxy Tab 2 7.0 (US Wifi+IR) P3113 [ROM Build Number: IMM76D.P3113UEBLH2] which is still 100% stock. I plan on installing a custom rom, but first I want to make a complete backup of everything.
I know I need to use a custom recovery (I plan on using ClockworkMod) and flash the custom rom. I don't have any problems with that part.
I also have all of my data already backed up. I plan on doing a full factory reset before installing anything anyway.
My main issue is that I want to backup the original stock ROM and all other partitions/images before making any permanent changes.
Since the device doesn't support fastboot I can't just "fastboot boot cwm-recovery.img" to do a temporary boot to backup the stock rom and recovery. All the instructions I've seen indicate I must first flash a new recovery image then boot the device from that. This would cause me to not have a backup of the stock recovery image.
I didn't see any backup options in Heimdall or ODIN either. No luck with Check Fus either.
Is there a way to backup the stock recovery image without flashing anything to the device first?
I have looked at sammobile at the P3113 firmwares, but I can't be sure those apply to my version (US WiFi + *IR blaster*) or would have the stock recovery image. Samsung Kies doesn't seem to have any updates or downloadable firmware for my tablet (it still has the ROM it came with out of the box) that I could extract the stock recovery for my P3113 (US WiFi+IR) from either.
I'd like a backup of everything so I could revert to 100% stock if needed. I also want to be sure I have the original recovery image and not some other version from a "stock rom" downloaded from the Internet.
Click to expand...
Click to collapse
Excellent way of articulating the issues and questions rbeede.
This is exactly what I have been trying to do too. I have searched the forums and google and haven't been able to figure out how to do this either. I was actually fixing to post the same questions myself and thought I should do one last search before I did, which lead me to this thread
I have the same tab and build (P3113 - ROM Build Number: IMM76D.P3113UEBLH2). As an android newbie I have been reading/researching for hours a day since Christmas and there is still a lot I don't understand. This is the first step I would like to take though and I intend on doing a full factory reset before installing anything too.
Can anyone help us with this please?
A. Want to backup the original stock ROM and all other partitions/images before making any permanent changes. Would like a backup of everything so I can revert to 100% stock.
B. For the same reasons as the OP, I also want to be sure I have the original recovery image and not some other version from a "stock rom" downloaded from the Internet.
I am happy to show proper appreciation for anyone who can help and once I get things sorted out and figured out I am willing to help others too. Thank you in advance
Backup
Howdy
You should find and download the stock rom for your device on the net. I myself do not recommend you to install custom rom as it can brick ur device.
For the backup:-
1. For the backup of your apps download this app (App Backup and Restore) from the play store. It can backup ur apps and then can also restore them back but also dont forget to take the backup of this app itself.
2. Connect your tablet/phone to your pc/laptop and then copy all the files in your SD card and Device and store them to seperate folders on your pc/laptop.
3. Now the backup of all your files is created.
According to my information you cannot backup your current rom you will have to download the stock rom from the net which you need and then fla**** in case of a mishappening or incase you wish to revert back.
Best of luck Happy flashing and a happy new year.
Sent from my GT-P3100 using xda app-developers app
@kunalthakur - There isn't an official Samsung download source that one can use. Most of the other downloads I've seen have had the recovery.img modified to enable the backup in the first place. We want a trustworthy (verified no malicious software added) stock OEM rom/recovery with no modifications.
I have had some initial success getting the Samsung Kies software to attempt to download the current official ROM from official Samsung servers. I guess Samsung wants people to only download via Kies instead of offering it on their website to reduce the load on their servers and prevent end-users from flashing the wrong ROM because they didn't know what they were doing.
I will update if I have success getting a clean download.
If u are successful in flashing the original rom then notify me too as i dnt know of any such method. Oh by the way here is a site where you can download original roms.
downloadandroidrom.com
And by original I dont mean official.
Sent from my GT-P3100
That site didn't have a ROM for the US (Wifi+IR) GT-P3113
I did however notice that an official ROM update has just become available in Samsung Kies.
Version ending in LK7 (update from LH2).
I'm going to try to save a copy of the download for backup purposes.
rbeede said:
That site didn't have a ROM for the US (Wifi+IR) GT-P3113
I did however notice that an official ROM update has just become available in Samsung Kies.
Version ending in LK7 (update from LH2).
I'm going to try to save a copy of the download for backup purposes.
Click to expand...
Click to collapse
I did not say that it had a rom for every device
Sent from my GT-P3100
Hello,
I'm using Galaxy Note 10.1 (N8013, UEALI3).
As our hardware and software are almost identical, I'll assume things will be the same for you and me.
How to create a full backup of your device, without touching anything?
There must be a way, but I also couldn't find it.
So, I found a way that just works as we expect.
To create a full stock device backup, with all images and partitions, without rooting, you'll have to....
Flash CWM! No, please, wait, let me finish...
When you flash a custom Recovery, it is actually not something permanent.
Once you boot your stock rom with stock kernel, your custom recovery is overwritten with the default one.
So, you can flash your CWM, and reboot your device immediately to it.
If you let your stock ROM boots, you are going back to stock recovery.
EXCEPTION:
- When you boot to CWM, choose "Reboot", you'll be given the following option: "ROM may flash stock recovery on boot. Fix? This can not be undone.". If you choose "Yes", you'll never get to stock again, even while booting stock rom.
So, flashing a custom recovery is actually very similar to "fastboot boot recovery recovery.img", as no permanent damages are made.
Finally, that's what you'll have to do:
1) Use Oding to Flash CWM. DO NOT Restart your device from ODIN.
2) Force turn off your device (press power button for > 8 seconds)
3) Boot to recovery (power button + volume up)
4) Make a full backup! In this backup, you'll have the CWM recovery.
5) Reboot your device.
6) Boot normally, and copy your backup from SDCard to your computer.
How to restore the stock I just saved?
1) Flash CWM again if needed.
1.1) If you want to get rid of the binary count, you'll have to make CWM permanent.. for a while.
1.2) Boot into CWM, go to Reboot Device, and choose "Yes - Make it permanent".
1.3) Boot your rooted ROM, download and execute TriangleAway.
1.4) Ok, your download count is zero.2) Now, go back to CWM and restore your backup.
3) This time, you have your stock rom + stock kernel, but still have the CWM recovery.
4) Boot your stock rom
5) Now, you have your stock rom + stock kernel + stock recovery.
I know this is not what you REALLY wanted (extract stock images, including stock recovery image), I wanted that to..
But this just works.
Let me know if I was able to help you.
Good luck!
So this is basically not possible then?
EASY... relatively speaking.
I read XDA forums for hours and hours... and hours. Seriously. I spent about 20 hours reading XDA just for this. All the info is out there, but it is spread out across a dozen different threads, and multiple posts within those threads.
When I actually went through the process, I had (no lie) eighteen windows open, each with a relevant thread/post.
Sheesh, and people think this is complicated... [/s]
But in the end - I have a custom Lollipop ROM on my phone (Goldeneye v53) and it is working beautifully. And I had NO issues with the process, it all went smoothly.
The phone (which previously was starting to run out of space, lag, and just all-around felt "old") is now like new. And, dare I say... better than a stock S6? It is certainly leaner and meaner than a stock system (that's a good thing - I despise all the bloat on stock systems)
So, to make it easier for all those who come behind me, here is how to do it. In 39 easy steps.
One post.
One list.
Bullet points.
Links.
EASY.
Do this EXACTLY - and you will have a custom ROM on your S4.
Do something "just a little" different... Or miss a step... I'm pretty sure your device will explode, or at least catch on fire.
Either way, there is no express or implied warranty on this process I have collected and posted here. Anything you choose to do to your device is on you, and if something goes wrong, I accept no liability.
For risk mitigation in my case (as I'm an overly anal type) - I made sure that I dug my previous phone out of the closet, charged the battery, installed my SIM, and confirmed that I could use the old phone to at least make calls/texts in the event that "something" happened to my S4 during the upgrade process and I had to go to work the next day without my S4. Everything went smoothly, but IMO you should definitely have a contingency plan just in case.
Note - this is only for those NOT on MDB or MDL bootloaders. You guys have it easy. Don't do all the crap below - you don't need to, and if you DO do it, you are locked into this "complicated" method FOREVER (mwa-ha-haaa!!!)
1. Preparation
1.1 READ THROUGH THIS POST 27 TIMES (NO LESS, NO MORE) AND MAKE SURE YOU "GET IT". IF NECESSARY, READ THE THREADS LINKED THROUGHOUT THIS POST. <<< THIS IS THE SINGLE MOST IMPORTANT PART OF THE PROCESS. IF YOU JUST READ THE FIRST FEW STEPS AND START FLASHING CRAP, YOU ARE GOING TO F SOMETHING UP. READ IT ALL, UNDERSTAND IT, THEN DO IT. I CAN'T EMPHASIZE THIS ENOUGH.
1.2 Backup. Back your stuff up. Back it all up - ALL of it. Understand that whatever you do not back up now, YOU WILL LOSE. This process is going to wipe your device clean. Anything you want to save, you need to back it up now.
1.2.1 Do not use Titanium Backup - for anything. It will F your stuff up. Which is unfortunate, because TB is a great app that is incredibly useful - just not this time. Apparently TB has issues when migrating form one version of Android to another (i.e. 4.x.x to 5.x.x). Sorry, but you gotta do it manually.
1.2.2 Copy your pics/vids to your PC
1.2.3 Use "SMS Backup& Restore" from the Play store
1.2.4 Let Google sync your contacts and calendar.
1.2.5 Any apps that store your data locally (not sync'd to their server) - manually find it (I like ES File Explorer) and copy it to your PC if you care about it.
All of that said - I found that wiping my device and migrating to Lollipop was a GREAT way to clean a bunch of useless crap I no longer needed off of my phone.
2. Rooting and Flashing STOCK KitKat (4.4.2) ROM (relevant thread - see post #2, under the "NB1 - KitKat 4.4.2 > Option 2" section.
Note: The reason you have to do this is because you must have rooted Lollipop on your device in order to flash custom Lollipop ROMS. If you just want stock, non-rooted Lollipop maybe you COULD just use Odin to flash Lollipop directly? But there is no way to get root on Lollipop directly - and you must be rooted if you want to wind up with a custom ROM. So you have to do this intermediate step of flashing and rooting a 4.4.x or higher OS. This version of NB1 is easiest because you can use Odin to flash a ROOTABLE ROM which makes the root process simple with Towelroot.
2.1 Download Odin v3.09 here. Place on PC.
2.2 Download ROOTABLE NB1 ROM here. Place on PC.
2.3 Download towelroot v3 here. Place on PC and copy to device (likely your SD card).
2.4 Use Odin to flash ROOTABLE NB1 ROM to your device. When the phone boots up, just speed through the "initial setup" screens, it doesn't matter since you're going to install a couple more ROMs before the finished product.
2.5 Go to settings>more>security and check "unknown apps", and uncheck "verify sources".
2.5 Navigate to towelroot v3, and install it.
2.6 Open towelroot and click the "make it rain" button.
Congrats, you are now rooted on KitKat NB1.
3. Upgrading to ROOTED STOCK OC3 (Lollipop) using "keep root" method (relevant thread)
As mentioned, this process takes you from ROOTED NB1 (KitKat, 4.4.x) to OC3 (Lollipop, 5.x.x). The only way to get rooted OC3 is to first get root in any 4.4.x version or higher and then upgrade to OC3 using the "keep root" method. There is (as of this writing) no way to root OC3 Lollipop directly. "keep root" reference thread - post #1
3.1 Download Flashfire app using below steps. (no direct link available).
3.1.1 Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
3.1.2 Sign up to receive the BETA versions from Play Here.
3.1.3 Use the link provided after sign-up to download the app. Note - the link was not immediately available for me, and apparently that is normal. (There was a link, but it told me something like "link not found" when I tried to access it at first.) I had to sign up, and then 30 minutes later I went back and had access to the Flashfire file.
3.2 Download I337_OC3_Stock_Rooted_ROM here.
3.3 Place ROM on SD card.
3.4 Use Flashfire to flash ROM (see "keep root" reference thread from above for specific details of using Flashfire)
Congrats, you are now on rooted (stock) Lollipop.
4. Install your CUSTOM Lollipop ROM
4.1 Download ROM and prepare Safestrap recovery
4.1.1 Download your chosen ROM. I chose Goldeneye v53 here. (I chose Goldeneye because after brief reading, Goldeneye seemed to be one of the more stable options, and stability is what I wanted when going through this the first time.) Place it on your SD card. Here are other options for Lollipop custom ROMs on AT&T GS4. If you happen to wander into the development section and see all the shiny, new, intriguing ROMs floating around, keep in mind that most of them won't work for the AT&T GS4. Any custom ROM on this device must be based on Touchwiz and setup to be compatible with safestrap - only a handful meet those criteria.
4.1.2 Download Safestrap v3.75 here. Place it on your SD card. Do not install it at this point, Safestrap is currently not compatible with Lollipop - you are going to flash a different Kernel in Step 4.2 to work around this.
4.1.3 Download BusyBox from Play store
4.1.4 Install BusyBox on your device.
4.1.5 Install Safestap 3.75
4.1.6 Open Safestrap
4.1.7 I did not do this step because I did not start this process with any previous version of SS on my phone. But if you did have a previous SS recovery installed, use the Safestrap to "uninstall" the previous recovery version. It is my understanding that you can't install v3.75 on top of another version, you need to first remove the old version before installing the new version. The "uninstall" option is done from within the SS app, not the Android application manager - you are uninstalling the custom recovery, not the SS app.
4.1.8 "Install Recovery" (from within Safestrap). NOTE: this only INSTALLS safestrap, it does not boot you into safestrap recovery. There is no need to go into safestrap recovery yet. That's later.
4.2 Flash NC1 Kernel
As mentioned above, you need to flash the NC1 Kernel so that you can do your thing in Safestrap. But then you MUST remember to reflash the OC3 Kernel after using Safestrap to install the ROM, or else your phone will explode (probably).
4.2.1 Download NC1 flasher app from here. Place it on your SD card.
4.2.2 Download I337_stock_OC3_kernel_recovery_flashable from here. Place it on your SD card.
4.2.3 Download OC3 modules from here. Place it on your SD card.
4.2.4 Open NC1 flasher app and press "flash" (it's the only button)
4.2.5 Wait for completion and press reboot. NOW you will get automatically rebooted into safestrap recovery.
4.3 Install your custom ROM!!!
(note: all the below is done in safestrap recovery)
4.3.1 Go to "Wipe" and perform factory reset (will wipe system data, cache, and dalvik)
4.3.2 Flash your ROM. For Goldeneye ROM, it uses the AROMA installer. Choose the options that you like, but make sure to READ THEM ALL BEFORE SELECTING ANYTHING - IF ONE OF THE OPTIONS MENTIONS AT&T/SAFESTRAP, YOU MUST CHOOSE THAT OPTION. HELLFIRE, BRIMSTONE, AND ETERNAL DAMNATION WILL AWAIT YOU IF YOU CHOOSE ANOTHER OPTION.
4.3.3 At the end of the ROM installation, uncheck the "reboot now" option and continue - it will send you back to safestrap.
4.3.4 From within SS, install the OC3 modules from your SD card.
4.3.5 From within SS, install the I337_Stock_OC3_kernel_recovery_flashable from your SD card.
4.3.6 Reboot > system
4.3.7 Keep hitting "continue" when you get the safestrap recovery screen. This is a symptom of Lollipop not being compatible with Safestrap. Hit "continue" repeatedly (like 4 or 5 times) and eventually you will get into your ROM.
4.3.8 (Optional) Install safestrap.apk (that you d/l to your SD card) to your phone, and then use it to UNINSTALL recovery. This will avoid the above step 4.3.7 happening every time you reboot your phone.
Congrats, you now have a custom Lollipop ROM running on your device.
Note: SuperSU is finicky on Lollipop. See this thread for how to manipulate SuperSU to get your root apps working.
.
.
.
.
See? EASY.
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Israelsalinas19 said:
Safestrap never works. I always select recovery when its powering on and it just powers up normally and takes me to my lockscreen. I installed safestrap using the apk, im already rooted on stock lollipop.
Click to expand...
Click to collapse
You probably missed the step where he said to flash the nc1 kernel.
Yup, safestrap is known to be not fully compatible with OC3, that's why you have to flash the NC1 kernel in order to be able to use SS to flash your custom ROM. Don't forget to flash back to the OC3 kernel though, as stated in step 4.3.4.
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
robot_head said:
Bootloops everytime. Flash kernels and modules after rom..reboot, samsumg custom screen then safestrap then 10 seconds later back to custom screen. After flashing kernels and modules I'm still able to get into recovery, nc1 should be gone in order for ss to work. I'm so sick of odin... :what:
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
So you got all the way to step 4.3.6 successfully, it sounds like? And now you are just getting the Safestrap screen - where you can either "continue" or "recovery"? How many times did you hit "continue" and go through the "bootloop" (if any)?
After step 4.3.6, when you boot into your custom ROM, you will have the Safestrap screen pop up several times (like, at least four or five) - keep hitting "continue" and you will eventually get into the ROM. This is another symptom of Lollipop not being fully compatible with Safestrap.
I did not put that detail in the writeup. Very sorry it caused you issues. I am updating with that info now.
I must of not been patient enough, with so many failed rom installs with this locked bootloader i just odin'd back to nb1 to get to oc3... Any custom recovery would be such a relief as ss acts wonkey in lollipop, and flashfire isn't accessible if you're caught in a bootloop or the radical "att unauthorized software". Thanks for the help
Sent from my sghi337 on oc3
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
robot_head said:
Update:
So once again I follow the instructions completely to the t
After I flash the ROM and the kernel and the modules and I reboot I get the Samsung custom screen then to safe strap then 20 seconds reboots to Samsung Galaxy s4 screen then safestrap then again to the Samsung Galaxy s4 screen with reboot to recovery again and this time it puts me into stock recovery no safestrap after rebooting system each time from recovery. It does the same thing and eventually i end up at the system recovery... I've tried this about 11 times, with no success to boot into the ROM
Sent from my sghi337 on oc3
Click to expand...
Click to collapse
Did you try wiping data/cache in the stock system recovery?
Yes wiped with system recovery and safestrap. This is an issue of flashing the oc3 kernels and modules with safestrap. I think.....
sent from my sghi337 on oc3
Read through your tutorial, very nice. ?The only thing I noticed is you flash the kernel before the modules. I think flashing the kernel should be the very last step before rebooting, I'm not sure it matters, but it might. Also when the phone is booting I never touch any buttons (continue or recovery) just let it work through the screens on it's own.
Thanks, Cats_PJs - I will edit the OP to indicate flashing the modules before the kernel. I didn't see such a recommendation to flash one or the other first in my research, and I honestly can't remember now which I flashed first. But I will update the OP to recommend flashing the kernel last, just in case.
If I'm safestrap'd and rooted on a custom 4.x.x ROM, should I flash to rootable NB1 per step 2.2 then start here with step 3? Thanks for compiling all this, I chuckled at the 18 pages open comment. I know that pain.
What version are you running now? If you already have root on a KitKat 4.4.x or higher ROM, you should be able to go straight to rooted Lollipop using the muniz_ri keep root method method here. (see the very first line of the linked reference post.) So if you meet that criteria, you could start in Step 3.
If you're on a lower build, you'll want to just start with step 2 and flash NB1 via Odin. I believe that you will need to uninstall your current version of safestrap at some point to be able to install the required v3.75.
So I have an update I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading. I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels you still have to safestrap your ROM though. In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required you must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin. So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must downgrade your kernel (via odin or nc1 flasher) then you can use safestrap to flash your ROM and flash your oc3 modules then reboot into download mode and use Odin to flash your oc3 kernel(sometimes it will fail,just try again, i hold my phone gently to comfort it through the process) and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Sent from my GT-I9505 using XDA Free mobile app
robot_head said:
So I have an update
I finally found that sometimes safestrap won't flash the kernel so you have to Odin it even if its downgrading the kernel or upgrading.
I've been able to flash any lollipop rom since I've been doing the Odin method for the kernels - you still have to safestrap your ROM though.
In another thread it said to flash the OC3 partition which I didn't find necessary and when I did try to flash them Odin kept failing therefore it wasn't required
You must also flash the module with safestrap right after you do your rom unless you have your modules in a tar file then just do it via Odin.
So to go over it one more time... you have to be able to use safestrap so if you were on lollipop you must:
downgrade your kernel (via odin or nc1 flasher)
then you can use safestrap to flash your ROM and flash your oc3 modules
then reboot into download mode and use Odin to flash your oc3 kernel (sometimes it will fail, just try again, i hold my phone gently to comfort it through the process)
and it boots up going through the safestrap screen at least 4 to 5 times.
Confirmed to work. ..
Goldeneye
Imperium
Car hd
I'll be testing all the compatible lollipop roms for my device it's exciting I can finally flash roms thank you for this tutorial for heading me in the right direction.
:thumbup::thumbup:
Click to expand...
Click to collapse
robot_head, glad to hear you got the custom ROMs working on your device! I will add a note in the OP regarding your experience so it helps others that might have the same issue.
Sorry, but stupid question - you did only try to install flashable ".zip" files from within safestrap, and ".tar" files using Odin? Your word choice in your above post seems to indicate that you do recognize the difference. But I ask that because I did not realize the difference at one point, until I tried to load a .zip into Odin and encountered issues. (and also I wanted to make this distinction for any others reading this thread)
Question for you – when you are swapping between custom ROMs, are you backing up your system settings and apps/data, then restoring them to each ROM (or are you just “sampling” each ROM for limited time and not worrying about your apps)? Based on advice I read in several places, I didn’t use Titanium Backup when I upgraded from 4.x.x to 5.0.1, but I figured I could use it to swap between ROMs now that I’m on Lollipop. But I just wanted to be sure I could easily move between ROMs without requiring so much time manually downloading apps like I did for the upgrade.
@sac02 yes I do have backups of all of my firmware and roms and yes I am just sampling through all of the roms and any apps that I need backed up are on my SD card and Google Play backs up the ones from them automatically. Yes when I'm flashing with safestrap obviously it has to be a zip file and Odin has to be a tar. And if you search the site there are downloads for your kernel in a tar format I actually got half of the help I needed from this thread and the other half from the Goldeneye thread when someone was having an issue with safestrap they had to Odin everything.
Sent from my GT-I9505 using XDA Free mobile app
The instructions are good. You may have a bad download of kernel file. Note that the instructions call for the "reflashable kernel zip file" which can also be found on the NC1 flasher thread.
My main problem is i couldnt flash kernels with safestrap after the rom. Tried a different download, same thing. Either said unauthorized att software
Or firmware update failed, use kies
Or bootloop into system recovery.
Finally. ..just odining kernels solved my issue.
Sent from my GT-I9505 using XDA Free mobile app
I have root on a base NJ4 4.4.4 ROM. I couldn't get the google play edition working on my i337 (dimming sensor worked poorly during calls) so I went to something basic. I'll try your recommendation, thanks again.
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
re: phone won't boot
bloewen4 said:
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you have either a custom or stock rom installed or the official Samsung firmware installed
then it should be an easy fix, you must have flashed a incompatible kernel or perhaps you
deleted the kerned. (the phone will not boot without a kernel)
You need to find a compatible kernel and flash it using twrp recovery.
Here is a link you may want to try, it's for kernels for the Note 5 only:
http://forum.xda-developers.com/tmobile-galaxy-note5/orig-development
It might even be better if you were to Odin flash a fresh copy of your Note 5 specific
firmware using download mode, that's the surest way to get your phone working again.
Give it a try...
Good luck,
Have a great day!
Good luck!
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Click to expand...
Click to collapse
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again
Click to expand...
Click to collapse
re: not sure what you mean
bloewen4 said:
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Click to expand...
Click to collapse
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
---------- Post added at 09:21 PM ---------- Previous post was at 09:08 PM ----------
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
Click to expand...
Click to collapse
I realize I have a W8 and hes providing the firmware for a T. I rooted with a kernel that was for a T version and everything worked fine. I researched rooting note 5 SM-N920W8 and they said do everything the same for the T version because theyre basically identical and isnt much info on the w8 version. So far Ive had no issues flashing everything designed for the T version on my W8. Actually Ive only tried flashing stock w8 firmware from.sammobile.com and got a fail in odin so now Ill try the version MisterJunkie provided me with for the T version unless considering all this you think I should still try a different firmware all together for the W8?
Misterjunky said:
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
Click to expand...
Click to collapse
Bud, that's not the official tmo pd1 firmware, and I'm not sure if the leaked (alright it would likely run) would be the best here...plus he scares me when he says he cleared EVERYTHING cuz I'm thinking back to exactly how much twrp will wipe, but it's a lot so I fear he's going to need some partitions restored that are only going to come from a full pit file mapping...I don't believe official pd1 would flash in odin, nor would I recommend doing so- I would locate the most recently official firmware to ensure all partitions are restored, then if he doesn't have official mm support he can look into the leak, but if he had official for his variant and carrier that's his best bet to ensure 100% fix and give him a solid foundation to start from if he wants to root, rom, mod, etc
Not to discount your advice, I'd just hate to see him in a worse place than he is...which he's not even bricked YET...but he's starts screwing with wiping efs or messaging with csc stuff from different variants and he could back himself into a corner...
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Click to expand...
Click to collapse
My carrier is Rogers. I did goto sammobile.com already and downloaded and flashed what I thought was the current stock firmware for my 920w8, but I flashed without wiping all data as previously stated. Maybe doing this will allow my firmware to flash? Will try when Im home from work. Will also post the link from sammobile.com for the exact firmware I download just to verify ots the right one.
Yeah I literally wiped everything I checked all the boxes and I remember having to manually type y e s to proceed so yeah pretty serious wipe lol.
I have the latest version of odin 3.10.7 and tried installing drivers on my pc said theyre already installed.
When I connect my phone to usb in download mode it says com:4
I thought also that just flashing the stock firmware would be the solution since I get download mode and twrp I just have a blank phone but as I said I did get the stock firmware from sammobile.com and try but it failed. Maybe I grabbed the wrong one but it looked pretty straightforward. Maybe with MM coming out Wednesday for rogers note 5 Im downloading the wrong version.
Im worried like you wrote earlier that I deleted too much with twrp if I needing mapping partitions and PIT files I will need some serious help that stuff is beyond me.
Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom
Click to expand...
Click to collapse
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Still with a blank phone, any ideas?
Or if anyone could direct me to another thread that might be useful for re mapping partitions?
Have you tried flashing twrp again in Odin?
I hit too many buttons before when wiping. It even erased my recovery.
Once I had recovery again I could Odin flash the official firmware.
Could try Philz recovery as well.
Sent from my SM-N920T using XDA-Developers mobile app
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Click to expand...
Click to collapse
bloewen4 said:
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Click to expand...
Click to collapse
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder.. Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it. If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note5/orig-development/kernel-skyhigh-tw-6-0-1-kernel-t3321646
If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
Click to expand...
Click to collapse
I did try immediately to connect with Windows to my phone so I could try flashing stock firmware with twrp but its currently not allowing me access to view storage on Windows though it does connect with odin saying com:6.
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder..
Click to expand...
Click to collapse
I will do this as soon as I am home from work. Will this perhaps allow access with Windows and/or adb sideloader?
Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it.
Click to expand...
Click to collapse
I will be researching how to do this. Have you any threads to learn adb? So basically this will allow me to put ROMS or other files into the internal memory?
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note...ernel-t3321646
Click to expand...
Click to collapse
Is this the right kernel for SM-N920W8?
* SAME kernel for ALL supported variant !!
** If other party cannot hear voice when on speaker phone ** Then read Post #636
SM-N920 C / CD / G / i [ v3.2 ]
SM-N9200_HK [ v3.2 ]
Click to expand...
Click to collapse
Also Marshmellow isnt out officially for SM-N920W8 so Ill need a kernel for lollipop 5.1.1 unless you suggest to wait for marshmellow then try a mm kernel?
Thanks for helping!
How about this adb sideloader does anyone think that will work to load the firmware? If so any good threads to guode me?
What did you end up doing? I have a similar problem except no recovery mode, just download mode for Odin.
bloewen4 said:
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Click to expand...
Click to collapse
Where did you get your firmware from?
Why oh why did I bother reading through this entire thread, with intentions to help OP. Lol I didnt realize the date till the last post.