Related
I'm build TWRP recovery for e4g(e2003).
tested and working all funtions.
Needs:
-pc
-fastboot and drivers
-unlocked bootlader
1. Unlock bootloader (developer.sonymobile.com/unlockbootloader/)
2. install android fastboot drivers (find in net or forum)
3. download recovery.img file and copy fastboot folder.
4. connect your phone in fastboot mode (hold volume up and plug in usb)
5. open command line in fastboot folder(hold shift and right click)
6. type "fastboot flash recovery recovery.img"
7. Wait until you see the phone OK.
8. unplug phone and start in to recovery mode (hold volume down and power)
download link
TWRP_2.8.7.0_for_E4g
Wow thanks n_s218 for your awesome work:good:
Perfect!
Nice work
@n_s218 Can we port lollipop based rom from elephone p6000 or other same CPU and GPU phones to e4g?
Like this thread: http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938
shinyghosts said:
@n_s218 Can we port lollipop based rom from elephone p6000 or other same CPU and GPU phones to e4g?
Like this thread: http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938
Click to expand...
Click to collapse
we can try
Flashtool
I can flash this recovery with Flashtool or not?
no question, i forgot tha flashtool cant flash recovery. sorry for spam.
n_s218 said:
we can try
Click to expand...
Click to collapse
I found this rom for Elephone P6000 We can maybe port this to e4g. http://www.needrom.com/download/elephone-p6000-3/
and all rom for P6000: http://www.needrom.com/category/elephone/p6000/
How Can we get E4g stockboot.img and META-INF folder for port this MIUI7 rom?
Thanks:good:
This app works great for backing up partitions, in options change it to (img) http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
shinyghosts said:
I found this rom for Elephone P6000 We can maybe port this to e4g. http://www.needrom.com/download/elephone-p6000-3/
and all rom for P6000: http://www.needrom.com/category/elephone/p6000/
How Can we get E4g stockboot.img and META-INF folder for port this MIUI7 rom?
Thanks:good:
Click to expand...
Click to collapse
If MIUI, then there's a newer version on MIUI pro.
You can back up boot image as @pryerlee said or via Flashify. For META-INF, we can take it from Elephone (as it's newer Android version so might be different) and just modify some lines (like the partition id's or the getprop lines at the beginning).
@n_s218 thank you, works great! This might be the beginning of custom ROMs for this device :victory:
Tomi_Ohl said:
If MIUI, then there's a newer version on MIUI pro.
You can back up boot image as @pryerlee said or via Flashify. For META-INF, we can take it from Elephone (as it's newer Android version so might be different) and just modify some lines (like the partition id's or the getprop lines at the beginning).
@n_s218 thank you, works great! This might be the beginning of custom ROMs for this device :victory:
Click to expand...
Click to collapse
Thanks:good: I have backup boot image with Partitions Backup & Restore app but this backup is 32mb so it is very big file elephone's miui boot image only 7mb.
and I have a another question Can we get boot.img in ftf file? but E4g's ftf doesn't contain kernel.sin but we have a boot.sin Can we getting boot image from this boot sin(elf)? look this thread:
http://forum.xda-developers.com/showthread.php?t=2699858
shinyghosts said:
Thanks:good: I have backup boot image with Partitions Backup & Restore app but this backup is 32mb so it is very big file elephone's miui boot image only 7mb.
and I have a another question Can we get boot.img in ftf file? but E4g's ftf doesn't contain kernel.sin but we have a boot.sin Can we getting boot image from this boot sin(elf)? look this thread:
http://forum.xda-developers.com/showthread.php?t=2699858
Click to expand...
Click to collapse
1. most of file empty (look at with hex editor) actually ~8 mb
2.boot partition backup file(boot.img) you must rename boot.elf and extract with flashtool elf extractor . you will get two file : boot.elf.0 = kernel , boot.elf.1=ramdisk
Thanks man...
n_s218 said:
1. most of file empty (look at with hex editor) actually ~8 mb
2.boot partition backup file(boot.img) you must rename boot.elf and extract with flashtool elf extractor . you will get two file : boot.elf.0 = kernel , boot.elf.1=ramdisk
Click to expand...
Click to collapse
Thanks:good: so that boot backup is a boot image? Is this right?:laugh:
Any recovery for e4 dual...
Can someone help with e4 dual e2115 for recovery....
shinyghosts said:
Thanks:good: so that boot backup is a boot image? Is this right?:laugh:
Click to expand...
Click to collapse
yes. right.
also you can boot.sin in ftf file ectract with flashtool sin editor
So I've tried to port Euphoria OS from P6000 using this guide.
I've done the ROM part, the updater script was also fine, but I've failed to port kernel: tried both tools mentioned there, Michfood's tool gave error for p6000 boot IMG, carliv's for both.
I've tried to flash the ROM with stock boot IMG, but with it the phone shuts down after Sony logo.
BTW I've backed up stock boot IMG via TWRP, but this shouldn't matter imo.
So can anyone help me with kernel?
EDIT: I'll try if the kernel in MIUI gives error too.
EDIT2: yes, same... Carliv's kitchen says unsupported archive format for ramdisk, Michfood's says something about that end offset is lower than start...
EDIT3: found this alternative for stock boot IMG. Still no solution for p6000 one
EDIT4: successfully decompiled P6000 kernel via Carliv's kitchen 1.0, by choosing regular Android (not mtk) mode. So now both kernels are decompiled but via different tool, so the output is not the same... Still didn't try the tool from EDIT3, it might be the solution.
EDIT5: I have no idea how to use tool from EDIT3 Now I'm downloading ftf, will see if I can do sth... Also I'll try this other tutorial for 64bit.
n_s218 said:
yes. right.
also you can boot.sin in ftf file ectract with flashtool sin editor
Click to expand...
Click to collapse
Thanks for information:good:
I did everything right. but not working. I think problem in boot.img
I working solve problem
n_s218 said:
1. most of file empty (look at with hex editor) actually ~8 mb
2.boot partition backup file(boot.img) you must rename boot.elf and extract with flashtool elf extractor . you will get two file : boot.elf.0 = kernel , boot.elf.1=ramdisk
Click to expand...
Click to collapse
this confused me,u read my mind,man,ty
but i cant follow this,can i use boot.sin file?
zokipfc said:
this confused me,u read my mind,man,ty
but i cant follow this,can i use boot.sin file?
Click to expand...
Click to collapse
yes. extract boot.sin via flashtool sin editor. Do you get boot.elf(boot.img)
Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
vinay durva said:
Hii.. All , I'm using A Lyf wind mobile , I have my my orginginel ( system.img ) file I don't have PC Computer . , I'm using TWRP 3.0 .. Somebody help me how to flash a System.img using TWRP
_ THANKS _
Click to expand...
Click to collapse
TWRP can flash .img files without having to do anything special.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
TWRP can flash .img files without having to do anything special.
Click to expand...
Click to collapse
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
vinay durva said:
Sir .. I was tried , there was only 2 options in TWRP 1st one recovery & 2cond one boot .. Which 1 ican select ,, I need to flash system.img
Click to expand...
Click to collapse
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I dont think you've booted into TWRP yet, I think you're looking at bootloader, select recovery and see if it boots to TWRP.
TWRP has more than just 2 options, are you sure you have TWRP? What version is it? Does it look like this?
http://cloud.tapatalk.com/s/58a730280544c/Screenshot_2017-02-17-12-15-48.png?
If that's what you have, select Install then find your .img and flash it.
Click to expand...
Click to collapse
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
vinay durva said:
Yes sir I'm Booting Into TWRP , Then > install > install images >. I found 2 options 1st one BOOT 2cond RECOVERY , but I won't to flash SYSTEM.img
Click to expand...
Click to collapse
I remember now that TWRP doesn't flash system.img correctly, system.img isn't a standard .img, you need PC and use fastboot.
Sent from my SM-S903VL using Tapatalk
Thanks Sir.. Any Another way to flash system , i don't have A PC
vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I wouldn't try it without PC
Sent from my SM-S903VL using Tapatalk
vinay durva said:
Thanks Sir.. Any Another way to flash system , i don't have A PC
Click to expand...
Click to collapse
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Aex12 said:
I know it is too late, but you can enter in Advaced > Terminal and then run this command:
dd if=/sdcard/system.img of=/dev/block/bootdevice/by-name/system
If your mobile phone doesnt have by-name symlinks you will need to enter the correct partition.
Click to expand...
Click to collapse
hi aex, I have the same problem but I dont have the folder
/bootdevice/by-name............
can you help me?
it will not work.
try to make a folder and "mount -o loop file in it.
and it will be not mounted also if you specify file system type.
(if it work probably you can use the file)
so ,i don't know how fastboot write in partition or probably
in to file system.
however if you do a dd of your current system partition in a file , after will be correctly mounted , or rewrited correctly in the original partition if you need.
then probably you cannot use fastboot system.img directly in twrp shell (using dd)
this is my experience (e2303 sony / pexorom 3.0 twrp 3.1.1)
if you are searching a fast way to know system partition device block
cat /etc/fstab
and look for system
or just mount system in twrp , then in a terminal do a
df -h
and search for system
for e2303 was /dev/block/mmcblk0p30
(example)
twrp have busybox and light kernel.
so , is linux.
for better support try to ask
tonystark88
u need to use simg2img
(sparse file format compression)
system partition device name can be different on other phones.
done.
img can be write by twrp whitout pc/fastboot.
c'ya
giuseppe
just go to file manager and search for system partition, and on first part type your system.img location and 2 part type just system location
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
chr2002 said:
I did this Steps on my Huawei P8. Sim2Img reported a non sparse image, so i moved directly to the DD steps. But after writing the image to the partition, the /system Partition cannot get mountet...
What the hell iam doing wrong ????
I extracted the system.img from an update.app Firmware file.
Its the same Firmware file i flashed before with the dload method.
I want to install TWRP on my Phone with an faulty USB Port. So i have no PC / ADB. I Installed the Firmware via the official Dload Method from Huawai. Then i used this crappy Kingroot to get root and installed TWRP. Now i wanted to flash the stock system partition to get rid of Kingroot for Safetynet.
But why i cant just flash the systempartition ?
Or is there another way to gain root for 15 seconds without traces ?
Click to expand...
Click to collapse
Why not just use the settings in Kingroot to remove root? Or convert from Kingroot to SuperSu then use SuperSu app settings to remove root?
You don't have to flash the stock system to remove root.
Sent from my LGL84VL using Tapatalk
Kingroots uninstall leaves traces in /system/xbin and Safetynet wont work. Why i did not try Supersu ? :-/
But i managed to flash the system.img without problems.
First i tryed an extracted system.img from the Huawei Firmware extractor and Sim2img reported an invalid sparse image. So i thought it must be a raw image.....And this was my mistake. It is a useless image for TWRP.
So i created a flashable zip (TWRP cant flash this, too and the /system partition is not mountable after flashing / installing this zip.
BUT, the system.img INSIDE this zip is a spase image, which sim2img can handle. It gave me a nice raw image which i just dd´d to /system and BINGO, my phone starts up normally
The Short Version :
- Create a FLASHABLE ZIP with the Huawei Firmware Extractor
- use SIM2IMG in TWRP Terminal to get a RAW Image.
- dd´it to the /system partition
System img
You use the restore in twrp to flash your system img, you just until the other boxes
Edit: Sorry wrong thread
Lenovo K5 Pro ROM img
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Help u
Hi u can download a deodexed rom because ais doesn't support some stock roms for ex ch Samsung roms. then decompile it.then decompile it with rar or zarchiver or etc. Then install android image studio (ais) from google
Then open it and tap unpack/mount and select system.img or system.img.ext4 file in decompiled rom . After mounting, copy all files to a directory for ex emulated/0/system/system or another. Attention if you copy it in another directory, rename it as (system) now copy the boot.img from decompiled rom into emulated/0/system .then download this file
https://forum.xda-developers.com/an...oid-o-beta-redesigned-emoji-set-t3608280/amp/
Extract meta-inf file into emulated/0/system using winrar or zarchiver or etc. Now you need to have a system folder,boot.img file and a Meta-inf in diractory emulated/0/system. Now compress system,boot.img and meta-inf into one archive and after completing, turn of your device and boot it into twrp recovery and wipe data and cache without wipping internal storage then select install. Then tap select storage and select internal storage.then go to the file and select it and turn off zip singuature verification and install it after installing tis rom, install root zip file and wipe cache/dalvik art and then reboot your device. It may take between 5-25 minutes to boot. Enjoy your new rom
#issues
Sometimes your device maybe take bootloop so you need to install your stock boot.img file and after installing your root zip file choose wipe cache/dalvik art and then reboot your system.
#Alert
1.Don't install the recovery.img file which exists in the decompiled rom because it takes your device into recovery mod and not boot anymore and after you need to install the stock rom using PC
2.your device maybe take bootloop in this method so do it with your own risk
---------- Post added at 07:58 AM ---------- Previous post was at 07:53 AM ----------
ShmuelCohen said:
After flashing img file (using TWRP 3.3.1) the phone (Lenovo k5 pro) starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Reboot your device and install twrp official app and open it and select flash image from a directory and select your own twrp and reboot your device [root]
Connect your phone to a PC and install stock rom using ADB or another app which was made for your smartphone [no root]
Application of the camera does not work
Yesterday I installed the update of miui 10 V10.2.1.0.OEKMIXM of xiaomi EU after the installation everything correct, but the app of the camera stopped working and I can not make it come back up, install the global version and nothing , the same error, make the wipe cache, data, system all except the misc folder because it throws an error now I'm trying to download the ROM by xioamitool, I read a similar error in this forum but in mi8 and I managed to solve the problem installed a previous ROM but I do not know if miui 10 allows me to return to 9. if someone can help me to download a stable global ROM of miui 9 I would appreciate it.
icemanzor said:
Application of the camera does not work
Yesterday I installed the update of miui 10 V10.2.1.0.OEKMIXM of xiaomi EU after the installation everything correct, but the app of the camera stopped working and I can not make it come back up, install the global version and nothing , the same error, make the wipe cache, data, system all except the misc folder because it throws an error now I'm trying to download the ROM by xioamitool, I read a similar error in this forum but in mi8 and I managed to solve the problem installed a previous ROM but I do not know if miui 10 allows me to return to 9. if someone can help me to download a stable global ROM of miui 9 I would appreciate it.
Click to expand...
Click to collapse
From flash in this file in TWRP > select persist partition > restart the mobile
> https://we.tl/t-uCinDRXFgX
Thank you very much I work, I repair the camera and compass app, total thanks. :fingers-crossed::victory:
douglassillva said:
From flash in this file in TWRP > select persist partition > restart the mobile
> hxxps://we.tl/t-uCinDRXFgX
Click to expand...
Click to collapse
Hi, can you re-send the file? I have the same problem and the link expired already. Thanks!
solmich said:
Hi, can you re-send the file? I have the same problem and the link expired already. Thanks!
Click to expand...
Click to collapse
I also have the same problem.
Tried many roms and standard miui to no avail. Tired the camera2api apks and nada. Camera just not working any more after upgrading to pie...
Any ideas?
cyr1s said:
I also have the same problem.
Tried many roms and standard miui to no avail. Tired the camera2api apks and nada. Camera just not working any more after upgrading to pie...
Any ideas?
Click to expand...
Click to collapse
I've found a solution. So, I download standard miui firmware, 10.3.x in my case (Pie version), and then extract the content. In one of folders, you'll find vendor.img, copy this file to your /sdcard phone. Go to the TWRP terminal and execute this command: dd if=/sdcard/vendor.img of=/dev/block/mmcblk0pYY
YY is the vendor partition number, you can find it using mount command and carefully see which one is. Reboot and all is well. If your TWRP has an option to flash the vendor partition, it would be easier. Mine has no such option.
Read somewhere involving modifying xml file and using miflash, also emergency download mode (since vendor partition is readonly in fastboot), but I've failed to flash and the dd method above is succeeded. YMMV and good luck.
**update: it's persist not vendor, so change accordingly (vendor.img -> persist.img, also the mmcblk)
thanks
solmich said:
I've found a solution. So, I download standard miui firmware, 10.3.x in my case (Pie version), and then extract the content. In one of folders, you'll find vendor.img, copy this file to your /sdcard phone. Go to the TWRP terminal and execute this command: dd if=/sdcard/vendor.img of=/dev/block/mmcblk0pYY
YY is the vendor partition number, you can find it using mount command and carefully see which one is. Reboot and all is well. If your TWRP has an option to flash the vendor partition, it would be easier. Mine has no such option.
Read somewhere involving modifying xml file and using miflash, also emergency download mode (since vendor partition is readonly in fastboot), but I've failed to flash and the dd method above is succeeded. YMMV and good luck.
**update: it's persist not vendor, so change accordingly (vendor.img -> persist.img, also the mmcblk)
Click to expand...
Click to collapse
i had the same problem, and your solution works, i probed it on a redmi note 6 pro, but i flashed persist.img from INSTALL->persist i chose install image and then persist.img, i had probed install other firmwares but this was the only thing that works...Thanks you saved my phone :good:
solmich said:
I've found a solution. So, I download standard miui firmware, 10.3.x in my case (Pie version), and then extract the content. In one of folders, you'll find vendor.img, copy this file to your /sdcard phone. Go to the TWRP terminal and execute this command: dd if=/sdcard/vendor.img of=/dev/block/mmcblk0pYY
YY is the vendor partition number, you can find it using mount command and carefully see which one is. Reboot and all is well. If your TWRP has an option to flash the vendor partition, it would be easier. Mine has no such option.
Read somewhere involving modifying xml file and using miflash, also emergency download mode (since vendor partition is readonly in fastboot), but I've failed to flash and the dd method above is succeeded. YMMV and good luck.
**update: it's persist not vendor, so change accordingly (vendor.img -> persist.img, also the mmcblk)
Click to expand...
Click to collapse
Thx u save my camera too, i have to ask, ur compass works fine too?
solmich said:
Hi, can you re-send the file? I have the same problem and the link expired already. Thanks!
Click to expand...
Click to collapse
Can send it to me as well my camera just Dont want to connect its writing i want to try you way
I would like to install TWRP and after that Lineage OS on my Samsung S8+ (Exynos). So i tried flashing TWRP with Odin (Dream2lte version 3.3.1.0). But i ran into a FRP lock so i googled and try to solve this, but so far i am unable to.
I have the password to my Google account, so i removed the Google account from the phone and removed the phone from my Google account. After factory reset i am still getting an error FRP lock when flashing.
Shouldn't the FRP lock be gone after removing google account and doing a factory reset? I have tried a couple of YT Howto's but they don't seem to work.
How do i remove the FRP lock so that i am able to install TWRP and Lineage OS?
Like i said i know the password to my Google account and i 100% own the phone
(Bypass probably isn't the correct word, i am simply trying to turn it off )
Got exactly the same problem, hence like you, ended up here for help.
Well i fixed my problem (Disable USB debug and OEM unlock, couple of reboots and enabled them and it worked). But after that i broke my phone
I am stuck at the screen saying: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I know this is meant to scare me (is kinda working...), but i also know that Odin is still working. So as far as i know i have to flash the original firmware now to fix this. But i keep getting the error: Invalid magic string. When i try to also flash a BL file i get the error: ""Secure CHECK FAIL: (BOOTLOADER)" The option Re-Partition in Odin is switched OFF, as far as i know this is okee... right?
I have tried 3 different versions (Android 9/8/7):
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU1AQC9/128974/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU4DSBA/259612/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXS4CSA4/256485/
This zip files contain a BL/AP/CP/CSC file, i have tried them all at the same time in Odin as well as the AP and BL files seperate. (from one zip file, NOT different version files together of course)
I tried using Smart Switch 4.1 to do the emergency procedure using model nummer SM-G955F with my serial number but before it does anything it tells me this is not possible with an SM-G955F.
They all give me the same result.
Does anybody know how to fix this?
TheGeneral said:
Well i fixed my problem (Disable USB debug and OEM unlock, couple of reboots and enabled them and it worked). But after that i broke my phone
I am stuck at the screen saying: An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
I know this is meant to scare me (is kinda working...), but i also know that Odin is still working. So as far as i know i have to flash the original firmware now to fix this. But i keep getting the error: Invalid magic string. When i try to also flash a BL file i get the error: ""Secure CHECK FAIL: (BOOTLOADER)" The option Re-Partition in Odin is switched OFF, as far as i know this is okee... right?
I have tried 3 different versions (Android 9/8/7):
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU1AQC9/128974/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXU4DSBA/259612/
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950F/TNL/download/G950FXXS4CSA4/256485/
This zip files contain a BL/AP/CP/CSC file, i have tried them all at the same time in Odin as well as the AP and BL files seperate. (from one zip file, NOT different version files together of course)
I tried using Smart Switch 4.1 to do the emergency procedure using model nummer SM-G955F with my serial number but before it does anything it tells me this is not possible with an SM-G955F.
They all give me the same result.
Does anybody know how to fix this?
Click to expand...
Click to collapse
Secure check fail on bootloader is your flashing a older firmware than on the device. Look at the builds 5th from last digit. You need to flash that equal or greater than.
The error screen you see for emergency recovery is ok. It's like a modified version of download mode. Kind of. You can still flash Odin files from said screen. Ii see you've flashed a bit 1. And two bit 4 firmwares. So you must be on a 5 or greater. I don't know the exy bit number but like snapdragon is at or near 7 or 8. I can explain better if you need. But not an exynos expert
TheMadScientist said:
Secure check fail on bootloader is your flashing a older firmware than on the device. Look at the builds 5th from last digit. You need to flash that equal or greater than.
The error screen you see for emergency recovery is ok. It's like a modified version of download mode. Kind of. You can still flash Odin files from said screen. Ii see you've flashed a bit 1. And two bit 4 firmwares. So you must be on a 5 or greater. I don't know the exy bit number but like snapdragon is at or near 7 or 8. I can explain better if you need. But not an exynos expert
Click to expand...
Click to collapse
Thanks for your reply! I am in the normal "Downloading...." screen is there anywhere i can check which number i am at?
But i have just tried this one: G950FXXS7DTA6_G950FOXM7DTA6_PHN and it is not working. But this is the newest one available on sammobile. Still the same bootloader error.
I have tried TWRP 3.3.1.0 and that worked, now i am in the TWRP menu but i don't have the LineageOS 17 + GoApps copied to the root. So i cannot install LineageOS now. What do i do now? My computer sees a SM-G955F but it is not showing any storage, if i can fix this i could copy the LineageOS files to the root...right?
TheGeneral said:
Thanks for your reply! I am in the normal "Downloading...." screen is there anywhere i can check which number i am at?
But i have just tried this one: G950FXXS7DTA6_G950FOXM7DTA6_PHN and it is not working. But this is the newest one available on sammobile. Still the same bootloader error.
I have tried TWRP 3.3.1.0 and that worked, now i am in the TWRP menu but i don't have the LineageOS 17 + GoApps copied to the root. So i cannot install LineageOS now. What do i do now? My computer sees a SM-G955F but it is not showing any storage, if i can fix this i could copy the LineageOS files to the root...right?
Click to expand...
Click to collapse
1. If you are on an S8+ flashing firmware for the S8 will cause you issues. Download firmware for the S8+ only. ie: 955f not 950f.
2. If you can't get into the system but can get into download mode there should be a line saying
AP SWREV: B:? K:? S:?
The B:? Is your bootloader version number. You will need to flash the same or higher.
3. How did you install TWRP?
If you don't have an SD card to store files on then after the Format Data stage you can then copy files from pc to phones internal storage.
spawnlives said:
1. If you are on an S8+ flashing firmware for the S8 will cause you issues. Download firmware for the S8+ only. ie: 955f not 950f.
2. If you can't get into the system but can get into download mode there should be a line saying
AP SWREV: B:? K:? S:?
The B:? Is your bootloader version number. You will need to flash the same or higher.
3. How did you install TWTP?
If you don't have an SD card to store files on then after the Format Data stage you can then copy files from pc to phones internal storage.
Click to expand...
Click to collapse
I am a bit embarrassed, it looks like i have been trying to flash the wrong ROMs last night 950 instead of 955, i am downloading the correct files now and wil try again. Sorry for this dumb mistake!
Just to be sure, i am trying to do this:
https://www.getdroidtips.com/lineage-os-17-samsung-galaxy-s8/
(I do know that this site says S8, but i picked the right files this time and thought the process would be the same)
But i first Flash TWRP with Odin, otherwise i cannot reach the TWRP recovery menu right?
But when i look bullet 5 (not number 5) it looks like i need to flash TWRP from within the TWRP menu. But that is not correct right?
I have placed these zip files on the phone:
lineage-17.1-20200211-UNOFFICIAL-dreamlte.zip
open_gapps-arm64-10.0-pico-20200303.zip
As a zip and unpacked, but when i am in the TWRP menu and i go to install, i cannot find the zip files. I placed them in the highest folder level possible. Why can't i find them now?
TheGeneral said:
I am a bit embarrassed, it looks like i have been trying to flash the wrong ROMs last night 950 instead of 955, i am downloading the correct files now and wil try again. Sorry for this dumb mistake!
Just to be sure, i am trying to do this:
https://www.getdroidtips.com/lineage-os-17-samsung-galaxy-s8/
(I do know that this site says S8, but i picked the right files this time and thought the process would be the same)
But i first Flash TWRP with Odin, otherwise i cannot reach the TWRP recovery menu right?
But when i look bullet 5 (not number 5) it looks like i need to flash TWRP from within the TWRP menu. But that is not correct right?
I have placed these zip files on the phone:
lineage-17.1-20200211-UNOFFICIAL-dreamlte.zip
open_gapps-arm64-10.0-pico-20200303.zip
As a zip and unpacked, but when i am in the TWRP menu and i go to install, i cannot find the zip files. I placed them in the highest folder level possible. Why can't i find them now?
Click to expand...
Click to collapse
I don't use custom roms yet.
Try searching for you device S8+ for installation instructions. Had a quick look the firmware is for S8 only not S8+. Need dream2lit for S8+
Try in separate stages instead of all at once.
I would sort out your stock firmware first get it up and running.
Then install TWRP. Install for S8+ from
http://twrp.me/Devices/Samsung/
They are many guides for this
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
If you need rmm bypass zip
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Get that up and running properly.
Then you can install custom roms,root etc.
In regards to transferring files to phone they need to be a zip file ( .zip ) or an image ( .img ) files to flash in TWRP.
Maybe select internal storage then from menu select sdcard folder check if file is there.
spawnlives said:
I don't use custom roms yet.
Try searching for you device S8+ for installation instructions. Had a quick look the firmware is for S8 only not S8+. Need dream2lit for S8+
Try in separate stages instead of all at once.
I would sort out your stock firmware first get it up and running.
Then install TWRP. Install for S8+ from
http://twrp.me/Devices/Samsung/
They are many guides for this
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
If you need rmm bypass zip
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Get that up and running properly.
Then you can install custom roms,root etc.
In regards to transferring files to phone they need to be a zip file ( .zip ) or an image ( .img ) files to flash in TWRP.
Maybe select internal storage then from menu select sdcard folder check if file is there.
Click to expand...
Click to collapse
I am using dream2lit.
I have the correct factory stock ROM (now), so i can always go back now. But i agree, my preparation wasn't good enough.
I will look at the links, but for now like i said my problem is that i cannot see my files in TWRP. But maybe that will be addressed in one of your links
With regards to your first link, i used the "Odin Method" so as far as i can tell i did this the right way(https://twrp.me/samsung/samsunggalaxys8plus.html):
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
TheGeneral said:
I am using dream2lit.
I have the correct factory stock ROM (now), so i can always go back now. But i agree, my preparation wasn't good enough.
I will look at the links, but for now like i said my problem is that i cannot see my files in TWRP. But maybe that will be addressed in one of your links
With regards to your first link, i used the "Odin Method" so as far as i can tell i did this the right way(https://twrp.me/samsung/samsunggalaxys8plus.html):
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Note: Samsung don't have fastboot commands. Have to use button configurations to enter recovery or download modes.
What stage are you at?
It will give me a better idea to be able to help more.
spawnlives said:
Note: Samsung don't have fastboot commands. Have to use button configurations to enter recovery or download modes.
What stage are you at?
It will give me a better idea to be able to help more.
Click to expand...
Click to collapse
Well i installed Lineage OS 17.1 and Open Apps (lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303) with an OTG plug and an USB stick. After installing i removed the USB Stick. But now i am having a new problem...
When the phone boots it asks: "To start Android, enter your password"
Which password is this? When i enter a password i often use it works but then:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt. (Which is no problem)
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.
(Button) Erase ALL DATA"
Of course i erase the data. Look at the attachment to see what happens then.
I will not give up, will get Lineage OS on this phone, and after that on my Tablet S2 and maybe even on my primairy phone (S10+)
What should i do now? Many thanks for all the help so far, and for help finishing this proces
TheGeneral said:
Well i installed Lineage OS 17.1 and Open Apps (lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303) with an OTG plug and an USB stick. After installing i removed the USB Stick. But now i am having a new problem...
When the phone boots it asks: "To start Android, enter your password"
Which password is this? When i enter a password i often use it works but then:
"Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt. (Which is no problem)
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.
(Button) Erase ALL DATA"
Of course i erase the data. Look at the attachment to see what happens then.
I will not give up, will get Lineage OS on this phone, and after that on my Tablet S2 and maybe even on my primairy phone (S10+)
What should i do now? Many thanks for all the help so far, and for help finishing this proces
Click to expand...
Click to collapse
Mounting data errors in twrp generally ( but not always ) means your device is encrypted/re-encrypted when booting into system. Twrp has issues with encrypted devices.
What version twrp are you using?
Have you flashed the no-verity-opt-encypt zip in twrp. This zip file will prevent device from re-encrypting when booting phone back into the system ( after the Format Data stage / reboot back into twrp)
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
What is your process of installing twrp?
If you have any passwords etc. installed delete them until after setting up you phone.
spawnlives said:
Mounting data errors in twrp generally ( but not always ) means your device is encrypted/re-encrypted when booting into system. Twrp has issues with encrypted devices.
What version twrp are you using?
Have you flashed the no-verity-opt-encypt zip in twrp. This zip file will prevent device from re-encrypting when booting phone back into the system ( after the Format Data stage / reboot back into twrp)
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
What is your process of installing twrp?
If you have any passwords etc. installed delete them until after setting up you phone.
Click to expand...
Click to collapse
I am using version twrp-3.3.1-1-dream2lte and no i have not flashed that no-verity-opt-encypt zip. I assume i should flash this one the same way flash the Lineage ROM right?
No passwords used on the phone.
My process:
i put the phone in download mode (POWER+BIXBY+VOL DOWN)
I use ODIN to flash twrp-3.3.1-1-dream2lte, and when the phone reboot i press POWER+BIXBY+VOL UP to enter TWRP menu,
Then i go to WIPE and Advanced Wipe and i select the data, system and davlik cache. Then swipe to wipe it.
Then i go to INSTALL and flash lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303
TheGeneral said:
I am using version twrp-3.3.1-1-dream2lte and no i have not flashed that no-verity-opt-encypt zip. I assume i should flash this one the same way flash the Lineage ROM right?
No passwords used on the phone.
My process:
i put the phone in download mode (POWER+BIXBY+VOL DOWN)
I use ODIN to flash twrp-3.3.1-1-dream2lte, and when the phone reboot i press POWER+BIXBY+VOL UP to enter TWRP menu,
Then i go to WIPE and Advanced Wipe and i select the data, system and davlik cache. Then swipe to wipe it.
Then i go to INSTALL and flash lineage-17.1-20200211-UNOFFICIAL-dream2lte and open_gapps-arm64-10.0-pico-20200303
Click to expand...
Click to collapse
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
spawnlives said:
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
Click to expand...
Click to collapse
how do i make a complete TWRP backup? and what is rmm bypass and how do i know if it is neccessary to install this zip file?
TheGeneral said:
how do i make a complete TWRP backup? and what is rmm bypass and how do i know if it is neccessary to install this zip file?
Click to expand...
Click to collapse
In twrp main menu
Select backup menu - select ( all ) partitions - select storage location ( bottom left of screen ) - then swipe to backup.
Note:
1. If backing up to internal storage copy/move backup to an external storage ie: PC, sd card.etc.
2. Since you want a custom rom backup of the EFS partition is important.
Rmm state can be found in download mode. It will have a line ( near the top ) saying RMM state. It will either say prenormal or normal /disappeared.
It won't hurt to flash it just in case.
See OP in the thread I sent before:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
spawnlives said:
To install TWRP
1. Flash twrp with odin - reboot straight into twrp
2. In wipe menu select Format Data ( bottom right )
Type yes to format
3. Reboot back into twrp ( use twrp menu )
4. Flash no-verity-opt zip and if needed rmm bypass zip ( using install button in twrp ).
5. Reboot back into twrp then reboot to system using twrp menu.
6. From system reboot back into twrp.
To check if device is un-encrypted use backup menu - check data storage size ( If reading 0mb then device is still encrypted ).
Note: If all ok I would do a complete twrp backup at this stage ( keep backup on a separate storage device ).
Then you can install custom Rom's as per the installation guide of that Rom.
Click to expand...
Click to collapse
I am really trying to do what you are saying...but when i try to "Format Data" (Step 2) it shows an error "Failed to mount '/preload' (Invalid argument). When i try to install no-verity-opt zip (step 4) at the end it shows the same error "Failed to mount '/preload' (Invalid argument). Which is probably because format data failed?
I am installing the zip from an USB stick with an USB-C to USB-A Converter. I don't think that could be the problem?
As Expected the "Data (excl. storage) is still showing 0MB.
TheGeneral said:
I am really trying to do what you are saying...but when i try to "Format Data" (Step 2) it shows an error "Failed to mount '/preload' (Invalid argument). When i try to install no-verity-opt zip (step 4) at the end it shows the same error "Failed to mount '/preload' (Invalid argument). Which is probably because format data failed?
I am installing the zip from an USB stick with an USB-C to USB-A Converter. I don't think that could be the problem?
As Expected the "Data (excl. storage) is still showing 0MB.
Click to expand...
Click to collapse
Failed to mount preload seems to affect some users.
You could try after the format data and reboot back into twrp ( using twrp 3.3.1.1 ):
Select wipe menu
Select advanced wipe
Select Preload
Swipe to wipe
Reboot back into twrp
Then try flashing no-verity/rmm zips files - reboot back into twrp.
Normally, for me , after this stage If i still get 0mb I will reboot into the Android system and then back into twrp. Then check in backup menu storage. If ok then try to flash custom rom.
spawnlives said:
Failed to mount preload seems to affect some users.
You could try after the format data and reboot back into twrp ( using twrp 3.3.1.1 ):
Select wipe menu
Select advanced wipe
Select Preload
Swipe to wipe
Reboot back into twrp
Then try flashing no-verity/rmm zips files - reboot back into twrp.
Normally, for me , after this stage If i still get 0mb I will reboot into the Android system and then back into twrp. Then check in backup menu storage. If ok then try to flash custom rom.
Click to expand...
Click to collapse
Yes Yes!! After doing the Preload i am able to flash no-verity/rmm zips file.
But Data is still showing 0MB.....
I thought why not give the lineage OS rom flashing another try. That worked, but now the phone seems to hang on a Lineage OS logo with a small circle moving around not straight line.
So i wiped everything again and flashed no-verity/rmm zip file, and will wait what for some advice and what do to next.
TheGeneral said:
Yes Yes!! After doing the Preload i am able to flash no-verity/rmm zips file.
But Data is still showing 0MB.....
I thought why not give the lineage OS rom flashing another try. That worked, but now the phone seems to hang on a Lineage OS logo with a small circle moving around not straight line.
So i wiped everything again and flashed no-verity/rmm zip file, and will wait what for some advice and what do to next.
Click to expand...
Click to collapse
Have you tried to reboot into system through twrp ie: reboot menu - system. Let it start normally, reboot into twrp, then check storage size. ( This is after the flashing of the no-verity/rmm zip and rebooting back into twrp ).
As I said I' m not familiar with custom ROMs. I do know that some custom ROMs do take some time to boot up on installation.
But out of curiosity I have a spare S8 and will give it a go.
Hi All
Noob too the tab scene (paradoxically developing a rom module to "reasonable success" haha)
Found found the time to put a guide together following updating to BTF2 firmware and installing TWRP in one flash.
This has probably been posted before but hopefully its useful nonetheless
Prerequisites
- May security patched TWRP image - its highly advisable to make sure your TWRP and any kernels used match the security patch date of your firmware use This awesome online tool thanks @evdenis - Mentalmuso's TWRP is running perfectly on mydevice patched to may with BTF2 firmware
-VBmeta.img from Mentalmuso's tar
- BL, CP, HOMECSC and Magisk patched AP with the May patched TWRP renamed as "recovery.img" and replacing the stock recovery and the VBmeta.img from Mentalmuso's tar replacing the stock one
- Multidisabler 2.3 linked below thanks @ianmacd
Process
1 - Backup anything you need to keep onto external SD as you will need to format internal storage to get TWRP working.
2 - Reboot to download and open odin - uncheck auto reboot and then load BL, Magisk Patched AP, CP and HOMECSC (from BTF2 firmware)
3 - Flash the files and when done hold vol down and power to exit download and immediately hold power and vol up until in initial TWRP screen (after holding it whilst it reboots you'll end up at the screen where it asks you if you want to allow system modifications) Check the box and swipe right
4 - You'll notice by going into install that your internal storage folders are now nonsense - go to wipe in TWRP then Format data and type yes then enter - your internal storage will be wiped (hence having to backup) but your internal storage will now be usable.
5 - Immediately flash the multidisabler 2.3 zip and then reboot recovery - You are now fully updated and have TWRP installed and working
6 - i have a personal stock debloated rooted base that I use for installing my rom module on - linked here for T865 ONLY - wipe data, system, vendor, cache and dalvik and then flash the base zip (stock rooted based on BTF2 DBT firmware) - FOLLOWED BY MULTIDISABLER ONCE MORE - reboot and set up
Hopeloos ....
Thanks.
It didn"t directly help. But now I know I didn"t do whats needed, for rooting my 865 lol
Any idea where I can find how to root specificaly my tab. Already rooted smartphones but this tablet seems a bit different. Or can you help me?
Downloading and looking at your multidisabler zip, seems you are dutch. So am I
Thanks for reading and hopefully waiting your respos
El
PS: om moedeloos van te wordena
Hi, thank you for the short guide.
Could you post expanded steps please?
I don't want to f' things up.
exocetdj said:
Prerequisites
- May security patched TWRP image - its highly advisable to make sure your TWRP and any kernels used match the security patch date of your firmware use This awesome online tool thanks @evdenis - Mentalmuso's TWRP is running perfectly on mydevice patched to may with BTF2 firmware
Click to expand...
Click to collapse
All clear and done, took 3.4.0-gts6l and patched it to May 2020.
exocetdj said:
-VBmeta.img from Mentalmuso's tar
Click to expand...
Click to collapse
Found that Magisk patched AP also has an empty VBmeta.img inside.
exocetdj said:
- BL, CP, HOMECSC and Magisk patched AP with the May patched TWRP renamed as "recovery.img" and replacing the stock recovery and the VBmeta.img from Mentalmuso's tar replacing the stock one
Click to expand...
Click to collapse
As Magisk on Samsung devices installs into recovery.img instead of boot.img (see https://topjohnwu.github.io/Magisk/install.html#additional-info), won't I kill Magisk if I overwrite the recovery.img inside the Magisk patched tar? Should I first add the recovery to the AP before Magisk patching it?
exocetdj said:
- Multidisabler 2.3 linked below thanks @ianmacd
Process
1 - Backup anything you need to keep onto external SD as you will need to format internal storage to get TWRP working.
2 - Reboot to download and open odin - uncheck auto reboot and then load BL, Magisk Patched AP, CP and HOMECSC (from BTF2 firmware)
3 - Flash the files and when done hold vol down and power to exit download and immediately hold power and vol up until in initial TWRP screen (after holding it whilst it reboots you'll end up at the screen where it asks you if you want to allow system modifications) Check the box and swipe right
4 - You'll notice by going into install that your internal storage folders are now nonsense - go to wipe in TWRP then Format data and type yes then enter - your internal storage will be wiped (hence having to backup) but your internal storage will now be usable.
5 - Immediately flash the multidisabler 2.3 zip and then reboot recovery - You are now fully updated and have TWRP installed and working
Click to expand...
Click to collapse
Should manage to do that
exocetdj said:
6 - i have a personal stock debloated rooted base that I use for installing my rom module on - linked here for T865 ONLY - wipe data, system, vendor, cache and dalvik and then flash the base zip (stock rooted based on BTF2 DBT firmware) - FOLLOWED BY MULTIDISABLER ONCE MORE - reboot and set up
Click to expand...
Click to collapse
If it won't work, I'll give that a try.
Again, thank you very much for this thread.
Regards,
sub
Cool any issues pop into the 420 telegram chat. Im working for next 5 hours but we can help there if you're stuck
Yay, stuck at the Samsung logo (after bootloader warning and "unofficial software" nag).
Followed all steps to the letter.
Created 3 APs:
- Stock magisk patched
- Stock magisk patched with replaced recovery.img
- Unpacked AP, replaced recovery.img with TWRP, repacked, then magisk patched
I managed to boot one variant (can't remember which) into safe mode somehow, but only once.
Trying to restore TWRP backup now.
I hate Samsung
Edit: At least the TWRP restore worked fine and the tablet booted
Edit 2: Played around again. This time flashed full stock BTF2 firmware. Now everything that contains a modded vbmeta fails. Let's see if I can get anything to work again.
Edit 3: Any non original vbmeta now fails to start at all.
I hate Samsung even more.
(partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM recovery
VBMETA T865XXU3BTF2, 31809105R)
subworx said:
Yay, stuck at the Samsung logo (after bootloader warning and "unofficial software" nag).
Followed all steps to the letter.
Created 3 APs:
- Stock magisk patched
- Stock magisk patched with replaced recovery.img
- Unpacked AP, replaced recovery.img with TWRP, repacked, then magisk patched
I managed to boot one variant (can't remember which) into safe mode somehow, but only once.
Trying to restore TWRP backup now.
I hate Samsung
Edit: At least the TWRP restore worked fine and the tablet booted
Edit 2: Played around again. This time flashed full stock BTF2 firmware. Now everything that contains a modded vbmeta fails. Let's see if I can get anything to work again.
Edit 3: Any non original vbmeta now fails to start at all.
I hate Samsung even more.
(partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM recovery
VBMETA T865XXU3BTF2, 31809105R)
Click to expand...
Click to collapse
If you get stuck at SAMSUNG screen again, try and force a reboot
Why don't I see a CP file in my firmware file?
All that's in there is :
AP
BL
CSC
HOME CSC
************************
T860 wifi
Do I just leave the CP slot blank?
exocetdj said:
If you get stuck at SAMSUNG screen again, try and force a reboot
Click to expand...
Click to collapse
Ok will do. If I can get myself to try that whole thing again, that is: TWRP backup to external SD alone takes more than 1,5 hours
Thank you.
Edit: Another thing I found: after flashing everything, my internal storage is *not* scrambled. Still formatted it last time around, though, but not sure if that would absolutely be necessary. Think the original rooting instructions on here (cannot find them any more) included installing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" which should remove the need for formatting.
jhill110 said:
Why don't I see a CP file in my firmware file?
All that's in there is :
AP
BL
CSC
HOME CSC
************************
T860 wifi
Do I just leave the CP slot blank?
Click to expand...
Click to collapse
Looks like a broken download. Where did you get that from?
Both T865XXU2BTC7_T865OXM2BTC7_DBT and T865XXU3BTF2_T865OXM3BTF2_DBT contain AP, BL, CP, CSC, HOME_CSC.
Possibly try sammobile, they should have complete ROM archives, although they're slow as hell on non-premium.
Regards,
sub
subworx said:
Looks like a broken download. Where did you get that from?
Both T865XXU2BTC7_T865OXM2BTC7_DBT and T865XXU3BTF2_T865OXM3BTF2_DBT contain AP, BL, CP, CSC, HOME_CSC.
Possibly try sammobile, they should have complete ROM archives, although they're slow as hell on non-premium.
Regards,
sub
Click to expand...
Click to collapse
Well that's interesting... I paid the $$ for faster downloads from Samobile. An hour is far better than 12 or 13. It's where I got the file(s) in the first place.
I downloaded the file again just to be sure and it's the same thing. It works so what the heck.
I'm curious as to what that particular (CP) slot/file is...
Oh btw, I'm T860 wifi.
jhill110 said:
Well
I'm curious as to what that particular (CP) slot/file is...
Oh btw, I'm T860 wifi.
Click to expand...
Click to collapse
CP is related to the Modem. Since your T860 doesn't have a 3G modem chip, you don't need the CP file.
I *think* that's correct anyway.