Database Develop

[Q] Removing Android System Recovery <3e>

I have a verizon Samsung Galaxy tab. I would like to use clockwork recovery. The tab is rooted and I used ROM manager from the marketplace to flash the recovery for a Samsung Tab (Verizon). When I flash the ROM everything is successful. However, when I boot into recovery the Android System Recovery <3e> shell loads which doesn't allow nandroid backups etc... all the neat recovery tools that come with clockwork recovery.
I searched around the forum and saw a thread titled how to replace Android System Recovery with a Custom ROM. These were the commands
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
I went into abd shell I tried the commands but by the time I got to the third line I keep getting permission errors before I can even finish typing the command. I cut and paste the command string from "mount-->" thinking I just wasn't typing fast enough and it still doesn't work.
Is there another way to remove the Android system recovery so that ROM manager will work properly?

Have a look at installing boushh's kernel, it probably going to be the best option around for you.
Sent from my X10i using XDA App

I don't know what that is?

I have also same problem ı tryed many flashes ı coudnt fix it yet.if you allready fixed could you please share thanks.....

CWM 3.0.1.0 issue and solution

make sure to read: http://forum.xda-developers.com/showthread.php?t=971197
the other day I realized that I did not have the OC kernel installed for CM7, so decided it was time to get that on there. I was unable to boot into recovery via ROM Manager or manually (using n+power). ROM manager was telling me 3.0.1.0 was installed, so I was a bit confused about why this was happening. I tried re-installing CWM via adb, that was a no go as well.
I then resorted to irc for help, people explained the proper way to use the key combo and then told me I was lying when I told them I didn't have the "touch the power of reading" splash
video of nook booting: http://www.youtube.com/watch?v=PGScwmoS7HU
so after a bit more poking and questions, found out the splash is within u-boot.bin, and somebody suggested I pull u-boot.bin from stock 1.1 image and push that to /boot.
Code:
1) download and unrar http://www.megaupload.com/?d=D7GFVHCQ
2) adb shell busybox mount / -o rw,remount
3) adb shell busybox mkdir /boot
4) adb shell busybox mv /boot/u-boot.bin /boot/u-book.bin-bak
5) adb push u-boot.bin /boot/u-boot.bin
6) adb shell busybox umount /boot
PROBLEM SOLVED. can boot into CWM after replacing u-boot.bin. I think this was related to attempting to format sdcard within CM7 on nook

So I have the same problem ... "Loading ..." screen and inability to boot into CWM after flashing with ROM Manager.
However your instructions are missing a step. You have the user creating the /boot directory with mkdir but not mounting /boot ... but at the end you have us umount /boot.
I sort of remembered this process from when I installed the HC pre-release, so I found my old bookmark. Following is your instructions with the missing step. Doing this made CWM load for me using power+N
Code:
# download and unrar http://www.megaupload.com/?d=D7GFVHCQ
adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
[i]adb shell mount /dev/block/mmcblk0p1 /boot[/i]
adb shell busybox mv /boot/u-boot.bin /boot/u-boot.bin-bak
adb push u-boot.bin /boot/u-boot.bin
adb shell busybox umount /boot
PS. I'm guessing this still isn't the RIGHT way to fix this issue, as I still can't get the reboot to recovery option working (I'm using CM7 nightly 39). However search function on the forums is offline, I'm very tired, and I'm about to go on a road trip early tomorrow so I'm not going to keep trying to fix it right now. If someone wants to post better info to get CWM 3.0.1.0 and ROM Manager working better for CM7 I'd love to see it. But I got my ALSA update installed so I'm happy for now

I've not been able to use Reboot into Recovery (from holding the power button) for a while now. However, the option from ROM Manager usually works, as does holding the n key while booting.

cannot root S5830

Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.

simmo2302 said:
Model Number - GT-S5830
Android Version - 2.3.6
Baseband version - S5830XWKT3
Kernel Version - 2.6.35.7-perf-CL787041 [email protected] #1
Build Number - GINGERBREAD.XWKT7
Virgin Galaxy Ace S5830.... i cannot root it.
so far i've tried..( This Guide )
universal_gb_root_v25.zip / universal_gb_unroot_v9.zip
and...
upd_1.zip / unroot.zip
and.....
AceGingerRoot.zip
also tried superoneclick which cannot root it on any setting.
what have I overlooked ?
i had planned to root it, install CWM recovery and make backup of the Optus carrier rom, then instal custom rom.... maybe i should download australian rom from sammobile and flash that replacing the current optus carrier one.
also when i load into the default android system recovery (Pwr + home key), down the bottom there is a message in yellow saying...
-- Appling Muti-CSC --
Can't access to '/system/csc/OPP/system'.
i have no idea what that means.
Click to expand...
Click to collapse
If your phone is unlocked try to flash a fresh stock rom via Odin, maybe you don't have enought free space in your system patition

cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....

simmo2302 said:
cheers i'll try that. freeing up some space.
also i dont know if it is locked to Optus (the carrier) or not, does it matter if it is ?
if so i might have to look into that....
Click to expand...
Click to collapse
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.

simmo2302 said:
hmmm... well aparently it IS locked to the carrier Optus network. - i dont kno how/if that effects it being rooted or not.
i tried to root the device with the gb_universal_v25.zip again, and then without rebooting installing CWM 5.0.26.
the CWM is there now. but still no root.
Click to expand...
Click to collapse
Do you have thinkdroid installed?

Viper The Ripper said:
Do you have thinkdroid installed?
Click to expand...
Click to collapse
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.

simmo2302 said:
OK, just had a terrible time with this, but i may have got it now..... (have tried to do as much research myself, so i dont be a noob and ask every noob question under the sun)
i ended up getting the crappers with it, so in the menu settings i did a factory reset.
and... got stuck in a boot loop.....
rebooted into recovery.. wiped data/factory reset, wiped cache, wiped davlik aswell.
rebooted, and still boot loop.
put Ace into download mode (Pwr +vol dwn + home), ran Odin multidownloader 4.38 and used proper firmware (one package) from sammobile and coopers_v1.0.ops, and reflashed stock FW onto the Ace.
successfully passed Odin, rebooted.. (cant remember if it worked right away or if i had to do another wipe session).... but got it working again...
went back into recovery (reverted back to stock now)... tried rooting with universal_gb_root_v25... didnt work... unrooted with universal_gb_unroot_v9.
tried for ages to find universal_gb_root_v26 but couldnt find a site that didnt want me to do a survey and give my mobile number... so i found (somewhere) a universal_gb_root_v25b.
rooted with that.... rebooted.. and checked with 3 different SU / root checkers... and each one says Root is Good ! Yay !
so now i'm going to go back and put on ClockworkMod Recovery 5.0.2.6 and then try some custom roms
still undecided which one to use. (ideally looking for one, lean, fast and stable considering how restricted the Ace is)
cheers for all your help.
Click to expand...
Click to collapse
I'd tell you that if you didn't have enough space on the system partition, maybe you could try flashing THIS before rooting your device and then you'll try flashing root again so...

Try The Ultimatum
Sent From my GT-S5830.
Current Rom-The Ultimatum
Kernel-Fire OC Kernel
Audio Manager-BEATS
Hit Thanks you unthankful $*%$&. Its There For A Reason.

Samsung Galaxy Ace [GT-S5830] root method (Optus branded units and possibly others)
I tried many methods, and none would work with my Optus branded S5830. I assume it was partly due to having less than 1MB available on the /system partition. After some perseverance, it now has root, here was my method, hopefully it can help others.
Some files mentioned in this are available here: http://goo.gl/6XlwEx
1. Install Samsung USB drivers: SAMSUNG_USB_Driver_for_Mobile_Phones.exe
2. Install and setup (for atleast your android version) the SDK from Google (http://developer.android.com/sdk/index.html)
3. Ensure that the platform-tools (or which ever folder contains adb.exe) is in your system path variable (google it).
4. Put custom recovery image on sdcard: recovery-clockwork-5.0.2.6-galaxyace.zip
5. Turn off device, and boot to recovery (home + power)
6. Flash recovery-clockwork-5.0.2.6-galaxyace.zip and reboot
7. Turn off device, and boot to recovery again (home + power)
8. From a command prompt, run 'adb shell' it should drop you to a shell with root privileges (#).
Code:
> adb shell
#
9. Mount the '/system' partition from the custom recovery (mount partitions)
10. Make some room on your '/system' partition, delete Skype, Think Office, etc. You will need to do this as the bloatware has left no room for the su binary and SuperUser.apk
11. To get rid of skype or Think Office, from the command line type the following and then press enter.
Code:
# rm /system/app/Skype.apk
# rm /system/app/thinkdroid.apk
12. Extract universal_gb_root_v25.zip to a folder, and open another command prompt at .\universal_gb_root_v25\system\xbin and type the following commands:
Code:
> adb push busybox /system/xbin/
> adb push sqlite3 /system/xbin/
> adb push ssh /system/xbin/
> adb push su /system/xbin/
> adb push ..\app\Rootvalidator.apk /system/app/
> adb push ..\app\Supersu.apk /system/app/
13. Go Back to you 'adb shell' command prompt, and type the following to confirm the files have been pushed (you should not get a 'No such file or directory' message)
Code:
# ls /system/xbin/su
# ls /system/app/Supersu.apk
14. Set file access permissions (change mode) with the chmod command
Code:
# cd /system/xbin
# chmod 6755 su
# chmod 755 busybox
# chmod 755 sqlite3
# chmod 755 ssh
# chmod 644 /system/app/Supersu.apk
15. Now also copy the files you pushed to /system/xbin to /system/bin
Code:
# cp su /system/bin/
# cp ssh /system/bin/
# cp busybox /system/bin/
# cp sqlite3 /system/bin/
Code:
# reboot
The phone should reboot as normal,
17. Once in turn on USB debugging (google it). Go Back to you 'adb shell' command prompt (which will have quit the shell after the reboot) and type:
Code:
> adb shell
$
18. Note that this time there is likely a $ prompt, if so, enter the command 'su' and hit enter. SuperSU should pop up on your device asking for su rights, say yes. If you get the # prompt, you are now rooted.
Code:
$ su
#
19. As an alternative to steps 17 and 18, (after the reboot, before turning on USB debugging), you can just open Rootvalidator from your app drawer to test for root privileges. You will also notice the SuperSU and cwm_recovery apps now in the app drawer too.
If it hasn't worked, make sure you've followed the steps correctly, you can safely repeat them, or play with the file's (busybox, sqlite3, ssh and su) user owner/group owners so they match most of the the other files in '/system/bin' and see if it helps. USe 'ls -l', 'chown' and 'chgrp' (again, google their usage)
ie. as an example, below shows that 'busybox' is owned by user 'root' and group 'shell', to change the group ownership to root, i would type 'chgrp root busybox' at a root (#) prompt.
Code:
# ls -l
-rwxr-xr-x root shell 2007456 2008-08-01 22:00 busybox
-rwsr-sr-x root root 311872 2013-12-08 09:09 su
- The End -

I think you should you should flash a stock rom via odin.

CyanogenMod installation 12.1

Hi all, im here because i have some problem about install CyanogenMod of this tread:
http://forum.xda-developers.com/xpe.../rom-cyanogenmod-12-neo-s-homebuilds-t2984988
i hade a Xperia T, with 4.3 stock, with root, followed thsi http://forum.xda-developers.com/showthread.php?t=2798411=2333577
then i unlocked my botloader, following a italian guide by "Unlock SE xperia bootloaders", ask to Sony the hey for unclock, and all work fine.
Downloaded cm-12-20151108-NIGHTLY-mint with Gapps open_gapps-arm-5.1-pico-20160226, and pun in my microsd.
i have:
(1) Boot into TWRP recovery
(2) Do a factory reset and wipe system partition
(3) Flash latest ROM zip, but no Gapps (I'd do it later, first I wanted to see if it was loaded right to the Rom)
Reboot, configured cell phone, everything ok.
Then i try to follow step about resize partition, so i reboot phone, press "vol down", and my xperia boot into a "Cyanogen recovery", and not in the PhilZ Touch Recovery.
So I made some tests, and i have install TWRP by APK file, install ok, so i can go inside TWRP at the boot.
krasimiretov tell me to do that:
1. Install build from 08-01-2016(final)
2. You need to fastboot boot.img . There is no cyanogen recovery its TWRP. You must have done something wrong.
3. No towelroot is needed. After installing the build and flashing supersu from recovery phone is rooted.
4. You can do that with TWRP recovery no Philz needed.
so i have downloaded 08-01-2016(final), try to zip with TWRP but not able https://www.dropbox.com/s/n6do3ucbx8oju5a/2016-02-27 12.08.52.jpg?dl=0
i try to fastboot boot.img, by flashtool, istall it following this http://forum.xda-developers.com/showthread.php?t=1963961 but at the reboot xperia still "tunr off" afeter logo SONY, i should reboot (vol up+on for 10 sec, go to TWRP and reflash cm-12-20151108-NIGHTLY-mint for work again.
I am tempted to start all over from the beginning...but i shoud unlock again bootloaders, use unlocked bootloader, than i can, maybe, reflas ftf, right?
sorry if it's a little confused, but I do not know how to install the latest ROM, to be able to resize the partition

ok ..ok... i try again and now have work fine...
i just arrived to the Reboot, afetr install rom, gapps and update superSU, but screen is "stuck" at the recovery...is freeze there...i can reboot manually?

done!
redone the procedure,
I was wrong to flash the boot.img :angel:

So its working fine now ?

yep! work!!
but i have a little problem for resize...
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
say "su" not found:
/ # su
Sh: su: not found

Flash latest SuperSU from here: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
Did you flash that in TWRP ?

yea... anyway im trying again... (It has a bad sensitivity TWRP )

nothing... "SU" dont work, but T work without "problem" ... i just have some lag and some closing's applications...
and this error after rebooting:
https://www.dropbox.com/s/tb4p3oykwhwglof/unspecified.png?dl=0
i would like try the latest UNOFFICIAL by Neo ... where i can download it? its cm-12-20150405-UNOFFICIAL-mint ??
maybe better version 12

ok..i have try install cm-12-20150405-UNOFFICIAL-mint, replace boot.img with flashtool, twrp change version, like this https://upload.wikimedia.org/wikipedia/commons/f/fe/TWRP_2.7.0.0.png but when i try install the .zip, i received a error ... so i try to install the cm-12-20151108-NIGHTLY-mint, ok without error, but now ROM have loop on CM logo ...

nevermind... I was able to do everything alone ...
I do always panic
buti have always the messa
https://www.dropbox.com/s/tb4p3oykwhwglof/unspecified.png?dl=0ge

Its from the google apps. Why are you unstalling CM12 when there is more optimized and up to date CM12.1. And i write again. READ EVERYTHING IN OP CAREFULLY.

krasimiretov said:
Its from the google apps. Why are you unstalling CM12 when there is more optimized and up to date CM12.1. And i write again. READ EVERYTHING IN OP CAREFULLY.
Click to expand...
Click to collapse
i have unstalling the latest 12.1 (cm-12.1-20160108-UNOFFICIAL-mint.zip), and use Build CM12 UNOFFICIAL by Neo - 5/4/2015, because 12.1 was full of lag, and some app freeze and quite without message...
Now Xperia T is more fat without lag ...
Anyway i can install other 12.1 ... except the last one that is not working well ... what would you suggest me about, version 12.1?

Ok, i have try again with this version:
cm-12.1-20160108-UNOFFICIAL-mint
open_gapps-arm-5.1-pico-20160301
BETA-SuperSU-v2.68-20160228150503
Follow always the istruction:
Flash the boot.img from ROM zip via Flashtool (use Fastboot mode)
Boot into TWRP recovery
Do a factory reset and wipe system partition
Flash latest ROM zip (check "Downloads" section)
Flash suitable GApps for CM12.1 or CM12
Flash latest SuperSU from here: Link
Reboot
i have always the same message when boot the phone about SETTINGS

nosadello said:
i have always the same message when boot the phone about SETTINGS
Click to expand...
Click to collapse
We all have that message, that's bug about CM Theme, and It's nothing to worry about.

nosadello said:
yep! work!!
but i have a little problem for resize...
13. Reboot
14. Enter the following terminal commands to fix storage permissions:
su
chmod 777 /mnt/media_rw/sdcard0
chown 1023:1023 /mnt/media_rw/sdcard0
chown -R 1023:1023 /mnt/media_rw/sdcard0
say "su" not found:
/ # su
Sh: su: not found
Click to expand...
Click to collapse
i should give this command on recovery or enable terminal on androd??

Cannot uninstall/install framework after backup restore

Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas

Lord Spectre said:
Dear community,
I installed xposed using the following adk: XposedInstaller_3.0_alpha4.apk then flash, from recovery, the framework for my Oukitel K6000 Pro (Android 6.0): xposed-v86-sdk23-arm64.zip
All worked fine until I have to restore a backup from recovery (backup taken before I flash the framework).
Now, Xposed cannot see the framework, so I tried to uninstall it using xposed-uninstaller-20150831-arm64.zip always from recovery. The uninstallation seems goes ok, so I reboot the device, enter again into recovery to flash again the xposed-v86-sdk23-arm64.zip
Unfortunately I got an error during install process:
chown: /system/bin/dex2oat.orig.gz read only file system
or
cp: can't create '/system/xposed.prop' File esists
And the installation stop there.
Could someone help me to reinstall the framework and come back to working status?
Thank you
Lucas
Click to expand...
Click to collapse
Try clearing art/dalvik and cache then reboot directly back into recovery and flash Xposed again
Sent from my SCH-R220

Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system

Lord Spectre said:
Thank you for reply mattzeller, unfortunately, after cleaning art/dalvik and cache and reboot directly into recovery to install sdk I got the same error:
chown: /system/bin/dex2oat.orig.gz read only file system
Click to expand...
Click to collapse
Try mounting system as read/write in recovery before flashing
Sent from my SCH-R220

mattzeller said:
Try mounting system as read/write in recovery before flashing
Click to expand...
Click to collapse
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!

Lord Spectre said:
I believe you mean from terminal, could you please share the command to do that? Thx!
However I see from recovery log, during uninstall/install processes:
Mounting /system and /vendor read-write
So, packages already tried to mount system... Maybe fails, I don't know!!!
Click to expand...
Click to collapse
In recovery open terminal :
mount -o rw,remount /system
Then try to flash Xposed
Sent from my SCH-R220

DAMN!DAMN!DAMN! This is what I done on terminal:
# mount -o rw,remount /system
Try to flash xposed-v86-sdk23-arm64.zip
Got: cp: can't create '/system/xposed.prop' File esists
Then from terminal:
# rm /system/xposed.prop
rm: can't remove '/system/xposed.prop': Read-only file system
At this point I don't know how can I proceed. Maybe flashing stock rom, then install framework from recovery, and then restore backup

Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.

Lord Spectre said:
Just to inform that I solved reflashing stock rom, recovery TWRP and SuperSU... Then flash again the Xposed SDK. Unfortunately I cannot use the TWRP backup, and I had to configure my phone from scratch.
Click to expand...
Click to collapse
Sounds like something in your backup got screwed up I would suggest deleting that back up once everything is set up and redoing it
Sent from my SCH-R220