Why root an android device? - General Questions and Answers

I get asked sometimes why root an android device. What is your reasons for rooting and what are the benefits? I'd be interested to hear your views.
Sent from my Nexus 7 using xda app-developers app

st3vo_1986 said:
I get asked sometimes why root an android device. What is your reasons for rooting and what are the benefits? I'd be interested to hear your views.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Most phones come with the operating system "locked" by the manufacturers. They do not want their devices to be meddled with and made unusable by the user. There are valid reasons for them to do this, some I think will be as follows.
1. Maintain integrity of the phone they sell.
2. Lower Helpdesk cost. Users who do not know how, meddled and rendered phone un-usable during warranty and then make claims for repair under warranty terms. This will unrealistically increase the cost of providing repair works under the warranty period.
3. Ease of maintenance. There is one copy of the ROM. If the user brings in a phone that is not working, they will just flash the standard ROM over as a first check. This is easy to do for the first step of troubleshooting.
4. Avoid bad publicity- the word of mouth that there is a high rate of return for maintenance (due to incompetent wannabe phone hackers) spread and this creates a public image of the phone being "unreliable".
Reasons for rooting is mainly to be able to use the phone as how we like to use it. Some examples:
1. Not happy with the phone producer's version of Android user-interface. Same version of Android, but different manufacturers offer their own take on the user interface. By rooting the phone, the user can change to a custom ROM that he finds suitable.
2. Not happy with the manufacturer's choice of apps. For example, the media-player app. Without rooting, you cannot uninstall the media app that came with the phone ROM. Yes, you can install an additional media-player app, but then you will have some bloatware (manufacturer's app) that you cannot uninstall.
3. Change to a newer (or older) version of Android. E.g., Older phones that are rooted can upgrade from Android 2x to 4x, if the hardware is suitable.
4. Change operating system. After having an Android phone, a user might want to change his mind try out a Windows Phone. After rooting the phone, it is possible to change the operating system from Android to Windows and vice versa. A good example are the older WM6x phones, such as HTC Touch HD or HD2, they can be installed and work with Android, and if the user is not happy, revert to WM6x. Without rooting the phone, this cannot be done.
5. Build and install our own tailor-made custom ROM using a Kitchen+ROM of choice. Sometimes, a custom ROM provided by an independent developer may not be entirely suitable for all of us. With the Kitchen+ROM, it is possible to break-down the ROM to components, and select the components to build another ROM (a variant of the original) that meets a specific requirement. For example, it is possible to exclude GoogleMarket, Facebook, Twitter apps and build a ROM without them, if a person wishes.
There are many more other reasons, but I guess the main ones are those.
Hope this helps.

Related

[Q] Why there is no uninstall feature in Android?

I have about two weeks experience with Android OS and as a software developer I will be interested to know the technical details behind the Android OS.
I have already noticed this is possible to upgrade applications ported with the handset's ROM i.e. the Market app. This raised the question to me why can't I uninstall applications from the ROM without rooting or risking my handset's warranty to achieve this?
Is my expectation as a user of computers for 20 years unreasonable to think in 2010 with all software development and technological advances the uninstall feature should have been in Android OS from day one?
This is not exactly like Google is the first company in the world developed an OS to just the lack of experience with what users would want. From what I have seen so far in world of Android is that, the first thing users would want to know how to root their handset to remove packages that they have no use for.
My guess is that Google doesn't want users removing Systems apps. I'm assuming that they think that these applications are core and thus don't want you removing them. Remove the market, no more apps... or way to get it back etc.
Applications installed by you can be uninstalled, I'm just thinking it is the same as in windows, you can't uninstall the task manager etc (Bad example but meh =P)
Very simple - to prevent lay users from removing critical components.
Can you imagine the service costs involved in reparing devices that that have been damaged by people trying to remove bloatware?
They still give you the option to restore.
OK DISREGUARD THIS AS I MISSED THE PART ABOUT NEEDING TO ROOT!
They can be removed but its not recommended to do so without know EXACTLY what your removing and weather is vital to your phones operating system.
BUT in order to do so your phone needs root access, and root explorer installed. There are several forums on just about all android support sites that explain how to root, install the manager, and which apps/files NOT to remove.
J_HaX said:
They can be removed but its not recommended to do so without know EXACTLY what your removing and weather is vital to your phones operating system.
BUT in order to do so your phone needs root access, and root explorer installed. There are several forums on just about all android support sites that explain how to root, install the manager, and which apps/files NOT to remove.
Click to expand...
Click to collapse
Ye u can remove almost every stock app but this may affect the stability of your phone, modifying your phone always comes with the option restoring it back to default. If something goes wrong with moding (something really hard and extraordinary rare ) u can restore it. Browsing through Xda might solve many questions, we all didn't wanted stock rom (not because it was bad, because we can have s omething better. This community has VERY VERY good developers.
Androids own!!!
One thing I still don't get is...
How can Google upgrade Market app without the su privilage but the rest of the world has to root their phones to remove bloatware such as 'amazon mp3'?
@ftgg99: How much bloatware in Windows cost Microsoft or PC manufacturers? None in fact they get paid to include them with your hardware. However, I see an issue with mobile devices. You have already paid for the ROM storage, the bigger ROM size is the more expensive your handset would be, then the manufacturer uses your already paid ROM to make even more money by installing bloatware. I would be a fool to think manufacturers would pass on a percentage of the bloatware earnings by reducing the cost of their products to the consumers in this model.
The way I see it, the burden has been put on the communities such as xda. Users wouldn't ask the manufacturers how to root their handsets and this is left to the dedicated individuals to overcome the mess compnies normally leave us with. I'm not going to say the mess is a cost saving measure by companies.
The thing is that there are a lot more people buy and use phones than computers. After someone buys a smart phone with intention to use for calls, text, web and to use some apps, they realize the possibilities of the smart phone, they start digging in to the files, therefore Google blocked the root folder from modifying, otherwise Google would have to repair warrantied phones that didn't have to end up there just because people didn't know or care what they did. But if you got passed ROOTING, you must know what you are doing and from this point you can modify files and apps, but now ROOTING becomes too easy.
Basically just because too many juveniles got their hands on the equipment.
CSharpHeaven said:
One thing I still don't get is...
How can Google upgrade Market app without the su privilage but the rest of the world has to root their phones to remove bloatware such as 'amazon mp3'?
Click to expand...
Click to collapse
I'm also very interested to read the answer for this one!
CSharpHeaven said:
One thing I still don't get is...
How can Google upgrade Market app without the su privilage but the rest of the world has to root their phones to remove bloatware such as 'amazon mp3'?
Click to expand...
Click to collapse
RAMMANN said:
I'm also very interested to read the answer for this one!
Click to expand...
Click to collapse
The answer, from my point of view, is quite simple: they just upgrade the application on /data/app ON TOP of the /system/app default Market version. So, you can always go back to your "default" version just by "uninstalling updates".
Summary: they do not upgrade the Market form ROM, just install the new version on top.
CSharpHeaven said:
I have about two weeks experience with Android OS and as a software developer I will be interested to know the technical details behind the Android OS.
I have already noticed this is possible to upgrade applications ported with the handset's ROM i.e. the Market app. This raised the question to me why can't I uninstall applications from the ROM without rooting or risking my handset's warranty to achieve this?
Is my expectation as a user of computers for 20 years unreasonable to think in 2010 with all software development and technological advances the uninstall feature should have been in Android OS from day one?
This is not exactly like Google is the first company in the world developed an OS to just the lack of experience with what users would want. From what I have seen so far in world of Android is that, the first thing users would want to know how to root their handset to remove packages that they have no use for.
Click to expand...
Click to collapse
Have you tried to work with iPhone(don't know about iPhone 4)? They build fortress around their system and even the apps you install cannot be uninstalled until you gailbrake it and use 3rd party installer to uninstall. And not talking about the "MONOPLY" they run with AT&T.

Android Backups

Let me start by saying I'm not the new kid on the block. I've been using Android since it's inception. I am an Android fanatic. I root, tinker with roms, apps, settings, kernels, mods, etc. . You name it, I do it( as far as android is concerned). I say this with a singular purpose, don't flame me for this question because to me it seems completely valid.
Why does android not have the ability backup itself built in( this should not require root) ?
Why has Google not implemented the ability to do so from a computer? <<- This should be identical to how an iPhone is backed up ( don't flame on this because it's actually one of the things iPhone does better than anyone else, and I hate Apple. However I give credit where it's due)
Don't tell me we have plenty of options even if we're not rooted, if this we're the case then people would not rely on clockwork mod recoveries, twrp, or the like. Those types of restores should be available without having a custom recovery, custom rom, or root in and of itself.
Also don't bring up the backup using adb, it's hidden, and it is mediocre. It fails to backup a lot of things.
I'm asking only about a complete backup option, with possibly the option to select and deselect certain types of data<<--This to should be similar to backing up an iPhone .
Now who here would like this to be a feature implemented in the next version of android?
If you answer my questions please just be clear and concise.
I will respond should it be warranted, or requested.
This is not a flaming thread, don't do it.
I look forward to all of your responses.
Sent from my LG-E980 using xda app-developers app
playerjunglejosh said:
Let me start by saying I'm not the new kid on the block. I've been using Android since it's inception. I am an Android fanatic. I root, tinker with roms, apps, settings, kernels, mods, etc. . You name it, I do it( as far as android is concerned). I say this with a singular purpose, don't flame me for this question because to me it seems completely valid.
Why does android not have the ability backup itself built in( this should not require root) ?
Why has Google not implemented the ability to do so from a computer? <<- This should be identical to how an iPhone is backed up ( don't flame on this because it's actually one of the things iPhone does better than anyone else, and I hate Apple. However I give credit where it's due)
Don't tell me we have plenty of options even if we're not rooted, if this we're the case then people would not rely on clockwork mod recoveries, twrp, or the like. Those types of restores should be available without having a custom recovery, custom rom, or root in and of itself.
Also don't bring up the backup using adb, it's hidden, and it is mediocre. It fails to backup a lot of things.
I'm asking only about a complete backup option, with possibly the option to select and deselect certain types of data<<--This to should be similar to backing up an iPhone .
Now who here would like this to be a feature implemented in the next version of android?
If you answer my questions please just be clear and concise.
I will respond should it be warranted, or requested.
This is not a flaming thread, don't do it.
I look forward to all of your responses.
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
Well, you want some gain, you would have to bear some pain.......
Well... to be honest, i really don't use backups much, just titanium backup and we've got non-root alternatives as you stated, so , it's not a matter of great attention to me.... I like fresh and clean installs
playerjunglejosh said:
Let me start by saying I'm not the new kid on the block. I've been using Android since it's inception. I am an Android fanatic. I root, tinker with roms, apps, settings, kernels, mods, etc. . You name it, I do it( as far as android is concerned). I say this with a singular purpose, don't flame me for this question because to me it seems completely valid.
Why does android not have the ability backup itself built in( this should not require root) ?
Why has Google not implemented the ability to do so from a computer? <<- This should be identical to how an iPhone is backed up ( don't flame on this because it's actually one of the things iPhone does better than anyone else, and I hate Apple. However I give credit where it's due)
Don't tell me we have plenty of options even if we're not rooted, if this we're the case then people would not rely on clockwork mod recoveries, twrp, or the like. Those types of restores should be available without having a custom recovery, custom rom, or root in and of itself.
Also don't bring up the backup using adb, it's hidden, and it is mediocre. It fails to backup a lot of things.
I'm asking only about a complete backup option, with possibly the option to select and deselect certain types of data<<--This to should be similar to backing up an iPhone .
Now who here would like this to be a feature implemented in the next version of android?
If you answer my questions please just be clear and concise.
I will respond should it be warranted, or requested.
This is not a flaming thread, don't do it.
I look forward to all of your responses.
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
it seems like a interesting idea, when i had a ipod touch back then, i jail broke it and after a few days it decided to not want to turn on (stayed at apple logo) and iTunes detected it and i was able to restore it to brand spanking new. i dont think it would be possible for google to do so without root ( and a few Sues here and there from apple ) Android is based off linux right? we can make backups on linux because we have Super User permissions, we own this Computer, we can do all the Admin Crap we want. for android, Samsung owns your phone or HTC owns your phone, You do not have full Admin permissions on your device to make a backup (of the sort we are talking about) also im sure the OEM's would be angry with people easily being able to Restore their broken device so they wont buy that phone a second time or even get a bigger more expensive phone.
The reason I bring it up is not because of fresh installs, or whatever.
Here is an example:
A regular non techie person, has Android phone x. They make a complete backup using the aforementioned capabilities that isn't implemented yet. There phones screen goes out, they drop there phone in water, whatever the phone is not in working condition. Well if they had the capabilities that I'm referring to, that phone would need to be called on warranty, or for the latter insurance. Either way they are sent a new device, same model as they had previously. Now they sync there backup, and there back up and running.
The way it is now, that person would have to hope that Google syncs back there apps ( it has never worked for me, except for contacts, and for the most part developers aren't backing up there app data to Google so that is not something you get back).
Not to mention settings are never synced, so there's that.
Point being android does not have any good options to make a complete backup. The only real options require root, which an average consumer will not have. This is why I'm saying it should be simplified, to where we can do it via one click on a pc.
I personally would like to start a petition for this, as anyone could benefit from this function.
Sent from my LG-E980 using xda app-developers app
eatsleep said:
Well, you want some gain, you would have to bear some pain.......
Well... to be honest, i really don't use backups much, just titanium backup and we've got non-root alternatives as you stated, so , it's not a matter of great attention to me.... I like fresh and clean installs
Click to expand...
Click to collapse
True, but if it's implemented within android that's not really an issue.
Look at it like this, we used to need root to screen shot, to Hotspot, to install apps out of the Android market ( not really been an issue since it hasn't been Google play because android was fairly mature by then). Point is Google gave those features, and implemented them natively, this removing need to root to do them. The same could be done with the ability to make backups.
Sent from my LG-E980 using xda app-developers app
Trozzul said:
it seems like a interesting idea, when i had a ipod touch back then, i jail broke it and after a few days it decided to not want to turn on (stayed at apple logo) and iTunes detected it and i was able to restore it to brand spanking new. i dont think it would be possible for google to do so without root ( and a few Sues here and there from apple ) Android is based off linux right? we can make backups on linux because we have Super User permissions, we own this Computer, we can do all the Admin Crap we want. for android, Samsung owns your phone or HTC owns your phone, You do not have full Admin permissions on your device to make a backup (of the sort we are talking about) also im sure the OEM's would be angry with people easily being able to Restore their broken device so they wont buy that phone a second time or even get a bigger more expensive phone.
Click to expand...
Click to collapse
Ment to quote you in the above quote.
Sent from my LG-E980 using xda app-developers app
playerjunglejosh said:
Ment to quote you in the above quote.
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
well i think google has done enough to make google as great as it is today, im thinking the reason why we dont have one of these options could be that they want us to make a program for this? im sure eventually they will have such a option to download multiple apps on a que so we can install them quickly without have to go over Each specific one.
Well actually what I'm referring to would have to be done by Google.
Here's why, locked bootloaders, encrypted boot loaders, etc.
The developer community could make such a program, but it's going to need root to be able to do what I'm referring to.
Google would have to make the OEMs use a standard, so that it could be accomplished without exposing there software. This would probably mean our backups would have to be encrypted on a per Google account basis.
It's not an impossible feat.
1) It would simply require Google to make the standard, and ensure that it's enforced. Ignoring it would mean no Google services, which to most is a huge negative.
2) Google release the program.
3) OEM would need to ensure compliance with said program, and submit software drivers to Google, or simply distribute them via there website( as they do now). Preferably submitting them to Google.
4) Making backups would become so much easier, especially for the average joe
Sent from my LG-E980 using xda app-developers app
Trozzul said:
well i think google has done enough to make google as great as it is today, im thinking the reason why we dont have one of these options could be that they want us to make a program for this? im sure eventually they will have such a option to download multiple apps on a que so we can install them quickly without have to go over Each specific one.
Click to expand...
Click to collapse
One big problem with this is the syncing of app data. I don't want to have to restart my games every time I get a different device( especially a replacement device that is the same model as my prior device).
Another thing, I keep an electronic checkbook, and would be thrilled if I could keep that app data from here on out, even when I change devices. However this definitely something I don't want Google's prying eyes on. So only local backup, which makes the complete backup via pc even more vital.
Maybe since businesses are the next aim, they will implement this feature because it can be vital certain data be absolutely private, but still have backups.
Sent from my LG-E980 using xda app-developers app

Rooting Sony's e-reader DPT-RP1 and DPT-CP1

Update (5/18/2019)
Since the first tool was released, HappyZ has improved many features so I think I can just refer to
* HappyZ's rooting guide: https://github.com/HappyZ/dpt-tools/wiki/The-Ultimate-Rooting-Guide
- The only thing I want to add as Windows user is (because the guide is for Mac/Linux users) it gets much easier if you use Linux terminal like cygwin, and the port name should be something like COM# where # can be found in Device Manager by comparing before/after you attach the device.
* HappyZ's upgrade guide: https://github.com/HappyZ/dpt-tools/wiki/The-Upgrade-Guide (Recommend to read this before/after you update the new firmware.)
You may donate a cup of coffee to him there Thanks to all others who contributed a lot.
--
Update (12/02/2018) -- These are outdated.
Finally we manage to root the device! Many thanks to all of your efforts.
Just refer to HappyZ's well written guide: https://github.com/HappyZ/dpt-tools
For whom have never used python like me (and probably using Windows):
(1) Install Python 3 and add it to PATH.
(2) Install MINGW64 and run scripts here instead of Powershell due to xxd issue if you are on Windows.
(2) pip httpsig pyserial on bash.
(3) Download HappyZ's dpt-tools and unzip.
(4* this issue is fixed by HappZ)
(5) Follow HappyZ's guide. You should execute dpt-tools.py in the folder you unzipped to use get-su-bin because of how the script is written.
Some suggestions after rooting (let me know if you have better ideas):
Here is my setup: install "E-ink Launcher" and "Multi action home button" using adb install.
Use adb shell am start -a android.intent.action.MAIN to change the main launcher to your launcher.
Then change the setting of Multi Action Home button (say, the height should be large to be visible in the bottom) and assign its function to be Home for click and Back for double-click.
Whenever you want to use Sony's apps (these are good for pdf markup), just push the home button to open the pop-up menu.
Otherwise, touch the Multi Action Home Button to access to other Android apps. So far I've never experience any crash.
Yet more tips:
Some complain fonts are too small after installing generic apps.
adb shell wm density 320 changes your DPI by 2 times (160 is a default value.) EDIT: I found 200 is quite enough that does not distort Sony apps too much.
My application is using "Tasker" to execute the above code when specific apps are open and execute wm density reset when the apps are closed.
The reason why we cannot change the global DPI is sadly because it makes the default apps by Sony so awkward.
Alternatively, I could successfully install Xposed to try App Settings but this app crashed.
You can also install Gboard (but it has no hide button, so prepare with virtual back button) if you need another keyboard.
Enjoy your DPT devices
--
Sony recently released a new digital paper device DPT-RP1, apparently using their own linux firmware but underlying on Android 5.1.1. Few weeks ago, some Chinese successfully hacked it to jailbreak for third-party apps (without changing the original firmware), but they don't share any information to sell those hacked devices. I'm willing to pay for it, but it is too risky to send my device to China so I'm trying to root it by myself.
I don't know much about this world, but I found some information that might be helpful. It uses Marvell A140 IoT Processor a.k.a. PXA1908. There are two Android smartphones (as the same version 5.1.1) with this chip - Samsung Xcover 3 and Samsung Galaxy Grand Prime. Fortunately, they have been both rooted in the past here.
Is this information really helpful to root my device? If so, is there any way to apply the previous methods to easily jailbreak DPT-RP1? I think the problem here is that it does not look like Android at all, so has no setting menu or developer tools. And not sure how to enter to the recovery mode since it only has two buttons - power/menu.
I'd appreciate any help or advice. Thanks!
And here you can find source codes.
oss.sony.net/Products/Linux/dp/DPT-RP1.html
sartrism said:
Sony recently released a new digital paper device DPT-RP1, apparently using their own linux firmware but underlying on Android 5.1.1. Few weeks ago, some Chinese successfully hacked it to jailbreak for third-party apps (without changing the original firmware), but they don't share any information to sell those hacked devices. I'm willing to pay for it, but it is too risky to send my device to China so I'm trying to root it by myself.
I don't know much about this world, but I found some information that might be helpful. It uses Marvell A140 IoT Processor a.k.a. PXA1908. There are two Android smartphones (as the same version 5.1.1) with this chip - Samsung Xcover 3 and Samsung Galaxy Grand Prime. Fortunately, they have been both rooted in the past here.
Is this information really helpful to root my device? If so, is there any way to apply the previous methods to easily jailbreak DPT-RP1? I think the problem here is that it does not look like Android at all, so has no setting menu or developer tools. And not sure how to enter to the recovery mode since it only has two buttons - power/menu.
I'd appreciate any help or advice. Thanks!
Click to expand...
Click to collapse
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
Click to expand...
Click to collapse
Thanks for suggesting a general principle! I just use the word jailbreaking not because I'm an iPhone user. What I actually want to do as the first step is not rooting an android system, but revealing it from the current customized linux system. Rooting is the next step if necessary. If the word choice is still not accurate and bothers you, I apologize.
It has apparently no typical bootloader, and neither PC nor adb recognize it as an android device. In fact, direct USB file transfer is blocked so I need to use Sony's designated software. But an android system surely coexists according to the hacker who already rooted it.
sartrism said:
Thanks for suggesting a general principle! I just use the word jailbreaking not because I'm an iPhone user. What I actually want to do as the first step is not rooting an android system, but revealing it from the current customized linux system. Rooting is the next step if necessary. If the word choice is still not accurate and bothers you, I apologize.
It has apparently no typical bootloader, and neither PC nor adb recognize it as an android device. In fact, direct USB file transfer is blocked so I need to use Sony's designated software. But an android system surely coexists according to the hacker who already rooted it.
Click to expand...
Click to collapse
Without some kind of way to flash or interface with the device there isn't much you can do.
I have a kindle fire HD that didn't come with a typical android system but does have a typical bootloader. The Amazon OS was removed and now it's full blown android but it required a "second" bootloader. You don't have a bootloader so I'm not sure what your options are with that device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You must be an iPhone user that isn't familiar with android. Jailbreak in is an Apple thing, not an android thing.
In android it's called "rooting" and it isn't quite the same thing as jailbreaking an Apple device.
This device does not at all seem to be worth the price, especially considering the limitations it has. What a waste of hardware.
I would assume that you could port something from one of those other devices to work on yours but it really depends on how your hardware is designed compared to those devices.
Does your device have a typical bootloader like other android devices?
Is the bootloader unlocked?
If it is locked, can it be unlocked?
Does the device use fastboot or does it have a flash mode that is used with a specific PC flashtool?
If it is unlocked or if you can unlock it and it has a flash mode that can actually be used, you might be able to port a custom recovery from one of the devices you named then use that recovery to somehow root the device. If the device can't install android apps then it would probably involve using adb to root the device.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Jailbreaking is the process of modifying any electronic device in order to remove restrictions imposed by a manufacturer (Apple) or operator (to allow the installation of unauthorized software).
Rooting is the act of gaining access to the root account of a device (such as a smartphone or computer).
There is a huge difference between the two. You can't just say that rooting is Android's version of jailbreaking. Not accurate in the least.
https://www.androidpit.com/jailbreak-android
Sent from my SM-G928T using Tapatalk
MarkBell said:
Jailbreaking is the process of modifying any electronic device in order to remove restrictions imposed by a manufacturer (Apple) or operator (to allow the installation of unauthorized software).
Rooting is the act of gaining access to the root account of a device (such as a smartphone or computer).
There is a huge difference between the two. You can't just say that rooting is Android's version of jailbreaking. Not accurate in the least.
https://www.androidpit.com/jailbreak-android
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
You're reading too much into what I said.
Basically, what I said was that jailbreaking isn't an android thing, it's an Apple thing(didn't say it was exclusively an Apple thing, just NOT an android thing). It applies to more than just Apple devices but on this website dedicated to mobile platforms, I'm only referring to its application in the mobile device world. For the mobile world it's pretty much only an Apple thing(still not exclusively but mostly so).
Then I said that in the android world it's called rooting(not exclusively an android thing, just NOT an Apple thing). And that jailbreaking and rooting aren't the same thing(this does not say that rooting is android's version of jailbreaking, that would imply that they are the same thing, I'm saying they aren't the same thing)
Basically, explaining what they "aren't", you explained what they "are".
I understand the difference, but thank you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
You're reading too much into what I said.
Basically, what I said was that jailbreaking isn't an android thing, it's an Apple thing(didn't say it was exclusively an Apple thing, just NOT an android thing). It applies to more than just Apple devices but on this website dedicated to mobile platforms, I'm only referring to its application in the mobile device world. For the mobile world it's pretty much only an Apple thing(still not exclusively but mostly so).
Then I said that in the android world it's called rooting(not exclusively an android thing, just NOT an Apple thing). And that jailbreaking and rooting aren't the same thing(this does not say that rooting is android's version of jailbreaking, that would imply that they are the same thing, I'm saying they aren't the same thing)
Basically, explaining what they "aren't", you explained what they "are".
I understand the difference, but thank you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I tend to read too deeply into everything. It's the way I am. Lol.
Sent from my SM-G928T using Tapatalk
Could you please post some information about usb device? Just like PID & VID.
Do it like:
Connect DPT-RP1 to Linux, and then type this command 'lsusb'
P.S. Under Windows or MacOS system, you can find the information from system settings...
happy to help with simple things
thisvip said:
Could you please post some information about usb device? Just like PID & VID.
Do it like:
Connect DPT-RP1 to Linux, and then type this command 'lsusb'
P.S. Under Windows or MacOS system, you can find the information from system settings...
Click to expand...
Click to collapse
Bus 001 Device 008: ID 054c:0be5 Sony Corp.
It is good to see some people have been interested in this thread.
So far, I realized that the hacker used a hardware hacking method. I actually obtained the hacked system apps from one of his customer. I guess he did sometihng like directly modifying eMMC to root and put "USBDeviceSwitcher.apk" to allow an usual USB connection. Since I don't want to take such risk, I decided to wait until the first firmware to see if there could be an indirect way to penetrate the system files. But if you want to analyze the hacked system, contact me.
sartrism said:
It is good to see some people have been interested in this thread.
So far, I realized that the hacker used a hardware hacking method. I actually obtained the hacked system apps from one of his customer. I guess he did sometihng like directly modifying eMMC to root and put "USBDeviceSwitcher.apk" to allow an usual USB connection. Since I don't want to take such risk, I decided to wait until the first firmware to see if there could be an indirect way to penetrate the system files. But if you want to analyze the hacked system, contact me.
Click to expand...
Click to collapse
Does it have a web browser? Maybe you can utilize for example the Stagefright Exploit + DirtyC0W to get root.
I have found out some interesting stuff about the device with the help of the Digital Paper App.
The app is built using electron and there is a file: /Applications/Digital\ Paper\ App.app/Contents/Resources/app.asar
This file contains the electron javascript files, which handle all the communication with the device.
It can be extracted with: sudo asar extract app.asar output
(github_com/electron/asar)
This also requires node to be installed: with e.g. brew install node (changelog_com/posts/install-node-js-with-homebrew-on-os-x)
The app communicates with the device via Restlet-Framework/2.3.7 on port 8443 with tcp (no matter if it is the bluetooth, wifi or usb connection).
This is the only port that is open.
In the file: /Applications/Digital\ Paper\ App.app/Contents/Resources/output/node_modules/mw-error/lib/codeparams.js you can find all the relative paths, which are getting called during e.g. file transfer, firmware update and stuff.
Running the app and placing breakpoints reveals that before you can transfer files and stuff:
'/auth'
'/auth/nonce/'
are called in order to authenticate, which looks e.g. like url digitalpaper.local:8443/auth/nonce/1e9ee24d-6613-433a-9770-76b04333ac95
the last part of the call is the "client_id": "1e9ee24d-6613-433a-9770-76b04333ac95", which is retrieved via the url digitalpaper.local:8443/auth call.
digitalpaper.local:8443/auth/
Important:
In /Applications/Digital\ Paper\ App.app/Contents/Resources/output/lib/config.js
change the line
config.DEVBUILD = false;
to
config.DEVBUILD = true;
After you finished your modifications you have pack the output folder again:
sudo asar pack output app.asar
I did not have time to continue, but the following relative urls look promising (especially recovery_mode):
'/testmode/auth/nonce',
'/testmode/auth',
'/testmode/launch',
'/testmode/recovery_mode',
'/testmode/assets/{}',
mcplectrum said:
I have found out some interesting stuff about the device with the help of the Digital Paper App.
The app is built using electron and there is a file: /Applications/Digital\ Paper\ App.app/Contents/Resources/app.asar
This file contains the electron javascript files, which handle all the communication with the device.
It can be extracted with: sudo asar extract app.asar output
(github_com/electron/asar)
This also requires node to be installed: with e.g. brew install node (changelog_com/posts/install-node-js-with-homebrew-on-os-x)
The app communicates with the device via Restlet-Framework/2.3.7 on port 8443 with tcp (no matter if it is the bluetooth, wifi or usb connection).
This is the only port that is open.
In the file: /Applications/Digital\ Paper\ App.app/Contents/Resources/output/node_modules/mw-error/lib/codeparams.js you can find all the relative paths, which are getting called during e.g. file transfer, firmware update and stuff.
Running the app and placing breakpoints reveals that before you can transfer files and stuff:
'/auth'
'/auth/nonce/'
are called in order to authenticate, which looks e.g. like url digitalpaper.local:8443/auth/nonce/1e9ee24d-6613-433a-9770-76b04333ac95
the last part of the call is the "client_id": "1e9ee24d-6613-433a-9770-76b04333ac95", which is retrieved via the url digitalpaper.local:8443/auth call.
digitalpaper.local:8443/auth/
Important:
In /Applications/Digital\ Paper\ App.app/Contents/Resources/output/lib/config.js
change the line
config.DEVBUILD = false;
to
config.DEVBUILD = true;
After you finished your modifications you have pack the output folder again:
sudo asar pack output app.asar
I did not have time to continue, but the following relative urls look promising (especially recovery_mode):
'/testmode/auth/nonce',
'/testmode/auth',
'/testmode/launch',
'/testmode/recovery_mode',
'/testmode/assets/{}',
Click to expand...
Click to collapse
Hope you get some result from wifi side. I also realized they use the port 8443 but couldn't get further as you.
For whom trying to hack it, here is the link for the already 'hacked' system apps (including the original files) - that of the famous hacked RP1 video. Inside the subfolder S1, there are also the hacked system apps for DPT-S1 just in case.
https://www.dropbox.com/sh/dvtvokdzrgwjc83/AACXOJA-E56nUpUfiWUOzrM3a?dl=0
George Malas said:
Does it have a web browser? Maybe you can utilize for example the Stagefright Exploit + DirtyC0W to get root.
Click to expand...
Click to collapse
The stock device has no web browser, no sd-card, no usb connection, and no typical system. I think SONY was haunted by some security issues maybe because they thought the major users are lawyers or very important people? lol
Any chance to create a buffer overflow PDF to attack RP1's pdf reader?
I am unable to help, but wanted to let you know I am definitely interested in and supportive of this. If this device can be unlocked as suggested in that one youtube video then I would buy it, despite the steep price.
jess91 said:
I am unable to help, but wanted to let you know I am definitely interested in and supportive of this. If this device can be unlocked as suggested in that one youtube video then I would buy it, despite the steep price.
Click to expand...
Click to collapse
If you're interested and supportive of this then go buy one anyway and apply yourself to going forward figuring out how to get it done. Other than that, you're not supportive, you're just hopeful that someone figures it out and then you'll probably go get one.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Hey guys,
I also recently got the RP1 and am also looking for ways to mod it. Big kudos and thanks to all of you for posting this! This alread is amazing. @sartrism: can you maybe give me a hint how to load the files on the rp1? Sorry if this might be a stupid question but I'm new to adroid and that stuff.
Paderico said:
Hey guys,
I also recently got the RP1 and am also looking for ways to mod it. Big kudos and thanks to all of you for posting this! This alread is amazing. @sartrism: can you maybe give me a hint how to load the files on the rp1? Sorry if this might be a stupid question but I'm new to adroid and that stuff.
Click to expand...
Click to collapse
Just a little update from my side. I'm currently tryng to recreate the steps @mcplectrum was using. It seems that my RP1 also uses other ports. I tried to wireshark the USB and WiFi connection. By that I saw that often GET /registration/information is called for Host: localhost:58052. Moreover the first call is GET /register/serial_number also on port 5808. This was via USB.
Trying to trigger the /auth/ call via Telnet returns nothing unfortunately. But also the 8080 port is open. Trying to call digitalpaper.local:8443/auth/ returns nothing on firefox.
@mcplectrum: how did you get the client_id and what would one need that for?
I also tried to change the config.DEVBUILD to true but that seemed to change nothing at all.
So to sum up what we know:
The device is using some kind of android structure, the source code seems to use the uboot bootloader, all communication is done by a rest restlet framework. So actually there should be some kind of way to use the restlet framework to PUT or POST the modified files.
The other option would be directly flash the eMMC right? I would take the risk and just load it on my device and see what happens. Any hints on how to do that?

Security-related arguments for root and custom rom usage...

Exodus, a popular, albeit closed-source, crypto wallet app recently stopped working on my device. After a few days of back-and-forth troubleshooting via support, they somehow realized that my device is both rooted and running a custom, open source, community-supported ROM. They told me this was no longer allowed because it is far less secure than running the proprietary ROM. I countered with both personal testimony (back when I had a Blu phone, and a year later they got kicked off Amazon due to spyware streaming customer data out without consent) and common fact that OEM ROMs are almost always packed full of bloatware and spyware. I countered that installing a reputable open source ROM with only those apps I want and need is better. I argued that root gives me the ability to use AFWall to block outbound access to apps that I don't want having having access to the Internet without my permission. I could have argue that continuing to use a 1-2 year old phone that no longer receives security updates when I could use an open source ROM that does is better. I also provided a few public articles showing how frequently apps from the Play Store and other "OEM" stores are caught abusing their users' trust and performing malicious action. My point was that it's not correct to just automatically assume that having root and using a non-OEM ROM is less secure. That's a falsehood. But that said, I am interested to know what the XDA community thinks about that. And if the XDA community has any facts about custom, open source, community-supported ROMs being more secure than OEM ROMs, I am interested to further arm myself. And of course, I am completely willing to be instructed by the XDA community that indeed Exodus is right and using a custom ROM and having a rooted phone is completely, inherently, automatically more insecure than using an OEM ROM full of bloatware and spyware, not having root so that any rag-tag app can stream data back to home base, and falling behind with security patches because the vendor is either too slow to release or decides my device is no longer worth supporting.
You can't blame them for not troubleshooting unknown firmware. You changed the playing field.
Less mainstream use and support* is one of the disadvantages of custom roms and rooting.
I run stock and use other methods to kill bloatware. Zero brick risk, little down time and they run well.
I'm not saying don't root etc... but you knew the job was dangerous when you took it.
*this can have potentially far reaching and multifaceted implication$
@blackhawk I'm pretty sure it wasn't broken on my phone. One day I opened the app and it said I needed to update to continue using it. So I thought maybe the app just had failed to automatically update from the Play Store. But shortly thereafter I found it wouldn't update. That led to opening support ticket with them which eventually led to them saying it no longer works on rooted devices. Their argument was that they were attempting to protect me. My rebuttal was that I don't want their protection, I want my freedom back. They should focus on making their app as secure as possible and then, if they discover I am running it on a rooted phone, then give me a warning box and force me to accept it but don't just take away my freedom.
The irony of their stance is that they still provide the Linux program. And who doesn't have root access on their Linux computer? Or their Mac or Windows computer, for that matter? I can completely understand if they don't wish to troubleshoot the installation of the Debian package or even the use of the zip on every Linux version out there. I wouldn't either! But that's completely different than saying, "Oh, you have root access to your Linux/Mac/Windows computer? We can't let you use our program anymore." That makes zero sense, and it's the same nonsensical argument they are making for rooted Android phones.
I run stock N10+'s because they're easier to troubleshoot, maintain and it doesn't trip the Knox efuse. I have to add a package disabler and do some optimizing but it's child's play for me to do it at this point.
Unfortunately if you root you're going to have to suck it up and do the work needed to optimize it.
Same thing I do with stock but with more tools at your disposal... after the learning curve.
It's this learning curve, the chance of bricking and the damage that can be inadvertently done to the OS with no access restrictions are some of the downsides. Rooting takes time to learn and perfect. With unlimited power, blah, blah, blah.
I rather just do basic infrequent troubleshooting and have fun... my current load is over 1.5 yo, still fast and stable.
I don't update the firmware because that breaks things. No updates needed once you optimize it and find any needed work arounds... it's good to go. Anything from Pie up is pretty secure; they have some vulnerabilities but in practice this isn't an issue... unless you do something stupid.

What's really at stake if rooting an older phone?

My phone is 5 years old, and hasn't had any OTA updates in years and its got no warranty. Apparently my older version of Android 8, isn't recognized as much and I'm starting to encounter more and more Play store apps that want a newer version of android and refuse to load. Hence I had to learn how to sideload stuff which is really annoying.
After a quick google search I learned you can root your phone and there is an Android 11 image called Lineage OS 18.1 ... which sounds pretty sweet. BUT after additional searches, I'm reading so many cons about rooting a phone. If bricking it isn't a concern, and I don't have a warrantee to void. What's at risk? I was probably going to buy a new phone anyways but now I'm intregued with this rooting process and wondiering if it might buy me time on a older phone that still works amazingly well. Why replace it if it still works, it just needs new software.
Questions: If I install Lineage OS 18.1 successfully...
Will the Play Store and Apps continue to update, or will I stop receiving notifications regarding available updates? Or am I forever stuck with sideloading?
If I don't install G Apps is this bad? I don't use stock Google Apps, I've opted to use the Microsoft equivalent like Outlook for email and calendar... or do I still need to install Google Apps to gain the ability to layer Microsoft products on top?
Why is there so much negative talk about malware infection with rooted phones? If I'm not downloading and installing apps constantly, the risk would still be no more threatening than it is now correct?
Are there any apps that would realize the phone is rooted and refuse to run? Some searches told me that security apps may not like a rooted phone. Does rooting it affect Microsoft Authenticator app?
Lastly, if I only want to pick and choose specific G Apps - can you install only the ones you need? or do they come all bundled together?
Thanks in advance,
What's really at stake if rooting an older phone?​
Click to expand...
Click to collapse
Ii is easy to answer:
Pro: Complete Control Over Your Device​
One of the most significant benefits of rooting your Android device is the ability to have complete control over it. You can remove any pre-installed apps that you don’t need, customize the look and feel of your device, and control every aspect of its performance. With rooting, the possibilities are endless, and you can make your device truly your own.
Con: Risk of Bricking Your Device​One of the most significant risks of rooting your Android device is the potential to brick it. Bricking is when your device becomes completely unusable due to a software malfunction. If you’re not careful, you can render your device useless. However, if you follow the instructions carefully and take the proper precautions, you can minimize the risk of bricking your device.
Speed up older Android hardware with a custom ROM​
Click to expand...
Click to collapse
Installing a custom ROM ( or a 3rd-party OS ) allows your device to live a second life, provided you can stomach the somewhat lengthy process. Custom ROMs become especially useful once your smartphone’s manufacturer stops delivering software and feature updates. Most ROMs are also based on vanilla Android ( AOSP ), which means you get a lighter and faster experience than default manufacturer skins.
Having said that, it’s worth noting that custom ROMs are completely unofficial. Some work perfectly, while others may exhibit bugs and instability - you’ll need to do some due diligence for your specific device model. But don’t worry, here is a guide on how to install Lineage OS, one of the most popular custom ROMs.

Categories

Resources