Database Info

1.18.405.1 OTA update

Hi
Here is the ota update i have just received on my azerty ChaCha :
http://www.megaupload.com/?d=JK8WZOY3
Maybe you can use it by copying it at the root of your sdcard, renaming it as update.zip and rebooting the ChaCha in recovery mode throw adb

geek78 said:
Maybe you can use it by copying it at the root of your sdcard, renaming it as update.zip and rebooting the ChaCha in recovery mode throw adb
Click to expand...
Click to collapse
I tried to update from Europe_1.13.401.1. Get error status7 and can't update.

This update is only for devices under 1.15 this is a diff patcher from 1.15 to 1.18.

Have you been able to get root access with this. This came on the device I won from htc at work and superuser keeps crashing. Im considering attempting a downgrade as I got the recovery menu installed as it came s-off

Just follow this guide :
http://forum.xda-developers.com/showthread.php?t=1184118

geek78 said:
Just follow this guide :
http://forum.xda-developers.com/showthread.php?t=1184118
Click to expand...
Click to collapse
thats the one that doesnt work. It force closes everytime an app requests access.

have you tried to update superuser (on the market) ?

geek78 said:
have you tried to update superuser (on the market) ?
Click to expand...
Click to collapse
yeah it doesn't work. im wondering if its a problem with the app

Please try the following procedures.
(1) Delete Superuser's update and clear data.
(2) Reinstall update.
(3) Enable 'Auto-rotate screen' on the Display settings.
(4) Change the screen to the portrait mode.
(5) Run Superuser and allow permission to update its own.
I solved a same problem in this procedure.

osahiro said:
Please try the following procedures.
(1) Delete Superuser's update and clear data.
(2) Reinstall update.
(3) Enable 'Auto-rotate screen' on the Display settings.
(4) Change the screen to the portrait mode.
(5) Run Superuser and allow permission to update its own.
I solved a same problem in this procedure.
Click to expand...
Click to collapse
Yeah this is what worked for me in the end. its a bit fiddley though isnt it. Oh well sorted now at least. Maybe this should be added to the rooting thread.
Have you noticed that you can move apps to the sd in manage applications. It seems that some people have been supprised that it does it.

FCW said:
Yeah this is what worked for me in the end. its a bit fiddley though isnt it. Oh well sorted now at least. Maybe this should be added to the rooting thread.
Have you noticed that you can move apps to the sd in manage applications. It seems that some people have been supprised that it does it.
Click to expand...
Click to collapse
isn't the option to move apps to sd in manage applications a feature way back in froyo?

Superuser crashed on me first time with every app that asked, either the button was cropped so rotating shows true button, or it worked fine after a reboot.
Sent from my HTC ChaCha A810e using Tapatalk

[Q] Root CAT b10

Hello,
I need to root a CAT b10 telephone. I tried using superuser program but it didn't work. I can't find any documentation for this phone in Internet.
Do you know a method to root this phone?
Thanks.

cabrerachaparro said:
Hello,
I need to root a CAT b10 telephone. I tried using superuser program but it didn't work. I can't find any documentation for this phone in Internet.
Do you know a method to root this phone?
Thanks.
Click to expand...
Click to collapse
You have to root this phone via RECOVERY. Use attached file and UPDATE FROM SDCARD.
Also you must not update (after recovery root) SUPERUSER app via android-market to newer version!!! If you'll do it, then it all comes broken. And you have to do it once again.

ninr said:
You have to root this phone via RECOVERY. Use attached file and UPDATE FROM SDCARD.
Also you must not update (after recovery root) SUPERUSER app via android-market to newer version!!! If you'll do it, then it all comes broken. And you have to do it once again.
Click to expand...
Click to collapse
Hi,
I followed the instructions but I'm getting Force Close message for superuser app. Even applying factory reset.

cabrerachaparro said:
Hi,
I followed the instructions but I'm getting Force Close message for superuser app. Even applying factory reset.
Click to expand...
Click to collapse
OK, that's no problem.
Attached package contains few another packages....(update.zip is the same like I uploaded here before)
1. Try to use "Superuser-3.1.3-arm-signed.zip" (this should be enough but I don't know why it isn't)
2. Reboot
3. Look at Superuser app
4. If Superuser app doesn't work then use "update.zip" once again
5. Reboot
6. Look at Superuser app
7. Now it should be working if not you can update Superuser app from market and try above procedure once again
Root this phone is really long term job. But never give up!! This phone is useless without root. I have been rooting this phone more then week.
Good luck and post if will you be successful.

just wondering since you have some experience with the phone.is there a custom rom for this phone or just the original one?

[Resolved] [Q]Need Help with Xperia Miro lost root access

Hi All,
I have screwed up my android which was perfectly fine with a perfect root. Please help me to restore the root access !!!
Here is my problem description:
I have a Sony Xperia Miro which was perfectly rooted.
Model : ST23i
Android : 4.0.4 ICS
Build : 11.0.A.5.5
The root verification using app 'root checker basic' was successful.
Now I had few of my company apps and bank apps which wouldn't work in rooted device. But I never wished to lose my root status. So I was searching for the ways to hide root access from these apps. I even came across apps exclusively built for this purpose (hidemyroot/OTA root keeper) But due to some bad comments about these apps, I decided to try manually
The idea was to fool the apps when checking the root access.
At first I renamed the super user apps at the location /system/apps. to some invalid file(super.txt)
This did the trick for couple of apps which weren't working before in my mobile. However couple of apps were still failing.
The next thing I did was renaming .su to ku in the below location /system/bin/.ext
Then I verified Root Checker Status, still it displayed "u have root access"
Then I went to /system/xbin and renamed the following.
.su to ku
.busybox to busyboxk
.dexdump to dexdumpk
Then I tried Root Checker Basic again. And got the message "device don't have proper root"
But still my apps were not working. Then I did the most foolish thing which was restarting the device.
BAM.. !!!! I lost my root access permanently. Now I don't have superuser app. And I m not able to use 'Root explorer', to rename back the files to its original state.!!! And most ironic thing is my company app still saying I have root access. I tried after deleting its cache and data. The result was same !!
How can I restore my root access ? Please help

one update
Since I renamed the superuser and superSu applications, I couldn't use them.
Today I installed both of them using package installer.
But they doesn't seem to work as they can't find su binary installed

See the attached

appviz said:
See the attached
Click to expand...
Click to collapse
Do you have a Custom Recovery setup and if so did you make a backup after root?.

keifus.rahn said:
Do you have a Custom Recovery setup and if so did you make a backup after root?.
Click to expand...
Click to collapse
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/

appviz said:
Nope . I neither installed any custom recovery like CWM nor took any back up.
I am really feeling the need right now !!:-/
Click to expand...
Click to collapse
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your device. The same thing happend to me awhile back :/ If you want to save your apps use titanium back up or app backup & restore and add a custom recovery like cwmr so if this happens agen you wont have to reroot. if you are still having problems with your apps for work boot your phone into recovery and go to advanced then fix permisions if you have any other questions or any problems just let me know.
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it

keifus.rahn said:
I hate to be the one to tell you this but it looks like your going to have to do a factory reset and reroot your
oya dont backup your superuser and supersu on your app backup sence you renamed them redownload your superuser if it dont come with your root program that you are using. and dont use supersu unless you really need it
Click to expand...
Click to collapse
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.

appviz said:
HI,
I prefer to fix the issue in the same way it's been happened. The issue occurred when I renamed the
Su binary manually. I was trying to find ways to rename it back. So here is what I am going to try...
1. Pull the files using. Adb to PC and rename and push it back to phone.
If this doesn't work,
2. Install CWM and flash the zip file to install su,busybox,superSu
If this also doesn't work,
3. Reroot the phone
Unfortunately I can't do any of this right away. I will try this as soon as possible
and tell you which method worked for me.
Click to expand...
Click to collapse
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device

keifus.rahn said:
:good: Plz do. I should have thought about pulling them. Im writing a guide on adb and didnt think about that lol guess my brain is fried from 18hr shifts and coming home and getting on here lol. But any ways after you pull them just replace them with new files insted of renaming them it would be less of a hassle. I would still install cwmr on your device
Click to expand...
Click to collapse
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...

appviz said:
Solved the issue Finally !!
I was trying to pull the renamed files to PC(Windows Xp SP3) using adb. But I find lot of trouble setting up adb in Sony Xperia Miro. I updated my device by using Sony PC companion. Still couldn't get my device detected in the command 'adb devices' . Then tried to update google usb drivers. It didn't work at first, but I could install google usb drivers after changing android_winusb.inf file to include my device ID.
But even after I could get my device show up in command 'adb devices', I couldn't pull/push files. For some strange reason, my device was disconnecting continuously and each time I have to stop adb.exe process and restart to get my device connected back. And I finally gave up in the process.
Then all of a sudden it clicked me that why don't I use terminal emulator installed in my phone. But the biggest road block was to get root access. Root access will be given if you execute 'su' command in 'adb shell' . But I renamed the su binary. what do I do!!
Then I decided to give it a shot that executing the renamed binary !! (I had renamed su to ku). So I simply gave ku in adb shell. whola!! It worked. I got root access.
All I need to do was, change the permissions (using chmod) and rename the files back(I used root explorer) to correct names.
And I am done I got my ROOT BACK !!:good::victory::victory::
Later I updated my su binary and all is well in my device now. And what more, I found way to get my company apps work in my rooted mobile. I installed OTA rootkeeper and temporarily disabled root. Guess what it was still not working.
Then I tried my old stupid trick again (together with OTA temporary unroot). Rename SuperSu in /system/app .
And it worked !! But I won't be stupid again to reboot my device with this settings. And even if I did accidentally, I know what to do.. !!
Thanks everyone...
Click to expand...
Click to collapse
That's Awesome :highfive: I'm glad the hear that you got everything working correctly and with your company apps too. :victory:
Thank you for sharing with me and everyone. You never know if some one out there is having the same problem and this could really help them out one day.

[Q] Lost root access?

Hi guys android newbie here! My friend rooted my Nexus 5 and it was working fine for a couple of weeks. Yesterday I tried to open SuperSU and it didn't work! Other apps that required root didn't work either.
I have been looking around and it seems OTA updates may have screwed up my root. Every time I try to open SuperSU it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" If you just upgraded to Android 4.3 (I have 4.4), you need to manual re-root. Consult the relevant forums for your device!" I have used root checker by joeykrim and it says "Sorry! this device does not have proper root access" (to confirm my root is busted).
My question is, is there any way to fix this without re-rooting? If I have to re-root, can I just directly re-root it again using something like Wugs rootkit?
Thank you very much in advance!

Just flash the newest version of supersu and you'll be good to go..... http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip

go to the play store, find supersu, install/update it, open tbe app and update your binaries.

simms22 said:
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
Click to expand...
Click to collapse
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!

seyba said:
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
Click to expand...
Click to collapse
cant even get into it?

Yea it says there is no SU binary installed. I think I've lost root access

seyba said:
Yea it says there is no SU binary installed. I think I've lost root access
Click to expand...
Click to collapse
flash this with your custom recovery, its the latest supersu http://download.chainfire.eu/supersu

bodooo said:
Just flash the newest version of supersu and you'll be good to go.....
Click to expand...
Click to collapse
I can install/update to v1.8! I just can't open it. Gives me a "SU binary not installed" when I do!

Did you install/update from the playstore or flashed the new update?

simms22 said:
flash this with your custom recovery, its the latest supersu
Click to expand...
Click to collapse
Sorry if this is a stupid question .. but how/ do I flash this or what program do i use?
My friend helped me root it so i have no idea on how to do this @@ Very sorry.

Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest

bodooo said:
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
Click to expand...
Click to collapse
Ok so I can't open flashify either. It also says I have lost root access and my superuser is busted. I have attached a screenshot!
http://i42.tinypic.com/2mgw0v6.png

Of course, you don't have root access, silly me lol Well guess we'll have to do it the hard way (it's not really that complicated) ok read carefully. Power off your phone, afterward hold the power and volume down buttons which should get you into the bootloader, cycle trough the options with the volume buttons and when you see recovery mode select it with the power button, now depending on which Recovery you have you'll have to choose the option that says install or install from sd card, again, depending on which one you have this will be slightly different. After doing i believe the paths will be the same, chose 0/ then look for the download/ folder which you should have that supersu.zip file, if you're using twrp recover it should be touch screen and you simply select it and swipe to install, if you're using cwm (which i do) you'' have to scroll with the volume buttons and select the file with the power button to install. I hope I was as clear as i could be, good luck

after going into recovery mode, there is just a android robot with his chest open and an exclamation mark! can't proceed after that.

Ouhhh you don't have a recovery then, do you have adb or any kind of toolkit?

I have wugs toolkit. but every time i try to do anything at all on it. It says ADB device not found? That seems to be preventing me from doing anything as well.

Do you have the adb drivers installed or/and usb debug turned on in developer settings?

how/where do i install adb drivers? I have not done so, and i doubt my friend did it when he rooted.
I do turn on usb debugging when i tried to unroot/root on wugs toolkit

In wugs toolkit it has a walk-through on how to do so, i suggest you use the RAW drivers option

I must be blind to not have seen this before. Thank you very much for your help I'll let you know how it goes!

MicroG Bricked Whole Phone

Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.

bitblocksplicer said:
Hello,
Actually I'm kinda new at root. I used to root phones that weren't too complicated to root, like the Samsung Galaxy W, so I have "pretty basic" rooting knowledge. I successfully rooted my phone this morning. There was no problem but in many modules and rooting applications it was not working properly because the system file was not read/write-able. I haven't been able to find any information, especially for Android 12, despite a lot of research. I was getting errors like "'
Code:
/dev/block/dm-0' is read-only
" and "
Code:
verity cannot be disabled/enabled - USER build
" when trying to grant write permission to the system file via adb. Eventually I came across this post on the forum: https://forum.xda-developers.com/t/fairphone-4-remove-google-apps-microg.4379791/post-86159173
I downloaded "NanoDroid-microG-23.1.2.20210117.zip" from here, then installed via Magisk app.
Actually I didn't know that this module removes Google apps. After I reboot, looks like my phone was completely broken. Not only Google apps, even the launcher crashes. Crash video here. After a while everything crashes, the phone automatically boots into Recovery mode.
I had a backup of Boot before. I first deactivated and then removed the last installed Magisk module via TWRP. I restored the Boot I backed up but the problem still persists. At the moment I have no idea of any solution other than a clean install on the phone but that would be the last thing I want. Is there any other way to solve this?
Thanks in advance.
Click to expand...
Click to collapse
Which ROM are you actually running?