Database Develop

[Q] Paradox of damaged partitions

Well, hello. Not new here, but quite new in posting things, was always just reading what these guys are doing and followed their instructions. result was always being able to flash whatever on a selected device. But today i'm coming with a stupid problem that i hope somebody would help me solve.
2 days ago (and i will be full of details here) di flashed ARHD51.0 on my Htc One. everything went well (as usual with those roms) but i wanted to format my whole phone (i had like 5gbs of backups that i could not find (4 months i was xda-ing and googleing solutions for removing invisible backups that cwm made. and then i read this http://forum.xda-developers.com/showpost.php?p=48108231&postcount=2
as you well know, this is a member of trust on this site so i decided to follow those instructions and that backfired on me i must say. what happened next was that my phone was in a bootloop, recovery was dameged and adb (and still) could not read my device, fastboot would on the otherside.
I managed to flash new cwm (philz touch 6.0.4.6.) via fastboot and it worked. but in cwm messages are following (will copy just some of the lines because you will understand the problem)
failed to mount /dev/block/mmcblk0p39 on data ext4 (file exists)
failed to mount /data
failed to mount /cache
then something like failed to install /tmp/update.zip (that message was shown when i was trying to install stock rom)
and i sideloaded stock (fail), arhd (goes to 30%, freezes on writing data&system)
when exiting cwm, it asks me to reinstall the root because it is missing (even when i install it manually via usb otg or sideload and it says done, still root is non existant.
baseline is this: i formated the sd card, and tried to do as much as i could with all the logical things, my partitions are messed up and i'm missing boot.img and system files, unable to mount data/cache/sd card. Now i can do only so much to ask you. I can try to relock the bootloader and use the ruu (but i am s-on) i can try to send boot.img or something (but how when adb push is not working, "device not found") i can format the partitions but do not know how to format them from cmd or cwm.
currently i'm downloading stock deodexed and odexed stock roms and ruu. i already have su, philz touch advanced (planning to try to flash that only because of more options than standard philz cwm) and otg ready cable to use it if there is no help for adb push.
Anybody, please help because i will tryto fix this, but i'm afraid that if i mess the order of things that needs to be done, i could brick this totally, and in this area of damaged partitions i have no exact experiance.
Any help appreciated, and can be (gladly) rewarded on demand
sorry for funky and somewhere incorrect gramatic structure, if something is unclear about it, feel free to ask

kriistofor said:
failed to mount /dev/block/mmcblk0p39 on data ext4 (file exists)
Click to expand...
Click to collapse
HOLD YOUR HORSES!!
post a "fastboot getvar all" (leave the first 2 characters of serial number, IMEI, and MEID, and "xxxx"-out the rest)
and maybe a screenshot of bootloader
you either have a Sprint/Verizon HTC and/or the wrong recovery!!
so stop!!!! and post above needed information

nkk71 said:
HOLD YOUR HORSES!!
post a "fastboot getvar all" (leave the first 2 characters of serial number, IMEI, and MEID, and "xxxx"-out the rest)
and maybe a screenshot of bootloader
you either have a Sprint/Verizon HTC and/or the wrong recovery!!
so stop!!!! and post above needed information
Click to expand...
Click to collapse
sorry,sorry i sounded a bit overexcited and impulsive.
well, i have international htc, but the cwm (even though i downloaded the M7(gsm) version was the biggest problem for the phone (based on the name of the cwm it does not sound logical to me). Also, i used 6.0.4.6 non touch and it also was useless but i managed to solve this after two whole days of mind****ng myself and this phone.
SOLUTION:
relock bootloader (without this you can try anything as i did but it will fail if the problem is the same)
unlock bootloader
install twrp (for some reason after this cwm, no other cwm was able to format partitions or anything)
format data, or full wipe option
stock rom (installed deodexed 4.4.2)
root if want
problem was gone in 4 minutes, it booted faster than any other thing i've put on this phone (like in 2 minutes fully booted into welcome screen).
now it is running arhd 51.0, elementalX and is alive and well.
solution is probably effective wih all of those problems with corrupted or badly formated internal sd on One but i will say that people here are giving solutions that are logical and are working for others with similar problems. this one is for those who have tried all the things with reflashing recovery, rom, with bad adb experiance because of formatted card and are unable to sideload anything.
thank you for help because if I haven't succeded with this leap of faith i would more likely f*c? something up by myself. and thanks for reply, expected no one would give any

Error mounting data and cache

Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?

devbro said:
Hello Everyone
I have run into an odd problem. My tf701 ran out of power while I was watching netflix on it. After that it got stuck on boot. When I tried to fiddle using CWM I found out that I cannot mount data or cache. Further more I get to see 5 lines of "E: can't mount /recovery/*" where * are folders within /recovery/ . I tried to format system using CWM or fastboot, they both say they succeed but when I reboot I still get my bootanimation. At this I am out of ideas as to how I can fix it. Furthermore thanks to being unlocked I lost my warranty .
Any suggestions as to how I can fix it?
Click to expand...
Click to collapse
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean. I had a situtation where some things would not mount. data being one of them.. Not sure what else. Then I just mounted /system and everything was ok. Could it be that for some reason system is not getting mounted and you not formatting it besides an empty directory.

YayYouFixedIt said:
Maybe I saw something like this I dont know. Did you try mounting system first and see if that fixes it? I have no idea.
EDIT: from CWM I mean.
Click to expand...
Click to collapse
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
some corruption seems to have occurred.
perform a hard reset in the 'stock' recovery (this will format /data).
then boot in and re-setup. any userdata you had will be gone (including media/content stored locally, etc.).
in case of /system corruption (after performing the above; you still cannot boot in), you can format that partition separately and re-flash it from the CWM file for the latest posted stock update.
you can find file(s) on droidbasement, as needed.

I belive I have the same probleme, how i could i do it right?

devbro said:
Yes I tried no luck. When I try to format /data using fastboot it simply hangs both the device and the terminal too.
Click to expand...
Click to collapse
How did you try to format data in fastboot??
That's done in recovery afaik.
nero0345 said:
I belive I have the same probleme, how i could i do it right?
Click to expand...
Click to collapse
What problem do you have? /data not mounting? Format it in recovery but you will loose everything stored on your internal SD.

I finally took my tablet in for a check with asus. They said that I ahve corrupted my boot and since I replace the recovery there is no way to fix it. the only way to fix it is to replace the motherboard at this point. It will cost 190$ to replace!!!!

Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.

devbro said:
Just as an update to the future readers. I ended up replacing my logic board inside using one that I got from ebay. My tablet now works just as new. As per advice of the Asus tech, DO NOT FLASH a new recovery. If anything goes wrong the original asus recovery is the only way to fix things.
Click to expand...
Click to collapse
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...

berndblb said:
I beg to differ....
The stock recovery can only flash firmware signed by Asus and perform some crude wipe operations.
With a custom recovery you have way more tools at hand to fix problems:
You can wipe or format partitions selectively
You can take nandroids and restore them
You can check the integrity of file systems on partitions
You can fix permissions
You can flash SuperSU, custom roms and more
Some have a build in file manager allowing you to move data off the tablet even if it doesn't boot anymore
Some have a build in terminal you can run commands from.
The list goes on...
But sure - you have to do all of the above including flashing the custom recovery correctly or you can seriously damage your device like you did.
I am really sorry that you lost your mainboard and had to buy a new one, but don't kid yourself: It was not the custom recovery damaging your tablet. It was you...
Click to expand...
Click to collapse
When I talked to the tech at their center, there is apparently some special actions that only their recovery can do. These actions are those that allow changing boot table and other low level functions of the tablet which has nothing to do with the built-in memory or system files.
If I did not replace the recovery, then the repair by asus would have only cost 40$.

[CLOSED]Vivo XL2 TWRP 3.0 and Root

I must note: I use linux. I only used Windows because SPFT Linux version gave me a chip mismatch error I couldn't fix easily.
1: Please read. It explains what problems might arise. Especially post #6 and #13.
2: There are 2 versions of the scatter file. The MT6735 version is what I used successfully. The MT6737Tmod version is what comes from post #6 & #13.
3: Please use each scatter file to Readback your boot and recovery partitions first, renaming as fit, so you can have a backup BEFORE ANYTHING. Then test unpacking them to see if everything went correctly. Then readback every partition in the scatter file so you don't have to depend on the stock ROM for a backup. I didn't and it led me to take this route.
3: Seem to be a difference in the naming of the scatter file and sizes of system, cache, and userdata inside from the stock ROM and what works..
4: DO NOT choose Format+Download until you know which scatter file works, unless you want to chance a Hard Brick.
5: Wiping the dalvik and cache in stock recovery before flashing TWRP seems to be the best thing to do to avoid boot loops or a hung boot.
THIS ROOT PROCESS WAS DONE OVER THREE DAYS OF CAR WORK, DRIVING, FAMILY, AND COMPUTER WORK. MOST OF THE TIME SPENT WAS THIS MORNING TRYING TO GO TO SLEEP. DIDN'T HAVE TIME TO DOCUMENT AND TAKE PICTURES. THIS WRITE-UP IS FROM WHAT I REMEMBER DURING THIS PROCESS. IF I CAN REMEMBER SOME VAGUE DETAIL THAT YOU NEED, GOOD. IF NOT, DON'T STRESS ME. THE HARD PART IS DONE. A GOOGLE SEARCH OF SOME OF THESE PROGRAMS WILL GET QUICKER RESULTS IF YOU DON'T HAVE THEM. THE MAIN THING NEEDED FROM MY RESEARCH WAS THE SCATTER FILE. LINKS FOR SCATTER FILE AND RECOVERY IMAGE ARE BELOW.
Looking for a way to root first day getting this phone in February. Read this post last Tuesday about MT67xx rooting, thanks lsemprini. Spent two days finding which versions of the programs work with this phone, already had the ROMs, drivers, and tools. Dove right in.
I downloaded the ROM from needrom. Scatter file was unusable. Wrong chip error. Phone reads MT6735 scatter file read MT6737. Did a manual diff. Used SP Flash Tool v5.1524 to flash, formatted instead of downloading by mistake, cord got pulled, Hard brick. Fought with Windows7 to get drivers to recognize a hard brick. Still don't know how I did it but it read then flashed. Looked like another hard brick but SPFT would recognize it for the Memory Test. I just held power+vol_down with just charging block power to get it to come on. Sometimes just one of the buttons was enough to get it to power on and start a bootloop. Took two minutes sometimes. Flashing the wrong recovery led to bootloops. Starting SP Flash Tool and plugging in the USB to the phone as soon as it powers off during a loop will let the preloader "register" and the images to be flashed. Flashing from a stock ROM will lead to IMEI being erased. Used SN Write Tool v1.1716 to write the IMEI numbers. Got them from the side of the box. The MD1_DB and AP_DB files needed are in the stock rom.
Ported TWRP, credit to jemmini for the post https://forum.xda-developers.com/vivo-xl/development/recovery-t3311601. Used that recovery as a base. Ported according to the myriad of guides that I have been reading over the past few days. None of them worked as instructed, had to modify trial and error style. Finally got TWRP to read the internal partitions AND remain after a reboot. A lot was going on when I did this. Not sure if I formatted before, I remember flashing a lot of because of something. I mounted the system just in case & flashed SuperSu from chainfire's website, no formatting afterwards. Rebooted and installed SuperUser and BusyBox. I tried adb and fastboot. They work but not for everything. Hooked phone up to computer with debugging enabled.
Code:
adb root
gives a shell, no errors unlike before. Edit: ADB won't let me start as root anymore.
Needed files
Blu Vivo XL2 TWRP 3 Recovery
MT6735 Scatter File
MT6737T Scatter File
BLU Vivo XL2 V0070UU Stock ROM if you don't have a backup of your partition images.
Step 1
Install Minimal ADB and Fastboot and USB VCOM drivers.
Download SP Flash Tool, SN Write Tool, scatter file, and twrp3.0 to a working folder.
Download SuperSu zip & SuperUser apk then put them on your SD Card.
Install SD card into phone.
Step 1.A For Full ROM Flash and IMEI Write
Download Stock ROM and extract to working folder.
Move twrp3.0 to ROM folder.
Step 2
Install SP Flash Tool and SN Write Tool and run.
Step 3 To flash TWRP only
Reboot phone to recovery then wipe cache and dalvik. Can't remember if it is a dalvik option in the stock recovery now.
Power off phone. Make sure it is not plugged up to the computer.
IN SP Flash Tool:
Load scatter file that works from working folder.
Make sure download only is selected in drop down menu.
Check only the recovery partition box and click the name of the recovery file on the same line.
Browse to TWRP recovery image and select.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success.
Step 3.B OPTIONAL
Select format and flash all using stock ROM or images backed up from your phone.
Stock ROM must be extracted and custom recover put into same folder and renamed to "recovery.img" to make
everything automatically load.
Click the Download button with the green arrow.
Plug phone into computer and wait until window with OK pops up. Success
Step 4 Only needed when formating+downloading ROM
With phone still powered off and unplugged, write IMEI numbers using SN Write Tool.
Step 4.A
Click System Config.
Select IMEI in Write Option Area.
Make sure IMEI Checksum and Dual IMEI are checked.
Load MD1_DB and AP_DB files from ROM folder.
Click Load Modem DB from DUT box.
Click Save.
Step 4.B
Click Start.
Input your IMEI numbers from box.
Click OK. Success
Step 5
Boot to recovery.
Swipe to make permanent.
Wipe dalvik and cache.
Flash SuperSu..
Reboot.
Install SuperUser apk and BusyBox of your choice.
Step 5.A
If SuperUser apk or any app that ask for root permission cannot get it, reboot to recovery.
Mount system partition: Shouldn't matter but it worked for me.
Flash SuperSu zip again.
Reboot.
Install SuperUser apk and BusyBox of your choice.
ENJOY

When i connect the device after clicking download, it says "CHIP TYPE NOT match!"
mind you the device is off, i tried to troubleshoot but still getting the same error.
any help would be appreciated
UPDATE: Im thinking it has to be the scatter file, but im not sure.
UPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.

[QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.[/QUOTE]
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.

=smith901;72841007][QUOTEUPDATE: I got it to work, after flashing superSU, my phone wont boot past the initial white Blu start screen.
Click to expand...
Click to collapse
Try powering it off, booting to recovery and then wiping dalvik and cache.
The longest it took to get past that logo was 15 minutes. It is either encrypting or decrypting. Didn't get any type of messages until after root, and those were optimizing messages. Only one came through before rooting when I interrupted the boot process and that was about encrypting the phone. Phone was encrypted before root, now it is decrypted. Could have something to do with that. Try wiping the cache and dalvik after flashing. I actually flashed it three times in a row. The third was after mounting storage then flashing the SuperSu zip. Once you see the next logo with the colorful circles and hear the sound it might be another wait. That is where it let me know it was optimizing.
I must note: Please use scatter file to Readback your partitions so you can have a backup BEFORE ANYTHING. I didn't and it led me to take this route.[/QUOTE]

chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
ANJIII said:
chip type not match. pls help
Click to expand...
Click to collapse
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update

ANJIII said:
chip type not match. pls help
---------- Post added at 10:46 AM ---------- Previous post was at 10:41 AM ----------
what version of stock rom did you use? there are 3 versions in needrom; v7, v11, and v12. i use v11 cause of automatic update
Click to expand...
Click to collapse
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done

ANJIII said:
i solved my own problem hahaha. just rename the file to mt6737t instead of mt6735. also edit the platform in scatter file. change it to mt6737t too then install your supersu with the use of twrp then wipe dalvic then its done
Click to expand...
Click to collapse
Good. I had to name it that because of the chip mismatch error. It was from the V7 ROM. The other two are updates. I also messed up big time along the way. My phone always read MT6735 but it does have MT6737T in different files. I always wondered about that. I got it to work without buying another phone.

It seem that the phone boot logo never goes away. What should I do now?

Alexis96312 said:
It seem that the phone boot logo never goes away. What should I do now?
Click to expand...
Click to collapse
Hope you Readback your original recovery and other partitions. I didn't and worked hard to get it back. When I just flashed the recovery and something went wrong, it reverted back to the stock recovery.
Try doing this:
1. Start SPFT with the reçovery you want to flash.
2. Hold down the power button. AS SOON AS IT VIBRATES, PLUG THE USB CORD IN.
3. Hopefully you timed it right and it will flash and boot.
Sometimes it took 15 minutes to get past the boot logo.

Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please

Alexis96312 said:
Here what I did so far
1. Format using SP Flash Tool
2. Download /// By Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) Which it check all the boxes AUTO ///// It works but I didn't change the recovery.img like TWRP.img
Download it
It works normal.
___________________________________
But I want TRWP.img to be my recovery for root (SuperSU)
I try SP Flash Tool to change the recovery img to TRWP.img /// Using Scatter-Loading Files (MT6737T_Android_scatter.txt {From Rom}) I UNCHECK ALL BUT RECOVERY.IMG
Before this happen I didn't factory reset or Format anything yet.
It work to Recovery.img but THE BLU LOGO IS STILL LONG
I feel like it not working
Help Help Help ME
Please
Click to expand...
Click to collapse
Try flashing stock ROM, wipe data in stock recovery, then flashing TWRP, wipe dalvik.
If that don't work, wipe data then flash stock ROM with TWRP recovery, wipe dalvik.
The scatter file from the stock ROM gave me problems. Had to modify mine.
Don't forget to restore your IMEI afterwards since you formatted+flashed.

I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please

Alexis96312 said:
I will try
---------- Post added at 08:33 PM ---------- Previous post was at 08:23 PM ----------
I did try it but it seem not to do anything
Can you be so kind to upload the mod Scatter File Please
Click to expand...
Click to collapse
The one I attatched on the first post #1 is my modified scatter file. The mods included changing the size to the system, cache, and userdata. Just compared all three. The stock MT6737T scatter file and the V12 ota scatter are the same. The one I changed, MT6735, have the file name, platform name, and partition changes. I don't know why I had to modify it., especially the size parts. It all worked when I did that. I basically gave up on it because of a hard brick. Then I remembered reading MT6735 in some file a few months back while roaming the file system. Made the changes and was back in business. Maybe you need the stock scatter file, here it is.
It's what the end result of this post @ANJIII did minus the size changes..
He just did the name changes and it worked for him. Ya'll seem 180° from where I was.
The second one is from the V12 OTA update. It is very minimal, must be all that is needed for a scatter file. Not really sure tho. Hope it is just scatter file issues.
As long as SPFT is reading your phone, it's still a chance on it all working out. That is how I viewed it.
@andromedaXVIII Don't know if you got it working. This might be a potential solution.

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

Alexis96312 said:
Unable to find partition for path '/sdcard'
Is this good or bad? This is in Twrp recovery
Click to expand...
Click to collapse
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:
Code:
("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.

Alexis96312 said:
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
Click to expand...
Click to collapse
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.

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.
@Alexis96312, try to run this command in terminal to get your partition map:
Code:
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.
@ANJIII 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.

ScreenShot
ANJIII said:
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.
Click to expand...
Click to collapse
Answer in pictures

ADB USB
It seem that the computer can't find it what now
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?

Alexis96312 said:
It seem that the computer can't find it what now
Do I need to install the ADB driver again
Click to expand...
Click to collapse
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.

galaxy tab s2 9.7 SM-T813 to start device, enter password after stock rom flash

Hello,
So as the title says, i flashed my galaxy tab s2 9.7 with the stock rom, I am now getting a screen that says to start device, enter password. How do i get around this? Bare in mind i have no password as this is a clean flash.
Thanks.

ahewitt13 said:
Hello,
So as the title says, i flashed my galaxy tab s2 9.7 with the stock rom, I am now getting a screen that says to start device, enter password. How do i get around this? Bare in mind i have no password as this is a clean flash.
Thanks.
Click to expand...
Click to collapse
If you have twrp installed... Boot into it... Go to file manager (maybe under "advanced")... Go to Data/system and Delete the 3 locksettings files. Reboot and you should be good.

jhill110 said:
If you have twrp installed... Boot into it... Go to file manager (maybe under "advanced")... Go to Data/system and Delete the 3 locksettings files. Reboot and you should be good.
Click to expand...
Click to collapse
Hello,
i am visually impared, so use the ADB interface for twrp, but yes, twrp is installed. however, the data partition is encrypted. when i tried to access the data partition, i got a message about encryption. so i attempted to decript the data partition, and got the message: faled to decrypt data.
#6n.
still stuck, is it possible to just wipe data and erase encryption? i also can't see enough to input password guesses at the boot screen, so the command line for password input is my only option, as talkback isn't enabled on that screen.
Thanks,
Aaron Hewitt.

ahewitt13 said:
Hello,
i am visually impared, so use the ADB interface for twrp, but yes, twrp is installed. however, the data partition is encrypted. when i tried to access the data partition, i got a message about encryption. so i attempted to decript the data partition, and got the message: faled to decrypt data.
#6n.
still stuck, is it possible to just wipe data and erase encryption? i also can't see enough to input password guesses at the boot screen, so the command line for password input is my only option, as talkback isn't enabled on that screen.
Thanks,
Aaron Hewitt.
Click to expand...
Click to collapse
Boot into twrp. If it asks you to keep read only don't. Go to wipe. Select Format data and type yes. Tap the button it should format data.
Are you the original owner?
If so was FRP on?
If the tablets reset protection is on and you don't know the Google account name and password your probably the proud owner of a nice paperweight.
Also if the reset protection is on in a Samsung account and not accessible you have the same nice desk ornament.

jhill110 said:
Boot into twrp. If it asks you to keep read only don't. Go to wipe. Select Format data and type yes. Tap the button it should format data.
Are you the original owner?
If so was FRP on?
If the tablets reset protection is on and you don't know the Google account name and password your probably the proud owner of a nice paperweight.
Also if the reset protection is on in a Samsung account and not accessible you have the same nice desk ornament.
Click to expand...
Click to collapse
Unfortunately, twrp won't wipe the data. At all. Won't wipe, gives an error about being unable to mount.

ahewitt13 said:
Unfortunately, twrp won't wipe the data. At all. Won't wipe, gives an error about being unable to mount.
Click to expand...
Click to collapse
I would suggest samsung's smart switch.
Here's a link with a video to watch:
https://forum.xda-developers.com/tm...h-stock-firmware-using-samsung-t3079176/page1
There's a YouTube video link in the thread.
You can install the firmware using it or emergency install. Give it a shot.

jhill110 said:
I would suggest samsung's smart switch.
Here's a link with a video to watch:
https://forum.xda-developers.com/tm...h-stock-firmware-using-samsung-t3079176/page1
There's a YouTube video link in the thread.
You can install the firmware using it or emergency install. Give it a shot.
Click to expand...
Click to collapse
Smart switch will not connect, just sits on connecting to device. Even in download mode, i get an unsupported device error and the device does not show under emergency software recovery.

ahewitt13 said:
Unfortunately, twrp won't wipe the data. At all. Won't wipe, gives an error about being unable to mount.
Click to expand...
Click to collapse
FORMAT data not WIPE data.

ashyx said:
FORMAT data not WIPE data.
Click to expand...
Click to collapse
How would i do this with the adb twrp interface?
Thanks.

ahewitt13 said:
How would i do this with the adb twrp interface?
Thanks.
Click to expand...
Click to collapse
You can't, you need to tap the FORMAT DATA button under the WIPE options.

ashyx said:
You can't, you need to tap the FORMAT DATA button under the WIPE options.
Click to expand...
Click to collapse
no such luck, unfortunately. I cannot see enough to hit said button, and no speech in recovery.

ahewitt13 said:
no such luck, unfortunately. I cannot see enough to hit said button, and no speech in recovery.
Click to expand...
Click to collapse
OK you can try the following
adb shell
--wipe_data
OR
format DATA
But I'm not sure it'll be enough.

ashyx said:
OK you can try the following
adb shell
--wipe_data
OR
format DATA
But I'm not sure it'll be enough.
Click to expand...
Click to collapse
no such command, apart from now when i type twrp wipe data or anything like that, i get a twrp is not started, waiting for twrp to start. press control"+c to continue.

ahewitt13 said:
no such command, apart from now when i type twrp wipe data or anything like that, i get a twrp is not started, waiting for twrp to start. press control"+c to continue.
Click to expand...
Click to collapse
Boot to TWRP and type the following in ADB, be aware formatting wipes the internal storage:
adb shell
umount /dev/block/mmcblk0p39
mke2fs -t ext4 /dev/block/mmcblk0p39
Reboot twrp and data should be formatted.

ashyx said:
Boot to TWRP and type the following in ADB, be aware formatting wipes the internal storage:
adb shell
umount /dev/block/mmcblk0p39
mke2fs - t ext4 /dev/block/mmcblk0p39
Reboot twrp and data should be formatted.
Click to expand...
Click to collapse
Ok, i did this, what next?
When I flash the stock rom, the device does not boot, so I flashed twrp, and it shows that the ownly folder in internal storage Is the 'twrp' folder.

ahewitt13 said:
Ok, i did this, what next?
When I flash the stock rom, the device does not boot, so I flashed twrp, and it shows that the ownly folder in internal storage Is the 'twrp' folder.
Click to expand...
Click to collapse
After a format it takes at least 10 mins for the device to boot as the file system needs to rebuild.
Also check that data is mountable in twrp.

ashyx said:
After a format it takes at least 10 mins for the device to boot as the file system needs to rebuild.
Also check that data is mountable in twrp.
Click to expand...
Click to collapse
Is it worth noting that when I formatted, it would not process the -t and ext4 part of the command, it said invalid blocks, so I removed them. I left it all night charging and still nothing. The screen Is lit up but that's all I can tell you.

ashyx said:
After a format it takes at least 10 mins for the device to boot as the file system needs to rebuild.
Also check that data is mountable in twrp.
Click to expand...
Click to collapse
nothing happens. I've left it for a good hour now.

ahewitt13 said:
Is it worth noting that when I formatted, it would not process the -t and ext4 part of the command, it said invalid blocks, so I removed them. I left it all night charging and still nothing. The screen Is lit up but that's all I can tell you.
Click to expand...
Click to collapse
That explains it. It's important to have those flags as without the data partition will be formatted to ext2.
Are you typing the command exactly as posted, I suggest copy and paste?
Any incorrect spaces will cause issues, ensure there is no space between - and t
EDIT: just realised there was a space in my post between - and t
Damn auto complete!
Sorry about that.

ashyx said:
That explains it. It's important to have those flags as without the data partition will be formatted to ext2.
Are you typing the command exactly as posted, I suggest copy and paste?
Any incorrect spaces will cause issues, ensure there is no space between - and t
EDIT: just realised there was a space in my post between - and t
Damn auto complete!
Sorry about that.
Click to expand...
Click to collapse
Done, copy and pasted exact commands then flashed stock rom. No dice.

(Guide) Get TWRP Working with Data Access on Stock [UPDATED]

Thanks to @seadersn and @SGCMarkus, Markus's new TWRP makes things extremely simple now.
What you need:​SGCMarkus's TWRP
fstab.judypn with forceencrypt set to encryptable.
magisk
and the .magisk file​
Instructions:​
1. Follow the instructions to boot and install TWRP on SGCMarkus's TWRP thread
2. While you're still in TWRP, mount vendor and push the fstab.judypn with:
Code:
adb push path/to/fstab.judypn /vendor/etc
3. Format data via TWRP.
4. Push the .magisk to /data (For dm-verity reasons. It will restore the fstab.judypn with forceencrypt enabled) with:
Code:
adb push path/to/.magisk /data
5. Flash Magisk.
You're done! No bootloops this time. XD

i want to try this at some point. When i did before, the screen was black. Thanks for the guide!

I need to get US pie on my device but will be doing this

i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....

dreamss29 said:
i got some issues..
i cant mount system_root and i saw there is no /system_root/system/priv-app folder... so i took modified LGSettings.apk to sd card and i put it to /system/system/priv-app/LGSettings... then i format userdata in fastboot,i got twrp loop.....
Click to expand...
Click to collapse
Flash the magiskpatched boot img included in the files

I just had my bootloader unlocked. I am trying to install TWRP, but if I flash stockpiemagisk.img or TWRP-judypn-2019-07-01.img then use the buttons to choose a factory reset I just get bootloops. I select yes both times, just like normal and it loops until going to a fastboot screen. I can then flash the original magisk_patched.img I got from the guy who unlocked my bl, but no TWRP. Even he wasn't sure why this is happening. Any ideas anyone?
Also, in case its related, I lost download mode and can't get that back even by flashing an original backup of laf_b or the lgup compatible laf. I had download mode and flashed Pie before the bl unlock...
Edit: I got download mode back. Turns out when he was unlocking the bootloader he flashed abl_b incorrectly. Once I flashed it correctly DL mode works... Now for TWRP...
NVM.... found the problem...

I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.

I am able to get to TWRP but the fastboot-loop has changed. The image attached is what I get. I suppose in my attempt to remedy, the wrong Laf files have been flashed. It's V405UA20a

Hello mister
Actually is it possible to flash this stockpie.img on a V406EBW ?
Regards
Fred

avaie said:
I have an issue. After clearing the userdata procedure, this attached images is what I get. It's a reddish boot-up screen. The Active Slot also defaulted to B (as opposed to A). I have a fastboot-loop. I am wondering where I went wrong. I completed a successful procedure on another device hours ago. LGUP does not function as well. The phone defaults to Fastboot.
Click to expand...
Click to collapse
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.

crubbish said:
I have exactly the situation you described (fastboot loop + pink letters screen when I try to get into DL mode). If you've managed to rectify this, can you please give me directions. Thanks.
Click to expand...
Click to collapse
Hi - I eventually lost root and the system factory-reset after an attempt to boot into TWRP. I have scheduled to have VLAD reflash the entire phone. My bootloader is unlocked though but don't think much can be done. There might be other variables that might be affected.
If there is a guide to using Octoplus, it will be appreciated. It also seems telegram is the new medium for development.

avaie said:
I have scheduled to have VLAD reflash the entire phone. .
Click to expand...
Click to collapse
That's what I plan to do as well. Thanks for responding!

crubbish said:
That's what I plan to do as well. Thanks for responding!
Click to expand...
Click to collapse
All the best.

will try out to follow up this info

When I follow step 3 "Format data via TWRP", at the end of the format it says:
"Updating partition details...
...done
Full SELinux support is present.
WTP Enabled
Formatting Data using mke2fs...
Done.
You may need to reboot recovery to be able to use /
data again.
Updating partition details...
...done
UNABLE TO MOUNT STORAGE, DECRYPTION NEEDED FIRST"
I don't think that's good... Or is it?

Please Clarify/Help
I have managed to get TWRP installed and working but did not notice to do this. I went ahead and used Android already only to find that I need to do this.
I have booted into TWRP but cannot select vendor to mount it. Everything except system and vendor (and USB-OTG because there is not attached) will let me check them. But not vendor.
Do I have to go all the way back and re-install TWRP and to this before I do ANYTHING else? Do I have to do this while I am still in TWRP loaded from the image on my PC?
I realize this will loose all I have done within Android and that is the price I pay for not reading in detail. But I want to make sure this is the last time.
Thanks!

Not What I Expected - Decryption Failed!
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks

whitedavidp said:
I went ahead and re-installed TWRP from fastboot per the Markus thread After rebooting back into TWRP I then followed instructions in the 1st post here.
I could not mount vendor but I saw messages saying it was busy. So I assumed it was not unmounted and went ahead with the push to /vendor/etc. It reported successful from adb. And in TWRP file manager I can see a file named /vendor/etc and in the terminal I can cat its contents which look like what I see on my PC.
I then wiped the /data only using advanced wipe and it used makefs, not format.
I then pushed .magisk to /data and it too reported successful from adb.
I then flashed magisk and that seemed successful as well. Inside to TWRP's file manager, I was able to see the .magisk and various folders under /data. This seemed promising enough.
I finally rebooted to system and got shown what is in the attached screenshot. At that point, I had no option but to agree to the reset. When I touched that button, I was returned to TWRP. So I powered off from TWRP and tried to restart the phone. Once again I get the same decryption unsuccessful.
So I seem to be in a TWRP loop. How to proceed? Thanks
Click to expand...
Click to collapse
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers

whitedavidp said:
Well, as they say, if at first... I went through the steps here again. I made sure I hit the format button instead of wipe. And I made triple sure that everything was where it seemed to need to be and looked right. When I finally rebooted to system, I am now in Android setup as expected. To see if there is still encryption (ie, TWRP can see and backup /data) remains to be seen. Cheers
Click to expand...
Click to collapse
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks

whitedavidp said:
Sadly, once finished with a minimal Android setup I went back into TWRP and /data shows nothing. In backing up, it shows /data as 0 bytes. So I presume this means I am still encrypted. Is there no way out of this hell? Thanks
Click to expand...
Click to collapse
Here's the thing I would try. Load up LGUP and reload a stock kdz. Make sure that before you begin futzing with the phone, you are booting from Slot A.
Then retrace all the steps carefully. And don't set up anything on the phone until you have reached nirvana (bootloader unlocked, unencrypted, Magisk installed).
You'll get there.
[NG]Owner