Database Develop

After installing aroma guestekrnL phone only boots to CWM

Hello
I've tried installing guestekrnL on WIUI. When installing guestekrnL, the only thing I've ticked extra that was other than defaults was:
"Activate init.d functionality and convert file system to EXT4?
- yes
select if init.d is not working yet or if you don't know"
Well, after reboot WIUI was screaming that my sd card is broken and format may help. It formatted it, but it still didn't work. So I've rebooted to recovery via option in power dialog in order to restore old firmware. However there's a problem now: CWM Touch says that it can't write logs to /cache. Mounting /cache, /data or /emmc from recovery doesn't work, only /system and /sdcard are mounting correctly. I've tried BackToExt3 with no luck. I've tried wiping it many times, with no luck. My phone only boots now to CWM. I can't flash stock via APX mode, because I have broken USB port in my phone. What can I do?

Does restoring a backup, flashing a zip file or wiping work?

Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558

exinepl said:
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
the Touch CWM might be the issue......most of the times it is found as the source of some unknown issues for some or intermittent issues.
I use the non-touch one always
Hope it helps

Well, how do I flash new recovery from CWM using zip then?

exinepl said:
Well, how do I flash new recovery from CWM using zip then?
Click to expand...
Click to collapse
check for the CWM thread by Rusty....you have the instructions and process in it.
THERE YOU GO>>>SEE HERE
Hope it helps

Unfortunately, it needs USB. I need to flash it via existing recovery.

Mounting problems occur on some zips using touch recovery . Change cwm to non touch 5.0.2.8. But hey, did you flash a stock kernel on wiui ? you need another kernel, like etana, symbiosis.....or just use the one shipped with rom

[Q] cannot root

i just purchased an HTC ONE and was successful in unlocking and installing TWRP..whereas i flashed TWRP via fastboot...
when i rebooted into recovery everything was as good as expected but ran into a problem installing superuser via recovery..
when i start recovery and i come to the start screen,,,i click on install but cannot access the superuser.zip file..it does not find the superuser.zip file...and if i try to browse for that file it will not let me mount the storage,,,it will only let me mount the internal storage where the superuser file is not located...
when i click on "install zip from sdcard" it shows E:cant mount /cache/recovery/command as well as
E:can't mount /external_sd
i have tried to install different recoveries and they seem to work fine but i get the same thing when i try to install superuser.zip
it seems to me that i am not able to access that specific partition where the .zip files reside
hopefully i am just overlooking something simple but i've been round and round and cant seem to work it out..
i have had an evo 3d in the past and successfully unlocked/rooted/and installed ROMs before so i am not what some might call a newbie at this..
BTW,,,,i installed Hansoon2000's HTC One All-In-One Toolkit and started to tinker with that as well..there is an extra where one can sideload a ROM so i figured i'd try that to see if it would load the superuser.zip.
it found the package,,opened it,,,installed it,,copied,fixed permissions,symlinked and showed the installation as complete..but alas no root...
any help would be greatly appreciated

spurfan33 said:
i just purchased an HTC ONE and was successful in unlocking and installing TWRP..whereas i flashed TWRP via fastboot...
when i rebooted into recovery everything was as good as expected but ran into a problem installing superuser via recovery..
when i start recovery and i come to the start screen,,,i click on install but cannot access the superuser.zip file..it does not find the superuser.zip file...and if i try to browse for that file it will not let me mount the storage,,,it will only let me mount the internal storage where the superuser file is not located...
when i click on "install zip from sdcard" it shows E:cant mount /cache/recovery/command as well as
E:can't mount /external_sd
i have tried to install different recoveries and they seem to work fine but i get the same thing when i try to install superuser.zip
it seems to me that i am not able to access that specific partition where the .zip files reside
hopefully i am just overlooking something simple but i've been round and round and cant seem to work it out..
i have had an evo 3d in the past and successfully unlocked/rooted/and installed ROMs before so i am not what some might call a newbie at this..
BTW,,,,i installed Hansoon2000's HTC One All-In-One Toolkit and started to tinker with that as well..there is an extra where one can sideload a ROM so i figured i'd try that to see if it would load the superuser.zip.
it found the package,,opened it,,,installed it,,copied,fixed permissions,symlinked and showed the installation as complete..but alas no root...
any help would be greatly appreciated
Click to expand...
Click to collapse
Try using the toolkit to sideload a Sense-based ROM, they come already rooted.
Sent from my HTC One using xda premium

what is the point in that ,,,,if i wanted to install any rooted apps i would not be able to..
there has to be someone with this same issue..
it seems that i am not able to get superuser to install to the correct partition

spurfan33 said:
what is the point in that ,,,,if i wanted to install any rooted apps i would not be able to..
there has to be someone with this same issue..
it seems that i am not able to get superuser to install to the correct partition
Click to expand...
Click to collapse
My thinking is that you wouldn't have to install superuser.zip - the ROM has it pre-installed already. Where /what folder have you saved the superuser.zip you're trying to install? Also, try clearing cache/davlik cache

All-In-One Toolkit try it again install cwm then permanent root i had your problem that worked for me had to do it 3 times to push super user

jaythenut said:
All-In-One Toolkit try it again install cwm then permanent root i had your problem that worked for me had to do it 3 times to push super user
Click to expand...
Click to collapse
i have tried that several time but keep getting this
C:\Users\mark\Desktop\One_M7_All-In-One_Kit_v1.2\data>adb shell "echo 'boot-reco
ery ' > /cache/recovery/command"
system/bin/sh: can't create /cache/recovery/command: Permission denied
C:\Users\mark\Desktop\One_M7_All-In-One_Kit_v1.2\data>adb shell "echo '--update_
ackage=SDCARD:SuperSU.zip' >> /cache/recovery/command"
system/bin/sh: can't create /cache/recovery/command: Permission denied
C:\Users\mark\Desktop\One_M7_All-In-One_Kit_v1.2\data>adb shell "reboot recovery
Reboot: Operation not permitted
C:\Users\mark\Desktop\One_M7_All-In-One_Kit_v1.2\data>pause
Press any key to continue . . .
C:\Users\mark\Desktop\One_M7_All-In-One_Kit_v1.2\data>
i have my device unlocked and TWRP successfully installed
i put this file (Android_Revolution_HD_Root_and_BusyBox.zip) on my thumb drive and tried to install it from OTG but with no success..when i do that i lose my recovery and have to reinstall that via fastboot

i just tried the AIO toolkit again to reinstall TWRP and to have it install the superuser files...
everything goes as planned but after the TWRP install it reboots onto fastboot where i am supposed to enter recovery,,,but when i do it says that i am entering recovery but never does,,,therefore it will not install the superuser files..
the only other way i can get a successful recovery install is if i flash one via fastboot,,,but then i cant find a way to install superuser ,,once i enter recovery when i click to install a superuser.zip file i cannot find the one i placed on my phone ...
in the video tutorials it shows that when i chose to install the superuser.zip file i navigate to the download folder,,,,but there is not such folder.
i placed the superuser.zip file on a thumb drive and navigated to it and clicked on it to install,,,it said that it installed but it didnt,,,i assume thats because it needs to be placed in a system folder

FINALLY !!!!
OK,,,i finally got it all wroking,,,i think,,,,,LOL
i followed the instructions here http://forum.xda-developers.com/showthread.php?t=2236620
come to find out that the partitions needed are hidden and are set so where one cannot write to them...
alot of digging allowed me to stumble across this...
thank you to everyone for all the help and patience

Bootloop after CM install. Won't restore backup, mount /data, flash stock

Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...

I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse

[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.

Need help with Rooting Moto G(6)

I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it

VineelKumar said:
I have installed TWRP, in recovery when im trying to install dm_verity file i'm getting error - "unable to find boot block location". can someone help how to flash it
Click to expand...
Click to collapse
You have to format data using the type "yes" to continue method. Then use twrp's menus to reboot back into recovery. Mount /system and /vendor in twrp then flash it. If you still have a problem, then try the 5/21/19 release of the disabler.

@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.

WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
It doesn't show data as mounted. It shows the external sdcard as being mounted. And there is an error, twrp is giving error 1, and the disabler is also showing an error saying it can't find the boot block location. This means twrp isn't able to modify block devices or mount them properly. What I told him to do will fix the problem. The script doesn't mount anything correctly if twrp is not able to run the script... I know what I'm talking about. I wouldn't steer the guy wrong.
Edit: I'm definitely correct. What I said is actually mentioned in the official twrp thread for this device. It says; "If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again." - direct quote from the instructions, under notes.

I flashed the same .zip with /data, /system and /vendor mounted properly and ran into the same error... (see screenshot)
To mount a device block it's not neccessary to have /data mounted.
The .zip is incompatible with Moto g6 - that's all!

WoKoschekk said:
@Spaceminer No, that's nonsense! Data is mounted correctly and is fully unencrypted. See screenshot where you can read "Updating partition details... done" There's NO error message.
That's the first thing...
Second, there's no need to mount sth manually, the script itself will do this if necessary!
@VineelKumar Download the dm-verity-disabler.zip by Zackptg5 from
https://zackptg5.com/android.php#disverfe
This will work with your device.
Click to expand...
Click to collapse
Thanks it worked fine. But for some reason the mobile was struck in boot loop(just warning message on screen saying, you have unlocked bootloader for couple of seconds and then same thing appears again), any idea how to fix it ?

VineelKumar said:
...any idea how to fix it ?
Click to expand...
Click to collapse
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
The magisk.zip also removes dm-verity within the installation process. So you don't need the disabler.zip for this.
To remove forceencryption you have to follow a few simple steps which are given in my instruction below:
preparation:
You have to be on the latest stock firmware with TWRP installed and nothing else.
Boot into TWRP and format /data (do not wipe it! you must use format). Then reboot directly into TWRP!!
Now let's start to remove forceencryption.
1.) place the attached .tar.gz file in your internal storage (/sdcard)
2.) mount /vendor in the options menu and open TWRP's terminal command under advanced settings
3.) type in (or copy it from here)
Code:
tar -xvzf /sdcard/fstab.tar.gz
4.) at next boot your device will be unencrypted
Now don't reboot your device and stay in TWRP to install the magisk.zip v19.3!! That's important to flash v19.3 instead of the latest v20.3 otherwise it causes a bootloop!! I don't know why it does but you can later update Magisk without any problems through the Magisk Manager.
Magisk will now remove the dm-verity during the installation process. That's a part of the installation script of Magisk.
When the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.

WoKoschekk said:
Yes, do it manually. The disabler.zip does two things on your device.
1.) remove dm-verity
2.) disable forceencryption of /data
...
the installation of Magisk has finished you can boot your device into system. Maybe it reboots one time but don't care. Also the bootanimation will take some time due to unencryption of /data. That's quite normal.
Click to expand...
Click to collapse
I appreciate your patience, WoKoschekk. I for one appreciate the guide and insight into the reason root must be achieved this way. I was using 20.3 and 18 the whole time. I was successful with your instructions the first time. It became stuck on boot after the initia reboot, so I pushed fstab and magisk again and it was fine. I remember that on one phone, encryption wasn't a problem if you had your pin or password. Could it be the same here provided there was no fingerprint assigned (might be the original pixel)? I'm guessing this TWRP can't decrypt? Just curious, because N/A balogna.

I'm glad to hear that!
TWRP for Moto g6 can't decrypt your data. That's the reason why you must disable forceencryption to use TWRP.

WoKoschekk said:
Code:
tar -xvzf /sdcard/fstab.tar.gz
Click to expand...
Click to collapse
I don't have a SD card, so I put the file into the TWRP folder. I then used,
Code:
tar -xvzf data/media/TWRP/fstab.tar.gz
Was that the right location?

/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot

WoKoschekk said:
/data/media/0 = /sdcard
/external_sd = external SD in SD-card slot
Click to expand...
Click to collapse
Ok, I see now. Anyway all updated and rooted with your instructions, thanks.