Database Develop

[HELP NEEDED] TRWP + Recovery - Partition Corruption???

Hi all,
I used the SRK Tool recently to TWRP and Root.
All was going well until I used hisuite to restore my phone.
It failed in restoring one app and it created a cache file in data/data, tried deleting the file in ES File Explorer, SD Maid to no avail.
So I went to format the partitions in TWRP.
The phone won't start (im guessing there is no OS so I am looking for the stock rom as the hisuite recovery doesnt work as well.)
TRWP Factory Reset is still showing the same following error
Updating partition details...
Error opening: '/data/data/renamedeleteapp/app_xwalkcore/Default/Cache/5de9a45e57c756c2_0' (No such file or directory)
...done
Click to expand...
Click to collapse
Anyone able to shed some light on how I can fix this corrupted partition and reload an OS so my phone works again?
Thanks!!!

the huawei erecovery system doesnt seem to be working either.
Nor does the hisuite recovery. Asking me to bring it to the service center

Managed to flash the new world ROM but the partition error still persisting. Anyone?

I would say probably your best bet is to use the stock rom here ... http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 to restore completely to stock and then start again from scratch

Phone cannot be flashed via eRecovery/dload/TWRP+update.zip

I botched up a ROM installation and now my phone cannot be flashed using dload (it doesnt accept any type of update.app since it says that it is incompatible), and eRecovery is not finding its package info every single time. On flashing the official ZIP file via TWRP, it always says that the /data cannot be mounted due to "device or resource busy".
Can someone help me? Thanks!

jaceleon said:
I botched up a ROM installation and now my phone cannot be flashed using dload (it doesnt accept any type of update.app since it says that it is incompatible), and eRecovery is not finding its package info every single time. On flashing the official ZIP file via TWRP, it always says that the /data cannot be mounted due to "device or resource busy".
Can someone help me? Thanks!
Click to expand...
Click to collapse
Device or resource busy shouldnt be a problem, the flash will be fine.
Goto twrp
wipe Cache, Data, Cust, System, Vendor, Product
flash for EXAMPLE EVA_L09_C432_B386_update.zip (dont try to flash the update.app only)
flash for EXAMPLE B386_update_data_full_EVA-L09_hw_eu.ZIP.
Reboot System
If this is not working or you already tried the tings i mentioned above you can extract the Update.app and flash the essential partitions with fastboot (watch out my friend)

This did the trick! Thanks!

Bricked phone

Hello,
First of all, my version was l19c185b385
I wanted to install marshmallow instead of nougat because of Xposed. Anyway, I didn't want to use rollback package (I didn't know that I can't install marshmallow like that) so, I just opened TWRP and then I removed everything even the system. Now, I can't install MM it always gives me the error "sparse flash write failure" in fastboot; however, when I installed b385 it finished the installation. In addition, I can't install anything for MM like recovery and twrp.
At the moment I can access only to trwp, fastboot, erecovery and dload (although it never works for me :crying
PS: I have tried to install rollback package via dload but it said it isn't compatible and stopped at 5%

IDontKnowAnythingAtAll said:
Hello,
First of all, my version was l19c185b385
I wanted to install marshmallow instead of nougat because of Xposed. Anyway, I didn't want to use rollback package (I didn't know that I can't install marshmallow like that) so, I just opened TWRP and then I removed everything even the system. Now, I can't install MM it always gives me the error "sparse flash write failure" in fastboot; however, when I installed b385 it finished the installation. In addition, I can't install anything for MM like recovery and twrp.
At the moment I can access only to trwp, fastboot, erecovery and dload (although it never works for me :crying
PS: I have tried to install rollback package via dload but it said it isn't compatible and stopped at 5%
Click to expand...
Click to collapse
Well done. Well done.
Try to flash firmware as zip file via twrp.
Are you able to mount/unmount /system in twrp?

xtcislove said:
Well done. Well done.
Try to flash firmware as zip file via twrp.
Are you able to mount/unmount /system in twrp?
Click to expand...
Click to collapse
yes I can mount system, I can't flash the firmware as zip because i don't have it i mean the update.zip can't be flashed in twrp

IDontKnowAnythingAtAll said:
yes I can mount system, I can't flash the firmware as zip because i don't have it i mean the update.zip can't be flashed in twrp
Click to expand...
Click to collapse
Come on... You risking your phone here, why don't you do some research before you mess things up?
The zip file with the update. App in it (firmware) is flashable with twrp
Huawei Firmware finder app in play store and you are fine

xtcislove said:
Come on... You risking your phone here, why don't you do some research before you mess things up?
The zip file with the update. App in it (firmware) is flashable with twrp
Huawei Firmware finder app in play store and you are fine
Click to expand...
Click to collapse
I thought you can't flash a system.zip without meta-inf
Anyway I have flashed it and it didn't work
I have also download another copy of the system, and yet nothing changed
Edit: the errors are
32K crc checked failure
E: unknown command [error]
E: unknown command [error]
update_huawei_pkg_from_ota_zip: update package from zip failed
updater process ended with error: 7
error installing zip file '/sdcard/update.zip'
updating partition details
failed to mount '/vendor' (invalid argument)
failed to mount '/product' (invalid argument)
failed to mount '/version' (invalid argument)
...done

okay, i have managed to fully fix my phone thanks to you , but now i need to rollback can you teach me how? idk why but dload method always fail

IDontKnowAnythingAtAll said:
okay, i have managed to fully fix my phone thanks to you , but now i need to rollback can you teach me how? idk why but dload method always fail
Click to expand...
Click to collapse
Look for a dload folder on your internal storage, there could be another folder something with "hw" in the name but i dont know anymore what i like to say there are maybe leftovers from an OTA or something like this just delete any folder with zip files in it.
Maybe you have the wrong Rollback package.
The Rollback package from the second link in my signature works on EVAL09 and EVAL19.

Accidently wiped /system , /data of honor 5c NEM L-22 . HELP ME .

Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.

get stock recovery and install stock recovery, then install B100. why people dont get that when twrp says system it means system....

hubertchen37 said:
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
Click to expand...
Click to collapse
Huge mistake. Why did you wiped data and system?
Sent from my Honor 8 using XDA Labs

hubertchen37 said:
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
Click to expand...
Click to collapse
Hi ..
Install this package and done.
http://www.hihonor.com/in/support/details?DOC_ID=91134
Download this file
Extract it and u will find a file named UPDATE.APP .
Create a folder named dload in your sdcard.
Put update.app in the dload folder.
Insert sdcard in ur phone and shutdown ur phone now.
Click vol down + vol up + power (all three buttons) simultaneously.
It will start to install it , let it continue and then ur phone will reboot . Thats it ur phone is brand new again

gopinaidu77 said:
Hi ..
Install this package and done.
http://www.hihonor.com/in/support/details?DOC_ID=91134
Download this file
Extract it and u will find a file named UPDATE.APP .
Create a folder named dload in your sdcard.
Put update.app in the dload folder.
Insert sdcard in ur phone and shutdown ur phone now.
Click vol down + vol up + power (all three buttons) simultaneously.
It will start to install it , let it continue and then ur phone will reboot . Thats it ur phone is brand new again
Click to expand...
Click to collapse
yeah but before you do any of this install stock recovery.

thelous said:
yeah but before you do any of this install stock recovery.
Click to expand...
Click to collapse
Erecovery does the job

Hi @hubertchen37 , can i know if u had solved the issue ? if so kindly post what u had done to tackle this issue . will help for future members coming here.

Flash nougat stock ROM...b3xx something and have full ota-mp-pv,it will appear ndrm90-testkey......and then, flash rollback package for nem l-22(India).

gopinaidu77 said:
Hi ..
Install this package and done.
Download this file
Extract it and u will find a file named UPDATE.APP .
Create a folder named dload in your sdcard.
Put update.app in the dload folder.
Insert sdcard in ur phone and shutdown ur phone now.
Click vol down + vol up + power (all three buttons) simultaneously.
It will start to install it , let it continue and then ur phone will reboot . Thats it ur phone is brand new again
Click to expand...
Click to collapse
Hey i Thanks for the info man really appreciate it but its not working. it says "Software install failed. Incompatibility with current version. please download correct package."
More worst part it now i am not able to connect phone to pc via usb. So now i cant even flash stock recovery. I am screwed .

hubertchen37 said:
Hey i Thanks for the info man really appreciate it but its not working. it says "Software install failed. Incompatibility with current version. please download correct package."
More worst part it now i am not able to connect phone to pc via usb. So now i cant even flash stock recovery. I am screwed .
Click to expand...
Click to collapse
Incompatible package, can u tell me the model again?

gopinaidu77 said:
Incompatible package, can u tell me the model again?
Click to expand...
Click to collapse
Honor 5c NEM L22C675 i think he need the backup of OEM file...
---------- Post added at 02:27 AM ---------- Previous post was at 02:09 AM ----------
hubertchen37 said:
Hello Guys,
So i was in the urge to Root my Phone so i went ahead and Unlocked the bootloader for my phone Honor 5c Nem L-22 (India). Then I flashed Twrp Recovery and download supersu and moved it to my sdcard, and when got into recovery mode and i wiped /data , /cache, /system after that i installed supersu and when i was going to reboot my phone a message displayed saying "No OS intalled , Do you wish to continue" This was the time i knew i messed up (worst part is i never backed up my data). Now i am trying to install OS into my phone i downloaed few Firmware for my phone and even got stock firm, Now when i go to Twrp recovery to install the .zip file i get many error notice saying unable to mount /vendor, /product (invalid argument) Which i am not able to understand (I even tried to mount /vendor /product from Twrp Menu>Mount but not able to select the tick in those). Please help What can i do to make my phone working.
Thank you.
Click to expand...
Click to collapse
You need to Flash the Oem file through twrp then Copy the stock rom to the dload folder and try again surely it will work..

Ranjithksr said:
Honor 5c NEM L22C675 i think he need the backup of OEM file...
You need to Flash the Oem file through twrp then Copy the stock rom to the dload folder and try again surely it will work..
Click to expand...
Click to collapse
Flashing oeminfo will wipe version history. Just install oeminfo through twrp and then u can restore ur rom again.

gopinaidu77 said:
Flashing oeminfo will wipe version history. Just install oeminfo through twrp and then u can restore ur rom again.
Click to expand...
Click to collapse
Ok Can you please share here?

Let me know if you still having issues. I updated the oeminfo file in repo thread for 5c.
Use it to see if your issue resolves.

shashank1320 said:
Let me know if you still having issues. I updated the oeminfo file in repo thread for 5c.
Use it to see if your issue resolves.
Click to expand...
Click to collapse
Also plz try to share custom.bin

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