Hi,
I recently tried to root my Acer A510 (without having a backup made). Silly I know, anyway I encountered numerous problems and at points it was impossible to load the android operating system. Now I have eventually enabled myself to use the operating system however I believe my resolution is set for the A700 not A510, this means that the screen is too big to be used properly. Is there an easy way to change this?
Kind Regards,
Stephen Way
P.s the irony is that my tablet is still not rooted
Do you have adb access ?
if so you can put the cwn recovery and go for a rom?..
BENETNATH said:
Do you have adb access ?
if so you can put the cwn recovery and go for a rom?..
Click to expand...
Click to collapse
Cheers for the quick response, is this an easy step as I don't want it to end as badly as it did last time?
Regards,
Stephen
The best way is to test..
It's not really hard, go to the 'thrills cwn recovery topic and follow the tuto
You need to have usb debugging enabled in android parameters to allow adb use
and for that, follow the topic
The other possibility is to try to flash the service rom for a510 which should accept to be flashed as update.zip
BENETNATH said:
The best way is to test..
It's not really hard, go to the 'thrills cwn recovery topic and follow the tuto
You need to have usb debugging enabled in android parameters to allow adb use
and for that, follow the topic
The other possibility is to try to flash the service rom for a510 which should accept to be flashed as update.zip
Click to expand...
Click to collapse
Thanks for the advice but still having trouble, do you know where I could find any stock acer a510 roms?
http://forum.xda-developers.com/showthread.php?t=1729073
or
http://forum.xda-developers.com/showthread.php?t=1731045
Maybe You should explain in more detail what happened so we ( the wise men which I'm not) could help you in a more accurate way.
Sent from my MB525 using xda app-developers app
stephenway said:
Hi,
I recently tried to root my Acer A510 (without having a backup made). Silly I know, anyway I encountered numerous problems and at points it was impossible to load the android operating system. Now I have eventually enabled myself to use the operating system however I believe my resolution is set for the A700 not A510, this means that the screen is too big to be used properly. Is there an easy way to change this?
Kind Regards,
Stephen Way
P.s the irony is that my tablet is still not rooted
Click to expand...
Click to collapse
Like seriously, how can you go wrong rooting? Unless you're referring to installing a custom ROM as well, rooting (to me) was very simple. With the drivers installed, all I did was connect to my computer and run the necessary file from my computer. That's all. You make this sound like a long process.
PS: I am a rooting newbie, but the root process for the A510 couldn't have been simpler. Please let me know where you went wrong.
Related
Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.
The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?
yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019
Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.
solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?
assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.
okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.
According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?
no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?
autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.
I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?
cwm 6.1 for tipo is out. See >>HERE<<
Well, I am unshure to use it.
Will it brick my phone?
My Sony Xperia Tipo is german from Telekom.
- bootloader is locked
- firmware is 11.0.A.0.16
- rooted
Does a locked bootloader block installing CWM or cause trouble in any way?
Are there german users out there who have succesfully installed the mentioned CWM already?
killerhippy said:
cwm 6.1 for tipo is out. See >>HERE<<
Well, I am unshure to use it.
Will it brick my phone?
My Sony Xperia Tipo is german from Telekom.
- bootloader is locked
- firmware is 11.0.A.0.16
- rooted
Does a locked bootloader block installing CWM or cause trouble in any way?
Are there german users out there who have succesfully installed the mentioned CWM already?
Click to expand...
Click to collapse
If you're rooted already, you're good to go.I suggest flashing 4.22 though, it is really noticeably better in performance.You can root that with UnlockRoot, and install CWM/TWRP afterwards, whichever you'd like.
Steam. said:
If you're rooted already, you're good to go.I suggest flashing 4.22 though, it is really noticeably better in performance.You can root that with UnlockRoot, and install CWM/TWRP afterwards, whichever you'd like.
Click to expand...
Click to collapse
Good news. Thank you for your encouraging answer.
As I have so far noticed documentation on this forum, in the case of error doing recover attempts are made with windows software.
I am running linux, if windows is nescessary, does recover software work at a virtual machine running Windows XP with USB piped through? Or is there even linux software to manage that?
And, can you advise a good location I can read and follow instructions in the case of CWM installation problems?
Please excuse my nooby questions, my fone is the very first and only one I could afford and I have no experience so far.
I'd like to prepare as much as I can to avoid having a bricked device asking questions at a lost situation.
Cwm is fine for you take care while flashing a rom though it can cause a mess but dont worry I have been messed up before I got my tipo back running in 17 minuts
I got sollution very quickly and stepwise you are not a noob but I am so just sharing my xperience????
Sent from my ST21i using xda app-developers app
killerhippy said:
Good news. Thank you for your encouraging answer.
As I have so far noticed documentation on this forum, in the case of error doing recover attempts are made with windows software.
I am running linux, if windows is nescessary, does recover software work at a virtual machine running Windows XP with USB piped through? Or is there even linux software to manage that?
And, can you advise a good location I can read and follow instructions in the case of CWM installation problems?
Please excuse my nooby questions, my fone is the very first and only one I could afford and I have no experience so far.
I'd like to prepare as much as I can to avoid having a bricked device asking questions at a lost situation.
Click to expand...
Click to collapse
It's hardly brickable by root procedures, the only thing you could've run into was not getting the files copied to system, but since you're rooted you don't have any probs.Just DL the zip from the CWM thread, extract the files in some folder, connect phone with usb debugging on, and double click the start.bat
it will tell you when it's done, you can press any key to continue.at this point, disconnect the phone from the USB cable, power off, then start it up and tap volume down at the Sony logo.
Steam. said:
It's hardly brickable by root procedures, the only thing you could've run into was not getting the files copied to system, but since you're rooted you don't have any probs.Just DL the zip from the CWM thread, extract the files in some folder, connect phone with usb debugging on, and double click the start.bat
it will tell you when it's done, you can press any key to continue.at this point, disconnect the phone from the USB cable, power off, then start it up and tap volume down at the Sony logo.
Click to expand...
Click to collapse
Success!!!
Thank you so much, tusharkulkarni008 and Steam.
There were no errors at all, though I had to fetch an adb executable first which I checked working with "adb shell".
I successfull opened cwm and did my very first full system and data backup!
Splendid, now I am able to do more exciting things with my fone!
So, I learned, installing CWM is nothing but copying files to system partition. It does not depend on an unlocked bootloader, it just needs a rooted fone.
unlocked BL is only required for flashing a custom kernel, which is required for most custom roms around here, they are all based on FXP release,CM10.
Hi everyone!!
Quick introduction: I'm just a regular guy, not that tech-y, that purchased a Galaxy Note for note taking in classes. And i have a problem: the bottom android is a pain for note taking. So, while searching for a solution, I ended up here. Of course, one thing leads to another and after reading a few threads, I already realized that are other "tweaks" I would like to make to my tablet that I didn't even knew I wanted But let's go step by step.
I've been reading the samir_a excelent thread, Guide - Installing Firmware, CWM recovery & Rooting, that seems to be the beginning of everything (correct me if I'm wrong). And I'm convinced I know how to do it... how to root, how to install firmware, so on. What I don't understand is what these actions actually do. In other words, I don't understand most of these concepts - like "rooting", "firmware", "CWM", etc etc etc - so I ended up not getting the process. Sometimes I feel like you guys are speaking other language that not English.. So sorry if some of these questions are dumb...
- Root the device means getting access to do stuff that I can't do without that, correct? Like entering as "root" in Linux - you can do stuff that you can't with other users. Is that it?
- I read a lot that to move the navigation bar to the top of the device I need to root it. But is just that? I root the device and boom... the top bar is on the top?
- Is "install a firmware" the same as "install a ROM"? (meaning, is it like install a new operation system in the device)
- The CWM Recovery... what is it?? Is it like.. to create a system recovery image, or something??
- Lastly... does any of these - rooting, installing ROM, etc - void the manufacturer warranty? And if yes, is there any way to undo that in case something happens?
Once again, sorry if these are dumb questions (or don't even make sense). And thanks for your patience!
Cheers!!
mmascosta said:
Hi everyone!!
Quick introduction: I'm just a regular guy, not that tech-y, that purchased a Galaxy Note for note taking in classes. And i have a problem: the bottom android is a pain for note taking. So, while searching for a solution, I ended up here. Of course, one thing leads to another and after reading a few threads, I already realized that are other "tweaks" I would like to make to my tablet that I didn't even knew I wanted But let's go step by step.
I've been reading the samir_a excelent thread, Guide - Installing Firmware, CWM recovery & Rooting, that seems to be the beginning of everything (correct me if I'm wrong). And I'm convinced I know how to do it... how to root, how to install firmware, so on. What I don't understand is what these actions actually do. In other words, I don't understand most of these concepts - like "rooting", "firmware", "CWM", etc etc etc - so I ended up not getting the process. Sometimes I feel like you guys are speaking other language that not English.. So sorry if some of these questions are dumb...
- Root the device means getting access to do stuff that I can't do without that, correct? Like entering as "root" in Linux - you can do stuff that you can't with other users. Is that it?
Click to expand...
Click to collapse
Right!
mmascosta said:
- I read a lot that to move the navigation bar to the top of the device I need to root it. But is just that? I root the device and boom... the top bar is on the top?
Click to expand...
Click to collapse
No. But after rooting you may download and "install" (flash via CWM) a mod that does that.
mmascosta said:
- Is "install a firmware" the same as "install a ROM"? (meaning, is it like install a new operation system in the device)
Click to expand...
Click to collapse
Yes. Actually there is a difference between a rom an a kernel. Kernel is the core system adapted and customized to the model of your gadget, the Rom the user interface, simply spoken. Different roms may be based on the same kernel.
mmascosta said:
- The CWM Recovery... what is it?? Is it like.. to create a system recovery image, or something??
Click to expand...
Click to collapse
The stock recovery does not allow to flash custom roms, to make nandroid backups (full backups of your operating system / Rom / Kernel, CWM recovery does. But vou need to find the cwm that is made for your device!
mmascosta said:
- Lastly... does any of these - rooting, installing ROM, etc - void the manufacturer warranty? And if yes, is there any way to undo that in case something happens?
Click to expand...
Click to collapse
Yes an Yes! With a pc and Odin you can flash back to your original Rom your device was delivered with.
mmascosta said:
Once again, sorry if these are dumb questions (or don't even make sense). And thanks for your patience!
Cheers!!
Click to expand...
Click to collapse
If that helped, just press the thanks-button.
Thanks a lot for clarifying, charly-whiskey.
I'm trying to root, but as soon as I connect the tablet to the PC I get something different in ODIN.. I get not one, but two yellow squares in ID:COM section..
h*tp://img543.imageshack.us/img543/5894/captureokl.jpg (Sorry, I'm new here, so I can't add images...)
Why is that? May I proceed?
Have you got any other android devices attached to the PC?
Also you must be in download mode to flash with ODIN. You hold down power and volume down until the screen with the scary warning comes up, ignore it and push up volume to get to download mode.
ODIN should recognise your device.
Just a piece of advice, CHECK and DOUBLE-CHECK that partition is UNTICKED...
You can get into really hot water if you have this ticked...
ultramag69 said:
Have you got any other android devices attached to the PC?
Also you must be in download mode to flash with ODIN. You hold down power and volume down until the screen with the scary warning comes up, ignore it and push up volume to get to download mode.
ODIN should recognise your device.
Just a piece of advice, CHECK and DOUBLE-CHECK that partition is UNTICKED...
You can get into really hot water if you have this ticked...
Click to expand...
Click to collapse
Thanks! Yeah, I don't know what happened, but I unplugged and plugged again and it was ok. So I rooted and I think everything went fine.
I used Darkman's rooting method and checked that SuperSU was working. Then flashed his rom, and once again I think everything went fine. The weird thing is that the device seems not to be rooted anymore. I can't install anything that needs root access. SuperSU is installed, but when I go there, it says that no binary SU is installed.
Is this normal? What should I do? Root again?
I would ask in his thread, but the forum won't let me until I have 10 posts...
Thanks!
Just to let you know that I re-installed SuperSU through CWM and it's solved! In case it happens to anyone else
Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true
I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!
So where does one get the latest OTA?
cheers
Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.
Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!
Apologies if this is not really the place for this question but I don't know where else to go for an answer. I have just purchased a Z1 after years of putting up with Samsung bloatware etc and it has changed my life! I would like to transform my wife's phone experience as well. She can only really use a small phone and has been happy with her Ace 3 until recently, when it started to get slow and erratic. In desperation she has bought an iPhone 5 but this has not been a happy experience at all! I cannot find any new small Android phones that come with Cyanogen pre-installed so I am wondering if we can get it installed on her old Ace 3. From the discussions in this forum I guess this can be done but, not having any technical training in this subject, I really dont understand much of what is being said. I have no idea how to go about this.
So is there either a very simple manual on what to do or else a UK-based expert who can do this for me (for a fee, obviously)?
you can look from the android development section. but, it may vary to your phone model. there is a instructions to on how to install a cyanogenmod os on your ace 3. at least you are familliar with custom recoveries like cwm or twrp, you should install it first on your phone via odin in your pc.
You guys know so much
Hi, PAPlinskie, and thanks so much for getting back to me. I really appreciate it. I have looked at the page you refer to and I just don't understand it! (I don't know what cwm or twrp or Odin are) I guess you guys don't realise just how much you know. I suspect that the answer to my question is probably that there isn't an absolute layman's guide so I will probably have to look for someone to do it for me. Thanks for trying anyway.
Garth Horigan said:
Hi, PAPlinskie, and thanks so much for getting back to me. I really appreciate it. I have looked at the page you refer to and I just don't understand it! (I don't know what cwm or twrp or Odin are) I guess you guys don't realise just how much you know. I suspect that the answer to my question is probably that there isn't an absolute layman's guide so I will probably have to look for someone to do it for me. Thanks for trying anyway.
Click to expand...
Click to collapse
At first I didn't want to flash Custom ROM's on my phone for fear of breaking it... But All I had to do was just follow instructions to the "T" and I had no hiccups...
Okay, so lemme clear some things up for you.
Odin is an Application which you run on a Windows machine, (Your PC). It serves as a bridge to allow you to put custom software such as custom recoveries and allows you to fix a broken device (If the software is the problem)
TWRP & CWM are both custom recoveries. You can think of the stock recovery mode in Android like Safe Mode in Windows, It allows you to Wipe your entire phone or perform other recovery options if you are unable to access the phone when you turn it on. A custom recovery allows all these functions, but on top of that, allows you to flash (install) files to your phone, Like your CyanogenMod.
In a nutshell, if you want CyanogenMod on your Ace 3, you will have to:
1. Install drivers on your PC so that it recognises your phone
2. Using ODIN, flash a custom Recovery
3. Download a CyanogenMod port found here on the forums.
4. Install (Flash) it in your Custom recovery.
The guides here on XDA are really good, all you have to do is do your homework, read, understand and you will have no problems.
Good Luck with your quest on Custom ROMS:good:
The coward's way out!
Sayrian said:
At first I didn't want to flash Custom ROM's on my phone for fear of breaking it... But All I had to do was just follow instructions to the "T" and I had no hiccups...
Okay, so lemme clear some things up for you.
Odin is an Application which you run on a Windows machine, (Your PC). It serves as a bridge to allow you to put custom software such as custom recoveries and allows you to fix a broken device (If the software is the problem)
TWRP & CWM are both custom recoveries. You can think of the stock recovery mode in Android like Safe Mode in Windows, It allows you to Wipe your entire phone or perform other recovery options if you are unable to access the phone when you turn it on. A custom recovery allows all these functions, but on top of that, allows you to flash (install) files to your phone, Like your CyanogenMod.
In a nutshell, if you want CyanogenMod on your Ace 3, you will have to:
1. Install drivers on your PC so that it recognises your phone
2. Using ODIN, flash a custom Recovery
3. Download a CyanogenMod port found here on the forums.
4. Install (Flash) it in your Custom recovery.
The guides here on XDA are really good, all you have to do is do your homework, read, understand and you will have no problems.
Good Luck with your quest on Custom ROMS:good:
Click to expand...
Click to collapse
I have taken the coward's way out. I went into my local neighbourhood PC techie shop and asked if they knew of a reliable local phone engineer who could install Cyanogen for me. The boss' assistant said he does that sort of thing for a hobby and was happy to do it for me in return for a donation to his drone fund! He seems to made a cracking job of it and my wife is overjoyed to have her Ace back in a turbo-charged state.
Many thanks for your help and I am only sorry I was not brave enough to act on it.
Garth Horigan said:
I have taken the coward's way out. I went into my local neighbourhood PC techie shop and asked if they knew of a reliable local phone engineer who could install Cyanogen for me. The boss' assistant said he does that sort of thing for a hobby and was happy to do it for me in return for a donation to his drone fund! He seems to made a cracking job of it and my wife is overjoyed to have her Ace back in a turbo-charged state.
Many thanks for your help and I am only sorry I was not brave enough to act on it.
Click to expand...
Click to collapse
It's okay. We all know how daunting these things can be because you don't want to brick your device.
Maybe in the future you will be able to try it yourself.