I recently rooted my phone to try and recover some deleted pictures after the phone completely crashed and wouldn't load up , I have tried to install an original firmware using Odin but I keep getting the same message about not being authorized . Am I installing the wrong files or am I not doing something thathat causes it to fail?
Where did you download the firmware? Are you sure you're using the correct version?
Are you on a G930T or a G935T?
I had the same problem on mine before, what solved it was downloading a later version of the firmware, as you can't downgrade just like that.
You can download the latest firmware from Sammbile. (I would link but I have less than 10 posts.
The T stands for T-Mobile, and the 930 is the regular, 935 is the edge. If you're not T-Mobile, you're in the wrong section, but I'm still glad to help once I obtain more information.
http://forum.xda-developers.com/showthread.php?t=2798396
apowers98 said:
Where did you download the firmware? Are you sure you're using the correct version?
Are you on a G930T or a G935T?
I had the same problem on mine before, what solved it was downloading a later version of the firmware, as you can't downgrade just like that.
You can download the latest firmware from Sammbile. (I would link but I have less than 10 posts.
The T stands for T-Mobile, and the 930 is the regular, 935 is the edge. If you're not T-Mobile, you're in the wrong section, but I'm still glad to help once I obtain more information.
Click to expand...
Click to collapse
It worked ... thanks man , I thought the sammobile website was fake because of the processence to download but it worked perfectly
xxmessxx said:
It worked ... thanks man , I thought the sammobile website was fake because of the processence to download but it worked perfectly
Click to expand...
Click to collapse
hey man i have the same problem ,
i rooted my phone like week go and was crappy but expected and lived with it ,
today punch of apps were crashing and stopped working , reboted the phone got stuck in the T-mobile welcome screen ,
decided to go back tried to get the stock rom but no luck
exact same problem now the phone goes straight to recovery mode , i can do to download mode ,
my question here which software of sammobile used ?
the last recent one ??
any help will be appreciated
my phone is Galaxy S7 With T-mobile , 930T
makemesway2007 said:
hey man i have the same problem ,
i rooted my phone like week go and was crappy but expected and lived with it ,
today punch of apps were crashing and stopped working , reboted the phone got stuck in the T-mobile welcome screen ,
decided to go back tried to get the stock rom but no luck
exact same problem now the phone goes straight to recovery mode , i can do to download mode ,
my question here which software of sammobile used ?
the last recent one ??
any help will be appreciated
my phone is Galaxy S7 With T-mobile , 930T
Click to expand...
Click to collapse
Always flash the most recent firmware becasue if you don't remember chances are you can flash an old version and run into issues, so to be safe flash the latest available firmware. Also when you first rooted did you change the CPU governor or run/install anything that could have caused the bootloop in the first place?
KillerClaw321 said:
Always flash the most recent firmware becasue if you don't remember chances are you can flash an old version and run into issues, so to be safe flash the latest available firmware. Also when you first rooted did you change the CPU governor or run/install anything that could have caused the bootloop in the first place?
Click to expand...
Click to collapse
thanks all for the help i got my phone back from the dead.
it has now the most recent stock rom. gave me so much hard time but i got it back from the dead .
and i didn't do any thing to the governor or any thing the root was running for 10 days fine and yesterday was freezing and a lot of apps stopped working restarted the phone. was stuck in the boot loop
all good stable again under the stock rom.
waiting for a stable root method to get rid of all the crap we got of T-Mobile
makemesway2007 said:
thanks all for the help i got my phone back from the dead.
it has now the most recent stock rom. gave me so much hard time but i got it back from the dead .
and i didn't do any thing to the governor or any thing the root was running for 10 days fine and yesterday was freezing and a lot of apps stopped working restarted the phone. was stuck in the boot loop
all good stable again under the stock rom.
waiting for a stable root method to get rid of all the crap we got of T-Mobile
Click to expand...
Click to collapse
You can install this awesome rom to speed things up don't worry it's a stock rom so no Knox trip. The link I will provide also has instructions. So to get started I recommend making a backup of applications with titanium backup which might require the pro so unfortunately you may have to buy a full version( if you don't want to spend money you can patch the app with lucky patcher). And I recommend checking out this rom: http://forum.xda-developers.com/tmo...stockdeodexeddebloatedrom-7-10-t3415952/page1
It is somewhat debloated and has the best speed I've seen yet... Ive been using it for a month now and I love it!
Related
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.
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Fleacore210 said:
As in the title states I have the galaxy tab 2 7.0 and recently I installed CWM and a ROM and everything looked like it went right however after I reloaded my tablet nothing seems different it jus seems to return to stock setting and now I cant do the OTA software update which means now certain apps and games I can no longer uses as it says my device isnt compatible. My goal was to simple update from Jellybean to at Least Kitkat.
Can someone help me. where did I go wrong?
Click to expand...
Click to collapse
Go to sammobile and flash the latest stock firmware for your device .
Newyork! said:
Go to sammobile and flash the latest stock firmware for your device .
Click to expand...
Click to collapse
Well after a short research I found a ROM called Resurrection Remix, loaded with 5.0.2 (or Lollipop) however now everything is force closing and I barely got my laptop to see it as MTP again after installing a new Binary (glad that did that trick for that) but I cant get it to boot into CWM Recovery bc I cant access the app the only thing it will let me do right now is change the Binary.
How can I fix this issue?
Edit: Okay so I got that solved with doing a factory reset twice, booted in CWM, loaded up the GApps. Now just wondering if there is away to make it not seen with phone options like the dialer or msgs as its jus a plan old tablet, doesnt take a sim card and has no carrier. I do have the source code but I am not tweaking that til I get a better understanding of it.
After a lot of research and tries (amazingly without bricking) I am now running an even newer version of a CM 13 Marshmellow
I was running Mokee 7.1.1 just fine on PB1 firmware... which was probably my first mistake. (not 100% sure) as of now
phone is currently G900V Kltevzw bootloader unlocked, TWRP recovery, updated bootloader to PL1 w/SS
I'm having issues getting service when I flash a new rom most of them have no service i've messed with APN settings.
I felt I was a pretty competent user, i've come from flashing and rooting back from the original Moto Droid, I'd like to know what i'm doing wrong
as of now my phone is useless :crying: with no service so i reverted to my S4 lol
I'd appreciate any help and guidance to bring service back to my phone on MM or Nougat firmware which i have been running for a month or so
i don't really know how to help you but I have the same same s5 as your and running mookee 7.1.1 and my cell service still works i dont know if its a problem with the latest update and i have not updated to pl1....so maybe that may give a hint.
bdawwgg said:
I was running Mokee 7.1.1 just fine on PB1 firmware... which was probably my first mistake. (not 100% sure) as of now
phone is currently G900V Kltevzw bootloader unlocked, TWRP recovery, updated bootloader to PL1 w/SS
I'm having issues getting service when I flash a new rom most of them have no service i've messed with APN settings.
I felt I was a pretty competent user, i've come from flashing and rooting back from the original Moto Droid, I'd like to know what i'm doing wrong
as of now my phone is useless :crying: with no service so i reverted to my S4 lol
I'd appreciate any help and guidance to bring service back to my phone on MM or Nougat firmware which i have been running for a month or so
Click to expand...
Click to collapse
I ran across this once.. not from 7.1 (forget what I did actually) .. no spc / min / etc.. Odin flashed back to stock, problem fixed itself.. flashing through TWRP wouldn't do it.. after that had to go through the steps of unlocking bl / etc again.. on CID 15
travioso said:
I ran across this once.. not from 7.1 (forget what I did actually) .. no spc / min / etc.. Odin flashed back to stock, problem fixed itself.. flashing through TWRP wouldn't do it.. after that had to go through the steps of unlocking bl / etc again.. on CID 15
Click to expand...
Click to collapse
Interesting... I may have to set aside some time to do that. What stock version did you flash? Since I'm on PL1 firmware would you think that make a difference as to what stock youre going to?
I'll have to do some more research as to how I should go about flashing stock then unlocking the BL again. Not sure if I can because of my updated bootloader..
I experienced similar issues with my g900v but mine was with texts being severly delayed and crappy service.. but atleast I still had service. I just finally fixed it this morning by completely flashing back to stock (PB1) and rerooting. I used this guide and started at the very beginning: https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
Follow it and you should have your problems fixed.
Clayton993 said:
I experienced similar issues with my g900v but mine was with texts being severly delayed and crappy service.. but atleast I still had service. I just finally fixed it this morning by completely flashing back to stock (PB1) and rerooting. I used this guide and started at the very beginning: https://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
Follow it and you should have your problems fixed.
Click to expand...
Click to collapse
Thanks!!! I'll Slowly start doing this after I post this. Hope to have a good outcome.
If you haven't started yet, I found an easier "how to" here: https://forum.xda-developers.com/ve...ewbies-guide-to-install-pb1-rom-root-t3481826
It includes all the info from the link I posted yesterday but also includes the steps to update to PF4, which I'm about to do right now. Hopefully the delayed text and crap service problems don't return with updating, if so I will post the outcome.
Clayton993 said:
If you haven't started yet, I found an easier "how to" here: https://forum.xda-developers.com/ve...ewbies-guide-to-install-pb1-rom-root-t3481826
It includes all the info from the link I posted yesterday but also includes the steps to update to PF4, which I'm about to do right now. Hopefully the delayed text and crap service problems don't return with updating, if so I will post the outcome.
Click to expand...
Click to collapse
Thanks for that. Just finished that. Gonna look try installing some custom roms. Ideally im looking to use a Nougat rom, but dont mind the MM at all...
What custom roms are you looking into.
bdawwgg said:
Thanks for that. Just finished that. Gonna look try installing some custom roms. Ideally im looking to use a Nougat rom, but dont mind the MM at all...
What custom roms are you looking into.
Click to expand...
Click to collapse
I've already ran a few different roms but haven't really found one I liked enough to stick with. I used Phoenix v15 for a few months then switched to the new 7.1 resurrection remix nougat ROM a few weeks ago. I'll probably go back to nougat unless I start having service issues again. Good luck
I'm still not getting either or one of the two data and cell service. SMS/MMS wont work. Still dont know what is wrong exactly. PF4 updated BL
Not sure if i need to flash a radio or something in odin to get service to work....
About 3 weeks ago I updated to the current stock firmware and since then I have gotten stuck on the tmobile splash screen about once a week. The only fix for this has been a factory reset... Not entirely sure what's going on here or how to fix it but this is getting really old. Has there been any other reports of problems like this with the current firmware?
My wife is using the phone and at work so I can't give the exact firmware right now, just trying to get some idea of what I could try.
zadane said:
About 3 weeks ago I updated to the current stock firmware and since then I have gotten stuck on the tmobile splash screen about once a week. The only fix for this has been a factory reset... Not entirely sure what's going on here or how to fix it but this is getting really old. Has there been any other reports of problems like this with the current firmware?
My wife is using the phone and at work so I can't give the exact firmware right now, just trying to get some idea of what I could try.
Click to expand...
Click to collapse
My 7.0 nougat on my s6 stopped the phone from charging. I got around it by flashing Dr ketans note 5 rom. It's touch wiz based so you keep your samsung goodies plus get some tweaks. It's very stable. Just remember to flash the call audio fix zip. Download odin and twrp for your device. Put the zip onto your device. Wipe dalvik/sysyem/cache/data from twrp then flash the zip. Your photos and files on internal storage will stay. But your apps will not.
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