Develop Bugs

/efs partition not being mounted

I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.

Bloodyskullz said:
I just got a note 2 (i317m - canadian carrier model) that got messed up some how. When attempted to boot the phone it said unable to mount efs partition. My research tells me that partition that contains module info such as IMEI, bluetooth, wifi are stored in that partition. Now I realize why the repair guy wanted $350 to fix it.
Is there a way I can tackle this problem on my own and try and fix it? Apparently there is a tool here in XDA that can wipe the partition but I am not sure if that would rebuild it and allow me to mount it so I can create a new data file with the IMEI number in it.
Where should I start to attempt to fix the problem.
Please note, I can still access recovery (currently TWRP installed) and download mode and use ODIN if necessary to flash back a stock rom BUT can't mount to the computer for any file transfers nor can I boot the android device (stays at samsung logo). I have no issue using ADB is neccessary if I am lead in the right direction. This phone is already trashed in the eyes of the owner so its basically a little project for me to tackle when i have time to kill.
Click to expand...
Click to collapse
Have you tried flashing your official rom? Flash your official firmware by downloading it from sampro.pl or sammobile.com, flash it with PC Odin under PDA tab.
After you done, don't let reboot your phone, goto recovery by pressing vol up+ menu key then power key(continuously hold it until your phone restarts might be 4~8 secs.) Then check 'Wipe Cache Partition', and then reboot phone.

Yup and nothing worked.

Anyone?

So the only solution is a $300 fix?

Phone still encrypted after reflash/factory reset?

Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?

Trying flashing marshmellow KDZ and it should reset everything
Let me know how things go

TTib said:
Hello,
I hope someone will be able to help with this, although it is very much a case of user error! I upgraded my G3 to Marshmallow using the steps detailed here:
http://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
It all worked perfectly until I decided to encrypt the handset. The encryption process worked as expected, but as I always did on previous Android versions, I used the CryptFS Password app to change the encryption password. The app advised that it was unable to change the password and that I should run the command via shell, which I did and it seemed to work. The problem is, I changed it to an alphanumeric password and my lock screen is just a numeric PIN, so upon reboot it prompts me to enter the password to decrypt but only allows me to enter numbers.
So, I kicked myself for not changing the lockscreen from PIN to password before rebooting, but figured I could just wipe/reflash and start again. However, when I reflash, I still get prompted for the encryption password at boot. So I figured I'd just enter the password wrong 30 times and factory reset the device that way, except that doesn't work either. It says it's going to reset, reboots to recovery (TWRP 2.8.7.0) and says it has reset, but then boots back to the encryption screen again (which now advises that I am -5 of 30 attempts!!).
Flashing CM13 or 12 works fine. I have settled on CM12 at the moment because it seems to be a bit more stable, but I'd ideally like to get back to stock Marshmallow. Is this possible?
I have tried wiping all partitions and data from within TWRP, and formatting partitions, all to no avail.
Is there any way I can reinstall stock Marshmallow?
Click to expand...
Click to collapse
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.

KronicSkillz said:
try booting into twrp, go into command terminal, manually format data partition using command line, then reflash cm12 and wipe cache and dalvik (you may not need to reflash it but why not if you are going back to mm)
if your partitions are the same as mine this is the command you want to run.
mke2fs -T ext4 /dev/block/mmcblk0p44
make sure you don't format the wrong partition check that your variant has the same partition (grab an app called diskinfo and click on data partition then alter the last parameter to w/e ur data partition is)
mmcblk0p44 is the paramater you want to change if yours isn't identical. this should reset encryption as data is the partition that gets encrypted.
after all of this use a guide to install marshmallow (kdz or something)
(when i encrypted my data partition twrp could no longer mount the partition to format it, but if you use command land format it formats the partition without mounting it.)
i'm assuming this is your issue as well.
Click to expand...
Click to collapse
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!

TTib said:
Hi, thanks for the advice, I gave it a try last night. My /data partition was named /dev/block/mmcblk0p43 according to DiskInfo, so I made sure the partition was unmounted in TWRP and formatted it via the terminal following your instructions and then reflashed the MM zip from the original link and... still encrypted.
I haven't tried flashing the kdz yet, as I use Linux and I don't believe there is a way to flash kdz files using *nix. I'll have to wait until the weekend and I'll try and do it via a VM.
I don't understand how this encrypted partition is still even there. I have CM12 installed and working, it's showing the full amount of disk space available, I've done multiple wipes, formats and resets, yet the minute I put MM on it, the phone thinks it's encrypted again.
I do actually know the encryption key, is there any way I can unlock the phone via ADB or something similar?
Not sure if it's relevant, but my phone model is D855. I don't think I mentioned that before.
Thanks for the help, I really appreciate it!
Click to expand...
Click to collapse
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.

KronicSkillz said:
very strange when i did that it got rid of my encrypted partition... i'm not sure what else to say except maybe see if someone will lend you a windows pc to do kdz flash.
Click to expand...
Click to collapse
I flashed the kdz via LGUP and... now the phone won't boot to anything except TWRP. Have tried restoring two previous nandroid backups, installing CM12 and MM, all install without reporting errors. LGUP detects it as an unknown device, so can't flash kdz again. Might have bricked this one. :crying:

Phew. Okay, solved! I followed the following guide to flash an old version of the stock firmware: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html.
Then, I upgraded, rooted, flash TWRP and finally installed MM again and it seems to be back to normal ("Android is starting" screen as we speak. Fingers crossed!). Thanks to everyone who helped me out with this one!

HELP! restoring stock rom on Verizon galaxy S5 (G900V)

First of all to admins..., I hope I'm posting this in the right section. If I'm not, please move it or direct me.
I have a Verizon S5 - G900V that is soft bricked and I have been pulling my hair out trying to restore stock rom to it via Odin. It fails every time. I have tried so many versions - some fail with aboot, which I understand means that th version I'm flashing is older and I can't downgrade. Fair enough. The only one that seems to work is G900VVRU2DPD1 (which shows up as the version in recovery mode) but it fails at loading the SYSTEM stage. In Odin on Windows it shows fail (AUTH) an on t device it shows secure check fail: system
Reactivation lock on the device in download mode shows OFF And I can't boot into the OS to verify that.
I have all the necessary device drivers installed in windows.
The device, I believe, is not rooted.
Using kies doesn't work because I asks for for device serial which I d know and does n show under the battery (only shows IMEI an model) and using the Verizon repair Assistant doesn't even see the device
I have wiped cache partition and did factory reset from recovery mode.
I have done exhaustive Google searches an been on many xda dev posts for weeks and not finding anything that works.
I've also tried pushing with adb sideload....didnt work.
The only thing I can think of, and think I might have read somewhere, is that my problems are caused by a locked bootloader. I anyone here able to attest to that?
One other thing...in recovery mode, if I select mount system, it gives errors in red e:Failed to mount /system (invalid argument).
Any experts here able to help me get passed this to successfully flash stock rom (or any rom even modified) back into this device and end my madness?
Any help would be appreciated.
Thanks in advance

Bump

any experts out there able to help me on this one?

need help

Bought new OP5t
Update OOS 5.1.5 latest
Unlock bootloader
Flash TWRP recovery
Wipe everything except otg format
Install lingue os 15.1 gapps 8.1 pico
Boot normally
Then try to install red flare kenel, magisk zip boot to fatboot menu can't boot make nandroid backup twrp then try to restore also boot on bootloader menu try to download magisk apk download but it's blank can't install notification bar have strange one
Discover trust "get to know to assure how your device is safe"
I don't know what happened if someone could help me if I didn't something wrong please

Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.

Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
Flash this solve your proplem
https://drive.google.com/file/d/14QnXJH9TWMZnYI9RItIPv8ivGUjz1q5S/view

Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks

Tobias101 said:
Not being rude, but do you really think no verity is going to help? I mean it usually doesn't fix stuff. Besides, thanks but it's not that it is encrypted, I can flash things if I know their directery, it's just that data can't be mounted. But thanks, I'll try flashing no verity and see what happens.
Many thanks
Click to expand...
Click to collapse
That's all I can help with I'm not professional sorry.

Tobias101 said:
Hello. Need help is exactly what I need right now. Basically, I just tried flashing Oxygen OS from LineageOS, as I was just getting a little annoyed about how the updates were getting stupid and apps kept crashing. However, when I did this, it got stuck on just a sec when I was setting up. I then tore through the internet looking for how to wipe /data and /data/media with twrp command line. I found out about fastboot erase userdata. I used that. However, it wasn't just the casual wiping of the data where everything goes except the critical files. I mean every single little god damn thing got removed. I tried pulling /data and it said 0 files pulled. I was not happy. I managed to flash the rom but the phone won't boot. the worst part, I tried mounting /data on twrp and it said failed to mount data, invalid argument. So that was that. I then formatted to the original using the twrp format, (needed sighted help for that...) And it succeeded. Now however, I try mounting and it says no such device. 1, how can I mount data? And 2, how can I get a data partition that actually works with setting up and even the booting up of my phone. Yes, it won't boot.
Please help me, you don't believe how annoying it is to have a virtually useless phone.
tobias
PS, I was using stock bootloader and twrp recovery. Also, please give the answer of fixing in a command line method, I'm blind so getting sighted help would be rather annoying.
Click to expand...
Click to collapse
brad:
It won't mount data for many reasons but just installing stock recovery and installing OOS would fix everything.
https://forum.xda-developers.com/on...-revert-to-oos-oreo-8-1-t3730952/post75096633

Is it possible to unlock FRP from fastboot? Bricked Honor 7x.

Greetings.
I had issues updating my Honor. Every time I would try the update, after downloading it, it would boot into TWRP with the message failed to unmount /system: device or resource busy.. Then, if I rebooted, the update simply didn't work (I was stuck in an older version of EMUI 8.0, I don't quite recall the precise number). Actually, the same error message would come every time I simply booted into TWRP.
At this point, after a backup, I thought I could just wipe the /system partition and then flash a zip, containing a new ROM, from the TWRP; I wiped the partition and rebooted, and of course the phone started into TWRP, because there wasn't a system anymore. The problem is: TWRP is stuck at splashscreen, and I can't access it anymore.
I tried going into fastboot, but only to find myself with the message Phone Unlocked, FRP Locked, and I was unable to boot another version of the TWRP.
Another thing I did was to boot into the e-Recovery, and from there if I tried restore to factory settings, it would boot again into the stuck TWRP; and if I tried to download latest version and restore, the download would fail because I couldn't retrieve package info.
I then tried a solution I've seen in this forum, namely , with a Windows 10 machine that I used as an hotspot (actually I wasn't able to use the same IP from primary and secondary DNS, only for primary).
I understand that the only thing left to do is to pay some amount of money to some company that would give me the FRP unlock key based on my IMEI, and I actually tried that, with HCU-Client, but after buying 12 credits, they reimbursed them for no appareantly no reasons. Did somebody use this method, perhaps with another company? And did it work?
tl; dr: honor 7x bricked: stuck into fastboot with FRP lock, can't open twrp, don't have system, need help to know if I can actually pay a company to give me the key for the FRP unlock.