Develop Bugs

Removing preinstalled apps on Xperia play

Hi,
I am been researching for few weeks now. Being just an android user and a beginner level android developer, I am kind of lost in trying to solve my issue. I bought a Xperia Play. It is carrier unlocked. The main issue is the internal memory which keeps getting filled up from time to time, that makes me sacrifice some less used but important apps. I would like to make use of my phone more efficiently and utilise it to its maximum potential. Request someone to help me achieve this by helping me remove these apps.
Thanks

you have to root your phone first and u will find a tutorial im the development section... And after that you can use titanium backup to remove those apps

Hi,
Thanks for the info. But I am kind of lost when I went through the forum. Can you please guide me a specific one? Thanks.
Sent from my R800i using xda app-developers app

You could unlock your bootloader. You can do this here: http://unlockbootloader.sonymobile.com/
This enables you to flash custom Kernels and Roms. Although you don't need this if you only want to root your phone, but in my experience custom roms and kernels are a great advantage if you want to get more out of your phone
The rooting thread would be this one: http://forum.xda-developers.com/showthread.php?t=1325334

Bombasti said:
You could unlock your bootloader. You can do this here: http://unlockbootloader.sonymobile.com/
This enables you to flash custom Kernels and Roms. Although you don't need this if you only want to root your phone, but in my experience custom roms and kernels are a great advantage if you want to get more out of your phone
The rooting thread would be this one: http://forum.xda-developers.com/showthread.php?t=1325334
Click to expand...
Click to collapse
Thanks Bombasti, but the unlock boot loader from sony mobile does not work for phones with IMEI numbers greater than 14 digits. Further, I also tried SuperOneClick but I keep getting the errors in Step 1 stating that the "rm failed for /data/local/tmp/boomsh. No such file directory", Step 2 also returns similar result. Can you help. Thanks.

xdadevprince said:
Hi,
Thanks for the info. But I am kind of lost when I went through the forum. Can you please guide me a specific one? Thanks.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Go to the general section then look for my "Mega thread all my tutorials in one thread"
Sent from my R800i using Tapatalk 2
---------- Post added at 12:25 AM ---------- Previous post was at 12:24 AM ----------
xdadevprince said:
Thanks Bombasti, but the unlock boot loader from sony mobile does not work for phones with IMEI numbers greater than 14 digits. Further, I also tried SuperOneClick but I keep getting the errors in Step 1 stating that the "rm failed for /data/local/tmp/boomsh. No such file directory", Step 2 also returns similar result. Can you help. Thanks.
Click to expand...
Click to collapse
Enter the first 14digits
Sent from my R800i using Tapatalk 2

xdadevprince said:
Thanks Bombasti, but the unlock boot loader from sony mobile does not work for phones with IMEI numbers greater than 14 digits. Further, I also tried SuperOneClick but I keep getting the errors in Step 1 stating that the "rm failed for /data/local/tmp/boomsh. No such file directory", Step 2 also returns similar result. Can you help. Thanks.
Click to expand...
Click to collapse
This is not correct. You just have to enter the 14 first digits. So it should work for your phone unless there are other restrictions (e.g. from your phone provider).
Did you try it with the first 14 digits?
Also did you run SuperOneClick as administrator? I have no idea how SupoerOneClick works, but the error says that it can't remove a directory that doesn't exist. Maybe you can create the dir on your phone to fool the program?
Greetings,
Bombasti
-----------------------EDIT:---------------------
I checked the SuperOneClick thread here: http://forum.xda-developers.com/showthread.php?t=803682/
The R800i isn't listed as compatible device, what doesn't mean it's not compatible since the list is incomplete. But I remember that it didn't work for my phone either ( I tried it some time ago). I solved the problem through flashing an already rooted rom. Later i user Cyanogenmod which rooted from the beginning. But this needs an unlocked bootloader first...

Bombasti said:
This is not correct. You just have to enter the 14 first digits. So it should work for your phone unless there are other restrictions (e.g. from your phone provider).
Did you try it with the first 14 digits?
Also did you run SuperOneClick as administrator? I have no idea how SupoerOneClick works, but the error says that it can't remove a directory that doesn't exist. Maybe you can create the dir on your phone to fool the program?
Greetings,
Bombasti
-----------------------EDIT:---------------------
I checked the SuperOneClick thread here: http://forum.xda-developers.com/showthread.php?t=803682/
The R800i isn't listed as compatible device, what doesn't mean it's not compatible since the list is incomplete. But I remember that it didn't work for my phone either ( I tried it some time ago). I solved the problem through flashing an already rooted rom. Later i user Cyanogenmod which rooted from the beginning. But this needs an unlocked bootloader first...
Click to expand...
Click to collapse
superoneclick works fine just make sure you have all the drivers installed

fma965 said:
superoneclick works fine just make sure you have all the drivers installed
Click to expand...
Click to collapse
Ah that might have been my problem then.

Bombasti said:
Ah that might have been my problem then.
Click to expand...
Click to collapse
by all I meant the adb,fastboot and flashmode
Sent from my R800i using Tapatalk 2

bypass battery limit without root

Hi guys,could someone explain to me clearly how to get my battery level back to 100% on my galaxy note 7?
I would like to do everything without giving root permits. I have searched on the forum but sadly i couldn't find a step by step guide to help me.
Model: SM-N930F
Android version: 6.0.1
Kernel version: 3.18.14-9450328
Build version: MMB29K.N930FXXU2BPJ9
Baseband version: N930FXXU2BPJ5
Serial number: RFH8H91FDMKW

I think you have to root once the update is on your device as the only way to remove it once it is on the device is to change the firmware.

fake991 said:
Hi guys,could someone explain to me clearly how to get my battery level back to 100% on my galaxy note 7?
I would like to do everything without giving root permits. I have searched on the forum but sadly i couldn't find a step by step guide to help me.
Model: SM-N930F
Android version: 6.0.1
Kernel version: 3.18.14-9450328
Build version: MMB29K.N930FXXU2BPJ9
Baseband version: N930FXXU2BPJ5
Serial number: RFH8H91FDMKW
Click to expand...
Click to collapse
----------------
Check this one on youtube, it call "How to fix your Note 7 after 60% battery update"
I just try it on today and it work for me.

Belimawr said:
I think you have to root once the update is on your device as the only way to remove it once it is on the device is to change the firmware.
Click to expand...
Click to collapse
no that's not true, you do not require root to flash firmware via odin..in fact if your already rooted doing so will unroot your device. but yes you need flash the previous firmware in odin to remove the charging killing update
the important part is keeping the OTA from happening again. most of the package diasablers i know of have been updated and dont work now.
there is an ADB method but the easiest way to prevent it is rooting but the OP doesnt want to root so he is going to ha e to research the other methods i mentioned to find something that works.
short if that get used re flashing the previous firnware over and ovet to get back full charging capability.
Sent from my SM-N930W8 using Tapatalk 2

force70 said:
no that's not true, you do not require root to flash firmware via odin..in fact if your already rooted doing so will unroot your device. but yes you need flash the previous firmware in odin to remove the charging killing update
the important part is keeping the OTA from happening again. most of the package diasablers i know of have been updated and dont work now.
there is an ADB method but the easiest way to prevent it is rooting but the OP doesnt want to root so he is going to ha e to research the other methods i mentioned to find something that works.
short if that get used re flashing the previous firnware over and ovet to get back full charging capability.
Sent from my SM-N930W8 using Tapatalk 2
Click to expand...
Click to collapse
Hi, thanks for reply,
when i flash with odin, the internal storage will be formatted?
ps. sorry for my bad english.

fake991 said:
Hi, thanks for reply,
when i flash with odin, the internal storage will be formatted?
ps. sorry for my bad english.
Click to expand...
Click to collapse
no you wont lose anything at all unless you factory reset...that will wipe your device.
that said sometimes a factory reset is needed after flashing in odin so i would move anything you want to keep to your ext SD card just in case then move it back after.
your English is fine my friend no worries!
Sent from my SM-N930W8 using Tapatalk 2

force70 said:
no you wont lose anything at all unless you factory reset...that will wipe your device.
that said sometimes a factory reset is needed after flashing in odin so i would move anything you want to keep to your ext SD card just in case then move it back after.
your English is fine my friend no worries!
Sent from my SM-N930W8 using Tapatalk 2
Click to expand...
Click to collapse
Thanks to your help, I think I can flash the old rom. Regarding the updates, I would like to use this app: "package disabler pro 6.2"
What do you think about that?

https://youtu.be/i04r3S6YIY0
Hope this helps to avoid 60% battery update.

Hi, I'm having a problem downgrading back to before the update. I have the FD version.
If I try to flash the bootloader in Odin, it tells me unsupport dev type and crashes. If i try to flash the twrp, it tells me custom OS installation is locked. What do I need to do? I am noob, never done this before. Please let me know what I need to do to fix this?

Free help
I found a group call Note 7 Alliance it is free help and everything you need to get you Note 7 back to 100% the forum is note7alliance com

fake991 said:
Thanks to your help, I think I can flash the old rom. Regarding the updates, I would like to use this app: "package disabler pro 6.2"
What do you think about that?
Click to expand...
Click to collapse
unless you paid for a license before the apk hit V7.0 then you cannot use the older versions sorry

force70 said:
there is an ADB method
Click to expand...
Click to collapse
Can you please PM me the link (if it's outside of this community) as I've never been told of that method?

Cr4z33 said:
Can you please PM me the link (if it's outside of this community) as I've never been told of that method?
Click to expand...
Click to collapse
no its posted here on xda in the note 7 forums..i dont have a link though sorry .

Cr4z33 said:
Can you please PM me the link (if it's outside of this community) as I've never been told of that method?
Click to expand...
Click to collapse
Just start reading here from post #204:
http://forum.xda-developers.com/note-7/help/dont-update-package-disabler-pro-want-t3489243/page21
However, maybe it's not working for you, if you were already hit by an android security patch in the firmware you actually have. It differs depending from your country or provider specific version. But if you don't get the java.lang.SecurityException, all will be fine. Just try.

Help with developer preview new to this

So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk

Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk

applezen said:
Did you set the fastboot path in your environmental variables correctly?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
IDK much about computers much but I learn quick and understand well what I did was set the power-tools as path I didn't do fastboot but fastboot is in the power-tools folder so is this correct?
Sent from my Pixel 2 XL using Tapatalk

Install latest SDK and start the CMD from there

Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.

Ace0spades808 said:
Just a question but...why are you flashing the developer preview if you are new to this and don't know much about computers? It is a developer preview for a reason and it is not intended to be used on a daily basis yet.
Since you aren't fully aware of what you are doing you could very well mess up your device.
Click to expand...
Click to collapse
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk

non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Click to expand...
Click to collapse
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh ???

Sounds like the same issue as here: https://forum.xda-developers.com/pixel-xl/how-to/guide-update-fastboot-t3498187/page6 - that's post number 51.
The user resolved it by updating ADB/Fastboot.

Badger50 said:
I like the attitude my friend! "Damn the torpedoes!..full steam ahead" If ya brick it, ya brick it! Then try it again! I've bricked 2 devices over the years. Best learning experience I could've had! Unless you do something very crazy with it, your not going to brick it! Keep up the good fight bruh [emoji108][emoji106][emoji41]
Click to expand...
Click to collapse
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Sent from my Pixel 2 XL using Tapatalk

non_smoker0922 said:
Exactly people always with the "it says developer preview why are you trying?!" That's a terrible way to look at things instead of helping others learn we learn by taking chances and making mistakes simple
Click to expand...
Click to collapse
Hell yeah!!! ???

non_smoker0922 said:
Def rooted phones before, unrooted so I'm not stupid,just know very little about far as playing with cmd and I def know it's a preview so there's going to be more bugs than a beta update it's ok not worried about a thing it can be my daily as long as text,phone and web works I'll be ok trust me...if you live with fear ur whole life u won't accomplish anything[emoji817]??*??*
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Didn't mean to offend you or anything. I just wanted you to be aware that the developer preview isn't meant to be flashed because it is the "latest and greatest". If you want to try it out go for it but you could end up causing yourself more headache than it's worth (you could brick it or render your phone inoperable for days) since you yourself said you aren't sure what you are doing.

non_smoker0922 said:
So I tried to install developer preview on pixel 2 xl from Google. Im running Windows 10. I unlocked bootloader using command >fastboot flashing unlock also tried unlock_critical after and it keeps failing. I've read something about it can be usb port or data cable I've changed cables all candles acted different but all failed. I've used best cable that sends commands but this is some of things I'm getting target didn't report max doesn't size and error: failed to identify current slot I would post pics but it won't let me says I don't have permission to do so
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.

uicnren said:
Sideload the OTA. https://developer.android.com/preview/download-ota.html
Just be aware however, if something goes wrong, and your bootloader is not unlocked, you potentially will have a brick on your hands.
Click to expand...
Click to collapse
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk

non_smoker0922 said:
Ok how about if something goes wrong with the bootloader unlocked
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.

uicnren said:
With an unlocked bootloader, theoretically you should be able to flash the factory images.
Factory images cannot be applied with a locked bootloader, so the unlocked bootloader is the fallback in case of disaster.
At the very bare minimum, ensure that you have OEM unlocking enabled in developer options. Though I would recommend the bootloader be unlocked before flashing the OTA.
Click to expand...
Click to collapse
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Sent from my Pixel 2 XL using Tapatalk

non_smoker0922 said:
Ok because I tried to flash image but I couldn't I think it might be my cable or something IDK I'm able to unlock bootloader just can't flash images
Click to expand...
Click to collapse
Did you run both bootloader unlocking commands?

Badger50 said:
Did you run both bootloader unlocking commands?
Click to expand...
Click to collapse
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk

So the issue is that you can't get the phone unlocked? Do you still have the option to enable ""OEM Unlocking" in Developer Settings? If it is greyed out, you'll have to reset the phone. First backup and then perform "erase all data(factory reset) and then skip through all of the setup on the phone. Once you are in the phone, gain developer settings, enable "OEM Unlocking" and USB Debugging. You should then be able to unlock via fastboot.

non_smoker0922 said:
Yeah and when I put in unlock_critical it says bootloader already unlock
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Best I can suggest for you now, is to see HERE.
You can ignore the stuff about C:/D: drives.

Twice now you have used the term unlock_critical. Did you actually type in "fastboot flashing unlock_critical"?

No "OEM UNLOCKING" option :(

I purchased my Samsung A8+ Saudi Arabia version running Nougat 7.1.1 and I also updated it to some new patch worth of 300MB April Update. I wanna root my phone but I cant see the OEM UNLOCKING option in my phone. Am I missing something there or doing something wrong ????

noob_coder said:
I purchased my Samsung A8+ Saudi Arabia version running Nougat 7.1.1 and I also updated it to some new patch worth of 300MB April Update. I wanna root my phone but I cant see the OEM UNLOCKING option in my phone. Am I missing something there or doing something wrong ????
Click to expand...
Click to collapse
Read the threads all info is their.
You will have to wait 7 days without a reboot.
After you see oem option you need read the threads on rooting your device.
Sent from my SM-A730F using xda premium

mchlbenner said:
Read the threads all info is their.
You will have to wait 7 days without a reboot.
After you see oem option you need read the threads on rooting your device.
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
Finally someone replied atleast. Thanks a lot man appreciate that you replied. Sign of relief. Yeah I was looking at the some of the forums yesterday and I saw that some were saying you have to wait somedays like week or more to get this option enabled or show up but I wasnt sure that was that all true about having to wait for OEM UNLOCKING to popup?
Anyways I updated my rom 2 days ago and I have been restarting my phone since that day . So you mean to say whenever I will restart the timer for OEM UNLOCKING to expire will go back to 0 ZERO ????

noob_coder said:
Finally someone replied atleast. Thanks a lot man appreciate that you replied. Sign of relief. Yeah I was looking at the some of the forums yesterday and I saw that some were saying you have to wait somedays like week or more to get this option enabled or show up but I wasnt sure that was that all true about having to wait for OEM UNLOCKING to popup?
Anyways I updated my rom 2 days ago and I have been restarting my phone since that day . So you mean to say whenever I will restart the timer for OEM UNLOCKING to expire will go back to 0 ZERO ????
Click to expand...
Click to collapse
Yes
Sent from my SM-A730F using xda premium

mchlbenner said:
Yes
Click to expand...
Click to collapse
I kept my phone running for consecutive 7 days equaling to 168+ hours but the OEM UNLOCK ? option never appeared. So now what is the problem and what's the solution?

noob_coder said:
I kept my phone running for consecutive 7 days equaling to 168+ hours but the OEM UNLOCK ? option never appeared. So now what is the problem and what's the solution?
Click to expand...
Click to collapse
Never had this with oem.
Factory reset and try a different rom.
Sent from my SM-A730F using xda premium

dont work en a8 730f
mchlbenner said:
Yes
Sent from my SM-A730F using xda premium
Click to expand...
Click to collapse
if you have the 730f I recommend you that there is no twrp nor root
if the device comes with blocked OEM,
There's a lot of XDA posts here, but they suck.
the cel always stays brick

sebas0802gt said:
if you have the 730f I recommend you that there is no twrp nor root
if the device comes with blocked OEM,
There's a lot of XDA posts here, but they suck.
the cel always stays brick
Click to expand...
Click to collapse
I have a 730f and I have been rooted since day one.
All factory unlocked 730f can be rooted unless you bought it from your carrier.

Here is what I did to OEM unlock
I flashed Russian OREO firmware and updated to PIE using the built in system updater. (I did it 2 times, I don't know if that has something to do with it)
After that, I flashed TWRP and a custom rom.
Hope this helps. I never get through with the 7-day method.

Root without PC

Is there a way to root without PC. I googled it but what I found was almost a year old so I wasn't sure if anything has changed.

UnicornHub said:
Is there a way to root without PC. I googled it but what I found was almost a year old so I wasn't sure if anything has changed.
Click to expand...
Click to collapse
Nope. You need a pc to unlock the bootloader so you can then root your device. Sorry man.

Badger50 said:
Nope. You need a pc to unlock the bootloader so you can then root your device. Sorry man.
Click to expand...
Click to collapse
Dang ok. I saw the all in one toolbox's are those stable and do they work well? If not what's the best easiest root method

UnicornHub said:
Dang ok. I saw the all in one toolbox's are those stable and do they work well? If not what's the best easiest root method
Click to expand...
Click to collapse
I've never used a toolkit. I prefer the manual method with my pc and fastboot commands. Here's a great guide to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Yes knowing how to do it manually is the best way typically I've tried a few all in ones and some reason usually have issues also some make it too easy to mess it up if I don't know what you are doing and hey inpatient
Sent from my Pixel 2 XL using Tapatalk

gjkrisa said:
Yes knowing how to do it manually is the best way typically I've tried a few all in ones and some reason usually have issues also some make it too easy to mess it up if I don't know what you are doing and hey inpatient
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that even with one click root methods, you'll still need an unlocked bootloader.

Yeah true
xunholyx said:
I'm pretty sure that even with one click root methods, you'll still need an unlocked bootloader.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk

Don't rely on the "AIO" Toolkits or the "One Click Root" Toolkits. I do appreciate the developers' effort they put in these toolkits to make people's life easier however many times they are outdated and don't work as they should and are just causing headache. Use Fastboot and ADB and nothing can go wrong! If something does, well... There are so many extremely nice people here who are willing to help you out, answer your questions and bring your phone back to life! Khm... @Badger50 just to mention one! Khm...

True, with oneclick root you must still have an unlocked bootloader otherwise i won't work.