Hey guys,
Well I have been trying to get the Kn0x0ut tool to work and I have been running into errors so I decided to try install Safestrap for the AT&T Note 3's and so far it seems to be working.
I installed TWRP using the app and the recovery seems to be working (except for showing the wrong time), I did a full backup successfully and booted back into stock. I also checked my Knox counter and its still 0x0.
I personally like the idea Safestrap however I have not tried flashing any roms with the recovery since apparently there are still bugs with aroma.
I just wanted to put it out there since more info cant hurt right?
Related
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
zuuus said:
Hey guys, so I've had my Aussie Telstra Note 3 (SM-9005) for just under a month, rooted it with Knox 0x1, installed TWRP 2.6.3.5 and have tried out a few custom ROMs - all went fine. (Last ROM that worked properly was Foxhound 1.0.)
That is until I flashed X-Note Transformer Edition (MJ7). I flashed this through TWRP 2.6.3.5, everything was successful and standard as any other flash, rebooted into the ROM only to find a message saying "Can't play this video" on the very first Interactive Tutorial (Language Select) page. This message appeared multiple times, then more messages saying the system has crashed. Also, everything is extremely slow and barely anything works - including sound, camera, settings, etc. Also Wifi detects networks but cannot connect to them (system crashes). Any time I try to do anything settings related the system bootloops, and I cannot get a mobile signal at all.
Now here's the weird thing, I thought it was just an issue with the ROM not being compatible, so I rebooted to recovery, tried to reflash the previously-working Foxhound 1.0 ROM - SAME ERRORS. Tried a full wipe/format/rm -rf - and install stock ROM from zip - SAME ERRORS. Downloaded the completely stock Telstra Odin ROM, flashed through Odin successfully - SAME ERRORS. Tried to restore EFS (It said successful) - SAME ERRORS... hope you can see where I'm going with this. I've also tried CWM, flashing with different versions of TWRP, full wipe before installing any ROM, etc. tried basically anything I could find on xda without any luck - the ROMs all boot up, but as soon as they load it pops up with the same "Can't play this video" message and everything starts locking up.
This has me really worried since I tripped Knox at the very beginning before Root de la vega, I'm only hoping whoever Telstra use to fix these doesn't care about the counter.
I have literally spent two days without sleep trying everything to fix this and completely failing, so If anyone could help me out I would be forever in your debt, cheers.
Click to expand...
Click to collapse
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
ultramag69 said:
What was the last version of firmware flashed?
You might need to flash the gsm modem for that firmware version to get it to work especially considering you have bootloops and no reception.
You might also need to use Megawipe to clear any errors that stay on your device after flash.
Click to expand...
Click to collapse
Hey mate, last version of firmware was the Stock Telstra SM-N9005 / TEL ROM I found on www . sammobile . com/firmwares/2/
I have tried at least 10 different ROMs with no luck, every single one does the same thing.
I did send it off to Telstra to try for a repair, they sent it back to me unrepaired due to nothing to do with the software but a 1/4mm scratch my keys made in the chrome plastic around the edge with the words "unable to be repaired due to physical damage" with a little sticker pointing to the scratch. ****ing ridiculous if you ask me.
Honestly I don't know all that much to do with the modems and csc's so it might be that causing my problems but I have tried a bunch of different ones without any change.
At my wits end here, phone is just over 30 days old and I can't use the damn thing.
try odin back to stock, then use kies to "emergency firmware restoore" Kies can be a life saver in some situation, make sure you use beta 3 version
I just flashed this rom successfully yesterday. The rom was stable and working, however I wanted to get the hotspot to work. I used a hotspot mod on a previous 4.3 rom, so I tried it again on this rom. I flashed the MDC Hotspot Mod while in Philz Touch 5.18 recovery. After flashing the hotspot mod, I reboot the system and it is stuck at the "Kit Kat" splash screen. I went back to recovery, wiped everything (data reset, cache, davlik cache) and reinstalled the rom and it seemed to work fine. However, I wanted to get the hostpot working so later in the night I reinstalled a 4.3 rom, and now I can not get any rom to work. When I boot up I am not faced with the Galaxy S4 screen saying:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
It will not go to the Kit Kat splash screen, I can get to download mode and recovery mode. I tried completely re-rooting the device, Installing different roms and even a different kernel, but I can't seem to get anything to work. At this point, I just need my phone to work and will use any rom. I don't think this is a fully bricked device because I can get into recovery and download mode. I can live without hotspot for now, just need a working phone. If anyone can advise here or help please reply here or email me at [email protected]. This is my daily driver phone and I need it to work, hopefully it is an easy fix like getting a stock 4.4 kernel? BTW this was a brand new galaxy s4 which came with stock 4.4, so I am not sure if installing 4.3 had an issue with it. Maybe using ODIN to fix the problem, I am not sure. I have successfully rooted many phones including HTC EVO 4G, HTC EVO 3D and Galaxy S4( until now) and have never ran into this issue. Please advice anyone!! Thanks!
RE: S4 Sac Rom Issue Please Help
I ran into a similar problem and my device would not boot. I simply just reflashed clockwork 6.0.4 recovery from Odin and was able to get back into recovery to wipe and reflash a new rom. Hope this helps. Note: I selected PDA in Odin. Here is a tutorial to get recovery back.
http://jellybean-news.blogspot.com/2013/02/complete-guide-to-install-clockworkmod.html
Good luck.
Hi I need desperate help
two days ago I went from CM11 to S4I9505 Google Play Edition ROM 5.0.1 and everything was running perfectly. Today I used an app known as "ROM Installer" to flash TWRP easily which it did but I couldnt go back to normal menus and it kept on booting back to Recovery. So I wiped everything and installed the same ROM as it is in my External SD. It was successful but it still would boot to recovery and nothing would work. So I thought my option was to unroot the phone. I used the XDA Unroot/Unbrick guide and used an Android 5.0. Lollipop firmware to flash the stock firmware (second time every using Odin, the first was disastrous and I hated it). I flashed the official stock and it is running but cannot activate WiFi what so ever. It just refuses to toggle. So I reflashed the stock firmware again and it still doesn't work. I was thinking of somehow downgrading to KitKat, use CM Installer which is how I initially rooted the phone and revert to a CWM backup that I made before I flashed the S4 GPE ROM and start over. However I tried using that CM Installer and since im on Lollipop it would refuse to work and I really wanna get back to how everything was before :'( I really dont know what to do (No warranty or anything on this S4) All I can do is make calls and texts. Please help!
fixed!
I've fixed it! Its all back on stock with the all that bloatware and useless features only problem now is whether there is a way to deleted this thread
First post, So hey everyone
So I rooted my phone around 6 months ago with CF Auto Root, everything went fine but i was still on stock ROM. So then i found the Alliance ROM and decided to flash that because it looked cool. I flashed it using FlashFire to ensure I keep root. Everything worked and booted just fine, really smooth and of course it looked awesome. One small problem though, I could not send messages but I could receive them. Probably a SMSC (that was around 3 hours of head ache attempting to fix that) issue or because Straight Talk didn't like my phone using Android 5.0. So then I tried downgrading to Alliance 4.4.2, NOPE. That was the end of my phone :'(
Im now stuck on the Galaxy S5 screen with "Set Warranty Bit: Kernel" in the top right. No idea how to fix it and obviously knox was tripped but that isnt a huge deal to me.
I have tried the following.
1. Tried to reroot (seemed to fix a lot of issues actually)
2. Tried to reflash Alliance ROM android 5.0
3. Multiple cache and system wipes.
4. Installed TWRP through Odin but thats useless because I was dumb and deleted my back up in the system wipe
Im currently downloading stock ROM but my hope for that is fading judging that TWRP even stalls out and the phone reboots right when it attempts to flash. - well this was a bust, there are 4 freaking md5 files. when i go to flash with odin it says it a modem and then fails
What i have access to:
1. Recovery
2. Download
Is my phone already 6ft under or is it hanging on for dear life?
Edit: Should also mention that my galaxy is a SM-G902L (Straight Talks' model???). CF Auto Root for Galaxy SM-900F was used to root. So that is what i based my choice for model when installing Alliance
Ok so recent update, When I go into reboot and do system or whatever, it says there's no OS installed. I guess that would make sense why it doesn't want to boot, because there's nothing to boot into... but why cant i install any OS through odin???
Another Update: So I have no OS, I know how to flash a new OS, such as a custom ROM, but my phone refuses to accept the flash whether through odin or through TWRP.... W.T.F. Did i really look my phone down? And I guess that means that I will need to get the Straight Talk variant of Android 4.4.2 Great If anyone has the a backup and they are on straight talk, please help me out
Thanks for the help!
FIXED!!!
So after around 14-16 total hours of headaches, I have managed to bring my phone out of the grave. I read over the Straight Talk Variant Galaxy S5 thread multiple times and saw people saying that most Verizon ROMs work decently if not perfectly fine with the SM-G902L. So I downloaded M.O.A.R ROM and flashed through TWRP.
Worked like a freaking charm!! She booted right up, into the waterspout boot animation, and after a very long 5 minutes, I got to the welcome and setup screens!! I guess it was just a matter of finding the right ROM. I just find it kind of weird that it would flash Alliance just fine and then not allow it the second time...
Anyway, the very helpful thread that saved my phone
http://forum.xda-developers.com/galaxy-s5/help/galaxy-s5-straight-talk-variant-sm-s902l-t3162340
Not sure what noob mistake I made here, but i can only flash CM based roms.
I unlocked the bootloader and loaded TWRP no problem. I've been running CM for months but wanted to try something else. I went with Resurrection Remix and realized i had no GPS. So i tried AICP, no GPS, Then Mokee, no GPS, then back to CM13 which worked before... No GPS! I saw threads saying to load rom based on stock and gps lock then reflash, so i tried but nothing else will boot!
g900v
Using twrp 3.0.2-2
No Boot.
Note5 Port
BS FREE
vzw stock something.. i already deleted this one and can't remember which it was now.
They all just bootloop.
What am i missing? Or if there is a gps fix i don't really care about loading non cm based roms, as thats likely what i'll go with in the end, but i need gps.
Flash a close to stock rom such as a rooted touchwiz rom in twrp
[email protected] said:
Flash a close to stock rom such as a rooted touchwiz rom in twrp
Click to expand...
Click to collapse
Thanks i tried a ton of stock based roms and nothing would load.
I tried to go back to stock on PD1 and that didnt work either. even after flashing kernel and stock rom through odin, it would lock on the verizon logo. no amount of factory resets or thread recommends helped. I ended up going to PB1 stock using odin and that fired right up after a pb1 kernel flash.
So i'm back at pb1 stock now, which is borderline unusable without root if nothing more than the constant dust cover notifications and update notifications that i can't seem to stop.
At least gps and everything works 100%. guess ill be following the pb1 root guide at some point soon. or maybe ill just do the ota to pd1, at least in 6.0 you can disable notifications on apps which would solve some of my issues..
Ok glad to hear you got it figured out
Sent from my SM-G900V using Tapatalk
I actually just ran into the same thing but I'd like to try and figure it out so I don't have to odin after updating ROMs. Hopefully my TWRP log attached. (Originally it was 9mb so I trimmed it down.)
This is my first time reading recovery logs but it looks like it's having an issue writing to some areas. I read on the net that someone had a similar issue due to encryption. I have never knowingly enabled encryption but i do use fingerprint lock. I tried removing that completely and testing again but get the same errors in the log. TWRP doesn't display any errors at time of flashing a TW ROM that I noticed.
Running latest TWRP 3.0.2.2 (i think that's it) using CM13. Tried multiple TW ROMs (and downloading) but other custom ROMs work fine.
Any thoughts?
Sent from my SM-G900V using Tapatalk
Sorry, I only now realized my logs never attached. Anyway, I was able to get it straightened out although I never determined the root cause.
I completely started over from scratch, odin to stock, root, unlock bootloader. I did continue to have issues flashing ROMs (including CM now) but finally resolved that by failing back to TWRP 3.0.0. Now I can flash Cam and TW ROMs again. I made a TW nandroid so if the GPS goes out again I should be able to easily do the CM->TW->CM trick.
I may have been firmware or partition corruption that CM just didn't care about but there may also have been related to TWRP > 3.0.0.
Sent from my SAMSUNG-SM-G900A using Tapatalk