Related
It seems the n9 is eligible. Anyone has tried or thinking of trying? I might try
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
dictionary said:
Flashing it right now. Just going to miss root, so u can drop my DPI and restore some apps.
Edit: sweet!! Though you can't fine tune the size, it now has default a way to change screen size/DPI. Now I'm only needing root to restore some apps and data.
Click to expand...
Click to collapse
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Do we have to be on stock to receive the notification?
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
greiland said:
I opted in for the Android N program. Received the OTA and installed but the install FAILED. Now I can't boot and can't install an image because my bootloader is locked. Am I screwed?
EDIT: It's stuck on the "Google" screen
Click to expand...
Click to collapse
Same thing happened to me. The ota failed about 1/4 of the way through. Luckily my bootloader was unlocked. After reinstalling the system image and booting up it failed a second time when installing the ota. I think the ota has some definite issues.
Try the Nexus Root Toolkit to return to stock.
mikereidis said:
Works pretty well for me so far, except for the fact that kernel support for libusb is gone, which stops my Headunit app from working over USB.
No root yet.
Recovery is replaced with stock recovery after a reboot.
There is more discussion in popular phone threads, like the one for Nexus 6p.
Click to expand...
Click to collapse
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
I also went the OTA route and then got stuck in a Google logo boot loop. Boot loader is locked so I am trying a factory reset. Factory reset just finished as I'm typing this. It took about 40 minutes!!!! Once again seems to be stuck on the Google logo.
Edit--
Was able to get into fastboot and install factory image! Used the Nexus Toolkit to unlock the bootloader and so far things seem to be going smoothly.
I got the OTA and it installed fine 2 bugs I have found are if you're watching YouTube and put it in split screen with hangouts and tap the hangouts screen the video will go black until you tap on the YouTube side and the other bug is that the device decided to randomly put itself in airplane mode but over all I am liking it
Sent from my Nexus 5X using Tapatalk
OTA fails for me with message stating "Android Beta Program Verification failed..." after the download. I've registered for the BETA program as normal and got the OTA notification. Same install method worked fine on my 6P. As stated above, looks like the OTA for the 9 has some issues...
USBhost said:
Well I don't think the kernel if it had libusb stopped supporting it.
Because this is pretty much what changed in it https://github.com/USBhost/FIRE-ICE/commit/b88667be3ca75cdfd67269e25fb43956d78004c9
the defconfig. I ripped the defconfig from the kernel image, and I applied the needed changes to my defconfig.
edit:
if you want the N defconfig here you go https://github.com/USBhost/FIRE-ICE/commit/afdf42bd4af6aa042b9d9997de91d3e60c9ccc7e
Click to expand...
Click to collapse
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
mikereidis said:
Has somebody released N kernel source ?
I don't think there is any /dev/bus/ directory, never mind /dev/bus/usb/... but I'd feel more positive about that if I had root to verify.
Click to expand...
Click to collapse
well Google did release the source for it but... they goofed on it
Check it out https://github.com/USBhost/FIRE-ICE/tree/android-tegra-flounder-3.10-n-preview-1
BTW my kernel works on the N preview
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
naddie said:
I registered my Nexus 9 for the beta and got the OTA. But it failed with an ERROR (android on it's back with a !). It then rebooted and gets stuck at the Google logo for hours. My Nexus 9 was completely stock on 6.0.1. I downloaded the factory image, but I cannot unlock the device to flash it. All guides seem to say I need to enable Developer Options and enable USB Debugging, but since I can't boot into Android, I can't go that far. Am I screwed?
Click to expand...
Click to collapse
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
USBhost said:
sorry to tell you but yep!
you can try talking to Google to see if they can fix it.
Click to expand...
Click to collapse
So being straight laced and not rooting actually bricked my tablet? What the hell....
I'm a bit surprised there's no way to flash a factory image when the bootloader is locked. If security is a concern why not sign the factory image? Make it something we can sideload like an OTA update.
I am in the same boat!!!
naddie said:
So being straight laced and not rooting actually bricked my tablet? What the hell....
Click to expand...
Click to collapse
I am in the same situation. I figured that the software would be buggy but not actually brick my tablet. If anyone knows of a solution, I hope they post it here!! I would advise against installing this onto a Nexus 9 if anyone reading this is considering this firmware!!!
better33 said:
Couldn't flash mine, always have "missing system.img" and "unable to allocate -xxxxx bytes"... Didn't have much time, I will try again later. Do I need to come from clean stock to flash it ?
Click to expand...
Click to collapse
No, just wipe everything except internal. You have to extract the last image.sksmsksjssksm whatever zip. Then just fastboot flash each file individually.
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
kalinskym said:
Will I be able to recover if the Android N preview fails on my Nexus 9 by unlocking the bootloader and enabling USB debugging beforehand then install Android N preview?
Click to expand...
Click to collapse
In short, yes. You're basically leaving yourself a backdoor to flash a factory image should the Android N preview OTA takes a dump on you.
As my professor said to us in the laboratory: Do as I say, not as I do.
To be fair, I was hoping to do a no-wipe upgrade so I could experience Android N with all my stuff intact. I knew it was beta, but come on!
Hi All.
I am in a bit of a situation right now.
My video recording app filled up internal storage and corrupted system files (because i forgot to point it to my external SD card).
This caused a boot loop, so I went into recovery and (regrettably) wiped the internal storage. Now when I try to flash or install a new (stock) rom, none will work. I have tried sideloading, installing through (TWRP) recovery and wiping the cache multiple times as I comb through the internet for files like the system.img, boot.img, and droidboot.img, to no avail.
TLDR; I need either a backup of someone elses Zenfone 2 ZE500KL, or the system files required to get me up and running, otherwise I have a brick on my hands.
Thanks for any help
Matt
Unlock bootloader, flash the official firmware, I think you can find it on the internet. Have you tried that? You can even get a deodexed rom from here and extract files needed and flash them...
Sent from my Tab3 Lite 7.0 using XDA Labs
Yep, found it on the official asus site...
Sent from my Tab3 Lite 7.0 using XDA Labs
jocamucko said:
Yep, found it on the official asus site...
Sent from my Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
Yeah, I have.
I've tried 2 different stock roms (Marshmallow, Lollipop) about 10 different times in both stock recovery and TWRP, mixing in some full wipes and just wiping the cache. I've been looking at a whole lot of tutorials on how to go back to stock, to no avail. I've tried modifying the rom so I no longer get the status 7 error (which I dont believe I should need to do) because I get signature verification errors on both my unmodified stock roms.
Sometimes it does do through the installation fine with the modified roms (in TWRP) and everything seems fine until I click reboot. On the screen it says that there is no OS installed, and when I do reboot to the OS I get stuck on the ASUS logo.
Not gonna give up, but a bit of a headache anyway.
I dont believe I have ever unlocked the bootloader, but how would I do that from outside Android?
Thanks in advance, Matt
mapooo said:
Yeah, I have.
I've tried 2 different stock roms (Marshmallow, Lollipop) about 10 different times in both stock recovery and TWRP, mixing in some full wipes and just wiping the cache. I've been looking at a whole lot of tutorials on how to go back to stock, to no avail. I've tried modifying the rom so I no longer get the status 7 error (which I dont believe I should need to do) because I get signature verification errors on both my unmodified stock roms.
Sometimes it does do through the installation fine with the modified roms (in TWRP) and everything seems fine until I click reboot. On the screen it says that there is no OS installed, and when I do reboot to the OS I get stuck on the ASUS logo.
Not gonna give up, but a bit of a headache anyway.
I dont believe I have ever unlocked the bootloader, but how would I do that from outside Android?
Thanks in advance, Matt
Click to expand...
Click to collapse
That's the problem, locked bootloader. forum.xda-developers.com/zenfone-2-laser/general/talking-ze500kl-g-unlock-bootloader-t3352776 there you got the old content, try it, it's from the outside of the phone. If your phone boots after that normaly, you got bootloader unlocked and your phone unbricked.
jocamucko said:
That's the problem, locked bootloader. forum.xda-developers.com/zenfone-2-laser/general/talking-ze500kl-g-unlock-bootloader-t3352776 there you got the old content, try it, it's from the outside of the phone. If your phone boots after that normaly, you got bootloader unlocked and your phone unbricked.
Click to expand...
Click to collapse
Thanks for your help.
My phone is now up and running.
Now I can close my 10 tabs on the Zenfone 2 lol.
mapooo said:
Thanks for your help.
My phone is now up and running.
Now I can close my 10 tabs on the Zenfone 2 lol.
Click to expand...
Click to collapse
It's nothing, that's the least I can do, put that phone to good use! :good:
Help !! you can give me all the files * img
Please
trongnguyen(vietnamese) said:
Help !! you can give me all the files * img
Please
Click to expand...
Click to collapse
Why do you need it? I can only assume that you haven't unlocked your bootloader. More info?
mapooo said:
Why do you need it? I can only assume that you haven't unlocked your bootloader. More info?
Click to expand...
Click to collapse
unbick
help
trongnguyen(vietnamese) said:
unbick
help
Click to expand...
Click to collapse
have you tried unlocking your bootloader?
mapooo said:
have you tried unlocking your bootloader?
Click to expand...
Click to collapse
I want file "img (system.img,boot.img...)
trongnguyen(vietnamese) said:
I want file "img (system.img,boot.img...)
Click to expand...
Click to collapse
I'm not sure if you understand, but it would be helpful if you told us your problem, rather than continuing to nag for an img file. I didn't need it to fix my phone, so without you giving us more info all I can say is try unlocking your bootloader.
I know you want an img file, but if life was that simple, you wouldn't need an img file in the first place *insert inception music*
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted
Hello,
I have Tab A 2019 & I need to downgrade Sm-t510 from Android 9 to 8..Any help please?
Jasmin74 said:
Hello,
I have Tab A 2019 & I need to downgrade Sm-t510 from Android 9 to 8..Any help please?
Click to expand...
Click to collapse
A) why do you want to downgrade from 9 to 8?
B) the tablet came with Android 9, it’s not possible to downgrade to 8.
secretwolf98 said:
A) why do you want to downgrade from 9 to 8?
B) the tablet came with Android 9, it’s not possible to downgrade to 8.
Click to expand...
Click to collapse
I could do it from 8 to 6 on other tablets - like tab A 2016 sm-t580
Jasmin74 said:
I could do it from 8 to 6 on other tablets - like tab A 2016 sm-t580
Click to expand...
Click to collapse
That's because the SM-T580 model came with Android 6.0.1
secretwolf98 said:
That's because the SM-T580 model came with Android 6.0.1
Click to expand...
Click to collapse
is there any custom rom based android 8 for this device? my device has 2GB ram and now updated itself to 11 but it gives me cancer almost garbage now..
i found a android 9 stock rom but i wonder what else can do? i know that android 8 works well with 2GB ram. any custom rom for this device suggestion should be perfect for performance usage. thanks regards
dedeoglumrt said:
is there any custom rom based android 8 for this device? my device has 2GB ram and now updated itself to 11 but it gives me cancer almost garbage now..
i found a android 9 stock rom but i wonder what else can do? i know that android 8 works well with 2GB ram. any custom rom for this device suggestion should be perfect for performance usage. thanks regards
Click to expand...
Click to collapse
There was never a stock OR custom ROM based on Android 8 for this tablet. There are many others, including myself, happily running Lineage 18.1 with only 2gb of RAM. Maybe you just need to do some de-bloating.
lewmur said:
There was never a stock OR custom ROM based on Android 8 for this tablet. There are many others, including myself, happily running Lineage 18.1 with only 2gb of RAM. Maybe you just need to do some de-bloating.
Click to expand...
Click to collapse
i used a twrp then the device stucked. waited a day long to drain battery now which twrp version is good for this device?
dedeoglumrt said:
i used a twrp then the device stucked. waited a day long to drain battery now which twrp version is good for this device?
Click to expand...
Click to collapse
The version linked in the OP.
lewmur said:
The version linked in the OP.
Click to expand...
Click to collapse
what does it means OP dude?
dedeoglumrt said:
what does it means OP dude?
Click to expand...
Click to collapse
I'm 82 yrs old and my generation doesn't like the term "dude". OP stands for Original Post. It is the first post in the thread and it is ALWAYS where you should start reading. It will have the instructions and the download links you need.
lewmur said:
The version linked in the OP.
Click to expand...
Click to collapse
The order I tried but did not get any results is as follows;
1- I installed the latest rom released by samsung which is android 11 with frija tool with odin and the device returned to its normal state.
2- I'm logging into the system with this official latest. I activate the developer options and activate the oem unlock. resets to factory settings. I pass the android welcome screens again and turn on the system. I am connecting to the wireless network. I go to developer options and see "oem already unlocked". When I restart the device to check, I get the "device unlocked" warning and I'm sure about the unlock.
3- After this stage, I tried to write this file "twrp-3.5.2_9-0-T510XXU5CUF4-20210725.tar.md5" with twrp by entering "download mode" with odin. when i try this, i get an error like "only official install is available" or sometimes it installs twrp in a way that i don't understand.
4- If twrp is installed, I install the file named "multidisabler-t51x-1.41.zip" by first doing twrp format&wipe, but the device never opens, so it gets stuck.
5- Or when I enter "download mode" with twrp installed and want to install android 10 or 9 stock rom of this device that I downloaded from SAMMOBILE, I get a warning "KERNEL ERROR, DEV 1 BINARY 3 etc.. I also tried linage and nexus roms. When twrp was installed they gave the same "KERNEL REV." errors.
What could I be missing at this point? I would be glad if you help me. I've been trying for 2 days with no results.
My main goal is to get rid of android 11, but obviously they put a "downgrade" barrier and how can we overcome it.
dedeoglumrt said:
The order I tried but did not get any results is as follows;
1- I installed the latest rom released by samsung which is android 11 with frija tool with odin and the device returned to its normal state.
2- I'm logging into the system with this official latest. I activate the developer options and activate the oem unlock. resets to factory settings. I pass the android welcome screens again and turn on the system. I am connecting to the wireless network. I go to developer options and see "oem already unlocked". When I restart the device to check, I get the "device unlocked" warning and I'm sure about the unlock.
3- After this stage, I tried to write this file "twrp-3.5.2_9-0-T510XXU5CUF4-20210725.tar.md5" with twrp by entering "download mode" with odin. when i try this, i get an error like "only official install is available" or sometimes it installs twrp in a way that i don't understand.
4- If twrp is installed, I install the file named "multidisabler-t51x-1.41.zip" by first doing twrp format&wipe, but the device never opens, so it gets stuck.
5- Or when I enter "download mode" with twrp installed and want to install android 10 or 9 stock rom of this device that I downloaded from SAMMOBILE, I get a warning "KERNEL ERROR, DEV 1 BINARY 3 etc.. I also tried linage and nexus roms. When twrp was installed they gave the same "KERNEL REV." errors.
What could I be missing at this point? I would be glad if you help me. I've been trying for 2 days with no results.
My main goal is to get rid of android 11, but obviously they put a "downgrade" barrier and how can we overcome it.
Click to expand...
Click to collapse
You have to go through the vbmeta install proceedure before you can install TWRP.
build no : T510XXU5CUF4
Samsung Galaxy Tab A SM-T510 gta3xlwifi
CSC : TUR
lewmur said:
You have to go through the vbmeta install proceedure before you can install TWRP.
Click to expand...
Click to collapse
how can i get the documentation of this stuff ? "vbmeta install proceedure"
lewmur said:
I'm 82 yrs old and my generation doesn't like the term "dude". OP stands for Original Post. It is the first post in the thread and it is ALWAYS where you should start reading. It will have the instructions and the download links you need.
Click to expand...
Click to collapse
I apologize for my way of speaking, Mr. Lewmur. im translating my words because my english not necessary for this type for chain tasks and tasks that require patience
dedeoglumrt said:
how can i get the documentation of this stuff dude ? "vbmeta install proceedure"
Click to expand...
Click to collapse
Go to the ROMs, Kernel, Recover section on how to install Nexus Stock ROM. It will install both the vbmeta and TWRP along with the ROM. If you don't like that ROM, you can then install what you want via TWRP. Just remember to format the data partition when it first boots to TWRP.
lewmur said:
Go to the ROMs, Kernel, Recover section on how to install Nexus Stock ROM. It will install both the vbmeta and TWRP along with the ROM. If you don't like that ROM, you can then install what you want via TWRP. Just remember to format the data partition when it first boots to TWRP.
Click to expand...
Click to collapse
also i edited now my this post and removed "dude" word
lewmur said:
Go to the ROMs, Kernel, Recover section on how to install Nexus Stock ROM. It will install both the vbmeta and TWRP along with the ROM. If you don't like that ROM, you can then install what you want via TWRP. Just remember to format the data partition when it first boots to TWRP.
Click to expand...
Click to collapse
mr lewmur, Is there a way to install the android 9 rom that I downloaded from sammobile instead of Nexus? i mean downgrade 9 from 11 ( T510XXS2ASK1_T510TUR2ASI4_TUR)
Android 8 is vulnerable to that nasty "immortal" rootkit.
Pie is a good OS and is immune to the uninstallable rootkit variants.
I wouldn't go less than Android 9 or more than 10...
dedeoglumrt said:
mr lewmur, Is there a way to install the android 9 rom that I downloaded from sammobile instead of Nexus? i mean downgrade 9 from 11 ( T510XXS2ASK1_T510TUR2ASI4_TUR)
Click to expand...
Click to collapse
No. You can't downgrade. And the Nexus Stock ROM isn't really stock. It is a custom ROM meant to feel like the Nexus ROM.
Hello!
I was recently gifted a Samsung Galaxy Tab S6 SM-P13. I only use my tablet to watch chess videos on Youtube, so I was happy to get a tablet to mess around a bit with it. I did not know much about rooting, but I thought installing Lineage OS and learning from it would be exciting.
I'm good at following instructions, but with some overenthusiasm, I realized that Lineage OS did not support my model a bit too late. So I reached step 5 of "Installing a custom recovery using heimdall" in the official instructions (https://wiki.lineageos.org/devices/gta4xlwifi/install).
But I could not do step 6 as it could not boot into recovery mode. It will stay in download mode with the following message:
<!>
_partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header(6)
CUSTOM recovery
VBMETA P613XXU1AVG5, 54410278R
I have looked around to see fixes, but I have felt slightly overwhelmed. So I have installed Odin, and at this moment, as Lineage OS is not an option, I don't care which ROM to install (stock, lite, etc...).
Can someone guide me on what to do now so I won't worsen things?
Thank you for your help in advance!
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
oFluffy said:
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
Click to expand...
Click to collapse
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Pablosky000 said:
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Click to expand...
Click to collapse
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
oFluffy said:
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
Click to expand...
Click to collapse
Perfect!!! Thanks a lot. I didn't have much expectation apart from "not bricking it". I just wanted to make sure I did not do anything stupid. Follow your instructions. And it worked perfectly! Thanks a lot for the help! I truly appreciated. I am usually alright at a lot of these things, but I ended up being a bit lost, and just wanted to make sure I stopped doing stupid stuff!
Million thanks!!!!
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
mr_scientific127 said:
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
Click to expand...
Click to collapse
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
deckardsdream1988 said:
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
Click to expand...
Click to collapse
Thank you, I managed to get my tablet working. Really wish samsung made the firmware more available.