Hello,
I don't know how, but I managed to end up with a system that has /dev/block/mtd* wiped clean. All the partitions contain valid yaffs2 file systems, but all they contain is a lost+found directory.
This includes the recovery partition, which I guess is the reason why I am not able to enter recovery or download mode anymore. No matter how I boot, the phone display only shows the cyanogen^mod splash screen.
I still have root access to the device using adb shell, and I can call flash_image and mount /sdcard as well as /dev/mtd*.
How do I best recover from this situation?
Can I download the missing contents from somewhere? I wasn't even able to find a suitable rescue image, even the clockwork recovery images from koushikdutta.com come as .zips which have to be properly installed.
And is it sufficient to mount mtdX and extract the files there, or do I have to use flash_image?
Thanks for any suggestions!
Here is how I recovered:
Download SpeedMod Kernel
Create a nandroid backup on a working phone, copy that over to the broken one
Copy zImage from SpeedMod kernel to SD on broken phone with adb
Enter shell mode on phone
Look into misc/recovery.fstab to figure out the name of the sdcard block device
Mount sdcard with `mount [blockdev] /sdcard`
Flash zImage with `flash_image boot /sdcard/zImage`
Flash nandroid backups with `flash_image {system,cache,datadata} /sdcard/{system,cache,datadata}.img` (but not data)
Leave the phone without battery for at least 1 and at most 6 hours (my phone appeared completely dead after this operation, not even adb shell access, so I went to bed frustrated)
Now you can boot into download mode again using "adb reboot download" (which didn't work when running the CM7 kernel)
Use One Click Odin to revert to stock firmware
Install 3ButtonFix to get combos working again
Note that the original problem that caused all the trouble was that flashing the stock ROM with Odin One-Click disables the 3 Button combos. You have to use the 3ButtonFix to get it working again.
Related
edit: I never did figure out how to backup the original rom. As far as rooting it goes make sure that your phone is in download mode and that you are using a real PC. I am using parallels on a mac and I still have yet to figure out how to get my phone connect to the VM in download mode.
Ok so I just got my galaxy S and I have spent a day and a half searching for the answer to this so if I missed it I am sorry.
I can mount the SD card, copy the update.zip (I have tried all of them I could find), reboot into recovery, flash the update.zip, and reboot
When the phone boots back up the superuser.apk is installed, busybox is in the /system/xbin folder but no "su" in the xbin folder.
My phone is an i9000 8GB
Firmware Version 2.1-update1
Baseband version I9000BGJF1
Build Number ECLAIR.BGJF4
I really want to backup the whole system before I flash a new rom.... any ideas on what could be going wrong?
Hi, I want to transfer a file called undo.zip from my computer to my phone, but it is bricked.
The file is in the external-sd, but in the recovery I can't flash it because my phone won't acces the external-sd in recovery mode.
The file is a zip to be flashed in the internal sd OR I can also have a framework to be moved directly to system/framework. Both ways should FIX my brick.
Okay, I can enter in recovery and download mode, but I don't want to wipe it or to change the ROM.
What I tried to do is:
Flash the file on the external sd on the recovery mode: Transfered the file to the external sd with an adapter... The recovery option for mount external sd in mounts and storage WON'T let me mount it. I think it's because of the kernel (I've got a DOC's kitchen rom with speedmod, but I installed Super Optimized Kernel and overclocked my phone up to 1.2GHz), so I can't mount the external-sd on the recovery.
So the other only solution is
Transfer the file to the internal sd with ADB
The file is in
C:\android\android-sdk-windows\undo.zip
And I have to move it to the ROOT of the Sdcard, but I don't mind where do I move it if it is on the internal sdcard.
This is what I exactly do:
-Connect the phone on the USB on recovery mode
-Open CMD.exe (I'm on wvista) and type adb.exe in the correct folder. A lot of scripts appear, so I suposse I'm doing it good.
-In adb, type ums_enable. DOES NOT WORK (does not recognize the command). I can't activate USB connection in that way.
-In adb, push my framework-res.apk to system/framework. Superuser error, DOES NOT WORK and my phone is rooted. I could do adb shell and then su, but I can't accept the su request in my phone because... well, it's on the recovery!
LAST AND ONLY SOLUTION: In adb, push the file to my sdcard root
--------------------------------------------------------------------------------------------------------------------------------------------------
SHORT STORY:
All I do is "adb push C:\android\android-sdk-windows\undo.zip sdcard", but it gives me error because it's a folder. So, YES, it's a folder because I want to move it to that folder! If I try to move it to a folder in the sdcard, for example by typing "adb push c:\android\android-sdk-windows\undo.zip sdcard/foldernameIwant" it gives me the same error.
------------------------------------------------------------------------------------------------------------------------------------------------
PART 2, IGNORE THE TEXT ABOVE
So, I managed to be able to move files to my sd on the recovery, but when I want to restore my framework by installing a JS5 stock theme, phone won't de-brick even if it has got a new stock framework that should make it boot... Any help? I'm sure the problem is on the framework-res, but it's now restored by another from a JS5 stock theme (I'm using a self-made JS5) and it continues bricked...
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse
A few Months Back I have Installed Bliss Pie rom on my Nexus 6 it is working fine but one day I reboot my phone it booted into ap-fastboot mode so I think I have bricked my device so i try to install stock rom and what I got remote failure error while flashing. So I try Nexus Root Toolkit but still, I failed so I try to boot into twrp using nexus root toolkit and I got success so i try to install rom through otg it started to install and then the error came with unable to mount system, internal storage, cache, and other things. I try every possible way from adb pull to twrp still no success.
Here are the things I have :-
My Bootloader is unlocked
i can boot into Twrp or stock recovery using nexus root toolkit
So If Anyone can help me to install stock rom on my nexus 6 i will give him 5$ on Paypal
You should be able to get some logs from twrp. If you post them it may tell us more.
At worst, the flash drive on the phone is defective, and in that case, I don't know any cure.
In Twrp its shows my internal storage 0 mb
runekock said:
You should be able to get some logs from twrp. If you post them it may tell us more.
At worst, the flash drive on the phone is defective, and in that case, I don't know any cure.
Click to expand...
Click to collapse
In twrp my internal storage shows 0 mb
In twrp, the usual copy logs function may not work because of your problem.
In that case, use adb to pull the logs to your computer.
Something like
adb pull /proc/kmsg
adb pull /tmp/recovery.log
(on the computer).
Why not flash stock through fastboot then?
Enter to recovery, go to wipe section, select internal storage to format and slide to confirm, you should be able to get back your internal storage restored
I have rooted my m10g using magics via twrp and also applied the "no-dm-verify" patch but I didn't notice about the "forced data encryption" patcher here so that's reason why I didn't patch it at this point! anyway the data section was mounting without any problems but after I reboot recovery I was getting error In mounting the data section I just ignore it and I was able to boot into system normally but after some days exactly after "insufficient space" I just rebooted for some reasons and after that the device won't boot anymore / stucked at bootloop...!
I was able to see the home screen/touch wiz about 4 seconds and after that it's reboots again and again (In this point I tried to delete unwanted files quickly but there's no luck).
Things I have tried:
- flashed an recovery.img extracted from combination firmware and tried the "lacking storage booting" an option from stock recovery menu the device started in safe mode (It's says something like this: please bacup your stuff and then perform factory reset) but it's still won't boot (bootloop).
- twrp decrypt (I set no password there but I just tried In hope of chance) btw twrp never asked before to decrypt my data or to enter any password.
- I did twrp backup to my ext-sd and decompiled the boot.img to see what can I do (but after magics's patch I can do nothing).
- Pulled full userdata (mmcblk0p26) section also the emmc (mmcblk0) and tried to mount via linux reader windows tool / opening via 7zip but still can't access the userdata section. also tried to open the dumped userdata via hex editor but still can't see anything(looks like encrypted).
Things I want to try next:
- Format the data section after that try to restore the dumped userdata section via dd command.
- Enable usb debug at boot time and try to adb shell stop then pull all important data from the device.
- Inject custom script in stock_recovery.img to copy all internal files to the externel-sdcard (or even delete some huge files that I'm pretty sure of their path).
Notes / just to be clear:
* Flashing the stock kernel will encrypt the userdata section and the bootloop will stop but I'll lose all my data (I know that so I was just switching from the stock recovery to twrp).
* I could just perform a format data from the recovery menu / twrp or just flash the stock firmware to fix the booting problem but first I need to all my files get back.
Looking for any help in things that I want to try next.
Finally after a lot of tries I have solved my problem...!
How?
Short answer: ClassyKitchen
Long answer:
I just started creating my first rom In ClassyKitchen and I just enabled adb and removed dm-vertify via the kitchen and after the rom has prepared I just flashed through TWRP after I reboot the phone wasn't able to boot (stucked at first samsung logo) switched the device to download mode and I flashed system only using odin... after that phone started with setup wizard! and it's was still in safe mode (the backup message was still showing also) anyway I completed the setup wizard then check the home screen and apks I have installed wasn't there...!!! I opened "My Files" and finally I was able to see my files again!
I just copied all my internal sdcard to my external sdcard...!
After the copy ends I tried to exit safe mode to get my installed apks/contacts again so I just rebooted the phone to exit from the safe mode! But after the reboot "custom binary flashed bla bla".
I flashed stock "boot.img" and "recovery.img" using odin But as I said in the first post data encryption was there...!!!
Anyway I flashed full stock firmware after that I unlocked my OEM and flashed TWRP again and I restored the emmc dump using dd after restore completed rebooted the phone and it's back to it's state...!
this time I just flashed the patched boot.img (ClassyKitchen) and after the reboot phone started normally with setup wizard as said above! Connected to wifi unlocked my OEM and I was trying to get out of safe mode I rebooted and rebooted and power off but I wasn't able to disable the safe mode...!!!
I tried to root using magics but it's failed (the boot was patched by bla unsupported something like that) also the data section was still unmount able! In the TWRP
Anyway I just stopped at this point! Because I have reach my point (Getting back my sdcard data).
Notes!:
* All thanks goes to the author of ClassyKitchen.
* TWRP I was using found here.
* Odin I have used found here.
* I was using the same firmware version (PDA) installed in my phone.
* I have unlocked my OEM using this method the first time I have used it's taked from me only 3 days!.
* The idea of taking full encrypted emmc backup was by this post (I was getting some error messages so I just used "dd if=/dev/block/mmcblk0 of=/your_external-sd/mmcblk0.img" In case of "no space left error" format your externel-sdcard to ext4 and try again).
Sorry for my bad English x).