Are there any recent updates on stability of lineage os for note 8 pro? I want to install it in my daily driver, but I'm not seeing any new info.
TIA
Try the Lineage17 GSI, seemed rock solid to me with everything I tried working. It's the same as Quack which has been flawless for me the past week.
wang1chung said:
Try the Lineage17 GSI, seemed rock solid to me with everything I tried working. It's the same as Quack which has been flawless for me the past week.
Click to expand...
Click to collapse
Can you point me to a link so I know I'm getting the right one?
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Grab the ab arm64 version, wipe data dalvik cache and system, then flash the system partition with the GSI above, close avb and reboot.
Nice thing is there's no danger of hard bricking if you're only flashing the system partition.
Make a TWRP backup of your current ROM and go back and forth to compare, takes no more than 10 per ROM.
wang1chung said:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Grab the ab arm64 version, wipe data dalvik cache and system, then flash the system partition with the GSI above, close avb and reboot.
Nice thing is there's no danger of hard bricking if you're only flashing the system partition.
Make a TWRP backup of your current ROM and go back and forth to compare, takes no more than 10 per ROM.
Click to expand...
Click to collapse
lineage-17.1-20200713-UNOFFICIAL-treble_arm64_bvN.img.xz that one?
wang1chung said:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
Grab the ab arm64 version, wipe data dalvik cache and system, then flash the system partition with the GSI above, close avb and reboot.
Nice thing is there's no danger of hard bricking if you're only flashing the system partition.
Make a TWRP backup of your current ROM and go back and forth to compare, takes no more than 10 per ROM.
Click to expand...
Click to collapse
im struggling pretty bad here, i was able to unlock the bootloader, every twrp flash i try looks like it succeeds then when i try to boot into twrp, it doesnt work.
justawfulgamer said:
im struggling pretty bad here, i was able to unlock the bootloader, every twrp flash i try looks like it succeeds then when i try to boot into twrp, it doesnt work.
Click to expand...
Click to collapse
By "it doesn't work", you mean you have a black screen?
Flash LR TWRP instead of all the other recoveries meant for begonian not begonia.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
wang1chung said:
By "it doesn't work", you mean you have a black screen?
Flash LR TWRP instead of all the other recoveries meant for begonian not begonia.
https://forum.xda-developers.com/re...overy-twrp-recovery-redmi-note-8-pro-t4033695
Click to expand...
Click to collapse
well, for starters, i go to flash twrp. it seems to go fine, then i send the reboot command, and it fails.
Edit: also, the links in the thread you just posted are dead
justawfulgamer said:
well, for starters, i go to flash twrp. it seems to go fine, then i send the reboot command, and it fails.
Edit: also, the links in the thread you just posted are dead
Click to expand...
Click to collapse
Think you're going to have to list all the steps you've done, but if fastboot reboot doesn't work, I don't think you flashed TWRP successfully.
Type "fastboot devices" with your phone connected in fastboot mode and respond back with the output.
Related
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
redheadplantguy said:
Hi everyone. Just guy my note tablet. Rooted with towlie.
Build number kot49h.p607tuvuane2
Finding a bit of confusion on which TWRP I should install. I did one with Odin, and it didn't take.
Can someone point me to right file and/or directions if i need to downgrade first?
I want to start playing and customizing, but cannot back up or reflash.
Click to expand...
Click to collapse
most stable version would be 2.6.3.3
buhohitr said:
most stable version would be 2.6.3.3
Click to expand...
Click to collapse
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
redheadplantguy said:
Have heard a few things about needing an Odin firmware downgrade. Is that necessary with my firmware? And should I use Odin, or ADB?
Really appreciate the info. I want to tinker, but without working recovery, I'm a bit Leary.
Click to expand...
Click to collapse
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
buhohitr said:
the version I stated is most stable, other twrp version may cause cache corruption and other issues.
Click to expand...
Click to collapse
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
redheadplantguy said:
the closest release i could find was twrp 2331.
i flashed with odin. but when i tried to reboot to recovery, i got a scrambled, pixelated screen which after a few seconds rebooted system.
Click to expand...
Click to collapse
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
buhohitr said:
Get it here http://www.techerrata.com/browse/twrp2/lt03wifiue
You need to wipe cache, davik cache and data, then flash the rom.
Click to expand...
Click to collapse
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
redheadplantguy said:
I found that version on the link, but i thought that was for the Exynos chipset.
I have the Qualcomm LTE version. Will it still work?
Click to expand...
Click to collapse
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Hi,
This post saved me, I installed TWRP 2.8 and my system froze, I couldn't get past the Samsung 10.1 screen.
But found this post and flashed 2.6.3.3 via Odin and it all went smoothly.
PS Goo.img.com dosen't have the files anymore
buhohitr said:
For Qualcomm LTE the version is 2.6.3.1
https://goo.im/devs/OpenRecovery/lt03ltexx/openrecovery-twrp-2.6.3.1-lt03ltexx.zip/
Click to expand...
Click to collapse
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
redheadplantguy said:
I currently have no recovery. I tried flashing 2.8 originally.
How would i clear cache, data, and all before trying to flash 2631?
Click to expand...
Click to collapse
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Is 2.6.3.3 more reliable / stable in terms of making / restoring nandroids? I just got my new Note last week (p607t) and flashed xKat with TWRP at one point, restoring apps from (some with data to avoid re-entering account info or redoing complex settings...) I have had one problem however, when I was almost done restoring, I noticed that I was getting fc's, particularly with games that required an internet connection. I wiped dalvik and cache in TWRP, then hit fix permissions, which I think screwed everything up (maybe due to the bootloader / firmware base mismatch). Anyway, my most recent nandroid was with the fresh xKat install, but fixing permissions caused this weird "hot"-bootloop where it skipped the boot animation but start loading immediately after rebooting, but then freezing before all boot tasks had completed (ex. some optimizations on boot with Android Tuner Pro, FolderMount mounting folders, loading xposed modules...)
Not wanting to re-restore, I first just tried dirty-flashing the ROM again (only wiped dalvik and cache, but did something I hadn't tried before: in the wipe menu I hit "repair partition" for system and data, pre-flash). Luckily it worked and set everything straight... but just want to make sure, 2.6.3.3 is still recommended as the most stable version (in my experience, fixing permissions in recovery can be very hit or miss on any version)?
2 questions before I roll back my recovery, I think these "killer features" (totally serious, #2 has been huge since I got a couple of the newish flash drives with micro usb on one side and regular usb on the other) of TWRP were implemented in 2.6.3.3, but just want to make sure: can you 1) compress nandroids and 2) mount a USB OTG drive and flash from or backup to it? Thanks all, really loving my new Note (massive upgrade from my Note 8!)
buhohitr said:
No, you flash TWRP 2631, then boot into the twrp then select advance then put a check for cache, davik cache and data, then swipe. Once done just flash your rom. I would copy the rom to the download folder on the internal storage (/sdcard/download/) before flash your new twrp.
Click to expand...
Click to collapse
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
redheadplantguy said:
I HAVE flashed 2631 for the qualcomm lte.
I've done or several times since you told me that's the best version.
IT WILL NOT BOOT INTO TWRP. it's a scrambled screen. That's all. No touch options. No check boxes. After a minute, tablet reboots itself. I am on stock firmware still. Rooted.
Maybe I should just try CWM. never had this much problems with twrp on any other device.
Click to expand...
Click to collapse
How about wipe cache/davikcache/data with your stock recovery (just reflash your stock recovery). After that let it boot up, then power down and flash twrp. Once done, don't boot up, boot back to twrp . Let me know how it goes.
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
redheadplantguy said:
Cool. I can try that when I get home. Do you have a link handy for the stock recovery?
Click to expand...
Click to collapse
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
buhohitr said:
Please try this twrp. Many ppl reported it's working for p607t.
http://forum.xda-developers.com/showpost.php?p=53138918&postcount=776
If not working then we will go for stock recovery.
Click to expand...
Click to collapse
THANK YOU SO MUCH! TWRP booted right up, and nandroid in progress. now I'll be able to try some custom ROM's and play in system.
:laugh:
Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe.
Click to expand...
Click to collapse
That's fine, you need to wipe system to flash a new ROM.
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Click to expand...
Click to collapse
How long does it stay stuck? Most ROMs take a lot of time in flashing system because it involves unpacking and flashing firmware. Depends on the installer, really.
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
Click to expand...
Click to collapse
Can you remember if you also selected System partition when making backups? If you did, try restoring after wiping System, data and cache.
mharis05 said:
That's fine, you need to wipe system to flash a new ROM.
Click to expand...
Click to collapse
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Simone98RC said:
What I've to see?
Wiping /system on OnePlus 3 is unreccomended, since many ROMs need a OxygenOS base already installed.
If you wipe system, before flashing anything you've to restore OOS (both Stock and Community Edition are good).
If you forget that, you'll see a graceful Error 7
Click to expand...
Click to collapse
That is wrong in any form. There is no rom that needs oos system to be present before flashing. And its not recommended to (dirty flash over a stock rom when switching to a custom rom)
---------- Post added at 02:19 AM ---------- Previous post was at 02:16 AM ----------
android_fury said:
Something is going on with my phone that doesn't let me flash anything. I was on CM14 with TWRP 3.0.2-22. I did an advanced wipe and I think I selected "system" there. I didn't really see it until I started the wipe. Now I can't boot into anything because I wiped the rom and am stuck without being able to flash anything.
Some things I tried:
When I flash the official CM14, it starts the flashing process, but doesn't get past that system flashing.
Flashing an OxygenOS-based rom (OP3Lite 2.4.2) got stuck on "extracting system."
Restoring a CM13 nandroid backup I had from before I installed CM14 finished restoring, but the phone won't boot into Android.
I ran out of ideas. How can I restore my phone?
Click to expand...
Click to collapse
Did you allow modifications in twrp ? Try to mount system in recovery before flashing / restoring
I ended up fixing it. I went to TWRP to do a regular wipe and saw the option to format partitions. I formatted system and it allowed me to reinstall roms. I flashed CM13 and CM14 with no issues. Thank you all for the suggestions.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
try wiping the dalvik cache and data and everything else and clean install the ROM
Tried wipe
anup807 said:
try wiping the dalvik cache and data and everything else and clean install the ROM
Click to expand...
Click to collapse
I wiped everything but the internal storage. I am quite new, what is clean install?
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Darrentay said:
I wiped everything but the internal storage. I am quite new, what is clean install?
Click to expand...
Click to collapse
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Thanks
jon52491 said:
Check this thread out: http://forum.xda-developers.com/oneplus-3/how-to/guide-downgrade-to-mm-flashing-ob8-t3511161
If all else fails, and you're fine with losing your data, pictures, etc. Reformat your phone. I had a similar problem when trying to go back to Android M from N. I ended up booting in fastboot and running the commands:
fastboot format:ext4 cache
fastboot format:ext4 data
fastboot format:ext4 system
Then from here you could either side load a ROM or boot into twrp and transfer your ROMs to flash. That's how I fixed my softbrick lol. There might be another way but that worked for me.
---------- Post added at 04:26 AM ---------- Previous post was at 04:25 AM ----------
Wiping all partitions except for internal storage then flashing a ROM is considered a clean flash.
Click to expand...
Click to collapse
Well in that case, I have clean flash multiple times with different ROM, but I'm still stuck at the logo once I try to reboot. I also tried to flash Os 3.2.7 and Cm 14.1 again but i got no results. Attempting to reformat I guess? I have no data since its a new phone, so I don't mind losing stuff.
Okay sounds good! Before you reformat through fastboot, try booting into twrp and reformatting the partitions through there. TWRP>wipe>advance wipe>cache>change file system>ext4
Repeat the steps for the data and system partitions as well. Then from there transfer a 6.0 ROM and flash it over with the correct Gapps.
Sent from my ONEPLUS A3000 using Tapatalk
Darrentay said:
I just got my new OP3, I rooted it and flash Cm 14.1. Everything was working fine until I added a 6x6 pattern password which I forgot. Search around a bit and looked like the only option was to factory reset. I went to twrp and wipe into factory reset. Afterwards I reboot system only to find that I'm stuck at the Oneplus logo screen, it wouldn't load into lock screen. I have tried flashing lastest stock rom as well as OS 3.2.7 which was the one I used in conjunction with Cm 14.1.
No idea how to fix this. I can use recovery mode and fastboot, but I just can't get pass that logo during reboot.
Any help would be great. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
anup807 said:
http://forum.xda-developers.com/one...ashing-ob8-t3511161/post69994625#post69994625
Try this method. It worked flawlessly for me.
Download the official ROM from oneplus Website. Support-->Downloads.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
official recovery:
http://oneplusroms.s3.amazonaws.com...694615&Signature=1Momnxm8gHWw03D401Oof5YxnE4=
Click to expand...
Click to collapse
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Darrentay said:
I notice something interesting after flashing 3.2.8, when I try to reboot system, it says no OS installed.
Click to expand...
Click to collapse
Really Strange. I think its the problem with the system partition format and encryption.
Anyway best solution now is to contact Oneplus tech support.
They'll hard reset your phone and restore it with stock firmware.
Partitions are probably corrupt or on f2fs. Check each partition and make sure it's set to ext4. If it won't allow you to do that in twrp, use the command "fastboot format:ext4 nameofpartition". After that you should be able to flash over a marshmallow ROM.
Sent from my ONEPLUS A3000 using Tapatalk
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
v.konvict said:
Have you tried changing / updating the twrp recovery. Newer roms require the unofficial one.
Click to expand...
Click to collapse
I can't solve the problem so I contacted Oneplus. They use remote access to help wipe everything and reinstall drivers. Thanks for the help though.
Hi! I went into the latest TWRP recovery with unlocked bootloader, and I wiped system, cache, dalvik and data. Then I flashed the proper vendor image, the ROM zip, Gapps and then Elemental X kernel. However, when I reboot, it just boots me into TWRP recovery. I have tried wiping dalvik cache and cache. I then tried restoring a nandroid, but it just got stuck on the Google screen. Didn't even get to the colored dots screen. I ended up flashing factory image, but I would like to get my Nandroids working and this ROM. Please help! Thanks
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Aman301582 said:
I'm no expert but I think it might be happening because of encryption. Did you disable encryption before doing all this stuff?
Click to expand...
Click to collapse
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
NateDev473 said:
Encryption in stock Android? As far as I know, I can't turn it off. It says that the device is encrypted in settings. I think nougat forces encryption.
Unless maybe there's a patched kernel that can do that?
Click to expand...
Click to collapse
I dont think is your problem , im encrypted and never have issues with twrp! Never!! What version of twrp you running? Theres an unofficial kicking around that is much better than official! Maybe you got a bad download! I would redownload all, find and download unofficial twrp 3.0.2.3 I believe. Let your phone boot before you flash custom kernel, thats always worked great for me. The latest official twrps 3022 and 3021 both have nandroid restore issues as well efs restore issues that could ruin your day
Format data and system (format, not wipe) and try installing it again. Should work
OK, thanks
neth15 said:
Format data and system (format, not wipe) and try installing it again. Should work
Click to expand...
Click to collapse
Only data and system? Not cache and dalvik like the purenexus install guide says?
NateDev473 said:
Only data and system? Not cache and dalvik like the purenexus install guide says?
Click to expand...
Click to collapse
Ofc wipe all partitions, but these two also format.
neth15 said:
Ofc wipe all partitions, but these two also format.
Click to expand...
Click to collapse
What's the difference between wipe and format? On TWRP there is only WIPE for all partitions, but a format data button.
NateDev473 said:
What's the difference between wipe and format?
Click to expand...
Click to collapse
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
neth15 said:
Wipe just deletes all data on the partition. Format makes the partition again, therefore it removes encryption, repairs potential problems etc. Format data has dedicated button in TWRP, for formatting System go to Advanced Wipe, check system, tap on Partition details, check EXT4 and perform format.
Click to expand...
Click to collapse
There is no Partition details button. Just fix partition or something like that.
NateDev473 said:
There is no Partition details button. Just fix partition or something like that.
Click to expand...
Click to collapse
Repair or Change filesystem? Yeah, it should be that.
neth15 said:
Repair or Change filesystem? Yeah, it should be that.
Click to expand...
Click to collapse
OK, I will do that. Thanks Just to clarify, I format data and system, and wipe cache and dalvik?
A Thought
Dunno if this will help, but whenever I flash a ROM/kernel combo, I always flash the ROM/gapps, boot up with whatever kernel is included in ROM to make sure it boots properly, and then after successful boot flash EX kernel through TWRP.
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
NateDev473 said:
OK, so I formatted DATA and SYSTEM, and I wiped CACHE and DALVIK. I then flashed the proper vendor image, pushing it to the device with adb push, and then adb sideload for the pure nexus ROM. It's currently installing. Then, I will adb sideload the gapps ZIP file. Then I'll reboot and see if it worked
EDIT: It just said "No OS installed"
EDIT 2: Just flashed the ROM again, and it is showing the boot animation. This time I did not do Gapps. I also wiped and formatted everything again. Hope all goes well.
EDIT 3: The ROM booted fine. Glad all is working now
Click to expand...
Click to collapse
Good job You're welcome
neth15 said:
Good job You're welcome
Click to expand...
Click to collapse
So I had flashed the ROM with no Google Apps or anything, just the ROM. But when I add a Google Account, I can't because it says Google Play Services has stopped. I just noticed that the build number is one of a Nexus 6P, and the vendor image is different, the one I manually flashed.
Hi!! I flashed twrp as soon as I got the device and as a redmi note 3 user I don't know anything about vendor so I wiped it and even flashed 3 OTA updates of RR will I face any problems in future?if yes are there any solution?
Ps- now the device is running fine no probs at all
**Thanks for tuning in this question is answered**
Yep. Now you can't mount data, vendor and probably can't flash any other roms.
Happens to my other devices.
beeduq said:
Yep. Now you can't mount data, vendor and probably can't flash any other roms.
Happens to my other devices.
Click to expand...
Click to collapse
False. Please don't spread misinformation.
RR overwrites the vendor partition anyway, so @sreek995 will have no problems. If you eventually want to flash GSIs just flash this first.
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
JoseRebelo said:
False. Please don't spread misinformation.
RR overwrites the vendor partition anyway, so @sreek995 will have no problems. If you eventually want to flash GSIs just flash this first.
Click to expand...
Click to collapse
thank you sir!!
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
This is actually my first phone with a vendor partition, but that is weird. Bad TWRPs are probably doing something terribly wrong, that shouldn't happen. But you should still be able to flash the vendor partition.
Sorry if my message came out a bit too harsh.
JoseRebelo said:
This is actually my first phone with a vendor partition, but that is weird. Bad TWRPs are probably doing something terribly wrong, that shouldn't happen. But you should still be able to flash the vendor partition.
Sorry if my message came out a bit too harsh.
Click to expand...
Click to collapse
Me and vendors were not in good terms, I guess. ?
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
I think after formating data ,you might mount it again.
Dush4711 said:
I think after formating data ,you might mount it again.
Click to expand...
Click to collapse
Nope, it's gone and never mounted again. Even format, repair or change the storage type cannot re-mount the vendor.
The only way, I can get it to work is by flashing original recovery using computer and let it format it. After that, using computer flash twrp.
But I never unlocked bootloader in this device (note5), so I don't know about it's recovery. Xiaomi's can be very tricky or very easy. My wifes phone (Mi 5X) came with unoriginal rom, and I brick it when trying to install twrp, but by open the device and doing something inside of it, I manage to restore it to original and flash twrp.
beeduq said:
Oh, then I might used bad recoveries. Happens to my two of smartphones and a tablet.
Every time, I wiped the vendor, I can't re-mount it after rebooting the recovery, even after wipe it and installing a rom seems works fine, but rebooting to recovery, "can't mount vendor" error pops up. Now I always stay away from clicking vendor when wiping the device.
Click to expand...
Click to collapse
it happened on my samsung j6 plus (SM_J610F) and i can not even flash it with original rom (in download mode it said sw rev check failed fused 4 binary 1) and t can not do any thing. twrp said /vendor has no data in it (0MB) and vendor img has (477MB). do you have any idea i can resurect my phone from dead.
tumo07 said:
it happened on my samsung j6 plus (SM_J610F) and i can not even flash it with original rom (in download mode it said sw rev check failed fused 4 binary 1) and t can not do any thing. twrp said /vendor has no data in it (0MB) and vendor img has (477MB). do you have any idea i can resurect my phone from dead.
Click to expand...
Click to collapse
Use PIT file for your model (don't use other or you'll brick the phone) in Odin.
Good luck.
Sent from my SM-A300FU using XDA Labs
;-;
you dont wipe vendor partition and reboot. If you wipe vendor, wipe system partition too reinstall the rom and everything runs fine. If you wipe vendor and dont flash rom, sure you'll get into trouble(Not that trouble actually,just cant boot into your rom).
Prathamesh 27 said:
you dont wipe vendor partition and reboot. If you wipe vendor, wipe system partition too reinstall the rom and everything runs fine. If you wipe vendor and dont flash rom, sure you'll get into trouble(Not that trouble actually,just cant boot into your rom).
Click to expand...
Click to collapse
yep, vendor is essential to runs the system