Related
to all the developers and well wishers out there. i'm actually excited to let you all know that i've just hard bricked my phone. custom roms like cm12, euphoria, resurrection remix were working fine when i actually wanted to flash MIUI v6 to my yureka.
the flash went good but the MIUI wouldn't stop restarting in every 30 seconds after being flash.. tried reverting to euphoria rom. and my phone wouldn't allow any other roms to be flashed unless its a MIUI v6 again.. -_-
i was actually tired of it so went through a procedure to factory restore the stock cm rom and went through the processes of this ****ty link...
http://www.thetechnotriad.com/393/ho...ick-yu-yureka/
and now my phone wont even fastboot. windows wouldn't detect it by any means. and i'm totally screwed.
i've been recently looking around this http://forum.xda-developers.com/yure...ode-k-t3068040 thread from xda itself by tirta.agung for a long time. no luck because he mentioned that the procedure would only work provided that windows could minimum detect my yureka as QHUSB_BULK in device manager.
HELP ME OUT PEEPS... is there any way of giving my YU life back?
ADVICES AND THOUGHTS ARE HIGHLY APPRECIATED...
P.S the YU support told me to download their official rom zip from a link and copy it to internal storage and flash and bla bla bla -_- do they even care to understand my problem properly whilst i've clearly mentioned that MY PHONE WOULDN'T FASTBOOT!!! -_-
same problem here bro
Pragun.Joshi said:
to all the developers and well wishers out there. i'm actually excited to let you all know that i've just hard bricked my phone. custom roms like cm12, euphoria, resurrection remix were working fine when i actually wanted to flash MIUI v6 to my yureka.
the flash went good but the MIUI wouldn't stop restarting in every 30 seconds after being flash.. tried reverting to euphoria rom. and my phone wouldn't allow any other roms to be flashed unless its a MIUI v6 again.. -_-
i was actually tired of it so went through a procedure to factory restore the stock cm rom and went through the processes of this ****ty link...
http://www.thetechnotriad.com/393/ho...ick-yu-yureka/
and now my phone wont even fastboot. windows wouldn't detect it by any means. and i'm totally screwed.
i've been recently looking around this http://forum.xda-developers.com/yure...ode-k-t3068040 thread from xda itself by tirta.agung for a long time. no luck because he mentioned that the procedure would only work provided that windows could minimum detect my yureka as QHUSB_BULK in device manager.
HELP ME OUT PEEPS... is there any way of giving my YU life back?
ADVICES AND THOUGHTS ARE HIGHLY APPRECIATED...
P.S the YU support told me to download their official rom zip from a link and copy it to internal storage and flash and bla bla bla -_- do they even care to understand my problem properly whilst i've clearly mentioned that MY PHONE WOULDN'T FASTBOOT!!! -_-
Click to expand...
Click to collapse
same my phone also bricked what did you do next
Pragun.Joshi said:
to all the developers and well wishers out there. i'm actually excited to let you all know that i've just hard bricked my phone. custom roms like cm12, euphoria, resurrection remix were working fine when i actually wanted to flash MIUI v6 to my yureka.
the flash went good but the MIUI wouldn't stop restarting in every 30 seconds after being flash.. tried reverting to euphoria rom. and my phone wouldn't allow any other roms to be flashed unless its a MIUI v6 again.. -_-
i was actually tired of it so went through a procedure to factory restore the stock cm rom and went through the processes of this ****ty link...
http://www.thetechnotriad.com/393/ho...ick-yu-yureka/
and now my phone wont even fastboot. windows wouldn't detect it by any means. and i'm totally screwed.
i've been recently looking around this http://forum.xda-developers.com/yure...ode-k-t3068040 thread from xda itself by tirta.agung for a long time. no luck because he mentioned that the procedure would only work provided that windows could minimum detect my yureka as QHUSB_BULK in device manager.
HELP ME OUT PEEPS... is there any way of giving my YU life back?
ADVICES AND THOUGHTS ARE HIGHLY APPRECIATED...
P.S the YU support told me to download their official rom zip from a link and copy it to internal storage and flash and bla bla bla -_- do they even care to understand my problem properly whilst i've clearly mentioned that MY PHONE WOULDN'T FASTBOOT!!! -_-
Click to expand...
Click to collapse
did u finded a solution ?
i have always been in the background on this site, but i have using y'all since i had a galaxy s2, note 3, vivo 5r and a few others.
I have boot and root on my phone (h910) and I'm trying to flash a few roms, but i haven't been successful. I looked at the lineage roms which seem to be the base for a handful, but the file size that i see are only like 435ish MB?? Then i tried the mega rom (4.0) because it has what appeared to be a full file, but it crashes and gives me a green screen on boot. I'm waiting for the super rom to come back since it seems like it will have the most up to date files and it has a large following.
Is there something i am missing on the small files? i cant seem to find a rom or a lineage rom that's a gig or 2 in size..
I recently did all the unlocking this past weekend, so whatever the latest links are for that stuff is what i used.
twrp 3.2.1-1 (think that's it)
h91010r
nrd90m
super su v2.82
stonerphoner said:
i have always been in the background on this site, but i have using y'all since i had a galaxy s2, note 3, vivo 5r and a few others.
I have boot and root on my phone (h910) and I'm trying to flash a few roms, but i haven't been successful. I looked at the lineage roms which seem to be the base for a handful, but the file size that i see are only like 435ish MB?? Then i tried the mega rom (4.0) because it has what appeared to be a full file, but it crashes and gives me a green screen on boot. I'm waiting for the super rom to come back since it seems like it will have the most up to date files and it has a large following.
Is there something i am missing on the small files? i cant seem to find a rom or a lineage rom that's a gig or 2 in size..
I recently did all the unlocking this past weekend, so whatever the latest links are for that stuff is what i used.
twrp 3.2.1-1 (think that's it)
h91010r
nrd90m
super su v2.82
Click to expand...
Click to collapse
Sounds like corrupt downloads, try a different browser or dl them on a pc
Sent from my LG-H910 using XDA Labs
stonerphoner said:
i have always been in the background on this site, but i have using y'all since i had a galaxy s2, note 3, vivo 5r and a few others.
I have boot and root on my phone (h910) and I'm trying to flash a few roms, but i haven't been successful. I looked at the lineage roms which seem to be the base for a handful, but the file size that i see are only like 435ish MB?? Then i tried the mega rom (4.0) because it has what appeared to be a full file, but it crashes and gives me a green screen on boot. I'm waiting for the super rom to come back since it seems like it will have the most up to date files and it has a large following.
Is there something i am missing on the small files? i cant seem to find a rom or a lineage rom that's a gig or 2 in size..
I recently did all the unlocking this past weekend, so whatever the latest links are for that stuff is what i used.
twrp 3.2.1-1 (think that's it)
h91010r
nrd90m
super su v2.82
Click to expand...
Click to collapse
Stock based ROMs will be around 2gb in size. Those need to have everything included (system, kernel, boot, vendor, recovery, efs etc partitions) while aosp ROMs like lineage are around 500mb. Those don't need to have all of lgs other crap.
droidrzr1610 said:
Stock based ROMs will be around 2gb in size. Those need to have everything included (system, kernel, boot, vendor, recovery, efs etc partitions) while aosp ROMs like lineage are around 500mb. Those don't need to have all of lgs other crap.
Click to expand...
Click to collapse
that is good to hear..
4**MB is the actual rom and all the guts it needs to run then the rest is just "fluff" wow!?! Just want to double check I'm hearing that correctly
stonerphoner said:
that is good to hear..
4**MB is the actual rom and all the guts it needs to run then the rest is just "fluff" wow!?! Just want to double check I'm hearing that correctly
Click to expand...
Click to collapse
You are indeed hearing that correctly. Aosp ROMs don't touch the bootloader, vendor firmware and other LG firmware. They simply replace your lg H910R system with aosp. Stock KDZs are upwards of 2gb in size and because of how stock based ROMs are built they need to function essentially like a kdz - updating all lg specific firmware as well to make sure they are all compatible with the newly installed system.
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an extended battery, and microSD combined with a custom ROM, this phone has the potential to be glorious.
Here’s what I did:
• Start with a running stock 10u phone. Did OEM unlocking. Did bootloader unlocking.
• Used LGUP to get it to 10p.
• Booted up FWUL. Ran the step 1 bash script. TWRP is installed.
• Instead of running the step 2 script, from inside of TWRP, I flash SuperSU and phoenix’s h918 build of TWRP.
At this point I have TWRP on two partitions—3.2.2 on recovery and 3.2.1-3 on laf. Running stock 10p + root is now working great. No issues.
Every time I flash lineage (with optional gapps + su), I tell TWRP to reboot. It consistently causes the phone to have the blinking backlight where it flashes on and off every 1 – 2 seconds. The LG logo appears, and then you're faced with the blackness. Think of it as an all black screen turning on and off. To recover from this, I pull the battery, hit the volume up button + USB cable to boot into TWRP, flash a 10u flashable zip, and then repeat from square one.
Things I have tried:
• I have tried flashing Lineage on the TWRP on recovery and the TWRP on laf to see if it would make a difference. Same blinking black screen.
• Before installing Lineage, I went into format and typed ‘yes’ to remove decryption. I installed Lineage. Hello blinking black screen.
• Under ‘advanced wipe’, I tried clearing everything onboard (Dalvik / ART Cache, System, Data, Internal Storage, and Cache). I went to installing Lineage. Hello black blinking screen.
• One guide suggested hitting ‘advanced wipe’ and to clear the /data and /cache partitions before installing. No difference. Hello blinkyness.
• I did the general wipe before installing Lineage. No change.
• I tried just installing Lineage images (tried different build dates) with no gapps or su to reduce the chance of any complications.
If I can get this phone working with Lineage with my triple capacity battery, tacos for everyone.
I don't use Lineage, so I am not 100% on this, but you didn't say you flashed a kernel. I am fairly certain that Lineage will not work with the stock kernel.
If you did flash a kernel, what kernel did you flash?
-- Brian
runningnak3d said:
I don't use Lineage, so I am not 100% on this, but you didn't say you flashed a kernel. I am fairly certain that Lineage will not work with the stock kernel.
If you did flash a kernel, what kernel did you flash?
-- Brian
Click to expand...
Click to collapse
I believe the lineage builds include it's own kernel
Sent from my LG-H910 using XDA Labs
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
runningnak3d said:
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
Click to expand...
Click to collapse
You're good, I don't use Lineage due to it's deficiencies, I just read up on it
Sent from my LG-H910 using XDA Labs
michaeljh9 said:
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an extended battery, and microSD combined with a custom ROM, this phone has the potential to be glorious.
Here’s what I did:
• Start with a running stock 10u phone. Did OEM unlocking. Did bootloader unlocking.
• Used LGUP to get it to 10p.
• Booted up FWUL. Ran the step 1 bash script. TWRP is installed.
• Instead of running the step 2 script, from inside of TWRP, I flash SuperSU and phoenix’s h918 build of TWRP.
Click to expand...
Click to collapse
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
lineage-14.1-20180721-UNOFFICIAL-h918.zip.md5
When lineage 15.1 becomes official the h918 builds will be aimed at post10p. x86cpu is currently doing unofficial builds for both.
Phoenix591 said:
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
Click to expand...
Click to collapse
I looked on xda lineage threads, h918 threads, v20 subreddit, lineage subreddit, etc. You're a hero for sharing that. I couldn't find any posts about that and it was becoming frustratingly insane. It explains everything. I have been successful in the past getting h918 official lineage running but you're absolutely correct in that it was using dirtycow on 10i. I'm currently working on getting this 10p working. After hearing the news, I am looking forward to 15.1's official release.
Give me a few minutes. I'm flashing your image.
michaeljh9 said:
I looked on xda lineage threads, h918 threads, v20 subreddit, lineage subreddit, etc. You're a hero for sharing that. I couldn't find any posts about that and it was becoming frustratingly insane. It explains everything. I have been successful in the past getting h918 official lineage running but you're absolutely correct in that it was using dirtycow on 10i. I'm currently working on getting this 10p working. After hearing the news, I am looking forward to 15.1's official release.
Give me a few minutes. I'm flashing your image.
Click to expand...
Click to collapse
Info is buried deep in one or more of the 3 lineage threads. Been watching them closely for ages.
Phoenix591 said:
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
Click to expand...
Click to collapse
I tried flashing it. When it boots up, it stays stuck at the LG logo. If it makes a difference, I did a normal standard wipe inside TWRP.
Phoenix591 said:
x86cpu is currently doing unofficial builds for both.
Click to expand...
Click to collapse
I went ahead and tried x86cpu's builds. While stock was installed, I booted into TWRP.
I flashed official-to-UNOFFICIAL.zip. Rebooted into the stock ROM as per the instructions.
Rebooted into TWRP. I flashed lineage-15.1-20180726-UNOFFICIAL-h918-10p.zip
I flashed 15.1 arm 64 pico gapps. I flashed the su add on. Hit reboot.
Son-of-a.... the Lineage boot animation started.....
I was greeted with the Lineage welcome wizard. This phone has never gotten this far. Words cannot express my relief and excitement. After it couldn't connect to WiFi, I fixed the 00:00:00:00:00:00 Mac address issue and that was straightforward.
I am one happy camper thanks to you guys.
To sum up my issue, it appears Lineage ROMs (and others?) need to be treated differently because the phone is configured to be ARB 1. *le sigh*
michaeljh9 said:
I tried flashing it. When it boots up, it stays stuck at the LG logo. If it makes a difference, I did a normal standard wipe inside TWRP.
I went ahead and tried x86cpu's builds. While stock was installed, I booted into TWRP.
I flashed official-to-UNOFFICIAL.zip. Rebooted into the stock ROM as per the instructions.
Rebooted into TWRP. I flashed lineage-15.1-20180726-UNOFFICIAL-h918-10p.zip
I flashed 15.1 arm 64 pico gapps. I flashed the su add on. Hit reboot.
Son-of-a.... the Lineage boot animation started.....
I was greeted with the Lineage welcome wizard. This phone has never gotten this far. Words cannot express my relief and excitement. After it couldn't connect to WiFi, I fixed the 00:00:00:00:00:00 Mac address issue and that was straightforward.
I am one happy camper thanks to you guys.
To sum up my issue, it appears Lineage ROMs (and others?) need to be treated differently because the phone is configured to be ARB 1. *le sigh*
Click to expand...
Click to collapse
yeah guess I forgot to mention that the first boot of lineage 14 after wiping takes 15-35 minutes. Usually not stuck on the lg logo.. ill take a look.
runningnak3d said:
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
Click to expand...
Click to collapse
Oh God dude!!!!!!! If and when you get involved in LOS, I will definitely flash that build.
You are by far my favorite Dev. That's why I'll always buy the same device you get. I know it would be WELL supported!
Sent from my LG-H918 using XDA Labs
so i was trying to flash CherishOS so i followed the instruction and found some problem but i was managed to solve the problem. FYI, the rom gave the link to the custom recovery which is the PixelExperience one, since i'm coming from the stock latest rom so i flashed that. until i done everything and boot to system, and it just keeps returned to the bootloader no matter which option i choose (boot to system & recovery), but luckily the device is still detected in my computer
What i've tried :
- flash recovery (PixelExperience & TWRP)
- Followed this instruction
but none of that is working, one thing i found out while doing the 2nd method is that it shows some errors like "flashing is not allowed for critical partition" and "partition not found".
I have no clue what to do, i've tried whatever solution i could find and none are working. please help, thanks
edit:
I also tried the "fastboot flashing unlock_critical" and tried to reboot into fastbootd but failed and the fastboot shows all command list
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
xtcislove said:
I guess you are referencing to CherishOS on xda.
[ROM][13.0]CherishOS-4.2[UNOFFICIAL][Oneplus 8 Pro]
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS. * Your warranty is now void. * I am not responsible for anything that may happen to your phone by installing...
forum.xda-developers.com
If i click on the link to download the recovery there is nothing about pixelexperience. So i guess you saw something about pixelexperience in the recovery itself. Thats not a problem anyway. You could use lineage recovery too. As long as the recovery is made for a12 thats not a problem as far as i know.
Its not written in the Cherish OS thread but in all other roms you have to be on the latest OOS11 on BOTH slots. Did you do this beforehand?
The easiest thing now is to use MSM Tool and go back to a locked oos phone.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
If you like to install a custom rom again, make sure to update both slots before.
Install LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org
I tried many custom roms or all i think. And tbh the best experience i had for now was OOS11 and the Open Beta 1 OOS12.
OxygenOS 12 [OB1] [Oneplus 8 Pro] - First Open Beta of Global OOS12
*Will update thread as rn im at work* The first Open Beta for Global OOS has been release really quietly (no announcemment so far) but here is the link from where i download it...
forum.xda-developers.com
Good luck.
Click to expand...
Click to collapse
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
B1nz said:
yoo it works, thanks a lot man. hope you know how relieved i am
yeah i know it's not the problem, but it was the first time i know this recovery in like few years of modding my phone
also i finnaly able to flash the the custom rom, thanks!
I totally agree tho, the oos for me is the best stock rom, i tried the beta 1 tho, but it just leans towards to the color os since oppo is the parent company of oneplus. it just feels more heavy and too many change from the stock android. that's why i decided to flash custom rom
again, thank you so much! have a great day!
Click to expand...
Click to collapse
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
flo musti said:
hi.... what exactly have you done to bring it back ??? I'm in the same situation, just fastboot.... thanks
Click to expand...
Click to collapse
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
B1nz said:
i just used the unbrick tool from the link above, and my phone is back to complete normal. hope it also works for you!
Click to expand...
Click to collapse
already tried but the phone is not going in Qualcomm EDL mode...
flo musti said:
already tried but the phone is not going in Qualcomm EDL mode...
Click to expand...
Click to collapse
in my experience, my phone is just showing nothing it's like the screen is off. i realized that my phone is in EDL mode is it's detected in my computer as qualcomm something.., when it shows like that that means you haven't installed the qualcomm driver. after that the name will change to "more normal" name. and then you can proceed into the tools
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.