Related
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.....]
Hello. I am having issues with my Nexus 7 2012 (WiFi i think)
It was all running well, it was like for 2 years or something on same stock rom kitkat 4.4.4 i think, and it worked fine.
Then i decided to transfer some photos from my phone to Nexus 7 via bluetooth, then one file transferred and then Nexus 7 froze completely, but it didn't restart by itself at all
I had to restart it manually by holding the power button.
Then it broke down somehow. I expected it to just reboot normally, but it got stuck at 'Google' screen and did nothing.
I went to bootloader and tried booting to recovery, but it just gave 'Booting failed' error and it has shown Google logo again for some reason and 'Go to recovery' button from bootloader
all on the same screen.
I used to have clockwork recovery which worked fine before, everything was fine. My nexus 7 is rooted and has unlocked bootloader but everything broke down and i don't know why.
I already tried myself to get adb and fastboot, fastboot seemed to detect devices, but adb didn't detect any device while my Nexus 7 was in bootloader mode.
Eventually i have tried just pushing 1 thing via fastboot which is recovery.img, and after it didn't work because it would say something like FailToWrite, i tried flashing bootloader but it didn't work and gave same error.
I tried stock recovery and other recovery found on net for my nexus 7 but they failed to flash with same error.
I haven't yet tried running fastboot-windows.bat which Google provides for installing FULL factory image, because i was afraid of losing my data.
Oh and i forgot to mention, that time when i tried flashing stock bootloader from Google, it gave an error, and then i saw in bootloader spamming messages something like CRC partitions missing...
I don't know what to do anymore, I would like not to lose my data. I have some important data on my Nexus 7 and i would either want to backup data somehow before flashing new rom/that stuff or i would like to flash stock rom without losing my data...
If you have important data on your device you also have a backup of it, haven't you?
Beside that, to get a backup from your device you need to get at least a recovery working. If you cannot flash a recovery, but you are in fastboot mode, you can try
fastboot boot recovery.img
in that case the recovery image is not flashed to the device, but started only. If everything is fine then in the next step I would do a nandroid backup directly to a usb stick connected by an OTG adapter. In that case you will be able to either extract your data from the nandroid files or for further experiments restore that device state.
If the recovery image fails to boot it wil lbe very difficult to get your data.
Hello, I have tried booting stock recovery, now i see picture of android opened but with red (!) sign... should i try booting custom recovery instead?
edit: tried booting clockwork recovery, even though it gave lots of errors that it can't open or mount stuff...
so how do i proceed now to backup the files and install new factory image without losing that backed up data?..
also there's a little problem, i got a 32gb version and like 30 gb is occupied... that means that there simply wont be space for backup? or i could format something like system because i don't really need it if it doesn't boot up to it anyway?
edit2:
i have noticed that no matter if in bootloader or in recovery, restarting bootloader doesn't seem to work, tablet stays on but there is no screen and fastboot doesn't detect it, so i have to manually power it off..
other thing i noticed is, i tried doing some harmless stuff like wiping dalvik cache, that refused to work, when i selected it it would just re-open the advanced menu in which i was in already
tried formatting /cache and it shut off the screen and before it did that it gave all those errors which i had when i opened recovery, that it can't open and mount stuff...
I don't know whether clockwork supports OTG-USB sticks, otherwise I would give TWRP a try ...
To do a backup, connect the USB-stick, select backup, select OTG as target for the backup and then start the backup and keep the fingers crossed ...
If everything goes well you will have a backup of your device in the USB-stick ... which then later on can be uncompressed / extracted / etc. but first you will need to get it before you can continue with installing a new ROM or a factory image
twrp seems like a pretty great and better recovery than clockwork, and i have discovered some things
back in clockwork mod before booting twrp, i tried 'install from zip' function just to see whats on my tablet, but it said that it failed mounting /sdcard...
after booting twrp i've discovered that adb works which means that i can pull files from my tablet to my pc which is even better solution than otg usb but when i tried doing:
adb pull /sdcard C:/N7BCKP
it said that 0 files are extracted.... could it be that all of this boot failure, and all of this was caused by some malware which wrecked havoc on my tablet?
i have tried pulling / instead of /sdcard but that doesn't seem to do much because more or less what i get is protocol not found
edit:
i have tried running adb shell command and then cd sdcard and then tried ls to list files, but nothing listed.... are my files gone for good?
edit2: twrp says Internal Storage (0 MB) .........
if my files are gone for good... can you please tell me how i can flash new factory image with bootloader, recovery and that stuff? because previously when i tried to flash just 1 file (recovery) it gave an error of not being able to write it, and then bootloader froze... im afraid of that happening again
edit3:
not a single file is in any folder when looking through twrp....wtf, is this a malware issue?
edit4:
tried installing google factory image from twrp recovery, and it gave huge amount of red errors, all of them saying that it basically cant mount any single thing, list:
/data
/cache
/system
more details:
Failed to mount '/cache' (Invalid argument)
Erimary block device '/dev/block/platform/sdhci-tegra.3/by-name/UDA' for mount point '/data' is not present!
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/system' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
Failed to mount '/data' (Invalid argument)
// then couple of times says above line but with /cache, /data, /system
Installing zip file '/usb-otg/nakasi-lmy47v-factory-5a0bb059.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Invalid zip file format!
Error installing zip file 'my hands hurt from writing this all down, and its up above'
Updating partition details...
Failed to mount /system, /cache, /data (Invalid argument)
...done
Hmm ... looks to me as if your memory is broken ...
AndDiSa said:
Hmm ... looks to me as if your memory is broken ...
Click to expand...
Click to collapse
but how did all of that happen? is there a way to fix this?...
i tried step by step executing via console what fastboot-windows.bat does when it install factory image from Google, but when i came to flashing bootloader, this happened
C:\Users\DH312\AppData\Local\Android\sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.img
target didn't report max-download-size
sending 'bootloader' (2100 KB)...
OKAY [ 0.268s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.405s
I can still do adb push and adb pull commands, would it be possible to open .img files from factory images, and extract folders such as sdcard, root, system, etc, and so on and then do adb push to my tablet and then reboot?
i have tried looking how to open .img files but nothing worked
No, no chance ... /root, /sdcard, /system are only mount points within the boot image and they are existing only after the device is started. But you are getting those error messages independently whether you are booting the ROM or a recovery image. This is an indication to me that there is some bigger problem with your device, most likely hardware related.
Oh so it's permanently dead... meh but thank you for helping me out even though the issue was hardware related so we can't do anything about it
Before you throw the tablet away you probably would like to try to format the internal partitions, either by using fastboot erase or by formating the /data, /cache, /system, etc. from within TWRP. This will *erase* all your data, but probably it will help to recover your device ...
If it really is dead, you can probably sell it on ebay for parts such as the screen.
Sent from my LGLS992 using Tapatalk
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
frederickrl said:
Hello guys, I ran into some trouble by trying to reset my phone to stock firmware. I followed this guide https://forum.xda-developers.com/showthread.php?t=2759495 but with the moto e4 firmware, now it bootloops to erasing and bad key. Please help, it doesnt let me boot into recovery
Click to expand...
Click to collapse
Update, I was able to boot into twrp, currently attemtping to flash a rom
similar problem: recovery loop
frederickrl said:
Update, I was able to boot into twrp, currently attemtping to flash a rom
Click to expand...
Click to collapse
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Fussloseskriechtier said:
Hello,
this is my situation:
- switchin-on my new moto e4 (XT1762)
- boot into recovery (TWRP)
- in TWRP, I am able to 'work', i.e. install LineageOS 15.1 (this is my main goal)
--- I WIPE
--- I INSTALL the lineage ZIP file (lineage 15.1 20180310 unofficial woods
--- I REBOOT
BUT, sadly, the reboot is done again into TWRP.
The installation of lineageos did not report any error.
How can I check, that what I've installed so far (TWRP and magisk) is correct and working?
Did I forget something? E.g. do I have to install GAPPS as well? Or Magisk? Or SUperSU?
Shall I try another custom ROM? Or another version of lineageOS? (Oh, yes, I tried Lineageos 15.0, but I got 'ZIP error'.
Thanks for your help!
Click to expand...
Click to collapse
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
TWRP loop
frederickrl said:
I imagine you are having the same problem that I was having. This is what I think happened, there is a particular partition which TWRP fails to erase, if this is the case I believe you are able to boot into the device by hitting start in the bootloader, hold volume down and power then select start. Tell me how it goes
Click to expand...
Click to collapse
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
I have no other recommendations as to what to do. Just flash stock firmware with rsdlite and everything will be back to normal, if you have any data that you need to back up you can use TWRP to transfer the files to a PC
Fussloseskriechtier said:
Thanks for this hint, frederick.
Unfortunately, it did not work.
I rebooted to bootloader mode, then I pushed 'DOWN' and 'POWER' for several seconds - but I could not select anything - display was switched off and the device rebooted to TWRP again.
That's strange, because yesterday I've got this 'MENUE', when pushing 'DOWN'&'POWER' for selecting FACTORY, RECOVERY, ... but this does not appear now.
More facts (it might help):
- After switching on the the device, I get this 'Orange state' message.
Perhaps any other hints?
Click to expand...
Click to collapse
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
madbat99 said:
In twrp select reboot bootloader. In bootloader, tap volume until you see "start". Tap power. Do not try holding buttons together in bootloader. It doesn't do anything. Single taps.
Click to expand...
Click to collapse
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Fussloseskriechtier said:
After "REBBOT BOOTLOADER" in TWRP, I get a black screen, where (on the very bottom) there are two lines: => FASTBOOT mode
=> device unlocked
Tapping or holding the volume&power buttons does not work in this state.
As mentioned before, by any reason I do not have this nice menue anymore, the one with RECOVERY, START, ...
So this could be the problem, right? Is my bootloader not working properly? Which part is telling the device to startup either in TWRP (=recovery) or into the Bootloader/System?
Mmmmh....
Click to expand...
Click to collapse
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
madbat99 said:
Fastboot mode is bootloader. Why the options aren't there I couldn't tell you. I see you flashed a rom for woods. Do you have the mediatek version? Hopefully you didn't flash wood stuff on a Perry device. Bootloader may be different. I have Qualcomm. Was that option ever there in fastboot mode?
This is how to fix the recovery loop. And possibly boot you in to whatever is left of your os.
Click to expand...
Click to collapse
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Fussloseskriechtier said:
Thanks again for your hints!
First of all, my device variant is XT1762, i.e. woods. I did not use PERRY software.
The bootloader options (RECOVERY MODE, FACTORY MODE, etc.) were there, but it seems I've somehow broken this peace of code... I believe this is the reason of my problems. Unfortunately I do not understand the Android boot sequence...
However, I tried >> fastboot erase misc << via terminal:
result:
erasing 'misc'...
FAILED (remote: partition table doesn't exist)
finished. total time 0.009s
I double checked it vie file manager in TWRP: there is no MISC folder.
It seems, my only option is to go back to stock ROM... :crying:
Click to expand...
Click to collapse
I think the partitions are different in mtk version. But I would try flashing stock.
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Fussloseskriechtier said:
Perhaps any other hints?
Click to expand...
Click to collapse
MiGri said:
I have exactly the same problem after trying to flash lineage 14.1 to my XT1762.
Unfortunately I have only a TWRP Backup of my stock system before the flash and recovering that didn't fix the problem.
Click to expand...
Click to collapse
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
I was able to get my phone back to work using https://forum.xda-developers.com/moto-e4/development/rom-original-stock-firmware-woods-twrp-t3766902
Stock ROM used to repair bootloader
Articul8Madness said:
I know what a pain in the ass my Perry variant was just to get the root going, so I can just imagine your frustration.
Did you guys take the update they're pushing out on the phones? Check. Some of the updates might be forced or you may accidentally said Okay and didn't realize it- that could be the reason why you're having trouble. The significant other got an update on the E4, and now can't do root.
Click to expand...
Click to collapse
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Fussloseskriechtier said:
Hello!
In the meantime I actually deleted everything and flashed the Stock ROM on my XT1762.
After that, my Bootloader menue (RECOVERY MODE, FACTORY MODE, START, ...) appeared again...
I felt lucky and started the whole procedure again: use TWRP, backup, delete Cache, Flash custom ROM, delete Cache, restart... and finally, I got lineageOS 15.1 and CrDroid running on my phone.
Now I use CrDroid, because LineageOS 15.1 did not Support my SIM Card... ? However, I am happy with CrDroid: fast, slim, nice looking, ...
So in the end, it seems that I deleted a specific part in my Flash which caused the "boot Loop". But I could repair it by flashing the Stock ROM again.
Thanks guys, you're doing a good Job!
Buy!
Click to expand...
Click to collapse
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
pancobe said:
I'm also stuck in boot loop... What directories/files did you delete? Have backup of stock rom, but restore fails:
This /data backup was made with f2fs file system! The backup may not boot unless you change back to f2fs
Failed to mount /data (Invalid argument)
TWRP says that file system of /data is ext4. Not possible to change or repair the file system in TWRP with Wipe / Advanced wipe / Repair or change file system. Result:
Error changing file system
or
/sbin/e2fsck -fp /dev/block/mmcblk0p27 process ended with error: 8
Phone is always starting in TWRP ending with:
Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
MTP Enabled
In terminal no problem to create (mkdir) and delete directories.
Flashing of lineage 14.1 or 15.1 for woods ends also with:
Failed to mount '/data' (Invalid argument)
This command in TWRP terminal didn't work:
fastboot erase misc
erasing 'misc'...
FAILED (remote: Partition table doesn't exist)
There is no misc folder.
Any ideas?
Thank you in advance!
Click to expand...
Click to collapse
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
frederickrl said:
Just flash stock firmware with rsdlite, it's the simplest way to go. Then if you'd like flash your rom
Click to expand...
Click to collapse
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Did following check:
mount /data
mount: '/dev/block/mmcblk0p27'->'/data': Invalid argument
e2fsck -n /dev/block/mmcblk0p27
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/mmcblk0p27
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>
Would it be safe to rmdir /data and mkdir /data ?
Thanks...
pancobe said:
Thank you for the hint on rsdlite, didn't know the program! Unfortunately I have two problems, have only access to an old XP box (I'm normally on a mac), and rsdlite doesn't recognise the phone, driver problem presumably... And the program doesn't recognise the format of the backup I made with TWRP...
Is it possible to repair the file system on the phone via terminal? Or to delete parts of the system safely and reinstall the stock system? The other guy apparently did something like that. Or to unpack a custom rom and place the parts via terminal so it can install on next boot?
Thank you!
Click to expand...
Click to collapse
Rsdlite is not meant to install your twrp backup. It's for installing the official firmware package. And you need to install moto drivers of course.
Hi folks,
I have a OnePlus 3T with LineagaOS installed with an encrypted system.
Today I finally decided to update my six months old LineageOS.
For that I had to install the new modem (V9.0).
After doing so TWRP showed "cannot mount data" (don't remember the exact message)
Not knowing what that means I just rebooted and entered my password. Then the system tells me "Your password is OK, but I cannot mount the data partition". (or any partition?)
I followd the advise to boot into boot mode and tried a
Code:
fastboot format userdata
which results in a
Code:
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
I have no clue how to solve this situation.
Any ideas?
EDIT:
Just for the ones having the same problem:
I fixed the problem with the following actions:
I booted into TWRP and tried to wipe all partitions;
The result was:
Code:
Full SELinux support is present.
MTP Enabled
Wiping Dalvik Cache Directories...
--- Dalvik Cache Directories Wipe Complete!
Formatting System using make_ext4fs...
Wiping data without wiping /data/media ...
Done.
Wiping internal storage -- /data/media...
Formatting Cache using make_ext4fs...
Updating partition details...
...done
After that , just out of curiosity I tried to repair all the file sytems, which almost worked.
When I try to repair "Internal Storage" or "Dalvic Cache" I get an error: "Invalid partition selection".
When I change into the file manager I can see all kinds of directories but no files.
Next I tried to install the modem, which was successfull.
Next I tried to flash LineageOS which failed with "mkdir /cache/recovery". I changed into the file manager and the directory was there. I flashed the system a second time, and now it finished with success.
Flashing gapps also finished with success.
System resurrected
applause
very good bro
Hi,
I have an international 6t and trying to install Lineage 18.1. After the following steps, I get the qualcomm crash dump error:
- Use MSM to install: ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222
- System Update to latest version of OOS: 11.1.2.2
- Unlock bootloader (tried via both ADB and TOOL ALL IN ONE)
- Flash: twrp-installer-3.6.0_9-0-fajita (tried via both ADB and TOOL ALL IN ONE)
- Qualcomm crash dump error
Am I doing anything wrong? I have looked at different guides and seems to be the right steps.
I also tried using MSM to install an older (9) ROM and didn't uprade. Found here that I could get TWRP working... However, after flashing Lineage Rom I got stuck in fastboot loop.
Some hours later...
OK, so I just tried it again, following this guidance exactly (and with Lineage Recover rather than TWRP) : https://lineageosroms.com/fajita/
Without TWRP I didn't have the crash dump error... but when I came to finally Reboot the System, I got another error:
Can't load Android System. Your data may be corrupt......
Then with this text at the bottom:
E: Failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
E Emulated failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
Any help very much appreciated!
benh77 said:
Hi,
I have an international 6t and trying to install Lineage 18.1. After the following steps, I get the qualcomm crash dump error:
- Use MSM to install: ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222
- System Update to latest version of OOS: 11.1.2.2
- Unlock bootloader (tried via both ADB and TOOL ALL IN ONE)
- Flash: twrp-installer-3.6.0_9-0-fajita (tried via both ADB and TOOL ALL IN ONE)
- Qualcomm crash dump error
Am I doing anything wrong? I have looked at different guides and seems to be the right steps.
I also tried using MSM to install an older (9) ROM and didn't uprade. Found here that I could get TWRP working... However, after flashing Lineage Rom I got stuck in fastboot loop.
Some hours later...
OK, so I just tried it again, following this guidance exactly (and with Lineage Recover rather than TWRP) : https://lineageosroms.com/fajita/
Without TWRP I didn't have the crash dump error... but when I came to finally Reboot the System, I got another error:
Can't load Android System. Your data may be corrupt......
Then with this text at the bottom:
E: Failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
E Emulated failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
Any help very much appreciated!
Click to expand...
Click to collapse
You should have already know by now that TWRP version is not compatible with OOS11.
You can try to restore your Phone with MSM tool and try again with this version [file attached]
Thanks
s.seila said:
You should have already know by now that TWRP version is not compatible with OOS11.
You can try to restore your Phone with MSM tool and try again with this version [file attached]
Click to expand...
Click to collapse
Thanks, I just tried with this... although with TWRP I am unable to switch on ADB Sideload. It just times out forever.
With Lineage Recovery instead of TWRP I could use ADB, although got other errors as in initial message.
benh77 said:
Thanks
Thanks, I just tried with this... although with TWRP I am unable to switch on ADB Sideload. It just times out forever.
With Lineage Recovery instead of TWRP I could use ADB, although got other errors as in initial message.
Click to expand...
Click to collapse
I thought sideload worked on that twrp. But you can try booting that twrp then install lineage recovery or another version of twrp from twrp.
Thanks, I think there is an underlying issue with my phone or I am just out of my depth. Pretty much followed every set of instructions I can find and always results in a bricking, bootloop or qualcomm crash dump. Was a second hand phone, so just got it back to 11.1.2.2 and will re-sell.
Got my trusted Z5 Compact onto 17.1 and that will do me for a few years yet!