[Q] system partition corrupted (can't umount) - Xiaomi Mi 2

Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:

Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...

Related

sdcard slot does not work!

First off thanks for all the wonderfull help. I finally managed to flash jf1.51 and get the phone running again. Kinda hard 2 do without a sdcard and when fastboot didnt work!!!!!
Now that the phone is running again I STILL have no sdcard slot!! The phone just says...
Removed SD card
The SD has been removed. Insert a new SD card to increase your device
No one has had this problem....
********Original********
We will start with what happened up till that point.
I originally was using haykuro hero with apps2sd (Original Tmobile 1gb sdcard) It worked but slow and crashing on just about everything.
Did the multiple speedups / optimizations for hero.
Switched too Superheros beta v1 hero rom. (No problems other than slow/app crashing)
Ordered a new Transcend 4gb class 6 sdcard.
Waited until I received the new card before switching too Superheros beta v2.
Setup the partitions on the new 4gb just like I had done with the 1gb (and the 1gb had no problems except 4 being slow)
Updated to superheros beta v2 rom. Everything went fine, had like 9mb free (I used the full Rom) After the phone was setup and rom was booted. Used the app2sd app built into the rom. Moved the apps/cache 2 sdcard. Rebooted phone and had a bootloop (kept replaying the htc boot animation)
So remembering reading when hero first came out. I assumed that some of the files for hero did not transfer too the sdcard (Remember when people had problems with app_s.zip)
So I go into the bootloader mode (home + power) to reflash the rom and receive this error (Now during this time I still have the 4gb in)
Installing from sdcard...
Finding update package...
E:Can't mount /dev/black/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
--------------------------------
I have tried 4 different sdcards with 3 different sdcard readers and every one of them has this error. I have tried wiping but didnt change anything.
It is like the phone cannot see any sdcard anymore. I can adb but I dont know anything that could help.
Thanks
-Matt
**Edit**
Have tried partitioning to only fat16 and fat32 on sdcards.
Have tried fastboot with dreaimg.nbh and still does not detect sdcard.
Have tried putting app_s.zip into ext2 partition.
Have tried Downloading different roms and rom types.
Have tried "mount /sdcard" *error mounting /dev/block/mmcblk0p1 on /sdcard failed: No such file or directory*
Have tried Pushing app and app_s to /data from update.zip
Have tried copying app and app_s to /mmcblk0p2 from a linux os "Phone will not detect either partitions" (/mmcblk0p1 is fat32. /mmcblk0p2 is ext2)
Have tried editing mountd.conf and init.rc
Everytime I try and apply update.zip I get these weird files on the sdcard. (http://www.pcxpressrepair.com/android/qxdm_20080904_032341_1.dm , http://www.pcxpressrepair.com/android/qxdm_20080904_032607_1.dm There are just 2 that I uploaded.
Also here is a Logcat of when the phone is trying to boot (bootloop)
http://www.pcxpressrepair.com/android/logcat1.txt
During bootloop here are the mounts
--------------------------------------------
Filesystem Size Used Available Use% Mounted on
tmpfs 48.2M 0 48.2M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 90.0M 76.7M 13.3M 85% /system
/dev/block/mtdblock5 89.8M 14.7M 75.1M 16% /data
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
I have had similar problems but it was because of a bad download. Or I disconnected the phone to quickly from the USB before selecting remove.
Wrong forum. Mods, lock this thread pronto!
Also I received a letter from tmobile saying that they are going to drop me because of roaming too much. I would be nice to get this worthless phone running again. I have until July 7th 2 switch carriers. Because my G1 is basically a paperweight now I was thinking of getting the HTC lancaster with AT&T but it will not be on the market in time.
By the way the phone is acting and no one else having this problem. I am lead 2 believe that this is a hardware issue with the G1. But, every time I try and flash the rom I get that weird file on my fat32 partition. So I would assume that the phone can still write to the sdcard, even though it cannot mount it. So don’t know if it is hardware or not. But, tonight I will disassemble the phone. (Because I’m not getting 2 much help here)
Also if apps2sd or cache failed when the rom was running for a moment what would be a way to restore it back (If the phone worked and no apps2sd is still fine 4 me!). Every time I try and link back 2 the phone it cannot find the directories that are on the sdcard (obvious cuz the sdcard is not mounted) I had this problem before but, the sdcard was mountable so there was no problem.
Would there be a configuration file that I can pull, modify, and then push back with the app2sd/cache info on it. I am moments away from pushing the entire update.zip 2 the phone. I am running out of options on what 2 do or how 2 fix.
-Matt
phone wont even turn on now.
Will it blend? Post results.
As soon as I get a blender
Same Prob
I'm having the exact same problem, has anyone found a solution yet?
Same issue here! Reformatted, wiped the works and nothing. And I have searched everywhere and like you it seems hardly anyone has this same issue. If I can't get it resolved soon I am getting the phone replaced.
I have got the same problem on my vodafone HTC Magic. Can boot to spl, fastboot to recovery rom but cannot mount SD Cards. Anyone found a solution?

Cannot Get Phone To Start Anymore

So today i rooted my phone installed JF1.41, i partitioned my sd card IN MY G1, since i have a mac and for some reason it wont partition the card right. Then i did the apps2sd deal... Then i wanted to use a theme, well that screwed everything, and it wouldnt get back to normal or even start again. So completely formatted my card, which now has NO PARTITIONS(i guess just 1), and i think the phone is trying to read files on a partition that dont exist now, and NOTHING is working. Anyone on here that can help? I am rather smart with this stuff, but really am going to need someone to help me. I need my phone tomorrow.
Thanks.
How did you reformat your sdcard? Did you check in parted to see that you in fact only had 1 partition again? I suggest you flash a new updated ROM like Cyanogen 4.2.5. That has apps2sd script built into the rom. It will do it automatically so you don't have to mess with all that.
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
illthinking said:
ok ill try it right now and see
I know FOR SURE i dont have a 2nd partition cuz i formatted it with only 1
Click to expand...
Click to collapse
you're going to need a second partition for apps2sd to work. I suggest you do that first before you flash a rom, or else you will just have to end up reflashing.
Ok Downloaded Cyanogen4.2.5
This is the problem i keep having when i try to apply the update it say
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted.
So i think it has to do with the fact it wants to read /dev/block...etc from the partition of the sdcard that is now non existent
problem is i have a mac and cant properly fromat the 2nd partition (ext2)
unless you know of a way
the way i first did it was using some code i got off of here to have the phone do it itself... now that i cant start the phone i cant do the partition
what recovery do you have? I suggest you put this one on your phone.
http://forum.xda-developers.com/showthread.php?t=566669
It partitions your sd card for you.
Also for Cyanogen, you need to flash the htc OTA update one, then flash his update for those to work.
ok...
so i found some plugins for the new Snow Leopard OS for mac called MacFuse 2.0 along with its counterpart fuse-ext2 and i partitioned my card
you might want to upgrade to ext3. it's faster than ext2 and runs smoother
just tried to flash the recovery found here
http://forum.xda-developers.com/showthread.php?t=566669
with no avail and tried to start the phone(power+camera) and said no image
heres what it said for the recovery
/ # mount -a
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
mount: mounting /system/modules/modules.cramfs on / system/modules failed: No such file or directory
mount: mounting /system/xbin.cramfs on /system/xbin failed: No such file or directory
I mean, what i want to know is how to build the file format back on my sd card so itll work, or build it so it will look on my actual phone... People put up the code to have it switch where it reads things from, there MUST be a way to switch it back manually as well
Use fastboot and write the recovery image
here's a link to fastboot
http://developer.htc.com/adp.html
then when thats running plug in your G1 and turn on holding Power and camera when the screen turns on you might have to press back to enable FB but once its enabled type in terminal
Code:
cd *where ever your recovery image is*
fastboot flash recovery *recoveryname*.img
reboot
can someone hook up a quick step by step on how to hook my phone up fastbooted? I have a mac and i can get the phone to say fastboot, but im lost after that... If you want to reroute me to a different thread, please verify that it REALLY has the info before posting it.
i have been trying to find the name of the device and im getting
/dev/tty.Bluetooth-Modem as the device name, but a Permission Denied thing... now i cant just go click something in the phone menus, since i cant get the phone to start, so is there a way to get permissions through the Terminal application?
that error you get when you type mount -a is normal continue as instructed:
flash_image recovery /(whatever your recovery image is called)
if you have adb you could try parted /dev/block/mmcblk0 and type print to see your parttitions.
so i can get it to say it flashes the recovery, but still not starting
so when i try to do any updates it says SDCARD wont mount
any input?
Looks like im going to go for a broken record, until SOMEONE can help me figure my phone out... I need to get it running, and i know someone can figure it out

NEED HELP PLEASE deleted partitions off emmc

Been semi bricked for hours... I messed up the emmc partitions using adb gparted dev/block/mmcbkl0 and now nook won't boot.. not even off SD card
the only thing i can get to boot off sd card image is rootpack which boots me into recovery.. i tried everything but no matter what I do in recovery i always get errors regarding the mounting of my cache and data, which obviously is because i deleted the partitions...
when i try to edit the partition table from adb parted denies me permission
please help... i'm very new to the nook and everything I just said I learned in the past 4 hours that i have been reading through forums trying to fix it..
thank you
In this very forum..
http://forum.xda-developers.com/showthread.php?t=958748
Besides, what makes you think you deleted the partitions? Did you?
on adb parted i went through every single one of the partitions and deleted them... only left one intact.. so i'm pretty sure i deleted them..
I have already tried flashing this and it flashed just fine however when I go back into the recovery menu I get the same error
E:\ something something can't mount data/recoverylog.log
E:\ something something can't mount cache/recoverylog.log
and four others just like it..
if anyone is willingto help the errors i get in clockwork recovery are
E: Can't Mount /cache/recovery/command
E: Can't Mount /cache/recovery/log
ralphsancho said:
on adb parted i went through every single one of the partitions and deleted them... only left one intact.. so i'm pretty sure i deleted them..
I have already tried flashing this and it flashed just fine however when I go back into the recovery menu I get the same error
E:\ something something can't mount data/recoverylog.log
E:\ something something can't mount cache/recoverylog.log
and four others just like it..
Click to expand...
Click to collapse
And why in gods name did you do that?
Anyway, get the repartition/fix tool that's in these forums.. I think in Development, might be in General. It just works.

[Q] e2fsck on boot time for fail-proofing SD Card?

I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
you must use e2fsck in order to check the EXT partition before mounting, esp if you are using it for DATA.
also, if you try to mount a bad partition it won't mount as r/w, instead it will mount as r/o (read only). that's why you were having the read-only issue.
regarding java, you need to install JDK. if you have a x64 system, you need both x86 and x64 variants.
hope this helps
blastsound said:
I spent more than eight hours to set up HD2 mount /data to sd-ext; but I found that LogCat keeps saying that the error EROFS(Read-only file system) has occurred. After that I went to CWM Recovery, ran e2fsck -yfv /dev/block/mmcblk0p2 and rebooted. It started working again from then; so maybe putting e2fsck command on boot-time script might be useful for failproofing the SD card.
I am using Windows; and I somehow the message cannot find java keeps occurring and I can't use the kitchen. So anybody can help?
Click to expand...
Click to collapse
How are you mounting /data to EXT? If you are using my method, I have included a accept that scans at boot and then mounts if the partition is clean. Mounted partitions can't be scanned, they have to be unmounted before scanning.
Swyped from my HTC HD2 using XDA Premium

[Q] Yet another bricked defy. can't restore cwm backup

Hi,
well... what can i say... i bricked my beloved defy. =(
How it happened:
Since Quarx's CyanogenMod 7 i used several CyanogenMod Versions from Quarx und Epsylon until about 2 weeks ago. I had the CM10 (4.1.2) Version from 11.05. installed.
Then i saw Quarx new release from 16.06.
Before i flashed the new version i made a full backup with cwm 5.7.0. Then i installed the new version trough cwm. everything look fine. But there wen't something really wrong. After rebooting the phone got stuck even before 2ndinit. I tried it several times but the the phone wasn't booting any more.
I thought: no problem. I have a backup. Let's restore is quickly. The easiest way to me was:
- start the phone in bootloader
- flash a stock sbf with rsd lite (sbf: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_UCAJRDNFRYORTCOREEU_P023_A008_HWp3_Service1FF.sbf
- root the phone with superoneclick
- install 2ndinit for defy (SndInitDefy_2.3.apk i think it's cwm 5.0.3.1)
- restore backup
but here the problem beginns trying to recover /system(log from recovery):
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
I:/system is not safe to format
I:Erasing from device...
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Skip system unmount, remount read-only
Remount /system read-only
50-cm.sh60-baseband.sh70-bootmenu.sh70-gapps.sh80-battd.shApollo.apkApplicationsProvider.apkAudioEffectSettings.apkBackupRestoreConfirmation.apkBluetooth.apkBrowser.apkCMFileManager.apkCMFileManagerThemes.apkCMWallpapers.apkCalculator.apkCalendar.apkCalendarProvider.apk
..... and so on and so on. (is quite a long list ).....
Error while restoring /system!
Problem while restoring system !
-------------------------------------------------------
i tried so many things like:
- install cm10 an try restoring with cwm 5.7.0 (same error)
- different stock sbf's (makes no difference)
- extracting system.ext3.tar and copying i to /system with adb (stops copying at about 50%)
and much much more... i forgot the rest ^^
the thing is.... i have no idea what exactly is going wrong. In my opinion it's here in the log: "Remount /system read-only". how should cwm be able to write the backup into system i it is mounted as "read-only".
im working on it since the last 2 weeks and it is getting super frustrating =(
Hopefully someone has better ideas than me? I would appreciate it.
At least: thanks for reading!
There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.
hotdog125 said:
There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.
Click to expand...
Click to collapse
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.
dediknight said:
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.
Click to expand...
Click to collapse
Yes, wiping system is important in this case. The option is present on the main screen of CWM.
hotdog125 said:
Yes, wiping system is important in this case. The option is present on the main screen of CWM.
Click to expand...
Click to collapse
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".
dediknight said:
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".
Click to expand...
Click to collapse
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).
hotdog125 said:
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).
Click to expand...
Click to collapse
Thank you very much. Sadly, it wasn't the solution to my Problem. But the error messages getting a bit clearer now ^^.
Here is the recovery log:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
script result was [because /system got wiped]
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
E:format_volume failed to unmount "/system"
Error while formatting device /system!
Problem while restoring system !
--End of log--
OK, somehow the devices are "busy" so the wipe script couldn't wipe. Although in cwm it said it was successful.
So i tried unmounting /system, /cache and /data before running the script. Here's what i got:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Invalid argument
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
unmount of /data failed; no such volume
script result was [because /system got wiped]
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
--End of log--
Is it possible to do something about the "busy" partitions. Whatever they're busy doing
Check out these threads, not sure they'll help - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/.
AND http://forum.xda-developers.com/showthread.php?p=20707200
Your partitions may be in the wrong format.
EDIT - You can try starting from sbf, then installing your preferred CM10 release, and then extracting the backups into the respective directories using ES file explorer (only the files that you've changed).
EDIT 2 - Install CM10 with clockworkmod (not TWRP) and then go to bootmenu (press go back on the main screen of recovery), and then format system and data to ext4, and then try restoring backup. <------ try this first
why??
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.
chawnix said:
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.
Click to expand...
Click to collapse
You are in the wrong device forum.
Sent from my Nexus 7 using Tapatalk
:good::fingers-crossed:Thank you, i have a similar problem. My battery's Defy was completly discharge. Normaly, i plug my Defy, wait for 10 % charging, and i turn it on and i let the battery charging all night. But, i forgot to turn my defy on, and the morning when i turn it on, the cyanogen 7 logo bootloop.
I do a wipe system reset to factory, the defy turn on, and when i restore my backup, bootloop again.
I do what hotdog125 write, i was thinking its works, but it didn't.
I lost my data, :crying::crying::crying::crying: but i have a nice cyanogen 10 bootloop :laugh::laugh::laugh:
I finaly restore my defy with a backup do with recorvery when my phone make a bootloop.
I put cyanogen 7 and i found an application name Nandroid Manager http://forum.xda-developers.com/showthread.php?t=2044414 , 1,46 euros, that permit to restore all or a part of the backup you do.
I restore my apps, my sms, my mms, my call log etc... i want to keep. My contact was backup on my gmail account.
Like i saw it works, i put cyanogen 11 and redo the partial restore.
My defy was fine, and increased from mb525 to mb526 when i install Cyanogen 11.
I recommand when you have an android phone to root it, put an recorvery, put Nandroid Manager and backup with recorvery regularly, you could restore all your phone if you don't change your rom, or resotre partial data if you change your rom.
Thank you to your site.:laugh::highfive:

Categories

Resources