Related
Does having a custom recovery mean your bootloader is unlocked? I have TRWP installed, in download mode it says samsung offical yada yada.
The boot loader is not unlocked. Do some more reading about your phone before you start doing something with your custom recovery. Many people have bricked their phones because they did not understand what they were doing. There is a lot of good advice here. Look for threads by axman, adamoutler,beerdriod, to name a few. They'll keep you out of trouble. Just some friendly advice
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
The boot loader is not unlocked. Do some more reading about your phone before you start doing something with your custom recovery. Many people have bricked their phones because they did not understand what they were doing. There is a lot of good advice here. Look for threads by axman, adamoutler,beerdriod, to name a few. They'll keep you out of trouble. Just some friendly advice
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
AdePower said:
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2292157
AdePower said:
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
Click to expand...
Click to collapse
The post above has a great link for you to research.
Basically, having a custom recovery means that you can flash roms that have had the loki patch applied to them or you can flash roms from similar hardware then flash a kernel that has been loki patched, or you can flash a rom from similar hardware using a recovery that has auto loki, or you can flash a rom from similar hardware and follow that by flashing loki-doki.zip.
Plenty of options, but if you have to ask, you shouldn't be flashing, Read the link above and everything else you can about loki and the att i337. Making a mistake with a brand new cellphone can be costly so research is imperative.
Not trying to discourage you from trying a custom rom, just trying to let you know that there's a lot of information you should have first.
acruxksa said:
The post above has a great link for you to research.
Basically, having a custom recovery means that you can flash roms that have had the loki patch applied to them or you can flash roms from similar hardware then flash a kernel that has been loki patched, or you can flash a rom from similar hardware using a recovery that has auto loki, or you can flash a rom from similar hardware and follow that by flashing loki-doki.zip.
Plenty of options, but if you have to ask, you shouldn't be flashing, Read the link above and everything else you can about loki and the att i337. Making a mistake with a brand new cellphone can be costly so research is imperative.
Not trying to discourage you from trying a custom rom, just trying to let you know that there's a lot of information you should have first.
Click to expand...
Click to collapse
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
AdePower said:
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
Click to expand...
Click to collapse
Once you get the hang of it, it's not that difficult. It's just slightly different than flashing with an unlocked boot loader. The main difference it that whatever you flash has to have a kernel with the loki patch applied before rebooting out of recovery. The patch can be applied to the roms kernel before you flash, it can be applied to the roms kernel by the recovery you use to flash, it can be applied by flashing a loki patched kernel after flashing the rom, or it can be applied by flashing loki-doki after flashing the rom.
The roms come from identical snapdragon 600 equipped S4's, not the octa-core models and you apply the loki patch as needed with one of the methods above.
essentially it's an extra step in the process with several different places you can put it.
If you've flashed other roms, it won't take too much reading before you get the hang of it, but it's still best to put a little time into research before pulling the trigger.
acruxksa said:
Once you get the hang of it, it's not that difficult. It's just slightly different than flashing with an unlocked boot loader. The main difference it that whatever you flash has to have a kernel with the loki patch applied before rebooting out of recovery. The patch can be applied to the roms kernel before you flash, it can be applied to the roms kernel by the recovery you use to flash, it can be applied by flashing a loki patched kernel after flashing the rom, or it can be applied by flashing loki-doki after flashing the rom.
The roms come from identical snapdragon 600 equipped S4's, not the octa-core models and you apply the loki patch as needed with one of the methods above.
essentially it's an extra step in the process with several different places you can put it.
If you've flashed other roms, it won't take too much reading before you get the hang of it, but it's still best to put a little time into research before pulling the trigger.
Click to expand...
Click to collapse
So the best option would be the recovery that applies the patch automatically correct?
AdePower said:
So the best option would be the recovery that applies the patch automatically correct?
Click to expand...
Click to collapse
It is the easiest way yes.
AdePower said:
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
Click to expand...
Click to collapse
It is easier than the HD2, I had that phone, and it was a nightmare to flash, it is not confusing, I give a STEP BY STEP in my guide, how easy is it...
5 step flash process...I don't get it, HOW HARD CAN IT BE?
here is an example...
1 - get a bowl
2 - open the box of cereal
3 - pour cereal in bowl
4 - add milk to cereal
5 - eat cereal and enjoy
it is NO DIFFERENT than that. If you can do that, you can flash roms.
go here, if you can't do this, then you need to keep your phone stock forever.
http://forum.xda-developers.com/showthread.php?t=2295557
I will help you, although, I can't flash it for you, you must pay attention.
good luck sir.
TheAxman said:
It is easier than the HD2, I had that phone, and it was a nightmare to flash, it is not confusing, I give a STEP BY STEP in my guide, how easy is it...
5 step flash process...I don't get it, HOW HARD CAN IT BE?
here is an example...
1 - get a bowl
2 - open the box of cereal
3 - pour cereal in bowl
4 - add milk to cereal
5 - eat cereal and enjoy
it is NO DIFFERENT than that. If you can do that, you can flash roms.
...
Click to expand...
Click to collapse
I've tried this, but all I get is cereal. I've repeated it exactly as written like 15 times and I think I going to be sick.
I am confused to why everyone has this problem, it is crazy. I am like you, it is embedded into my brain, my wife had to wake me up one time, because she said I kept saying flash it, flash it, over and over. Oh well.
I have seen some people, they don't like going through all the posts to find an answer, back in my early days they included a new feature called BOOKMARKS...I ask myself, what does that do...hmm it takes me to places that I have been before, that dare I say...dare dare.. explain what to do so I could reference back.
I honestly don't know where to start, I bought the Samsung galaxy s4 i337m from virgin mobile, and use it with my Bell carrier. I was browsing the internet when I come to a video that states that you can flash i9505 roms on my i337/i337m phone! So silly of me to try that, it actually worked. When I was tired of that ROM, I go on this forum thread and look for another ROM, a ROM that is i337m cooked, and it soft bricked my phone, 3 times for 3 different i337m ROMS, at this point I have absolutely no clue what is going on with my phone, is the bootloader unlocked? WTF IS LOKI?? WHY does a i9505 ROM work on my phone, and a i337m cooked ROM does not, I just need some answers!! I have been flashing my phone with ROMs since my s1 and now the s4 comes along and completely wipes any knowledge I had before I got the phone, if anyone can help me on which ROMS I can and/or can't flash, that would be great, sorry for english not my first language!
Read and do some research. Just because you flashed a number of other phones doesn't mean you know how to flash this one. Every phone is different. It would also help to know what roms you flashed that didn't work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
TheAxman said:
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
Click to expand...
Click to collapse
I still don't understand, I have the north american version of the i337m from Canada....
Dragosmp said:
I still don't understand, I have the north american version of the i337m from Canada....
Click to expand...
Click to collapse
What roms did you try to flash? Where did you get them? The boot loader is not locked and they should flash. Did you check the md5sum? They could be bad downloads.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Loki is needed for phones purchased through at&t. The Canadian version is the same phone, but without a locked boot loader, so the Loki hack is not needed.
What I have found is that some of the custom recoveries don't wipe out the phone properly. Try using Odin and go back to stock, wipe, then restart fresh
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Matridom said:
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'd do the full wipe before flashing. If you wipe after DON'T wipe system or you'll be in trouble.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Actually, I totally found that the Loki fix was needed for my Canadian i337m device (Bell). Many ROMs wouldn't work without it; they'd just get stuck in the boot logo (including SlimRom and CyanogenMod).
Just flash the ROM, then flash the Loki-Fix and you should be good to go.
If you're seriously stuck and you can't get back into your custom recovery, let me know and I'll help you out.
Now I am confused. Why would the I337m need a loki anything?
It is not needed. I surprised it even flashed.
TheAxman said:
Now I am confused. Why would the I337m need a loki anything?
Click to expand...
Click to collapse
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
Do you know what your stock firmware was before you started flashing custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
jd1639 said:
Do you know what your stock firmware was before you started flashing custom roms?
Click to expand...
Click to collapse
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
TheAxman said:
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
Click to expand...
Click to collapse
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Te3k said:
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Click to expand...
Click to collapse
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
Which custom recovery are you using to flash with and how did you get it on your phone?
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
This is just not true. No way. Friggin way weird.
scott14719 said:
Which custom recovery are you using to flash with and how did you get it on your phone?
Click to expand...
Click to collapse
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
And this procedure worked for you? You said you had to loki, where did that come in?
TheAxman said:
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
And this procedure worked for you? You said you had to loki, where did that come in?
Click to expand...
Click to collapse
Phone identified as i337m from settings menu prior to any flashing. Model number under battery matches: Model: SGH-I337M / IC: 649E-I337M.
Using Loki came in where I found that flashing ROMs wasn't working. I had already rooted and tried to unlock the phone through the debug menu. Unlocking didn't work, but rooting did and I could load custom recoveries without problem. I thought that I should try flashing other ROMs to see if I could unlock the device through their debug menus, but no luck. The first ROM I tried to flash was a SlimRom nightly. That one appeared to flash properly (recovery said "success"), but upon reboot I got stuck in a boot loop. I then went back to recovery and messed around trying to flash other ROMs and ran into the same issue persistently. I eventually panicked and Odined back to stock ROM and kernel (numbers previously mentioned). Everything was fine after I figured out how to make Odin work. (I even learned how to make signed-MD5 tarballs with Cygwin to try to make flashing recoveries and roots simpler by using Odin.) After wondering why I couldn't flash any custom ROMs, I dug around a bit and found out that some ROMs' first-posts mentioned that certain fixes had to be applied—some of which were labelled ROM-specific (e.g. GOLDENEYE-i337m-FiX-XXUBMF8) and others that just said that they required a Loki fix, and sometimes provided a link to download it. At the time I didn't know what Loki was, and I wasn't understanding why certain ROMs would come pre-"Lokified" (brain was full after hacking around for >6h). So in the moment it made no sense not to try flashing that to see if it would help. Lo and behold, it worked! I started flashing Loki after every ROM install from then on out. Previously not-working ROMs that I had already tried suddenly worked just fine (I didn't redownload them; I kept the same zip files and just started flashing the Loki Fix after each of them to make them work).
It's still the case that when I want to flash a new ROM, I wipe everything from recovery and flash the ROM. If it doesn't boot, I flash the Loki Fix and then it does boot properly.
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
BNerd89 said:
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
Click to expand...
Click to collapse
No mate tried all that, makes no difference. Even in safe mode its still behaves the same. And installed stock firmware many times, also without battery too. No improvement. Even the stock recovery isn't installed, thats the biggest question i have in that process.
malakalofung said:
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Click to expand...
Click to collapse
Have you tried to update the firmware of the touchscreen? Enter *#2663# into the dialer with your S pen and then click TSP FW Update.
Oh my God. Bro u saved my life. Thank you so much for replying and suggesting this. U r post was the 1st thing I read and did and it worked. Thanks man. Thanks so very much. U don't know how delighted I am now. Thank you again.....
Sent from my SM-N910G using XDA Free mobile app
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
coolfire said:
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Well im sure i followed the process right but now i doubt it used an incorrect file (CWM) to flash on odin, which caused this. Anyhow thank God its fine now lol. I Was literally in tears man. Ha ha
I can totally understand how you felt. Glad all is great now!
Sent from my SM-N910G using Tapatalk
This problem has nothing to do with rooting or installing a custom recovery. Only when upgrading or downgrading firmwares the touchscreen firmware can sometimes bypass the update.
Good one... Hackberrybold
More details in the Verizon Note 4 forum here.
XDA:DevDB Information
EFIDroid, Kernel for the T-Mobile Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-20
Last Updated 2017-03-31
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
vegoja said:
THIS IS INCREDIBLE!! Greatest thing since sliced bread where is the donation link this an amazing piece of development 2nd lvl bootloader f yaaaa!!
Click to expand...
Click to collapse
Believe me, I didn't do much work. You can donate to @m11kkaa, though. He's the developer of EFIDroid (if you didn't already know that...). I believe he has a donation link in his profile...
Sent from my Samsung Galaxy Note 4 using XDA Labs
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Mtotallywired said:
tried to do a bit of light research and couldn't find what's different between this and other preexisting multiboot solutions. I've been using Dual Boot Patcher for sometime without issues. Is this somehow better? and if so, how?
Click to expand...
Click to collapse
EFIDroid is what you would call a "second-stage bootloader". The main advantage over Dual Boot Patcher (at least for me) is that you no longer have to patch zip files before installing. Also, EFIDroid is more than just a multi-boot solution. Quoting @m11kkaa:
efidroid tries to focus on simplicity, and doesn't require any kernel modifications etc.
in general: well having such a powerful bootloader in your boot stage gives you lots of possibilities, like multiboot, replacements/additions for kernels/ramdisk/cmdline.
This project has a lot more potential than what's currently implemented. i.e. you can give samsung devices fastboot and sony devices a standalone recovery. Also you can natively boot GNU GRUB if you're into booting linux kernel's the desktop way.
Click to expand...
Click to collapse
The two solutions are similar enough that you can migrate your setup from Dual Boot Patcher to EFIDroid without losing any data. I'll try to post a guide later this week.
I was I under the impression dual boot required multiple ROMs running the same kernel... If that is the case a huge advantage efi has is each ROM having their own boot img. I'm currently running 3 ROMs a lollipop a marshmallow and of course a nougat. I really just wanted to see all 3 latest android os running flawlessly on 1 device. And I did just that hats off to the developer for this.
baharvey7817 said:
This is great but is there a way to uninstall it (if necessary) and get back to the primary ROM (stock or Lineage OS) without losing data?
Click to expand...
Click to collapse
There's an uninstall button in the app. Or, you could just flash the original boot.img via TWRP (basically what the uninstall button does).
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
mlock420 said:
I'm a noob...What is this? Where do I need to go to learn about why I would want this...Please explain lol
Click to expand...
Click to collapse
you can look at their website, and then decide if you want this level of control over your phone.
http://efidroid.org/
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
1freedude said:
Thanks for bringing us this tool. One thing I can't figure out...how do we Odin a different bootloader? I have DOK2 loaded now, and want to put Dr. Ketan's on the phone. The sub instructions say to Odin the BL and CP, as the ROM is generally generic. There us also a datafix and an essential fix that needs to be applied. Doing all of that is easy, but how do I keep two separate bootloaders (LP and MM) totally separate? If I flash a LP over a MM, my camera breaks, and if I flash a MM over LP, WiFi breaks. And I'm not talking about dirty flashes, a full system, data, and cache wipe 3x. Only Odin back to the base ROM keeps my phone happy.
Click to expand...
Click to collapse
There's no way to have two different bootloaders. EFIDroid comes between the bootloader and the boot.img, so it has no control over the bootloader.
EDIT: EFIDroid may be able to emulate the behavior of another bootloader... you would have to ask @m11kkaa for details...
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
CousinMikeyP said:
Where can I download this for T-mobile ??
Sent from my SM-N9300 using Tapatalk
Click to expand...
Click to collapse
Here is the LINK. You can see more info HERE
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
I will have to look into it... The EFIDroid app error messages are not exactly the most helpful kind. (Good thing the app is being phased out soon). That particular error message could mean many things, but most likely it's a connection issue. We will continue this in Slack.
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
baharvey7817 said:
I downloaded and started up the EFIdroid unofficial apk but got the following message:
=====================================
Error
Can't load device info. Please check your connection.
/data/user/0/org.efidroid.efidroidmanager.debug/files/devices.json (No such file or directory)
override ota server try again
===============================================
Could you please explain what's going on? Seems that this version is different from the one i downloaded in March. Could it be that it's not getting root access? What can I do to get around this error?
Click to expand...
Click to collapse
RaySCLA said:
Go to back to the link posted above where you got the unofficial apk and go to post #83. The OP posted an apk there that works fine on our phone.
Click to expand...
Click to collapse
Tried what you suggested but it didn't work either. So, I chose the 'nuclear option': I wiped the phone completely then reinstalled the stock Marshmallow ROM. using Odin. After that i installed TWRP v3.0.2 (trltetmo) and Supersu v2.79 as well as Busybox v1.26. Only then was I able to install EFIDroid successfully. Now, I'm able to boot the stock rom as well as Resurrection Remix.
It seems that if your going to install EFIDroid you must have the phone rooted using SuperSU. Using Magisk to root your phone instead of SuperSu won't work (at least it didn't work in my case).
lowkeyst4tus said:
Will this work on tw 7.0 if i was porting a rom. Also why wont aosp kernel work on tw.. i always thought tw was aosp with skin..
Click to expand...
Click to collapse
This should work anywhere, regardless of ROM... But btw, it's a stretch to say TW is just a skin on top of AOSP. In fact, TW is probably the farthest you can get from AOSP... There's a lot of significant differences that make AOSP kernels incompatible with TW ROMs...
Like I have mentioned to the others in the J3 Emerge community, I had this done just didn't have the opportunity to upload it until today. This is a Deknoxed and Deodexed base for custom ROMs for users who are currently on the QI2 stock firmware. And since I did nothing but remove the odexes(including the one on the boot img iirc which is why it comes up with the typical custom kernel message on bootup) and removed Knox, I'm not posting this as a DevDB thread as Samsung did all the heavy lifting so to speak.
[url]https://androidfilehost.com/?fid=745849072291691412[/URL]
And yes, this can be flashed as is but as always, you do so at your own risk. I will not replace your device and neither will Boost Mobile nor Samsung in the event of data loss, corruption, theft, fire, pod people, etc.
Please do not mirror this zip without express permission from me.
I believe this COULD be used on VMUS and SPRINT as well, but because I do not have the Emerge from those carriers. Also, from what I see it can only be rooted using SuperSU in Systemless mode or Magisk.
How can i get wifi working after flashing this?
evilgold said:
How can i get wifi working after flashing this?
Click to expand...
Click to collapse
If you're not on QI2 when you flash this, it won't work. No idea how to fix it unless you use the QI2 ODIN package to "upgrade" which is found on AFH under the user the_yankee, iirc. Not at pc so can't verify this. Have stuff to do rn so can't get on one.
SammaelAkuma said:
If you're not on QI2 when you flash this, it won't work. No idea how to fix it unless you use the QI2 ODIN package to "upgrade" which is found on AFH under the user the_yankee, iirc. Not at pc so can't verify this. Have stuff to do rn so can't get on one.
Click to expand...
Click to collapse
Thanks! that's exactly what i was missing, I guess i was using a different version before, flashing the QI2 first did the trick.
I think I will put together a set of zips that can be used to get any of the three we are all on,working on the various versions. All a user will need to do is pick their carrier and flash it in TWRP after first boot that way the system writes the csc directory. I will post you all a link when I get them built. They are sorely needed and long over due.
SammaelAkuma said:
I believe this COULD be used on VMUS and SPRINT as well, but because I do not have the Emerge from those carriers. Also, from what I see it can only be rooted using SuperSU in Systemless mode or Magisk.
Click to expand...
Click to collapse
help how to flash this zip??
help me understand please
please help me. i used the A|1 sprint Rom and soft bricked my phone and stuck in complete boot loop. it goes as far as recovery screen in TWRP and reboots. i have tried to download official Rom from your links through google drive but for whatever reason they wont download.
please help me i just need an official J327P ROM. Odin keeps getting stuck on "setup Connection"
worked for my sm-j320p boost thank you
bro, what part of the Q 12 stock did you flash in odin? im guessing the bootloader but it keeps failing on me and i'm just a bit confused on the stock Q12 i downloaded i got 5 slots last 2
look like sprint packages to me so hopefully someone can clue me in on which slots are needed to so my wifi will work please! thanks in advance
evilgold said:
Thanks! that's exactly what i was missing, I guess i was using a different version before, flashing the QI2 first did the trick.
Click to expand...
Click to collapse
is it possible to uninstall this rom?