Related
Hi,
I recently purchased a generic brand Android phone. General specs are; Android 4.1.1, Dual Core 1GHz, RAM 256MB.
I'm brand new to the smartphone thing, and Android 4.1.1 on a generic device isn't helping my experience. Lots of 3rd party apps have been factory installed on it to the point of choking the RAM and making it nearly impossible to run more than 1-2 apps simultaneously.
I need to root this phone, like, badly.
I searched XDA Forums diligently and tried several suggestions, but nothing worked. I searched plenty of other forums too, but haven't received any kind of satisfactory solution.
The saddest thing is, this phone doesn't seem to have a Recovery option. I've pressed and held the Vol - and Power buttons together, nothing. I've pressed both Volume + and - and the Power buttons together, nothing. I've pressed all 3 buttons plus the Menu button, nothing. I even tried begging it. Nothing.
This phone doesn't have any USB drivers, so that I can use an Android SDK and the SuperUser app to root it.
I'm crazed beyond the point of recovery, because I seem to have purchased an Android that can't do anything it's meant to do.
This is the device description on the company's website;
gphonebd.com/index.php?action=product_details&no=114
Some internal hardware and software details;
Phone Name: G'phone
Model Number: D16-Eye
Android Version: 4.1.1
Baseband Version: MTK6517 (Dual Core)
Kernel Version: 2.6.35.7 [email protected] #3
Software Version: G'phone-D16-Eye_D8_V1.2-20130424
Hardware Version: 1.1.0
Please help in finding a solution, anybody! :crying:
Thanks in advance, to whoever responds.....
Have you tried framaroot? I honestly don't think it'll work, but it's worth a shot.
Worse case, it'll tell you none of the exploits work, so you'll have to uninstall.
Sent from my SPH-D710 using xda app-developers app
Zoow said:
Have you tried framaroot? I honestly don't think it'll work, but it's worth a shot.
Worse case, it'll tell you none of the exploits work, so you'll have to uninstall.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply. Since posting my original thread, my phone has now gone on the blink. I connected my phone to my laptop via USB to transfer some photos and BANG! The screen goes white and shuts down. I tried rebooting, but the OS isn't loading anymore. I tried Recovery Mode, but it seems there isn't any recovery software installed in this thing.
I'm desperately searching for a solution to this, now......
sisilk said:
Thanks for your reply. Since posting my original thread, my phone has now gone on the blink. I connected my phone to my laptop via USB to transfer some photos and BANG! The screen goes white and shuts down. I tried rebooting, but the OS isn't loading anymore. I tried Recovery Mode, but it seems there isn't any recovery software installed in this thing.
I'm desperately searching for a solution to this, now......
Click to expand...
Click to collapse
YOu are gonna be hard pressed to find anything, and to be honest your gonna have trouble no matter what you do. Your device doesnt even meet the min requirments to run android. So it will lag and be barely usable.
zelendel said:
YOu are gonna be hard pressed to find anything, and to be honest your gonna have trouble no matter what you do. Your device doesnt even meet the min requirments to run android. So it will lag and be barely usable.
Click to expand...
Click to collapse
Yeah, I know. But believe me, I've seen phones with much lower specs, RAM, Clock speed and so forth, comfortably run Android 2.3.6 (Gingerbread). I guess the manufacturers of this phone shouldn't have put Jelly Bean on a device with these specs. I tried searching on the Forums here if there were minimum hardware requirements to run Jelly Bean, but haven't found anything informative enough.
Can you tell me, if you know, the minimum hardware requirements to run Jelly Bean 4.1.1? It would be a big help and guide for me, because I plan to replace the phone I currently own. I'll have to get it replaced from the dealers first (it's still under the device warranty) and once that's done, I'll put it up for sale. Then, I'll probably hunt around for a better phone. That's why it'd be a big help if you could give me a guide on minimum hardware requirements to run Jelly Bean.
Also, if it's not much trouble, could you tell me which would be better to run, Android 4.1.1 or Windows Phone 8? I mean, if you consider everything, such as prices, device range, apps, usability and durability.
Thanks so much for responding to my questions!
For the most part it is ok but if you search google for the requirments you will see that anything above GB needs a min of 512 mb of ram and then it still lags all over the place.
I am a developer at heart so Android is my choice but with all things considered I would look at windows phone. It is a good set of devices and is very easy to use.
Wayne Tech Nexus
zelendel said:
For the most part it is ok but if you search google for the requirments you will see that anything above GB needs a min of 512 mb of ram and then it still lags all over the place.
I am a developer at heart so Android is my choice but with all things considered I would look at windows phone. It is a good set of devices and is very easy to use.
Wayne Tech Nexus
Click to expand...
Click to collapse
Thanks so much for the reply! I guess for a smartphone noob like me, I'm probably much better off using Windows Phone. Android is way too complicated for me, I guess....
One final question, please. D'you think I should go for a Lumia device or one of those HTC's running Windows Phone 8? Is there one or two that you can recommend? Thanks again!
sisilk said:
Thanks so much for the reply! I guess for a smartphone noob like me, I'm probably much better off using Windows Phone. Android is way too complicated for me, I guess....
One final question, please. D'you think I should go for a Lumia device or one of those HTC's running Windows Phone 8? Is there one or two that you can recommend? Thanks again!
Click to expand...
Click to collapse
I heard the Lumia is a good device but IF i was to get a WP I would get an HTC as they have proven themselves to me over the years. I really cant say which one is better as I have never looked at a WP device.
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
McDastardly said:
Because you can't. Once you take the 4.3 OTA, you're stuck with it.
Click to expand...
Click to collapse
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
What features were taken out? Anything that can be replaced with better apps on the market shouldnt count. In my opinion the new stock task manager makes it worth it.
---------- Post added at 01:17 PM ---------- Previous post was at 01:11 PM ----------
Well if I could go back in time I would have just waited for a custom 4.3 tw rom. But at least I don't feel the need to flash a new rom every day now.
ThePagel said:
What features were taken out?
Click to expand...
Click to collapse
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
galets said:
At this time, my biggest issue is that codes do not work, and i cannot get into hidden menu, so no QPST. I'm on PagePlus, so updating PRL is a manual process, and without putting phone into modem mode I cannot do that.
There are a few other annoying things, such as: can't turn off warning against increasing volume on headphones (i think there's some add-ons which let you do it though)
Click to expand...
Click to collapse
I can understand your annoyance with the hidden menu being gone. But that wasn't a "feature" it was a "hidden menu" after all and with root there are ways to get rid of the volume warning. That bugs the crap out of me as well but not to the point to change it yet.... YET!
galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
Click to expand...
Click to collapse
Nah, Samsung hasn't been overwhelmingly developer friendly for awhile. There's a bit of dislike for them due to Exynos processors.
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step. That's why it was mentioned multiple times to not accept the 4.3 update in case it locked the bootloader.
Samsung hasn't been developer friendly for a long time. Anytime you take an OTA update you can expect it to prevent the use of custom firmware unless a trusted source says it doesn't.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Additionally, it wasn't that sneaky. The phone was intended to have a locked bootloader from the beginning. It was expected that the update would patch the loophole we found from the leaked aboot step.
Click to expand...
Click to collapse
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"
galets said:
I still maintain it's been sneaky. The boot loader was not patched for a long time, you even get an icon which indicates custom firmware. Many folks understood it as if Samsung quietly endorses modding. The S3 has had a reputation of phone friendly for modders. Many purchased this very model specifically because they intended to mod it. Also don't forget, people look up to tinkerers, so a lot of sales were made because "this guy who knows the phones has samsung"
Click to expand...
Click to collapse
Samsung isn't as nice as you think. HTC will often allow you to unlock the phone by signing an agreement that you are voiding the warranty. Verizon has had a history of locking bootloaders that other carriers wouldn't.
This bootloader lock is mostly Verizon's implementation anyway. They're the ones who changed the bootloader and patched our loophole. Other devices on the 4.3 OTA update (sprint and T-Mobile) still have unlocked bootloaders.
The custom icon was only stating we had a custom recovery installed. Didn't have anything to do with firmware checking.
Sent from my SCH-I535 using Tapatalk 2
It's hard to call it sneaky if you look back at the thread that was all about waiting for the update it was repeated daily, if not a couple of times a day that if the OTA hits your phone not to take it because it would lock your bootloader. Taking my early upgrade from the Bionic this didn't really surprise me lol. It just clinched it that, I'll maintain my unlocked bootloader and rom away until its time for my next phone, which will be a nexus or amazingly enough a moto if i can let go of my bionic anger lol....
If you purchase a phone to be modded, after you mod it, why would you ever take a manufacturer OTA?
Sent from my SCH-I535 using xda app-developers app
galets said:
I have to say, it was incredibly disappointing that Samsung decided to sneak device lock-down disguised as a software update. Very lame. I was under impression that Samsung does value community building mods for its overpriced phones, understands the value of such community. Apparently, they don't. I agree with someone who said it will be the last Samsung device he purchased, I think it's time for me to join the boycott.
But coming back to the issue at hand: lets imagine I was lucky enough not to trust Samsung to deliver me an update and instead took a hacked one. Is there any reason whatsoever to stay on 4.3? And by that I mean:
- does 4.3 solve some problem in original firmware, that anyone should care about?
- does 4.3 implement some new feature, which was not in original 4.1 firmware that I should be excited about?
Click to expand...
Click to collapse
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Its samsung. Every version of the s3 is locked on 4.3 the only difference is nobody is complaining about it on the other forums. samsung wants to be able to have there phones used in government agencies and the like so they locked the phone down. I accidentally upgraded and haven't complained once because its not that big of a deal. I am just not buying from samsung from now on (unless they make the tablet that folds into a phone). Someone can correct me if I am wrong but everything I have read says every s3 on 4.3 has been locked down. If you do say I am wrong please give me a link so I can educate myself.
XdrummerXboy said:
Samsung probably does value it, however we need to keep in mind it doesn't HAVE to be their fault.
Android is released from Google, then Samsung gets a hold of it, adds their own skin/features/framework, then hands it off to Verizon, where Verizon locks everything down and adds crap things to it. Verizon is EXTREMELY against community mods and such.
We need to figure out if other carriers are having issues with the 4.3 rollout (if it exists) then we might be able to decide who dropped the ball
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang
XdrummerXboy said:
Ahhh I forgot about the Knox or whatever they call it. I thought you were able to switch between using it and not though.
But I guess maybe they have to make sure EVERYTHING is secure, then build the "non" secure stuff on top of that framework.
SGS3 running Android 4.4 KitKang
Click to expand...
Click to collapse
You can still root the OTA by using saferoot. Once rooted, superSU will ask if you want to disable knox. You can then load safestrap which will allow you to load other 4.3 roms and multi-boot your phone etc. Read ALL the threads on saferoot and safestrap before you install them.
Sent from my SCH-I535 using xda app-developers app
galets said:
Okay, we got the 4.3 update we all been waiting for. Now comes the magic question - WHY.
I'm not trying to troll here, I think I have a valid question. It's got features taken out, a lot of stuff is different now, some things work, some things don't. It looks different, but - is it better? I am yet to find what is it that it does better than original 4.1 firmware.
I guess what I'm trying to ask is : "give me a reason not to revert back to where it was"
Click to expand...
Click to collapse
App access to notifications. That is my killer app for 4.3
Very tempted to purchase one now with the android l beta out. A few questions (as I'm sure many have who are in the same predicament) before I do:
1. Since I'm purchasing one from Google play and it comes pre loaded with latest kit kat version, can this device's boot loader be unlocked and rooted using various all in one toolkits that are currently out there?
2. For those of you who are currently using it have you noticed any issues with battery life? Any difference with connectivity to mobile data.
I look forward to hearing from you guys before I make my purchase and thank you in advance.
ThatArchVillan said:
Very tempted to purchase one now with the android l beta out. A few questions (as I'm sure many have who are in the same predicament) before I do:
1. Since I'm purchasing one from Google play and it comes pre loaded with latest kit kat version, can this device's boot loader be unlocked and rooted using various all in one toolkits that are currently out there?
2. For those of you who are currently using it have you noticed any issues with battery life? Any difference with connectivity to mobile data.
I look forward to hearing from you guys before I make my purchase and thank you in advance.
Click to expand...
Click to collapse
well if you have made up your mind to get into the party then
1.Yes, it can be rooted fine with toolkit, but still advisable to do it the adb way but toolkit works fine for many who dont want to get into hassle of learning adb stuff
2.for battery it will easily last a day though significant drainage was there with earlier builts on 3g data but it has been solved to some extent now and if you are on wifi no worries
3.if you are not aware of the fact that the next nexus device is there,and expected to release oct/nov so if you want to wait as it comes pre loaded with android L which will get a better name rather than L soon
make your choice :good:
shhbz said:
well if you have made up your mind to get into the party then
1.Yes, it can be rooted fine with toolkit, but still advisable to do it the adb way but toolkit works fine for many who dont want to get into hassle of learning adb stuff
2.for battery it will easily last a day though significant drainage was there with earlier builts on 3g data but it has been solved to some extent now and if you are on wifi no worries
3.if you are not aware of the fact that the next nexus device is there,and expected to release oct/nov so if you want to wait as it comes pre loaded with android L which will get a better name rather than L soon
make your choice :good:
Click to expand...
Click to collapse
Thank you so much for your quick reply. If a new nexus will be releasing in 4-5 months and it will have the new android os then I guess I can wait. I hope it stays at the $350 price point. For my personal device I use a galaxy s4 running slimkat and it works fine with slight damage around the edges with the battery lasting an easily 15+ hours with moderate to high use. Again thank you because you saved me $350+ dollars but I'm sure you made it a lot easier for the people who are on the fence still and are looking to get a new phone (who actually need a new device) who were looking to do the same thing.
ThatArchVillan said:
Thank you so much for your quick reply. If a new nexus will be releasing in 4-5 months and it will have the new android os then I guess I can wait. I hope it stays at the $350 price point. For my personal device I use a galaxy s4 running slimkat and it works fine with slight damage around the edges with the battery lasting an easily 15+ hours with moderate to high use. Again thank you because you saved me $350+ dollars but I'm sure you made it a lot easier for the people who are on the fence still and are looking to get a new phone (who actually need a new device) who were looking to do the same thing.
Click to expand...
Click to collapse
well a s4 is a good enough phone to spend this 4to 5 months of wait till the next beast is release and whatever drawbacks we can conclude from nexus5 though its a user expectation stuff, still expecting few things after the google I/O and expected to sweep all other phone by large
expected:
64bit snapdragon 810/808 render 4K video,/3gb ram/13mega pixel camera/a larger battery
ThatArchVillan said:
Very tempted to purchase one now with the android l beta out. A few questions (as I'm sure many have who are in the same predicament) before I do:
1. Since I'm purchasing one from Google play and it comes pre loaded with latest kit kat version, can this device's boot loader be unlocked and rooted using various all in one toolkits that are currently out there?
Click to expand...
Click to collapse
Please do not use a toolkit. If you use a toolkit, you wont learn anything about fastboot. Unlocking the bootloader and flashing a recovery via fastboot is ridiculously easy on this phone. If you don't take the time to learn fastboot now, when you get into trouble later on - you wont know what you're doing and when we try to give you instructions if you need to use fastboot to recover, it makes it much more difficult for us to help you fix it.
It's like turning up to a creative writing course, but expecting us to teach you to read first,
Please click the link in my signature and look at section 1a and 1b. To root an unlock your bootloader, section 1b has all you need to know.
It really is as simple as installing fastboot and drivers then running a couple of fastboot commands. Very easy and worth learning.
rootSU said:
Please do not use a toolkit. If you use a toolkit, you wont learn anything about fastboot. Unlocking the bootloader and flashing a recovery via fastboot is ridiculously easy on this phone. If you don't take the time to learn fastboot now, when you get into trouble later on - you wont know what you're doing and when we try to give you instructions if you need to use fastboot to recover, it makes it much more difficult for us to help you fix it.
It's like turning up to a creative writing course, but expecting us to teach you to read first,
Please click the link in my signature and look at section 1a and 1b. To root an unlock your bootloader, section 1b has all you need to know.
It really is as simple as installing fastboot and drivers then running a couple of fastboot commands. Very easy and worth learning.
Click to expand...
Click to collapse
Thank you for linking that guide. This will be most helpful to those looking to purchase that nexus 5 in the near future. I could go either way at this point. I'd feel real salty if I got it and the nexus 6 comes out a as early as mentioned above. Any set release date on that yet?
ThatArchVillan said:
Any set release date on that yet?
Click to expand...
Click to collapse
Anything anyone here says about the Nexus 6 is a guess. We do not even know if there will be a Nexus 6 at this point, let alone a release date. If you're concerned about that, wait until November and see what happens. If no Nexus 6 has been announced, get something else.
rootSU said:
Anything anyone here says about the Nexus 6 is a guess. We do not even know if there will be a Nexus 6 at this point, let alone a release date. If you're concerned about that, wait until November and see what happens. If no Nexus 6 has been announced, get something else.
Click to expand...
Click to collapse
So I bit and purchased a white 16gig nexus 5. I look forward to doing things properly. I must ask though, is Franco kernel compatible with android L? Also can L be rooted on the nexus 5? I could have sworn there's already a thread created for this question already
L is a preview. It isn't an official release. No source code has been released so no one can develop a kernel for it.
Click the link in my signature. It contains all the important threads including rooting L
Sent from my Nexus 5 using Tapatalk
rootSU said:
L is a preview. It isn't an official release. No source code has been released so no one can develop a kernel for it.
Click the link in my signature. It contains all the important threads including rooting L
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have all the guides open so I'll refer to that when the phone comes in later on in the week. I guess I could use cpu tuner after I gain root access. Hows L been working out for you so far on your device?
Don't buy a Nexus 5 just because the developer preview for L is here.
too late lol. and my GS4 is really beat up so I was looking to try out a nexus phone anyway. Thanks rootSU for including guides in the sig. they really helped and made the process really smooth and easy. going to be using this for awhile. hopefully battery isnt too bad on L. if so prolly put that slimrom on there
Few apps don't work presently but that goes without saying. Battery life is not bad at all. Sure do miss pie launcher and changing icon size from slimkat but I'll manage
Sent from my Nexus 5 using XDA-FORUM, powered by appyet.com
I've not tried L. I'll just wait for the slim release most likely.
Sent from my Nexus 5 using Tapatalk
Hi new to the forum.
I bought the Xcover 2 in order to get a smartphone capable of surviving in the construction site.
But I realised it could not hold too many apps.
It's screen is allready shattered but at least, thanks to xda, I rock rootetd it and I can now have some usefull apps with me at work.
This week I bought a brand new Leica Disto D510 laser distancemeter with bluetooth pairing to use on site with my ruged (!) smartphone but ... Oh Lord, it DOESN'T PAIR.
It uses Bluetooth Smart 4.0 which can only be used with Android 4.3 or higher!!!! BoloX. The Xcover 2 runs 4.1.2
So THE QUESTION:
1: Is there any way to go around this without upgrading? I don't want to push the poor device too far and since it was designed for 4.1.2 I would like ti leave it with that if possible.
2: If I have to upgrade.. how the heck do you do that? I ,ve spent more that three hours now trying to find the right ROM to flash and I can't!!!!
Thanks in advance to the lady or gentleman, kind enough to post an answer. He will save me the cost of a new phone.
Nagno said:
Hi new to the forum.
I bought the Xcover 2 in order to get a smartphone capable of surviving in the construction site.
But I realised it could not hold too many apps.
It's screen is allready shattered but at least, thanks to xda, I rock rootetd it and I can now have some usefull apps with me at work.
This week I bought a brand new Leica Disto D510 laser distancemeter with bluetooth pairing to use on site with my ruged (!) smartphone but ... Oh Lord, it DOESN'T PAIR.
It uses Bluetooth Smart 4.0 which can only be used with Android 4.3 or higher!!!! BoloX. The Xcover 2 runs 4.1.2
So THE QUESTION:
1: Is there any way to go around this without upgrading? I don't want to push the poor device too far and since it was designed for 4.1.2 I would like ti leave it with that if possible.
2: If I have to upgrade.. how the heck do you do that? I ,ve spent more that three hours now trying to find the right ROM to flash and I can't!!!!
Thanks in advance to the lady or gentleman, kind enough to post an answer. He will save me the cost of a new phone.
Click to expand...
Click to collapse
i dont believe there is any direct way around the bt issue.
your phone shipped with 4.1.2, seems odd that it never got any updates. did you go into settings near the bottom or in about phone, and check for updates?
there is at least one 4.4 rom for your phone that i found with a quick search, so there must be root and custom recovery some where, but its difficult for me to give accurate advice on how to proceed for a device i have no experience with.
ill just throw a couple google search links down here for you to look through if there are no software updates when you check.
if you decide to go the custom route, the first thing you want to do after installing twrp, and before installing a custom rom, is make a backup and save a copy to your pc for safe keeping. some times on these less popular devices it is hard to impossible to find the factory software, so you need a backup of it if anything goes wrong, or you dont like the rom.
https://www.google.com/search?q=Sam...=UTF-8#q=Samsung+GT+S7710+Xcover+2+custom+rom
https://www.google.com/search?q=Sam...ie=UTF-8#q=Samsung+GT+S7710+Xcover+2+recovery
I'm seeking the Android 12 Update from 11 on my Samsung A32 5g .... To be ... I'm really seeking knowledge about this kind of thing... So shoot me a link for damm near any kind of install update attachment that I can apply in order to gain the knowledge on it...
🕸🕸🕸🕸🕸🕸🕸🕸
I don't know if this will help, but here are my experiences updating my Samsung Galaxy A32-5G from Android 11 to Android 12 earlier this month.
Did Google screw up on your upgrade of Android 11 to Android 12?
It's unclear to me, but did you upgrade (OTA) to A12 from 11? And, more importantly, if it wasn't an OTA upgrade, if I may, how did you go about obtaining it for your handset?
evnStevn said:
It's unclear to me, but did you upgrade (OTA) to A12 from 11? And, more importantly, if it wasn't an OTA upgrade, if I may, how did you go about obtaining it for your handset?
Click to expand...
Click to collapse
Sorry I wasn't clear. I apologize. I didn't do anything special.
I just ran a normal standard update process from Android 11 to Android 12 over the air where I ran a check in the settings for what was available and the phone said the Android 12 update was available to me from the carrier.
This week I ran another update the normal way over the air as shown in these screenshots but this isn't the Android version but the software patch level version - but the point is I just do normal updates over the air whenever they're available - just like everyone else does them.
thanks, and apologize for not seeing your help!
For sure, I'm the same model, but we're TracFone(pre-paid) variant of Verizon, I guess? But, I see some other folks using pre-paid variants like Mom's here, and they're bragging about it, getting 12! So, if anyone has a way, or knows the secret handshake requirement, I'd be grateful, as I'm not seeing much about workarounds, I think they're called ? In a last ditch effort, could I get the firmware specs from you on your 12 update, build #, etc., which should get me going somewhere. Thanks! es
All the fun stuff is rooted on A11 ;-)
GalaxyA325G said:
This week I ran another update the normal way over the air as shown in these screenshots but this isn't the Android version but the software patch level version - but the point is I just do normal updates over the air whenever they're available - just like everyone else does them.
Click to expand...
Click to collapse
too cool with that, and i'm still not seeing that secret passage we catch ourselves looking for, in my case some geek notes on how to get 'r done & get Mom's "new one" rocking on A12 all day, & everyday, baby!! Thanks, to you for your help and input, friend!