Hey guys, first time on this forum because I've run out of options otherwise. So last night i decided to finally root my phone after reading about it a lot. The root it self went just fine and it was working great. I then tried to download xposed using TWRP. However, that put my phone into a bootloop. It keeps restarted after it comes to the Samsung logo. I did some research and people said to simple put it back to the stock firmware so i downloaded some ( had trouble downloading because sammobile wouldn't work for me) However, now every time I try to flash it back to the stock firmware using odin it says failed and comes up with an error on the phone saying SW REV CHECK FAIL DEVICE 3, BINARY 1. The phone is a SM-G920W8. Any suggestions cause right now I have a $700 paper weight and no back up phone. I'm kinda freaking out haha.
Thanks for the help. I can send screen shots if you guys need them.
same problem.is there a way to install xposed framework without these annoying problems?
how to install the custom recovery and xposed properly?
Yeah, use the correct Xposed for S6.
There's an uninstall tool for the Xposed you've already installed (look in OP for Xposed you installed), that should have been your first step after bootloop. Try now, see if it will uninstall.
There's a Windows tool called SamFirm, or an Android app + website called Updato, use those to download stock ROMs if you still need to.
Then search for Wanam Xposed s6, and use that version.
Sent from my SM-G920W8 using Tapatalk
Related
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
the files that you use to odin with are a different extension (.tar) than what you flash with (.rar)...so you can only use cwm/twrp to use that rooted image. I recommend using odin to get back to stock, then using the root one click method that was recently stickied...that will get you up in running and able to use roms quickly
Yes its possible but first try to install a custom recovery. Download goomanager and then install open recovery script from the menu options. Then you should be able to boot into twrp and flash a new rom
Sent from my XT912 using xda app-developers app
eyc said:
My wife's rooted Samsung Galaxy S3 (vzw) has been acting strange lately. It has been asking to update and then locking into a screen that says "System software not authorized by Verizon..." I can successfully reset the phone, as well as get into Odin, but I cannot get into recovery mode to flash a new rom. (The first and only rom I flashed on her phone was stock Touchwiz about 8 months ago.)
I'm kind of a noob at this stuff, so I'm not sure what to do. First, I'm not sure why this is happening in the first place. My research shows that it can happen when you don't unlock the phone properly, but I'm virtually certain I did. In any event, what next? I have read that I should Odin back to stock. Is it appropriate for me to attempt to Odin back to a rooted stock rom? Is that even possible? For example, can I Odin back to this rom (http://forum.xda-developers.com/showthread.php?t=2332840)?
Click to expand...
Click to collapse
If you are Verizon Stock rooted and have SU and busybox installed without disabling updates, that will occur whenever Verizon rolls out an OTA. if you want the update, ODIN back to stock and take the updates before rooting. If you don;t want updates then find the thread on disable Verizon OTA and that will stop the update request.
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
TBH. im a noob at all of this.
i rooted my phone because i wanted to use g3 tweakbox app. I did successfully root my phone.
Recently i got an update on my phone. In which i did update my phone. software currently is 4.4.2. im guessing it was 4.4.1 before, not too sure. Still android kit kat despite lollipop already being out.
The problem i run into right now is when i open g3 tweaksbox, i get an error message saying 'the module is not enabled or xposed framework is missing...". i then opened xposed and Xposed gives me an error message saying "the lastest version of xposed is currently not active. did you install the framework and reboot?" ive searched all day to figure out why this is the problem but i havent been able to find a solution. I also got an error message in supersu saying that "there is no SU binary installed and superSU cannot install it".
I looked into resetting my phone, but i can not get anything to backup at all. Ive tried many placed to back up my stuff too but all fail. Im guessing its because im stuck between these two worlds right now: between a stock phone and a rooted one. Idk how to fix it and i cant back anything up anywhere. i also dont want to lose all of my stuff on my phone just by hitting the reset to factory button on my phone. Can yahll please help, thank you. my phone does run fine but im just not the type that leaves the problem alone.. i want to fix it but i cant cause im just stuck right now.
akshaythakor said:
TBH. im a noob at all of this.
i rooted my phone because i wanted to use g3 tweakbox app. I did successfully root my phone.
Recently i got an update on my phone. In which i did update my phone. software currently is 4.4.2. im guessing it was 4.4.1 before, not too sure. Still android kit kat despite lollipop already being out.
The problem i run into right now is when i open g3 tweaksbox, i get an error message saying 'the module is not enabled or xposed framework is missing...". i then opened xposed and Xposed gives me an error message saying "the lastest version of xposed is currently not active. did you install the framework and reboot?" ive searched all day to figure out why this is the problem but i havent been able to find a solution. I also got an error message in supersu saying that "there is no SU binary installed and superSU cannot install it".
I looked into resetting my phone, but i can not get anything to backup at all. Ive tried many placed to back up my stuff too but all fail. Im guessing its because im stuck between these two worlds right now: between a stock phone and a rooted one. Idk how to fix it and i cant back anything up anywhere. i also dont want to lose all of my stuff on my phone just by hitting the reset to factory button on my phone. Can yahll please help, thank you. my phone does run fine but im just not the type that leaves the problem alone.. i want to fix it but i cant cause im just stuck right now.
Click to expand...
Click to collapse
Try installing the Framework again from Xposed Installer. Disable and enable again the module and reboot.
Try to do this
Xposed installer
Go to Xposed module
Check the tweaks
Then go to
Xposed framework
Click install /update
The it will asked to reboot
Then click OK
That's it
Sent from my Xperia Z2 using XDA Free mobile app
Maybe you lost your root with the update, get the root checker ap to find out
Sent from my LG-D852 using XDA Free mobile app
Update probably unrooted your phone.
hey all
I did a basic root on my samsung galaxy s6 a few days ago. just installed superSu and gave me root access. after that I installed TWRP which I then used to try and install the xposed framework. From then on my phone is stuck on the samsung screen saying kernel is not seandroid enforcing. I downloaded the stock rom for my phone (sm-g920F on 6.01) and attempted to flash it via odin 3.07 but it always failed after the sboot.
i have searched to try and find a solution but nothing I can find will work. can anyone help?
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
vickstew2000 said:
so i got my s6 working after flashing a full stock firmware i found via a link on this forum (i forget which one...sorry)
it gave me BL_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
AP_G920FXXU3DPBG_CL7086820_QB8626574_REV02_user_low_ship.tar.md5
CP_G920FXXU3DPB6_CL7086820_QB8569466_REV02_user_low_ship.tar.md5
CSC_BTU_G920FBTU3DPB1_CL7140831_QB8460122_REV02_user_low_ship.tar.md5
it also recommended that I flash the pit file ZEROFLTE_EUR_OPEN.pit.
this was all done via the latest version of odin. initially, the flashing failed at cm.bin so I reflashed omitting the bootloader and all seemed to be well.
My phone set up fine and then I realised that it will not recognise my sim...or any sim for that matter. in settings under sim card status...every entry is listed as unavailable. IMEI is unknown as is baseband version.
i realise that I have obviously messed up big time with the initial flashing (uhuh....backup...backup....backup) but I would really like some help to get my phone back up and running as a ...well...phone.
any help or suggestions would be most appreciated.
thanks in advance x
Click to expand...
Click to collapse
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Rosli59564 said:
Try smart switch. Not sure if it could restore the imei but it could bring the phone back to original csc when you bought it.
Sent from my SM-G925F
Click to expand...
Click to collapse
i had tried several times to connect to smart switch but it would not recognise my phone. after a lot of faffing about I finally managed to get it to do an emergency recovery and all seems well so far. it even restored my imei number so thanks for that suggestion Rosli. much appreciated xx
When u install xposed did u ude the special wanam version of the framework
Would say whipe cashe and wait a little while for stock roms like 40 minutes after first time install
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Devansh_Droidgeek! said:
So first off I would say I am average in the world of modifications, I know the basics. I used to run a stock Nougat rom with Magisk.
Being the clumsy fool that I am, I dropped my phone and the screen broke. I went to a Samsung service center and deposited my phone there for screen replacement and they decided to update my phone for no reason...
As my phone was rooted, after forcing an update on my phone a soft brick happened and they had to flash a new firmware which meant that I lost everything. Now I am running latest stock Oreo 8.0.
I tried these things to root my phone again:
(The first thing I did was flashing twrp through odin)
#1: Downloaded Magisk and a decryptor for getting past the locked bootloader... flashed them both using recovery (twrp works 100%), and my phone got stuck on the Samsung S7 - powered by android after a reboot from recovery. Waited for a long time. Tried a lot of alternatives on this method but got stuck..
#2 After I gave up on rooting the firmware I was given, I decided to go back on my old Nougat firmware which used to work flawlessly... so I had the nougat firmware on my computer but this time Odin gave me an error along with some red text on top right in download mode. I looked up the error and it basically meant that I cannot revert back to Nougat anymore (which is surprising as I could easily swap between Nougat and Marshmallow but I can't do the same with Oreo and Nougat)
Quote from a person on the internet: ''SW REV CK FAIL usually means that you are not flashing the most current released firmware version. Most Samsung devices will not let you downgrade. You have to flash what was previously installed or higher Android version.''
#3 I was frustrated. I tried using a last resort.. downloaded a custom rom which has root included called ''Galaxy Project''... Flashed it using twrp and got a bootloop for 2 hours. To get past the bootloop I had to download Oreo stock rom and flashed it using Odin. That worked.. I'm back on stock Oreo again... back to square one.
Please help out a stumped Android enthusiast... I have spent 2 days on this... but no solution works. My phone is not in danger of a hard brick as I can always revert to stock Oreo using Odin but having root would be nice.
I am having average experience, I know just the basics... please help me out and tell me what to do in a step by step manner.. I will try everything and report the findings till I finally come across a method which works.
EDIT: My phone model is G930FD
Click to expand...
Click to collapse
OEM unlocked???
cooltt said:
OEM unlocked???
Click to expand...
Click to collapse
through developer settings? yes
Devansh_Droidgeek! said:
through developer settings? yes
Click to expand...
Click to collapse
follow this guide here