Recovery replaced

Every time I flash cyanogenmod 12.1 on my device, xperia M C1904, I loose my custom recovery, i.e., CWM or TWRP and get reverted back to Cyanogen Recovery and I say to you that this recovery is bad, literally very bad. Nothing ever works with this recovery.

The command am using to flash recovery is:

Quote:

fastboot flash boot boot.img

Thank you in advance. :)

Sent from my C1904 using XDA Free mobile app

Replaced USB port LOST OTG CAPABILITIES

I have a rooted Samsung Galaxy Mega 6.3 that needed a charging port, I replaced the,part myself this past weekend and now all of the sudden it only registers to anything that is a Samsung part when it comes to charging or sync....Nothing else, tried other cables and no luck.... Then I wanted to transfer something out of my flash drive via OTG and once again NO LUCK whatsoever. So what could be the problem with this? Do I now have to get genuine oem accessories in order to utilize this phone or is there something missing that I didn't get to do software wise.

Sent from my GT-I9205 using XDA Free mobile app

TF300 no power at all. Replaced batt/charging ribbon. Mainboard next?

So, this was my mothers tablet and it stopped working one day. She hadn't used it in a while and it was simply under her bed. After a period of no use she pulled it out and tried to use it - didn't work at all. Plugged in = no response, etc.

Friend has same tablet, same charger, etc. Tried his charger with her tablet, nothing. No charging light, no indication of response of the tablet whatsoever.

Tried the long-time trickle charge using a lower power charge, left it charging for days on end. Still nothing.

Tried replacing the battery and the charging port/ribbon, still nothing. Left to trickle charge again and still nothing.

This was all many months ago and she has since given up and purchased a new tablet. I thought of a good use for this TF300 if I could get it working so figured I'd try to fix it. Is there anything else I need to try before I just go ahead and replace the main board? It's only like on ebay so no harm done if it doesn't work.

Archos 50c Neon: Rooted with KingRoot, replaced, but unable to use SuperSU

Hello Archos community,

I have bought the new Archos 50c Neon in early July, because of its nice price-performance ratio and the fact that it runs Android 4.4.2.

I have been able to successfully root it using Chinese "KingRoot", but am looking for an alternative SuperUser app. I already own a license of SuperSU Pro (which I am using for my tablet), but it turns out that the current versions of SuperSU (both 2.46 and 2.49) currently cause a crash when calling "su" from adb - seemingly because the Dalvik VM is unable to instantiate class "android.os.Environment" from SuperSU code when SuperSU wants to display its UI dialog that asks for permission. For the detailed issue description, please see here:

My thread in XDA SuperSU forum: Crash when trying to run su

Unfortunately, Chainfire (the author of SuperSU) from his signature is "away for most of the summer", and I will wait until he's back and then point him to this issue one more time.

In the meantime, I have created a script to successfully remove all remains/remnants of KingRoot (after successful rooting with it) and replace it by Koushik Dutta's OpenSource Superuser package:

https://play.google.com/store/apps/d...utta.superuser
http://www.koushikdutta.com/post/superuser

I have attached a ZIP file to this post that includes everything needed to do so - here are the instructions:
Please note that I do not take any responsibilities in case you brick your device, and also note that you void your warranty for the phone when rooting (these should be clear anyway)!

1. Reset your Neon 50c to factory settings (optional, might be needed in case you run into issues otherwise when removing KingRoot)


2. Unzip the attached ZIP and copy its contents to the root of the internal SD storage on your 50c Neon (directory /sdcard)


3. Use the included kingroot_4.0.0.apk to root your phone (allowing to install apks from untrusted sources)


4. Then, from your PC, open an "adb shell" to your device (you need to activate developer mode and USB debugging in order to do so)


5. From this adb shell, execute "su" and allow this root access through the KingRoot dialog on your phone. You now have a root shell on your phone.


6. Open a second adb root shell in the same way to not become stuck in case something goes wrong with the first one


7. In the first adb root shell, cd to /sdcard and execute my script in the following way:
   
   
   

   Code:

   
   

   ---

   cd /sdcard
sh -x ./kingroot_2_koush_su.sh ./busybox ./superuser.zip

   ---

   
   
   and while it is running, press enter three times when "ps | grep king" and "ps | grep k_" show whether there are still processes running on your device that are related to KingRoot. General rule here is: When there are processes still running for the first ("ps | grep king"), something went wrong and KingRoot uninstall will most probably fail, while the fact that only processes matching the second ("ps | grep k_") are found, is normal and will NOT stop the script from working successfully.


8. When the script has finished, your phone will do a "soft reboot" (from killing zygote). You should do another explicit "hard" reboot afterwards anyway before trying to use the newly installed Superuser package.

I have run this script myself on my device, and am pretty confident that after the script has run successfully, there are no remains/remnants of KingRoot left on my device. The Open Source Superuser app by Koushik Dutta runs without any issues.

Hope this helps - and am still looking for some help with why SuperSU crashes on the 50c Neon although it seemingly has been installed properly...

Best regards,
awl

Attached Files

kingroot_2_koush_su.zip - [Click for QR Code] (11.79 MB)