>I have a Nexus 7
>Rooted, with CWM recovery
>Paranoid Andoid installed, works fine
>Decide to try alternative Rom's
>Download and install CM
>Bootloops
>Flash to stock and unroot using Nexus Root Toolkit
>Root again, install TeamWin recovery
>Try and flash CM again
>Bootloops
>Flash to stock again, install TeamWin recovery
>Try Smooth Rom
>Starts fine
>Reboot
>Bootloops
>Flash to stock again, install CWM recovery
>Decide to flash Paranoid Android as I wish I hadn't changed anything
>Flash PA
>Bootloops
>Flash to stock again, install CWM recovery
>Flash PA
>Boots fine, all going well
>Reboot
>Bootloops
So basically, that is the situation, and I can't figure out why it is happening. I have flashed Rom's before with no problem, but ever since I tried CM, it's all funked up, so yeah, any help at all would be greatly appreciated
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
bftb0 said:
The one thing I don't see in your set of trials is whether or not the complete stock ROM (whether rooted or not) bootloops on it's 2nd boot the way all the other combinations seem to.
Did you do that, or did you presume that we would also presume that Stock always boots in your experiments (at least twice!)?
BTW, you don't need to follow then entire Stock installation script if your tablet bootloader (& radio in the tilapia case) are up to date. That will save you extra steps and the need to re-flash the recovery image afterwards. All that should be needed are:
Code:
fastboot erase system
fastboot format system
fastboot flash system system.img
[b][color=red]fastboot format userdata[/color][/b] *
* obviously this nukes EVERYTHING in userdata, so a complete backup of anything you want saved from /sdcard is needed beforehand. You could replace this step with just a "factory reset" procedure in the custom recovery if you want to avoid the hassle and are convinced that the userdata partition is not causing problems (it's filesystem looks healthy & is appropriately-sized for the variant of the device you have).
Note that this proposal assumes that "flash userdata userdata.img" from the factory install instructions is superfluous. (Unless perhaps there is some sort of "oneshot" logic in there that alters /system on the first boot but not thereafter) - otherwise, how could you erase all of /data and get a "factory reset" some time later? But I think the filesystem sent by this command actually has no files in it, so... same conclusion... superfluous).
Click to expand...
Click to collapse
I kept flashing to stock so I know where I'm at each time, I'm pretty knew to all this so I don't want to confuse myself.
I'm just about to flash stock and see if that bootloops now.
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
okay, so I have flashed stock, and it DOES NOT bootloop
miketino said:
I don't understand how any files could remain on there after a factory reset though, thats why can't grasp why it's bootlooping every time
Click to expand...
Click to collapse
It does seem unusual. OTOH, a "factory reset" in the custom recovery never re-builds the /data ext4 filesystem - so I suppose if the filesystem itself was bolluxed up, that would persist across a (custom recovery) "factory reset".
The thing is, the sequence you describe involves re-doing things with the factory install, and either
Code:
fastboot erase userdata
fastboot format userdata
fastboot flash userdata userdata.img
or
Code:
fastboot format userdata
fastboot flash userdata userdata.img
seems like they certainly should be rebuilding the ext4 filesystem in the userdata (/data) partition.
I mentioned something like this in a couple other posts, but I have experienced odd troubles with the /system partition where I could occasionally create an empty (and new) filesystem using the "Wipe system" option in TWRP, and immediately after that, if I manually checked it's status using (TWRP's) "e2fsck" program, it would report massive problems
Code:
adb shell e2fsck -f -n /dev/block/mmcblk0p<PARTNUM>
which doesn't make any sense at all - a brand-new & empty filesystem should be perfectly clean!
Anyway, something you might want to try is to run the above e2fsck program as a sanity check just after you flash a ROM and just before you are getting ready to reboot into the normal OS. The "-n" option to "e2fsck" prevents it from altering anything, so this is a nondestructive (no touch/read only) test. (I've never tried to actually use e2fsck for a repair - I just start over either with fastboot or the recovery filesystem formatting).
Note that "e2fsck" needs the partitions to be unmounted, so e.g. in TWRP you would:
Code:
adb shell umount /system
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper system = p3)
adb shell umount /sdcard
adb shell umount /data
adb shell e2fsck -f -n /dev/block/mmcblk0?? (grouper data = p9)
If they don't come up clean, obviously you need to do something. Because "mount /sdcard" seems to fail when performed manually in TWRP, I just re-boot the recovery from within TWRP to do other tasks, should that be necessary.
Hope this helps.
miketino said:
okay, so I have flashed stock, and it DOES NOT bootloop
Click to expand...
Click to collapse
I wonder if this means something screwy is being caused by the ROM flashing in the recovery. Maybe try the above suggestions just as a sanity check?
BTW, what recovery and version are you using?
Its Clockwork Mod Recovery, version 6.0.2.3
miketino said:
Its Clockwork Mod Recovery, version 6.0.2.3
Click to expand...
Click to collapse
fwiw, I just booted the touch version of CWM 6.0.2.3
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
to make sure that it had e2fsck present in it's /sbin. It does.
e.g. my (32 GB grouper) device:
Code:
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/UDA: 24564/1875968 files (0.4% non-contiguous), 2641387/7503608 blocks
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/APP
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/sdhci-tegra.3/by-name/APP: 1100/41664 files (1.0% non-contig
uous), 121097/166400 blocks
also, "tune2fs" seems to be present too. You can get a listing of the filesystem creation options using the -l option, as in
Code:
tune2fs -l /dev/block/platform/sdhci-tegra.3/by-name/APP
although I will say I've compared this output before, searching for difference(s) between the way that fastboot formats things and the custom recovery does things and didn't see anything compelling.
[ TWRP might be different than CWM though - it has a utility called "make_ext4fs", whereas I think CWM uses "mke2fs" for fs creation. ]
HTH
If you are hard core droid user, then you already know that a broken or corrupt efs partition can be your worst nightmare yet, causing all kinds of trouble, more so like having hard bricked device, not easy to troubleshoot. It so happened that my friend's S2 lost the baseband and IMEI got blank. Efs professional and Samsung Tools failed to repair the corrupt efs partition or restore data.
Then, I encountered this error in stock recovery. "E: failed to mount /efs (Invalid urgument)"
Tried upgrading the device from 2.3.3 to official jellybean 4.1.2 ROM in hope that a complete wipe would enhance the chances of troubleshooting the efs partition to recover the imei and baseband and hopefully get the network working again. I tried different Odin flashable ROMS but after Odin finished with no errors, device could not boot past the samsung boot logo, kept restarting frequently. I soon found that no ROM flash,kernels or CWM jigs could resolve this error. I dug up thorough the net but I could not find a working solution for my i9100.
So today am posting this solution in the hope to save many other users the agony.
NOTE: This solution worked on GS2 i9100, if you are having the same problem with another samsung device, the same could work but you MUST change the EFS mount point 'mmcblk0p...' part to match to your device.
Most Epic part; Repairing the bad EFS partition also fixed the Blank Imei and Unknown Baseband issue for GS2!!!!!
Now that's utterly spectacular!
Instructions:
Download and flash official firmware for your phone in odin. I flashed the i9100VJMS1 4.1.2 Jelly bean.
Flash a CWM recovery&root your device in recovery. For S2 I used PhilZ CWM.zip recovery which is root ready for your installed firmware.
Install ADB on your computer. See How to install ADB, Fastboot drivers the Easier way
Boot your device into recovery mode.
Connect your device to the PC via USB cable.
In CWM recovery Choose “mount and storage > mount /system” (If it indicates unmount/system, then leave it as that)
Open ADB command window&type:
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1
reboot
NB. If you get this error: can't find /dev/block/mmcblk0p1 in /etc/fstab just reboot and cross your fingers that it works.
After you run the above adb commands your device should reboot all the way up&Voila u should be up and running! Celebrations!!!
You may find that your power key menu&lock screen are not working after this. Thus far, you shouldn't panic. You are probably stuck in factory mode like i was.
This post from XDA member Kunterk fixed that. http://www.forum.xda-developers.com/galaxy-s2/help/solved-official-jb-ls8-lock-screen-t2116497Here
If I provided any help to you, kindly hit that thanks button.
Happy G:victory::victory:king!!
UPDATE:
I have long since written a detailed post about this on my blog http://www.selftechgenius.com/?p=284
thank you
Many thanks.
Sent from my GT-I9100 using XDA Premium 4 mobile app
Omg Thank you Droidsan, I have had the same problem with my daughters S2 been searching all over and trying all sorts then came across this.
Simple and easy.
Phone now boots and works. Im so Grateful.
Only problem I have is the no service, which is how i ended up with nof efs folder in the first place after following a number of guides.
Thanks again Droidsan.
If this post helped you in any way, just HIT that THANKS BUTTON! instead of saying thank you.
Hello,
I have a Redmi 2 - 2014813 (TD-LTE)
I live in Europe but the phone is a chinese version.
History: It was running an old MIUI version (no idea wich one it was... I don't upgrade much...). This version gave some troubles a few weeks back (some programs stopping running etc) I had to return to factory defaults and since that gave some other problems I flashed TWRP and a custom rom (Cyanogenmod 13 from http://forum.xda-developers.com/redmi-2/development/rom-cyanogenmod-unofficial-builds-t3267958 ). That went fine for several days and then suddenly, the phone did not boot anymore. I fixed that by again flashing the same rom. Again, a few days all ok, then again no more booting.
Problem: This time however flashing did not work anymore in TWRP. Unfortunatly also not when using fastboot, MiFlash or MiPCSuite
The error I get in MiFlash (2016.04.01) is "(0x80004005: FAILED (remote: failed to write partition))"
If I try to flash using TWRP (tried both 3.0.0.0 and 3.0.2.0) it fails to flash. When it tries to update the partition details is gives the eror:
"failed to mount '/cach' (invalid argument)"
"failed to mount '/system' (invalid argument)"
Updater process ended with signal: 11
So far that tells me there is something wrong with my partitions....
When I go in TWRP to -wipe - advanced wipe both /cache and system have the ext4 file system but have a 0MB size. Repairing or changing them in TWRP does not help.
If I go in TWRP to - mount only data and micro SDCard are mounted. If I try to mount System and Cache the phone "buzzes" but it does not select them.
If I go in TWRP to - file manager I do see all kinds of directories. (boot, cache, cust, data, dev etc) so apperantly that partition is still there....
When trying to find the correct ROM for my phone I did have some troubles. Naming of the Redmi 2 phones is not very clear... I tried several fastboot roms and will put them all here.
Mismatching image and device (and therefore did not want to install for that reason but just here for information):
wt88047_global_images_V8.0.1.0.KHJMIDG_20160805.0000.29_4.4_global_daca6227c0
wt88047_images_5.3.6_4.4_cn_684e616dfa
wt88047_images_V7.3.1.0.KHJCNDD_20160419.0000.19_4.4_cn_7c7e1e1a71
wt88047_pro_global_images_6.8.18_20160805.0000.29_5.1_global_b9951b6005
wt88047_images_V6.4.3.0.KHJCNCB_4.4_cn_7a50d016b9
Matching but failing to flash with above errors:
wt88047_pro_images_V7.5.3.0.LHJCNDE_20160725.0000.28_5.1_cn_eb95720f3e
I don't realy get the differences... It appears my phone is made for the "China" ROM and at this moment does not like Global roms. Fine with me for now, as long as I can find a rom that can fix my partitions...
However, so far that has failed....
I found that there is now a new version of MiFlash called XiaoMiFlash. (20160830) I tried that also but this give the error:
error:Flash tz error (again with the wt88047_pro_images_V7.5.3.0.LHJCNDE_20160725.0000.28_5.1_cn_eb95720f3e image)
Global rom and another again give the "mismatching device" error.
Hopefully somebody can see what is going wrong and know how to fix this. Please let me know if there is anythin that I could try or any information that you want.
All help apreciated !
Greetings
I think the name for HM13 is wt86047 and not wt88047 , but then again as you said its comparatively difficult to find ROMs For HM13 ..
Anyway , I may not be Of much help but if it is a Mismatching error [0x8fxxxxx , something like this] , try changing the MI flash tool or even the PC (I don't exactly know the reason behind doing this but , I had this issue of mismatching and Mentioned method solved it )
Hope I was of any little help
Hello Hollow,
thanks for trying to help. You atleast point me in the direction to where it might have gone wrong in the past. I was confinced my phone has to be flashed with 88047 but not so anymore. When trying to find differences between 88047 and 86047 some say they are the same (but later MIUI versions) and other seem to think they are still different. I have found several references to my phone, the 2014813 (this is 100% correct) being an 86047 so I decided to give those rom's a try as far as I could find them.
I updated my twrp to 3.0.1.0 with specific reference it being for the 86047
Then I tried two roms trhoug fastboot / miflash
wt86047_images_V7.1.2.0.KHJCNCK_20151209.0000.6_4.4_cn - it resulted in a mismatching error
wt86047_pro_images_V7.5.2.0.LHJCNDE_20160629.0000.25_5.1_cn_160c620370 - again the partitioning errors
I also tried flashing through twrp but again it resulted in the same errors as described in my original posting.
So unfortunatly the 86047 roms do not seem to change anything and also do not want to flash....
Hopefully someone has some other idea's, I am welcome to try anything by now
Greetings
Always keep a firmware backup of miui KitKat from twrp...it will help to restore the firmware when LP firmware is flashed... It will be easy to switch to kk ROM nd custom ROMs also...if u want I'll upload my kk firmware... My device 2014818. I hope it will restore by which u could easily flash to miui 8 kk rom and boot up without any problem...this is the only method I use to switch from LP to KK
Thanks Riyanx55tu, I would say it's worth a try.
By the time I was installing twrp it was allready to late to make a backup. I had miui 6 or something, running fine for more than a year, but it got corrupted with all kinds of errors. From that corrupted miui I went straight to Cyanogenmod 13 wich got my phone working again. To be honest... never thought about making a backup at that point
It is worth a try I would say. The firmwares are supposed to be somewhat compatible so it might revive my phone after which I can go to correct roms again....
Do you want to upload it to ftp or something else ?
Thanks in advance !
kk Firmware.
nachtwacht said:
Thanks Riyanx55tu, I would say it's worth a try.
By the time I was installing twrp it was allready to late to make a backup. I had miui 6 or something, running fine for more than a year, but it got corrupted with all kinds of errors. From that corrupted miui I went straight to Cyanogenmod 13 wich got my phone working again. To be honest... never thought about making a backup at that point
It is worth a try I would say. The firmwares are supposed to be somewhat compatible so it might revive my phone after which I can go to correct roms again....
Do you want to upload it to ftp or something else ?
Thanks in advance !
Click to expand...
Click to collapse
I will upload it in google drive...just download it and paste it in ur TWRP -> BACKUPS .... Use twrp 3.0 not 3.0.1
---------- Post added at 06:57 PM ---------- Previous post was at 06:28 PM ----------
https://drive.google.com/folderview?id=0Bw3_QwnI11oUcEw3ZTkwR2ZCMG8
Hello Riyan,
first of all, thanks for your effort to help me. Very much appreciated !
Unfortunatly however it did not work
I will discribe what I did and hopefully it will help to find my problem.....
I downloaded your backup. (Only 67MB in files ? I was expecting much more since the normal roms are WAY bigger)
I installed twrp 3.0.0.0
Created a backup with twrp (it was empty by the way... nothing to backup apperantly) I did this so it would create the folder structure for later.
I deleted everything in that folder (only the log was present) and I copied your backup to this folder.
I started again in twrp and choose restore.
Unfortunatly it did not work. It ended with the cache and system not mounted error.
I copied the log to http://pastebin.com/KuJ18XYz maybe somebody can see something in it......
My idea is that it all boils down to something being wrong with the cache and system partition. This is what it looks like (both look the same) if I look at them in twrp.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Again thanks so far, hopefully we can find some solution
nachtwacht said:
Hello Riyan,
first of all, thanks for your effort to help me. Very much appreciated !
Unfortunatly however it did not work
I will discribe what I did and hopefully it will help to find my problem.....
I downloaded your backup. (Only 67MB in files ? I was expecting much more since the normal roms are WAY bigger)
I installed twrp 3.0.0.0
Created a backup with twrp (it was empty by the way... nothing to backup apperantly) I did this so it would create the folder structure for later.
I deleted everything in that folder (only the log was present) and I copied your backup to this folder.
I started again in twrp and choose restore.
Unfortunatly it did not work. It ended with the cache and system not mounted error.
I copied the log to http://pastebin.com/KuJ18XYz maybe somebody can see something in it......
My idea is that it all boils down to something being wrong with the cache and system partition. This is what it looks like (both look the same) if I look at them in twrp.
Again thanks so far, hopefully we can find some solution
Click to expand...
Click to collapse
1)The only option left is connect the phone to PC or Laptop etc...in fast boot mode then open mi PC suite(make sure u have installed adb drivers of xiomi) then once detected click to flash option on the right Connor of the PC suite and it will ask for
Global ROM or Developer rom(click to global) and wait until it flashes... It is only only way which I restored my redmi 2 when it was totally bricked.
2)if u had not flashed LP ROM of Miui then try to flash Phillz Recovery by jav team and flash the rom. I hope it should fix ur device. or Give away to service center.
The Twrp backup of my phone only contains firmware were I just delete the old ROM first then I restore the firmware then I reboot to recovery again and flash the global kk rom...it works like charm. No need to flash all with fastboot so that's the best option I have.
Thanks again.
I had tried flashing with MiPCSuite in the past but have now tried it again. It does see the phone, (Shows Flash wt88047) and give the options to flash either Stable or Beta firmware. Choicing either will make it download the firmware and then, when it tries to flash, it stops after just a few seconds with the error "couldn't flash device"
When searching I have found reference to Phillz recovery but so far could not find it for my device. I will search for that again and try to find the right version. Will post the results here.
nachtwacht said:
Thanks again.
When searching I have found reference to Phillz recovery but so far could not find it for my device. I will search for that again and try to find the right version. Will post the results here.
Click to expand...
Click to collapse
http://www.mediafire.com/?vkg0b4q0m8ka1cl
Phillz recovery.
Thanks again.
Unfortunatly a new problem has occured.... I can not boot into recovery any more.
If I flash twrp with Flash-TWRP.bat script, my phone reboots to twrp (the script handles that) but if I close twrp down, it is not possible to boot to recovery anymore (pressing VOL UP + POWER and VOL UP + VOL DOWN + POWER don't work) I can still get into twrp by running the .bat script but unfortunatly Philz recovery does not work with that script.
When trying to boot into philz recovery using fastboot (fastboot boot recovery.img where recovery.img is philz recovery) I get the error:
FAILED (remote: dtb not found)
Strange enough, using a twrp recovery it does work... (but twrp does not work anymore with the vol up and power button.....)
Very unfortunate because I had some hope that Philz would be a little more advances so it could fix my partitions...
nachtwacht said:
Thanks again.
Unfortunatly a new problem has occured.... I can not boot into recovery any more.
If I flash twrp with Flash-TWRP.bat script, my phone reboots to twrp (the script handles that) but if I close twrp down, it is not possible to boot to recovery anymore (pressing VOL UP + POWER and VOL UP + VOL DOWN + POWER don't work) I can still get into twrp by running the .bat script but unfortunatly Philz recovery does not work with that script.
When trying to boot into philz recovery using fastboot (fastboot boot recovery.img where recovery.img is philz recovery) I get the error:
FAILED (remote: dtb not found)
Strange enough, using a twrp recovery it does work... (but twrp does not work anymore with the vol up and power button.....)
Very unfortunate because I had some hope that Philz would be a little more advances so it could fix my partitions...
Click to expand...
Click to collapse
Philz isn't compatible with your bootloader. For device mismatch follow below thread.
http://en.miui.com/thread-178314-1-1.html
Since your device is 2014813, you should try wt86047 roms. Anyways, your partitions are corrupted and there's less chance of getting it work. Boot up twrp and flash any other new custom roms and check.
Sent from my 2014818 using XDA Free mobile app
Venkatesh said:
Philz isn't compatible with your bootloader.
Click to expand...
Click to collapse
Yes.. again it is for the 88047 and not my phone....
Venkatesh said:
For device mismatch follow below thread.
http://en.miui.com/thread-178314-1-1.html
Click to expand...
Click to collapse
I found some roms that are 100% for my phone so I desided to take that step last (see below).
Venkatesh said:
Since your device is 2014813, you should try wt86047 roms.
Click to expand...
Click to collapse
Yes. I have now all correct versions for my phone. Will write my results at bottom of message.
Venkatesh said:
Anyways, your partitions are corrupted and there's less chance of getting it work.
Click to expand...
Click to collapse
This is indeed what I think has happened. My partitions are corrupted and the miui stock roms are not able to repair it.....
Venkatesh said:
Boot up twrp and flash any other new custom roms and check.
Click to expand...
Click to collapse
This is what I have done after your advice:
First of all, I installed the wt86047 stock recovery and then tried to install the original miui. This unfortunatly failed. (the stock recovery just gives a "failed" notice and nothing more)
Then I tried to install the following roms using twrp (wt86047-TWRP3.0.2-0_LP):
HM2014813_Redmi2TD_THUNDER_MiUi7-6.1.28
HM2014813_Redmi2TD_THUNDER-MiUi7-6.3.31
sMiUI_v8_wt86047_6.9.1_YRTTFC
xiaomi.eu_multi_HM2014813_V7.0.9.0.KHJCNCI_v7-4.4
All tries again failed. updater process ended with error 7 or signal 11 and the cache and system partitions where "unable to mount" / zip unable to install.
Then I tried searching for some custom roms and must say... it's hard to find them for my 2014813 / 86047. Most of the custom roms are made for the other models. (this must also be the reason why several people report the "unable to mount system / cache error... flashing the wrong roms....)
So all I could find where following roms wich are 100% for my device (I was able to find some that are reported to work on both but I want a 100% sure fit now....)
wt86047_images_6.9.1_20160805.0000.29_4.4_cn_59a99f5e10
wt86047_images_V6.5.3.0.KHJCNCD_4.4_cn_3c57a69a64
wt86047_images_V7.1.2.0.KHJCNCK_20151209.0000.6_4.4_cn_3df2accecd
wt86047_pro_images_V7.5.2.0.LHJCNDE_20160629.0000.25_5.1_cn_160c620370
And now another the interesting thing.... they all failed, but not with the same error.
The first 3 (non pro ?) failed with the mismatching device error. (are there different versions of the wt86047 ???? probably I can overcome this by disabling the 2 lines....)
The last failed with "error: flash tz error" (this is MiFlash 2016.08.30)
When trying that same rom with MiFlash 2016.04.01 the error is "unspecified error (0x80004005: FAILED (remote: failed to write partition))"
So I disabled the 2 lines in the flash_all.bat files (the check for the mismatch) and I tried flashing all 3 that gave the mismatch error again.
Now flashing in MiFlash fails but with the error: "flash tz error" / failed to write partition
So my conclusion so far....
Partitions are corrupted and show in twrp as ext4 with a size of 0mb and are not mounted.
I apperantly messed up my phones partitions flashing the wrong rom. Flashing original roms or custom roms, either with twrp or miflash / fastboot does not work anymore.
Anyone know how to fix partitions ? Can I manualy resize them ? Any other ideas welcome
nachtwacht said:
Yes.. again it is for the 88047 and not my phone....
I found some roms that are 100% for my phone so I desided to take that step last (see below).
Yes. I have now all correct versions for my phone. Will write my results at bottom of message.
This is indeed what I think has happened. My partitions are corrupted and the miui stock roms are not able to repair it.....
This is what I have done after your advice:
First of all, I installed the wt86047 stock recovery and then tried to install the original miui. This unfortunatly failed. (the stock recovery just gives a "failed" notice and nothing more)
Then I tried to install the following roms using twrp (wt86047-TWRP3.0.2-0_LP):
HM2014813_Redmi2TD_THUNDER_MiUi7-6.1.28
HM2014813_Redmi2TD_THUNDER-MiUi7-6.3.31
sMiUI_v8_wt86047_6.9.1_YRTTFC
xiaomi.eu_multi_HM2014813_V7.0.9.0.KHJCNCI_v7-4.4
All tries again failed. updater process ended with error 7 or signal 11 and the cache and system partitions where "unable to mount" / zip unable to install.
Then I tried searching for some custom roms and must say... it's hard to find them for my 2014813 / 86047. Most of the custom roms are made for the other models. (this must also be the reason why several people report the "unable to mount system / cache error... flashing the wrong roms....)
So all I could find where following roms wich are 100% for my device (I was able to find some that are reported to work on both but I want a 100% sure fit now....)
wt86047_images_6.9.1_20160805.0000.29_4.4_cn_59a99f5e10
wt86047_images_V6.5.3.0.KHJCNCD_4.4_cn_3c57a69a64
wt86047_images_V7.1.2.0.KHJCNCK_20151209.0000.6_4.4_cn_3df2accecd
wt86047_pro_images_V7.5.2.0.LHJCNDE_20160629.0000.25_5.1_cn_160c620370
And now another the interesting thing.... they all failed, but not with the same error.
The first 3 (non pro ?) failed with the mismatching device error. (are there different versions of the wt86047 ???? probably I can overcome this by disabling the 2 lines....)
The last failed with "error: flash tz error" (this is MiFlash 2016.08.30)
When trying that same rom with MiFlash 2016.04.01 the error is "unspecified error (0x80004005: FAILED (remote: failed to write partition))"
So I disabled the 2 lines in the flash_all.bat files (the check for the mismatch) and I tried flashing all 3 that gave the mismatch error again.
Now flashing in MiFlash fails but with the error: "flash tz error" / failed to write partition
So my conclusion so far....
Partitions are corrupted and show in twrp as ext4 with a size of 0mb and are not mounted.
I apperantly messed up my phones partitions flashing the wrong rom. Flashing original roms or custom roms, either with twrp or miflash / fastboot does not work anymore.
Anyone know how to fix partitions ? Can I manualy resize them ? Any other ideas welcome
Click to expand...
Click to collapse
Custom roms are same for 2014811 and 2014813 models. You can try any rom but it shouldn't contain any firmware files. Try custom roms from redmi 2 section, all are compatible with your device model.
Sent from my 2014818 using XDA Free mobile app
Venkatesh said:
Custom roms are same for 2014811 and 2014813 models. You can try any rom but it shouldn't contain any firmware files.
Click to expand...
Click to collapse
ok. I am not 100% sure how I can know / see / find if it contains any firmware files but I gave it a try.
Venkatesh said:
Try custom roms from redmi 2 section, all are compatible with your device model.
Click to expand...
Click to collapse
Downloaded 4 (random) roms and tried to flash them with twrp 3.0.2.0:
Tesla-wt88047-6.0.1.EMP.v2.1-BETA-20160509-1435
MK51.1-wt88047-201604121722-UNOFFICIAL
tipsy-wt88047-5.1.1.Final_hangover.v2.3--20160715-1939
ZEPHYR-OS-6.0.1-20160901-wt88047
The first 3 fail.... Several things in the log:
Unable to mount cache and system
This package is for device: HM2014811, HM2014812, HM2014813, etc (up to version 112)
This devices is wt86047
Updater process ended with Error: 7 Error when installing zip file
Since HM2014813 and wt86047 are the same... I don't get why that line is there and the process immediatly fails after this check. The package check is however shown in white and the error in red so maybe the device check does not belong to the error.....
The ZEPHYR-OS-6.0.1-20160901-wt88047 image only failed on the mount error. More specific:
mount: failed to mount /dev/block/bootdevice/byname/system at /system: invalid argument
unmount of /system failed: no such volume
Flashing SuperSU
mount: failed to mount /dev/block/bootdevice/byname/system at /system: invalid argument
unmount of /system failed: no such volume
script succeeded: result was [ ]
And then again the can not mount cache and system error (invalid argument)
Maybe another rom that I should try ? Anything else I can try ??
tia !
nachtwacht said:
ok. I am not 100% sure how I can know / see / find if it contains any firmware files but I gave it a try.
Downloaded 4 (random) roms and tried to flash them with twrp 3.0.2.0:
Tesla-wt88047-6.0.1.EMP.v2.1-BETA-20160509-1435
MK51.1-wt88047-201604121722-UNOFFICIAL
tipsy-wt88047-5.1.1.Final_hangover.v2.3--20160715-1939
ZEPHYR-OS-6.0.1-20160901-wt88047
The first 3 fail.... Several things in the log:
Unable to mount cache and system
This package is for device: HM2014811, HM2014812, HM2014813, etc (up to version 112)
This devices is wt86047
Updater process ended with Error: 7 Error when installing zip file
Since HM2014813 and wt86047 are the same... I don't get why that line is there and the process immediatly fails after this check. The package check is however shown in white and the error in red so maybe the device check does not belong to the error.....
The ZEPHYR-OS-6.0.1-20160901-wt88047 image only failed on the mount error. More specific:
mount: failed to mount /dev/block/bootdevice/byname/system at /system: invalid argument
unmount of /system failed: no such volume
Flashing SuperSU
mount: failed to mount /dev/block/bootdevice/byname/system at /system: invalid argument
unmount of /system failed: no such volume
script succeeded: result was [ ]
And then again the can not mount cache and system error (invalid argument)
Maybe another rom that I should try ? Anything else I can try ??
tia !
Click to expand...
Click to collapse
Try to mount partitions and formar them from twrp. But i feel you can't do much except playing with partitions. Try some tutorials on formatting corrupted android device partitions.
Sent from my 2014818 using XDA Free mobile app
Venkatesh said:
Try to mount partitions and formar them from twrp. But i feel you can't do much except playing with partitions.
Click to expand...
Click to collapse
I have tried that before. If I select "mount" in twrp it does not want to mount. The phone "fibrates" and thats all that happens.
I tried formatting and even changing from ext4 to some other type.
All seems to fail because it does not want to mount.....
Venkatesh said:
Try some tutorials on formatting corrupted android device partitions.
Click to expand...
Click to collapse
Will do a search for that and give it a try, thanks.
i using twrp 3.0.1 and it works fine
Sent from deep sea
Hello Exo,
I can not find 3.0.1 for my 2014813. I did find 3.0.0.1 but that failed to download from the source where I found it.
I have however tried with both 3.0.0.0 and 3.0.2.0 and the stock recovery, all fail.
For twrp I have made a video of what is actualy happening and where I think the problem lies...
twrp with cache and system directories
@Venkatesh - Still working on the "corrupt android partitions". Will update here as soon as I have done it. I will however start with a clean PC just to rule out that anything is wrong with the ADB drivers so it will take a few hours / days.
Update: Tried booting into edl mode to try to flash using edl. Unfortunatly no luck. The phone does not want to boot into edl mode.
Also tried fixing my partitions. I get reasonably far.... I get into the adb shell, I was able to figure out some other things but unfortunatly, when running e2fsck I get some errors that go above my head. Hopefully someone can tell me what to do next.... (process copied below)
tia !
============ adb shell copy paste ============
~ # umount /cache
umount: can't umount /cache: Invalid argument
[Cache was not mounted....]
[ran the next command to find out what I had to fix]
~ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=968148k,nr_inodes=154348,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=968148k,nr_inodes=154348)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p30 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p30 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk1p1 on /external_sd type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ # cat /etc/fstab
/dev/block/mmcblk0p24 /cache ext4 rw 0 0
/dev/block/mmcblk0p23 /system ext4 rw 0 0
/dev/block/mmcblk0p30 /data ext4 rw 0 0
/dev/block/mmcblk0p25 /persist ext4 rw 0 0
/dev/block/mmcblk0p1 /firmware vfat rw 0 0
/dev/block/mmcblk1p1 /external_sd vfat rw 0 0
/usb_otg auto rw 0 0
[I desided to start with trying to repair cache]
~ # e2fsck -fv /dev/block/mmcblk0p24
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p24
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[what followed where bad magic numbers.....]