Hi,
I have got Galaxy SL GT-i9003. The problem is the /data partition can't be mounted. I have already flash stock rom + pit, but it doesn't solve the problem.
Now is there any HACK I can use to fix it ? right now I am stuck in bootlooping on GB and Encryption unsuccessfull on ICS [EHNDROIX] ROM.
Any Help is Really Appreciated. Thanks.
yokowasis said:
Hi,
I have got Galaxy SL GT-i9003. The problem is the /data partition can't be mounted. I have already flash stock rom + pit, but it doesn't solve the problem.
Now is there any HACK I can use to fix it ? right now I am stuck in bootlooping on GB and Encryption unsuccessfull on ICS [EHNDROIX] ROM.
Any Help is Really Appreciated. Thanks.
Click to expand...
Click to collapse
Greetings;
I don't know if you've solved your problem.
But i'll leave some tips.
First of all i want to mention that:
I also came from an ehndroix ICS Rom when i got that problem.
"emmc" Stands for external SDCard
"sdcard" Stands for Internal "SDCard"
Note: "sdcard" it's not an SDCard. This is the device internal storage with a little bit more than 1.5GB.
If you need to fix the emmc (the "real" external SDCard) you can download and install an application that (usually fixes many SDCard problems and size issues)
Application Name: "SDCard Formater"
Download Link: www.sdcard.org
Also know that most custom roms will resize your partitions; wich usually cause that error.
The common fix for your partition problems is to make a clean install.
For a clean install:
1) Remove SD Card
Note: Remove if you have important data there; or leave it if you will flash a ROM from there.
2.1) If you have CWM Recovery on your Device:
Reboot your device in CWM Recovery Mode.
Select: "Advanced" and Erase Dalvik Cache.
Go back and Select: "Mounts and Storage"
And Format:
- Data
- System
- Boot
- Cache
2.2) If you don't have CWM Recovery:
- Flash DDLF2 Full or Stock Firmware from sammmobile.com
- DDLF2 Full Link: http://forum.xda-developers.com/showthread.php?t=2329200
- Flash CF-Root (wich Contains CWM and Roots the Device)
- Reboot your device in CWM Recovery Mode.
Select: "Advanced" and Erase Dalvik Cache.
Go back and Select: "Mounts and Storage"
And Format:
- Data
- System
- Boot
- Cache
After that Power Off your device and boot into download mode.
Open Odin; plug the USB Cable; select the files in Odin (note that last 2 files are switched - Modem and CSC)
Press start; and wait untill Odin says "Pass".
Note that 1st boot takes longer.
Also do not remove the cable utill Odin says "Pass"
My device will restart 1 time for each Rom and CF-Root Flash and only then Odin will show the "Pass" message.
I'm not aware of any hacks.
But If there's a way to do it manually for this device (like in previous android devices) then it would be loading into a pseudo "bootloader Mode" wich i think it doesnt exist on this device.
If it does... The steps would be (briefly) Downloading android SDK; locate the folder wich contains adb.exe and fastboot.exe.
Copy | Paste that folder to an easier path to access it through terminal | command prompt.
"adb" will allow you to show all your partitions
"Fastboot" will allow you to erase|format partitions.
But like i said. I tried to do that on my device but without luck. Even with Vendor ID the device wont let me use fastboot.
My solution went to make clean installs.
Please press thanks if i helped you.
This will motivate me into researching more; provide more help; make some applets; tutorials and some more.
@yokowasis You have posted in the i9000 section. Best delete the text from this post and post it in some Galaxy SL thread.
tetakpatalked from Nexus 7 flo
Hi !
I tried to install Milaq Rom CM11 from CM10.1.
My partitions layout is ok :
- system 600 Mb
- cache 200 Mb
- media 6Go
- data ~20 Go
But, after flashing with CWM 6.0.4.6, the screen stayed blank.
So, i decided to format partitions, but i formated all partitions (i was tired :crying Now, i don't have access to my .zip on CWM.
How could i retrieve them to flash again ?? maybe with WebOS ?
Thanks for you help !
Bristow69 said:
Hi !
I tried to install Milaq Rom CM11 from CM10.1.
My partitions layout is ok :
- system 600 Mb
- cache 200 Mb
- media 6Go
- data ~20 Go
But, after flashing with CWM 6.0.4.6, the screen stayed blank.
So, i decided to format partitions, but i formated all partitions (i was tired :crying Now, i don't have access to my .zip on CWM.
How could i retrieve them to flash again ?? maybe with WebOS ?
Thanks for you help !
Click to expand...
Click to collapse
try sideloading your installation zips
Choose install from ADB Sideload in CWM. On your Computer type in a terminal: adb sideload image.zip, where image.zip is the file you like to flash.
Good luck on the sideload.
And you now have 10 posts and can post in the CM11 thread!
Flash with ADB sideload on Ubuntu
Thanks !
I tried with success adb sideload on Ubuntu.
It's pretty easy :
Code:
sudo apt-get install adb-tools
Go in to the recovery and activate sideload (install zip from / activate sideload...)
Code:
adb devices
in order to see if device is recognize
Code:
adb sideload rom.zip
That's all !
I like it :victory:
I've been able to do the beginning root process, but after entering TWRP I can not see the SuperSU zip file. I went back and transferred again to the internal storage- but my PC (Windows 10) said it was already there (I went ahead and added it which over wrote the original file)!
After I went back into TWRP- it is still not showing there (or the no-verity zip file or the aptX zip file which I ultimately want to install. ) It says also there is 0mb in the folder.
How come my file is not showing in TWRP? I have toggled the image/zip file setting in TWRP so that is not it...
Thank you!
hkdavexda said:
I've been able to do the beginning root process, but after entering TWRP I can not see the SuperSU zip file. I went back and transferred again to the internal storage- but my PC (Windows 10) said it was already there (I went ahead and added it which over wrote the original file)!
After I went back into TWRP- it is still not showing there (or the no-verity zip file or the aptX zip file which I ultimately want to install. ) It says also there is 0mb in the folder.
How come my file is not showing in TWRP? I have toggled the image/zip file setting in TWRP so that is not it...
Thank you!
Click to expand...
Click to collapse
Is it just this one file/folder or in the complete system?
Problem might be because of pin/pattern error. Hence TWRP might not be able to decrypt the data.
One working solution to this is complete factory reset which will erase internal memory ,
I suggest copying your internal memory to PC. Then goto bootloader and type
Code:
fastboot erase userdata
.
Then goto TWRP and advanced option and sideload Oxygen OS Rom.
The above process is highly experimental however I was able to do this successfully once when i had the same problem.
Might search a bit more before proceeding.
MoonBlade said:
Is it just this one file/folder or in the complete system?
Problem might be because of pin/pattern error. Hence TWRP might not be able to decrypt the data.
One working solution to this is complete factory reset which will erase internal memory ,
I suggest copying your internal memory to PC. Then goto bootloader and type
Code:
fastboot erase userdata
.
Then goto TWRP and advanced option and sideload Oxygen OS Rom.
The above process is highly experimental however I was able to do this successfully once when i had the same problem.
Might search a bit more before proceeding.
Click to expand...
Click to collapse
Well, I rebooted and everything worked... I was just hesitant to do anything... not sure what actually happened... but all seems OK now. Thanks for your reply.
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.
Hello
I try to install a custom recovery on my tf701 (android 4.3, USB debug ON)
here are the previous steps i did :
1/ i have unlock the bootloader using ASUS tools : OK
2/ i have root the TF701 : OK
for this, I installed Minimal ADB and Fastboot
I copy the files found here
and I lauch the command : adb reboot bootloader
then : fastboot boot zImage_dtb ramfs.img.gz
the root is ok
-------------------------------------------------------------------
3/ i try to install recovery
i download the file here : droidbasement.com/asus/tf701t/recovery/
i put the file in the folder of Minimal ADB and Fastboot
and i launch the commande : adb reboot bootloader
then, when the fasboot usb mode is ready on the device : fastboot flash recovery recovery.img
first time :
target reported max download size of 64382
sending 'recovery' (6652 KB)...
FAILED (data write failure (Unknown error)
finished. total time: 5.050s
second time :
target didn't report max-download-size
sending 'recovery' (6652 KB)...
FAILED (remote: (Timeout))
finished. total time: 2.010s
Can you help me please ? I add that, when the device is ON in a normal mode (not fastboot) and connected to the PC with USB, the adb driver interface are ok :
"
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
E1OKCY174091 device
"
i have tried to plug on other usb port ... it's the same ...
i have tried to reboot my computer : ... it's the same ...
i have tried to download another version of adp/fasboot (platform-tools_r28.0.2-windows.zip) : it's the same
without this installation, I can't install a custom rom ..
Many thanks in advance !
There are only two working recoveries for the TF701, one CWM without touch interface which I don't quite trust and a pretty good TWRP with touch here https://www.google.com/amp/s/forum....-kang-twrp-tf700t-2-8-x-xarea51-t3121989/amp/
The one you have there is probably the stock recovery...
The Kang TWRP is a little buggy though. You may come to a point where TWRP tells you it cannot mount /system or any other partition for that matter. All you have to do is convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.
Good luck!
Sent from my Pixel 2 using Tapatalk
Hello berndblb
Many thanks for your help
The recovery I try to install is Recovery v6.0.4.6 CWM 11.
Which one is the easier to install for a beginner ?
Because what you said previously seems difficult for me ("convert the file system on /system to ext2, then convert it right back to ext4 and proceed with rom installation.")
Can you explain me how to do ?
Recovery v6.0.4.6 CWM 11 or Kang TWRP : can i install then the Rom "
ROM][N 7.1.2] [ KatKiss - Nougatella #037 ] for asus tf701
?
Many thanks in advance
They are equally easy to install since you just flash both of them in fastboot
But if you are asking which is easier to use, then it is the Kang TWRP. CWM does not have the drivers for the touch interface and you have to navigate everything with the vol buttons. More importantly I do not trust the "format data" function in CWM and that is crucial to install a custom rom. The issue with the corrupt file system in the Kang TWRP is a minor nuisance and you fix it right in TWRP. If you get the "cannot mount....." error, you just go to Wipe > Advanced > Change or repair file system, check the System partition and convert it to ext3 (or ext2 - does not matter). Swipe the button and when it is done (less than a minute) you repeat the step and change it back to ext4. After that everything should be good. If you want to read more about this issue search the Katkiss thread for "cannot mount"
Actually, there is another custom recovery out there which I have not tried and cannot vouch for. But maybe you go for that one, it does not seem to have the same issue and is based on a later version of TWRP: https://forum.xda-developers.com/tr...lopment/recovery-twrp-3-2-1-x-tf701t-t3720912
Read the thread, it seems to work fine. The Kang TWRP is 2.8, that one is based on 3.2.1 - both are fine to flash a Katkiss rom.
You do know that you have to fully format /data before you can flash a custom rom, right? You do that in your custom recovery (in TWRP: Wipe>Format Data, swipe the button). TWRP does a secure erase which wipes and trims every block. That's why this formatting takes around 60 minutes. Do not interrupt it!! CWM does not have this functionality, another reason I prefer TWRP..
hello berndblb and all helpers !
i have installed the Kang TWRP: it's ok
then I copy the custom rom KatKit for TF701 on /sdcard
i do a full wipe : error : "cannot mount..." : so I convert to ext2 and then I convert to ext4 the partition System and data
then i do a full wipe
my problem ... i'm sure you find it : i have erased all my data on /sdcard. No kitkat.zip yet !! :crying::crying::crying:
how to copy the rom on my tablet ?
for your information, when I am in TWRP, i can do "adb devices" on my computer :
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
15C4110C61C00000009FB01C0 recovery
But push commande is failed
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push KatKiss.zip /sdcard/
adb: error: failed to copy 'KatKiss.zip' to '/sdcard/KatKiss.zip': no response:
Connection reset by peer
i put kitkat.zip on a USB Key and I plug it on my docks : it seems not be recognized ...
i 'm really lost
please help !!
Put the Rom on a microSD, mate. You can navigate in TWRP to the card and flash from there
Sent from my Pixel 2 using Tapatalk
Hello !!
I have nevers seen the microsd port ! I discover it 2 days ago !
Just before your answer, a 'adb push' was successfull ! I don't know why, and the next 'adb push' for gapps ans supersu were unsuccessful...it's strange !
But all IS ok now !
I have just a last 2 questions :
1/ next Time, where Can i copy the rom (.Zip) , somewhere it will not be deleted ?
2/my tablet is not rooted now ... Is the way to root depends on the Rom ?
If I follow the steps i did when my tf701 has the rom stock, IS still good ? (https://forum.xda-developers.com/showthread.php?t=2516215)
Thanks for your help !
1) the safest place is a microSD. You can flash the Rom straight from there. But as long as you do not format your data partition - and you only need to to that if you install a different rom - you can keep it on internal storage. In most cases you only need to wipe /data, not format, and that leaves /data /media where your files live, untouched.
2) First the question is: Do you need root? You should only root your rom for a good reason. If you are not sure if you need root - you don't.
Cyber threats are multiplying. You're safer if the tablet is not rooted.
That said: you can root by just flashing the zip in recovery.
BTW, if you did not flash gapps yet, you always should flash it together with the rom, not separate. To install gapps now flash the rom, then gapps, then root (if needed), reboot
Sent from my Pixel 2 using Tapatalk