Related
ATTN: My rom is bare basic, if your looking for a more streamlined rom
check out grdlock bluid based on the same source. Link removed because of assholes.
SNIP SNIP Several others released far more indepth and better roms, use them (like grdlock's).
http://www.androlib.com/android.application.com-hookerbots-rpics-twDt.aspx
I don't take donations. If you like my worth, the above app is from my favorite author, support him and of course XDA.
jcase said:
# id
uid=0(root) gid=0(root)
# busybox whoami
whoami: unknown uid 0
# busybox uname -a
Linux localhost 2.6.29-564a4a15 #1 PREEMPT Thu Feb 25 15:56:06 CST 2010 armv6l GNU/Linux
#
Just wanted to put that out there. If not one else puts out a better rom based on OTA tomorrow, I'll release it.
Its just bare OTA with su/superuser.apk.
Click to expand...
Click to collapse
That's exactly what i'm looking for an OTA with su added.
Thanks! can't wait for the upload.
i see you conquered the problem. MAGIC! well done
Thanks jcase! Will be testing tomorrow. Don't forget to rm /system/etc/security/otacerts.zip
flashing now. letting it run overnight should let me know if the stock Messages app bug is fixed. if not, Handcent it is!
So once again... no root for us that went to the 2.1 leak?
LexusBrian400 said:
So once again... no root for us that went to the 2.1 leak?
Click to expand...
Click to collapse
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
hoban_eris said:
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
To be clear, install the otaroot rom released by jcase if you already have root. Install the OTA rom direct from HTC if you currently have the leaked 2.1.
hoban_eris said:
Nope. In order to flash a new rom without root, the HTC signature needs to be valid. In order to preserve root, the rom was modified by jcase to include su which breaks the signature hash. So, while you will be able to update to the official OTA update (assuming version is higher, which I believe to be the case), you can't install this rom.
Since most people will be updating to the OTA 2.1 away from the leak or away from 1.5, I'd personally recommend installing the OTA 2.1 directly from HTC. We'll likely be targeting it for root exploits next and abandoning version 1.5.
Click to expand...
Click to collapse
Thanks for the clarification. I really appreciate it. Can't wait for OTA root
The new 2.1 is exactly what I wished the last leaked 2.1 would have been. Its working so much better with no noticeable lag at all.
Thanks again guys!
wipe data
I have root now and am currently running the .3 rom, question
1. is this just an update to what i am running now?
2. Do i need to preform a wipe?
3. if i dont wipe does the phone maintain all my apps and settings i.e email google etc?
Damn, I was just uploading my all-in-one batch script and then I noticed this had been released... I started making a rom of it, then I noticed you already did! hah!
Thanks for being a night owl and already doin the work jcase. I'm gonna incorporate this into the all-in-one script.
mv error: cross-device link
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
liushk said:
i have updated this rom, works great!
bu i can't mv from /system/app to /sdcard
error message is "cross-device link"
but i had already remount the /system partion as rw, and i notice that rm is working fine - i can remove files in /system/app, but can't move to another directory!
before update to this rom, mv is working correct
any advice?
btw, there is no busybox in this rom
Click to expand...
Click to collapse
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
hoban_eris said:
same problem here. you can copy files and then remove the source. that's what I've been doing for my moves. As for busybox, I installed it myself, but I'm sure someone (if not me) will release an update.zip to install it sooner rather than later.
Click to expand...
Click to collapse
thanks for reply
I tried install busybox myself, but it dosn't work. this is my steps:
adb push busybox /sdcard/
adb shell
remount /system
mv /sdcard/busybox /system/xbin
failed
adb shell
remount /system
switch to another console
adb push busybox /system/xbin
failed
and, there is no "cp" command, I didn't find another way to copy from /system/app to /sdcard/
Wipe??
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
The mv and cp commands are in busybox. I did not install busybox, so you don't have them. The Toolbox that comes with the OTA is lacking them.
Install busybox yourself, or wait for grdlock or ivan's release.
in case anyone is interested, the Messages app bug and cell standby bugs are fixed in this release too (as well as the already known gmail login bug fix) the phone also seems to power down a lot faster than previous leaks.
havent tested google voice yet, probably cant till later today. someone else feel free..
shickfaced said:
I just want to reiterate denonlake's question, does installing rooted OTA 2.1 require a wipe of DATA and CACHE partitions like the original root process? Can we preserve settings through this flash or is it best to go through the whole setup process again?
Click to expand...
Click to collapse
I first tried installing from zip through recovery.
This did not appear* to work.
Next, wiped device and cache, then installed zip through recovery.
Success!
*My experience is limited. Maybe it did work, but nothing on the phone appeared changed.
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
rustyman14 said:
Ok so this is just a rooted version of the Official OTA 2.1 right??? Nothing else has been done to it??
Click to expand...
Click to collapse
All this info is in the first post... X_X
jcase said:
This is the 2.1 OTA Rom with su, a modified sh, SuperUser.apk and spare_parts.apk added (root). Thats it, nothing else modified.
Click to expand...
Click to collapse
Greetings.
I am trying to install Cyanogenmod 7.0.2 on my HTC Tattoo (still has 1.6). This is the first time I've done this.
I am following the Cyanogenmod wiki page that shows you the whole process of rooting+flashing a new rom (since this is my first post I am unable to post outside links in this thread).
In the "Installing Clockworkmod Recovery" section, I get the following error when trying to flash the image:
flash_image: not found
I listed the files in /sdcard and saw that it was completely empty.
Can anyone tell me what I missed?
I copied the Clockworkmod image file to the root directory by connecting my phone to my PC through USB (USB Debugging was on) and copying the file there.
Please let me know how to solve this.
Thank you.
I was able to solve my problem and proceed with the attempt to flash Clockworkmod. Now I'm getting another error though:
error writing recovery: No space left on device
I have plenty of space in the SD Card (~2GB), but I'm assuming the problem is with the phone's internal memory. I don't know what I can delete.
Any thoughts?
Thank you.
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
CROpipe said:
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I tried to do as you said and installed both Rom Manager and Superuser. But now I have other issues...
1. On Superuser, it says there is a newer version of su and to update. I accept and get the following error:
An error occurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your binary.
2. So, I decided to ignore the update of su and just move on to Rom Manager. Here, I get an error like "su was not found in /system/bin". Well, su is in "/data/local/bin", as per the cyanogen wiki to root the phone. After this, any attempt to flash Clockworkmod fails.
3. To try to make it so Rom Manager has everything it needs, I followed the wiki again, but this time I tried to move the su file to /system/bin. I got the following error:
failed on './su' - Cross-device link
Any ideas?
Thanks in advance!
Hmm, i had the same problem when i was trying to Flash CM7...
Your phone is not rooted...
I know its very frustrating but no worries!
1.Download program from this thread ->http://forum.xda-developers.com/showthread.php?t=761507... you'll see the program in attachemnts and dl the first one.
2.Paste it in your's SD card , install it (use ASTRO MANAGER, to find the program)
3.Open the program and root the phone with 1 click
4. Then Superuser will ask you to allow it and click yes, and go to ROM MANAGER.
5.You will have to allow the Superuser here too.. Do it.
6.Flash Clockwork Mod recovery, and reboot into recoverymod.
7.Flash your Rom , flash Gapps(Google applications)
8.Enjoy
Thank you CROpipe!
Your instructions worked! I now have CM7 installed on my HTC Tattoo!
Here are the issues I found though:
1. When I was trying to download the ROM using ROM Manager, the list of ROMs was empty. Maybe it's because I was not using the Premium version...? I ended up downloading the ROM from the forum, copying it to the SD card and installing it that way.
2. I tried also to install GApps through Rom Manager. I was afterwards able to set up my google account, but I still had to manually download GMail, Google Maps, ... I'm not sure if this is actually how it's supposed to go... :-/
Anyway, thanks again for the help.
Yap that is quite allright Congrats on your new ROM ))
I open this thread to motivate to carry ice cream sandwich to our Motorola Defy Mini, and now we need to update root our devices and enjoy the latest versions of android.
Let's see if we can all get something.
I searched the internet and found yesterday that the Motorola Defy mini and htc xplorer have the same hardware, and the latter has adapted cyanogenmod 9.1, we can start there.
Let's try in this thread and with the help of all get a fully functional ics rom.
Please someone can move thist post to defy development
davis15 said:
Please someone can move thist post to defy development
Click to expand...
Click to collapse
Have you found new informations about the CM for defy mini? I am really impatient !!
You can find some kind of hw comparison on wikipedia's Snapdragon chipset:
http://en.wikipedia.org/wiki/Snapdragon_%28system_on_chip%29
and look at similar models what for support they got
.
CM10 HTC Explorer (Pico) port
First thing: What SystemROM size showing in Titanium Backup?
Model name will show as A310 (Explorer). Try that because I don't have Defy Mini. Build contains stock defy mini kernel. Defy Mini recovery: http://forum.xda-developers.com/showthread.php?t=2187074. Make nandroid of stock rom. Tell if you can boot to it. If yes i will try made custom kernel (kexec or 2ndboot) & simpler cwm usage (2ndinit or 2ndboot) ,Model name will show as A310 aka Pico. If not, when restore nandroid or reflash stock rom via RSD Lite.
LINK: http://www.gigasize.com/get/g3kc53g7o7d
Also: if it boots make screenshot (better photo cause i will know if you didn't faked) of About Phone.
new stock roms
I just got a new Motorola Defy Plus phone with gingerbread 2.3.x stock rom.
Where can I find a Motorola Defy Plus ICS or Jellybean stock rom?
Not Cyanogenmod or AOKP/AOSP.
Is there any such thing as a stock ICS or Jellybean for Motorola Defy Plus rom?
So far all I see is cyanogen/aokp/aosp ics and jellybean roms.
Does this means that most likely there are no stock ics/jellybean roms for the phone?
Thanks
Misterjunky said:
I just got a new Motorola Defy Plus phone with gingerbread 2.3.x stock rom.
Where can I find a Motorola Defy Plus ICS or Jellybean stock rom?
Not Cyanogenmod or AOKP/AOSP.
Is there any such thing as a stock ICS or Jellybean for Motorola Defy Plus rom?
So far all I see is cyanogen/aokp/aosp ics and jellybean roms.
Does this means that most likely there are no stock ics/jellybean roms for the phone?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1795647
created kernel for defy mini
For who is interested:
I created an ICS kernel based upon the motorola sources merged with some stuff from a 3.4 kernel from code aurora.
You can find it on https://github.com/de-wolff/android_kernel_motorola_xt320.git
I think it is capable of everything you need, but I am still working on the CM stuff for it.
(At this moment my phone can start using fastboot, into a CM9 version.I have a working touch screen, a working volume button, audio, when I touch the screen, and a working shutdown. I will commit this also soon, so anyone who is interested, can create his own CM9 version)
If someone can point me to how 2nd boot is supposed to work, I would be very thankful.
de-wolff said:
For who is interested:
I created an ICS kernel based upon the motorola sources merged with some stuff from a 3.4 kernel from code aurora.
You can find it on https://github.com/de-wolff/android_kernel_motorola_xt320.git
I think it is capable of everything you need, but I am still working on the CM stuff for it.
(At this moment my phone can start using fastboot, into a CM9 version.I have a working touch screen, a working volume button, audio, when I touch the screen, and a working shutdown. I will commit this also soon, so anyone who is interested, can create his own CM9 version)
If someone can point me to how 2nd boot is supposed to work, I would be very thankful.
Click to expand...
Click to collapse
2nd-boot is similar to how 2nd-init works where it uses a hijack to and it boots the custom kernel on top of the Motorola Stock kernel. It basically consists of a miniature bootloader to execute 2nd-boot. Can please upload what you have so far? I can help you to debug it. Thanks.
more progress
I am able to make a booting system, using code at:
https://github.com/de-wolff/android_device_motorola_xt320
I produced images and kernel:
http://dewolff.home.xs4all.nl/system.tar.gz
http://dewolff.home.xs4all.nl/kernel
http://dewolff.home.xs4all.nl/recovery.img
http://dewolff.home.xs4all.nl/boot.img
It boots (using fastboot), display working, touchscreen working, onscreen keyboard working.
I am convinced the kernel is complete, but I have still to create a correct camera.lib, and correct audio libs.
Also the gpu is not used (yet), but that is a matter of finding the right egl adreno libraries, and creating the correct libgsl.
If anyone wants to explore it: In system/lib/egl is egl.cfg.
This is a text file. When you remove the # on the second line, after reboot the system will try to use the adreno gpu.
The way to put system on the phone is extract on your system (eg using) remove all files in the existing system, create all directories on the system, and then transfer all files using adb push.
de-wolff said:
I am able to make a booting system, using code at:
https://github.com/de-wolff/android_device_motorola_xt320
I produced images and kernel:
http://dewolff.home.xs4all.nl/system.tar.gz
http://dewolff.home.xs4all.nl/kernel
http://dewolff.home.xs4all.nl/recovery.img
http://dewolff.home.xs4all.nl/boot.img
It boots (using fastboot), display working, touchscreen working, onscreen keyboard working.
I am convinced the kernel is complete, but I have still to create a correct camera.lib, and correct audio libs.
Also the gpu is not used (yet), but that is a matter of finding the right egl adreno libraries, and creating the correct libgsl.
If anyone wants to explore it: In system/lib/egl is egl.cfg.
This is a text file. When you remove the # on the second line, after reboot the system will try to use the adreno gpu.
The way to put system on the phone is extract on your system (eg using) remove all files in the existing system, create all directories on the system, and then transfer all files using adb push.
Click to expand...
Click to collapse
Use the Adreno Libs from the Qualcomm website. Is Hardware Acceleration working? How come it's saying its CM7 in the Github
@MauroSZ This is the instructions on how to install the custom ROM.
Use these commands in cmd
Code:
fastboot erase system
Code:
fastboot -w
Code:
fastboot boot recovery.img
Now mount /system
Code:
adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
Code:
exit
Code:
adb push system.tar.gz /sdcard
Code:
adb shell
Code:
cd /system
Code:
busybox tar xvzpf /sdcard/system.tar.gz
Code:
exit
Code:
adb reboot-bootloader
Code:
fastboot boot boot.img
And you will boot into the custom ROM.
EDIT: Custom ROM is not BOOTING
@Guitwo2 @Bernd.Defy @wilberfish and @junk031 There is a custom ROM for Defy Mini by @de-wolff
Read the previous post for installation instructions.
@de-wolff, I'm getting a blue screen, is that how it boots up?
Going to try this later. Sounds great!
Sent from my HTC Desire C using xda app-developers app
rootdefyxt320 said:
I'm getting a blue screen, is that how it boots up?
Click to expand...
Click to collapse
No, this is when you use a normal boot (with old kernel)
At this moment you have to boot using fastboot:
$fastboot boot boot.img
When I have everything more working, and the rom is smaller (at this moment it is 136M and the gapps are not even installed on it.) I will try to implement 2ndboot in the rom,
And I will also create a more user friendly way to install it.
de-wolff said:
No, this is when you use a normal boot (with old kernel)
At this moment you have to boot using fastboot:
$fastboot boot boot.img
When I have everything more working, and the rom is smaller (at this moment it is 136M and the gapps are not even installed on it.) I will try to implement 2ndboot in the rom,
And I will also create a more user friendly way to install it.
Click to expand...
Click to collapse
Contact @Hashcode to port 2nd-boot to our device. Upload our stock init.rc and he will find a 2nd-init hijack. Once, we have the hijack, we can boot into 2nd-boot. So I extracted system.tar.gz and adb pushed all the files to it and already did a fastboot boot boot.img to the phone and it gives me a blue screen. I already formatted /system how come I keep getting running out of space. Please give us a tutorial on how to install CyanogenMod to our phone. Just adjust the updater-scripts for gapps so that it flashes it to /flex and symlink it to /flex/app and /flex/lib.
rootdefyxt320 said:
Contact @Hashcode to port 2nd-boot to our device. Upload our stock init.rc and he will find a 2nd-init hijack. Once, we have the hijack, we can boot into 2nd-boot. So I extracted system.tar.gz and adb pushed all the files to it and already did a fastboot boot boot.img to the phone and it gives me a blue screen. I already formatted /system how come I keep getting running out of space. Please give us a tutorial on how to install CyanogenMod to our phone. Just adjust the updater-scripts for gapps so that it flashes it to /flex and symlink it to /flex/app and /flex/lib.
Click to expand...
Click to collapse
Thanks for your suggestions.
There is a lot to do, and it is a hobby project, so I will do those things one at a time. But when there is progress, I will keep you informed.
Maybe your problem is you are using windows?
(In that case symlinks will be expanded to the whole file)
But there is an alternative way:
Boot into fastboot and do:
Code:
fastboot boot recovery.img
adb shell 'mount -a'
adb shell 'rm -rf /system'
adb push system.tar.gz /sdcard/
adb shell 'tar -xzvf /sdcard/system.tar.gz'
adb reboot-bootloader
fastboot boot boot.img
de-wolff said:
Thanks for your suggestions.
There is a lot to do, and it is a hobby project, so I will do those things one at a time. But when there is progress, I will keep you informed.
Maybe your problem is you are using windows?
(In that case symlinks will be expanded to the whole file)
But there is an alternative way:
Boot into fastboot and do:
Code:
fastboot boot recovery.img
adb shell 'mount -a'
adb shell 'rm -rf /system'
adb push system.tar.gz /sdcard/
adb shell 'tar -xzvf /sdcard/system.tar.gz'
adb reboot-bootloader
fastboot boot boot.img
Click to expand...
Click to collapse
Bugs are Hardware Acceleration but I'm going to try the Qualcomm ICS ARMv7 Libs, wrong DPI, no settings. I will send my logcat and dmesg later.
EDIT: When I try to run a OpenGLES2.0 benchmarks, it crashes. Basically for now it's only a bootup. I suggest you to contact @cute_prince to help you to port CyanogenMod as he has ported it to HTC Pico (Explorer). Also another suggestion is that you use the codename of the Defy Mini which is Tinboost to compile CyanogenMod.
You guys are really amazing!, it won't surprise me that all the information, tutorials and videos all around the web came from all the experiments you made here. Thanks for all the time you spend, and go on guys!
Waiting for the ICS upgrade.
@cute_prince. Would you please help us to port CyanogenMod 9 to our device? As the Defy Mini has the same chipset as the HTC Explorer. I will provide whatever you need to port CM9. Thanks.
So is there a possibility of CyanogenMod on our device?
this Inc. has CWR 5.0.2 on and. 4.1.
how do u download the latest twrp on this?
my usb cable seems to be charging only.
since you seem to have gotten that far, you must be unlocked, rooted and have cwm and some alternate CM 10.0 ROM installed succesfully, right?
did this thread
http://forum.xda-developers.com/showthread.php?t=1404464
not have all the info you need about TWRP? All you are doing is replacing CMW with TWRP. I think you can do this even without a USB cable by downloading the img file to your phone's sd card via goo manager and issuing this command in the terminal app-refer to post #142 in this thread
http://forum.xda-developers.com/showthread.php?t=1404464
the steps are as follows
Flash it through terminal. It's in the Goomanager folder. Rename it as recovery.img.
Open terminal, type:
su, enter,
change directory to goo manager by typing-assuming you downloaded it to sdcard.
cd /sdcard/goomanager
flash_image recovery recovery.img, enter.
Should show a list with no errors.
CM 10.1 has not installed yet.
Is goo manager apps?
Goo play store does not launch.
tekweezle said:
since you seem to have gotten that far, you must be unlocked, rooted and have cwm and some alternate CM 10.0 ROM installed succesfully, right?
did this thread
http://forum.xda-developers.com/showthread.php?t=1404464
not have all the info you need about TWRP? All you are doing is replacing CMW with TWRP. I think you can do this even without a USB cable by downloading the img file to your phone's sd card via goo manager and issuing this command in the terminal app-refer to post #142 in this thread
http://forum.xda-developers.com/showthread.php?t=1404464
the steps are as follows
Flash it through terminal. It's in the Goomanager folder. Rename it as recovery.img.
Open terminal, type:
su, enter,
change directory to goo manager by typing-assuming you downloaded it to sdcard.
cd /sdcard/goomanager
flash_image recovery recovery.img, enter.
Should show a list with no errors.
Click to expand...
Click to collapse
Splash01 said:
CM 10.1 has not installed yet.
Is goo manager apps?
Goo play store does not launch.
Click to expand...
Click to collapse
goomanager is a separate app for downloading roms onto your phone. it;s an app that can be found on Google Playstore
you said you have 4.1 installed-what is that? is that Jellybean? or are you still on Gingerbread 2.34?
if Google Playstore doesn;t load, try clearing the data for that app.
It's JB.
i had cm7, gingerbread before JB was installed.
and
i clicked 'storage' in settings,
PB31MG.zip is in SD card.
Are apps. on this device from Gapps?
tekweezle said:
goomanager is a separate app for downloading roms onto your phone. it;s an app that can be found on Google Playstore
you said you have 4.1 installed-what is that? is that Jellybean? or are you still on Gingerbread 2.34?
if Google Playstore doesn;t load, try clearing the data for that app.
Click to expand...
Click to collapse
Splash01 said:
It's JB.
i had cm7, gingerbread before JB was installed.
and
i clicked 'storage' in settings,
PB31MG.zip is in SD card.
Are apps. on this device from Gapps?
Click to expand...
Click to collapse
what exact ROM is on the device? did you flash it yourself or did you buy it flashed by someone else?
do you have the apps Superuser and Terminal Emulator on the device? If so, I think you can just extract the recovery.img file and put it on the sdcard, then run the set of commands listed above inside Terminal Emulator.
GAPPS refers to Google Apps-the built in stuff coming from Google like Google Playstore, Email, Messaging. But on the Incredible, since it;s limited in the amount of disk space for the OS to about 260 mb, we have to use a version created by the maker of the ROM to fit in this tiny space. When you flash a ROM onto the incredible, it;s a 2 or 3 step process. In recoveryy(either CWM or TWRP)You flash the ROM, it;s associated GAPPS and then optionally, the Low space fix. You also wipe Cache and Dalvik Cache.
hi, 2months ago I root the device with cm-10.2.1-maguro all working as expected, till I liked to use voice recorder after recording stopped the app close, realize that has to do with root.
I couldnt find how to enable the app through superuser, so start to check for alternatives so I landed here
Code:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
no hope also with that, uninstalled. The problem :
through adb + eclipse I can browse the device folders when using adb root - OK
on device superuser still @ settings - OK
when on android terminal - and run the command su writes su not found!
then I red @ superSU GplayURL
Superuser access management runs through a so called "su binary". There can be only one of these at a time.
Click to expand...
Click to collapse
how I can restore the original cm-10.2.1-maguro su binary?
whokn0ws said:
hi, 2months ago I root the device with cm-10.2.1-maguro all working as expected, till I liked to use voice recorder after recording stopped the app close, realize that has to do with root.
I couldnt find how to enable the app through superuser, so start to check for alternatives so I landed here
Code:
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
no hope also with that, uninstalled. The problem :
through adb + eclipse I can browse the device folders when using adb root - OK
on device superuser still @ settings - OK
when on android terminal - and run the command su writes su not found!
then I red @ superSU GplayURL
how I can restore the original cm-10.2.1-maguro su binary?
Click to expand...
Click to collapse
Have you tried installing a rooted ROM?
Sent from my Nexus 4 using Tapatalk
nada, just download the cm desktop + cm android and made the root, nothing else.. please, advise how I can fix it..
whokn0ws said:
nada, just download the cm desktop + cm android and made the root, nothing else.. please, advise how I can fix it..
Click to expand...
Click to collapse
What recovery do you have installed?
Sent from my Nexus 4 using Tapatalk
http://www.cyanogenmod.org/
from desktop navigate to http://get.cm (download app)
from mobile navigate to http://get.cm (download app)
mobile get rooted in ~15min
thanks
so I dont know anything else..
I used to have this issue (but I didn't realise I had lost root because of an app), so I just downloaded and reflashed SU and all was good.
Download and flash from recovery: http://download.chainfire.eu/282/SuperSU/
hmm tried I got :
- Mounting
- Removing old
- Extracting files
- Restoring files
- Settings Permissions
set_perm : some canges failed
E: Error in data/media/0/CWM-SuperSU-v0.98.zip
(Status 7)
Installation aborted
-- when tried sideload ^the same with :
E: Error in /tmp/update.zip
!?
@nicknc writes :
ClockworMod Recovery v6.0.4.7
[searching..searching..searching..]
the solution is to download the latest SuperSU zip aka
http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip
there isnot error7, installed rebooted su is there!.
the final Q, is how to enable an application to have root access (when SuperSU not prompt me) ?
Marvlesz thanks!
whokn0ws said:
the final Q, is how to enable an application to have root access (when SuperSU not prompt me) ?
Click to expand...
Click to collapse
When an app requests SU, you should be prompted. If you've set a default choice, you should be able to change that from the SU app. You should also be able to change previous choices from there as well.
basically the problem is :
1-voice recorder recording but no output
2-on built-in browser in any page has 'browse' to choose a file - the open dialog never opens! (aka facebook.com upload photo or imgur.com)
how I will resolve these? googlesearch=0%