Database Info

[Q]Can't connect to sim, can't mount persist ,Camera Error, Can't flash android L img

I am not sure what did I do wrong on my nexus 5 but i suddenly get tons of errors
1.Every boot i get camera has stopped and I cant connect to camera
2.Seems like the device can't recognize the sim card
3.In recovery it can't mount persist
4.Baseband version is unknown
5.When i flash android L image the device get stuck in the google boot icon
6.I tried flashing android 4.4 image from bootloader five times, I tried flashing 4.4.4 image from bootloader a couple of times I keep getting the same errors above
7. I tried flashing custom roms such as paranoid android , cyanogenmod and miui, paranoid android causes the problems above, cyanogenmod can't be flashed, it gives a can't mount /persist error in recovery and miui causes all problems above + system uids inconsistent error
I tried flashing cache.img
Please help

Try also manually formatting data from your stock recovery once you have fastboot flashed userdata.img

rootSU said:
Try also manually formatting data from your stock recovery once you have fastboot flashed userdata.img
Click to expand...
Click to collapse
Did not work

Seems like a hardware issue to me as it looks like you've covered all possible bases. What errors do you get while flashing system, boot etc?

vin4yak said:
Seems like a hardware issue to me as it looks like you've covered all possible bases. What errors do you get while flashing system, boot etc?
Click to expand...
Click to collapse
I'm not getting error during installation of stock images but once it boot later it gives me all the error mentioned above

rosenpin said:
I'm not getting error during installation of stock images but once it boot later it gives me all the error mentioned above
Click to expand...
Click to collapse
If you've flashed all the img files successfully, go to recovery and perform a factory reset. If it still doesn't fix it.. Don't know what else to suggest

rosenpin said:
I'm not getting error during installation of stock images but once it boot later it gives me all the error mentioned above
Click to expand...
Click to collapse
Have you tried LG flashtool?

bitdomo said:
Have you tried LG flashtool?
Click to expand...
Click to collapse
I have d820 32gb and i can't find a working tut file for it

rosenpin said:
I have d820 32gb and i can't find a working tut file for it
Click to expand...
Click to collapse
https://mega.co.nz/#!ChQiyK4A!6CiOtwW82sriV2dDj1BV6dUO1gNXfcUiGC2fuPECkBw

bitdomo said:
https://mega.co.nz/#!ChQiyK4A!6CiOtwW82sriV2dDj1BV6dUO1gNXfcUiGC2fuPECkBw
Click to expand...
Click to collapse
That's the one i used it's just showing the ready screen and nothing happens.

rosenpin said:
That's the one i used it's just showing the ready screen and nothing happens.
Click to expand...
Click to collapse
Reconect the phone

bitdomo said:
Reconect the phone
Click to expand...
Click to collapse
Finished the installation all the former errors didn't go away

rosenpin said:
OK it worked
THANKS
The flashtool finished but now the phone shows black screen and the notification light blinks green
Click to expand...
Click to collapse
remove the usb cable, then wait until the greeen light dissapears then turn on your phone

bitdomo said:
remove the usb cable, then wait until the greeen light dissapears then turn on your phone
Click to expand...
Click to collapse
Finished the installation all the former errors didn't go away

rosenpin said:
Finished the installation all the former errors didn't go away
Click to expand...
Click to collapse
If you unlock bootloader or lock bootloader is the change reverts when you restarts your phone?

bitdomo said:
If you unlock bootloader or lock bootloader is the change reverts when you restarts your phone?
Click to expand...
Click to collapse
No, the changes are applied

rosenpin said:
No, the changes are applied
Click to expand...
Click to collapse
Then there is a chance it is just your persist partition, and not a semi-dead emmc.
Go to here. Do part 7, but use this command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist instead of e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
You have to perform it in recovery through adb shell

bitdomo said:
Then there is a chance it is just your persist partition, and not a semi-dead emmc.
Go to here. Do part 7, but use this command e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist instead of e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
You have to perform it in recovery through adb shell
Click to expand...
Click to collapse
I performed this action the terminal gives me this error
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/persist
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>
Click to expand...
Click to collapse

rosenpin said:
I performed this action the terminal gives me this error
Click to expand...
Click to collapse
Make a backup of your persist partition by this command
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/data/media/0/persist.img
the backup will be on the internal storage.
Send it to me to take a closer look at it.

bitdomo said:
Make a backup of your persist partition by this command
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/data/media/0/persist.img
the backup will be on the internal storage.
Send it to me to take a closer look at it.
Click to expand...
Click to collapse
sent

[Q] Nexus 5 stuck at screen of the eternally spinning balls

I'm going to start off by saying I'm the noobiest of noobs, so please be gentle with your replies.
I was watching Youtube on my Nexus 5 yesterday when it suddenly shut down and attempted to restart itself. I watched it go very slowly from the white Google logo to the colourful spinning balls screen, and it got stuck there.
Status right now:
Phone stuck at spinning balls screen
I can get to fastboot and factory recovery screen
Factory reset doesn't work
Power button appears to be working fine
Charging is fine and I can see the battery icon when it's off
Phone is not rooted, bootloader has not been unlocked
What I did so far:
Someone posted a thread with a similar problem and said to flash the factory image a few times, so I followed these instructions. Except to do that I need to unlock my (currently locked) bootloader first. I then tried to follow these instructions of unlocking bootloader, but got stuck at the last step of "fastboot reboot“ because my phone still won't get past the screen of spinning balls, no unlocking the bootloader for me. HELP!
This is what's at the bottom of the system recovery screen:
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
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: failed to mount / cache (Invalid argument)
E: Can't mount /cache/recovery/last_kmsg
E: Can't open /cache/recovery/last_kmsg
E: failed to mount /cache (Invalid argument)

So. Have you tried the fastboot commands to fastboot flash system system.img and boot and cache etc etc?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
So. Have you tried the fastboot commands to fastboot flash system system.img and boot and cache etc etc ?
Click to expand...
Click to collapse
I think I have, it didn't work because the bootloader is locked, and if I am able to unlock it right now, there would be no problem.

laughingcloud said:
"fastboot reboot“
Click to expand...
Click to collapse
Not surprising. We already know your phone won't boot and that what that command tries to do. Use the command "fastboot reboot-bootloader".

Wakamatsu said:
Not surprising. We already know your phone won't boot and that what that command tries to do. Use the command "fastboot reboot-bootloader".
Click to expand...
Click to collapse
Tried it, then when the fastboot screen came on, it's "Lock State - Locked" again.

laughingcloud said:
Tried it, then when the fastboot screen came on, it's "Lock State - Locked" again.
Click to expand...
Click to collapse
Not a good sign. Points to a physical problem, not software.

And you have done fastboot oem unlock yea?
Sent from my Nexus 5 using Tapatalk

Wakamatsu said:
Not a good sign. Points to a physical problem, not software.
Click to expand...
Click to collapse
Does that mean I have to take it to a repair shop? Or is it irrepairable?

Ben36 said:
And you have done fastboot oem unlock yea?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, the status shows as unlocked right after I do fastboot oem unlock, but as soon as I reboot it, goes back to locked again.

laughingcloud said:
Yes, the status shows as unlocked right after I do fastboot oem unlock, but as soon as I reboot it, goes back to locked again.
Click to expand...
Click to collapse
Yup, does sound like pooped nand. Nothing you can do about unlocking. But can you not flash the img's locked tho still as they're Google img's. I can't remember now
Sent from my Nexus 5 using Tapatalk

Phone Stuck on Cyanogen Logo

I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?

megamonkey said:
I was charging my phone when I noticed it restarted itself and then now it's stuck on the Cyanogen Logo screen.
I've gone into Recovery, pressed wipe data/factory reset but nothing actually happens. A bunch of stuff shows up saying
E:failed to mount / cache (Invalid argument)
E:Can't mount / cache / recovery /last install
E: can't open /cache recovery/last install
I tried pressing wipe cache partition, same thing
I pressed wipe media, same thing.
Reboot to bootloader, it just stuck on Fastboot logo.
I havn't done anything to the phone such as rooting or unlocking bootloader. I just left the phone as it is and only did system updates provided by Cyanogen.
Any idea?
Click to expand...
Click to collapse
You probably have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
You'll need to unlock your bootloader, which will wipe your device, but it's the only way. I have a guide here that explains how to unlock it (also how to install adb/fastboot and the drivers). Once you've unlocked your bootloader, put the persist file in your fastboot folder, open a command prompt from within your fastboot folder (shift + right click, then select open command prompt here), and issue these commands:
Code:
fastboot erase persist
fastboot flash persist persist.img
Once it's done flashing you can try rebooting your phone. If it still doesn't boot you'll have to go back to my guide and follow the instructions in section 8 to flash the stock images.

There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!

megamonkey said:
There's no way of saving my photos is there? I assume no...but might as well ask.
Thanks so much for the help!
Click to expand...
Click to collapse
Unfortunately not if you can't boot into the OS.

I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?

megamonkey said:
I typed: fastboot oem unlock
It says OKAY
So when I type: fastboot oem device-info
<bootloader> Device tampered:true
<bootloader> Device unocked: false
<bootloader> Charger screen enabled: false
I assume something went wrong?
Click to expand...
Click to collapse
Yeah, this happens sometimes. I can only suggest you try again in the hope that it works, without the bootloader unlocked there's gonna be nothing you can really do.

So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...

megamonkey said:
So I keep typing it till it shows true for "Device unlocked"?
I typed it 4 times now....it still doesn't say Device Unlocked True...
Click to expand...
Click to collapse
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.

Heisenberg said:
It isn't going to work. You're only other option is to try this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
I know you're not hard-bricked but this is likely your only chance to get the phone working again.
Click to expand...
Click to collapse
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?

megamonkey said:
I'll try doing all over again one last time. But I was reading the guide you gave me, it says it won't work on soft-brick, will it still work tho?
Click to expand...
Click to collapse
I'm pretty sure others in similar situations to you have used it, I could be wrong.

Heisenberg said:
I'm pretty sure others in similar situations to you have used it, I could be wrong.
Click to expand...
Click to collapse
I tried using the method but I'm not sure why it isn't working. I ran the program and it gave me a few problems letting me know what's wrong with my phone:
userdata_64G.img: FAILED
boot.img: FAILED
persist.img: FAILED
recovery.img: FAILED
system.img: FAILED
I'm running near the end where nothing is going my way and I may need to either ask someone to attempt to fix it or buy a new phone...

Bricked Nexus 5, can't get it to work.

My N5 decided suddenly the other day to stop working. I held it, it turned off and on and then the boot animation just continued. I have googled and tried everything I can but it seems to go wrong someplace every time. I tried to wipe it from recovery mode but then it gave this as "error message".
-- Wiping data...
Formatting /data...
E:Failed to mount /cache (Invalid argument)
Formatting /cache
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
E:Can't open /cache/recovery/last_log
E:Failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
Data wipe complete (but it's not really done it seems) and then this repeats:
E:Failed to mount /cache (Invalid argument)
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
E:Can't open /cache/recovery/last_log
E:Failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
Click to expand...
Click to collapse

is this clockworkmod recovery?

androidcues said:
is this clockworkmod recovery?
Click to expand...
Click to collapse
No. Have not used that or am not familiar with it.

Numite said:
No. Have not used that or am not familiar with it.
Click to expand...
Click to collapse
is your device even root?

Is the phone running a stock or custom recovery such as TWRP?
You may have to try flashing a stock ROM but that will require an unlocked bootloader.
Being rooted should not cause a problem with formatting the data and cache partitions.

audit13 said:
Is the phone running a stock or custom recovery such as TWRP?
You may have to try flashing a stock ROM but that will require an unlocked bootloader.
Being rooted should not cause a problem with formatting the data and cache partitions.
Click to expand...
Click to collapse
Yea it is running custom recovery TWRP, was a long time since I played around with this. The bootloader is unlocked if it is "LOCK STATE - UNLOCKED" is bootloader. I don't know why it doesn't work, but I belive the problems is that the mobile can't find cache. Will take it to service and if it isn't my fault it will be covered by the shop. So regarding the last thing, do I have to lock the bootloader or do the warranty work anyways? I'm a noob at this just FYI

Numite said:
Yea it is running custom recovery TWRP, was a long time since I played around with this. The bootloader is unlocked if it is "LOCK STATE - UNLOCKED" is bootloader. I don't know why it doesn't work, but I belive the problems is that the mobile can't find cache. Will take it to service and if it isn't my fault it will be covered by the shop. So regarding the last thing, do I have to lock the bootloader or do the warranty work anyways? I'm a noob at this just FYI
Click to expand...
Click to collapse
You should download "Nexus Root Toolkit" to your PC. There is a function in the Advanced Menu tha will allow you to fix a boot loop/soft bricked.
I hope that helps
---------- Post added at 08:00 AM ---------- Previous post was at 07:50 AM ----------
Here is the link to the "Nexus Root Toolkit"
go search google for the Wugfresh. com site
It's a great source....

I'm not sure but locking the bootloader may not make a difference for warranty if the phone has TWRP installed.

Have you tried using the Nexus Root Toolkit? There is an option to restore factory and unroot, with a bricked unit. This helped me once, although not with your particular problem.

I had same issue with MOTO G 2014. Motherboard replaced on warranty. I suppose there was prob;lem with flash memory.

Bigbossradio said:
You should download "Nexus Root Toolkit" to your PC. There is a function in the Advanced Menu tha will allow you to fix a boot loop/soft bricked.
I hope that helps
---------- Post added at 08:00 AM ---------- Previous post was at 07:50 AM ----------
Here is the link to the "Nexus Root Toolkit"
go search google for the Wugfresh. com site
It's a great source....
Click to expand...
Click to collapse
I have already tried to use that option and have used Nexus Root toolkit before. Will give it another shot though. Will update.
Run 1:
Flash stock + unroot. Device os soft-bricked/bootloop
Chose Android 4.4 as the image to flash. No problems so far.
ADB device not found.. Aparently I can't do it because USB debugging seems to be off, but I can not access settings to change it...
Run 2: Flash stock + unroot. Device os soft-bricked/bootloop
Chose Android 4.4 as the image to flash. No problems so far.
Here is the cmd log. http://imgur.com/uR2KntS
Writing bootloader failed
Writing radio failed
Writing boot good
Writing cache failed
Writing recovery failed
Erasing system failed
http://imgur.com/BLmHMBx
Waited 20 mins: this pops up
http://imgur.com/biXRFOL
and then this
http://imgur.com/Gvqi0Zz
and meanwhile the phone just tries to boot but can't even after this....

Numite said:
I have already tried to use that option and have used Nexus Root toolkit before. Will give it another shot though. Will update.
Run 1:
Flash stock + unroot. Device os soft-bricked/bootloop
Chose Android 4.4 as the image to flash. No problems so far.
ADB device not found.. Aparently I can't do it because USB debugging seems to be off, but I can not access settings to change it...
Click to expand...
Click to collapse
Your best bet is to get a fast boot cable and use direct fastboot commands

Try using the flash-all batch file using a pc with the phone in fastboot mode. If that doesn't work. If that still doesn't work, it may be that the emmc in the phone is damaged.
What is a fastboot cable? I've got a couple of nexus 5 motherboards with booting problems. It would be great if I could fix them. Thanks.

bricked nexus 5
hey guys, my phones bricked to the max due to an update to cm13. here are all the issues:
-settings doesnt work, at all
-google play services doesnt work, like not even installed on phone anymore
-status 255 when i try to flash any update
-factory wipe fails
-wipe cache partition fails
so i looked online about what status 255 is and people were saying to flash a new super su to the phone, so i tried that, and now the phone doesnt boot up. so i dont know what my options are now that i cant put any files onto the devices from pc because it wont boot, and flashing from recovery doesnt work.
any ideas?

Corneliusvinyo said:
Your best bet is to get a fast boot cable and use direct fastboot commands
Click to expand...
Click to collapse
Could you explain what those are and best way to get one that will work for sure?

Numite said:
Could you explain what those are and best way to get one that will work for sure?
Click to expand...
Click to collapse
You can order one online .. It looks like a USB cable .. When it is connected to your device it immediately boots it into fastboot mode
---------- Post added at 07:05 PM ---------- Previous post was at 06:40 PM ----------
Are you able to boot into recovery ?

ozAztekk said:
hey guys, my phones bricked to the max due to an update to cm13. here are all the issues:
-settings doesnt work, at all
-google play services doesnt work, like not even installed on phone anymore
-status 255 when i try to flash any update
-factory wipe fails
-wipe cache partition fails
so i looked online about what status 255 is and people were saying to flash a new super su to the phone, so i tried that, and now the phone doesnt boot up. so i dont know what my options are now that i cant put any files onto the devices from pc because it wont boot, and flashing from recovery doesnt work.
any ideas?
Click to expand...
Click to collapse
Your best bet would probably be to flash back to a completely stock ROM and start over with CM. Be aware of the fact that flashing back to stock will require wiping the data partition.

audit13 said:
Your best bet would probably be to flash back to a completely stock ROM and start over with CM. Be aware of the fact that flashing back to stock will require wiping the data partition.
Click to expand...
Click to collapse
thanks man, i found a tutorial for doing it using fastboot.exe and im back to 6.0.1 now, just have to get back to cm. thanks again and hello from hamilton.

Glad you got your problem solved. Greetings from Toronto.
I will have to look into a fastboot cable. I heard about fastboot cables when I have a Motorola Atrix HD.
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
I see factory fastboot cables for certain Motorola devices but none for the LG. Are these factory cables universal?

audit13 said:
Glad you got your problem solved. Greetings from Toronto.
I will have to look into a fastboot cable. I heard about fastboot cables when I have a Motorola Atrix HD.
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
I see factory fastboot cables for certain Motorola devices but none for the LG. Are these factory cables universal?
Click to expand...
Click to collapse
I'm not sure they are

partition corrupted. Need help?

This is my friend's phone and when she showed me, it was asking for android's password with the title "Decryption unsuccessful".
I then tried mi-flash and it didn't gave any errors but when it rebooted it went to fastboot screen. It was on latest MIUI7 stable when this happened. I tried formatting again from recovery, I got the below error logs.
/data, /system and /cache - (invalid argument)
Even recovery is gone and it only boots to fastboot screen. I can only go to recovery by doing
fastboot boot recovery.img (recovery is twrp 3.0.2-0) from fastboot.
I think the only possible way is to full format the partitions and bring it to stock but I am not finding any threads to point me to proper directions. Any one here care to help revive this mi4i.

warlord060816 said:
This is my friend's phone and when she showed me, it was asking for android's password with the title "Decryption unsuccessful".
I then tried mi-flash and it didn't gave any errors but when it rebooted it went to fastboot screen. It was on latest MIUI7 stable when this happened. I tried formatting again from recovery, I got the below error logs.
/data, /system and /cache - (invalid argument)
Even recovery is gone and it only boots to fastboot screen. I can only go to recovery by doing
fastboot boot recovery.img (recovery is twrp 3.0.2-0) from fastboot.
I think the only possible way is to full format the partitions and bring it to stock but I am not finding any threads to point me to proper directions. Any one here care to help revive this mi4i.
Click to expand...
Click to collapse
Anyway
Can i ask you,your friend using ext4 or f2fs??
I faced this issue if i format my data partition as f2fs at miui
Yeah, full format is good

faizauthar12 said:
Anyway
Can i ask you,your friend using ext4 or f2fs??
I faced this issue if i format my data partition as f2fs at miui
Yeah, full format is good
Click to expand...
Click to collapse
Thanks for replying.
I have the phone with me so I can answer queries right away. Its in ext4 format. Didn't tried f2fs. but the recovery I have, is not providing me f2fs file system type? How did you get that?
no idea, on doing full format. any thread links, please?

warlord060816 said:
Thanks for replying.
I have the phone with me so I can answer queries right away. Its in ext4 format. Didn't tried f2fs. but the recovery I have, is not providing me f2fs file system type? How did you get that?
no idea, on doing full format. any thread links, please?
Click to expand...
Click to collapse
here is a step
http://forum.xda-developers.com/showpost.php?p=35368127&postcount=7
about recovery here

faizauthar12 said:
here is a step
http://forum.xda-developers.com/showpost.php?p=35368127&postcount=7
about recovery here
Click to expand...
Click to collapse
I followed the format instruction and successfully formatted userdata, system and cache but when I went to recovery to wipe the partitions it again said the same thing (Failed to mount '/system' (invalid argument) and the same error for cache and data.

warlord060816 said:
I followed the format instruction and successfully formatted userdata, system and cache but when I went to recovery to wipe the partitions it again said the same thing (Failed to mount '/system' (invalid argument) and the same error for cache and data.
Click to expand...
Click to collapse
which recovery you're using?
why you wipe your system data and cache?
what do you want to do? (flash a rom,explain it )

faizauthar12 said:
which recovery you're using?
why you wipe your system data and cache?
what do you want to do? (flash a rom,explain it )
Click to expand...
Click to collapse
Recovery - twrp 3.0.2-0
Those mounts were not visible when I check the mounts using df command and for the above errors I tried to format as it showed successful operation.
I have the latest fastboot rom for flashing but unless the mounts work, I am hopeless.
Here are the recovery logs
Below output shows that userdata partition is encrypted. I think this is preventing the partitions to be mounted

warlord060816 said:
Recovery - twrp 3.0.2-0
Those mounts were not visible when I check the mounts using df command and for the above errors I tried to format as it showed successful operation.
I have the latest fastboot rom for flashing but unless the mounts work, I am hopeless.
Here are the recovery logs
Click to expand...
Click to collapse
how about using TWRP unofficial ?
a weird error i ever seen till now

faizauthar12 said:
how about using TWRP unofficial ?
a weird error i ever seen till now
Click to expand...
Click to collapse
I'm eager to try the twrp you have linked but just wanted to ask few qs.
1. The version I am using is also listed in the link you've provided. Is there a way to check or after flashing I would find differences in the functionality?
2. Which version you want me to try?
3. Since I updated my above post with the image showing the encryption flag on data partition, can that be fixed in your unofficial TWRP you've linked?

warlord060816 said:
I'm eager to try the twrp you have linked but just wanted to ask few qs.
1. The version I am using is also listed in the link you've provided. Is there a way to check or after flashing I would find differences in the functionality?
2. Which version you want me to try?
3. Since I updated my above post with the image showing the encryption flag on data partition, can that be fixed in your unofficial TWRP you've linked?
Click to expand...
Click to collapse
well, just give it a try
since i'm using my own unofficial(because it has f2fs )
i'm not face any of those error
which Miui you're using??
i think any of rom and recovery just support miui6

faizauthar12 said:
well, just give it a try
since i'm using my own unofficial(because it has f2fs )
i'm not face any of those error
which Miui you're using??
i think any of rom and recovery just support miui6
Click to expand...
Click to collapse
tried the latest in the twrp folder. I was using just the previous of the latest version and got the same result when tried "Format Data" as it said it will also remove the encryption.
I also tried to flash the latest mokee build below are the screen snaps of the logs
Reboot to recovery is also not working and it loads to fastboot screen.
Edit: Previously when i tried flash_all in miflash it gave me error:
0x80004005: FAILED (remote: failed to write partition) at the line where it invokes flash partition command.

warlord060816 said:
tried the latest in the twrp folder. I was using just the previous of the latest version and got the same result when tried "Format Data" as it said it will also remove the encryption.
I also tried to flash the latest mokee build below are the screen snaps of the logs
Reboot to recovery is also not working and it loads to fastboot screen.
Click to expand...
Click to collapse
okay, now i see you're using otg (case 1)(i never used OTG for flash any files)
how about format data from fastboot ?
which miui you're using?

faizauthar12 said:
okay, now i see you're using otg (case 1)(i never used OTG for flash any files)
how about format data from fastboot ?
which miui you're using?
Click to expand...
Click to collapse
Fastboot MIUI version - ferrari_global_images_V7.5.1.0
I tried the format data command from fastboot. If you are referring to "fastboot format userdata" , then it was successful. I tried again and below is the log.

warlord060816 said:
Fastboot MIUI version - ferrari_global_images_V7.5.1.0
I tried the format data command from fastboot. If you are referring to "fastboot format userdata" , then it was successful. I tried again and below is the log.
Click to expand...
Click to collapse
somebody(i forget who is he)
said to me that when using miui 7,you will got a lots of trouble when using TWRP
use any of miui 6 firmware

faizauthar12 said:
somebody(i forget who is he)
said to me that when using miui 7,you will got a lots of trouble when using TWRP
use any of miui 6 firmware
Click to expand...
Click to collapse
I was thinking of trying this unbrick-qualcomm-mobiles/. but again this phone is not entering into "Qualcomm HS-USB QDLoader 9008" mode.
Tell me which miui version other than 7 I should try? and if possible link me to that.
Edit: Now downloading this: ferrari_global_images_V6.5.6.0.LXIMICD_5.0_global hoping to fix the partitions if this has those files required like
"rawprogram0.xml"
"patch0.xml"

warlord060816 said:
I was thinking of trying this unbrick-qualcomm-mobiles/. but again this phone is not entering into "Qualcomm HS-USB QDLoader 9008" mode.
Tell me which miui version other than 7 I should try? and if possible link me to that.
Edit: Now downloading this: ferrari_global_images_V6.5.6.0.LXIMICD_5.0_global hoping to fix the partitions if this has those files required like
"rawprogram0.xml"
"patch0.xml"
Click to expand...
Click to collapse
do you mean edl?
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
go to fastboot then use that files
since we only can type reboot edl with adb not fastboot, that thread have a modified fastboot to support reboot edl

tried edl. phone is not going into edl. Well i don't know how it will look like if it goes into edl, right now it boots to fastboot. I don't know if I'm missing anything.

warlord060816 said:
tried edl. phone is not going into edl. Well i don't know how it will look like if it goes into edl, right now it boots to fastboot. I don't know if I'm missing anything.
Click to expand...
Click to collapse
Hey Warlord,
I believe I'm facing the same issue as you did. Have you made any progress?..