I have a Samsung Galaxy S5 running Lollipop 5.0. Model # is: SM-G900V. I am a little hard of hearing and speaking with contractors on speaker phone is hard due to the poor volume. I downloaded a sound booster .zip file to help with this. I have Samsung Kies & Odin installed on my pc. My device is recognized by both. Can I use Odin to install this sound booster zip file..and it so...what's the procedure?
Thanks!
estimator1960 said:
I have a Samsung Galaxy S5 running Lollipop 5.0. Model # is: SM-G900V. I am a little hard of hearing and speaking with contractors on speaker phone is hard due to the poor volume. I downloaded a sound booster .zip file to help with this. I have Samsung Kies & Odin installed on my pc. My device is recognized by both. Can I use Odin to install this sound booster zip file..and it so...what's the procedure?
Thanks!
Click to expand...
Click to collapse
I'm not sure if you need root for it, if you're talking about the one here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/surround-sound-mod-rear-speaker-t3150306
then no, you should follow those instructions, and those instructions definitely require root.
It would be helpful to know where you got this mod from, and what the baseband of your phone is, (this can be found in Settings->About Phone). Also, you could always try earphones/IEM's, because those are generally much louder than the phone's speakers. Bluetooth ear pieces as well.
Baseband is: G900VVRU2BOG5...
I downloaded Odin so I could install a recovery on my phone so...I could install the sound booster zip file..but guess what? Odin only sees my phone when it's booted up...not in recovery mode... I give up....
estimator1960 said:
Baseband is: G900VVRU2BOG5...
I downloaded Odin so I could install a recovery on my phone so...I could install the sound booster zip file..but guess what? Odin only sees my phone when it's booted up...not in recovery mode... I give up....
Click to expand...
Click to collapse
The bootloader on the S5 is locked so you cannot install a recovery anyway. On build OG5 the bootloader is locked down to the point where you cannot downgrade to an earlier build to root and install safestrap of flashfire, so I don't think there is a way for you to flash that zip file.
So, what you're saying is: I can't root my device and I can't flash anything to it? I have the build OG5. lol I used to have a RAZR M...and it was fun trying out new ROMS and tweaking it...this Samsung is no joy at all.
estimator1960 said:
So, what you're saying is: I can't root my device and I can't flash anything to it? I have the build OG5. lol I used to have a RAZR M...and it was fun trying out new ROMS and tweaking it...this Samsung is no joy at all.
Click to expand...
Click to collapse
You can't root after OE1 or later. OG5 is after OE1.
Related
Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
BurnAll said:
Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
Click to expand...
Click to collapse
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
agent929 said:
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
Click to expand...
Click to collapse
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
heck at this point i'd be happy just to get it back to normal as its late and i need to sleep and work tomorrow
BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
agent929 said:
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
Click to expand...
Click to collapse
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
BurnAll said:
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
Click to expand...
Click to collapse
It says page not found...get the dots out of your link
Did you use your carriers Kernel?
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
agent929 said:
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
Click to expand...
Click to collapse
i have the m
BurnAll said:
i have the m
Click to expand...
Click to collapse
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
agent929 said:
It says page not found...get the dots out of your link
Click to expand...
Click to collapse
sorry here it is.
another fella on bell said this one worked for him
http://forum.xda-developers.com/showthread.php?p=41675354
lgsshedden said:
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
Click to expand...
Click to collapse
okay thanks i'll try to restore it using odin with the MG1 and then give the philz a shot. i'll update u once i've done so.
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
lgsshedden said:
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
Click to expand...
Click to collapse
okay got it back to stock, now quick question for the philz do i flash the .tar with odin? or do something else with the .zip?
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
agent929 said:
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
BurnAll said:
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
Click to expand...
Click to collapse
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
READ THIS FIRST:
MAKE SURE YOU DO NOT HAVE THE MF3 FIRMWARE ON YOUR S4. THAT IS THE MOST IMPORTANT THING TO DO RIGHT NOW. IF YOU DO, DO NOT ATTEMPT TO INSTALL A CUSTOM RECOVERY.
You don't have a custom recovery already that's why. Did casual not install TWRP for you? If not try installing Goo Manager from the app market and try installing TWRP that way. MAKE SURE THAT WHEN YOU INSTALL IT, IT SAYS YOUR MODEL NUMBER EXACTLY! I CAN NOT STRESS THIS ENOUGH! When you have TWRP installed, then flash philz with TWRP and you'll have that custom recovery instead.
BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
do not use the zip you quoted it is not for your phone
use odin flash the tar philz_touch_5.15.0-jfltecan.tar.md5
now you have stock updated MG1 firmware with the latest baseband
root by CF root
Philz Recovery
Now follow the next steps:
1. set up your google account play store etc.
2.next, go into the recovery and do a full nandroid backup -- this gives you a stable base you can restore when needed
3. go flash a custom rom, I highly recommend the latest version of Goldeneye -- updated, well maintained, great developer, clear install instructions
4. try itt then again, use recovery to make a 2nd nandroid, this one of your custom rom install -- try different kernels, every phone is different and someone's favorite kernel just may not like your phone -- doesn't make it a bad kernel just makes it the wrong one for your phone, flash a different one
5. theme if you want -- this is where your recoveries become important as themes are notorious for not always sitting well and all is ok if you have a backup you can return to
6. NEVER flash a baseband from another variant -- stick with your MG1 from your carrier until your carrier updates stock firmware
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
h_smith said:
NOTE: AT&T variant. Phone is running 4.2.2 with MF3 baseband
So I'm helping a friend root his phone and run a custom ROM. The root went successfully (motochopper) and we installed SafeStrap and then we did a backup and wipe and then installed a 4.3 Google Play edition ROM (first mistake as we meant to download the 4.2 version)
I have the stock firmware zip for the phone and figured that that was the way to fix it, but I can't figure out how to get it to install. Through ADB it gives me an error after starting DAEMON. I converted the zip to a .tar and tried to use ODIN but ODIN stops working as soon as I tell it to run. I made sure I had the most current, correct drivers and am running ODIN3 v1.85. I thought maybe if I put it on the SD card I could install it though that method via the stock recovery but it says there is an invalid arguement.
What am I doing wrong?
Help
Click to expand...
Click to collapse
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
HiTideBlastoise said:
How does he have mf3 and motochopper works? It shouldn't. Also you have to have a custom recovery to flash the gpe rom and we don't. The closest thing we have is safestrap.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure. I just used the first method I found and it worked. Then when it came to the recovery part that's when I found out about his baseband
jd1639 said:
What stock firmware zip do you have? You have to have the mf3 .tar.md5 file if you're trying to use odin
Click to expand...
Click to collapse
I'm on the SamMobile site trying to find the firmware and it says that they don't have it. I find that weird that such a popular model doesn't have the firmware needed to do this. I put in the correct model and country
EDIT: nevermind.
So I'm kinda a newbie to flashing ROMs I just got a galaxy s4 back in November and the official kit kat update killed my expirence with the s4 so I got a refurbished s4 with mk2 baseband and from what I've read the bootloader was locked. I'm on sprint but I've been flashing away like no tomorrow and yes I've been making nandroid backups and everything incase something goes wrong. (I've soft bricked my phone 4 times) but I'm just curious on how to get back to my stock mk2 rom? I've tried restoring my backup from twrp and can't get it to boot it just get stuck in a bootloop. Any help would be really nice.
how to get back to my stock mk2 rom?
Click to expand...
Click to collapse
Use the MK2 tar found in these forums.
leaderbuilder said:
Use the MK2 tar found in these forums.
Click to expand...
Click to collapse
Thing is I only have access to my phone. I don't have a PC I use my phone and my gfs phone to do stuff. Is there anyway to download a flashable zip and install through twrp
poopet22 said:
Thing is I only have access to my phone. I don't have a PC I use my phone and my gfs phone to do stuff. Is there anyway to download a flashable zip and install through twrp
Click to expand...
Click to collapse
If you REALLY want a complete wiped stock phone you'll need a PC (or Mac if you use Heimdall).
If you want to try something (with NO garuantees that'll work and not brick your phone!) you can try Mobile Odin Pro. It'll flash .tars BUT it will not flash the modem. And, like I said it may not work or worse.
So...
Find a PC, download PC Odin 3.07 (or 3.09), Downlaod the tar. Run Odin as administrator and then flash phone. DONE.
So I accidentally flashed the recovery package through Odin to a friend's s4 gt i9505 and i get a no access error in the recovery with an android and a red triangle. Since it has a custom recovery odin doesnt detect it. My question is what should i do ? . There is literally noone that has experienced the same (noob) mistake so there is no real fix. The phone is running 4.4.2 with an official upgrade to lollipop but KNOX was tripped so I would like to fix for him without having to pay for official service.
Thanks in advance.
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Strephon Alkhalikoi said:
Odd. I have a custom recovery on my S4 and Odin detects my S4 without a problem, meaning something else is causing your connection woes. Obviously, make sure you're in download mode first (hold down the volume down, home, power keys), which wouldn't be affected by a custom recovery, and change USB ports until Odin does recognize the device. Then flash the stock ROM again to restore the S4 to working order.
Click to expand...
Click to collapse
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
CostasV23 said:
the thing is it bypassed download mode straight into the recovery so it didnt recognize it at all. Maybe it was because it had a non rooted recovery? Anyway i rooted the phone with kingoroot which on the one hand it worked on the other hand the phone laggs like hell but it wiped the custom recovery somehow so i got samsung's download mode back flashed cf auto root but it doesnt update su binary so thats my problem now . The phone is a 4.4.2 firmware so should i Flash first lollipop and then root it or flash a recovery to install the su binary from there?
Click to expand...
Click to collapse
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Lennyz1988 said:
Based on your first post and this post I have come to the conclusion that you have absolutely no idea what you are doing. You are mixing everything up. And I mean everything.
- A non rooted recovery? What is that? It doesn't excist. A recovery has nothing to do with root.
- Because you had a custom recovery Odin doesn't detect it? Completely impossible. A custom recovery has nothing to do with Odin detecting or not detecting.
- Wiping the recovery and getting download mode back? Dude that's impossible. Download mode and recovery are two completely different things.
1. Flash Lollipop if you want Lollipop. With .pit and re-partition.
2. Perform a factory reset.
3. Flash cf-auto root.
That's all there is to it.
Click to expand...
Click to collapse
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
CostasV23 said:
What I meant was that I accidentally flashed the recovery tar.md5 file before cf-auto-root and it wasn't working . aside that I get an su binary update error is there a fix for that?
Click to expand...
Click to collapse
Root and recovery are two unrelated things. You don't need root for a custom recovery and you don't need a custom recovery to root.
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Lennyz1988 said:
I would start with a clean install since you used Kingoroot and cf auto-root.
Flash a stock rom with re-partition and .pit. Then only use cf auto-root.
Click to expand...
Click to collapse
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
CostasV23 said:
If I flash the official lollipop firmware via odin will it work you mean ? (Sorry for noob question ) also about that .pit I haven't found anywhere a .pit file is it necessary ?
Click to expand...
Click to collapse
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Lennyz1988 said:
You can also wipe /system and /data in TWRP and then flash Lollipop firmware.
Click to expand...
Click to collapse
Is it obligatory i wipe the system partition because odin flash rewrites it anyway or am i wrong on this one?
Also after kingroot the recovery was wiped clean for some reason
Bro my s4 GT I9505 have stock rom v5 .0.1 UHOE3.now I need rooted and install philz touch recovery so pls proper guide and file.thanks in advance.
Philz is outdated, and certain ROMs will not install with it. Use TWRP instead. For installing, it's just like installing a stock ROM through Odin. We have guides on this in the General section.
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Download firmware from sammobiles. com
http://www.sammobile.com/firmwares/database/SM-N910H/
yashthemw said:
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Click to expand...
Click to collapse
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Blu3sman said:
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Click to expand...
Click to collapse
try flashing a custom recovery specific for your phone model and from within flash superSU.
its_me_Sandy said:
try flashing a custom recovery specific for your phone model and from within flash superSU.
Click to expand...
Click to collapse
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
aaron74 said:
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
Click to expand...
Click to collapse
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Blu3sman said:
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Click to expand...
Click to collapse
Oh, I misunderstood.
If that's the case. If you can goto download mode, download stock firmware, then flash with Odin.
To get your csc, since you can go in twrp. Use twrp file explorer. copy the file in /efs/imei folder. Thinks it's called mps_code. Copy to ext sd. Now that file should have your csc region code written in it. Read file in pc. That should be firmware you want to download.
See if that helps.
Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
Find the correct version of superSU from the above post..put it in a pen drive or in the memory card via card reader.
Flash it via OTG cable or put back the card n flash
ALRIGHT!!!! Ok guys just a heads up. As you can probably guess my phone is WORKING!!!....so far. Was able to do as you suggested and found the txt file, Using TWRP file browser ,that told me what ver firmware i have, inserted an sd card i had in my Tab S, copied file to that, read in my pc card reader, downloaded and installed said firmware and BADA BING BADA BOOM, all good!! I still am unsure on how this happened. I've rooted 3 HTC phones and my Galalxy Tab S successfully, so it's not like i didn't know what i was doing, 1 question that hasn't been answered though is, must the phone be network unlocked in order to root it? Because thats the one thing i didn't do that i did on the others. Want to thank all you guys for all your help. This was doing my head in and without your direction i probably would not have been able to do this.
Many Thanks.
PS: any one suggest a good rooting method for this phone??? lol
hi. i have the exact problem. can you please help,, i dont have twrp or supersu. [email protected] please if anyone can help