yashsingh1/xdaforums huggingface dataset:
[Blu Vivo XL] Alexis96312:
Unable to find partition for path '/sdcard'

Unable to find partition for path '/sdcard'

Unable to find partition for path '/sdcard'

Updating partition details...

Failed to mount '/protect_f'(Invalid argument)

Failed to mount '/protect_s'(Invalid argument)

Failed to mount '/nvdata' (Invalid argument)

...done

Full SELinux support is persent,

MTP Enable

Wiping Dalvik Cache Directories...

--Dalvik Cache Directories Wipe Complete!

Formatting Cache using make_ext4fs..

Updating partition details...

Failed to mount '/protect_f'(Invalid argument)

Failed to mount '/protect_s'(Invalid argument)

Failed to mount '/nvdata' (Invalid argument)

..done

Is this good or bad? This is in Twrp recovery
[Blu Vivo XL] smith901:
I take it TWRP flashed successfully, it is having a problem reading those four partitons. Possibly encryption is stopping you. Try flashing this in TWRP before anything else to remove the encryption.

I didn't get any errors. I know the userdata partition was different in the scatter files. That could be the reason for /sdcard not being recognized. Must be a difference in the layout of phones, not really sure. My protect_s, protect_f, and nvdata partitions and /sdcard all mount fine, pictures attached. I am able to do a backup in TWRP. I have been playing around with porting different ROMs and came across an issue similar to this. Had to change some lines in updater-script.

I checked fstab.mt6735 file in the stock recovery, the modded twrp3 recovery, and stock boot recovery to make sure I didn't make any typos or leave anything out. They all have the same lines. Had to do this:

("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system")

in the updater-script I was working on. I got ahead of myself flashing a ROM and was stuck on the 1st logo screen. Held power+vol_down to get it unstuck. Yes I was all calling myself kind of names like I'm sure some people have done following this guide.

Which scatter file you used? Did you do a readback in SPFT with the WORKING scatter file and mount one of those images to check if you can read and write the files. I mounted system.img from the stock ROM to make sure I could read and write the files before I started with flashing. I'm thinking there is are internal differences in the XL2s. You might have to reflash using the stock ROM with TWRP as the recovery with the

Format+Download

option since you got TWRP installed.

Once I get through playing around with trying to flash this ROM, I will restore and try to find all the partition mappings and update TWRP to work with the format from the updater-script and see if that work. Will let you know what happened.
[Blu Vivo XL] ANJIII:
can you send us your vivo xl2 specs because there are two versions of xl2, V0070UU and V0070EE. Mine is V0070UU. I just did some renaming and editing in the scatter file of MT6735 and it bootloop once after I installed the twrp. I restarted my phone during the bootloop by holding the power button. After that, I opened the twrp to install the supersu then wipe dalvic cache. You may now boot up the phone and it took 10-15mins to use it because the system shows that it optimizes 205 apps(in my case, maybe because I have installed numerous apps). After that my phone is usefull again and I installed V4A because that's the only reason why I wanted to root this phone.
[Blu Vivo XL] smith901:
Here is all the information I have pulled so far from the phone. Have a screenshot attached from About device in settings. The attached zip file is all the information I could think to pull using adb . The attached file is my partitionlayout. I just ran cat against every file to see what it would give me and redirected the output. Using adb while the phone is in recovery let me pull and read the files I couldn't while the phone was booted.

[MENTION=5826652]Alexis96312[/MENTION], try to run this command in terminal to get your partition map:

adb shell "su -c 'ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/'" > someFileName.txt

I have mine listed in the zip file as partitionLayout.txt It will list which names go to what device in /dev and save it in your current directory. The file can be used to get the correct partition layout on your phone. Post the results and I will repack the recovery to see if it will work for you. You can do it also with Carliv Image Kitchen, it has a menu :good:. You will have to modify the fstab files in the ramdisk folder of the extracted image to what the partition map specifies. I went thru all of them to be sure when I first ported TWRP.

[MENTION=8376362]ANJIII[/MENTION] is correct about the different versions, nice catch. I forgot about that. I assumed you had the V0070UU version like mine, fault on me for not asking. Mine specifically says BLU_V0070UU_V07_GENERIC 25-11-2016 09:46. I'm thinking the GENERIC part comes from me having to flash the stock ROM. I think it had BLU_V0070UU_V07 with user/keys before I bricked it and had to flash the stock ROM. Got three extra apps that I instantly removed. Seems like the stock ROM function the same as before bricking flashing stock.
[Blu Vivo XL] Alexis96312:
ScreenShot

Answer in pictures
[Blu Vivo XL] Alexis96312:
ADB USB

It seem that the computer can't find it what now :mad::mad::rolleyes:

Do I need to install the ADB driver again?

I'm trying to do it on stock recovery

Do I have to do it on TWRP recovery?
[Blu Vivo XL] smith901:
It look like the pid:vid aren't recognized correctly. Usually a reboot will help.

Are you connect using adb while in recovery? If so, see if Windows will install new drivers for you. My Linux box read mine as a Samsung at one point. Try running the ls part of the command in TWRP terminal.

This is where I fought with windows when the cord got pulled during flashing. I never got an error like the 2 at the top, always like the bottom one. I kept adding legacy hardware in device manager until one of them worked. The Linux version of SPFT always give a chip mismatch error. Wish it worked so I won't have to boot to Windows.

I kept doing format+download and and plugging the phone in until Windows recognized it because it was in a bootloop when that happened. You need the preloader to be recognized.

Both stock ROMs are on needrom.com. I downloaded the UU version, the EE version is what you might need. I'll pm you a link to my backups from TWRP to see if they will work for you. Same thing happened to me playing with the new ROM. Restoring my boot and system got it back working.
[Blu Vivo XL] :
You did an OTA update, I didn't. I got the update for the V12 update after flashing stock but moved it and stopped the Wireless Update app. The update had root checks and a different partition sizes layout. That could be the source of this particular problem.

Can you boot to recovery? You might need the boot, system, and data partitions to get back working.
[Blu Vivo XL] Alexis96312:
Okay here what I'm gonna do I

Set to Scatter (MT6737T_Android_scatter)

format + download (BLU-Vivo-XL2-V0070UU) AUTO check on SPFT

Then, I'll chnage the recovery again to TWRP.img

The reasons why I'm saying this it because to let you where am I

Now what next?

Sorry for dragging you guys in my trouble please forgive me
[Blu Vivo XL] :
edit: The V0070UU_V07 is what seems to work. Only three people posted on results one way or another so I don't if that is the only version that TWRP works with. It worked for ANIII. It works for me coming from a brick. Seems reasonable you having V11 is why it didn't work for you at first.

That is where I am also because the ROM I was playing with put my phone in a 7 second bootloop. I went stock ROM with TWRP, backups worked. Then I went stock Recovery to see if I could restore my backups made with the stock recovery before I put TWRP on and that cause many problems.. Had to wipe. I'm working out this encryption conflict, if that is the problem, so I can know exactly what to do for next time.

Using format+download, I went stock ROM with TWRP recovery when I first started and it worked. All at once worked better just to get it working. Everything else will be downhill once you get it to work. Also going full stock ROM worked. Just remember to use SN Writer for your IMEIs. I usually do that right afterwards, then boot to TWRP and flash SU.

Using download only for boot and recovery caused problems, probably because I decrypted my phone.
[Blu Vivo XL] Alexis96312:
I just did Format + download on SPFT

Using MT6737T_Android_scatter which auto all boxes for (BLU-Vivo-XL2-V0070UU)

It work only using the stock recovery.

This is helpful for anyone who had a brick now or before.

Now, I try doing this MT6737T_Android_scatter which auto all boxes for (BLU-Vivo-XL2-V0070UU) USING TWRP.IMG which lead me to this again

Unable to find partition for path '/sdcard'

Unable to find partition for path '/sdcard'

Unable to find partition for path '/sdcard'

Updating partition details...

Failed to mount '/protect_f'(Invalid argument)

Failed to mount '/protect_s'(Invalid argument)

Failed to mount '/nvdata' (Invalid argument)

...done

Full SELinux support is persent,

MTP Enable

Wiping Dalvik Cache Directories...

--Dalvik Cache Directories Wipe Complete!

Formatting Cache using make_ext4fs..

Updating partition details...

Failed to mount '/protect_f'(Invalid argument)

Failed to mount '/protect_s'(Invalid argument)

Failed to mount '/nvdata' (Invalid argument)

..done

I try stock and twrp recovery but fail FPR ADBS

Will it work trying to install the BLU-Vivo-XL2-V0070UU in the Twrp recovery??

and how would I do it?

Thanks
[Blu Vivo XL] :
That happened to me testing all the different ways to do this. Those partitions are encrypted.

This post from earlier is what I did to get past that. It removed encryption. I didn't reencrypt my phone afterwards because of testing.

Flash the zip attached to this post and you will be good. That way you can backup all your partitions in TWRP after you are sure it will boot to System. I will do the same soon, busy testing. Will let you know if reencrypting after TWRP is flashed will cause problems to keep you from having any more issues.
[Blu Vivo XL] Alexis96312:
I try flashing the zip attached in Twrp recovery but keep getting error I'll upload a picture ASAP
[Blu Vivo XL] :
I did

1: a stock ROM+TWRP recovery Format+Download,

2: immediately after wrote IMEIs,

3: boot to TWRP and wipe dalvik+cache & flash, got failed to mount protected_s errors, flashed no-verity zip, rebooted to TWRP,

4: flashed SuperSu, rebooted to TWRP to see if I can mount those partitions,

Everything worked.

My first TWRP backup works well, 2nd and 3rd was the problems. Titanium backups work. Back to where I was before flashing the 7sec bootloop ROM.

When you get it to work, Stericson's BusyBox from PlayStore was laggy and wouldn't symlink apps. The one from fdroid app from f-droid.orgworks well. Apps that need BusyBox don't bog down with this one.
[Blu Vivo XL] Alexis96312:
I'll try it your and will let you know if work

Again I'm so sorry for causing trouble here please forgive me :)
[Blu Vivo XL] :
No apologies needed. You wouldn't have tried if I didn't put it out there. It would be wrong of me to leave you hanging.
[Blu Vivo XL] Alexis96312:
When you said a stock Rom that mean all the options must be check but not the stock recovery right.

Examples:

preloader Check

IK Check

Boot Check

Recovery is Twrp.img

Logo Check

Serco Check

Tee1 Check

Tee2 Check

System Check

Cache Check

Userdata Check
[Blu Vivo XL] :
BLU_V0070UU_V07_GENERIC from needrom.com

TWRP as the recovery Format+Download, IMEI write, wipe dalvicCache+cache(to be safe, or not), flash SU, flash no-verity, boot to system.

I'm impatient so around 3min, I start wondering. This last time around 10min on colorful logo, I gave up & started to power down. Before I could, I saw '''Starting Apps

1 of 22'''

Restored from TWRP backup, restored other apps & configs from Titanium.

The Stericson BusyBox Pro said it installed and symlinked applets but it didn't. Used the BusyBox from Open Source BusyBox and haven't had a problem since.
[Blu Vivo XL] :
↑ all options checked. just replace the stock recovery with twrp. ↑ just like you wrote ↑ $£€¥
[Blu Vivo XL] Alexis96312:
I did it

SuperUS Work :) :) :)

But no-verity-opt-encrypt-5.1.zip it

fail

in the picture it show

I feel close to victory :)
[Blu Vivo XL] :
I think I got that the very first time. I just rebooted and flashed SU. Booting took a while, saw "decrypting" but didn't pay attention because multitasking. I just figured I would take a while to boot for the first time.

Line up a good movie and play it when you do the final boot to system. By the time it end, you should know either way.
[Blu Vivo XL] :
Boot to TWRP and see if you can backup. That way you can keep different "stages" of your progress. Like Fresh Flash, Debloat, App Install, or whatever to keep you from having to do installs, removal and configs of apps.
[Blu Vivo XL] Alexis96312:
Still on BLu BOLD LIKE US logo

In anytime it should be finish

---------- Post added at 03:51 AM ---------- Previous post was at 03:15 AM ----------

What would happen if I went to Stock recovery and everything and setup everything up (meaning normal phone working)

Then, I go change the recovery to Twrp and backup from there

Then I go in Twrp format type yes boom gone

Reboot to recovery restored app and flash Superuser (To Skip the long process of booting Logo using Twrp recovery)

I have a question what should I backup and restore in order to skip the long process??

I forgot to do the backup before doing the Twrp or anything
[Blu Vivo XL] :
You will have a configured stock backup.

Fresh phone.

Still will take some time to start the apps. About 200 apps took 10-15 minutes to boot.

I back up everything on the first one. After that it's usually system, and userdata. I even made a few system images and full backups.

Restore first full backup after a flash. Restore System and userdata for the rest. Backup and restoring always take time.

You got the process now so you can restart as many times you want. Make sure they will work before you start full time phone use.
[Blu Vivo XL] Alexis96312:
It seem that I can flash SuperUser and restored anything then I reboot system

I waited around 20 minutes and I went to the recovery to check it

I find out that nothing has been flash or restored

What does this solution mean?
[Blu Vivo XL] :
This is coming off a fresh flash right?

Maybe you are restoring old data over new. Are you choosing the right backup?

Which partitions are you restoring!

Are you wiping the dalvic+cache before/after restoring, or both?

Are you restoring from a fresh install, using the first backup if so?

This world be the time I start over with system ROM+TWRP recovery, IMEU write, flash SU, boot to check, then start with my first TWRP backup restoring system, data, & userdata partitions, boot to check.

I use TWRP for partition backups after system configuration, Titanium for app backups after installing and configuring groups of apps.
[Blu Vivo XL] Alexis96312:
I figer out the problem when I download + flash stock

I let it run I saw an android saying encryption

Should I use no-verity-opt-encrypt-5.1?

How should I stop it or fix this solution?

Got it FIX! Thank for the HELP Smith901 User and the Root
[Blu Vivo XL] :
Boot a see if your phone is encrypted or decrypted. It is your choice. Don't flash unless you are sure of what you want. I tried reencrypting but it kept doing a factory reset loop when booting.

I didn't care for it at the time. I wanted to backup all my partitions so I decrypted. Unlimited access is what I wanted and I got it.
[Blu Vivo XL] :
[MENTION=5826652]Alexis96312[/MENTION] don't PM if you don't want to receive PMs. To answer your question, the MD1_DB file is correct, the correct AP_DB file is the one without ENUM on the end. Just download SN Writer from this site for MTK Androids tools that worked for me. Get the latest one and make sure your phone is off when you do it. I haven't had any errors with SN Writer so I don't know what to do about that. Google will help you with the hard parts, gotta keep searching.

Good luck.
[Blu Vivo XL] Alexis96312:
It work thank bro :)
[Blu Vivo XL] ekooo:
What to do zip file I downloaded
[Blu Vivo XL] :
Delete it if you got to ask.
[Blu Vivo XL] makwanad370@gmail.com:
How to dunlode nuggets 7 vivo V5s
[Blu Vivo XL] SumitKrSoni:
Hey xda developers!

I wanna update my android to marshmallow or nougat... Need help.. How to update... Or how to mod?

Please help...
[Blu Vivo XL] combatplane57:
Will this root guide/process work with an original Vivo XL (the first one that came out in Jan 2016)?
[Blu Vivo XL] :
[MENTION=6877662]combatplane57[/MENTION]

No, that guide is somewhere in this Device forum.
[Blu Vivo XL] Tajvinder singh:
How to root my phone...?
[Blu Vivo XL] :
Do a search in XDA or Google, read, understand, do.
[Blu Vivo XL] souvik.rony7@gmail.com:
How to rootvivi v1
[Blu Vivo XL] Flippy498:
The thread got closed at OP's request.
[Samsung Galaxy S7 Questions and Answers] Luc!en:
[IMG="The Camera Spec"]https://drive.google.com/file/d/0BybYDJtRaQRwSGpjdGVTLXVKeE0/view?usp=drivesdk[/IMG]

I cracked my lens and replaced it, but it seems a tiny piece of glass is on the actual camera (I can tell because the little black kind of flir moves with the image stabilisation). Any ideas on how to at least remove it off the camera without removing either the lens or back glass? I also voided warranty by jailbreaking and replacing lens?
[HTC One E8] Chainslayer:
Hey everyone! So my HTC One E8 is rooted and I have flashed exposed in it. It was working fine until last night when I was using built-in onscreen recording. Once I finish the recording, I was expecting captions to be turned off as it always does after recording is finished but the captions still are showing. I have tried turning the captions on and off but that doesn't work either.
[LG G6 Questions and Answers] electric0ant:
hey,

anyone else have issues with the photos for the contacts not synchronizing down from google?

I have all the contacts, but none of their photos are showing...
[LG V20 Questions & Answers] Kevinrdz91:
Hi everyone,

Well I bought a phone on ebay and now it has Rent a Center lock.

The first step to remove this is to have the bootloader unlocked but I cannot access the phone and activate options usb debugging and OEM unlock since the phone is blocked.

I've read some people have figured it out but I just dont know how to do it. So how can I unlock the bootloader if I cant access to the phone and activate those options? I know its possible I just need some help and detailed information please!!

Thanks everyone
[General Topics] jdauncey:
Hi,

I have an O2 XDA Trion running WM6 (standard O2 release), and Windows XP with Outlook 2003 and ActiveSync 4.5.

Rom Version: 3.54.206.1

ROM date: 06/25/07

CE OS 5.2.1238 (Build 17745.0.2.3)

I've been synching my data for months now without any issue, but something just stopped working today?

When I plug it in via USB I get an error message saying that 'Synchronization cannot be completed successfully. Please reconnect and try again, etc.'.

I can explore the contents of my device, but not synchronize, and a third party app will even synch, but nothing from Outlook, and quite a lot of the options in ActiveSync are greyed out (though I can still explore via ActiveSync).

When I look at the ActiveSync application on my phone, it looks as if it's never been set up to Sync, and tells me that I need to install ActiveSync on my PC.

I have done a repair install of Activesync 4.5, I've rebooted the PC, I've switched the phone off and on again (fully). Nothing changes. I have (as advised) reconnected several times.

I've not knowingly done anything to either of them in the last few days, which was when it last worked.

I couldn't find anything on the forum on this topic, but if you can refer me to previous issues like this then I'll go have a look.

Thanks,

Joe
[General Topics] jdauncey:
fixed!

Hi,

I just wanted to say that I deleted the sync partnership on the PC and created a new one, and it worked after that!

There was an initial problem where it refused to sync again, but since a soft reset it's all been going fine.

I'll keep an eye on it still as I'm a little suspicious, and I don't know what caused the problem!

Joe
[Huawei P9 Lite Questions & Answers] nimus:
First I must say sorry for my bad english.

So, let's start. First I wanted to root my phone, so I downloaded SRKToolHuawei and unlocked bootloader. Next I've installed custom recovery named "RevolutionRecovery_Nougat_P9Lite_B.9_15-12-16" and I've installed it through adb.

Next I've tried to install SuperSU but i had a error named "failed to mount /data (invalid argument)". So i wiped "/data" folder and changed format to another and come back to original.

Next I've installed original stock firmware with Android 7.0 and EMUI 5.0 and later come back to custom recovery and i saw the same error, so i search internet for a bit and I've found something interesting on xdadevelopers and i tried to use it on my phone.

I've entered this code to my console in custom recovery:

mke2fs -T ext4 /dev/block/mmcblk0p8

[/QUOTE]

And now i have problem.

When I boot up my phone i saw a green screen with two red and blue boxes in the center of the screen. Next the system load normally, but i don't have some apps like "options" etc. and i hear a strange sounds when i unlocking my phone.

Next when i get into bootloader and rescue screen i have unlocked phone but I DON'T SEE FRP [LOCK/UNLOCK] STATUS. I'm scared about my phone. Please help me :crying: :crying: :crying:

[MENTION=3497715]edit1[/MENTION]

I flashed OEMinfo for this phone in the custom recovery and i don't have this crazy startup screen like i written before, but now i can't load any custom recovery, becouse my adb gives me this information: "FAILED (remote: Command not allowed).

Please help me! :c
[Huawei P9 Lite Questions & Answers] rambik33:
Vendor of you phone?
[Huawei P9 Lite Questions & Answers] nimus:
I live in Poland. This phone is from "Orange", but i think it doesn't have brand.
[Huawei P9 Lite Questions & Answers] :
Unlock bootloader again
[Huawei P9 Lite Questions & Answers] rambik33:
*#*#2846579#*#*

3. Network information Query - 4. Vendor Country info

What ? Must be hw/eu
[Huawei P9 Lite Questions & Answers] nimus:
Oh my godness...

And here is the problem, I can't now boot system, only eRECOVERY from Huawei.

But it's hw/eu.
[Huawei P9 Lite Questions & Answers] rambik33:
Ок, post №4.
[Huawei P9 Lite Questions & Answers] nimus:
Im sorry XD

But i unlocked again bootloader and I can get into custom recovery. (Thanks to Johnny TDN).
[BlackBerry KEYone Questions & Answers] Almor:
Hi all, somebody knows how to enable the phone option "roaming assistant" on keyone? This option should enable the primary country code prefix when i'm in a foreign country for number without international prefix. this option is present on iphone and samsung s6, i can't see on K1

Thanks
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Shubham2910:
Here is a new group for kenzo users ..all kinda users here ..pro, super pro , noobs too.... Everything about kenzo is here ..either miui or custom rom...kernel or theme ...brick or hardbrick..anything....

LINK

https://chat.whatsapp.com/7MyBta8fT8w3ff3WFdttVe
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Ajendra25:
Joined:good:
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Panneer Selvam:
i like to join
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Sachin:
Then join :eek: