This is my first attempt towards creating a zip file to update the kernel using Clockworkmod Recovery (v126.96.36.199) on a Galaxy Nexus phone. My repeated attempts to flash the boot.img to the phone failed. I checked the logs to determine the cause of problem and I'm getting the "can't find boot partitionscript aborted" error that is causing the update to fail.
i'm having trouble to boot my desire S..i tried to install some new roms, but something web wrong: usualy i had the following partitions:
/dev/block/mmmblck0p25 -> cache /dev/block/mmmblck0p26 -> system /dev/block/mmmblck0p27 -> data
al of them ext3, but now if i log in with adb i'm able to mount anoteher partition /dev/block/mmmblck0p28 -> witch in some point was montend on /system/lib and is ext4
now if i adb shell: parted /dev/block/mmcblck0 i becom the error: Can't have a partition outside the disk.my asumtion is that some rom flashing wrote somting were it shoudn't. if i format using fastboot, (i'm not sure if this is posible www_ omappedia.com/wiki/Android_eMMC_Booting ) i'm preaty sure i'm formating also x-load and bootloader.
Not so long ago I flashed a custom rooted ROM. After this I realized that I forgot to save some important app configs (im history, notes). As far as I know, Android uses ext4 filesystem on its root partition. Is there a way to perform undelete or any other method to try to recover deleted files? Searching the forums gives some results of repairing data on internal storage, but I guess the user data space is meant, not the root. My device is Huawei U8850 Vision, Android version 4.1.2.
I try to understand android boot sequence on my JB (under CM10). I found some docs and there should be specific partitions (boot, recovery, system, cache, data).
My understanding of the boot sequence is now:
A) normal boot: 1) Power ON -> 2) bootloader -> 3) boot-partition where i flashed the kernel aka boot.img -> 4a) system-partition with the OS (libs, UI, etc) where i unpacked over CWM my customROM.zip -> 4b) data-partition, where i unpacked google-apps.zip and installed all the apps -> 4c) cache-partition with user data
B) recovery boot (adb reboot recovery): 1) Power ON -> 2) bootloader -> 3) recovery-partition with CWM where i may unpack all the .zip stuff to proper partitions, or restore from sdcard, etc.
Is this correct? I wonder, because i didn't installed CWM into recovery-partition. It cames from install of CM10 (fastboot -i 0xfce flash boot boot.img), so it must be in boot-partition and not in recovery?
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
# ls -lha /sdcard/clockworkmod/backup/2012-10-04.18.49.55/ d---rwxr-x 2 system sdcard_r 4.0K Oct 4 18:56 . d---rwxr-x 3 system sdcard_r 4.0K Oct 4 18:49 .. ----rwxr-x 1 system sdcard_r 1.6K Oct 4 18:54 .android_secure.vfat.dup ----rwxr-x 1 system sdcard_r 54.6M Oct 4 18:55 cache.yaffs2.img ----rwxr-x 1 system sdcard_r 360.2M Oct 4 18:53 data.yaffs2.img ----rwxr-x 1 system sdcard_r 212 Oct 4 18:56 nandroid.md5 ----rwxr-x 1 system sdcard_r 214.6M Oct 4 18:51 system.yaffs2.img #
So, i think i didn't understand the boot sequence and partition schema corectly.
I am running rooted stock Android 2.3 on LG E405 (no working 4.x ROMs exist for the device)
I have two questions:
1) What is the shell command to manually make android allow the PC to mount androids' (internal) partition as USB-drive? (I cannot think of right keywords to google this one up - )
2) How does android determine which partition is which (i.e. which one to remount for the PC when connecting in "USB storage" mode), beside vold.fstab and init.rc? On android 2.3 that info is not in "framework-res.apk", so where is it? In the partition table itself?
I had switched data partition with internal sdcard partition.
Here's how: Phone had a very small "/data" partition on /dev/block/mmcblk0p21 and large internal "/sdcard" partition on mmcblk0p20
So I reformatted mmcblk0p20 (ex-sdcard partition) into EXT4 and mmcblk0p21 (ex-data partition) into FAT32
Then I changed init.rc to mount mmcblk0p20 as /data type EXT4 and mmcblk0p21 as /sdcard type VFAT (mounting /sdcard was commented out in stock init.rc for some reason). This required modifying my boot image.
I have also set correct partition number in vold.fstab:
[#]dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.3/mmc_host[/#]
So basicly I now have a large /data partition and small internal /sdcard. I'm able install up to a gigabyte of APKs and it works fine.
However, when I connect to my PC via USB into "USB Storage" mode, the phone seems to still try to unmount what was previously sdcard partition (/dev/block/mmcblk0p20), instead of what is NOW an sdcard partition (/dev/block/mmcblk0p21) I can still send files to the phone via wi-fi and ADB, but the ability to mount it directly would be nice.
If I accidentally select "erase internal sdcard" from storage menu, that will also most likely erase what is now my /data partition, softbricking the phone. The "factory reset" option will probably only corrupt the sdcard.
I'm have been trying to create a second partition on my sd card using miniTool Partition Wizard.But in the end I never get a 2nd partition but just a smaller first one.My approach is as follows:
insert empty SD card (FAT32, 4GB) open miniTool Partition Wizard right click on SD card - "Move/Resize" choose 1gb for unallocated space after - click ok right click on 2nd partition and choose "create" create 2nd partition with FAT32/Ext2/Ext3 (tried all options already) and "primary" and Cluster 4KB - click ok Apply
Afterwards my SD card is still shown as one partition, but this has just 1gb less capacity then before.Neither the Wizard nor the phone detects the 2nd partition then.
I have a new ace 3 LTE S7275R. I tried installing CWM recovery found here: URL....I tried with odin 3.07 and 1.85Every time, odin shows success, but when trying to boot into recovery, the phone gets stuck at "recovery booting...."The phone is otherwise working...getting CWM to work? how can I return to stock recovery at least?
So I just got my S4 rooted and everything seems correct. I then installed Rom Manager so I could start demoing some of the ROMs out there. Went through all the steps to flash Rom manager as the recovery but I cannot get my recovery to go to CWM, it just keeps going to the stock android recovery. I have googled the crap out of this and am coming up with nothing. in fact I have written several android apps but this just does not work.
My device is a Verizon Samsung S4 model SCH-I545 running android version 4.2.2 Kernal: 3.3.0-690088se.infra@S0210-13#1
I am pretty sure I have root, as if I open emulator and SU It goes $ to #. I am running build "2.19.605.1 CL123435 test_keys" and everything seems stable. It's funny that I'm running 2.1 because I never flashed the ROM, I couldn't get past recovery partition set-up.
When I try to press power+up volume all I get is the yellow triangle exclamation point with the android cartoon. This is where I stopped on my first attempt. When I powered the phone back up, it's running 2.1.
Can I re-download the recovery partition .zips and re-flash the root ROM to start all over? I'm thinking my DL's of some of the recovery images may have been corrupted. I'm thinking since I have root, re-flashing the root ROM shouldn't hurt anything right?
Kinda green here, it took me a long time to realize why there a bunch of different files with the same name, but not the same contents (pmb). I'm assuming that's the only filename that the boot loader will recognize.
I feel like such a moron for not knowing this. I used the one click method for rooting a week or so ago, and im currently running kaos froyo v30. I'm looking at running xtrROM188.8.131.52 and it says in the installation instructions that "YOU MUST HAVE A ROOTED PHONE WITH THE AMON_RA RECOVERY PARTITION"
I don't like how Samsung gives us a nice 250gb drive but chunks it into two ~100mb partitions with a little left over for the hidden recovery one. I want to keep the recovery partition but have the remainder in one nice big drive. I tried out Easeus Partition Master but that doesn't seem to allow me to do what I want. Does anyone have any suggestions on how I could do this?
i wanted to upgrade my galaxy s2 g i9100 and since that time i hve not been able to use the phone again.
i tried rooting it but after that i can not boot recovery anymore all that comes on the screen is SAMSUNG GALAXY SII with a yellow triangle.even if i press the up volume key+home key+power nothing happens.
I have a Karbonn A6 phone given to me by my friend because it was locked. It's asking for gmail user/pass but he doesn't have it. I tried to boot into recovery mode using Power+Volume Up button but all I get is a white triangle with an exclamation mark in it. I can't seem to go beyond that. USB debugging was perhaps not enabled unless it was enabled by default. There is no camera button, only power and Volume Up/Down. What do I do?
I just need to get this phone working somehow. Is there a way to use a computer and a USB cable to get it running?
I have tried using rom manager, holding the power button and selecting reboot recorvery, and by holding the power button and x. Each way I see the white m twice then the phone just boots up. I am running cm7 7.0.3. I have only had the phone for a week, I am trying to wait for the vigor. It worked fine Friday when I flashed cm7
I'm on a Galaxy S2 running Gingerbread 2.3.4, my baseband version is I9100XXKI1 and my kernel version is 184.108.40.206-I9100XWKH4-CL487028root@DELL136 #2
Using Odin3 v1.85 and S2 Root. (Superoneclick kept freezing on me)
My aim is to install Cyanogenmod 7.1.
So far I started off by trying to flash it with XWKDD Insecure, which I believe is wrong? However after rooting it, I installed ClockworkMod Recovery, downloaded the ROM and tried installing it - which is where the problem started - I kept getting the error in recovery mode 'Invalid whole-file signature'.
It just wouldn't boot in to ClockworkMod Recovery.
So after some digging around I managed to find a file to flash to my device for the CWM Recovery mode, tried it, and it worked. However, I still couldn't install Cyanogenmod from my SDcard.
I tried it a few times, wiped/formatted a few times and ended up getting my device stuck in a bootloop.
So, I've managed to get it out of the boot loop, and started fresh...
I flashed it with XWKH4 Insecure, unrooted, rerooted etc. I've downloaded CWM again, downloaded the Cyanogenmod again, tried installing it, and once again it's gone back into Androids recovery and failed to install because of the 'whole-file signature' and failing to verify it.
I did post this in Q&A as well, however it doesn't seem to be as popular a forum as this one, I'm not really looking to wait for days for a response.
I rooted my phone using Z4 then used Titanium Backup for backing up and then recovery. Now while rebooting into recovery mode the phone took a long time in booting so I removed the battery and tried to reboot. But the phone makes the signature sound and after that only displays the following word 'spice'.
I flashed Omega rom today for my galaxy note 2. It uses Aroma installer which i think could be the problem. Basically I cant boot into recovery. The rom is also very laggy where people on its development thread are praising it stability! The device will stay on the 'Samsung galaxy note II gt17100' bootscreen when i try to.boot into recovery.
i have a cheap alwinner a13 tablet (simmtronics xpad x720) from indian manufacturer. It is stuck at cwm recovery it countineously boots to cwm after restart.I have no backup stock rom. But i can sideload zip from adb or external ed. And not able to mount internal sd or wipe cache.
ok, so I put the PB31IMG file on my sdcard, and the dinc_ota. I changed dinc_ota to update. (I did not name the file update.zip.zip) I powered down, I entered bootloader, and it loaded the PB31IMG and whatever. then I hit volume down and selected recovery. this brought me to clockwork recovery. I noticed the isntructions said to boot into STOCK recovery. well, I like a dummy ignored that and tried to apply the update.zip thru clockwork.
This is what I got:
So, is this because I tried doing it through clockwork recovery? is it because I didn't apply the first OTA update we got? what does that mean exactly anyways? is it saying I need to install the leaked froyo ROM, and then update the radio? How do I boot into stock recovery and not clockworks recovery? does this count as applying the update.zip once, meening if I do it again I'll brick my phone? should I sell this thing and get a samsung flip phone because I'm too stupid to own a Dinc?
I have an Android tablet (Diablotek D2-721, very cheap I know, but it serves its purpose) that is stuck in a boot loop. The real problem here is that this device apparently does not have any sort of recovery mode and being in a boot loop means it does not get recognized by ADB or any firmware flashing software.
I researched all day yesterday perusing forum after forum but almost every single solution requires booting into recovery.
My EVO 3D (Sprint) is rooted and is on android version 2.3.4 and I believe it's not an android official release, this is how it was given to me. I'm trying to install CM10.1
I installed ClockworkMod 220.127.116.11 using ROM Manager and since then I haven't been able to boot into recovery mode. I can get into bootloader but not recovery. I've tried powering it on with the volume button down, using the recovery reboot option, and tried using "Reboot into Recovery" in ROM Manager, but I keep seeing the same thing. It boots with the HTC logo then goes black then at this point i believe I should be seeing recovery mode but instead I see the HTC logo again and then it just boots like normal. Is there something I did wrong and is there a way to get recovery to work again?
I've been trying to track down a solution to my problem, but every solution seems to contain a "Boot into recovery mode" line which I cannot do. I attempted to update a rom that I had installed, and now I am stuck at the google logo with the unlock icon. I cannot boot into recovery with the volume keys and power, and now I cannot figure out how to use adb to recover the phone, as it cannot recognize it.
Is there anyway I can access this phone while it is in this state from my computer and recover it somehow. I tried following leads that people have posted in other threads, but it seems like most suggestions involve "Use adb", yet every adb tutorial involves the phone being in recovery mode. I've tried to uninstall and reinstall drivers via Wug's Toolkit, but when I plug my phone in, I am not able to install the drivers properly. I try to run adb items through the console, yet it does not recognize my device.
Is there anyway to install the necessary software I need and recover my phone while I cannot get past the google logo screen?
I Have An Ainol Novo 7 Crystal Tablet..(Rooted With TWRP Recovery&Cyanogenmod 10.1 Installed).It Was Working Fine Till This Afternoon But I Don't Know What Happened Next..I Turned Off My Device And I Tried To Turn It On Again After Some Time But It Wasn't Booting...
I Don't Even See Any Boot Animation Or Android Logo That My Device Used To Display While Booting,The Screen Of My Device Lights Up Though..And I Can't Even Boot Into Recovery (I Have TWRP Installed),When I Try To Boot Into Recovery I Don't See The Android Logo That I Used To See But The Screen Of My Device Lights Up And Doesn't Boot Into Recovery.. I Tried Removing TWRP Recovery From My sd card And Booting Into Recovery But The Screen Lights Up For Like 5 Seconds And Then The Light Goes Off..