Hi everyone,
Right I have a serious issue with a 4 day old S6 from the UK bought SIM-Free off Amazon.
My phone was rooted but didn't have ADB or any sort of custom recovery. I edited the build.prop file for the RAM management thing, and created a copy back up on my storage. I didn't like it too much, so I copied the back up over the edited one and restarted - phone went into boot loop.
I have attempted to use Odin and flash a stock firmware ROM (had to settle for a H3G variation because the XEU unbranded was off some download website that takes 10 hours to download). I went through all the steps with Qbking77's walkthrough with Odin and it came up that it failed at the end.
The phone then booted into the Emergency Recovery screen, and couldn't get back into Recovery (to do the Smart Switch recovery), and can only get back into the Download bit.
I've tried flashing it again, and no avail.
I seriously, seriously hope someone can help me out here, it's a brand new phone and I love it and I don't want to be left with a brick.
Thanks.
I was in the same boat, if you rooted and didn't trip Know, your best bet is the Samsung Store, they're all over the UK
Well an update:
After the third time flashing failed, I did a root via Odin which had previously failed, and it booted up, completely normal and set up the device as normal.
I have no idea how that worked - but it did. Probably tripped the Knox I think but it works.
Hey guys,
I've used XDA for quite a while now as a resource for rooting and flashing my phones. After some trial and error, I finally got a custom rom and root onto my previous phone, the Samsung Galaxy Light (SGH-T399). However, I booted the T-MOBILE kernel, not MetroPCS, and got locked out. So I bought a Galaxy Core Prime, and after a bit decided to root that as well. But when I did some sort of permission modification and tried to make my extSD writeable, the phone crapped out. It would not load the kernel past the bootloader. I tried flashing everything and anything. It just would not allow it to write or mount properly.
So I went back and tried restoring the T399 until I sorted that out, and the same thing is happening. I even flashed ShabbyPenguins stock rom which never failed me before, to no avail . I was able however to successfully install TWRP again. Someone please help me out, I can't afford another phone at the moment. Im still a novice, but I know enough to know it's more than just a mistake in Odin or a file I didn't upload. I've tried searching for an answer to no avail.
P.S. -I'm 90% sure it's a partition issue of some sort, where the filesystem isn't being communicated with properly.
Yo, I've been trying to fix the damned phone for ages now. I accidentally wiped it by being a dumb idiot. Now I'm trying to fix the situtaton. So, I've tried installing a stock firmware and just flashing it with Odin. After trying this with like three different Firmwares, and sequential failures, I moved on to trying to flash it with a custom rom using adb, as the s6 doesn't have a removable sd. So I tried this, It said it worked. I used an installer and everything. But after I reboot, it still says there's no os and I cant find the zip anywhere on my phone to install. I'm not sure what to do. I'm a noob with this hence why my phone is in this state. Help MUCH obliged, S6 edge Sprint
http://forum.xda-developers.com/showthread.php?t=3219484
Hi folks,
just posting this writeup thinking maybe it might be of help to some people.
Started with a clean S6 Edge straight from Samsung repair for broken screen. Factory wipe, KNOX reset. It had the PD2 update. Tried using Skipsoft's Toolkit and ponied up a donation to get the Pro version with the S6 Edge 6.0.1 update, but it didn't work: it got stuck at the "SEANDROID NOT ENFORCING" screen after flashing TWRP 3.0.2. I know there are issues with 3.0.2, but it's what's optioned in Toolkit now.
Flashing TWRP 2.8.7.0 results in normal boot, but I could not enter recovery mode for some reason. 3.0.0-0 didn't work, either.
What I ended up doing is forcing phone into download mode (Power+Volume Down+Home), ODINing TWRP 3.0.2-1. This resulted in a bootloop (somewhat expected). But I could get into recovery easily. From recovery, I flashed Renegade's PD2-Aroma V3.0 Full ROM via ADB sideload. After a very long first boot, everything works 100%! Root, SuperSU, etc., all taken care of. Hotspot works.
Notes and tips:
- While I didn't use Skipsoft's Toolkit in the end, it's still worth supporting. Might work smoothly using 3.0.2-1 instead of 3.0.2.0, but I'm comfortable with adb/fastboot/etc. so just ended up using that. If you don't already have Android SDK and tools/platform-tools, Skipsoft conveniently includes those commands in its directory under C:\Unified_Android_Toolkit (they're named adb-toolkit and fastboot-toolkit. You can copy and rename them as "adb" and "fastboot" for convenience).
- Make sure you get the right TWRP 3.0.2-1 device version. You want to use twrp-3.0.2-1-zeroltespr.tar.md5 for Sprint S6 Edge. Remove the .md5 part and set it to use the .tar extension (stupid Windows asks you to confirm file extension type change).
- In TWRP you can either push your custom ROM or sideload it. To push a file, move the custom ROM into the same directory you've got adb/fastboot for convenience. Open a terminal window in that directory, and either "adb push customromfilenamehere.zip /sdcard/" or in TWRP, click Advanced/ADB Sideload, and enter "adb sideload customromfilenamehere.zip".
- If you're sideloading it, it's gonna take a while, and will start flashing even while the transfer percentage is creeping up. Example: at around 9%, it started AROMA, around 14%, it went through some of the installation options. It was done flashing everything and ready for reboot even though the terminal window said only 76% was transferred. That's ok. Click "finish" in AROMA on phone, reboot. Unplug phone. Wait a long time for first boot (this took around 20 minutes for me). ENJOY.
Remember: all is not lost as long as you can get into download mode! Power-Volume Down-Home until you get to screen prompting to get to download mode. Volume up to select that mode. You can ODIN from here.
Additionally: if you find yourself for whatever reason stuck at the initial S6 Edge boot screen with "SEANDROID NOT ENFORCING," you might be in some kinda of boot limbo. I was able to issue some adb commands here, even with recovery was borked and the phone didn't boot all the way. Doing an "adb reboot-bootloader" would let me do a complete boot to ROM while I was trying to get the different TWRP versions working (until 3.0.2-1).
Hope this helps someone.
tl;dr: For PD2/6.0.1 Sprint S6 Edge, manual flash TWRP 3.0.2-1. Push custom ROM through Recovery. Reboot, wait a long time. Success!
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN latest TWRP 3.0.2.1 - HERE.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Alpine- said:
Just to Clarify (and mostly for myself), I think this is the simplest and most foolproof way to get yourself fully update and on a custom rom with root.
1. ODIN Stock PD2 Image. Reboot, make sure dev options + USB debugging is enabled.
2. ODIN Ram's TWRP 3.0.2 - HERE I'm assuming the other guy's 3.0.2 works fine too, I am not sure why you hung and had to revert to a 2.x TWRP build.
3. Obtain root by going into TWRP immediately after you install it and flashing the root kernel Ram did for this device - HERE
4. Then after wiping cache, dalvik and data in TWRP, flash Renegade ROM 3.0 PD2.
Using CFauto root method is known to cause issues. This is the type of approach I took and it was flawless. The initial boot of the Renegade ROM can seriously take like 20min though, I thought I was looping for a second.
If anyone disagrees with this method or sees where it can be done better, please advise. This seems to prevent the instance of any loops or issues. The Renegade ROM has a rooted kernel so flashing the root kernel is likely a redundant step. You could omit Step 3 if you are flashing a custom ROM, probably, but it seems to prevent any hangups. But if you plan to stay stock, you still have to flash a rooted kernel after TWRP.
Click to expand...
Click to collapse
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
baknblack said:
I noticed chainfire now has a CF-autoroot for the 925P 6.01 and people were having success using the one for the 925F. Any verification on this? Haven't seen anyone on this forum say anything about it. I just bought a new S6 edge for sprint. I always am about year behind on phones because of the high cost of the latest and greatest. I picked the edge because my wife has had one a year and it gets a lot better reception than my N5. But, I gots to have root and don't wanna screw up a new phone. I know the first thing I need to do is check which software it's running. Should I do this before I activate it or can i stop any system upgrades before they install?
Click to expand...
Click to collapse
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Alpine- said:
I have not attempted to use CF-autoroot just because of reported issues and the general recommendation being to use the standard method. It may work fine now that its been updated, but I have not personally tested it.
Click to expand...
Click to collapse
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
baknblack said:
I just bought my phone new off ebay it updated to PF4 just as soon as I activated it. I couldn't stop it. Anyway I used the CF autoroot on it and it worked perfectly. I tried to do it manually a couple times first and never could get TWRP to flash. It would say it was successful but, stock recovery stayed. Anyways, I got er done and running Renegade wich btw is an awesome ROM. This is my first samsung device and had I done a bit more research I'd of known the majority of development is on the regular S6. I just picked the edge because my wife has one and it worked so much better in the boonies than my N5 did.
Click to expand...
Click to collapse
Edge is better imo, certainly looks better. All you need is Renegade rom anyway. May be a few more roms in active dev for s6 but nothing better per se. Renegade rom dev is alive and well.
Would these root methods trip knox?
chen69chuck said:
Would these root methods trip knox?
Click to expand...
Click to collapse
Yes
Thanks.
Working for g920v 6.0.1?
freaking thank you been struggling with twrp on and off for two days trying to bring this phone back from the dead! YOU the man
Hi all,
Before you jump at me telling me I haven't searched the forum, I DID and I couldn't solve my issue even with these solutions. To get you up to speed on what exactly I did.
Briefing (not very important):
I was doing my own business and I was free, I use my phone daily and it served me well. But I noticed that the last security patch I got was on 2020 and got me thinking. Why not just use custom ROMs to update my phone and get a year or two from my MIX3 (2018). I just recently flushed my brother's phone (Samsung) with a custom ROM and I liked it. I already installed TWRP 3 years ago on my brother's phone and I just had to install a zip file and boom new Android 12 on a 2014 phone.
The problem:
after reading here on the forums, it seemed that it is more complicated to do. I'm up to the challenge, I have done it before and the reward is worth it.
+Unlocking the Bootloader
this was a bit easy other than the connection issues but I got it unlocked eventually. (use the QR code to sign it. it is much easier)
I had an issue where after unlocking the bootloader the phone didn't allow me to install TWRP and do a backup, it immediately went into erasing the entire phone.
+Installing TWRP
I downloaded the files from TWRP website and everything was smooth other than the Mi Recovery popping every time I restart (install Magisk to plant TWRP then remove it if you don't need root)
+The downhill
after restarting, the phone worked fine I installed all the apps and restored everything. Afterward, I noticed that the camera does not work. It gives me an error. I reinstalled TWRP again since it was reverting to its Mi Recovery and I think here was the problem I flashed the recovery.img into the boot partition by mistake (I didn't notice at first) but after going back to the command I saw I made a mistake and reflashed the recovery with recovery.img and installed the Magisk and everything was ok. At the initial start, the SIM and the WIFI are not working.
after several attempts at reinstalling different flashable stock ROMs, I saw that the issue is consistent. I read online that you have five .img files that control the different parts of your phone. I got tired and decided to reflash the stock ROM via the Mi flasher and get it back to stock.
Even after flashing the stock ROM, I'm still having the same issue.
I reflashed the modem.img in the modem and still wifi and sim card are not working
I read that some phones have an A/B partition and my phone does NOT have it.
I'M AT A LOSS I CAN NOT FIX IT. IT'S BEEN 3 DAYS ON THIS AND I CAN NOT FIGURE IT OUT!!
Ok, If anyone was passing by I think I found what was the problem.
First, check if your problem matches mine. Go to Settings and check your IMEI. Or just dial *#06# ,if your phone did not return with a number then you lost your IMEI number.
follow this guide and I hope it helps. this is only for some phones so don't try it, it might break your phone
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com