Database Info

[Q][GT-i9020a] How do I reflash back to factory?

Hi, new Android user here.
I was trying to root my Nexus S phone yesterday and I'm having problems. There is a lot of rooting guides out there and I used one from xda and also one from unlockr.com. Managed to root the phone ok (I think), but everytime I flash a custom ROM, the phone won't start at all, it just sits at the boot up screen and repeats itself.
So I'm thinking, I should just start over again. So I flash the stock ROM from xda back to 2.3.1. Everything seems ok, the phone starts up... but it's always stuck on airplane mode and the phone itself doesn't even show stuff like IMEI, mac address anymore.
So now I figure I've probably messed the phone up enough and need help lol. How do I go about reflashing the stock ROM and getting my Nexus back to out of the box condition (Stock ROM and no custom bootloader)?? Any guides or step by step instructions would be very helpful.
Thanks

Did you wipe before flashing roms?
Sent from my Nexus S c",)

Maybe flashing the KB2 modem would help that but the 9020a came stock with 2.3.3 and not 2.3.1 so that could be it...I'm not sure but that software wasn't meant at all for ours so it could be part of the problem. But if I was you I'd take a look at this thread wich has all the stock software for your phone. Make sure you wipe everything in clockework and then flash the stock rom. http://forum.xda-developers.com/showpost.php?p=13123996&postcount=39
dsixda uploaded the stock backup and the stock recovery, you can read more at that link, good luck hope it helps

You can download the full stock ROM from the link below:
http://goo.gl/8P8vl
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.

jungbum said:
You can download the full stock ROM from the link below:
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
Click to expand...
Click to collapse
that did the trick. thanks everyone, now time to try rooting and flashing ROM again!
hrm lol now trying to update it to 2.3.4, it downloaded the update, but on reboot i get the white triangle with ! in it :\
this phone is so messed now
edit: well now everything is ok again, wiped data, flashed with CM7 and now it says 2.3.4, go figure.

[Q] Is my phone back to stock yet?

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!

Alright guys I'm stuck :( (soft brick? ) please help

I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?

j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709

psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium

volume up/home/power button is recovery try that
and you used rom manger to flash rom?

j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.

PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.

not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.

If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?

j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.

j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.

[Q] M8 Stock Recovery help

I want to go from TWRP recovery to stock recovery so I can take the latest OTA and update to latest version of viper. When I try to flash stock recovery through fastboot, I can't reboot into recovery, but I can boot into the my current ROM. After I flash TWRP back, I try to RUU using the RUU zip, but it says that "it doesn't have enough space."
My 2 questions are
What steps should I take to return to stock so I can update the firmware?
On my fastboot menu, it shows the OS - spot as blank, what should I do about that?

oFumbleSo said:
I want to go from TWRP recovery to stock recovery so I can take the latest OTA and update to latest version of viper. When I try to flash stock recovery through fastboot, I can't reboot into recovery, but I can boot into the my current ROM. After I flash TWRP back, I try to RUU using the RUU zip, but it says that "it doesn't have enough space."
My 2 questions are
What steps should I take to return to stock so I can update the firmware?
On my fastboot menu, it shows the OS - spot as blank, what should I do about that?
Click to expand...
Click to collapse
Have you tried putting the RUU on an SD card and booting into bootloader mode and letting it automatically detect it and install it? This would usually take a few minutes all the way up to 20 minutes, just incase you were expecting something quicker and may have exited out of it previously.
To my knowledge the RUU would/should fix the OS issue as it installs everything again back to stock.

oFumbleSo said:
I want to go from TWRP recovery to stock recovery so I can take the latest OTA and update to latest version of viper. When I try to flash stock recovery through fastboot, I can't reboot into recovery, but I can boot into the my current ROM. After I flash TWRP back, I try to RUU using the RUU zip, but it says that "it doesn't have enough space."
My 2 questions are
What steps should I take to return to stock so I can update the firmware?
On my fastboot menu, it shows the OS - spot as blank, what should I do about that?
Click to expand...
Click to collapse
I have had this exact same issue on the last two M8s I've had to RMA, so I have to return them to stock/locked/S-On. I had to use the SD card option that SilentShadows is referencing above to get the stock bootloader on my previous phone. But I can't find my old SD card that I used before now, so I went back to this thread to see if anyone had posted a solution to it from the last time I posted in there asking the same question you have. I found this nice post which may explain it for me at least. I was using my laptop that only has a 120GB SSD that stays pretty full, so that may have been the issue for me. Make sure you have at least 2GBs free on the PC/partition you're flashing the RUU from.

Soft Bricked Note 5 SM-N920W8 - Please Help Recover

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.