Related
I'm coming from the HTC environment and the Note 4 will be my first Samsung phone. I have a few concerns regarding root. Assuming the Note 4 can be rooted, using the Note 3 and the S5 as a precident, how does one maintain updates? With HTC, if you had root, you could flash a new ROM for software updates (newer android versions, bug fixes, carrier updates). However, to update firmware, like updated radios, you needed S-Off.
Please help explain. With the Note 4, what will we need in order to do the following, and what is the likelyhood each of the following will be possible:
1) Obtain Root to run apps requiring root (Titanium, adblocker, WIFI tether...)
2) Install custom recovery
3) Flash custom ROMs
4) maintain a phone with updated and current Firmware and Radios.
Otherwise, what do people do who root there phone on day 1? Do they go 1-2 years with the phone without updating firmware?
Thank you
you can update samsung software with no issues. Assuming they'll keep it like the Note 2, there under the settings>update, there are different tabs, and one is Samsung.
Modems and other such updates, you'll just need to wait a day or two for someone to upload the newer OTA with root. Sometimes, some of the root tools, like SuperUser, will have OTA survivor mode, but they're not guaranteed to worked.
End of the day, it's not anything you're not already use to
Thanks for the response. So if the bootloader is NOT able to be unlocked, what will we be missing out on then? If the bootloader IS locked and there is no way around it, we can still root, flash ROMS, and update radios/firmware?
we can only go by the past to predict the future, but in US ATT Note 3 had locked bootloader, T-mobile loader was unlocked, so it was up to the carrier, but I believe both had way to root. One problem with Samsung was Knox software, which once triggered by root or loading custom firmware couldn't be reset back to zero. Based on that flag some people claimed to be refused warranty repairs, others didn't, so who knows. One thing is that Samsung "donated" knox to Google L Android, so it may be on all Android phones in the future, but again who knows how Google will implement it. It may take a time for developers to find their way around new phone, so if you have concerns, wait a little until all is clear, for now we can only guess. My Note 3 is rooted, "official" with Knox flag 0, but I had to wait for proper methods to be developed and every time I update I need to re root (and make some other changes) again. There could be developer model also with everything open, who knows.
Thanks for the response.
I just need to clarify what can be done on a rooted Samsung device vs what can be done with a rooted AND unlocked Samsung device.
Am I correct:
Rooted Only:
-superuser
-can run root required apps (Titanium, Wifi Tether)
-can flash custom ROM but must be stock based only, and must be on stock kernel
-can NOT install CM or TWRP custom recovery
-can update firmware and radios but must OTA and then re-root
you cant flash a rom with stock recovery
if no bootloader unlock, and no custom recovery, then no rom flashing..
flyhighx said:
.... Rooted Only:
.. -can flash custom ROM but must be stock based only, and must be on stock kernel .../QUOTE]
As stated above, this not correct. You'll able to flash the stock firm via Odin. In fact, you'll be able to get the tar file from Samsung if you wanted.
Click to expand...
Click to collapse
I haven't used it in awhile, but I believe you still need a custom recovery to use Mobile Odin, don't you?
i want root mostly for four reasons:
Disable logging
Multi window enable more apps
Make one hand mode background black
because its mine and i can...
But I also need it rooted without tripping knox (for work purposes..)
Rogers Canada: i9505 "App stopped working" and cellular data not working off and on
Hi, I have the galaxy s4 i9505 from canada on rogers network. The actual model is SGH-i337M though. I have been using cyanogenmod but most recently, the optimized cyanogenmod 5.1.1 from alcurd. And for both OS's I have constant random app crashes from gapps and stock cyanogenmod apps. they randomly crash when i'm in them or they'll crash right away when i try to open one. they don't always crash, but it happens enough to get annoyed from it. Also my data disconnects all the time. it will say I have no service. this happens everynow and then. I've tried installing stock samsung firmware for 5.0.1 then installing cyanogenmod optimized after but it does nothing to fix it. I've even tried installing the new modem after. maybe I didn't find the right one, i'm not sure. Does anyone know what could be causing these issues and help me out with how to fix them or does anyone know a good rom that wont have these issues? I want a cyanogen like rom or pure android. I hate samsungs stuff lol. Thank you so much if you can help :]
OathVyne said:
Hi, I have the galaxy s4 i9505 from canada on rogers network. The actual model is SGH-i337M though.
Click to expand...
Click to collapse
Then you don't have an I9505.
I don't think there is a separate modem file available for your S4, unless it's in the forum for your device, so you'll likely have to download the complete ROM. The correct ROM for your S4 is here. Make a nandroid backup of your current ROM and make sure it's saved to the MicroSD card. Flash this ROM through Odin, let it boot, and let it take care of its business. Then head back into download mode, flash your custom recovery, reboot into the recovery, and restore your nandroid backup.
I would try and find just the modem and bootloader package for your S4, as none of the modem/bootloader packages here are for your device. If you can find that, then you can avoid having to do all the steps above and simply flash the modem and bootloader via Odin.
With luck, installing the right bootloader and modem will cure many of your issues.
Strephon Alkhalikoi said:
Then you don't have an I9505.
I don't think there is a separate modem file available for your S4, unless it's in the forum for your device, so you'll likely have to download the complete ROM. The correct ROM for your S4 is here. Make a nandroid backup of your current ROM and make sure it's saved to the MicroSD card. Flash this ROM through Odin, let it boot, and let it take care of its business. Then head back into download mode, flash your custom recovery, reboot into the recovery, and restore your nandroid backup.
I would try and find just the modem and bootloader package for your S4, as none of the modem/bootloader packages here are for your device. If you can find that, then you can avoid having to do all the steps above and simply flash the modem and bootloader via Odin.
With luck, installing the right bootloader and modem will cure many of your issues.
Click to expand...
Click to collapse
Would it be this: http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758 ?
It only has modem file, theirs no bootloader :/
It's marked "Modem/Baseband" so the one file should cover both. But even without the bootloader the modem should still be able to be flashed.
Hei all,
I bought my phone off ebay without realizing that there are different models for different markets. However inside the battery case the model number is SM-G900A. Since I off course wanted the latest android version that my wife has on her G900F I went about googling for a solution. After lots of tries and lots of failures, I eventually managed to root my phone with towelroot. I went on to flash a G900V firmware onto my phone (Don't ask why). Now I have a G900V baseband, bootloader and rom entirely. I then went on to update OTA to end up with Android 6.0.1 version only to realize that it cannot be rooted yet. I then went back to 5.0 in order to root and to install custom Twrp 3.0.2.2 recovery and unlock the bootloader to developer mode using sambootloader unlocker.
My question is this: How the h... was I able to transform my G900A to a G900V model to begin with. This is over a year ago, and I cannot remember how I went about it. What I do remember is that I used ODIN, with a G900V pit file and did a complete wipe checking repartition, nand erase all, phone efs clear, and bootloader update.
Now my follow up question is this: If it was possible to "transform" my G900A into G900V, would it be possible to "transform" it into a G900F model given that the hardware on the phone is identical ? I mean what is it that makes the phone a G900V, G900F, G900A model in the first place ?
Would it be possible to completely repartition the internal memory of the phone and flash a complete G900F package with bootloader, recovery, system, modems etc ?
If you are inclined to answer this with a short no, then please be so kind to explain why my phone now only accepts G900V firmware ?
You have done something very risky
Flashing another phone's PIT is a quick way to hardbrick (*i've done it before. what an argue at the service center!*)
Don't try to convert to a G900F... that's an even more different phone
Simply flash G900A PIT+FIRMWARE
Also, NEVER TOUCH any checkboxes in Odin like nand erase all and phone efs clear! Your phone will never work on cell signal again.
There is no way it should not accept ATT firmware because the signing key is in true ROM on Qualcomm S5s I believe
this is risky and dangerous i know all partitions except bootloaders can be flashed with flashfire on a bootloader unlocked phone but ive never heard of someone flashing bootloaders succesfully i wouldnt attempt it and agree with lightning i do remember g900a and g900v modems seem to be compatible but im dangerously curious can you remeber anything else oja60
[email protected] said:
this is risky and dangerous i know all partitions except bootloaders can be flashed with flashfire on a bootloader unlocked phone but ive never heard of someone flashing bootloaders succesfully i wouldnt attempt it and agree with lightning i do remember g900a and g900v modems seem to be compatible but im dangerously curious can you remeber anything else oja60
Click to expand...
Click to collapse
No, not really. All I can remember is best described in the post above. I bought an S5 from ebay, probably delivered from asia somewhere. The back of the phone said G900A and I was curious as to why I couldn't get any OTA-updates. I the downloaded a G900V pit file and a stock G900V ROM from sammobile, and went at it. After installing it all the phone worked like a charm, so I could then go about rooting and unlocking the bootloader with the above mentioned method.
I have now gotten a hold of a G900F phone which I wanted to begin with. That means I could try the procedure again to see If it's possible to convert the now G900V phone into a G900F in the same way. I need to specify this however: We are not talking about running a G900F ROM on an unlocked G900V bootloader here (That's easy!). This is about converting the whole shambam. What I still haven't gotten an answer to is what makes a G900V a G900V and what makes the other models unique ?
Best regards
OJA
Thinking I'll post the TLDR up top:
What ROM should I use for the most basic (no extra "features") for my phone? Perhaps I'm too soon for such a version? I have the Exynos S8+.
So ~4 years ago I decided to move to Windows Phone (xperia 1020 -> Lumia 950XL). I'm not a big Facebook guy, so my phone is mainly for notes, texts and calling. I have however become a "fan" of Microsoft products, and I managed to change everything from "Samsung all the way up your ass" to "Microsoft when you desire it" on my S8+, including remapping the bixby button to Cortana. I have turned of all permissions possible for all Samsung apps I could, the only reason I want to root/change ROM is because I hate the "always active, **** up your battery and start all apps lockscreen home button".
I don't want any fancy stuff, I just want a clean android version for my Phone, with the option to disable the Home button on lock screen... And perhaps a point in the right direction for how to root/ROM my phone correctly. I believe it's 7 years since I've looked into rooting, hell, might even use the wrong terms here... That's what not looking into tech like I did 7 years ago does to a man
Edit: My 950XL basically went to hell, so I had to more or less impulse-purchase my S8+, without looking into what I really bought.
I've had this Samsung phone for maybe a month and a half. So please take this with a grain a salt. Information that was scattered around and I had to go searching for when I bought this phone. Here is my brain dump...
There isn't an AOSP or Vanilla Android ROM, they're all touchwiz based. Most of the ROMs give you an option during installation of certain apps you can remove. I dabbed around making a very clean and minimal ROM, but turns out if you remove too much the setup wizard falls apart and the phone basically freezes before even selecting your language. So I resorted to installing someone elses ROM and after setting it up, using ROM toolkit to remove random system apps and hoping it doesn't crash after a reboot. haha
This is my first Samsung phone (exynos S8) so getting around to using ODIN and the different files you need to flash was a headache. The general rules to follow are.
1. Enable Developer Options and turn on OEM Unlock. Then never again change that option. If you are not running 100% stock the bootloader will prevent the phone from turning on correctly and kick you into Download mode basically forcing you to flash a stock ROM. So once you turn on OEM Unlock, just leave it turned on. I was messing around in Dev Options and without knowing turned it off. Next time I restarted my phone I was forced to flash stock rom again. Custom ROMS tend to remove that option entirely so someone doesn't mistakenly turn it OFF.
2. KNOX is Samsungs security in stock ROMs. The moment any kind of custom recovery or anything is installed. KNOX will be tripped and stop the phone from completing boot up. It'll basically tell you that theres something that wasn't signed by Samsung and to reset the phone. An endless cycle unless you, 1. Install a Custom ROM or 2. Flash a stock ROM to undo whatever you did.
3. Keep your firmware (modem bootloader etc) as recommended by the ROM Dev. AQF7 is the last known stable and developed for firmware.
Right now there a new update AQG5 that has an updated Bootloader that will softbrick your phone. People have tried installing the entire Stock ROM and ran into issues. It worked for some, but avoid it for now. If you do find the need to play with it. For the time being flashing just the modem (CP file) and keeping or using the previous AQF7 Bootloader (BL file) should keep your phone usable.
4. The S8 and S8+ are very much identical except the obvious size difference. Cross Development allows Devs to create a single ROM for both devices. With only the Kernel being the difference. Which is some cases both are in the ROM zip and automatically selected for you. So if they state its compatible with both. If not just focus on S8+ only ROMS.
5. ODIN is a program that's used to flash files. Either to flash custom recovery or stock files. Samsungs SmartSwitch program is like Windows Phone Recovery Tool. It'll detect the phone you have connected and download the latest stock ROM it can find and flash it. ODIN is a stripped down program that we use to flash individual files. Its only really used to either flash a stock ROM or custom recovery. In some cases bootloaders and modem updates, but id avoid those for now.
6. ROM/Firmware structure. Samsung stock ROMs and Firmware zips are available all over the place. Basically its a .zip file with more tar files in it.
Lets say you download a stock ROM.
The name is normally Model|Region|Version.zip so for me I have G950FXXU1AQF7 that tells you. G950F is the Euro S8 Exynos, XXU1 is basically just New Zealand and some carrier, AQF7 is the firmware version. The file name might have multiple regions. Theres more into what means what. I personally just focus on the Model and the Firmware. I can delete carrier apps or flash my carriers CSC later on. From what I've seen version numbers increase with the next letter in the alphabet and a number. So obviously an update with AQF7 is newer then one named AQD6 etc.
If you where to extract a stock firmware/ROM zip to use in ODIN etc. It normally gets broken down to these tar files. If stock files are renamed ODIN will not accept them. It happen to me
BL** - Contains the Bootloader, partition layout etc.
AP** - Actual ROM. Kernel, System, cache, userdata (for some), recovery
CP** - Modem files.
CSC** - Preloaded carrier apps, settings. This comes in two files. If you flash HOME_CSC your data is kept if you decide to do an update. CSC file without HOME will format the data partition.
These files are flashed in their prepacked files. You wont flash individual system, kernel files etc with odin.
7. TWRP the go to recovery for Android. You'll use ODIN to flash it. On twrps website just find the S8+ (dream2lte) and download the .tar file. Using ODIN it will be flashed as an AP file.
8. Once you have TWRP installed it will trip KNOX if using a stock ROM. The button combination to get you into recovery from a fully turned off phone is,
PWR + Vol Up + Bixby
Vol Down is Download Mode, also used as the button combo to force the phone to restart. If you restart it this way, quickly move your finger and hit Vol Up and if done right will go into recovery.
9. CSC is carrier bloatware, but in the forums its what gives you VoLTE & WifiCalling. As long as your carrier supports it and in an area/wifi network that will allow it. Some ROMs have it included, if not you can find a forum thread which offers a flashable zip that will give you all the carriers around the globe. If selected correctly should give you those features for your carrier on your phone.
___________
The jist of all that is. Enable OEM unlock > use ODIN to flash TWRP > Boot into TWRP and flash a custom ROM. You'll use TWRP to flash ROMS, Mods, Custom Kernels. ODIN/SmartSwitch would be used to revert to 100% stock. If you ever some how turn off OEM unlock while using a custom ROM. FAP will be turned on and block you from using your phone until you flash a stock ROM and turn on OEM unlock again.
I'm personally using Renovate ICE on my S8 and have removed ALOT of system apps. Windows Phone has a special place in my heart, but Microsoft is just terrible about it now. I had a 950XL for a bit, but always had HTC phones when it came to Android. For me HTC was so much easier to work with when it came to ROMs. Now I'm rocking an S8 so had to learn fast.
Always do your research before flashing anything. Make sure multiple sources say the same thing or risk flashing something that might break your phone. If any other user finds something I mention to be wrong, PLEASE correct me. I will learn and so will others.
What I missed from HTC forums was the sticky threads. The go to threads that broken everything down and explained it. All the HTC phones I had while using XDA had these sticky threads in each devices forums. I was and still am reading threads from other Galaxy phones just to get a better understanding of how it all works since they aren't in this devices forum.
Not to talk bad about long time Samsung users, but yall need to get organized haha. Once I'm confident with Samsungs inner programming workings I'll try to make an actual knowledge thread with links and where credit is do. But dam it's like sink or swim around some galaxy phones.
Hello everyone, I recently decided to root my Axon 7 and try some custom roms, I couldn't get any of the roms to completely boot so I went back to stock. After doing so I have no imei/unknown baseband. The issue I'm more concerned with though is my audio skipping, even when I'm not playing anything I still notice a stutter in the system and witness the higher clocked cores of the 820 jumping to 100% utilization. It happens almost like clockwork and I'm pulling my hair out trying to diagnose it.
TekHead2 said:
Hello everyone, I recently decided to root my Axon 7 and try some custom roms, I couldn't get any of the roms to completely boot so I went back to stock. After doing so I have no imei/unknown baseband. The issue I'm more concerned with though is my audio skipping, even when I'm not playing anything I still notice a stutter in the system and witness the higher clocked cores of the 820 jumping to 100% utilization. It happens almost like clockwork and I'm pulling my hair out trying to diagnose it.
Click to expand...
Click to collapse
First let's diagnose the custom ROM thing. They don't boot because you're doing something horribly wrong there m8.
To install a custom ROM you need 5 files:
-Universal Bootloader
-Corresponding modem file
-The actual ROM
-SuperSU or Magisk, to disable dm-verity
-TWRP 3.2.1-0.img (Have it installed AND ALSO on the phone (internal or SD card, same).
So, you wipe data, caches and system, flash the Universal Bootloader, then the TWRP.img, then modem, ROM, and Magisk. If you forget about flashing the modem file you'll lose signal.
Second error: Lost your IMEI
What did you do to go back to stock? What files did you use? And most importantly, what's your phone's model? If you flashed an A2017G package on an A2017 it is possible that you'll lose your IMEI. There are ways to rewrite it though, but I don't know any/they are illegal and stuff.
To fix the stuttering I recommend that you download MiFlash, a corresponding update package for your device model, and flash it via edl. The IMEI is screwed but you probably still have the phone's box with the stickers.
Choose an username... said:
First let's diagnose the custom ROM thing. They don't boot because you're doing something horribly wrong there m8.
To install a custom ROM you need 5 files:
-Universal Bootloader
-Corresponding modem file
-The actual ROM
-SuperSU or Magisk, to disable dm-verity
-TWRP 3.2.1-0.img (Have it installed AND ALSO on the phone (internal or SD card, same).
So, you wipe data, caches and system, flash the Universal Bootloader, then the TWRP.img, then modem, ROM, and Magisk. If you forget about flashing the modem file you'll lose signal.
Second error: Lost your IMEI
What did you do to go back to stock? What files did you use? And most importantly, what's your phone's model? If you flashed an A2017G package on an A2017 it is possible that you'll lose your IMEI. There are ways to rewrite it though, but I don't know any/they are illegal and stuff.
To fix the stuttering I recommend that you download MiFlash, a corresponding update package for your device model, and flash it via edl. The IMEI is screwed but you probably still have the phone's box with the stickers.
Click to expand...
Click to collapse
I used miflash to revert to stock, using the b19 file from the toolkit for the phone, then did all the OTA updates and it's still there
As for the roms, I flashed all the files properly but it kept freezing on the boot logo so I gave up
TekHead2 said:
I used miflash to revert to stock, using the b19 file from the toolkit for the phone, then did all the OTA updates and it's still there
As for the roms, I flashed all the files properly but it kept freezing on the boot logo so I gave up
Click to expand...
Click to collapse
But what model is it? Etched on the back, of course, not the original software model
Choose an username... said:
But what model is it? Etched on the back, of course, not the original software model
Click to expand...
Click to collapse
A2017U
I made sure I had all the right files,
Okay so I've made some progress, I discovered that my definitely US model phone is allergic to something about the US modem file. I was trying out the 8.0.0 edl rom which has the Chinese modem included and I noticed that all my problems were fixed, but it just wouldn't connect to the network (duh), I went back to stock and the issues were back until I flashed a Chinese modem from a post I'll reference once I'm back at my pc. If it's possible to make said modem capable of connecting to Verizon it would be amazing.
Not saying this is related but I've seen that with phones using combination low and high power cores, sometimes it switches down to low power even with music playing and maybe gets buffer issues or a stutter switching back up to the big cores. My Mate 7 did this. Didn't have the performance of the Axon 7 which is usually more stable in this regard.
You could have a governor issue or storage read performance problem.