I have a running theory for devices running another ROM and can't get advanced calling enabled. Typically, you have to Odin the latest factory tar, enable advanced calling, then Odin NCG and start the root process from square one. I have had to do it in the past, and it is an annoyance every time. I have confirmed that using FlashFire to flash the stock BOK3 tar is possible, and it injects root during the process. I believe if you use FlashFire to flash the factory BOK3 Tar, then you should be able to enable advanced calling, and then flash whatever ROM you'd like without the need to Odin back to NCG to regain root. My advanced calling isn't broken, so I can't test if this fix will actually work. If I remember correctly, @jrkruse believed the needed data to enable advanced calling was in the factory cache partition. For those who haven't used FlashFire to flash factory firmware packages, it gives you the ability to choose which partitions to flash. If someone would like to try flashing the cache partition only, then turning on advanced calling, rebooting, and check to see if it is enabled. As a note, sometimes it takes multiple attempts to enable advanced calling, even on completely stock devices. If the cache partition alone doesn't work, then use Flashfire to flash system and cache partitions, then attempt to enable advanced calling. If I'm correct, you'll have advanced calling on a completely stock odexed, but rooted BOK3 system. Then you'll be able to use FlashFire or Safestrap to install whatever lollipop ROM you want and advanced calling should still be enabled.
Steps:
1) Download whichever tar applies to you from here.
2) Use FlashFire to "Flash firmware package" and choose the downloaded tar.
3) First try the cache partition only, and make sure EverRoot is enabled.
4) After the cache is flashed, try enabling advanced calling multiple times. Then tell us did it work???
5) If the cache partition only didn't work, then use FlashFire to "Flash firmware package" and choose cache and system. Again, make sure EverRoot is enabled.
6) Try enabling advanced calling a few more times. Then tell us did it work???
7) Now go install whichever lollipop ROM you want, while hopefully enjoying advanced calling.
I did this many months ago. Unfortunately, I cannot accurately recall if it worked, hahaha. @[email protected] IIRC, I had to flash the supersu zip explicitly--simply injecting root didn't work. Don't know if that's still the case.
Wish I could remember. If I have time later I'll mount the cache images and have a look-see.
blair.sadewitz said:
I did this many months ago. Unfortunately, I cannot accurately recall if it worked, hahaha. @[email protected] IIRC, I had to flash the supersu zip explicitly--simply injecting root didn't work. Don't know if that's still the case.
Wish I could remember. If I have time later I'll mount the cache images and have a look-see.
Click to expand...
Click to collapse
I don't think I had to flash supersu afterwards to get root. I did this a couple weeks ago, and I don't remember if I had to install the supersu app or not. Perhaps EverRoot has been changed since you originally did it. Something I'd like to note, I don't believe I wiped data when I did this method.
Does your advanced calling work?
The only thing you need to do is flash one of my stock factory odexed roms then it will activate
jrkruse said:
The only thing you need to do is flash one of my stock factory odexed roms then it will activate
Click to expand...
Click to collapse
I was not aware of this. Every time you had previously mentioned activating advanced calling it was using Odin to the latest tar, then Odin back to NCG and start over. This is a much better approach!
CVertigo1 said:
I was not aware of this. Every time you had previously mentioned activating advanced calling it was using Odin to the latest tar, then Odin back to NCG and start over. This is a much better approach!
Click to expand...
Click to collapse
Also I had a family members phone that it would not activate even when doing that ,went to verizon got a new sim and bingo it worked. This is all I have had to do to get it too work. After BOK3 I havent heard of much of a problem anymore. Part of the problem was the odin back to NCG full tar when I made the rescue NCG rescue tar Which had no bootloaders and kept the lollipop modem. I think the problem was greatly reduced.
jrkruse said:
Also I had a family members phone that it would not activate even when doing that ,went to verizon got a new sim and bingo it worked. This is all I have had to do to get it too work. After BOK3 I havent heard of much of a problem anymore. Part of the problem was the odin back to NCG full tar when I made the rescue NCG rescue tar Which had no bootloaders and kept the lollipop modem. I think the problem was greatly reduced.
Click to expand...
Click to collapse
I am on BOK3 and still can't get HD calling to activate. Is there a quick fix like this I can use? Would I need to reinstall xposed after flashing the file in the link above? Thanks in advance.
jrkruse said:
Also I had a family members phone that it would not activate even when doing that ,went to verizon got a new sim and bingo it worked. This is all I have had to do to get it too work. After BOK3 I havent heard of much of a problem anymore.
Click to expand...
Click to collapse
I put my NO_BS BOK3 ROM on my buddy's phone and he lost advanced calling. His phone was completely stock on BOC4 with advanced calling enabled before starting the root process. He goes to school a few hours away and he was only in town for one night, so he didn't have time for me to go back through the process to get advanced calling to work. He'll be back in town this evening, so I'll attempt your Odex ROM fix, then go back to NO_BS.
bclay12 said:
I am on BOK3 and still can't get HD calling to activate. Is there a quick fix like this I can use? Would I need to reinstall xposed after flashing the file in the link above? Thanks in advance.
Click to expand...
Click to collapse
You can attempt this fix, or use one of Jrkruse's Odexed ROMs. If you flash a ROM, then you'll have to reflash your system mods, including Xposed. Do NOT flash Xposed until you are back on a Deodexed ROM!!!
CVertigo1 said:
I put my NO_BS BOK3 ROM on my buddy's phone and he lost advanced calling. His phone was completely stock on BOC4 with advanced calling enabled before starting the root process. He goes to school a few hours away and he was only in town for one night, so he didn't have time for me to go back through the process to get advanced calling to work. He'll be back in town this evening, so I'll attempt your Odex ROM fix, then go back to NO_BS.
Click to expand...
Click to collapse
Let me know.
I downloaded VZW_BOK3_RETAIL_TAR_IMAGE_WITH_BOD5_BOOTLOADERS.tar.zip and tried using FF to do cache partition only. I activated HD calling and restarted multiple times and it didn't do anything. I then tried doing the cache and system using the same file above and now in settings I do not have the option to even get into the advanced calling menu. I must have done something wrong here.
You probably aren't doing anything wrong. As I said, this is experimental. I'm not even sure if it will work yet. I have a strange feeling that the factory recovery.img and/or boot.img may need to be used, since enabling advanced calling requires a reboot before it takes effect.
okay. thank you. I will try flashing an ODEX rom, activating then flash the rom of choice. Hopefully that does the trick. Appreciate you looking into this though. I have not been able to get it working for a while now.
jrkruse said:
The only thing you need to do is flash one of my stock factory odexed roms then it will activate
Click to expand...
Click to collapse
The only odexed ROMs I can find by you are the BOG5 BS_FREE variants. Is that what you are referring to?
CVertigo1 said:
The only odexed ROMs I can find by you are the BOG5 BS_FREE variants. Is that what you are referring to?
Click to expand...
Click to collapse
This one would probably be the best
https://www.androidfilehost.com/?fid=24052804347794768
jrkruse said:
This one would probably be the best
https://www.androidfilehost.com/?fid=24052804347794768
Click to expand...
Click to collapse
I tried enabling advanced calling on this ROM and it didn't work. I didn't have enough time with the device to try using FlashFire to flash the factory BOK3 tar.
CVertigo1 said:
I tried enabling advanced calling on this ROM and it didn't work. I didn't have enough time with the device to try using FlashFire to flash the factory BOK3 tar.
Click to expand...
Click to collapse
I never gave it a thought but the rom build would need to match firmware and bootloaders
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
jrkruse said:
I never gave it a thought but the rom build would need to match firmware and bootloaders
Click to expand...
Click to collapse
Probably quicker to flash tar with FlashFire and inject root anyways. Then you know that will work
If they need to match the bootloader, then maybe going with the BOD5 tar would be the best bet. Does that sound like a better idea instead of using the BOK3 tar on the BOD5 bootloader?
If someone wants to try the same approach with the BOD5 tar and let us know the results, I'd appreciate it. I won't have access to my buddies S5 to test it out for a few days at least. My advanced calling works perfect, so I can't verify if this works or not.
NOTE: ONLY DO THIS IF YOU ARE ALREADY ON THE BOD5 BOOTLOADER. IF YOU ARE ON AN UPDATED BOOTLOADER, YOU WILL BRICK!!!!
The BOD5 tar can be found https://www.androidfilehost.com/?fid=24052804347763422
Nobody has tried BOD5 with FlashFire yet?
Related
A while back I flashed cm10 but the data wasn't working and I went back to stock through odin. Since then I have only been able to get 4g lte and receive texts, I can't send texts and can't call. I lose data when ever I go out of verizon lte range. I also can't root it like I had been able to before. This is because I can't get into recovery. I tried to flash cwm through odin, but when I try to go into recovery I get the screen saying it's booting into recovery and it vibrates a second time and boots normally. I have looked for solutions but can't find someone this this same exact problem.
Any help would be greatly appreciated, thanks!
mattmcs2 said:
A while back I flashed cm10 but the data wasn't working and I went back to stock through odin. Since then I have only been able to get 4g lte and receive texts, I can't send texts and can't call. I lose data when ever I go out of verizon lte range. I also can't root it like I had been able to before. This is because I can't get into recovery. I tried to flash cwm through odin, but when I try to go into recovery I get the screen saying it's booting into recovery and it vibrates a second time and boots normally. I have looked for solutions but can't find someone this this same exact problem.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Dial *2767*3855# it will do a complete factory reset, but your problem will be solved. I ran into the same problem and spent forever trying to find a fix. Cyanogenmod 10.1 currently is not working for me (and what seems like all verizon users) I keep hoping each update will fix it, but nothing does. If anyone finds a complete fix let me know.
Still not working
trevod523 said:
Dial *2767*3855# it will do a complete factory reset, but your problem will be solved. I ran into the same problem and spent forever trying to find a fix. Cyanogenmod 10.1 currently is not working for me (and what seems like all verizon users) I keep hoping each update will fix it, but nothing does. If anyone finds a complete fix let me know.
Click to expand...
Click to collapse
It doesn't do anything it just keeps dialing, still don't know what to do. Can someone help?
Try this guide first if you haven't already: http://forum.xda-developers.com/showthread.php?t=2066275. If that doesn't work, then follow section 5 here: http://forum.xda-developers.com/showthread.php?t=1762709. Then you should be able to do the dialer reprovision code.
BigErnM said:
Try this guide first if you haven't already: http://forum.xda-developers.com/showthread.php?t=2066275. If that doesn't work, then follow section 5 here: http://forum.xda-developers.com/showthread.php?t=1762709. Then you should be able to do the dialer reprovision code.
Click to expand...
Click to collapse
One quick question before I start, how will I wipe data after I odin if I can't get into recovery?
mattmcs2 said:
It doesn't do anything it just keeps dialing, still don't know what to do. Can someone help?
Click to expand...
Click to collapse
The reprovision code only works on ICS VRALF2 and VRALG1 based roms.
mattmcs2 said:
One quick question before I start, how will I wipe data after I odin if I can't get into recovery?
Click to expand...
Click to collapse
Not sure what you mean. Odin wipes the data from your previous rom when you Odin stock images. Depending on which .tar that you use, it will either leave internal storage alone or it will format it also. You won't have a custom recovery to wipe data with btw.
I had same problem after restoring a bad back up from twrp.
I highly reccomend the unbrick method over at the android development thread.
http://forum.xda-developers.com/showthread.php?t=1840030
It will make it so you reboot your phone. And you'll get stuck in boot loop. Pull battery and then you'll be able to access stock recovery. Wipe data. And cache. And reboot.
If you used root66 in the unbrick method you will be rooted with a LOCKED boot loaded. So unlock it and reinstall your favorite recovery
Hit that thanks button if it works for you
Sent from my SCH-I535 using xda app-developers app
I flashed a prerooted stock Jelly Bean file and it worked, then I unlocked the bootloader and installed cwm recovery. I'm planning on flashing a nightly version of CM10.1, but I tried to do a nandroid backup first. It was taking a long time and then it said "error while making a backup image of /data." Does anyone know why?
I also still only have 4g and can't send texts or call. Should I flash a radio file? (I don't know what that does)
SlimSnoopOS said:
The reprovision code only works on ICS VRALF2 and VRALG1 based roms.
Not sure what you mean. Odin wipes the data from your previous rom when you Odin stock images. Depending on which .tar that you use, it will either leave internal storage alone or it will format it also. You won't have a custom recovery to wipe data with btw.
Click to expand...
Click to collapse
I flashed a prerooted file through odin and then unlocked bootloader and installed cwm recovery. I still only have 4g lte and can't send texts or call. Then I flashed a couple of different modems and it didn't change anything. Any advice?
mattmcs2 said:
I flashed a prerooted stock Jelly Bean file and it worked, then I unlocked the bootloader and installed cwm recovery. I'm planning on flashing a nightly version of CM10.1, but I tried to do a nandroid backup first. It was taking a long time and then it said "error while making a backup image of /data." Does anyone know why?
I also still only have 4g and can't send texts or call. Should I flash a radio file? (I don't know what that does)
Click to expand...
Click to collapse
Here is what I HIGHLY recommend.
1.Flash stock unrooted ROM through Odin.
2.Dial that number to stock reset. (*2767*3855#) let phone reset and reboot.
3. Check your data and text/ calling.
If good. Go to step 4. If not, I'd follow the unbrick method and then repeat step 1.
4. Flash root66.tar through Odin
5. Unlock boot loader.
6. Download latest version of CWM and flash through Odin.
7. Back up current ROM and go from there.
flash-a-holic on my Verizon Galaxy S3
young and flashing.
michaeldizzowns said:
Here is what I HIGHLY recommend.
1.Flash stock unrooted ROM through Odin.
2.Dial that number to stock reset. (*2767*3855#) let phone reset and reboot.
3. Check your data and text/ calling.
If good. Go to step 4. If not, I'd follow the unbrick method and then repeat step 1.
4. Flash root66.tar through Odin
5. Unlock boot loader.
6. Download latest version of CWM and flash through Odin.
7. Back up current ROM and go from there.
flash-a-holic on my Verizon Galaxy S3
young and flashing.
Click to expand...
Click to collapse
Thank you! I got my phone working now!
Hi all,
This is an app by which you can flash the NC1 stock KK kernel(while on lollipop OC3) that is Safestrap friendly. Then you can enter to SS recovery and flash whatever you need onto your LP ROM. As we all know that SS won't work after flashing a lollipop ROM using muniz_ri method, unless you Odin a KK kernel. All you have to do is download the app and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish without having to be stuck or having to use Odin to flash the KK kernel. We are not always home by the PC to use Odin. After done flashing your files MAKE SURE TO FLASH THE I337_OC3_Stock_KERNEL_Recovery-Flashable before you reboot in order for your phone to boot up.
(NOTE: OC4 recovery flashable kernel is located here for those who need it. Thanks to Carl again)
-I did NOT make this app and I take absolutely no credit for it. All thanks go to @benwaffle the original creator of this app for our AT&T Note 3 and @carl1961 for remaking it for the S4.
If you have any questions, please let me know.
-Please note that the purpose of this thread is only to help users. No donations needed. A "thank you" is more than enough
Hope this will help.
WARNING: it may or may not work for some of you. It DID work for me with no problem, so use it at your own risk.
K-alz said:
Hi all,
This is an app by which you can flash the NC1 stock KK kernel(while on lollipop OC3) that is Safestrap friendly. Then you can enter to SS recovery and flash whatever you need onto your LP ROM. As we all know that SS won't work after flashing a lollipop ROM using muniz_ri method, unless you Odin a KK kernel. All you have to do is download the app and open it up then hit " flash", wait for it to finish then hit "tap to reboot" and it will take you directly to SS recovery. Then you can flash whatever MODs or addons you wish without having to be stuck or having to use Odin to flash the KK kernel. We are not always home by the PC to use Odin. After done flashing your files MAKE SURE TO FLASH THE I337_OC3_Stock_KERNEL_Recovery-Flashable before you reboot in order for your phone to boot up.
-I did NOT make this app and I take absolutely no credit for it. All thanks go to @benwaffle the original creator of this app for our AT&T Note 3 and @carl1961 for remaking it for the S4.
If you have any questions, please let me know.
-Please note that the purpose of this thread is only to help users. No donations needed. A "thank you" is more than enough
Hope this will help.
WARNING: it may or may not work for some of you. It DID work for me with no problem, so use it at your own risk.
Click to expand...
Click to collapse
Sound Fantastic! Lets see if I got it straight: 1. Using the Safestrap/Odin method get into LP. 2. Then install the NC1 app to get SS. 3. Flash the file you want then Flash I337 OCS Stock Kernel and the reboot.
Sound right?
Source is here https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
rfb813 said:
Sound Fantastic! Lets see if I got it straight: 1. Using the Safestrap/Odin method get into LP. 2. Then install the NC1 app to get SS. 3. Flash the file you want then Flash I337 OCS Stock Kernel and the reboot.
Sound right?
Click to expand...
Click to collapse
Yup, you got it. I was actually worried that I didn't make sense. LOL
From my Allianced S5!
benwaffle said:
Source is here https://github.com/benwaffle/AT-T-Note-3-Kernel-Flasher
Click to expand...
Click to collapse
Thank you so much, man.
From my Allianced S5!
Used this to make a backup in safestrap just to test it out. Worked great, so I plan on trying to flash the Imperium ROM when I gat a chance. This will be very useful since Flahfire doesn't work with aroma yet. Thanks for this.
Cats_PJs said:
Used this to make a backup in safestrap just to test it out. Worked great, so I plan on trying to flash the Imperium ROM when I gat a chance. This will be very useful since Flahfire doesn't work with aroma yet. Thanks for this.
Click to expand...
Click to collapse
Thank you for confirming, bro. I'm glad it's helping. And what ROM are you talking about? Can't find it in the development section. I want to flash it, too!
K-alz said:
Thank you for confirming, bro. I'm glad it's helping. And what ROM are you talking about? Can't find it in the development section. I want to flash it, too!
Click to expand...
Click to collapse
It's in the 9505 forum. I know that those ROMs worked on our phones on 4.4.2 so I thought they may still work, but I'm not guaranteeing anything.
Cats_PJs said:
It's in the 9505 forum. I know that those ROMs worked on our phones on 4.4.2 so I thought they may still work, but I'm not guaranteeing anything.
Click to expand...
Click to collapse
Well, I think you should ask in the thread first. Just in case the ROM comes with any other kernel then give it a try.
from my lollipoped Alianced N3!
K-alz said:
Well, I think you should ask in the thread first. Just in case the ROM comes with any other kernel then give it a try.
from my lollipoped Alianced N3!
Click to expand...
Click to collapse
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Cats_PJs said:
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Click to expand...
Click to collapse
That's an easy one. If you can sideload nova launcher, I think that message won't pop up. Unless, it's constant.
Could you give me the link for the thread?
Cats_PJs said:
I just gave it a shot. It did boot but kept popping up the message " unfortunately system ui has stopped". Not sure if there's a way to solve this, but for now I just restored my backup from safestrap, so at least I can confirm that part.
Click to expand...
Click to collapse
Or maybe you did a dirty flash? Did you wipe system along with caches and internal in safestrap?
K-alz said:
Or maybe you did a dirty flash? Did you wipe system along with caches and internal in safestrap?
Click to expand...
Click to collapse
I always clean flash, here's the link. Good luck, I would have looked into it more but I need my phone for tomorrow and it's time to call it a day .http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Cats_PJs said:
I always clean flash, here's the link. Good luck, I would have looked into it more but I need my phone for tomorrow and it's time to call it a day .http://forum.xda-developers.com/galaxy-s4/i9505-develop/rom-imperium-ll-v1-0-t3046889
Click to expand...
Click to collapse
Thanks. I won't flash it now. I'll wait for tomorrow as well. ?
from my lollipoped Alianced N3!
I updated to OC3 via the safestrap method muniz_ri posted. I completely debloated my phone and decided to play a bit. Thinking hey I need a backup! So I downloaded this NC1 flasher granted it root access and let it flash the NC1 kernel then hit the reboot button. Safestrap is alive. I made a backup of my now debloated rooted OC3 S4. Just to check I then in safestrap restored the backup I just made and flashed the recovery flashable OC3 kernel. While still in safestrap I wiped dalvik and cache then rebooted the phone. It went through the usual barrage of safestrap screens until the Ole Sammy logo finally showed up. When the phone booted I was greeted with nothing but force closes. No home screen nothing. Everything forced closed. Thinking the backup failed I first decided to boot stock recovery and delete the cache there. Upon reboot a bunch of safestrap screens then it booted up as usual. No force closes! The backup flashed fine and now have a slim working fall back of OC3. Thanks to everyone who has contributed here on xda. Without these forums my I337 would be att junk lol.
I flashed NC1 apk after installing safestrap and busybox on my Rom which had been flashed with The safestrap method. Flash worked great and then I backed up the Rom. I then flashed another Rom which I decided against and rebooted into safestrap and restored my original Rom. Perfect! I then tried to reboot into Safestrap with the NC1 apk and nothing happened it just rebooted into the Rom. I removed and reinstalled Safestrap and the NC1 apk and tired again. Nothing. Any Ideas?
Did you reinstall recovery thru safestrap too?
macasus76 said:
I updated to OC3 via the safestrap method muniz_ri posted. I completely debloated my phone and decided to play a bit. Thinking hey I need a backup! So I downloaded this NC1 flasher granted it root access and let it flash the NC1 kernel then hit the reboot button. Safestrap is alive. I made a backup of my now debloated rooted OC3 S4. Just to check I then in safestrap restored the backup I just made and flashed the recovery flashable OC3 kernel. While still in safestrap I wiped dalvik and cache then rebooted the phone. It went through the usual barrage of safestrap screens until the Ole Sammy logo finally showed up. When the phone booted I was greeted with nothing but force closes. No home screen nothing. Everything forced closed. Thinking the backup failed I first decided to boot stock recovery and delete the cache there. Upon reboot a bunch of safestrap screens then it booted up as usual. No force closes! The backup flashed fine and now have a slim working fall back of OC3. Thanks to everyone who has contributed here on xda. Without these forums my I337 would be att junk lol.
Click to expand...
Click to collapse
I'm thinking the force closes happened because you restored your back up without a clean wipe, but that's just a guess, though.
rfb813 said:
I flashed NC1 apk after installing safestrap and busybox on my Rom which had been flashed with The safestrap method. Flash worked great and then I backed up the Rom. I then flashed another Rom which I decided against and rebooted into safestrap and restored my original Rom. Perfect! I then tried to reboot into Safestrap with the NC1 apk and nothing happened it just rebooted into the Rom. I removed and reinstalled Safestrap and the NC1 apk and tired again. Nothing. Any Ideas?
Click to expand...
Click to collapse
First of all, if you have used the safestrap method to upgrade to OC3, then you don't need to reinstall SS and busybox again. They're both there already. It's just that SS isn't compatible with the OC3 kernel and that's why it doesn't show up and only shows up when you flash NC1 back (because it works with NC1).
Secondly, I remember that on KitKat, when having trouble with SS installing it was recommended to download SElinux changer and change the SElinux to permissive instead of enforcing. I don't know if this method would work with Lollipop and never actually tried it. Do you wanna try that and see? Do it on your own risk, though. Lol
If not then just install SS again and uninstall recovery and reinstall it again and try.
Let me see if i got it right
1. Extract the .zip file and intall the app
2. Flash the nc1 kernel using the app
3. Boot to ss
4. Install the rom
5. Flash the oc3 kernel using ss
Is that right?
7mada said:
Let me see if i got it right
1. Extract the .zip file and intall the app
2. Flash the nc1 kernel using the app
3. Boot to ss
4. Install the rom
5. Flash the oc3 kernel using ss
Is that right?
Click to expand...
Click to collapse
Yes. But if you're already on a KK ROM, you don't need it. This is only for those who are on a Lollipop ROM and want to reboot into SS.
Also, if you want to flash a ROM, like you said, make sure to wipe your phone first so you don't a ton of FCs.
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.
FAQ section in the 2nd post.
BEWARE OF EVERYTHING! I AM NOT RESPONSIBLE if your phone implodes, aliens take over Mars, don trump starts WW3 and WW4, or your dish washer starts working again from using this guide. Remember: just because it worked for me, does not mean it will work for you, but it might! I recommend having an ODIN copy (.tar file) of the MDL bootloader so in case anything goes south, you can get back to stock and start over from scratch.
IMPORTANT! This guide will show you how to (easily) maneuver around the At&t sgh-i337 on the MDL bootloader as far as root and other things are concerned. This guide is NOT for any other bootloader! Once you have updated past jelly bean 4.2.2 then you will not be able to use this guide!
Now for the good stuff...
So you've just taken your new At&t GS4 out of the box and discovered that you're on the MDL bootloader (like I did)! First you're going to want to root it. You can do this by grabbing a good 'ol copy of towel root (just search the forums here or Google for it). Next, you're going to want to freeze the OTA update so the phone won't update off the MDL bootloader (after installing SuperSU of course). You can do this via the Titanium Backup app or the MyBackup Root app (now called just MyBackup I think).
Let's recap...you will need a copy of the towel root app, then SuperSU, then TB or MyBackup Root app. SuperSU will kill the evil KNOX for you.
Next you may want to install a custom recovery. To do this, you will need to use an exploit file called Loki Doki. Follow this video to take the needed steps to get loki'ed and a recovery installed: https://www.youtube.com/watch?v=VmkL9atpVHw
Yes, I know it installs CWM which is way out of date, if you want to use TWRP go ahead. However, this guide deals with CWM so if you use TWRP you're using it at your own risk and going against the guide! GO WITH THE GUIDE!
However, if you want to update to TWRP recovery then this video by the same guy as in the last video should do it: https://galaxys4root.com/galaxy-s4-...or-verizon-galaxy-s4-with-twrp-v-2-8-4-0/amp/
Once you've got loki lurking around your phone's memory, you're good to install a custom ROM! TA-DA! Awesome how all that worked out isn't it?
How to install a custom (TW) ROM
If and only if you followed the ZedoMax video, you should now have OUDhs CWM Touch Req0very v1.0.3.4 installed. Now would be a great time to boot into it so power off your phone then hold power, home, and volume up at the same time. Hold it! Hold it! Hold it! Release when you see the CWM menu. Now let's Nandroid this hush puppy!
Goto backup and restore and hit backup. It will most likely save it to your internal memory, but you can copy it to SD card later, or just reboot now and move it. We now have a working backup in case your dog eats your homework. After that's done, make sure the ROM .zip file you are going to boot is on your SD card. Now go to wipe cache partition and select yes. Go to Advanced and wipe dalvik cache. Go to wipe data/factory reset and select yes. Goto mounts and storage and select format cache, then select format /system.
NOTE: If you want to keep all your personal data (pics, videos, etc.) then stop here! If you want to completely nuke your phone and start from scratch then select format /data from the mounts and storage menu.
Once you've formatted /system (or did a complete wipe by formatting /data too so now you have nothing), you're ready to install a ROM. Select install zip from SD card from the main menu. Find your ROM .zip file and select it. I used the latest GoldenEye ROM because it has an Aroma installer built in so it pretty much does everything for you once you tell it what you want. Easy!
ROM should now be installed and everything should work ok once your phone reboots out of CWM recovery.
How to boot a custom (AOSP/CM) ROM
WARNING! THIS IS EXPERIMENTAL! Following this may get your ROM booted or not. Do so at your phone's own risk! You could erase stuff on accident!
Place the ROM file on your SD card. Boot into recovery and select wipe cache partition. Then select wipe dalvik cache. Now select wipe data/factory reset. Once all that's done, you will need to format /system and /data. Now goto install .zip from SD card. Select your ROM file and pray to whatever higher power yourbelieve in that it worked. Next you're going to (maybe) need a kernel.
Kernels and Modems
Download a compatible kernel for the ROM you want to use. Boot into recovery and flash the .zip file for the kernel from your internal memory or external SD card. Be sure if you are booting a TW ROM that you use a TW kernel. Same goes for CM and AOSP.
Modems are pretty much universal on the MDL firmware and possibly on others as well. To flash a modem just select the .zip file and flash in recovery from your SD card or internal memory. You can use any baseband modem...MDB, MK3, NB1, OC3, etc.
FAQ Section
What is the MDL bootloader? It's the jelly bean 4.2.2 firmware for the at&t galaxy s4. It's a locked bootloader, however it has a flaw in it that can be exploited by Loki Doki to allow a custom recovery to be installed.
What is Loki Doki? It's something that exploits the flaw in the MDL bootloader allowing you to do things an unlocked bootloader can do. To my best of knowledge, it acts similar to a PlayStation modchip by tricking the bootloader into thinking that whatever you feed it, is authorized to boot.
Can I downgrade my bootloader to MDL if I took the OTA? Only if you're a Samsung or at&t smartphone hardware tech.
Why can't I use Loki on other bootloaders? Because the flaw that loki exploited was patched in the MF3 firmware. With the exception of the MDB bootloader which was the bootloader before MDL.
Do I need motochopper to root my at&t s4? Nope, towel root works just fine to get root on the MDL bootloader.
Why does OUDhs CWM recovery tell me root or recovery may be lost on reboot and want to fix it? I have no idea, I think it's a bug. Just select "go back" until your phone reboots and all should be fine.
Why does your guide say "experimental" for AOSP or CM based ROMs? Mainly because I haven't messed around with any and am basing on how to boot them off my time using the galaxy s2.
Why can't I use TWRP recovery instead of CWM? You can, as I pasted a link to get TWRP installed in my guide. It's just I based my guide around CWM because that's what I have always used. Do note that TWRP is different, so you'll have to figure out how to wipe and install the ROM property.
What's the difference between CWM recovery and TWRP recovery? Nothing really, except the UI and how they handle files and things. Due note that CWM recovery has been discontinued, while TWRP still thrives today with updates.
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Tubifex said:
So I am on MDL and have OctOS 7.1.1 flashed but no root. I have tried towelroot with no success. I do however have TWRP 3.0 on my phone but SuperSU won't flash. Do you have any ideas?
Click to expand...
Click to collapse
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
StoneyJSG said:
OctOS has root disabled by default. You have to flash a root .zip file to activate root. Make sure you are loki'ed and that you have the right TWRP version as well as the right root .zip for your phone. Towel root only works on stock Android jelly bean 4.2.2, 4.3, and kit kat 4.4.2
Click to expand...
Click to collapse
Where do you suggest I find root.zip file?
Tubifex said:
Where do you suggest I find root.zip file?
Click to expand...
Click to collapse
I am not too sure, I haven't messed with OctOs at all. Try here:
https://forum.xda-developers.com/galaxy-s4-att/orig-development/rom-team-octos-oct-n-t3532663
Someone there in that thread will probably know.
Finished! This guide is done!
Bump....happy flashing!
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
jabulon said:
Can anyone please provide the ATT-I337UCUAMDL-20130430103714.zip file? All the mirrors are dead
NVMD,found something similar here:
https://androidfilehost.com/?fid=23203820527944165
and here:
https://server.samsung-firmware.org...de28764422/ATT-I337UCUAMDL-20130430103714.zip
Click to expand...
Click to collapse
You are needing the MDL ODIN .tar / zip file correct?
7ravler said:
Does this APK work anymore? It will not download to my phone. I had to download it to my pc then transfer it via usb to my phone. When I go to install it I get an error saying There is a problem parsing the package.
Click to expand...
Click to collapse
Which APK file are you referring to? Towel root or something else?
StoneyJSG said:
You are needing the MDL ODIN .tar / zip file correct?
Click to expand...
Click to collapse
yep, but I've already found it
Thank you!
jabulon said:
yep, but I've already found it
Thank you!
Click to expand...
Click to collapse
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Scottie32583 said:
Hi,
I'm trying to find a way to install MDL to be able to get past my att bootloader lock. I have everything except the MDL Odin file. Can you please tell me the link to get it. I'm new on the site sorry if Im in the wrong section. I want to be able to install custom rom on my SAMSUNG-SGH-I337 Att. I have already downgraded all the way to NB1 and rooted and updated all the way back to OK2 without losing Root access. I went ahead and reflashed stock for fun however to see if I could do it. It worked. So now I'm unrooted back on OK3 official via OTA. I just tricked the time on the phone, changed the date, to bypass ATT's stupid ota 24 hour update wait period inbetween updates. . So I have no issue experimenting because I have the way to downgrade all the way back to NB1 no problem with Odin and then Ota update back to OC3 then OK2, Ok3 ext. Ext. So I just need to get to MDL so I can use loki from what I have read. I'mean only able to get to NB1 basically due to lack of .tar/Odin file for the exploitable mdl bootloader.
So if I can get the Odin file or zip to MDL I will know what to do.. Thank you ahead of time for all your hard work! This post is amazing.
-Scott
(Hopefully I did this right lol)
Click to expand...
Click to collapse
Once your phone has been updated past MDL, you cannot go back. NB1 is the farthest back you can go without bricking. You are stuck with safe strap recovery for kit kat and flash fire for lollipop. You can only boot custom touchwiz ROMs.
Thank you so much!! You saved me a lot of time with this information. I can quit trying to find a way to go back. I will stick with flash fire and safestrap.
Scott
No problem. Be careful as safe strap works only with kit kat to my knowledge. If you're on NB1 I think that's kit kat. Flash fire works with lollipop as safe strap doesn't. Flash fire may also work under kit kat, but I am not sure.
StoneyJSG said:
Which APK file are you referring to? Towel root or something else?
Click to expand...
Click to collapse
Sorry to leave you hanging here. I was referring to towel root and I did find a good file. Thanks. I see you posted that I cannot go back to mdl after updating to OC3? Bummer! I should have researched a little more before I did that
Nope, once you update past MDL which is MK3 I believe it patches the loki doki exploit so it can't be used and also makes it so if you try to downgrade back to MDL you can brick the phone.
good guide.
err on the side of kindness
Hello everyone,
Here is what happened: Lucky Patcher was not working on my device so I saw a thread that said I had to flash Superstock Kernel, which I did through TWRP. I only noticed later that it was for SM-93XX, but I have 95XX. I am new at this studd and didn't realize it was device specific. I used the file found on this link:
https://forum.xda-developers.com/galaxy-s7/development/kernel-superstock-v1-3-5-t3453464
My phone won't boot now and I REALLY dont wanna format everything for the zillionth time. Is there a way to use TWRP to undo the flash or flash something in its place to allow me to boot normal again without wiping my data?
And if wiping my data is my ONLY option, how exactly should I go about doing it (while preserving as much of my data as I possibly can)?
Thank you
I should note that I know how to use Odin to flash stock firmware back on. Would this restore stock android without wiping my data? Would it adversely affect my files in any way?
Got it! I just flashed this Kernel here:
https://forum.xda-developers.com/ga...rnel-jesse-s-kernel-galaxy-s8-exynos-t3603521
It isn't stock, but it claims improvements, and lucky patcher works now.
can you open download mode ? then download stock rom and flash? https://www.sammobile.com/firmwares/
Thank you for your reply, but as I mentioned, I got it now. Sorry if I wasn't clear. What I meant was that I had TWRP and flashed another kernel. Now its fine. Thanks again!