I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
kernelpanic_ said:
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
Click to expand...
Click to collapse
Someone correct me if I'm wrong but that was only in the early root guides. I think its been fixed because even after a week and a half after the launch, I rooted and didn't lose radios. Just follow the original root guide and you'll be fine. Or just install twrp and then leedroid or viper rom and make it much simpler for yourself
kernelpanic_ said:
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
Click to expand...
Click to collapse
btort1 said:
Someone correct me if I'm wrong but that was only in the early root guides. I think its been fixed because even after a week and a half after the launch, I rooted and didn't lose radios. Just follow the original root guide and you'll be fine. Or just install twrp and then leedroid or viper rom and make it much simpler for yourself
Click to expand...
Click to collapse
true the previous version of supersu rooting used to mess up encryption and break your signal post which they had set the flag to enforce encryption and thus letting you root and retain radio but then if you decrypt your data manually you used to lose radio again..
but now almost all of the custom roms like ice lee viper does let you root and decrypt data and radio works fine...
i have tried it on ice and lee both works fine and i am currently decrypted with super 2.74-2 system mode from su thread
SacredDeviL666 said:
true the previous version of supersu rooting used to mess up encryption and break your signal post which they had set the flag to enforce encryption and thus letting you root and retain radio but then if you decrypt your data manually you used to lose radio again..
but now almost all of the custom roms like ice lee viper does let you root and decrypt data and radio works fine...
i have tried it on ice and lee both works fine and i am currently decrypted with super 2.74-2 system mode from su thread
Click to expand...
Click to collapse
So it does have something to do with the encryption
Side question for you - Have you noticed performance differences between encrypted and non?
_-..zKiLLA..-_ said:
So it does have something to do with the encryption
Side question for you - Have you noticed performance differences between encrypted and non?
Click to expand...
Click to collapse
Personally, I haven't noticed much difference, if any, at all between encrypted and unencrypted. Haven't bothered running any benchmarks, though, either.
schreckles said:
Personally, I haven't noticed much difference, if any, at all between encrypted and unencrypted. Haven't bothered running any benchmarks, though, either.
Click to expand...
Click to collapse
_-..zKiLLA..-_ said:
So it does have something to do with the encryption
Side question for you - Have you noticed performance differences between encrypted and non?
Click to expand...
Click to collapse
doing benchmarks on both theres is no difference, if anything its a bit slower decrypted.
kernelpanic_ said:
I know there are ways around breaking the radio, but I'm just really curious. How would rooting break the radio? Does it have something to do with the weird encryption that comes on some Marshmallow devices now? Thanks.
Click to expand...
Click to collapse
also the losing of the radio during root, like said in pervious post is a thing of the past, fixed like the first week. Just make sure your using the latest twrp recovery, and this su
afuller42 said:
doing benchmarks on both theres is no difference, if anything its a bit slower decrypted.
also the losing of the radio during root, like said in pervious post is a thing of the past, fixed like the first week. Just make sure your using the latest twrp recovery, and this su
Click to expand...
Click to collapse
No decrypted devices are always faster in performance due to less layer of security while ur soc tries to access files . but then again those differences are very hard to notice . . . encrypted devices are always a bit slower than decrypted. . .
Sent from my HTC 10 using XDA-Developers mobile app
Related
Is any method of root or custom ROM compatible with our T Mobile Samsung Note tablet? Coming from a HTC one m7 where all rom were compatible other then CDMA/ GSM
I've used the towelroot but really looking to install aosp on this thing already
Sent from my One using XDA Free mobile app
law16 said:
Is any method of root or custom ROM compatible with our T Mobile Samsung Note tablet? Coming from a HTC one m7 where all rom were compatible other then CDMA/ GSM
I've used the towelroot but really looking to install aosp on this thing already
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Prod1702 said:
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Click to expand...
Click to collapse
I'm looking for ROMs too. But I think I'll stay with stock for now. Any recommendations on what apps to debloat?
dmunjal said:
I'm looking for ROMs too. But I think I'll stay with stock for now. Any recommendations on what apps to debloat?
Click to expand...
Click to collapse
Your best way is to just use TB and froze whatever you do not want. If you run into problems just unfroze it. If you uninstall and you run into a bootloop you will need to have the stock Odin firmware ready. here is a link to get the stock odin file.
http://www.sammobile.com/firmwares/3/?download=29807
I just uninstalled whatever I did not want. If you google What apps are safe to remove on a Note 3 to debloat, it will pretty much be the same as the 10.1. Both the note 3 and the 10.1 are pretty much the same other then screen.
Edit: I got this list from here
https://docs.google.com/spreadsheet...ZzBfWlR4MC03aDMyZ1BDUFNqU0E&usp=sharing#gid=0
Here is a a list for the GS4 which as a lot of the apps we have as well
http://forum.xda-developers.com/showthread.php?t=2317714
unlocking bootloader
I think we need to get the bootloader unlocked to get development on this thing rollin'
I'm willing to lend my device to a well-reputed senior-member/developer and pay shipping both ways if they think they can work some magic for the SM-P607T
Should I make a new post with regards to this?
Was able to root using this method no Knox either
http://forum.xda-developers.com/showthread.php?t=2785804
Sent from my SM-P607T using XDA Free mobile app
TG2008 said:
I think we need to get the bootloader unlocked to get development on this thing rollin'
I'm willing to lend my device to a well-reputed senior-member/developer and pay shipping both ways if they think they can work some magic for the SM-P607T
Should I make a new post with regards to this?
Click to expand...
Click to collapse
bootloader is unlocked and there is no problems getting root and current Twrp can be installed which says the bootloader is unlock. if the bootloader was locked you wouldn't be able to flash Twrp. from the looks of it no one has a p607. it is all 605 or the wifi only one p600 and 601. stock rom with root and debloated works great. try a 605 rom. hopefully CM starts to pick up more then we are set.
Sent from my HTC One_M8 using Tapatalk
Do P605 ROMs even work on a P607T? I've been wondering that myself. I have a 607T and although I am very impressed with the stock ROM it just is never going to measure up to CM for me.
I've been thinking about giving the P605 CM 11 port a try in a few weeks when it's just a bit more stable, but I have no idea how similar they are or if my device would even boot after flashing it!
amirite said:
Do P605 ROMs even work on a P607T?
Click to expand...
Click to collapse
Yes.
kcrudup said:
Yes.
Click to expand...
Click to collapse
Anyway to flash the "modem.bin" and "NON-HLOS.bin" flash partitions yet?
kcrudup said:
Yes.
Click to expand...
Click to collapse
And how do i install a dialer app to make voice call with my haedset on my note 10.1 2014 edition (T-Mobile) p607t..is it possible at all??
TG2008 said:
Anyway to flash the "modem.bin" and "NON-HLOS.bin" flash partitions yet?
Click to expand...
Click to collapse
Guys... Did you even read that thread in the link?
You should be asking these questions there... That whole thread is dedicated to making calls on the P607T.... And if you read the thread you'll know the author hit a brick wall and a boot loader hack is needed to flash the proper modem files for phone calls.
amirite said:
Guys... Did you even read that thread in the link?
Click to expand...
Click to collapse
Reading is Fundamental, amirite? (... sorry, couldn't resist )
But yeah, go there for any updates.
kcrudup said:
Reading is Fundamental, amirite? (... sorry, couldn't resist )
But yeah, go there for any updates.
Click to expand...
Click to collapse
Haha. Thank you kcrudup for pointing to that thread, gave me some useful info on using P605 Roms on a P607T.
Any idea about what sort of problems may pop up from doing this? I got a reply in the CM thread that their P605 version of CM should work fine on my P607 but... Surely it can't be that simple? Any idea what differences there are between thecode of the two tablets or is it really that similar?
amirite said:
I got a reply in the CM thread that their P605 version of CM should work fine on my P607- but surely it can't be that simple?
Click to expand...
Click to collapse
I'm 95% sure the only difference physically is the radio "front end" hardware is tuned for the T-Mo LTE frequencies so the modem baseband SW reflects that, and software-wise all that's new is a few pre-installed apps like the "My T-Mobile" app and that (loud-and-annoying-as-hell-and-quickly-removed) T-Mobile "jingle" on startup; I've put several P605 ROMs on my 607T and everything's worked OK ('cause the bootloader won't let me overwrite the radios and potentially-dangerous bootloader files anyway).
kcrudup said:
I'm 95% sure the only difference physically is the radio "front end" hardware is tuned for the T-Mo LTE frequencies so the modem baseband SW reflects that, and software-wise all that's new is a few pre-installed apps like the "My T-Mobile" app and that (loud-and-annoying-as-hell-and-quickly-removed) T-Mobile "jingle" on startup; I've put several P605 ROMs on my 607T and everything's worked OK ('cause the bootloader won't let me overwrite the radios and potentially-dangerous bootloader files anyway).
Click to expand...
Click to collapse
Awesome info thanks so much!! So if I understand correctly, any differnces that would render my tablet completely inoperable are already protected from flashing? So I don't need to meet with the TARs for the Roms to remove the modem files or anything?
I mean, I don't mind if my radio breaks or something, I can handle flashing back to stock I am just never sure when I start flashing a new Android device what risks there are of bricking it completely (which, with Knox in the picture, could totally screw me).
So with that I will probably be going flash crazy tonight and tomorrow to test our some different 605 Roms starting with Cyanogen. I'll try to post any findings or quarks here or in those threads!
amirite said:
So I don't need to [mess?] with the TARs for the Roms to remove the modem files or anything?
Click to expand...
Click to collapse
You will have to remove all the "*.mbn" and "*.bin" files from (Samsung-supplied) non-P607T ROMs, though- Odin will abort the flash if it receives a bad status from the bootloader when the bootloader rejects the flash operation. But it should be a straightforward unzip/rm/zip operation to repack, and I'm sure the CM flashes are just "boot" and "system" (and possibly "recovery") partitions anyway.
kcrudup said:
You will have to remove all the "*.mbn" and "*.bin" files from (Samsung-supplied) non-P607T ROMs, though- Odin will abort the flash if it receives a bad status from the bootloader when the bootloader rejects the flash operation. But it should be a straightforward unzip/rm/zip operation to repack, and I'm sure the CM flashes are just "boot" and "system" (and possibly "recovery") partitions anyway.
Click to expand...
Click to collapse
so is it necessary to remove the above mentioned files. I can't just flash a p605 rom with twrp?
stoehner said:
so is it necessary to remove the above mentioned files. I can't just flash a p605 rom with twrp?
Click to expand...
Click to collapse
Yes it is necessary, the .mbn files relate to the bootloader and the .bin files is the modem and NON_HLOS, being that they are for a different ROM it could cause major problems and maybe even bricking. @kcrudup even mentioned the bootloader conflicting with Odin if the device models don't match, so it seems you won't get the 605's installed without removing said files.
Prod1702 said:
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Click to expand...
Click to collapse
I have been looking for a guide for flashing twrp onto my sm-p607t but i cant find one. I mainly need the correct twrp img.tar file for odin. I found this one ( openrecovery-twrp-2.6.3.3-lt03wifiue.img ) but I don't know if it is the right one. I used towelroot to root it and i used the proper supersu to disable knox so i just need the custom recovery now.
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
niko26 said:
Hi
Does anyone know anything a out the current status of Flashfire on the Pixel (XL)?
I've tried to backup data and the screen turned black, afterwards I hard to hard reset the phone to get it working again.
Click to expand...
Click to collapse
Good place to start https://plus.google.com/+Chainfire
danw_oz said:
Good place to start https://plus.google.com/+Chainfire
Click to expand...
Click to collapse
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
niko26 said:
I've tried to contact him already, plus asked him in one of his threads/posts. No response.
Click to expand...
Click to collapse
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
danw_oz said:
It's probably because he got sick of being asked the same question over and over again.
If I read the XDA forums http://forum.xda-developers.com/general/paid-software/flashfire-t3075433 searching for the word PIXEL. This app appears that people have this working on Pixel XL, but not since the November release
Click to expand...
Click to collapse
Thanks for your comment.
I was not asking why he was not replying to my questions - I've got total sympathy for that because the number of messages he might get must be insane.
My question still stands: Obviously Flashfire is not yet aware of the different layout of partitions on the Pixel phones. Does it still work correctly? If not, did Chainfire say anything about Flashfire being fixed to work with the pixels? I couldn't find anything, that's why I'm asking here.
I assume any announcement on it working on the Pixel will be made when it works on the Pixel. Much like superSU. (hope that doesnt sound like an ass thing to say) it's just the way things have been. unless someone else works on something and it looks like they are going to beat another dev to the punch, you don't usually see any info, much like boot-loader unlocks, rooting of a certain phone etc.. i.e when there is a bounty and team blahblah looks like they gonna take the glory, BANG! suddenly there's a solution that said dev was already working on secretly but wasn't planing on releasing any time soon but since there's competition, kinda thing. Know what I mean?
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
Hey just curious what you mean by this. I know that TWRP has some bugs but I thought everything with SuperSU was worked out
I'm thinking they are still working on having them coexist without one wiping the other
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
No they work fine, especially SuperSU. TWRP is in alpha but works for installing and most other things but backup and restore does not yet.
larsdennert said:
I'm thinking they are still working on having them coexist without one wiping the other
Click to expand...
Click to collapse
Wow, that was like week number one.
You're waaaaaay behind on updates.
Lol then we should get on chain fires case
larsdennert said:
SuperSU is going to be a much higher priority for him to get going reliably with twrp and the new partition layout.
Click to expand...
Click to collapse
What? SuperSU working perfectly with twrp. As others said twrp still in alpha and some features are iffy, but SuperSU is solid.
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
CZ Eddie said:
Are you verizon?
Because if you're verizon then add Verizon to your profile so people can appropriately address your questions.
And add your freaking state/country while you're at it. :good:
Click to expand...
Click to collapse
My apologies. T-Mobile, US - added to profile. Thanks for the suggestion!
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
You can sideload the update via ADB supposedly.
I've never used that method though.
I just flash the entire update on top of my old OS using flashboot and my guide here:
http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Make sure to remove the -w from the script if you don't want your old data/apps wiped.
Then re-root your phone afterwards.
Nothing to worry about there if it's not a Verizon phone.
s1dest3pnate said:
Without Flashfire, how do we install a new OTA update if we are rooted? What's the proper/safe procedure?
Click to expand...
Click to collapse
I do it like in this guide http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
s1dest3pnate said:
Very helpful, thanks guys. I did it and it worked - ran flash-all with -w removed. I wonder though if there's any downside to doing this that may not have been identified yet, such as extra space being taken up or diminished performance (even if negligible) possibly due to some duplication of data or something like that.
Click to expand...
Click to collapse
No, no downside at all. Flash all without the -w is how most people do it. It could even be argued that it is better.
Sent from my Pixel XL using XDA Labs
Just wondering when the new security update will be out as I feel the last one is making my battery drain quite a lot. Tried all the normal routine stuff and still nothing specially after two factory resets. Here is hoping that with the new software it will be fixed
Hey Goku80, judging solely by past-trends, it should most certainly be out today.
It's live guys! https://dl.google.com/dl/android/aosp/crosshatch-pq3a.190801.002-factory-15db810d.zip
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
BoboBrazil said:
Flashed August full image from google website and touchscreen doesn't work. Can't even use pin to access phone. Anyone else?
Click to expand...
Click to collapse
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
ota is not here yet
Goku80 said:
Could I flash it without root? Sorry it has been a long while since I did something like this. I remember on the OnePlus you could flash manually
Click to expand...
Click to collapse
The OTA can be flashed using stock recovery. No wipe.
spotmark said:
The OTA can be flashed using stock recovery. No wipe.
Click to expand...
Click to collapse
True but means I need to use ADB which I don't have a pc
Goku80 said:
True but means I need to use ADB which I don't have a pc
Click to expand...
Click to collapse
You can flash it as long as your BL is unlocked. It has nothing to do with root. You still need to use the flash-all batch file though, so a computer is still necessary.
Hello, I have a problem to flash any ROM, i flashed a pxiel GSI for s9 snapdragon but now I can't flash another ROM, TWRP says something like:
dev/block/bootdevice/by-name/system at/ system
I don't know what can I do I tried to return to ROM stock using Odin but it doesn't flash the ROM
ottoland said:
Hello, I have a problem to flash any ROM, i flashed a pxiel GSI for s9 snapdragon but now I can't flash another ROM, TWRP says something like:
dev/block/bootdevice/by-name/system at/ system
I don't know what can I do I tried to return to ROM stock using Odin but it doesn't flash the ROM
Click to expand...
Click to collapse
Bro if you would of stood on stock and didn't modify this device you wouldn't have this issue.... There's a possibility you could of hard bricked your device however just maybe you can come out this situation reflash twrp and hopefully you could be able to flash something....
([emoji3590]09-09-18[emoji3590])
ottoland said:
Hello, I have a problem to flash any ROM, i flashed a pxiel GSI for s9 snapdragon but now I can't flash another ROM, TWRP says something like:
dev/block/bootdevice/by-name/system at/ system
I don't know what can I do I tried to return to ROM stock using Odin but it doesn't flash the ROM
Click to expand...
Click to collapse
the only snapdragon phones that are rootable are the chinese versions eg the G9600, no root for the G960U
PoochyX said:
Bro if you would of stood on stock and didn't modify this device you wouldn't have this issue.... There's a possibility you could of hard bricked your device however just maybe you can come out this situation reflash twrp and hopefully you could be able to flash something....
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
i would suggest flashing stock instead of TWRP on second thought
youdoofus said:
the only snapdragon phones that are rootable are the chinese versions eg the G9600, no root for the G960U
i would suggest flashing stock instead of TWRP on second thought
Click to expand...
Click to collapse
I mean honestly these S9s and S10s should be left alone the performance is crazy good off the rift
([emoji3590]09-09-18[emoji3590])
PoochyX said:
I mean honestly these S9s and S10s should be left alone the performance is crazy good off the rift
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
my S9 gets laggy from time to time, but its otherwise very good performance-wise. I havent felt the need of persuing root with it because its a: impossible atm b: not worth it. The reason people rooted in the first place was to customize, tweak for performance enhancements and increase battery life. None of those things are that much of an issue anymore these days, so root is becoming unneeded by a great many, including myself. And i root EVERYTHING!!!
youdoofus said:
my S9 gets laggy from time to time, but its otherwise very good performance-wise. I havent felt the need of persuing root with it because its a: impossible atm b: not worth it. The reason people rooted in the first place was to customize, tweak for performance enhancements and increase battery life. None of those things are that much of an issue anymore these days, so root is becoming unneeded by a great many, including myself. And i root EVERYTHING!!!
Click to expand...
Click to collapse
How a S9 gets laggy that's a scary thought it's a S9
([emoji3590]09-09-18[emoji3590])
As the title states. Am just wondering what happens exactly when you take a ota on a rooted device. Am not talking about the full ota. Am talking about the smaller otas just curious to know
v.konvict said:
As the title states. Am just wondering what happens exactly when you take a ota on a rooted device. Am not talking about the full ota. Am talking about the smaller otas just curious to know
Click to expand...
Click to collapse
You can't on OOS. You have to take full.
jhlogan said:
You can't on OOS. You have to take full.
Click to expand...
Click to collapse
That much i know. I want to know what will happen
v.konvict said:
That much i know. I want to know what will happen
Click to expand...
Click to collapse
Do it then tell us
ej8989 said:
Do it then tell us
Click to expand...
Click to collapse
Am sure its already been done just wanna understand how root affects the partions when taking an ota
v.konvict said:
Am sure its already been done just wanna understand how root affects the partions when taking an ota
Click to expand...
Click to collapse
You'll end up breaking your phone's functionality, simply causing boot looping, unable to root your device and have to install a full base factory ota to fix the damage done. And you wouldn't even be able to backup anything either since the device will basically be semi-bricked
Shen Ron said:
You'll end up breaking your phone's functionality, simply causing boot looping, unable to root your device and have to install a full base factory ota to fix the damage done. And you wouldn't even be able to backup anything either since the device will basically be semi-bricked
Click to expand...
Click to collapse
Thanks for this. Am not new to flashing updates with root. Was hoping for a more detailed explanation. Like the ota updates a certain partition which when rooted will cause a bootloop because a certain partition wont readable
v.konvict said:
Thanks for this. Am not new to flashing updates with root. Was hoping for a more detailed explanation. Like the ota updates a certain partition which when rooted will cause a bootloop because a certain partition wont readable
Click to expand...
Click to collapse
Every partition except the boot partition will be ok for the most part but you'll still end up boot looping even if you installed magisk over again, so unless you do a fresh install which depending on how badly you messed something up or forgot to disable any modules, you will have to start from scratch to save your phone. But if you already made a backup whether it's before everything went south or in twrp to save your data then you should be okay