Related
Hello!
I have rooted my Samsung Galaxy Tab 7.7 successfully, then I installed Mobile ODIN Pro 3.4.5 and tried to flash clockworkmod recovery using the kernel file from wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide (specifically, "Technomancer's Kernel with the ClockworkMod Recovery"). The device rebooted and started making clicking noises (while stuck at "Samsung Galaxy Tab"). I waited for some time, rebooted it again... Now it doesn't make clicking noises, but still stuck.
Have I superbricked it *again*? I know that it would brick when made full wipe, but Mobile ODIN isn't supposed to wipe while flashing a kernel...
Please help me. Just today I got it from service centre, and I really don't want to wait another two weeks.
Thanks in advance
UPDATE 1: Wow, I was able to flash clockworkmod recovery through Heimdall 1.3.1 (something that I wasn’t able to do previously). Running memory check… maybe it is going to be fine after all [crosses fingers]. For all those who want to flash clockworkmod recovery on their Galaxy Tabs: don’t use Mobile ODIN, don’t use Heimdall 1.3.2 and flash the latest recovery (v6).
UPDATE 2: No errors! Now I am going to try to install Paranoid Android 2.23 (no official CM9 builds for P6800 yet).
Artyom.Kazak said:
Hello!
I have rooted my Samsung Galaxy Tab 7.7 successfully, then I installed Mobile ODIN Pro 3.4.5 and tried to flash clockworkmod recovery using the kernel file from wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide (specifically, "Technomancer's Kernel with the ClockworkMod Recovery"). The device rebooted and started making clicking noises (while stuck at "Samsung Galaxy Tab"). I waited for some time, rebooted it again... Now it doesn't make clicking noises, but still stuck.
Have I superbricked it *again*? I know that it would brick when made full wipe, but Mobile ODIN isn't supposed to wipe while flashing a kernel...
Please help me. Just today I got it from service centre, and I really don't want to wait another two weeks.
Thanks in advance
UPDATE 1: Wow, I was able to flash clockworkmod recovery through Heimdall 1.3.1 (something that I wasn’t able to do previously). Running memory check… maybe it is going to be fine after all [crosses fingers]. For all those who want to flash clockworkmod recovery on their Galaxy Tabs: don’t use Mobile ODIN, don’t use Heimdall 1.3.2 and flash the latest recovery (v6).
UPDATE 2: No errors! Now I am going to try to install Paranoid Android 2.23 (no official CM9 builds for P6800 yet).
Click to expand...
Click to collapse
You realize you flashed a recovery for a completely different device and you are lucky to get your tablet running again, don't you? The "Galaxy Tab" is a 2010 device, one of the first Android tablets; it came with Froyo. Ours is over a year more recent, with a much improved architecture. The "Tab" was an overgrown Galaxy S; ours is an overgrown Galaxy Note.
Check the development board (for the 7.7 ). You should use either the latest CWM 6.x.x from locerra or TWRP, you will find them there. Also, you'll see that there are CM9/10 ports to our device (by locerra), in addition to ParanoidAndroid (ported by Androguide.fr).
Steve_max said:
You realize you flashed a recovery for a completely different device and you are lucky to get your tablet running again, don't you? The "Galaxy Tab" is a 2010 device, one of the first Android tablets; it came with Froyo. Ours is over a year more recent, with a much improved architecture. The "Tab" was an overgrown Galaxy S; ours is an overgrown Galaxy Note.
Check the development board (for the 7.7 ). You should use either the latest CWM 6.x.x from locerra or TWRP, you will find them there. Also, you'll see that there are CM9/10 ports to our device (by locerra), in addition to ParanoidAndroid (ported by Androguide.fr).
Click to expand...
Click to collapse
Ouch.
Now when you said it… Guess I’m very lucky. Thanks a lot! I swear I will pay more attention to, er, everything in the future
Artyom.Kazak said:
Ouch.
Now when you said it… Guess I’m very lucky. Thanks a lot! I swear I will pay more attention to, er, everything in the future
Click to expand...
Click to collapse
No worries, **** happens. Take care of the device (we are vulnerable to a pretty nasty bug, if you use the older or touch CWM). And as usual, #BlameSamsung for the confusing nomenclature...
My wife has finally decided she'd like me to put a custom ROM on her TF101. I have experience (both good and bad) on my phones and tablets, but she doesn't want hers "messed up." So, I'm a lot less comfortable taking chances with her device than I am with mine. She still loves her TF101 and uses it daily and I don't want to mess it up. Her TF101 is still stock, not rooted, and has the last available ASUS update on it (IML74K.US_epad-9.2.1.27-20120615).
Initially my research indicated this was going to be the quickest and easiest Root/Recovery process I've ever gone though! Download Razorclaw to the device, run it to get root. Download Recovery Installer to the device, run it to get CWM. Easy peasy mac and cheesy. But, Razorclaw seems to be gone. The link to the tool gives a Page Not Found error. Another link on that site outlines a complicated process with a bunch of adb shell commands that made me a little uneasy. Recovery Installer likewise is no longer available at the link given in the first post of that thread. There's a link to a mirror location later in the thread, but if it's not available from the person who made it, then I have to worry. I've also now realized that her firmware version is not compatible with those tools to begin with!
So with my reluctance to upset my wife, some outdated information floating around in the threads, I just wanted to confirm my current plan was the proper way to go.
Use the PERI-0.42 tool to root and install TWRP. I wish I could find a video or screen shots of the process so I can know what to expect. (Or should I use the "1-Click Transformer Root" tool? I'm thinking not as TWRP would be preferable to Rogue Recovery?)
Nandroid backup from TWRP
Flash ROM following ROM's instructions
That about it?
As for which ROM, Root-Box looks interesting, but it says the camera doesn't work and my wife uses the camera (and the CamScanner app) frequently, so that's a no go. So, I was thinking about Paranoid-Android or No-name CM10?
First, Razorclaw only works on a very few firmwares, and the .27 is not one of them.
I wrote a guide on rooting the TF here: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This uses EasyFlasher and APX mode. It does install an older TWRP, but if you replace the twrp.SOS file in the EasyFlasher "tools" folder with the latest official 2.3.2.3 file found here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob (rename to twrp.SOS and replace the file) then EasyFlasher will flash the 2.3.2.3. EasyFlasher will show the old version in the menu drop down, however it will flash the newer version. If you want TWRP 2.5.0.0 you will need to get it from the thread in the development section.
I have used Peri 0.4 in the past, and it is very easy to follow the prompts. I have not made a tutorial or video of it, but as I said it is pretty straight forward.
As far as the ROM to flash, I am using Domination right now and have flashed the RootBox one as well. At the current time the keyboard dock has little support for both of these ROMs. Many users have had issues with SOD and RR on the CM10.1 no-name. My favorite for stability and features is still TeamEOS 4. It has full dock support and is very very fast and stable.
I am actually looking to restore my EOS 4 Nandroid later today.
Easyflasher is about as no-brainer as you can get, I would recommend using that to install TWRP recovery (note: and update to a newer version as per above poster).
http://forum.xda-developers.com/showthread.php?t=1688012
I've used it with three different PC's and three different TF101's without any issues, and I've used it to revert to stock a couple times on mine.
As far as ROMs are concerned, I have had the best luck in term of a happy blend of fully-baked (everything works)/stability/compatibility/features/speed-smoothness with the EOS 4 ROMS and KAT kernals, though I have as of yet only given the latest PA ROMs (with halo) a quick look. I am admittedly biased on that front since I switched to EOS 3.0 long ago, but I also haven't heard of any complaints from my folks or a friend who are running slightly older versions of the EOS 4 ROM.
Some people say they aren't pleased with smoothness with the stock launcher in EOS (I run Nova Prime on mine and Nova free version on the other two I've helped "upgrade", seems quite smooth to me). I don't know if that is a perception issue, a difference in hardware, or maybe installed apps/widgets. Or if it is still even an issue.
The only issues I have had on mine (SOD's/RR's) in many months was with one short-lived version of the Kat Kernal, which was fixed asap. For me, it's just as stable as the last official ASUS ICS update, and way way more stable the the preceding one.
By all means, give them all a shot, but I have never really had a problem with using EOS as a daily driver.
Thank you, Gentlemen! That's just the sort of help and information I needed. I don't know how I overlooked EasyFlasher in my research.
I had the same firmware - I used PERI to root and went with EOS nightlies v118 and KatKernel v103. Best decision I ever made. Stable, fast and enough features to sink a battleship.
I overlock to 1400mhz using smartassV2 governor. IO scheduler is set to 'sio' (settings->EOS control center->syste,->Performance settings). Since then its been a dream to use, no lag, no waiting. I stuck the dolphin browser on for good measure. Since all that was done, its smooth, fast and really enjoyable. To think a week ago I was ready to sell it and get something new, no need to do that now!
good luck!
About a month ago I had what I thought was a hardware issue with my microSD card reader and started a thread in this subforum about that. Someone suggested I try flashing a custom ROM before I try replacing hardware. Long story short I am now running TeamEOS + Kat kernel and everything is great. Tablet is faster and more stable than it ever was on stock and its nice to be running JellyBean. Only warning, you'll need TWRP not CWM to flash ROMs using Android 4.1+ but otherwise there really isn't too much to worry over.
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
HeathicusF said:
I got my wife set up with the Team EOS 4 ROM last night. I ended up having to use PERI instead of EasyFlasher. I couldn't seem to get the tablet into APX mode. Vol UP + Power either did absolutely nothing, or the PC just couldn't "see" the tablet in APX mode. It could see it just fine upon regular boot, and I got the "new device" ding as soon as it started booting, but nothing when trying to enter APX. Vol DOWN + Power, then Vol UP to enter RCK mode brought up the "dead" android with the red triangle for a few seconds, then it rebooted.
But, PERI worked like a charm to root and install TWRP. Then I flashed TeamEOS 4, and she went to work setting it back up.
Thanks for the help!!
Click to expand...
Click to collapse
Awesome!
Check out my FAQ guide on EOS 4 to help explain many questions you may have, and how to set it up the way you (or your wife) likes.
let us know how she gets on with it ,it really is a great rom my tab has never been so quick i use nova launcher and dolphin overclock it in setting to 1400 i have mine on 1504 and still see good battery life ,,,,,,install goo manager from play for updates to rom and also pimp my rom is good for a few tweaks here and there ,,but first when its all set up and working good MAKE A BACK UP i always make back ups as i go along i have 2 all the time only takes 320 seconds ,,,,,enjoy
Sent from my Transformer TF101 using xda premium
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
HeathicusF said:
She told me last night that she really liked the new ROM, so I think we have a winner. I like it too and wish it was available for the TF700 I recently got!
Click to expand...
Click to collapse
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Thing O Doom said:
[AOSPA-4.2.2][June 13,2013(build #4)]ParanoidAndroid-3.6 | HALO IS HERE
[KERNEL][CM10.1 PA Liquid]bryce[overclock, gov, sched][VER 4.0][04/05]
Click to expand...
Click to collapse
I tried that ParanoidAndroid and it wouldn't get past the boot animation. I didn't try that Kernel, or an older non-Halo'd version of PA.
Thing O Doom said:
Glad it was a smooth process. The TWRP install via peri worked? Did you use 2.5 or 2.3?
Click to expand...
Click to collapse
Yep, the TWRP install via Peri worked flawlessly. It was vesion 2.5 of TWRP (Peri v0.42)
Hi Everyone,
I come to you for a bit of help. I have spent a long time trying to fix this and come for help from you guys.
So I got a little bored with standard Samsung Android on my Note 2 (GT-N7100). Having used Cyanogen before, I decided to try it on the note.
I rooted the device and installed CWM on it no problems. I then loaded CM from a micro usb.
On reboot it just gets what i'd call the "Spinning blue screen of death" where it just has the big blue circle going round until it runs out of battery. After some research I used CWM to clean out the caches etc but it still didn't appear to work. This was using the stable version for my Note 2. I then went on to try other versions and got the same issues. Alas, trying to do a restore didn't work either, as it didn't seem to have all the files.
At this point I am happy to go back to stock Android or indeed CM. I'd just like a phone that works!
My device details:
Model GT-N7100
SSN: -N7100GSMH
Network Provider Virgin UK
Any help appreciated.
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021
IMO you should contact developers of Bliss OS to get your issue fixed.
Recovering Spaghetti said:
Hi everyone,
This is driving me mad. I've been trying to install a bunch of different ROMS on my Samsung Galaxy A10 and while it seemingly installs just fine, when I press "reboot system" it gets into a perpetular loop. Am I doing something wrong here?
Click to expand...
Click to collapse
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
jwoegerbauer said:
Bliss OS Rom v14 w/ Android 11 for Samsung A10 Arm64 ( Stable Unofficial ) released 2021View attachment 5799499
IMO you should contact developers of Bliss OS to get your issue fixed.
Click to expand...
Click to collapse
Hi,
The thing is I also tried DotOS & OctaviOS & the issue perseveres
vdun1188 said:
I don't have experience with Samsung phones in particular, but with Moto phones I've used the online recovery tool to restore the phone back to stock and start over. Not sure there is anything similar with Samsung? Good luck!
Click to expand...
Click to collapse
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Recovering Spaghetti said:
Hi, I believe there is, but the thing is that this is like my third ROM on this phone (Decided to install a new one after my bluetooth headphones refused to connect with my phone while being able to connect just fine to literally everything else) & this is the first time I'm having issues like that. Before, when I managed to install the ROM then it was smooth sailing since hence why I'm asking for help. I've spent a few hours trying different ROMS already.
Click to expand...
Click to collapse
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Recovering Spaghetti said:
Since it has worked fine up to now I'd like to first exhaust all the concievable solutions before going for the nuclear option of stock firmware.
Click to expand...
Click to collapse
Understood. For some reason that is beyond my comprehension, it seems it is sometimes suggested to install stock and then a different custom ROM. Again, I don't know what it is actually supposed to do, as I've stayed with LineageOS to keep it simple. I'm not saying to stay with stock, just use it to get phone back to default, then start from there.
nuclear option..stock - hahaha )
Gawd Damit, I tried LineageOS too & a bunch of other stuff & it's always the same problem. I'm all out of ideas now.
Please help, Tried every ROM, same result, doesn't boot
Hi, I've got a Samsung Galaxy A10 SM-A105F and I tried installing all kinds of different roms on it and they install just fine but then when i go to boot to system I end up in this hell hole of perpetual booting and restarting. I've been at it...
forum.xda-developers.com