Develop Bugs

[Q] Failed 4.1.1 flash; please help!

Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted since, after I factory reset and cache wiped my 4.1.1, I get passes on Odin whenever I try to install 4.1.1 again, which is all I wanted to do so I could try to upgrade to 4.3, but I never got that far. I just can't get 4.1.1 working again after a factory reset cache wipe.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.

Pfhyde said:
Hi all--apparently I "softbricked" (or "soft bricked") my unlocked at&t s3 (SGH-I747) that I rooted myself, later, since I get passes on Odin whenever I try to install new firmwares, so I don't have the same problem those trying to roll back to 4.1.1 after failing to get 4.3 going, since in my case, I just can't get 4.1.1 working again after a factory reset cache wipe. I wanted to put a stock 4.1.1 on so I could try to update to 4.3, but I never got far enough to even try that.
What happens, now, is that my phone just can't get past the pulsing blue samsung logo after rebooting into any new 4.1.1 firmware I load with Odin (and I tried a few options--both stock SGH-I747 4.1.1 and the one here), or root66, but my phone just gets stuck on the pulsing blue samsung logo and stops there every time. Kies can't connect to my phone any longer, either, and it won't recognize my phone for a firmware reset, and my computer will no longer recognize my phone nor successfully install drivers for it when it's trying to boot (when I connect my phone in recovery or download mode, however, my computer will install a driver to let the computer see the phone, but I can't actually do anything with the phone after that--and Kies doesn't connect after the computer installs these drivers, either).
So, in sum: I can successfully flash 4.1.1 stock/alternatives with Odin ("pass!") but that doesn't get me past the pulsing blue samsung icon. I think I've tried to flash a new boot partition during this process, but I'm not sure. Any advice would be much appreciated, since I've been working on trying to fix my phone for a day and a half now without any luck
Slight update: I installed CWM Recovery (PhilZ Touch) and wiped again but after loading the 4.1.1 stock/alternative (above link) my phone--still--won't get past the pulsing blue samsung logo still.
Additional info.: when I boot in recovery mode after flashing the above root66 rom, I get the following errors:
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E:failed to mount /data (Invalid argument)
Also, I just noticed when I try to factory reset again it says this:
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
etc.
Thanks for taking the time to read this. I appreciate it very much. I honestly can't do anything until I get help here.
Click to expand...
Click to collapse
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.

mstrswrd06 said:
If you're just looking to get back to stock 4.3, you can use this:
http://forum.xda-developers.com/showthread.php?t=2496425
You'll need the Heimdall suite:
http://glassechidna.com.au/heimdall/
Once the drivers and all are there, use the Flash tab in Heimdall and attach each file appropriately.
I had to do this same process recently so feel free to hit me up if you have an issue.
Click to expand...
Click to collapse
Well, I haven't ever had 4.3 on my phone, so there's nothing to 'get back' to. I was wanting to upgrade to 4.3, but then my factory reset/cache wipe made my phone unbootable after installing 4.1.1 firmware roms. If you think I should just try to install 4.3 in the state my phone's in now, then okay--but that seems to possibly introduce other problems, from what I've been reading elsewhere.

Did you get the stock 4.1.1 firmware from sammobile.com?

audit13 said:
Did you get the stock 4.1.1 firmware from sammobile.com?
Click to expand...
Click to collapse
Yes, as it turns out I did that already--I recognized the site immediately. I downloaded the default at&t rom again and will try flashing it (again) in the morning, but I doubt anything new will happen.

Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.

audit13 said:
Try flashing 4.1.1 again in Odin, uncheck everything except F. Reset. When you see reset in the status windows, remove the USB cable, remove, the battery, replace the battery, go into recovery, perform a full wipe, then reboot. Do a full wipe before you first boot the newly-installed OS may fix the issue.
Click to expand...
Click to collapse
First, when I go into recovery after flashing 4.1.1 default for at&t (though my phone is unlocked and was rooted--don't know if the root is still there after all that's happened) it says right away
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
#Manual MODE#
--Appling Multi-SCSC...
Applied the CSC-code:ATT
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data'(Invalid argument)
E: etc.
Then, when I try to wipe it gives me an error:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
Data wipe complete.
Then rebooting freezes on pulsing blue samsung logo--again

Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.

audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
It says
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Sorry for my belated responses, but I work late on the weekends in NZ.

audit13 said:
Did you flash an updated bootlaoder? Boot into download mode and let us know what it says on the screen.
Click to expand...
Click to collapse
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.

Glad you got your phone working. You do not have the 4.3 bootloader and, if I were you, I would not install the ATT 4.3 OTA update. This will install the 4.3 bootloader which makes it more difficult to get back to stock.

Pfhyde said:
Strange--I just booted up in recovery mode and wiped again; this time I got no errors, so I rebooted and--it works now in 4.1.1. Why it never wiped altogether before, when I didn't do anything different, is confusing; but there you have it. Now I'll venture into trying to get 4.2 or something.
Thanks all for your patience and help, even though in the end it worked on a fluke.
Click to expand...
Click to collapse
Some people have no problems at all, but CWM has a history of not wiping properly. That's why I don't using it anymore. There always came a point when it just would not wipe properly.

[Q] Bricked Nexus

Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
EDIT: Fixed, formatted data as ext2, ran e2fsck, then formatted as ext4 again, then flashed userdata.img, system.img, and boot.img in fastboot.

CraftedAndroid said:
Hello. Today I flashed the factory image of Marshmallow without much problem. But when I installed MultiRom, problems started to arise. When I tried booting to the primary rom, it took me to recovery. I thought a reflash of the factory image would remove MultiRom. Apparantly I thought wrong. I kept trying to flash system and userdata, but to no avail. Now the system bootloops at Google, and I cant mount /data. I still have access to recovery and bootloader, but TWRP displays Internal Storage as 0MB. Does anyone know how to solve this? It would be very, very appreciated.
Click to expand...
Click to collapse
Try using the Nexus Root Toolkit by Wugfresh to unbrick.
It will automatically install the latest stock firmware, making your device as good as new.
Just boot into bootloader mode, plug the device into a computer, open up the program, click "flash Stock", and watch as the magic happens.

Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!

alexfone said:
Having a similar problem - powering on the tablet either leads me to TWRP (with all sorts of error messages like below) or it simply sits at the google screen, in excess of 30min.
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/misc'
E: Primary block device '/dev/block/platform/msm.sdcc.1/by-name/userdata' for mount point '/data' is not present!
E:Unable to find mount '/data/'
E:Unable to recreate /data/media folder.
E: Unable to find partition size for '/sbl1'
E: Unable to find partition size for '/sbl2'
E: Unable to find partition size for '/sbl3'
E: Unable to find partition size for '/tz'
E: Unable to find partition size for '/rpm'
E: Unable to find partition size for '/aboot'
E: Unable to find partition size for '/sbl2b'
E: Unable to find partition size for '/sbl3b'
E: Unable to find partition size for '/tzb'
E: Unable to find partition size for '/rpmb'
E: Unable to find partition size for '/aboobtb
E: Unable to find mount '/system'
E: Unable to find mount '/data'
E: Unable to find mount '/cache'
....
E: Unable to find mount '/data/media/TWRP/.twrps' when trying to read settings file
Attempts to wipe in TWRP fail. Attempts to use Nexus Toolkit to
Attempted using Nexus Toolkit to do stock un-root/flash (of 4.4 - 6.0), flash other recoveries, or anything besides /boot and bootloader all fail.
I am still unlocked, was previously rooted (and happy) before this trouble started when attempting to flash the stock recovery, which has never been successful.
Bootloader is flo-4.05, I have also seen 4.02.
Now I'm staring at a bricked device. Is this similar to what you see, CraftedAndroid? Any help would be much much appreciated!!
Click to expand...
Click to collapse
I'm looking much better than you. I only cannot mount /data and anything under it, like /data/media. Yours looks a bit irreversible if I've ever seen irreversible.

Fixed, updating OP

hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: DEB-Z00_2.44.0_0213
Serial Number........: 09e4b977
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (7448 KB)...
Click to expand...
Click to collapse
some attempts from fastboot flash also ends up with failure
any ideas?

fr3ker said:
hello,
i'm having similar problem . I upgraded to 6.0 manually from 5.1.1 via the flash-all method and stucked in bootloop.
it wont boot even after a data wipe.
so
i tried the method fastboot erase boot, recovery, system etc
after a restart it wont boot to anything else but the bootloader.
tried reflashing through various methods it just wont work
here is where its stuck
some attempts from fastboot flash also ends up with failure
any ideas?
Click to expand...
Click to collapse
Try doing fastboot flash userdata userdata.img, fastboot flash system system.img, and fastboot flash boot boot.img in that order.

i did that too, I tried flashing tru a lot of method ... it just wont boot at all
does it have anything to do with the partitions? i cant find how to repair a partition for Nexus devices ...

^ So what's it say when you flash each .img individually? You get the "OKAY"?
You say some end in failure which ones? Throw in a fastboot format cache for the hell of it. Your bootloader and baseband are correct?
If you're getting the okay on all images and wiped everything in stock recovery.. I don't know man I might be stuck.
If you figure it out let us know. We can erase and format the partitions, usually you don't even need to use those. Hmm.. I clean flashed flo with just boot system and userdata (bootloader stayed the same as 5.1.1). Worked perfect.

Seems that we're stuck ... I've flashed a custom ROM and works perfect but when I flash any stock firmware it'll stuck at the bootani ... Flashing process were cleared until end ... I get everything as expected. I did everything founded on google and it's still fcuked up ..
Sent from my Z1 using Tapatalk

Problem with Wipe in TWRP Recovery

Hello together,
I wanted to try the CM13 nightlys on my Desire HD.
I installed the TWRP recovery with aceopt and tried to wipe (normal wipe, not advanced)
I always get an error:
E:Unable to mount '/data'
Repairing Data before resizing
Repairing Data using e2fsck...
E:/sbin/e2fsck -fp process ended with ERROR=16
E:Unable to repair '/data'
E:Error repairing file system
What could I do...?

same here,
some help plz

As far as I am aware you need to install the latest version of twrp v2.8 as earlier versions are not compatible with marshmallow.

mkward said:
As far as I am aware you need to install the latest version of twrp v2.8 as earlier versions are not compatible with marshmallow.
Click to expand...
Click to collapse
Thanks! TWRP v.2.8.7 solved the problem. :good:

Hi,
I want to install the CM13 nightlys on my Desire HD.
I installed the TWRP v.2.8.7.0 recovery with aceopt and tried to wipe.
I have this error: E:Unable to mount '/data'
In Mount menu, I can't select Data nor SD-Ext.
In Install menu, Storage said : Internal Storage (0 MB) and when try to install CM13 nightly error message Unable to mount '/data.
Thanks for your help.

[NEED HELP] TWRP wiping + flashing ERROR, Bootloop

hello,
does someone know what problem i have and how i should fix this?
first of all, when i was wiping my phone it all went fine but it took to long so i turned off my phone and turned it back on, i got in an boot loop and couldnt even get into recovery mode because that would also led me into a ''teamwin'' bootloop, anyway i reflashed my recovery so luckily i can get back into recovery, but i still have bootloop for the system so i cant start up, but now i also face this problem.
i wanted to flash stock rom and this is the full error log i get ( i also tryed with custom rom but same problem)
_____________________________________________________________________________________________
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I also tryed wiping my phone, i tryed advanced wipe and full wipe and also factory reset, but i always get this same kinda error.
anyone know a fix for this?

Which version of twrp do you use?

i use Twrp 2.8.7.3

Try the last one : https://dl.twrp.me/Z00A/twrp-3.0.0-0-Z00A.img.html
Your zenfone 2 is WW or CN?

its CN

sorry for the kinda late answer tho,
well i wanted to flash the 3.0 twrp version, but it gives me an weird kind of bootloop, so thats why i downgraded to 2.8.7 :/

that's strange, are you sure it was for Z00A?
Look at this : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 to change to WW version.

Need help flashing my Mi Mix 2

Hey guys,
im completly new to this flashing thing an i think i made a big mistake.
I tried to flash a new miui version (Global) via the already installed TWRP on my phone.
But that didnt quiet work, after the installation it just booted back in TWRP and i couldnt get the phone to do otherwise.
I googled a bit and found this tool called MIFlash (ver. 2017.4.25.0)
i also downloaded the fastbood rom from the Offical miui site and saved it on C: in a folder called rom
So i put the Phone into Fastboot and tried to flash it with MiFlash but in the end i got an error ( error:FAILED (remote: Check CRC failed))
And after that i couldnt even wipe the Data via TWRP i got an error there too
"Could not mount '/data' and unable to find crypto footer."
"Failed to mount '/data' (invalid argument)"
"Unable to recreate /data/media folder"
"Unable to mount /data/media/TWRP/.twrps"
"Unable to mount Storage"
PLS HELP!!!! :crying: