I've lerked for three days with no success, I did trapkernal just fine but it broke the wifi and any attempt to recover or change the kernal through odin has yielded nothing. I don't know if it's roofted or if I can do anything. I followed the guide exactly but with the wifi slider permanently off I couldn't download checkroot or any rom mannagers. please help, I haven't had any luck flashing anything after flashing trapkernal to it.
I had same issue with a family members phone. The latest security releases aren't fully compatible with trap kernel. I fixed by downloading an older firmware version and rooting
Found a Solution
Hey everyone.. just wanted to chime in and let you know that I ran into this problem as well on my T-Mobile Galaxy Core Prime SM-G360T, and after some trial and error, I found a root method that worked.
Ok... My spare phone is a stock Galaxy Core Prime SM-G360T w/ latest stock rom update. I wanted to try my hand at rooting it, so when I attempt to root my Galaxy Note 4, I don't run across any issues...lol
Well on my first attempt on rooting the Core Prime... I got the (custom binary lock by FRP)... reinstalled factory rom, and tried again.
Second attempt... Was the TrapKernal method witch achieved root, but wi-fi and internet was inoperable.... reinstall stock firmware, and try again...lol
Third attempt.... was just install TWRP & SuperSu, and again achieved root, but when booted in recovery, the screen wasn't responsive....so reinstall stock firmware, and try again...lol
Fourth attempt... I used the CF-Root method, and finally achieved good root, on my Core Prime, and no issues so far.
Anyone have firm for this flushable in twrp as all i can do as boots twrp all the time that's it and system gone too
just do a google search for it... it's been out long enough that it's easy to come by.
Related
Hello everyone, i'm a new member. I apologize if my english is not good enough.
After been driven insane by one pre-installed app from my Operator (Claro Peru) i decided that it was time to root my device to get rid from that pest. I'm a noob, so i started to investigate about the safest methods to not damage my phone. My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Copellius said:
... My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Click to expand...
Click to collapse
ok so you have the i337m canadian version... making anything related to safestrap and the att i337 irrelevant, completely different methods so don't get them confused lol
you were updating from stock 4.3 right? your best bet is to factiry reset and reflash stock fw for 4.4.2 before you brick your device... kitkat is very different from 4.3, maybe read up on it a bit too...
for ex, the "message with a shield appeared saying that my device security stopped the operation" isn't related to needing to root, it's an option under security settings.
to enable superuser on kitkat you need to enable developer options, then enable superuser. I prefer supersu so manually install that from play store afterwards. I recommend checking and/or enabling this as soon as the phone completes booting up after flashing.
also I think there's a known issue w/ 4.4.2 and wifi not turning on until after 2nd boot completed if I rememebr correctly, been using 4.4.4 for awhile now though so could be wrong...
good luck and check out the help section :angel:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?
I've rooted and replaced the ROM on 3 other Android devices. I've spent two or three nights on this. Googling and reading page after page to try to get this right. I know I'm seriously lacking in knowledge, but I just can't stand the bloatware and lack of control over an OEM ROM. I knew I was taking a risk, but I did my best to be diligent without spending an excessive amount of time. All that said, I appreciate, in advance any help anyone can offer me. Whether that's direct advice or directing me to proper resources that I can't seem to find.
Samsung S5 SM-G900P (kltespr)
I had rooted it. I replaced the Sprint stock ROM (5.0.1 I think) with CM12.1 (which just got an OTA). I had TWRP 2.8.7 on it.
Unfortunately, I needed my research suggested I needed a Touchwiz ROM in order to activate phone service on the cell provider I'd chosen (Ting).
So I selected MOAR v7 and started following the directions here:
at galaxys5root.com/sprint-galaxy-s5-custom-roms/moar-lollipop-rom-for-sprint-galaxy-s5-w-2-8ghz-oc
I made a backup. I wiped the system/cache/davlik/etc.
I installed the Android 5.0 Bootloader TAR (G900P NDK Lollipop) per the instructions via Odin and using the Bootloader option. The flash failed. I can repeat the failure (ran Odin as admin, tried multiple USB ports, restarted the computer etc). I've since tried to send several recovery ROMS or OS ROMS (pardon if I'm using the wrong terminology here) to the device, but all I can get is download mode or a screen that says Samsung Galaxy S5 powered by Android (with Kernel is not Seandroid enforcing at the top). Sending TWRP via Odin has worked with a PASS, but still can't startup the device.
I can provide more detailed logs or information about where I'm stuck and how, but on the off chance that this is an obvious thing I'm going to stop here unless more detail would be useful.
Again, I'm grateful in advance for any help.
Moshker
Follow up and how I fixed my brick
This post is intended as a follow up in case anyone runs into a similiar problem and stumbles onto my post.
After trying several different bootloaders, including the stock ones from Samsung (multiple download attempts, very slow speeds, some didn't pass md5 check), and full ROM efforts via Odin 3.10.7 I was finally able to get one ROM to take.
G900PVPU3BOG1_G900PSPT3BOG1_SPR from androidfilehost.com/?fid=24052804347794921
After getting the phone activated on Ting I used Odin to push Chainfire Auto Root (408). I verified root after restart. Used Nandroid to make a new backup. I used Flashify to install TWRP 2.8.7. I restarted to recovery and DID NOT use TWRP to wipe the system/data/etc and instead loaded the MOAR7.0.OA6 ROM. During the ROM install process it asked if I'd like to wipe system/cache/davlik/etc. I did. The ROM installed successfully. I ran a Nandroid restore to bring back my apps and data. Most restored properly.
I still don't really understand what went wrong, why my efforts to fix it failed, and why the last thing I tried worked.
Really loving MOAR. I'm using the Numix theme and it's just incredibly clean and fast. CM12.1 had intermittent micro-freezes/lags that were driving me a little nuts and MOAR is really smooth and quite fast. I was pretty disappointed in CM as I had it a long time ago on an original DInc (7.2!).
Anyway, if you're phone is bricked, keep on fighting the good fight.
Hello everyone.
N910W running stock Samsung firmware, 5.1.1 Lollipop.
I had my phone rooted a few months back and decided I wanted to try a Marshmallow rom. I created a backup of my pre-rooted device a few days prior, so I wasnt worried.
The rom I flashed for some reason would not allow me to use my carriers network, but only other networks. So i restored my unrooted backup.
Now whenever I try to root my phone, I get a bootloop. Every method I've tried so far (TWRP flash and ODIN, pretty much) has produced similar results. I could find the original samsung firmware for the device and flash it over and start from scratch, but I don't want to lose my data if I don't have to.
Halp. Send halp.
thanks guys.
P.s. i tried using the search, but this is either a unique problem or the search bar sucks.
I installed TWRP bootloader onto my OEM Unlocked Samsung Galaxy Core Prime G360P Via Odin, and afterwords attempted to boot into Bootloader.
Upon doing so the phones screen goes black, and it acts like its turned off. My computer can't detect it with ADB, and I can't boot it back on without removing the battery and then inserting it again, after which it boots normally.
So yes my phone is working, but I need to get the bootloader working, I don't even have the normal android one right now because of this odd bug, i have rooted phones and tablets before both via Kingroot, and ADB depending on the needs of the device, and have some slight experience with it but limited technical knowledge, i have found seemingly similar problems but all said to solve via ADB, which doesnt really work as my ADB cant detect my phone when it is in this dead state it goes into instead of bootloader.
I would like a fix that will allow me to have TWRP installed, nothing that requires root as i have attempted all one-click rooters and none work for my phone, and i cannot install a custom OS as I am on textnow wireless and getting it to work with one is the biggest pain on earth (plus my calling would become sh^te without the custom textnow rom calling)
So basically i need to fix the bootloader without installing a new OS altogether, without deleting any of my inbuilt apps, and without factory resetting as I cant get to the bootloader to factory reset anyway, honestly i just need a way to get TWRP to work. If the answer involves another way of rooting my phone via Odin (yes i can still get to the odin downloader) and then running a root requiring app to fix my recovery thats fine but i dont know how to do that or what it would entail
im using: twrp-3.0.2-0-cprimeltemtr
Textnow wireless uses a custom os that is slightly modified from the default, I don't know what that entails but i know that affects what fixes may/may not work so i am mentioning it
before i get the same answers i have tried:
redownloading TWRP and flashing the new copy instead in case of corrupted image
removing the battery after flashing and then booting directly into bootloader so as to stop it restoring anything
I have tried flashing other recoverys, however upon doing so found that when i tried to boot into the bootloader it would then boot to Odin instead and give me an error saying it was unable to boot normally, so i reflashed the TWRP one and it gave me the same blackscreen once again.
Any advice would be very helpfull, im at my wits end and id like to be able to recover my phone should it have problems later, id much prefer i not get stuck
Software Version: G360PVPS2APE2
Hardware Version: G360P .03
Model #:SM-G360P
Android Version : 4.4.4
Android Security Patch Level: 2016-06-01
Kernel Version:2.10.28-675169
Build #: TNG360PVPS2APE2
SOLVED
http://forum.xda-developers.com/gal...ime-sm-g360p-root-t3217885/page2#post70113291
I found something that worked highly reccomend this autoinstaller for Odin
Search the forums for stock rooted deodexed sm-g360p, thats the TWRP that I use ... almost to much. The rom is also alot more susceptible to root,mods,and tweaks. The rom is sprint, boosts a sprint partner. Its helped me get the 4glte i couldnt pickup with the boost. But definitely find that post. Twrp isn't official to our variant(that i know yet) but it works the same tho a lil dated.