Hello,
I know, that professionals usually don't like these questions but I really want to know sth:
I recently installed Froyo 2.2.1 with Kies Reg Patcher and it works GREAT! The only thing that matters is the old RFS file System.
So I decided to install the Voodoo lagfix.
I put the update.zip in my root/sdcard and tried the following:
1. I started the DOWNLOAD Mode - but only the yellow shield appeared - nothing happened as expected (maybe nothing to download?)
2. I started the RECOVERY Mode and selected "Apply update.zip". ==> It was telling me after 2 seconds "Error ... unsigned ..."
==> I knew this is caused by the new recovery assistent. After all I rebootet my phone and every thing works like it was before.
Now the questions:
1. Is my system unchanged? I mean has the update.zip file copied some files until it aborded?
2. Is it bad when I turn my phone in Download mode? I mean it didn't flash/download anything - so does it really damage my phone when I press the power key 5 sec and restart my phone (ONLY IN THIS SITUATION - I know that pressing it during an update process/by appearance of the status bar can damage the phone).
Please give me some answears!
PS: By the way, on woodoo-project.org it is written that the update.zip mode "...works with clockworkmod" - what is this for a mod? I googled but I only found variations about it - not a documentation and their website seems o be down.
Has this mod automatically been installed before the "Unsigned Error" came?
LG,
Dennis
In order to have your phone lag fixed, you need to root the phone (root: complete system access of your phone).
1. In download mode the phone wont update anything on its own. You need to use odin for flashing (installing) through the computer.
2. In froyo 2.2.1 you have a 3e recovery (which only updates with signed apk's) - your update.zip file is custom hence its unsigned.
about your q's
1. Your system has not been changed as the process was aborted (no files are copied or changed)
2. Its completely safe to restart you phone in download mode if you aren't flashing anything.
Note: In order to use voodoo lagfix you need to get 2e recovery for flashing custom unsigned apk's. This can be done by using CF root method (this will root your phone and also install ClockWorkMod - CWM). CWM will allow you to install the update.zip.
*For more info. just check the thread about rooting/lagfix etc. to get step by step instructions.
Thank You very much! Now I get it!
Ok
Please forgive me I have spent up to 7 hours today searching and trying but to no luck.
So I didnt realise what i was doing and Semi Bricked my Phone. I edited build.prop and saved it in MyExplorer(name?) to try and turn off the camera sounds and when I rebooted, it just gets stuck on the galaxy S 2 screen, boot loop.
I'm on SGSII (Australia) Stock Vodafone's ICS 4.0.3 Rooted.
I have CWM installed but tried a few things:
- I can get into Download MOde (no idea what to do here)
- I can get into CWM mode 5.0.2.7 Recovery mode but cant do anything still.
- I tried various Edify script builders to try and put the original build.prop back in but get multiple Status 0 errors whenever I try update.zip from the SD card.
- I tried rebuilding the backup on there and changing the build.prop file on there and trying to restore but MD5 check fails. Even tried rebuilding the MD5 file with the modified files and still no luck. MD5 files fails.
Would anyone have any suggestions and how to resolve this without a flash or wipe? I didnt back recent backup and will lose everything.
I am coming to a point where I really am wanting to back to Apple
There are 2 build.props attached. One is the bad one that stopped me from booting up and I found another one that was named .bak (extension taken off) I found in the same directory (/SYSTEM)
If anyone can help me build an update.zip to push in via CVM I would greatly be in your debt (I tried for 4 hours with no luck)
If you have recovery and download mode yet nothing is lost.
In first, do saved your apps ?
If you had saved them or if it doesn't matter to you, reflash a rom via recovery
LINK HERE:
http://download.cyanogenmod.com/get/jenkins/2773/cm-9-20120615-NIGHTLY-galaxys2.zip
Flash it GoogleApps folder
http://goo.im/gapps/gapps-ics-20120317-signed.zip
The rom that I attached to the reply is a CM9 ICS version, it's quitly stable and we can have some settings on it.
If it doesn't work reflash with Odin (it's with software who use the Download Mode)
http://hotfile.com/dl/149514867/aea2f22/I9100XXLPQ_I9100OXALPQ_XEO.zip.html
Instructions
-Unzip the Rom Folder ( I9100XXLPQ..........)
-Open the included Odin
-Put your phone on Download Mode
-Click PDA and select I9100_CODE_I9100XXKP*_CL*_REV02_user_low_ship.tar.md5
-Click PHONE and select MODEM_I9100XX*_REV_02_CL*.tar.md5
-Click CSC and GT-I9100-MULTI-CSC-OXA*.tar.md5
-Click Start and don't touch anything still the colored case become green
-And now your phone resurrects
Reply me of results
thanks for your reply
unfortunately i didnt save my apps and havent got backups of my data either
i cant reach the file via ADB either, when i run ADB (have KIES installed and worked before) - adb devices.
nothing shows up when the phone is stuck on "Samsung GS2" screen.
do you have any recommendations around keeping my data there?
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
understood thanks
what if i just want to flash build.prop via update.zip?
i tried so many methods but it always fails. is anyone able to create a update.zip for me?
i used a GUI script creator to try and update it via CWM recovery mode but it doesnt seem to like it.
If i turn off signature verification, it gives me a (status 0) error saying : E: Error in /sdcard/update.zip
and if i turn on verification toggle, it says E: signature verification failed
can anyone help?
calum96 said:
If you find the exact same software your on now to download you could try flashing that in cwm without wipes I think that would work i think it replaces all system stuff so it will work, worth a try
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i know there are 2 types of ROMS right? the nonwipes and wipes. i really dont want the wipe versions.
the one i downloaded is 1G which i'd imagine is the wipe version if i were to upgrade via odin?
http://www.androidaddicted.com/firm...-vodafone-australia-firmware-update-1267.html
Can you mount any sd on your pc, because you can the recovery mount trick to access to your data.
When you are in the recovery menu, go to mount and storage and click on "mount usb storage" and the internal and external sd will appear on your pc.
you are posting in galaxy s thread....repost in galaxy s2 thread
I don't think so but then again I don't own a s2 but you can select advanced restore: restore data then flash a compatible ROM, then restore the data if you worried but as I said before flashing the same ROM shouldn't remove user data
Sent from my GT-I9000 using xda premium
Hello,
Problem - Device keep on rebooting showing Mi logo (every 2 sec), Does not boot into system
What I did?
exteneded system partition to 1.2 gb - success
flash Marshmellow custom rom - success
misinstalled system ui of theme - system ui stopped
reinstalled clean rom from custom recovery - success
then it does not boot into system - keep on rebooting at mi logo (every 2 sec)
tried fastboot rom - failed (remote size too large)
rebooted into recovery
flash stock partition via adb - success
fastboot flash (with flash all) - success (says miflash - operation compeleted successfully)
Still it does boot into system - keep on rebooting at mi logo (every 2 sec)
Help?
if you can access recovery now then go to recovery and take a backup of current rom. The wipe everything except internal storage and then restore the backup.
maybe it'll fix it because thats what happened to me too after flashing the MM custom rom. Every time i was rebooting the phone kept bootlooping at Mi Logo.
Hmm i ll try but i have to install twrp from adb for backup.
Cwm backup not promising.
You think there ll be problem in hardwere?
No problem in hardware.
and yes do it twrp only. never try cwm.
the thing is i am not able to enter into recovery mode at all.
No recovery and fastboot accessible.
Then connect it to PC and tell me what name the device manager shows for the device.
fastboot is accessible.
i've flashed fastboot rom from miui. successfully completed. but it won't boot.
yesterday it booted into system so i was charging the phone, as soon as i removed charger it went the same boot looping.
now,
clicking flash_all_except_storage from fastboot command
it shows one line in every process - 'target reported max size 80909989 '
process goes on and success.
but does not boot into system. same bootloop.
one strange thing is,
when i connect to pc, - just by pressing vol down button i'm entering to fastboot. (even without holding power button)
does this mean there's something wrong with power button which causing cont. reboot? i mean it cont. forcing system to on and off? :s
Nothing is wrong with the hardware. In this situation the phone boots into fastboot by pressing vol when plugged in.
You didn't answer my question. What does it show in device manager on PC.
sorry for late reply , net connection loss
device manager
1st one is android booloader interface
other devices - bluetooth peripheral devices
Did you use miflash tool to flash fastboot rom
yes,
flashed successfully says miflash.
While flashing using miflash did you select all files in advanced menu properly.
Like all the bat, mbn and xml files.
i didnt try all the file separatly.
trying now.
Then go to advance and choose all the respective files properly.
1st one - flash_all_except_storage.xml
2nd one - nvflash_all.bat (leave it as it is)
3rd one - MPRG8974.mbn
4th one - 8974_msimage.mbn
5th one - rawprogram0.xml
6th one - patch0.xml
i found
flash_all.bat
could not find nvboot script
flash programmer
boot image
could not find kernelflinger image
could not find UFS provision image
RAW xml file
patch xml file
should i go with files?
Which MiFlash tool are you using.
I used the 2014.05.09.0 version
Try this one.
And extract the fastboot ROM twice till you get the images folder inside the "cancro_images_V7.0.****" folder. There you'll fill all the files.
Then in miflash click browse and select that images folder.
And in advanced options select the respective files which are there outside the images folder.
2015.10.28 version
i ll leave the navboot as it is.
giving it a try.
appreciate your help brother.
If it doesn't work then try my version.
It has proper names of files. To avoid confusion.
And all files are there in fastboot ROM except nvboot
i checked on miui
no halos.bin
tz.bin
these all files?
p.s.
operation completed successfully but same boot loop.
trying your version now.
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.