I have a Samsung Galaxy Tab 10.1 (gtp7510) - I have install a OS that wasn't good, the screen is flicking before I boot - only 4GB are available, etc...
I would like to format my tablet and install a fresh new android kitkat, is that possible on my device?
EV2121 said:
I have a Samsung Galaxy Tab 10.1 (gtp7510) - I have install a OS that wasn't good, the screen is flicking before I boot - only 4GB are available, etc...
I would like to format my tablet and install a fresh new android kitkat, is that possible on my device?
Click to expand...
Click to collapse
Twrp latest here better flash it
http://forum.xda-developers.com/showthread.php?t=1833136
Then 4.4 rom from here. Rom is a bit experimental)
http://forum.xda-developers.com/showthread.php?t=2576610
You might wanna take a look here too...
http://forum.xda-developers.com/showthread.php?t=2668337
Also by kasper_h. Thou in beta status it works like a charm.
Related
Hi, this is my first post, so if I am posting in the wrong section, please tell me so. I have a Galaxy grand Duos, it had Android 4.1.2 (stock) and I wanted to upgrade it to Android KitKat (4.4) so I rooted it and I upgraded first to 4.2.2 using RR (Resurrection ROM) and it worked flawlessly then I used CM 11.0, I flashed CM 11.0 (the ROM) and gapps, but now it just won't boot, it's stuck at the Galaxy Grand Duos logo and it just won't go to the main screen or anything, did I brick it or what?
Yes, when it stucks in manufacturer logo it's because it simply cannot initialize correctly, any system file can cause that, or any rom
djlucask said:
Yes, when it stucks in manufacturer logo it's because it simply cannot initialize correctly, any system file can cause that, or any rom
Click to expand...
Click to collapse
Thanks for the reply, but actually, you added nothing. Obviously, it cannot initialize correctly and I know the ROM was the cause, I just need a fix for it.
Red_Dragon. said:
Thanks for the reply, but actually, you added nothing. Obviously, it cannot initialize correctly and I know the ROM was the cause, I just need a fix for it.
Click to expand...
Click to collapse
Actually I answered your question. But, to fix this you have to re-flash CM, or another rom with CWM...
djlucask said:
Actually I answered your question. But, to fix this you have to re-flash CM, or another rom with CWM...
Click to expand...
Click to collapse
Actually, I re-flashed CM many times, but still no avail. I flashed Resurrection Remix with CWM and then CM 11.0 with CWM also, the same version. Should I've used another version for flashing CM 11.0 as it upgrades to 4.4 unlike the RR which upgrades to 4.2?
Red_Dragon. said:
Hi, this is my first post, so if I am posting in the wrong section, please tell me so. I have a Galaxy grand Duos, it had Android 4.1.2 (stock) and I wanted to upgrade it to Android KitKat (4.4) so I rooted it and I upgraded first to 4.2.2 using RR (Resurrection ROM) and it worked flawlessly then I used CM 11.0, I flashed CM 11.0 (the ROM) and gapps, but now it just won't boot, it's stuck at the Galaxy Grand Duos logo and it just won't go to the main screen or anything, did I brick it or what?
Click to expand...
Click to collapse
do u have a backup then restore
if not reflash stock rom through odin
Hello guys. I have installed the Omni Rom 4.4.4 (2014-10-27) on a Samsung Galaxy Tab 10.1 P7510.
Also, I have the Asus Transformers TF101 in which I have installed KatKiss 4.4.4 #36.
As far as I know, both devices have the same chipset, CPU and GPU.
The thing is that KatKiss performs better than Omni Rom.
Question: Is possible to adapt the KatKiss in order to run on the Samsung Galaxy Tab 10.1?
Thanks!
bishop0102 said:
Hello guys. I have installed the Omni Rom 4.4.4 (2014-10-27) on a Samsung Galaxy Tab 10.1 P7510.
Also, I have the Asus Transformers TF101 in which I have installed KatKiss 4.4.4 #36.
As far as I know, both devices have the same chipset, CPU and GPU.
The thing is that KatKiss performs better than Omni Rom.
Question: Is possible to adapt the KatKiss in order to run on the Samsung Galaxy Tab 10.1?
Thanks!
Click to expand...
Click to collapse
If the devices have the same chip,display resolution,and so on. You could ( possible ) port that rom over to the gtab. There are a ton of porting guides on XDA. Some that only need you to move ( copy/paste ) certain files and such from the port rom to the rom you wish to port. You will also have to change the kernel in the rom to be ported as well as make a few changes to the build prop.
Be careful....You could end up with a new coaster.
Gil81 said:
If the devices have the same chip,display resolution,and so on. You could ( possible ) port that rom over to the gtab. There are a ton of porting guides on XDA. Some that only need you to move ( copy/paste ) certain files and such from the port rom to the rom you wish to port. You will also have to change the kernel in the rom to be ported as well as make a few changes to the build prop.
Be careful....You could end up with a new coaster.
Click to expand...
Click to collapse
I thought that it might be easier. I'm not that good with programming.
Thanks Gil81!
hi everyone,
i am searching a way to dual boot (or triple boot) my galaxy s2 between gingerbread(stock), jelly bean (stock) and nougat (aosp)
i don't want to be dependent from one kernel, simply i want a method similar to dual boot patcher.
i tried this application but i9100 device is not supported.
maybe i can select galaxy S3 i9300 in the configuration of dual boot patcher, but i don't want to risk to brick my loved S2
i don't know... but i really need a way to do this triple boot without depending from a kernel and storing rom files in the user storage (/data or internal storage... or external sd...)
cescof said:
hi everyone,
i am searching a way to dual boot (or triple boot) my galaxy s2 between gingerbread(stock), jelly bean (stock) and nougat (aosp)
i don't want to be dependent from one kernel, simply i want a method similar to dual boot patcher.
i tried this application but i9100 device is not supported.
maybe i can select galaxy S3 i9300 in the configuration of dual boot patcher, but i don't want to risk to brick my loved S2
i don't know... but i really need a way to do this triple boot without depending from a kernel and storing rom files in the user storage (/data or internal storage... or external sd...)
Click to expand...
Click to collapse
Dual boot requires a kernel that supports it like DorimanX kernel, which will never support Nougat (I'm not personally going to update it).
You can dual boot stock jelly bean and lollipop, but that is as far as you can get (marshmallow dual boot support is unknown and most likely is broken).
Dual booting gingerbread and newer android versions is impossible as there is no kernels known for allowing this.
Saber.
Lineage Nougat
LineageOS 14.1 has everything thought of, as far as i understand,but can it be flashed ontop of a stock orange gingerbread ROM? i1900P(withNFS)?
Hello Buddys ,I wanted cyan 10.1, but does not go anymore,i have install Lineage 7.1.1 on my S2,have not installed the gapps, running stable.I would like in the monitor mode, had bcmon, but did not go.I also have the alfa rt3070 and a radio antenna.Would like to use this hardware
Official weekly build?
https://download.lineageos.org/i9100
hayabusa777 said:
Hello Buddys ,I wanted cyan 10.1, but does not go anymore,i have install Lineage 7.1.1 on my S2,have not installed the gapps, running stable.I would like in the monitor mode, had bcmon, but did not go.I also have the alfa rt3070 and a radio antenna.Would like to use this hardware
Click to expand...
Click to collapse
Monitor mode and bcmon doesn't work on lollipop or above roms unfortunately, not sure about kitkat, but it works great in jellybean, it's an app related as it wasn't updated for years.
I recently purchased a Roku Express and want to cast (screen mirror) from a Nook HD+. I have CM14 (Android 7.1.1) installed on the HD+, but when I select Settings>Device>Cast the tablet does not find the Roku device (although it does find my Google Home Mini). I also have a Samsung Tab A 10.1 running OEM Android 7.0 with the same problem (feature?). However, I am able to find and screen mirror using my Samsung S4 mini running CM13 (Android 6.0.1).
I have read that Android dropped native support for miracast from recent releases, which I suspect may be the problem. While the HD+ is a great tablet, it doesn't get a lot of use now that I have the Tab A. So I'm thinking of installing an earlier version of CM to see if this solves the problem. I am using TWRP 3.1.1-0 for recovery purposes.
Here are my questions. Is there any danger or problem when installing an older version of CM over a newer one? If this doesn't solve the problem, will my backup of the current OS reinstall without a problem? Are there reasons why this may not be a good idea? Is there another option to implement screen mirroring?
Thanks!