Database Info

Galaxy S4 i9500 rom written to i9505 device!!!NEED HELP.

Hi guys.I am new to forum so i didn't know where to open this thread.Also i have checked internet for a solution but never seen a dumb thing like this before in my life.So even google search engine couldn't help me about that.
One of my friend has purchased a device from dubai.it is an original device of i9505 with snapdragon 600 processor.I am personally using an i9500 octa version btw.my friend told me to check his device after he had problems with gsm service+wifi for 3g doesn't connect(or connect and drops fast) so i went to check his device.i have used some system info tools and benchmark softwares to identify the device is ok.but NO IT WAS NOT OK.all of the system info tools says that the device is i9500 but it has snapdragon processor.some idiot somehow managed to write i9500 rom to i9505 and it is working with problems.i have checked camera both ok frontal and rear.and other device properties working good as well.i should expect that it should even fail to boot but somehow working with great deal of no phone service+3g problem(phone service sometimes work i really don't know how it works or how it fails).
So i decided to make things right.Which is put the right original galaxy s4 i9505 rom to that device.i have checked sammobile and found germany version of kitkat.
general info : device is rooted.it says it has Wanamlite rom 4.2.2.
My Try list:
1)downloaded odin 3.09 and followed the instructions.(used the official rom given from sammobile.)and put the mobile to download mode(i couldn't do it with volume down+home+power button cos it is not working)but i thought i was lucky cos that custom rom had an option when i push the power button/restart/ it says there is a download menu so i choose that to put the device to download mod.after that i was hoping odin will do the job.but it FAILED DUE TO WRITE PROTECTION ENABLED on device.
2)i tried to setup cwm recovery to device(which i figured out later it was already on device but i didn't know it was there).downloaded rom manager from playstore.and i thought it would work.rom managers says i had 2 recovery programs or rom managers on the phone 1 is cwm and other is teamwin recovery.also rom manager asks me to update or upgrade cwm but it does't recognise the device cos it is i9505 with i9500 rom and rom manager couldn't identify the device as it should be.so cwm update doesn't work.also i couldn't get to the user interface of cwm which is already on the device no matter what i do.also i know old version of cwm will not make it happen for what i need to do if i was able to get in the user interface as well.i think teamwin is blocking cwm.
so on rom manager i decided to use the team win cos there is no other option for me there which puts the phone after a restart to recovery mod,the user interface works ok there but teamwin also FAILED TO WRITE THE ROM(i think it is an old version too)i couldn't say the exact version of cwm cos the device is not with me and i forget the version but team win i asked to my friend just yet and he said TWRP 2.6.00 is on it.
3)CWM i can't even get to user interface,i really don't know how to with team win there.So yeah i couldn't even give a try.
4)I am stuck.and i don't know what to do.
general user profile about me: i have a general understanding of computers,but i haven't written any rom to galaxy s4 before yet i found myself in a situation i can't handle.someone screwed up an i9505 with a i9500 rom.
ANY HELP FROM ANYONE will be very appriciated.

i have managed to upgrade tw recovery with flashify to final version but in odin still write protection is enabled in the download mod.so odin again failed.btw after upgrading tw with flashify i lost my ability to get into operating system.i just have tw recovery on the screen atm.
the rom file i tried is this one I9505XXUFNB8_I9505VFGFNB3_I9505XXUFNB8_HOME.tar.md5 which i have downloaded from sammobile.
I9505XXUFNB8_I9505VFGFNB3_VOD.zip vodafone version it says for uk.
now i have a screen of tw recovery when the device opens.strange thing is i have 2 versions of tw recovery installed at the same time.when i press volume up+home+power tw version 2.6.00 loads.
or when i open the device with only power button tw recovery 2.7 loads.no operating system yet.
i tried I9505XXUFNB8_I9505VFGFNB3_VOD.zip with tw. it gave me an error of md5 not found and failed.
what now?
anybody around there to help?
another note : i don't know if it is important or not but it says the product name is sghi337.checked google it says at-t network.is this a useful information or what to identify the problem?
all i want is any rom to make the device work again with fully functioning.

after having twrp 2.7 i tried some roms had md5 error,so after a search i wanted to try wanamlite rom wanamlite-xxufnbe-v2-4-android-kitkat-4-4-2-xposed.after installing wanamlite rom it has asked me to reboot.so i did reboot it.it had adam kernel 2.1 version.
i was expecting the device will reboot but thanks to at&t for making odin useless + making twrp useless as well.it had a message on the screen and it was written ''samsung custom'' with a locker logo open.i thought i have to wait for the first boot and be patient and after waiting about half an hour still nothing.(on the left up of the screen written red : kernel)i checked more than maybe hundreds of threads to find an answer about at&t sghi337 galaxy s4 and some ppl say i have to change the kernel.and some say i have to change it to at&t kernel i searched again for an at&t kernel i found a file name KT-SGS4-TW-JB-ATT-06-06-2013.zip.then i gave a try to that.but suddenly i realized i have lost the ability of booting to twrp 2.7.all i have left with is twrp 2.6.00 when i press volume up+home.still lucky to have it.i used that kernel reboot and got a message on the screen ''system software not authorized by at&t''.then i started searching again ppl say about loki doki.downloaded the file and flashed it on at&t kernel this time it showed samsung logo appeared and the boot sound which you know all of us familiar with and samsung led was blue.the led was like it is a pounding heart coming on and off.this should be the first load of the rom i thought again and waited and got no result.it didn't load again.failed failed and failed many times.
i also tried this file named MDOB-KERNEL2STOCK-LIB.zip.flashed it no result again.failed.this result was another strange thing.it was showing samsung custom logo boot it with sound and then turn the device off after 10 seconds.and repeats the process.reboots sounds and reboots again and again.
questions :
1) do i have a bootloader locked device?since i can't use odin to flash anything.(odin version 3.09) and if i have what can i do to fix it?
2)since i only have twrp 2.6.00 how can i upgrade it to 2.7 back with twrp.i mean twrp update using twrp.
3)with twrp 2.6.00 i used wanamlite rom kitkat version.and it says it has flashed it.but can it flash roms succesfully enough like 4.4.2?if it says it flashed everything is ok? or it misses some important features to make the rom work.what is the maximum capability of twrp 2.6.00.Do i have to try roms like 4.2.2?
4)about kernels with at&t i337 galaxy s4 what can i do?what should be the reason preventing the rom load successfully?if i have access to twrp does it mean i don't have to mess with bootloader cos i have already passed that step and got an interface for loading roms?i mean everything is ok with bootloader if i have twrp installed user interface? and after flashing a rom do i have to use the specific kernel coming with the rom or can i use any kernel for the device like stock kernels(doen't allow me to load) with loki doki or some kernels with loki doki?
i am so helpless,please enlighten me with your knowledge.any moderators or any developers can answer me?or help me?
stuck in the middle of nowhere.please help.

Getting some progress at the end!!!
Since twrp 2.6.00 is the only option i have,or i can say ''was the only option i had'' i knew i had to get an android user interface for upgrading my recovery.after a bit more search i found slimroms for android version 4.2.2 just to make the device run,and it is already loki patched.so yeah that rom flashed as lightspeed and loaded extremely fast!that worked!!! i have downloaded aptoide market since it was lacking google apps.and downloaded flashify to upgrade the version of twrp to 2.7.01.from now on i believe i can find my way to whichever kitkat rom that is loki patched would work with this recovery support.
THANKS TO SLIMROMS for making downloadable and flashable small sized roms and tnx for the guy whoever found the loki way to make it possible.Also great thanks to TWRP team!!!
PLEASE NOTE THAT : Why did i write this after no reply or no help or no messages to this thread?Because i have figured out my way reading,trying and hard pushing after failing a lot but i found my way with xda developers threads out there even no one ever replied for help.I mean thanks anyway :cyclops:

When in doubt, flash to stock ROM and proceed from there.

you mean to tell me u cant enter download mode? ask someone to press the 3 buttons together to enter it and flash the firmware specified for that S4.

[Q] Kind of new to the Rooting, but I need a bit of help.

Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.

Snake2594 said:
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Click to expand...
Click to collapse
wish i could help, but after searching i came up empty just like you.
you really need the stock file to even see if this is fixable.
in the future you really should make a backup after installing a custom recovery before flashing anything else, for cases just like this.

Snake2594 said:
Okay, so recently this week I rooted my Tmobile Galaxy note 3 SM-N900T model. I installed the Xnote Custom Rom and everything was pretty much fine.
This is where the problem started. I have a mobile app Called Odin Mobile, which I used to actually Custom Rom Flash, because I didn't see the option during the Bootloader to where I'm able to Custom Rom flash it from my external card, so I bought the Odin app to help me do it mobile and use CW Recovery to handle it. Now I went to find a wifi patch, because my wifi would NOT work with this Rom at all, I found a patch to install, so I used Odin Mobile Pro to simply just Flash the install on it and hope it would go through after a bit of research. Now my phone I believe is Paperweight softbrick. It doesn't go past the Xnote KitKat Menu of 4.4.2. I can't do anything, even worse my computer isn't reading my phone to where I can just get the files from my phone or external Microsdcard.
What should I do ? I'm pretty helpless at the moment. I even went to try and find a Stock Rom for my Model number which is the Tmobile Model Number: SM-N900TZWETMB Variant, I haven't been able to locate any, my only hope from what I'm reading, is to find a Stock Rom of 4.4.2 with my model and use Odin and hopefully that works, but I'm not able to locate anything, and the internet here is pretty horrible. If there is anything anyone can do to help me I appreciate it.
Click to expand...
Click to collapse
Your phone is bricked. You should find a file of the stock rom and flash it via odin. Remember you can flash any note 3 firmware onto any note 3, so I'd recommend you to find the rom file of the international version of your phone (which is the N9005). Remember, if you're able to boot your phone into flashmode, you'll always be able to unbrick/repair it.

|>/\nte said:
Your phone is bricked. You should find a file of the stock rom and flash it via odin. Remember you can flash any note 3 firmware onto any note 3, so I'd recommend you to find the rom file of the international version of your phone (which is the N9005). Remember, if you're able to boot your phone into flashmode, you'll always be able to unbrick/repair it.
Click to expand...
Click to collapse
Okay thank you for the info, I actually fixed my phone not a couple of hours, shortly after this post. What I did was get the latest Clockworkmod, mine was an old version and didn't have the Install option, when I used Odin, I use the updated Version and was able to Wipe my data, then simply Reflash the Custom Rom and solved my problem. Soon as I got my phone on, I instantly went and Nandroid, so.....won't be doing that again.
I actually didn't know I can flash any note 3 firmware on my phone, least the Tmobile versions, good to know. I'll find em and keep on my computer just in case. I still have the wifi problem, so hopefully I can tackle that down and learn to patch my rom.

Snake2594 said:
Okay thank you for the info, I actually fixed my phone not a couple of hours, shortly after this post. What I did was get the latest Clockworkmod, mine was an old version and didn't have the Install option, when I used Odin, I use the updated Version and was able to Wipe my data, then simply Reflash the Custom Rom and solved my problem. Soon as I got my phone on, I instantly went and Nandroid, so.....won't be doing that again.
I actually didn't know I can flash any note 3 firmware on my phone, least the Tmobile versions, good to know. I'll find em and keep on my computer just in case. I still have the wifi problem, so hopefully I can tackle that down and learn to patch my rom.
Click to expand...
Click to collapse
Just to mention it, that doesn't work only for t-mobile samsung phones. As I said, you can flash any note 3 firmware onto any note 3. I recommend the international version because it's generic, and generic firmwares are always the best ones, with as little bloatware as possible.

Help Deodexing stock rom-Verizon i535PP

im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated

bjf189 said:
im in need of help deodexing. i used the universal deodexer and didnt get proper start up. it became stuck on verizon logo. i reflashed the firmware so its like new again. question is how to properly deodex the stock rom so i can theme status icons? maybe some zip file that i can use in safestrap to make things easier. oh im using verizon prepaid galaxy s3 which is i535PP. any help is appreciated
Click to expand...
Click to collapse
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5

Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)

ShapesBlue said:
If root can even be obtained this might be an option, otherwise your probably out of luck
Sent from my Nexus 5
Click to expand...
Click to collapse
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5

ShapesBlue said:
Ok, there wasn't really a need to mention me in this thread. Everytime someone does that I get an email. And just because root has been obtained doesn't mean you can flash roms via safestrap
Sent from my Nexus 5
Click to expand...
Click to collapse
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.

OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Its cool. Good to see safestrap works on the prepaid version also
Sent from my Nexus 5

I'm not sure what a bash terminal is unless it's the same thing as the terminal emulator. I tried using that rom that's called paulpizz or something like that. I used some other rom to. The paulpizz one always failed to install even after downloading it a third time. The other one i can't remember the name but it installed but wouldn't start at all. It would just go black and bootloop and goes into stock recovery for some reason. I came across the nf5 module when i found that paulpizz rom on the goo server they hosted it on. So i got the module and i figured if i were to flash the module over the i535 rom that it would fix the wifi an data problem but never got an answer because it always failed to start up properly and would just bootloop into stock recovery. Ugh Verizon is making things so difficult with modding lol. As of now I'm just using xposed to get at least some theming in and tweaks. I couldn't get any deodex program to work. Whenever i used the deodex files and pushed them to the system of apps and framework, it would restart and just stick on the Verizon logo. So i had to flash the firmware to fix the problem.

When i was on 4.3 with this phone safestrap worked and i got the wifi and data sim error. Now that i got it replaced I'm running the kernel of July 22 2014. Everyone was saying I'm out of luck but i came across kingroot and got the most recent version and it worked. I have root. Installed safestrap for 4.4 and it runs fine but can't get any custom roms to boot. I only managed to find one 4.4 touchwiz rom unfortunately

OpenSourcererSweg said:
Root has been obtained @ShapesBlue
Nobody has created a ROM for i535PP users yet(the i535 roms run but no wifi/data). And you're correct about having to use safestrap to flash it.If you're comfortable with a bash terminal you can try using one of the various tools found around here to modify the stock rom. If you're not then I'll see what I can do this weekend and try to get something for us i535pp users (after a day or so of testing)
Click to expand...
Click to collapse
OpenSourcererSweg said:
Flashing via safestrap appears to work fine on my i535pp. The only issue I ran into was wifi not working with roms meant for the i535. And sorry for you having to receive an email for that.
Click to expand...
Click to collapse
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something

bjf189 said:
Can you tell me what rom you have successfully flashed with safestrap? I would like to test something
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.

OpenSourcererSweg said:
http://forum.xda-developers.com/gal...iterom-v1-0-i535vrudne1-t2805797/post53919312
If you're going to try flashing an i535 rom and then the i535pp modules let me know how that goes, can't test as I won't be able to do anything till the weekend. If that's the case then there's no need for roms for the pre paid version. Cyanogenmod was also bootable but very buggy.
Click to expand...
Click to collapse
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader

bjf189 said:
I'll let you know how it goes and thank you. How is it that you were able to boot CM? From my understanding being that the bootloader is locked and has Knox for extra security to make the unlocking like impossible. But a genius came up with safestrap so we are able to use some custom roms but the down side is that it has to be the same Android OS and has to be a touchwiz based rom. So how are you getting lucky with all this? I love CM and I'd pick CM over any custom rom any day but i gave up an lost hope of ever getting CM because of the locked bootloader
Click to expand...
Click to collapse
Safestrap 3.75 had support for AOSP roms (wifi/data didn't work for them either) and 4.0 dropped support for that (there is currently no point). Read the thread for more info http://forum.xda-developers.com/showthread.php?t=2797314

Ok i wasn't using safestrap 4.0. I had 3.75 B05 which i thought was the latest version they had. I'm updated to 4.0 now and about to test the modules on the superlite rom

Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't

bjf189 said:
Update: i have tried the super lite rom using safestrap. The boot animation won't work during start up. When it gets to the welcome screen it freezes. It still does it even without applying the nf5 module. It freezes and will keep popping up that system isn't responding. System just keeps freezing and prompting me to wait or force close. So not sure why my s3 has a problem running it but yours don't
Click to expand...
Click to collapse
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that

OpenSourcererSweg said:
Did you wipe cache/data after installing? Other than that I can't think of anything that would cause that
Click to expand...
Click to collapse
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?

bjf189 said:
Well no. The instructions just said to do a full wipe off everything then install and reboot so extra what i did. What version you running of the rom?
Click to expand...
Click to collapse
I'm running the stock prepaid rom, not superlightrom, sorry if there's any confusion there.
When I tried out superlightrom (quite some time ago) it appeared to work fine (excluding wifi/data and nagging about no SIM card being inserted, nothing like what you're describing) and I went back to stock.

Oh ok. Well it seems that the prepaid version or the s3 in general is dead. That's unfortunate

Root on PD2 6.0.1 Sprint S6 Edge/TWRP 3.0.2-1.

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

change baseband and firmware

hello
i have a galaxy s6 920F zerofltelgt
i had first a stock rom with android 6 installed on it
so i've install TWRP then a custom rom
i tried this one: 10 LineageOS-10-zero-multitarget-2020-04-13_2047 17.1
but the phone cant boot even i try flashing it multiple times and reboot the phone many times
i also tried this one:
10 EvolutionX_4.3_zerofltexx-10.0-20200511-1751-OFFICIAL
but i always get problems in calling and the phone call apk tells me the the call in ended while it is not, when i try to make a call it takes me to the previous one
i tried this one:
9 Havoc-OS-v2.1-20190129-zero-common-Unofficial
but i get lot of bugs, for example: when tring to open the dialer the phone stuvks in a dark screen, when i click night mode the screen turns dark
so i start thinking that the problem is in my phone and not in these roms
in this topic:
https://www.getdroidtips.com/havoc-os-samsung-galaxy-s6/
they wrire: You should be running the latest firmware on Samsung Galaxy S6: Download.
so i think the problem is may be here. and i dont know what to do now
my current baseband is: g920kkku3dpe3
my kernel is: 3.10.108 hyper flx
do i need to flash the phone with a v7 android version? (G920FXXU6ESA1 ) or there is a way to just flash the needed partition?
i hope that you can help
Edit: i've flashed Stock 0920k rom via odin then custom ROM
but i still have the same problem with Havoc OS. that what i've tested now

ARDV said:
hello
i have a galaxy s6 920F zerofltelgt
i had first a stock rom with android 6 installed on it
so i've install TWRP then a custom rom
i tried this one: 10 LineageOS-10-zero-multitarget-2020-04-13_2047 17.1
but the phone cant boot even i try flashing it multiple times and reboot the phone many times
i also tried this one:
10 EvolutionX_4.3_zerofltexx-10.0-20200511-1751-OFFICIAL
but i always get problems in calling and the phone call apk tells me the the call in ended while it is not, when i try to make a call it takes me to the previous one
i tried this one:
9 Havoc-OS-v2.1-20190129-zero-common-Unofficial
but i get lot of bugs, for example: when tring to open the dialer the phone stuvks in a dark screen, when i click night mode the screen turns dark
so i start thinking that the problem is in my phone and not in these roms
in this topic:
https://www.getdroidtips.com/havoc-os-samsung-galaxy-s6/
they wrire: You should be running the latest firmware on Samsung Galaxy S6: Download.
so i think the problem is may be here. and i dont know what to do now
my current baseband is: g920kkku3dpe3
my kernel is: 3.10.108 hyper flx
do i need to flash the phone with a v7 android version? (G920FXXU6ESA1 ) or there is a way to just flash the needed partition?
i hope that you can help
Edit: i've flashed Stock 0920k rom via odin then custom ROM
but i still have the same problem with Havoc OS. that what i've tested now
Click to expand...
Click to collapse
Just flash latest Stock firmware first and you're good
Yes Android 7 latest stock version

Johannesdavidsen said:
Just flash latest Stock firmware first and you're good
Yes Android 7 latest stock version
Click to expand...
Click to collapse
yes i did, i flashed the latest stock rom:
G920KKKU3ERG1_G920KKTC3ERG1_KTC
i'm now using this rom:
FloydRom_V5.1_Exynos7420
i still have the calling problem, i cant make add call, when i click it the phone caller bugs and i cant hear the first calling and the calling screen goes off and i cant get it back. and also when i get a waiting call it bugs, i cant hear the first one and it tells me: call ends. but it is not end.
i cant stay with stock 7 rom because i really need the dark mode and the night mode.

ARDV said:
yes i did, i flashed the latest stock rom:
G920KKKU3ERG1_G920KKTC3ERG1_KTC
i'm now using this rom:
FloydRom_V5.1_Exynos7420
i still have the calling problem, i cant make add call, when i click it the phone caller bugs and i cant hear the first calling and the calling screen goes off and i cant get it back. and also when i get a waiting call it bugs, i cant hear the first one and it tells me: call ends. but it is not end.
i cant stay with stock 7 rom because i really need the dark mode and the night mode.
Click to expand...
Click to collapse
Try this page: https://androidfilehost.com/?w=files&flid=313737
if your phone is:
flat select: zerofltexx [it has f ]
If it is edge select: zeroltexx [no f here.]