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.
So my phones digitizer stopped responding last night. I plan to buy a used phone exact same model, and I am aware of all the steps such as baseband and modem and such needed to get the phone to the status that is required to apply the rom I have on my old phone.
My question is since my digitizer isn't working I cannot use TWRP to perform the backup. I will needn't to do it from some other option such as using my laptop or maybe some other option. Does anyone know how I can perform a backup without using the touch screen?
Thank you! Love XDA!
Zaileion said:
So my phones digitizer stopped responding last night. I plan to buy a used phone exact same model, and I am aware of all the steps such as baseband and modem and such needed to get the phone to the status that is required to apply the rom I have on my old phone.
My question is since my digitizer isn't working I cannot use TWRP to perform the backup. I will needn't to do it from some other option such as using my laptop or maybe some other option. Does anyone know how I can perform a backup without using the touch screen?
Thank you! Love XDA!
Click to expand...
Click to collapse
Google is your friend. You can try this but I don't know. Sounds doable
http://androidforums.com/threads/broken-screen-no-backup-and-need-your-data-try-this.841614/
I know we are not suppose to use outside links but I didn't find anything here.
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])
Hi there!
I've installed the full OTA SQ1D.211205.016.A4 using Adb sideload but I had have installed another OTA version, specifically SQ1D.211205.016.A1.
I've tried to install the correct version over using adb sideload but it fails because it says is an older version.
How can I install the correct OTA for my Pixel 6 Pro?
Cheers.
sgbmad said:
Hi there!
I've installed the full OTA SQ1D.211205.016.A4 using Adb sideload but I had have installed another OTA version, specifically SQ1D.211205.016.A1.
I've tried to install the correct version over using adb sideload but it fails because it says is an older version.
How can I install the correct OTA for my Pixel 6 Pro?
Cheers.
Click to expand...
Click to collapse
Hmm strange, as I'd done similarly in that I'd installed A1 and needed A4. However I didn't experience an issue with side loading...
Perhaps you could try flashing the full factory image but with the -w removal (research this fully) to avoid data loss, so essentially dirty flashing the full image should help?
cd993 said:
Hmm strange, as I'd done similarly in that I'd installed A1 and needed A4. However I didn't experience an issue with side loading...
Perhaps you could try flashing the full factory image but with the -w removal (research this fully) to avoid data loss, so essentially dirty flashing the full image should help?
Click to expand...
Click to collapse
Thank you for your response cd993. Then, a full factory image flash with full wipe also works, it's true?
sgbmad said:
Thank you for your response cd993. Then, a full factory image flash with full wipe also works, it's true?
Click to expand...
Click to collapse
Sure, a full wipe will indeed clear all data of yours and install the factory image. But I'd try first to remove the line of code in the flash-all.bat file that prevents a data wipe. Plus also there's the factor of keeping root, if you are actually rooted. Let me know if you need any guidance on this though there are lots of info around on these forums
cd993 said:
Sure, a full wipe will indeed clear all data of yours and install the factory image. But I'd try first to remove the line of code in the flash-all.bat file that prevents a data wipe. Plus also there's the factor of keeping root, if you are actually rooted. Let me know if you need any guidance on this though there are lots of info around on these forums
Click to expand...
Click to collapse
Thank you so much,
Well, first of all I would need to know where download the factory image and how can I remove the code in the flash-all.bat. If you show me where can I found that info your help will be very apreciate.
On the other hand, I still have no clear what would be the version I need. I bought the phone at the Google Store in Germany. Also, I do not really do not know what the difference between one version is and if it really is important to put the one that corresponds to you.
sgbmad said:
Thank you so much,
Well, first of all I would need to know where download the factory image and how can I remove the code in the flash-all.bat. If you show me where can I found that info your help will be very apreciate.
Click to expand...
Click to collapse
No problem. The factory image can be found here:
https://developers.google.com/android/images
Are you wanting to root? Forgive me I'm mistaken, though I sense that you are relatively new to this and so I'd suggest following the guide found here:
https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/
cd993 said:
No problem. The factory image can be found here:
https://developers.google.com/android/images
Are you wanting to root? Forgive me I'm mistaken, though I sense that you are relatively new to this and so I'd suggest following the guide found here:
https://forum.xda-developers.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/
Click to expand...
Click to collapse
Well, I'm not new to this really, but it is my first Pixel. Long time ago I was addicted to flash ROMs
Currently I prefer to use the phone without root.
sgbmad said:
Well, I'm not new to this really, but it is my first Pixel. Long time ago I was addicted to flash ROMs
Currently I prefer to use the phone without root.
Click to expand...
Click to collapse
Great, you'll enjoy this phone!
There's lots of how-to guides on this forum so give them all a good read to benefit your understanding on how the Pixel works and let us know if any questions
cd993 said:
Great, you'll enjoy this phone!
There's lots of how-to guides on this forum so give them all a good read to benefit your understanding on how the Pixel works and let us know if any questions
Click to expand...
Click to collapse
Thank you cd993
I didn't know the Android Flashing Tool for Chrome. There is an option to flash without wipe the device. I'll probably use this tool for flash an image.
sgbmad said:
Thank you cd993
I didn't know the Android Flashing Tool for Chrome. There is an option to flash without wipe the device. I'll probably use this tool for flash an image.
Click to expand...
Click to collapse
Yeah that's a very handy one, especially when not wanting to root.
Have fun!
cd993 said:
Yeah that's a very handy one, especially when not wanting to root.
Have fun!
Click to expand...
Click to collapse
Sure! I think I'll wait for Google says something about this:
[U: Not the wrong build] Latest Google Pixel 6 update is causing network issues in Europe
Some Pixel 6 and Pixel 6 Pro owners in Europe have found that the December update is causing various network issues on their phones.
9to5google.com
Thanks!
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
granosalis said:
Hello everyone
I have a question for you who are more experienced. I'm missing from the Android ecosystem from the glorious Pixel 3 from Samsung, about 11 years ago. I loved the Pixel3 user interface, so polisched and modern for the times. Now I have finally decided to do the swith from my iPhone xs to Pixel 6 pro.
I bought the phone in USA, directly from google, but I live in Italy.
Do you advise me to flash the P6P with a different factory image?
I understand that the code name for P6P is raven, but it's not clear to me which factory image I should upload. Can you give me the right suggestion?
Thanks in advance for the support.
Regards,
Giuseppe
Click to expand...
Click to collapse
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
roirraW edor ehT said:
Hi, I mention in this post which image is for where. https://forum.xda-developers.com/t/...a4-and-otas-for-017-016-a1-available.4384059/
I believe you want the Global one, SQ1D.211205.016.A1.
Click to expand...
Click to collapse
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
granosalis said:
Thanks,
I do not have the phone right now in my hands, and most probably this will not happen for the next 10 days. Maybe is's worth waiting for the Jan update?
Click to expand...
Click to collapse
You're welcome! It's at least 50/50 chance that it would be better to wait. I have no problem on the .017 December firmware, but plenty of folks do, and I haven't had much of a problem at all with any of the firmwares so far.
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
Because it fixes some things for some people.
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
granosalis said:
So January update is finally here and, if I well understood is a Global (unified) version.
I have downloaded raven sq1d.220105.007 Factory.
And sorry for the stupid question, which is the best way to install it on a brand new, out of the box P6P?
I have to start the phone first and do the first configuration or I can immediately flash the factory image and start from a fresh new install? How?
Click to expand...
Click to collapse
You'll have to allow the phone to boot up first since you'll need access to the OS to perform some commands on your PC. You can just allow the phone to boot and skip a lot of the setup process, only because flashing the most recent factory image will put you back to stock, AKA wipe your phone back to where it was when it left the factory, and then once the new image has been installed you can do a proper phone setup from scratch.
If you're not familiar with using terminal commands and don't want to run the risk of messing up your phone, I suggest you use the Android Flash Tool since it'll do everything for you and is fairly simple. Just connect your device over USB and visit the Android Flash Tool using the link below. Android Flash Tool works with any Web browser that supports WebUSB, such as Chrome or Edge. The Android Flash Tool guides you step-by-step through the process of flashing your device - there's no need to have tools installed, but you will need to unlock your device and enable USB Debugging from Developer Options.
I've provided a link on how to enable USB Debugging and Developer Options, here - https://source.android.com/setup/contribute/flash
To flash the latest January Stock image on your device, simply visit this link - https://flash.android.com/build/8030436?target=raven-user&signed
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
RetroTech07 said:
Click through those links and see if it all makes sense; and if not, report back. Either I (or someone else) will be happy to help.
Click to expand...
Click to collapse
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
They do the same thing, however the android flash tool is much easier to use.
granosalis said:
What I do not understand is why there are those who force the installation of a release that has been intentionally removed from distribution. If google did there will be a reason, I think. But perhaps the benefits are greater than the disadvantages.
Click to expand...
Click to collapse
I forced it on day one and I guess I was one of the lucky ones that didn't have any issues.
granosalis said:
I would like to thank you. You were really very helpful.
I have a doubt: what's the difference between loading a Factory image with ADB and using the Android Flash tool?
Click to expand...
Click to collapse
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
RetroTech07 said:
You're welcome! I'm assuming all went well and you're on the latest release?
The flash tool is automated and much simpler. it's a better way to make sure you're fully stock if you were planning on selling the device or trading it in.
Think of ADB as a more advanced way of interacting with your phone when you plan on modifying it from stock. The flash tool only allows you to flash official Google images, unless a developer has implemented the same tool with a custom ROM they've developed that you plan on using.
I'm sure there's other things I'm missing that folks will chime in with.
Click to expand...
Click to collapse
No my phone should arrive in about 10 days if everything goes as planned.
It is not easy to take a P6P 256gb white from italy , this model, in fact, is not sold in europe for what I know.
While waiting I try to keep myself informed. It's been a long time since my Galaxy Nexus.