Database Users

[Q] Rooting official 2.3.5 wirelessly

Hello!
How can one root official 2.3.5 rom without connecting to usb and adb?
The goal is to install custom ICS on U8800 that has no usb port - completely broken and even not charging phone. No warranty and repair cost is close to actual phone cost. So repairing is not an option.
Wireless adb app requires root first - so it is not an option for me also.
Any help is appreciated - I need ISC because I need ipsec vpn which is npt available in gingerbread.
I am ready to test any operation you suggest - I don't fear to brick the phone, need no backups.

It's impossible. I have one USB broken u8800 and that's why I use cm7 (.32) on it.
Sent from my U8800 using Tapatalk 2

Qqqxxxzzz said:
It's impossible. I have one USB broken u8800 and that's why I use cm7 (.32) on it.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
There is nothing impossible I believe
Maybe we could find the trick - gingerbreak works on some roms - another fine exploit maybe.
I don't know - worth a try I think.

tranced1 I might have 1 possible solution for you. I've rooted my 2.3.5 some time ago and I've done a backup of boot.img.
I remember with froyo we could root it with boot.img "rooted". I bet this won't work on 2.3.5, but who knows right?
If you want to give it a try, I upload that boot.img for you.
EDIT: darn! Totally forgot you can't access bootloader directory without root & damaged usb port
Can't remember another way out... sorry

tranced1 said:
There is nothing impossible I believe
Maybe we could find the trick - gingerbreak works on some roms - another fine exploit maybe.
I don't know - worth a try I think.
Click to expand...
Click to collapse
Gingerbreak and z4root doesn't work. Only solution is build your own exploit.
Sent from my U8800 using Tapatalk 2

Is there any way to flash zip from stock recovery? I saw this root method for some samsung phones.
Does anybody know how to compile such .zip file?

tranced1 said:
Is there any way to flash zip from stock recovery? I saw this root method for some samsung phones.
Does anybody know how to compile such .zip file?
Click to expand...
Click to collapse
compiling zip is easy. Your problem is that we don't know how to sign it correctly.
Sent from my GT-P1000 using Tapatalk 2

I believe that you can use terminal emulator and zergrush exploit to root the phone.
The automatic root methods basicaly push the needed files on /data/local change permissions etc... All can be done with linux commands which are available from a terminal emulator. So I don't think that you need the usb cable to root the device. You can try investigate the runme.bat file from doomlord's root method and give the commands manually after you have put the files from files directory on sdcard.

dancer_69 said:
I believe that you can use terminal emulator and zergrush exploit to root the phone.
The automatic root methods basicaly push the needed files on /data/local change permissions etc... All can be done with linux commands which are available from a terminal emulator. So I don't think that you need the usb cable to root the device. You can try investigate the runme.bat file from doomlord's root method and give the commands manually after you have put the files from files directory on sdcard.
Click to expand...
Click to collapse
adb can access the phone as root user - from terminal file system is read-only, so even first step permission denied

Yes, you have right about that.
But, check this thread:
http://forum.xda-developers.com/showthread.php?t=1716068
the last post.
EDIT:
After reading the discription on first post of gingerbreak, I had another Idea.
Seems that gingerbreak uses sd card to temporary store the necessary for root files. So, maybe you can replace these files(and especially the exploit) whith those of doomlord's root app, before you press the root button, so to use the working zergrush exploit.

This is the B528 root bat script:
http://pastebin.ca/raw/2163499
@adb wait-for-device
@echo --- DEVICE FOUND
@echo --- reboot to bootloader
@adb reboot-bootloader
@echo --- flash the rooted bootimage
@fastboot boot boot.img
@echo --- reboot to nomal mode
@fastboot reboot
@echo --- wait for adb connect
@adb wait-for-device
@echo --- DEVICE FOUND
@adb remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
You're problem is in red... you have to flash the exploited boot image. The rest is just installing busybox, su and SuperUser.apk.
You have the stock recovery which allows you to flash .zip files, but they have to be signed correctly and I don't think that's possible.

VuDuCuRSe said:
This is the B528 root bat script:
http://pastebin.ca/raw/2163499
You're problem is in red... you have to flash the exploited boot image. The rest is just installing busybox, su and SuperUser.apk.
You have the stock recovery which allows you to flash .zip files, but they have to be signed correctly and I don't think that's possible.
Click to expand...
Click to collapse
To boot a different boot image, you have to use USB, atleast on fastboot.

dancer_69 said:
Yes, you have right about that.
But, check this thread:
http://forum.xda-developers.com/showthread.php?t=1716068
the last post.
EDIT:
After reading the discription on first post of gingerbreak, I had another Idea.
Seems that gingerbreak uses sd card to temporary store the necessary for root files. So, maybe you can replace these files(and especially the exploit) whith those of doomlord's root app, before you press the root button, so to use the working zergrush exploit.
Click to expand...
Click to collapse
Thanks for clues but seems there is no way - I cant execute exploit via ssh - permission denied I cant even chmod it.
Gingerbreak completely not working - no files created on sdcard.

Ι didn't find any other way on net. There are several discussions for this problem but not a solution. I think that the only way is to do it for an app. You can contact with the creator of gingerbreak or z4root to ask for it. Also I'll try to make an app myself, but my android developing knowledge is very basic, so don't count too much on this. If I have some kind of success I'll contact you via PM.
EDIT:
Try this mod, and if you are lucky...

dancer_69 said:
Ι didn't find any other way on net. There are several discussions for this problem but not a solution. I think that the only way is to do it for an app. You can contact with the creator of gingerbreak or z4root to ask for it. Also I'll try to make an app myself, but my android developing knowledge is very basic, so don't count too much on this. If I have some kind of success I'll contact you via PM.
EDIT:
Try this mod, and if you are lucky...
Click to expand...
Click to collapse
No I am obviously not the lucky one
My android development knowledge is zero, so if you can run zergRush from executable area it will be a very good start.
And I want to thank everybody for your support.

So, it doesn't work?
I just updated the file, so give it another try.
Also, check if you have logcat and usb debuging enabled(is needed for other methods, so maybe needed here too)

dancer_69 said:
So, it doesn't work?
I just updated the file, so give it another try.
Also, check if you have logcat and usb debuging enabled(is needed for other methods, so maybe needed here too)
Click to expand...
Click to collapse
Logcat: Cannot copy boomsh. : Permission Denied

I will revert to first beta now - and will test if it will work

I suppose this logat message is for z4root fail. Unfortunately I don't know what boomsh is. I just decompiled the apk and replaced the exploit, busybox, superuser, and su files with these from doomlord's root files directory.
So, easy solution didn't work. If I have something else I'll let you know.
EDIT:
I get some info about "cannot copy boomsh"
The exploit creates this file when run. This message appears when this file already exists and needed to be deleted from /data/local/tmp.
I checked z4root-mod on my device(which is already rooted and with ICS custom rom), and I get this message too.
The problem is that this file doesn't exist on my device, so I cannot delete it.
---------- Post added at 04:16 PM ---------- Previous post was at 03:17 PM ----------
I read on a forum that these apps(as z4root) run better after a fresh boot. So, install the latest apk(has newer files), reboot the device and run z4root again.

z4root is a froyo root exploit (I think) and seems "dead" for a long time.
Check Chainfire's Gingerbreak: http://forum.xda-developers.com/showthread.php?t=1044765

KitKat Loss of SD card write access

To anyone who has installed Kitkat XXUFNAD and lost write access to their SDcard, here is a solution.
I am not the original person who found this solution , I'm just putting it together here to help others.
You need root access to do this, of course.
1. Use something like root explorer to to go to the root folder
2. From there go to folder system/etc/permissions
3. Look for file called "platform.xml"
4. Edit this file ( your editor should open it in R/W mode )
5. Locate the following line :
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
6. Add this line " <group gid="media_rw" />", so you get
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
7. Save the file
8. Reboot
You should now have WRITE access back for your SDcard.
I have done this on my i9505 snapdragon without any issue.
All the usual caveats apply ie I not responsible etc etc
I can only assume that when Samsung release the official version, they will put this feature back.One of the fundamental reason I have bought and stayed with Samsung is because of the SDCARD possibility.

sohotha said:
To anyone who has installed Kitkat XXUFNAD and lost write access to their SDcard, here is a solution.
I am not the original person who found this solution , I'm just putting it together here to help others......
I can only assume that when Samsung release the official version, they will put this feature back.One of the fundamental reason I have bought and stayed with Samsung is because of the SDCARD possibility.
Click to expand...
Click to collapse
Good, good, I feel that the Force is strooong in you, young padawan. But, still the learning need you. It will be a day, when the force will allow you to be able with understanding to read, and to search.
But you are not patiently waiting until your abilities will grow I see. Into the dark side it will take you, I feel.
For the next time, instead to rediscover the America, please read the General section. Doing such, this old info you will find.
And now return to the Jedi practice with sword I recommend you to get stronger force control I ask you.
:laugh::laugh:

spamtrash said:
Good, good, I feel that the Force is strooong in you, young padawan. But, still the learning need you. It will be a day, when the force will allow you to be able with understanding to read, and to search.
But you are not patiently waiting until your abilities will grow I see. Into the dark side it will take you, I feel.
For the next time, instead to rediscover the America, please read the General section. Doing such, this old info you will find.
And now return to the Jedi practice with sword I recommend you to get stronger force control I ask you.
:laugh::laugh:
Click to expand...
Click to collapse
Yes .. yes.. I find myself too impatient to look for the ways of the power of the "SEARCH" on my path to enlightenment ...:crying:

sohotha said:
Yes .. yes.. I find myself too impatient to look for the ways of the power of the "SEARCH" on my path to enlightenment ...:crying:
Click to expand...
Click to collapse
:good:

Camera not working after this tweak

[HOW-TO] Remove AT&T Boot Screen

You must be rooted to do this
Using your favorite File Manager with root permissions:
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
That should be it.

gg AT&T carrier garbage
thanks for post!

Thanks. Everyone is crying for nothing, took only 30 sec to remove the boot screen.

Bjray said:
Thanks. Everyone is crying for nothing
Click to expand...
Click to collapse
Well it could have been much more difficult but yes there seems to be a great deal of fretting about this phone and AT&T. Actually about the N6 (Nexus in Name Only) in general.

that was easy as hell! thanks! now I just need to find out how to get rid of those AT&T ringtones.
edit: found em in the same directory, can just remove em.

Thank you for this. I had a feeling it couldn't be too hard to get rid of. I .bak'd all of those stupid at&t ringtones too.

P1 Wookie said:
Thank you for this. I had a feeling it couldn't be too hard to get rid of. I .bak'd all of those stupid at&t ringtones too.
Click to expand...
Click to collapse
I did the same as well.

P1 Wookie said:
I .bak'd all of those stupid at&t ringtones too.
Click to expand...
Click to collapse
There's an (earlier) AT&T un-customizing thread.

g33k3r said:
You must be rooted to do this
Using your favorite File Manager with root permissions:
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
That should be it.
Click to expand...
Click to collapse
Out of curiosity, is there anything else on the /oem partition? Can someone post a complete file listing or partition image? Are there any driver/binary blobs, or are those all in /vendor? I imagine a "format /OEM" function will be really handy to have in all custome recoveries going forward, as an easy way to remove bloat without rooting.

DA6030 said:
Out of curiosity, is there anything else on the /oem partition? Can someone post a complete file listing or partition image? Are there any driver/binary blobs, or are those all in /vendor? I imagine a "format /OEM" function will be really handy to have in all custome recoveries going forward, as an easy way to remove bloat without rooting.
Click to expand...
Click to collapse
The partition is empty on Sprint.
Sent from my Nexus 6 using Tapatalk

DA6030 said:
Out of curiosity, is there anything else on the /oem partition? Can someone post a complete file listing or partition image? Are there any driver/binary blobs, or are those all in /vendor? I imagine a "format /OEM" function will be really handy to have in all custome recoveries going forward, as an easy way to remove bloat without rooting.
Click to expand...
Click to collapse
Here is what was in mine:
/oem/lost+found/
(empty)
/oem/media/
/oem/media/ringtones/
/oem/media/ringtones/ATT_Catch_Me.mp3
/oem/media/ringtones/ATT_Firefly.mp3
/oem/media/ringtones/ATT_Play_On.mp3
/oem/media/ringtones/ATT_Stargazer.mp3
/oem/media/bootanimation.zip
/oem/oem.prop
oem.prop contains one line:
"ro.config.ringtone=ATT_Firefly.mp3"
The entire oem partition looks completely useless and should be safe to nuke.
Edit:
I emptied the oem partition entirely. Going to do a quick round of testing and make sure nothing is messed up and report back.
Editx2: back!
Everything is working great. The only thing I noticed is that the call ringtone was initially set to "Unknown ringtone" after first boot. It was probably set by oem.prop and then couldn't find it after that. Just changed it to a different tone, works great.

My accelometer stopped working, can anyone make a backup of the AT&T oem partition, or grab the files and send them my way. I would be greatly appreciative.

Nopcodex90 said:
My accelometer stopped working, can anyone make a backup of the AT&T oem partition, or grab the files and send them my way. I would be greatly appreciative.
Click to expand...
Click to collapse
Did you ever get this resolved?

Nopcodex90 said:
My accelometer stopped working, can anyone make a backup of the AT&T oem partition, or grab the files and send them my way. I would be greatly appreciative.
Click to expand...
Click to collapse
See this post in the Remove AT&T Carrier customization open thread for a backup file of the AT&T oem directory. Although I don't think that there is anything in that directory that would effect your accelerometer.

Quick question: I just ordered a Nexus 6 from AT&T, and when my 18 month Next period is over, how can I get the AT&T logo back on to the phone?

pyrogoggles said:
Quick question: I just ordered a Nexus 6 from AT&T, and when my 18 month Next period is over, how can I get the AT&T logo back on to the phone?
Click to expand...
Click to collapse
They won't notice it is gone, and probably wouldn't care if they did notice. I returned two phones through Next, all they did was a factory wipe, didn't check any settings.

pyrogoggles said:
Quick question: I just ordered a Nexus 6 from AT&T, and when my 18 month Next period is over, how can I get the AT&T logo back on to the phone?
Click to expand...
Click to collapse
as already stated. they wont care. i sent back my ATT HTC One m8 after converting it to GPE. They just care if its damaged and powers on.

Wait so just deleting the bootanimation.zip will fix the att boot screen?

Itzamistry said:
Wait so just deleting the bootanimation.zip will fix the att boot screen?
Click to expand...
Click to collapse
The OP in this thread is an unattributed lift from <remove-att-carrier-customization-thread>
Note the identical text.
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
Click to expand...
Click to collapse
Please read the original. Note that rebooting isn't required. It's only to verify you renamed the correct file.

Since I haven't rooted mine yet I wonder if I can do this or disable it using sideload? Any thoughts?

How to Disable proximity sensor in Nougat

Hello everyone,
My sensor went bad after screen replacement. It always detects as near. Until now I was using xposed to disable it. But now after upgrading to Android N, I don't have xposed and I don't know how to fix it.
The screen is turned off when I make/attend a call, making it difficult to end.
Is there any config file or something in source where I can disable it??
Thank you.

You can use settings>accessibility>Use power button to end call...

Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.

swapnil0545 said:
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
Click to expand...
Click to collapse
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.

The solution for that it change the black thing make the bigger hole on sensor of light and the small one with other
Default for that is small one with sensor light and bigger one for something else
So sorry for bad language see that steps here
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176

ze7zez said:
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
Click to expand...
Click to collapse
I am going to try this. I hope I don't soft brick it.

swapnil0545 said:
I am going to try this. I hope I don't soft brick it.
Click to expand...
Click to collapse
Hey did you get it to work?

I've tried - no, did not work on 7.1.

Have you any other solution? I've the same issue on nexus 6p After display replacement. And now on nougat i can't fix it. Simeone Can help me?

My other solution was to recompile Dialer.apk with proximity disabled.

digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Where is the apk located? I'm running 7.0 and cannot find it in the system/apps folder.

On CM14 it is in /system/priv-app/Dialer/

digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253

You are a life saver
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7 ?

sweetmyke said:
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7
Click to expand...
Click to collapse
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.

driftking132 said:
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Click to expand...
Click to collapse
You should run these commands on a PC, to which phone is connected by USB cable.

digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
I've attached my version of the fix that I've been running since CM13, now recompiled for CM14.1. There's effectively only one line of code changed. Source is up-to-date to Feb 6, 2017.
As far as I can tell, digital0's version works just as well, so there's no reason to try mine if you're not having issues with his.
Same way to install the apk. Attached diff for the curious.

Shimakaze said:
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
Click to expand...
Click to collapse
The CM build I used at the time of compiling gave the error. It is most probably not needed now.

driftking132 said:
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
Click to expand...
Click to collapse
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped

sweetmyke said:
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
Click to expand...
Click to collapse
its worked but in call screen there is no answer/ reject buttons please fix this

Solved Is there a way to disable "10 attempts remain before device data is deleted"

Solved Is there a way to disable "10 attempts remain before device data is deleted"
I'm on a VZW 7.0 stock s-off locked rooted (SuperSU systemless) busybox systemless
Is there a way to stop Android from erasing the phone if the lock screen is
misentered 10 times? I mean other than turning off the lockscreen.
Thanks

fuzzynco said:
I'm on a VZW 7.0 stock s-off locked rooted (SuperSU systemless) busybox systemless
Is there a way to stop Android from erasing the phone if the lock screen is
misentered 10 times? I mean other than turning off the lockscreen.
Thanks
Click to expand...
Click to collapse
You can edit the system\customize\ACC\default.xml
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]10[/B][/COLOR]</item>
[B][COLOR="Red"]to[/COLOR][/B]
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]0[/B][/COLOR]</item>

andybones said:
You can edit the system\customize\ACC\default.xml
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]10[/B][/COLOR]</item>
[B][COLOR="Red"]to[/COLOR][/B]
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]0[/B][/COLOR]</item>
Click to expand...
Click to collapse
That worked, but I lost advanced calling, (presumably due to modifying /system), sigh.
Restored system from TWRP backup and advanced calling works again,
I wonder if there is a way to do it with Magisk?

fuzzynco said:
That worked, but I lost advanced calling, (presumably due to modifying /system), sigh.
Restored system from TWRP backup and advanced calling works again,
I wonder if there is a way to do it with Magisk?
Click to expand...
Click to collapse
Sorry I should had realized that from your OP.
A Magisk module can def be created I'm sure, however I haven't dug into creating any, so I'll take a look - but if others are reading this and don't mind lending a hand that's be great.

andybones said:
Sorry I should had realized that from your OP.
A Magisk module can def be created I'm sure, however I haven't dug into creating any, so I'll take a look - but if others are reading this and don't mind lending a hand that's be great.
Click to expand...
Click to collapse
1. Copy (don't move) default.xml from \system\customize\ACC to a new folder \cache\magisk_mount\system\customize\ACC\.
2. Edit the copied (not original) default.xml in the magisk_mount subfolder as per @andybones' instructions in post 2.
3. You should be good to go.
I have made other tweaks (from time to time) in that file and Magisk mounts it just fine.
.

Works ! with advanced calling.