Related
So after blowing off the second half of my duties at work today, I managed to allocate enough time to get my SM-N910V rooted.
I have a few basic questions about what I should expect to see happen.
Allegedly, Verizon is rolling out an OTA upgrade to 6.0.1 Marshmallow sometime soon. Now that I have 'custom' boot and root achieved, will my device still receive and adhere to this OTA upgrade?
I have not applied any custom ROMs to the device. All I have done is follow the steps on this forum to unlock the bootloader and permroot.
If yes, cool!
If no, could someone please share with me a uniform resource identifier (lol) that links to a guide for installing CM13 to this device?
I will use my mind to beam eternal luck at anyone who helps me out. Thankyas.
Have you ever used Odin?
If you have twrp just load onto an sd or the phone and make sure to clear cache and wipe.
Bicknasty said:
Have you ever used Odin?
Click to expand...
Click to collapse
Yessir Mr. Nasty,
I followed a guide on this part of the forum that had me use Odin. After using Odin successfully I was able to get TWRP up before normal boot!
vIgGeN7 said:
If you have twrp just load onto an sd or the phone and make sure to clear cache and wipe.
Click to expand...
Click to collapse
Just to clarify, you're saying that if I boot into TWRP again and clear the cache/wipe, I'll go back to factory settings and get the OTA?
If you have a microSD card, use TWRP to backup all of your current data to it if you'd like to preserve it and have something to restore if anything goes awry. Download a custom ROM zip and whatever other zips you'd need for that particular ROM, and put them on the card. Use TWRP to format data and wipe everything EXCEPT FOR THE CARD, and then reboot into recovery mode again and open the TWRP install menu.
In that menu, navigate to external_sd (or whichever root level folder it is that contains the strings "ext" and "sd", referring to the microSD card), and select the zip or zips (in the proper order) that you want to flash. Then flash them, wipe cache/dalvik, and reboot.
I wouldn't stay on a stock ROM if I were you. You might avoid getting the OTA, but you're guaranteed to avoid it by running a custom ROM. JasmineROM seems to be the go-to ROM for stability, but hsbadr's CM13 builds are very functional.
Bicknasty said:
-snip-
Click to expand...
Click to collapse
Thank you for being so specific and clear, and for helping me out. I am new to this, used to working on computers that I can tear apart more easily and change things inside of.
I will keep this in mind and consider switching. I have a lot of free time with a 1GB/1GB
Futtermax said:
So after blowing off the second half of my duties at work today, I managed to allocate enough time to get my SM-N910V rooted.
I have a few basic questions about what I should expect to see happen.
Allegedly, Verizon is rolling out an OTA upgrade to 6.0.1 Marshmallow sometime soon. Now that I have 'custom' boot and root achieved, will my device still receive and adhere to this OTA upgrade?
I have not applied any custom ROMs to the device. All I have done is follow the steps on this forum to unlock the bootloader and permroot.
If yes, cool!
If no, could someone please share with me a uniform resource identifier (lol) that links to a guide for installing CM13 to this device?
I will use my mind to beam eternal luck at anyone who helps me out. Thankyas.
Click to expand...
Click to collapse
I dont know what everyone is thinking, but OTA will not work with rooted device. It will failed and in most case you will nee to flash full stock rom to fix it, then your bootloader will locked again. The best bet is to wait until Samsung released the rom and Dev here will modified it the right way so you can flash with TWRP.
Sent from my SM-N920V using Tapatalk
Honestly, don't bother with CM13 yet. It's buggy. I was on it for a short while, tried a couple different builds but I got sold on the Note 5 port which is on 5.1.1. If you have any apps that don't allow mock locations, they won't work on any 6.0/Marshmallow ports (i.e. CM13) from my short experience. I could be wrong. I couldn't find a way to allow mock locations on CM13, so I went somewhere else.
JOSHSKORN said:
Honestly, don't bother with CM13 yet. It's buggy. I was on it for a short while, tried a couple different builds but I got sold on the Note 5 port which is on 5.1.1. If you have any apps that don't allow mock locations, they won't work on any 6.0/Marshmallow ports (i.e. CM13) from my short experience. I could be wrong. I couldn't find a way to allow mock locations on CM13, so I went somewhere else.
Click to expand...
Click to collapse
I think CM13 is worth giving a chance.
I'm about 90% sure the MM update will come with a new bootloader (a locked one). I highly advise against trying to accept it if/when it comes. Someone here will tear it apart and make odin flashable images to get us on 6.0.1 TW rom. Until then, flash TWRP and CM13. I've been using it daily and it's one of the better CM roms I've used on any device.
Also look into Dual Boot Patcher so you can crack flash roms without affecting your primary one.
Sent from my SM-N910V using Tapatalk
Bicknasty said:
If you have a microSD card, use TWRP to backup all of your current data to it if you'd like to preserve it and have something to restore if anything goes awry. Download a custom ROM zip and whatever other zips you'd need for that particular ROM, and put them on the card. Use TWRP to format data and wipe everything EXCEPT FOR THE CARD, and then reboot into recovery mode again and open the TWRP install menu.
In that menu, navigate to external_sd (or whichever root level folder it is that contains the strings "ext" and "sd", referring to the microSD card), and select the zip or zips (in the proper order) that you want to flash. Then flash them, wipe cache/dalvik, and reboot.
I wouldn't stay on a stock ROM if I were you. You might avoid getting the OTA, but you're guaranteed to avoid it by running a custom ROM. JasmineROM seems to be the go-to ROM for stability, but hsbadr's CM13 builds are very functional.
Click to expand...
Click to collapse
I might add to that storing a copy of that backup on another device... your desktop computer, perhaps, so that if something really goes bad and wipes your sd card, you still have a backup.
Do not, no matter how much your phone nags you to, take an OTA now that you're rooted. The odds are good that they've closed the exploit used to get root.
If you're looking for stability, Jasmine ROM is the best that I've tried. It's not being supported anymore, but it really doesn't need it. Everything works. I froze, then deleted every single Samsung and Google app that I don't use and it is just smooth.
CM 13? The last I looked, the camera doesn't work well, Bluetooth is problematic, you can't set your sd card as internal storage and a few other niggling issues. I've been doing this since my Droid Incredible and have found that ROMs ported from other devices will have issues until the developers marry the software to the hardware. I'm now waiting for the official Marshmallow to drop and let the developers take a crack at it.
joshw0000 said:
I'm about 90% sure the MM update will come with a new bootloader (a locked one). I highly advise against trying to accept it if/when it comes. Someone here will tear it apart and make odin flashable images to get us on 6.0.1 TW rom. Until then, flash TWRP and CM13. I've been using it daily and it's one of the better CM roms I've used on any device.
Also look into Dual Boot Patcher so you can crack flash roms without affecting your primary one.
Click to expand...
Click to collapse
Dual boot patcher has worked pretty reliably for me. Just be sure to thoroughly read the directions to make doubly sure that nothing goes wrong.
douger1957 said:
CM 13? The last I looked, the camera doesn't work well, Bluetooth is problematic, you can't set your sd card as internal storage and a few other niggling issues. I've been doing this since my Droid Incredible and have found that ROMs ported from other devices will have issues until the developers marry the software to the hardware. I'm now waiting for the official Marshmallow to drop and let the developers take a crack at it.
Click to expand...
Click to collapse
Bluetooth is flawless. I can't see why anyone would set their sd card as internal (defeats the point of being able to move info between other phones and/or computers). Camera works very well (for CM). I've had very few issues with taking pictures. Recording video doesn't work for me. I've modded every phone I've used (I've owned many that I wouldn't carry due to no root) since the Eris and this is IMO the best CM port ever.
Sent from my SM-N910V using Tapatalk
I am using PaulPizz 5.1.1 ROM and it's working almost flawlessly. I'm happier than ever with this phone. I want to wait for the OTA 6.0.1 to hit and the teardown of that to begin before I switch.
I'll look into dual boot.
Hey,
I just wanted to inform you about an issue that happens in TWRP. I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B. I think TWRP should inform the user that rebooting will brick the device. What are your thought on that? It could be done similar to how TWRP informs the user to install supersu if the phone isnt rooted.
This would be really helpful as it would prevent many people like myself from bricking their phones.
Now if I connect my pixel it only shows Qualcomm HS-USB Diagnostics 900E (COM3). No bootloader, fastboot, or recovery is present.
Here are a coupe of links of other people that did the same thing:
https://productforums.google.com/forum/#!topic/phone-by-google/sXjCoQ8glac
http://forum.xda-developers.com/pixel-xl/help/pixelxl-bricked-t3517310
Thanks!
Edit
I contacted the devolper of TWRP and he says that it should have boot loader regardless.
Here is the history: At work 3pm, froze Android system apk and some other telephone apps to troubleshoot something, I know I shouldn't do this. Resulted into boot loop. Go into twrp recovery and wipe data. It boots up fine and I see it downloading updates but it never goes through, I attempt to go back to recovery and apparently it's back to the stock recovery even though I originally had TWRP rc1.
I get home at 7 pm, I want to install TWRP rc1 so I send the command to boot into TWRP and then I install the zip, then I install sr5 SuperSU. I change to slot b and it's been bricked since.
It arrived November patch and it stayed like that since I was rooted. It attempted to install 7.1.1 but it returns installation problem. I think the bootloader was removed because of the failed update.
Your in download mode. I had this happen once on my Nexus 7. I held power for 90 seconds and it went back to bootloader. However I dont know about the pixel. Its still a new and uncharted device.
You also have to realize TWRP is in an unstable stage. You really should not flash anything until its in final release mode. I know I know... Hindsight is 20/20.
If you have insurance you could get it replaced.
Good luck.
sorry to hear dude..
bahehs said:
I think TWRP should inform the user that rebooting will brick the device. What are your thought on that?
Click to expand...
Click to collapse
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
bahehs said:
I just bricked my Pixel by switching to slot B without flashing a bootloader in slot B.
Click to expand...
Click to collapse
Does anyone have an understanding about how something like this could potentially happen? Do these phones ship without information on the second slot? After my phone OTA updated, I switched slots without issue back to the previous version by following the information from Android Police. I'm not clear on what exactly would need to happen for the noted situation, and how someone could potentially get into a similar situation, unless the phone ships without information on the second slot. Switching slots worked without issue the times I tried it, but my phone had been through a typical OTA update before switching slots, so there was definitely information on both slots when I tried it.
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Scott said:
Just an FYI: I am running Slot B on my device. Never tried Slot A. Just an FYI
Click to expand...
Click to collapse
Same, mine is on slot B. Dunno if it came that way, but it is only two days old. I let it take the OTA then flashed Francos kernel and then booted the root su image.
I really regret not watching more closely how all of impacted which slot it was on.
Sent from my Pixel XL using XDA Labs
Everytime you get OTA update you will switch slots. If you update via flashall it will say on the same slot.
This mode can't be a complete brick but it doesn't look like anyone has a solution yet. Maybe we will need some HTC tool?
Also when you root or modify you take responsibility for anything that happens. There is always a chance of a brick. At least Google will still probably warranty these devices.
Sent from my Pixel using Tapatalk
CZ Eddie said:
I'm just curious. Have you ever donated any money to TWRP for the free developmental software they provide for free to the community to try/test with for free?
Click to expand...
Click to collapse
This comment is unnecessary and serves no purpose in this thread.
Sent from my Pixel XL using XDA-Developers mobile app
I'm okay with that.
Updated op with more info
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
reb1995 said:
I installed TWRP while in the car riding with my girlfriend. I had some issues with the mobile radio showing no SIM card. Due to my limited options, I tried switching rom slots. It booted into the old software and said there was an update etc. I don't think switching rom slots leads to bricking if no other mods were done.
Click to expand...
Click to collapse
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Sent from my Pixel XL using Tapatalk
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
Sorry for the long delay. No I was not rooted.
yearn2burn said:
I kind of had the impression none of the stuff we're flashing is the bootloader itself. Isn't the bootloader the Android equivalent of Windows BIOS? Doesn't the bootloader load the boot image? Then the boot image mounts the system partition? So how could anything we're flashing cripple the bootloader?
Click to expand...
Click to collapse
Bump
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
bahehs said:
were you rooted because I had an ota in process wich failed while I was rooted which I think was the cause of the issue.
Click to expand...
Click to collapse
You are right a failed OTA could brick a pixel phone
DR3W5K1 said:
The problem is that the phone ships with an empty slot. If you try to boot it your permanently bricked do to having no bootloader on that slot. Once you take an OTA both slots have data and you're safe.
You are right a failed OTA could brick a pixel phone
Click to expand...
Click to collapse
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
aholeinthewor1d said:
There is only one bootloader though so that's the confusing part. Still not sure how some people bricked completely. The bootloader is the first thing to load and tells the phone which slot to boot. Each slot does have its own boot, system, and vendor though. Been discussing this a lot on some other threads and there is still no answer has to what some of these people did internally that messed up their phones
Click to expand...
Click to collapse
Failed bootloader flash? The Google .IMG files contain bootloader's.
EDIT I do believe the flash_all.sh flashes the bootloader
So you cant even run ADB commands ( a.k.a Bootloader / Recovery mode ), its a hard brick or soft ?
Does your PC detect the device when its on and connected via USB ?
Why did you switch slots in the first place ? if your taking an OTA on a rooted device with SU an OTA wont even apply via TWRP, you have to manually flash with the flash-all.bat script or part by part and the A / B boot slots are handles by the updates so you don't accidentally boot with a slot with no bootloader.
There is no need to swap A / B manually and if your going to flash and want to play with the A / B slots you should at least flash the partitions first but hindsight is a wonderful thing.
Aboot here might be your friend, but as this device is still quite new to many devs and or the tools might not be publicly available . . .
So I've seen slot of people discussing and people complaing about people discussing it in other OPs and figured I'd just make one here to openly discuss this massively confusing matter.
This a good start. I have tried dual slot boot, but end up losing the ability to access quick settings, developer options etc. also, switching from one slot to another is not convenient.
Hope in the near future, some one can make the dual slot boot be helpful
bush911 said:
This a good start. I have tried dual slot boot, but end up losing the ability to access quick settings, developer options etc.
Click to expand...
Click to collapse
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Finally, after wiped userdata, everything gets back.
by the way, some time I can switch between slots, some times I can't via twrp.
So, it's long way to go maybe.
billiepreks said:
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Click to expand...
Click to collapse
Just to be clear I have no knowledge other than what I've read on the many threads and and insatiable need for knowledge....I'm not a dev or themer or modder.
My Google factory Image flashing experience.
Active Slot
Radio
Bootloader
Vendor
Boot Image
System
Inactive Slot
System_other Image
I believe this based on command prompt output and the fact that after flashing custom rom and switching slots, I had the old (previous) bootloader
Radio
Vendor in the new slot.
I hear people having different command prompt outputs?
Running latest Android sdk 2.5.03
Golf c said:
My Google factory Image flashing experience.
Active Slot
Radio
Bootloader
Vendor
Boot Image
System
Inactive Slot
System_other Image
I believe this based on command prompt output and the fact that after flashing custom rom and switching slots, I had the old (previous) bootloader
Radio
Vendor in the new slot.
I hear people having different command prompt outputs?
Running latest Android sdk 2.5.03
Click to expand...
Click to collapse
I'm gona be starting completely over today. Don't have to but I'm more curious to figure some stuff out. So how do I go about flashing complete stock to both slots. Trying to make it like it was out of the box
aholeinthewor1d said:
I'm gona be starting completely over today. Don't have to but I'm more curious to figure some stuff out. So how do I go about flashing complete stock to both slots. Trying to make it like it was out of the box
Click to expand...
Click to collapse
Thats the question? I have no idea how it came out of the box. I can figure it out from my own flashing history though. One issue is OTA'S switch slots, factory images do not. So you would have to pay attention to your flashing history to know what's in your inactive slot.
I have never messed with what slot to flash to. I have been flashing it just like my nexus and have never had any problems.
jasonsamms666 said:
I have never messed with what slot to flash to. I have been flashing it just like my nexus and have never had any problems.
Click to expand...
Click to collapse
This phone is far from a Nexus. TWRP and Root are in the kernel now. Flashing is definitely different.
Are you taking OTA'S or keeping the same slot with factory images?
billiepreks said:
Same here, how did you fix this bug ? I had to do a factory reset to fix it, because when I update the rom the bugs still here.
So I've a question: it is possible to use the 2 slots of Pixel to dualboot it or it's just a dream ? Stock rom on Slot A and Pure Nexus rom on Slot B for exemple
Edit : and what is the action who activate the "bug-mode"?
Click to expand...
Click to collapse
I think in the coming weeks we should be getting more insight into our capabilities so hold tight grab a beer enjoy the ride this Cadillac phone will take us on
Golf c said:
This phone is far from a Nexus. TWRP and Root are in the kernel now. Flashing is definitely different.
Are you taking OTA'S or keeping the same slot with factory images?
Click to expand...
Click to collapse
I have not taken an ota.
jasonsamms666 said:
I have not taken an ota.
Click to expand...
Click to collapse
Me too. I think it's a little safer and easier. Depending on what your flashing, you probably have old
boot,
Bootloader,
Radio,
Vendor
in your inactive slot.
Which is easily fixed and would only come into play when switching slots on custom roms
Golf c said:
Me too. I think it's a little safer and easier. Depending on what your flashing, you probably have old
boot,
Bootloader,
Radio,
Vendor
in your inactive slot.
Which is easily fixed and would only come into play when switching slots on custom roms
Click to expand...
Click to collapse
I don't really understand how the slots work. As long as I don't tell fastboot to switch slots everything should be fine? I read that people are actually bricking these things.
Golf c said:
Thats the question? I have no idea how it came out of the box. I can figure it out from my own flashing history though. One issue is OTA'S switch slots, factory images do not. So you would have to pay attention to your flashing history to know what's in your inactive slot.
Click to expand...
Click to collapse
I know what's on each of my slots now. Slot A is NMF26U stock unrooted. Slot B is pure nexus rooted. That doesn't matter though I just wanna doublt check how to flash both slots back to factory. I think I have to flashall twice but I'm not sure
aholeinthewor1d said:
I know what's on each of my slots now. Slot A is NMF26U stock unrooted. Slot B is pure nexus rooted. That doesn't matter though I just wanna doublt check how to flash both slots back to factory. I think I have to flashall twice but I'm not sure
Click to expand...
Click to collapse
I don't think flash all twice will work because of that System_other Image? It will make all the partitions the same though, except for the system. We have to figure out the edit or command to flash twice and switch slots.
I flash all'd both by switching the active slots. What ever slot was inactive after doing this would bootloop. Tried several times. No idea what is going on, I know there are several peeps that have dual boot working.
And yes, I think the system_other might be part of it. But just guessing.
TonikJDK said:
I flash all'd both by switching the active slots. What ever slot was inactive after doing this would bootloop. Tried several times. No idea what is going on, I know there are several peeps that have dual boot working.
And yes, I think the system_other might be part of it. But just guessing.
Click to expand...
Click to collapse
I believe there is a fastboot command for switching active slots. I don't know it yet. I noticed when you throw an error in fastboot, a list of commands comes up. We have to take a look at that. I seen the - w command in there.
---------- Post added at 03:31 PM ---------- Previous post was at 03:26 PM ----------
Here is some of the commands, certainly not all of them.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/post69366928
Golf c said:
I believe there is a fastboot command for switching active slots. I don't know it yet. I noticed when you throw an error in fastboot, a list of commands comes up. We have to take a look at that. I seen the - w command in there.
Click to expand...
Click to collapse
Yes, I am using it. Fastboot set_active a
Let me reexplain what I tried.
Slot a active ran flashall.
Slot a boots fine. Then next I switched slots with
Fastboot set_active b
Flashall
B boots fine
Then made a active again.
A now bootloops.
Here is a link to the commands for fast boot.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/page1
TonikJDK said:
Yes, I am using it. Fastboot set_active a
Let me reexplain what I tried.
Slot a active ran flashall.
Slot a boots fine. Then next I switched slots with
Fastboot set_active b
Flashall
B boots fine
Then made a active again.
A now bootloops.
Here is a link to the commands for fast boot.
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080/page1
Click to expand...
Click to collapse
Out of thanks for the day. Thank you. Your example is interesting. Maybe your right, that System_other Image?
hey guys
Been messing around with tablet to find best setup then to find netflix wont work. I have reflashed back to stock rom from lineage os. but now my sd card size is showing 16gb under storage space but if I look at it elsewhere its like 6gb, when it should be 64gb, I read this is to do with userdata but I cant find any userdata files to flash.
other issue is attempting to factory reset using twrp getting alot of /data/.... (permission Denied)
how can I solve these issues? and the streaming apps (netflix and disneyplus)
thanks guys
Your data partition is encrypted. I had the same issue and found this thread:
https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595
Seems to have worked, TWRP sees the full storage amount, but still trying to get Lineage loaded...
Elysian893 said:
Seems to have worked, TWRP sees the full storage amount, but still trying to get Lineage loaded...
Click to expand...
Click to collapse
Having had this same issue recently TWRP will be your saving grace but before you go through the process in the link you should at least look at (while in TWRP) the WIPE section. Go through each of the listed options individually and hit the "repair or change File system option." What happened with mine is that the act of flashing stock changed The /DATA partition from EXT4 to NTFS and I Needed to change it back.
Regarding the Stock image you flashed double check to make sure its the one intended for your particular device storage size. Apparently there are different variants of the same stock ROM but with different PIT files (the file that sets your device partition.
One last piece of advise that may seem like a captain obvious is thing but I admittedly overlooked is when you flash your stock ROM, make sure to include not just the AP file, but also BL and CSC as well whwhenever you flash
Seems to have worked, TWRP sees the full storage amount, but still trying to get Lineage loaded...
[/QUOTE]
I tried flashing Lineage and Havoc and was never able to get either working for this device which I'm sure is likely user error but I gave up either way lol
Mekzul said:
I tried flashing Lineage and Havoc and was never able to get either working for this device which I'm sure is likely user error but I gave up either way lol
Click to expand...
Click to collapse
I actually got Lineage working fine on it. Once I got the data partition figured out I believe it was smooth sailing, though it was a while ago now.
Elysian893 said:
I actually got Lineage working fine on it. Once I got the data partition figured out I believe it was smooth sailing, though it was a while ago now.
Click to expand...
Click to collapse
Hey so I was able to get it up and running eventually as well but in the end wound up just running stock rom on this device as I was getting these weird "screen shatter" type glitches on bootup and so it wasnt really worth the hassle lol. Does rooting really even provide that much of a benefit for this device?
Mekzul said:
Hey so I was able to get it up and running eventually as well but in the end wound up just running stock rom on this device as I was getting these weird "screen shatter" type glitches on bootup and so it wasnt really worth the hassle lol. Does rooting really even provide that much of a benefit for this device?
Click to expand...
Click to collapse
Why in the world would you go back to stock just because of these "screen glitches" when booting up? They are gone after Boot and don't cause any issues .... Also this might be caused by you being on an old (or newer but it's rather unlikely as I fixed this "issue" for newer ones) firmware (bootloader matters)
Stock is laggy and bloated while lineage is not.
Edit: Btw, which model and firmware are you on?
If it's P615 with BTK2 firmware I might need to update dtbo sources again and this "issue" will be gone
Hello,
I tweaked a lot of my Nexus 5 and Oneplus 3T but it's going to be the first time that I'll flash a GSI ROM.
For the moment, I just unlocked the bootloader and read threads during several hours
Odin is ready for a potential flash in a virtual machine (since my laptop is running GNU/Linux).
My current firmware: T500XXU3CVG4
CSC code: EUX
I downloaded the latest firmware via samloader (maybe useless): T500XXS4CVJ1. The 4 .tar.md5 files have been extracted: AP, BL, CSC and HOME_CSC (HOME_CSC is not necessary since I want to wipe my user data). I have no CP file.
The tablet is very slow so I hope that LineageOS 19 (or 18.1?) will help.
I downloaded: lineage-19.1-20221011-UNOFFICIAL-arm64_bgS-vndklite.img.xz (source) to install LOS 19 with GApps.
I have no external sdcard.
How can I flash this GSI build?
Should I install this TWRP version then follow these instructions?
Should I flash SM-T500-GSI-kernel.zip to fix unwanted reboots? Or is it specific to LineageOS 18.1?
Too much things to learn/read/understand since I purchased my Oneplus 3T lol
Any recommendations are welcome!
Thank you in advance for your kind help.
Primokorn said:
Hello,
I tweaked a lot of my Nexus 5 and Oneplus 3T but it's going to be the first time that I'll flash a GSI ROM.
For the moment, I just unlocked the bootloader and read threads during several hours
Odin is ready for a potential flash in a virtual machine (since my laptop is running GNU/Linux).
My current firmware: T500XXU3CVG4
CSC code: EUX
I downloaded the latest firmware via samloader (maybe useless): T500XXS4CVJ1. The 4 .tar.md5 files have been extracted: AP, BL, CSC and HOME_CSC (HOME_CSC is not necessary since I want to wipe my user data). I have no CP file.
The tablet is very slow so I hope that LineageOS 19 (or 18.1?) will help.
I downloaded: lineage-19.1-20221011-UNOFFICIAL-arm64_bgS-vndklite.img.xz (source) to install LOS 19 with GApps.
I have no external sdcard.
How can I flash this GSI build?
Should I install this TWRP version then follow these instructions?
Should I flash SM-T500-GSI-kernel.zip to fix unwanted reboots? Or is it specific to LineageOS 18.1?
Too much things to learn/read/understand since I purchased my Oneplus 3T lol
Any recommendations are welcome!
Thank you in advance for your kind help.
Click to expand...
Click to collapse
Why don't you have an SD card? You are saying your 500 is slow. You are using Odin an not Heimdall, so I'm assuming you aren't a CLI fan that would rather do things with fastboot instead of just flashing with TWRP. SD cards are dirt cheap. I recommend you get one, install TWRP, put the files you want to flash in it and flash with TWRP. Then you can move all of your data, such as movies, photos, music and downloads to the SD card and not lose them every time you need to wipe for a clean upgrade. This will also help speed up the tablet by increasing the available internal storage.
lewmur said:
Why don't you have an SD card? You are saying your 500 is slow. You are using Odin an not Heimdall, so I'm assuming you aren't a CLI fan that would rather do things with fastboot instead of just flashing with TWRP. SD cards are dirt cheap. I recommend you get one, install TWRP, put the files you want to flash in it and flash with TWRP. Then you can move all of your data, such as movies, photos, music and downloads to the SD card and not lose them every time you need to wipe for a clean upgrade. This will also help speed up the tablet by increasing the available internal storage.
Click to expand...
Click to collapse
Why? Because I don't need it I have 2 phones so this tablet is used to have a bigger screen when searching stuff on the web with my wife or when cooking.
Actually I like CLI tools but I found few information about Heimdall to flash properly and a hard brick is not far away if I don't flash the good partitions.
Odin is used by many people and I have never touched a "modern" device with A/B partitions, GSI builds,... so...
I don't care wiping the data since I quickly backup/restore them through adb pull/push.
I have few documents on the tablet so moving files to an external storage wouldn't change anything. By the way I'm not convinced that moving pictures and movies to the external sd card would help.
Can I do what I said in the original post? Can I follow the instructions in the mentioned post? Is there a special kernel to flash for LineageOS 19?
Thanks for your support.
If other GNU/Linux users read this thread, here is how to get a .img from the .img.xz downloaded from Andy Yan's personal builds.
Sass:
sudo apt install xz-utils
unxz the_gsi_build.img.xz
Primokorn said:
Why? Because I don't need it I have 2 phones so this tablet is used to have a bigger screen when searching stuff on the web with my wife or when cooking.
Actually I like CLI tools but I found few information about Heimdall to flash properly and a hard brick is not far away if I don't flash the good partitions.
Odin is used by many people and I have never touched a "modern" device with A/B partitions, GSI builds,... so...
I don't care wiping the data since I quickly backup/restore them through adb pull/push.
I have few documents on the tablet so moving files to an external storage wouldn't change anything. By the way I'm not convinced that moving pictures and movies to the external sd card would help.
Can I do what I said in the original post? Can I follow the instructions in the mentioned post? Is there a special kernel to flash for LineageOS 19?
Thanks for your support.
If other GNU/Linux users read this thread, here is how to get a .img from the .img.xz downloaded from Andy Yan's personal builds.
Sass:
sudo apt install xz-utils
unxz the_gsi_build.img.xz
Click to expand...
Click to collapse
To each his own. No, you don't NEED an SD card. I just feel they are so cheap that if I'm going to spend the time rooting and installing custom ROMs, which I've been doing with Samsung tablets for close to a decade, then why not add an SD card to make things a little easier. In all that time, in the dozens of installs and upgrades, the closest I've come to a hard brick is when I unintentionally flashed an AP without flashing the BL on a T510. The tablet would still boot, but only to the system. Couldn't get in recovery or download no matter what I tried. But at least the tablet was still usable. And, come to think of it, in all that time here in XDA, I've never heard of anyone else hard bricking a Samsung tablet by flashing. Sure, can't count the number of bootloop messages, and even the occasional time when it was necessary to let the tablets battery run down, but never a true hard brick that wasn't due to hardware failure.
lewmur said:
To each his own. No, you don't NEED an SD card. I just feel they are so cheap that if I'm going to spend the time rooting and installing custom ROMs, which I've been doing with Samsung tablets for close to a decade, then why not add an SD card to make things a little easier. In all that time, in the dozens of installs and upgrades, the closest I've come to a hard brick is when I unintentionally flashed an AP without flashing the BL on a T510. The tablet would still boot, but only to the system. Couldn't get in recovery or download no matter what I tried. But at least the tablet was still usable. And, come to think of it, in all that time here in XDA, I've never heard of anyone else hard bricking a Samsung tablet by flashing. Sure, can't count the number of bootloop messages, and even the occasional time when it was necessary to let the tablets battery run down, but never a true hard brick that wasn't due to hardware failure.
Click to expand...
Click to collapse
OK. I'll try the above instructions to install the GSI build from the fastboot mode of TWRP.