Database Develop

Trouble installing JacxHEROSki 2.1

I get a bootloop on the seconds splash screen with the little green android popping out.
I've tried wiping and reflashing multiple times, as well as repairing the file system extensions. Sometimes, however, it gets to the third "HTC" screen, but then goes back to the green android popping out.
No luck. I'm coming from Cyanogen Mod 4.0.1
If anyone has any ideas, I'd appreciate it.
Thanks.

nasman1993 said:
I get a bootloop on the seconds splash screen with the little green android popping out.
I've tried wiping and reflashing multiple times, as well as repairing the file system extensions. Sometimes, however, it gets to the third "HTC" screen, but then goes back to the green android popping out.
No luck. I'm coming from Cyanogen Mod 4.0.1
If anyone has any ideas, I'd appreciate it.
Thanks.
Click to expand...
Click to collapse
did you wipe the ext partition?
you need too

Sorry for the noob question, but how do I do that?

Here be sure to follow this or this guide.
i wuld recommend u do the manual partition and only delete the ext2 partition and remake it for a lot more simpler process i.e only rm 2 n rm 3 after print so that your sd card files are not deleted

Dare{D}evil said:
Here be sure to follow this or this guide.
i wuld recommend u do the manual partition and only delete the ext2 partition and remake it for a lot more simpler process i.e only rm 2 n rm 3 after print so that your sd card files are not deleted
Click to expand...
Click to collapse
yup thats how i did it, but if you dont want to go through all that, you can follow these steps: http://forum.xda-developers.com/showthread.php?t=535797
1.) Turn on the phone holding the home key and power to boot. Attach the phone to your computer via usb.
2.) Wipe your phone from the menu in cyanogen
3.) Open console ALT + X and enter the following commands. Press "Enter" after each line. This wipes the ext partition.
mount -o rw /dev/block/mmcblk0p2 /system/sd
rm -r /system/sd/*
or this in adb
adb remount
adb shell
rm -r /system/sd/*
Click to expand...
Click to collapse
Note: this will delete your apps on your sd as well as userinit files or w/e was there
Code:
to backup your ext partition to your current directory: adb pull /system/sd/ %CD%\sdbackup
to restore back to sdcard: adb push %CD%\sdbackup /system/sd

the easiest way to wipe ext3 partition is in the recovery console with
Code:
mke2fs -j /dev/block/mmcblk0p2
that is all. one command. and all is gone.

[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.

[Q] Accessing /data if CM9 won't boot

How can I access the /data/ partition?
I was using the touchpad, installed some apps like teamviewer/unified remote/xbmc from the market, and all was going well and then for no reason the tablet froze, CM9 just stopped responding. So I rebooted it (holding the home button and power button was the only way to get it to do anything) but it's stuck at the Cyanogenmod boot animation. It's been on that animation for 5-10 minutes, so I rebooted again, went into clockworkmod and reflashed the latest nightly and gapps. I then rebooted, android booted up, said it was upgrading/optimizing 77 something apps, then it said it was starting the apps, and then it froze at that point, wouldn't proceed. I then reboot and am stuck at the boot animation again. My best guess is that one of the apps I installed is hosing it. I plugged the usb cable in and normally during the boot animation of my phone I can adb logcat but I can't seem to adb detect this device during boot animation. Windows see's it as a MTP device but no filesystem comes up in my computer. So adb logcat and adb shell so I can get into /data/app to wipe out the last few apps I installed won't work, but on my phone I can also adb shell in from CWM. So I rebooted into CWM but when I connect the cable to the laptop it still doesn't see it as an Android ADB device. No adb shell. Not like my phone at all.
So back to my original question, short of wiping /data from CWM, is there anyway for me to get at /data/app to delete some files? I'm curious what's causing this.

You can do an and pull from clockwork mod or have you tried mounting it on the computer from the clockwork mod options?

I've mounted before in clockwork but only sdcard, so that i can put a zip on it to flash. Can you also usb mount the /data partition?
Sent from my SGH-I777 using XDA

If you can reboot into WebOS, I know a way you can mount it and grab what you need.
Boot into WebOS, and connect your tablet to your PC. Then start up Novaterm (C:\Program Files\Palm, Inc\terminal\novaterm.bat). Connect to your tablet.
From there, you'll be at a root prompt. This is good. Type the following commands:
- mount /dev/mapper/store-media /media/card
- mount /dev/mapper/store-cm--data /media/hdd
- cd /media/hdd
- mkdir /media/card/cmdata (this will make a backup folder for you)
From there, you can use basic linux commands to copy files from your data partition to your media card. The ones you should need (forgive me listing the extra commands, even if you know them):
- ls (LS) will give you a directory listing
- cp -r <Folder> /media/card/cmdata (this will backup whatever folder you wanna backup to the cmdata on your card)
- rm -r <folder> (this will remove whatever folder you wanna remove)
- rm <filename> (this will remove whatever file you wanna remove)
I just tested this method, and it allows you to back up whatever you want, as long as you can get into your /data partition. You can do whatever you need to do. Just be careful you don't remove something you don't have to.
Hope this helps you, mate. If so, hit Thanks, if not, drop me a PM and we'll discuss other options.

glitchsys said:
I've mounted before in clockwork but only sdcard, so that i can put a zip on it to flash. Can you also usb mount the /data partition?
Click to expand...
Click to collapse
Yes, you can, but you can only read it from a Linux PC. A Windows system will not be able to access the partition, because it is an ext3 filesystem.
You can also use the "USB mode" used to install CM, but it will run into the same problem. Without Linux, you will not be able to access files.
I would clear the cache, that usually seems to solve these kind of issues. (Of course it could also mess it up further...)

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.