Related
I was wondering why we've never seen a TWRP build from TeamWin for the TF101. I remember when the tablet came out that a few team members had the device and there was talk of builds upcoming for our device. Then there was the long break and TWRP2 and everything that happened at TeamWin, finally with 2.1 builds showing up. But there was nothing for our device, while the TF201 and TF301 were getting love.
I pinged dees_troy on twitter and found out some interesting info:
The Recovery Partition is only 5MB on the TF101
The Kernel needs to be less than 3MB to leave enough room for TWRP, meaning a custom recovery kernel.
Without a device in a devs hands, we'll not see TWRP
https://twitter.com/Dees_Troy/status/216631211366424576
https://twitter.com/Dees_Troy/status/216631556863836160
If I didn't rely on mine daily, I'd send it over for some builds, but that is not feasible for me.
Maybe we can get a developer to notice and build this, because I'd love to see a refined touch recovery like TWRP. I mean with the kernel though, how big is it with a stripped down version of it?
Darn shame about the partition sizes, those can be moved around.. but that's not a really great fix. I'd compile it and do a tad of bug-fixing since it should be the same process, but I really don't want to mess with partition sizing being too small and stripping recovery down. X.x
I've asked before and pm'ed about being a tester, and if it happens I'll be on top of it!
See, that's one thing Moto did good with their phones. I would have no issues with partitioning being similar, but I think they did go a little over board on what the system got versus what the consumer should be able to use for storage, IMO.
If there was a guide and I knew I could do it without creating to much headache trying to get it right, then I'd start on a similar project. My biggest problem is, I don't know very much about this at all. The last time I did any programming, I was in highschool and was learning C++ and did some PHP coding, but that doesn't apply here. HaHa.
TWRP has a step by step compile from source linux guide
Just the partitioning, I think it would work straight from source pretty well, but considering that the partition is too small that's where it gets tricky
Thing O Doom said:
TWRP has a step by step compile from source linux guide
Just the partitioning, I think it would work straight from source pretty well, but considering that the partition is too small that's where it gets tricky
Click to expand...
Click to collapse
just build it and see what the size is then we might be able to engage one of the kernel devs to help strip stuff out
Sent from my CM9 Transformer TF101 using Forum Runner
Alright, I'll compile from source and see what I can do. Give me a while though, because I'm upgrading my computer.
Sent from my TF101
Thing O Doom said:
Alright, I'll compile from source and see what I can do. Give me a while though, because I'm upgrading my computer.
Sent from my TF101
Click to expand...
Click to collapse
just checking in, any progress?
Sent from my CM9 Epic 4g Touch using Forum Runner
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Thing O Doom said:
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Click to expand...
Click to collapse
no worries, appreciate the effort
Im also eagerly awaiting any news on this... Im stuck on Rogue recovery because all the other versions dont use the MicroSD card, only the internal memory
Can someone post where I can find the partition layout/structure/description? (or PM it to me, that woul work as well)
Thing O Doom said:
I'll admit I've been lax so far, it is on my list, but I'm so close to finishing APK peri >.< I just wanna get that done first.
Click to expand...
Click to collapse
Hammerfest said:
Im also eagerly awaiting any news on this... Im stuck on Rogue recovery because all the other versions dont use the MicroSD card, only the internal memory
Can someone post where I can find the partition layout/structure/description? (or PM it to me, that woul work as well)
Click to expand...
Click to collapse
Looks like rayman has taken the reins on this one. There is a thread in dev for a WIP TWRP recovery
Yep he mentioned it and took over, which is great! Works decently well.
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
In that case I'll give ya $100 for it.
Sent from my Galaxy Nexus using Tapatalk 2
zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unfortunately, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thread that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before via HOT LINE but without any response!) This tablet is really a piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Well my friend not exactly the best words to start with if needing help from the many fine members of this forum.
The unlock tool will eventually work if that's what you want to do.
Personally your being "really ugly" to Asus thru e-mail could be why they remain unresponsive.
If you could perhaps take the calm approach those trying to help would be much more willing.
absurd paradox
Unfortunately I can understand where all these negative feelings derive from.
I am the rightful owner of a tf700 too.
To be quite frank (and I won't surprise anyone), I am not pleased.
There is no reason why I can't enjoy a smooth and flowing experience.
There is no reason why in order to make the best out of the tf700 it is recommended that I flash a custom rom.
I refuse to unlock my tf700 because there is no reason why I should void my warranty, trying to fix it - this is an absurd paradox!
It is about time someone filed a class action in order to stop this "tf700 incident",
so Asus will start to make their excuses in court or maybe solve this unfortunate condition,
once and for good.
cheers.
Nothing stopping you from filing a class action lawsuit is there?
Or you could just take control and unlock and flash a custom ROM and be done with it....
Choice is yours as Asus are not going to help you.
wish it was that simple
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
For example, I read a guide which explains how to unlock and install a custom recovery using an "adb tool",
but there is no explanation how to install the newest version of TWRP, which is required for cromi 3.4.X.
Anyone know a plain and full guide for 10.4.4.25 build?
http://forum.xda-developers.com/showthread.php?t=2088176
No very ugly
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
zrebec said:
OK, that wasn't very ugly mail, just I wrote to ASUS that I tried contact HOTLINE two times and nobody response me I was very frustrated that I cannot unlock my tablet
Can someone explain me, why doesn't exists alternative way around unlock?
The processor is encrypted or what?
Thanks
Click to expand...
Click to collapse
A work around for the unlock isn't available.
Seems as though the key for the bootloader is encrypted very well.
Until someone leaks the key to the internet we're stuck.
My understanding is:
Asus wants the embedded serial for any tablet requesting a bootloader unlock.
The serial is registered with Asus from an outside server database.
Asus voids the warranty then shuts off OTA's because they don't want to push updates over any customisation to the tablets firmware.
This would most likely result in a bricked\non-functioning device.
Asus knows people inherently re-code devices with non-manufacturer firmware and risky applications.
The manufacturer is saying to the buyer we can't be responsible for user induced damage.
zrebec said:
Hello, dear fans
Yes.... I think also that TF700 is piece of crap and not solid tablet but anyway.... I have Asus Transformer Pad Infinity (TF700) with last official update (WW_epad-user-10.4.4.25.zip) JB stock ROM... But the tablet is still laggy and unstable. I want try to another ROM. Unofrtunatelly, I cannot unlock my device (Maybe you see the message: An unknown error occurs, which may be a network connection issue. please wait and try again later). If I cannot unlock I cannot get the ROOT on JB also I saw in some thred that people with earlier or equal ROM with 9.4.5.26 can unlock the device and in 9.4.5.30 and later NOT. But I cannot flash to .26 ROM because JB needs almost .30 ROM and later (I tried writing blob via fastboot and update via EP201_768_SDUPDATE.zip on SDcard also... But I can install only .30 ROM as MINIMUM! But on this ROM I cannot unlock my device ALSO. I really try anything... Any ideas? Of course, I wrote very ugly mail to ASUS support but without effects (I tried before viac HOT LINE but without any response!) This tablet is reaaaaly piece of trash. Thanks for advice.
Click to expand...
Click to collapse
Another woe-is-me post! Someone please get me a hankie, quick!
zrebec said:
OK, that wasnt very ugly mail, just I wrote to ASUS that I tried contact HOTLINE twotimes and nobody response me I was very frustrated that I cannot unlock my tablet Can someone explain me, why doesn't exists alternative way around unlock? The processor is crypted or what? Thanks
Click to expand...
Click to collapse
First of all you could use the search button
Here is a thread where I specified how I got my tablet unlocked: http://forum.xda-developers.com/showthread.php?t=2146543
Just keep in mind that the Asus Support employees are not personally responsible that the MDM-server in Taiwan does not know your tablet. Don't act like a jackass and don't act like mister-know-it-all, then they will help you, like they helped me.
I wish flashing a clean rom was that simple, but there is no plain guide.
Everywhere I go (including xda forums) there are "half explanations" and I am tired of trying to solve this puzzle.
Click to expand...
Click to collapse
These forums here provide all information one needs to unlock/ root/ install custom ROMs. I got all information from here and I did not have any problem whatsoever.
You know, people here are willing to share their experience and to help out each other, but the burden to do the work is on you. Also the risk of bricking your device is on you.
Just don't expect anybody to do your work.
As a matter of fact, installing custom ROMs on the TF700 is not trivial. You do need ADB and Fastboot to flash a recovery first. Also you have to have some basic knowledge about how computers work in general and about Android devices.
Even as complete noob, you can find all needed information here. So either you take your time and educate yourself - like I did - or you use the stock ROM or you hire somebody who does the work for you.
Root it but keep it locked! I was loosing sleep at night because I thought I was suckered into believing this was a quality machine and its got tons of glitches, no doubt. But they are mainly lack-of-RAM related. If you root, and disable most of your startups, you can get a clean 500MB after boot, and that makes all the difference in the world, trust me. I was in you boots and was actually dreaming about getting an iPad (please forgive me guys). Honestly, I was sick to my stomach then the rage set in. I decided to learn and root before throwing this POS on ebay or craigs list, and starting over with another brand, probably an Apple, I was so hurt by lack of quality and testing/debug.
Like day and night! Now I love this thing. Hasn't had a random reboot, app crash, etc. in nearly a month now. Before I was getting 5 per day. Its an amazing difference attributed to the OS and apps having room (RAM) to run in. Whoever decided that 1GB RAM for a 4-core droid tablet was enough should be tarred and feathered then shot in the head twice!!! If it had been 2GB instead of 1GB we wouldn't be having this discussion at all.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unlocked! Yay!
Hello dears,
so I have my tablet Unlocked now... I forgot.... You must register account and then register tablet here https://vip.asus.com/login.aspx?. So maybe this can help to someone... OK, I have installed Clean Rom Inherited now and it looks and works fine Thanks to all.
So steps to reproduce:
1) Create account on https://vip.asus.com/login.aspx?.
2) Register device after that
3) Download Unlock Device App: Unlock boot loader from Android -> Utilities from http://support.asus.com/download.as...Pad Infinity TF700T&hashedid=fq2B3oq64av1O95u
4) Run the application
5) Tick the you understand that your warranty is now VOID
6) Type your google account login and password
7) After restart you should see in up-left corner message "Device is unlocked"
8) Enjoy
Update: Fixed my last known problem which was wifi streaming movies to the device from external source (wifi HDD or network connected storage). Got Dice Player, that's all I have to say. Now EVERYTHING is working perfectly. No more random reboots, app issues, conflicting apps, got plenty of RAM, got all my desired startups loaded including System Tuner with a few tweaks added, Browser2RAM, RAM booster, etc. and device runs fast, smooth, and without any "glitches". I finally have achieved rooted stability and will now take a rest and enjoy this tablet a bit before I do anything more to it because this has been a hair-puller to get to this point. Finally very happy with this device but I had to venture far from stock to get here and it was worth it.
By the way, what day of the week is it?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
I've never seen a two day span where I've seen this many near bricks and recovery problems. Its starting to look like the TF300 fiasco. Did CWM screw something up recently or are all these user problems unrelated and coincidental?
elfaure said:
I've never seen a two day span where I've seen this many near bricks and recovery problems. Its starting to look like the TF300 fiasco. Did CWM screw something up recently or are all these user problems unrelated and coincidental?
Click to expand...
Click to collapse
It is mostly user problems, but CWM can brick your device by wiping the wrong partition. TWRP has been patched and wont do this. AKA why TWRP is recommended, rather than CWM, which is a good recovery, but for our device it can cause issues. And if you read, 99% of the bricks are recovered. So the point of the bricks is nothing, it is if we can recover them or not, to which most are, which is a wonderful thing. 10 TF300s a day were bricking, this is not occurring with the TF700, so there is no fiasco happening here .
Tylor
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
_that said:
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
Click to expand...
Click to collapse
As a newbie, I may suggest that the Tylorw1 remarks could be announced on the http://forum.xda-developers.com/showthread.php?p=30223822#post30223822 topic (regarding that it is advised to use TWRP until CWM will be patched). Because I parsed all this topics and others before starting to flash my TF700 and never seen that recommandations and the other like "do not use software launch of recovery". Those information, you can only get them on the topic you look at once you have had an issue.
I was not totally a newbie with switching to developer mode / rooting / flashing, since I began doing this on my HTC magic, continued with an HTC desire HD, then a galaxy note. Never got those hard troubles (once I had a fear, but has been able to unlock it alone with my magic).
At last, that's very good you're here to help us after our mistakes!
The problem is that there are a lot of (stupid) people who can't bloody read.
florck said:
At last, that's very good you're here to help us after our mistakes!
Click to expand...
Click to collapse
I must be honest: I fear the day _that transitions to another device. The work he put in in your case is nothing short of amazing (to me). We all have our perks and qualities, but... pfff...
On-topic: it does seem like we are having more bricks and recovery/boot problems lately. Is that a market thing? Has the 700 gone done in price, thus reaching a greater user base? (Not to my knowledge.) Are we seeing more inexperienced users now than we did at first? (That might be a likely cause.)
_that said:
Most people who brick their device don't read enough. And then, when they come here with their problem, they don't write enough.
Click to expand...
Click to collapse
Well put. We have two ears and two eyes and two hands but only one mouth. Intelligent people tend to use their senses in those proportions. Only after they have mastered this can they attempt to use their brains.
MartyHulskemper said:
I must be honest: I fear the day _that transitions to another device. The work he put in in your case is nothing short of amazing (to me). We all have our perks and qualities, but... pfff...
On-topic: it does seem like we are having more bricks and recovery/boot problems lately. Is that a market thing? Has the 700 gone done in price, thus reaching a greater user base? (Not to my knowledge.) Are we seeing more inexperienced users now than we did at first? (That might be a likely cause.)
Click to expand...
Click to collapse
I'm going to be the first to second @florck 's suggestion to top-sticky a warning about CWM with a statement that it could wipe the wrong partition and leave the user SOL (maybe not in those exact words) and for XDA to point a suggestion towards using TWRP (touch) instead as a safe alternative. At least until CWM patches this bug. This would be paramount for new users to read. I found it during my rooting research but I agree that its fairly buried.
[Edit] One thing to note is he was not using an "old" CWM, in fact it was a future developer version not even released yet?? So the masses haven't even seen this version yet. Someone should inform CWM about this before they release it, it if came from them broken. I don't think I'll ever be using their recovery after seeing what can happen.
*************************************************************************
Quote @Pretoriano80 from other thread: "CWM 6.0.5.3?The latest official version is 6.0.3.0 iirc. AFAIK this kind of brick occur when using an" old" recovery (both CWM and TWRP) with the new bootloader and is triggered when the Wipe Data option it's used."
***************************************************************************
I'm also interested in learning how his cryptographic key got messed up/deleted. I've been wondering if this could be used for a bootloader exploit to enable NVflash?
Lucky for @florck to have @_that for sure as we all are, but also lucky for him he wasn't that much of an inexperienced user that he couldn't at least access a terminal and type some commands, run an adb shell, and follow instructions. He seemed to be a pretty good student but he should have read more I agree.
I find there are three types of people. Dumb people who never learn from their mistakes, smart people who do learn from their mistakes, and then there's the wise people who learn from *other peoples* mistakes.
For me as a fairly inexperienced user getting to ride the roller coaster and see the guts of a near brick was fascinating to say the least. Its good to know about these things before you need to. Its great to know @_that if you don't. His knowledge and troubleshooting prowess is phenomenal. Rare breed indeed. It wouldn't surprise me if he didn't have a mother and was beamed down.
Guys, i think you are mixing stuff here, let me explain.
1)The "wipe data/media" option in CWM
This bug can lead to a corrupted partition but it's easy to recover by installing the Stock Firmware from MicroSD with CWM recovery (yes CWM install option will still work because the staging partition is not corrupted). After the install process is complete and the tablet rebooted once you can use the Wipe Data option from the Bootloader menu, that procedure will also fix your corrupted data/media partition.
So as you can see no ADB knowledge or other skills are required in order to recover your device.
2) Using and "old" recovery version with an incompatible bootloader (both CWM and TWRP recovery)
Using the Wipe Data option from the Bootloader menu under this circumstances could lead to a bootloop to Recovery and if you don't have good ADB knowledge/skills (or if _that it's not around ) you are doomed. Anyway it seems that as long as you still have ADB you can recover from this too.
Also some users reported a hard brick under this circumstances (bootloader signature mismatch error) but there wasn't much background info from the users on the matter.
ONLY way to recover from this issue is by sending the device back to Asus and pay for repairs.
3) Regarding the missing token my understanding is that a wrong offset was used so i presume that using the correct offset you will find that the token is still there.
And even if someone could remove the token it would still be impossible to trick Asus because they already have your device's serial number on their server.
P. S: I already planned to update the AIO thread with the latest stuff /info but i've just got recovered from a knee surgery so i'm not in the mood yet.
Using
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Thanks for the very clear play-by-play problem descriptions and future resolutions of what recently happened with the one user's near brick who then witnessed the miracle of _that in action. It'll be good for CWM users if it comes up again so they can self-resolve their problem with your instructions.
Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.
I think you can only install nvflash on not-yet bricked devices!
Sent from my Transformer Pad TF300T using xda app-developers app
vahid_shirvani said:
Hi everyone,
So lets say that the sun would rise from the west tomorrow and Asus/Nvidia released an update for NVFlash compatible with 4.1 and 4.2. Would people including myself who have a bricked tf300t with nonfunctional "fastboot flash" be able to save the tablet or are we simply screwed? (changing motherboard is not worth it in my opinion) Could some body with enough knowledge be kind and explain?
By the way, if you haven't signed the NVFlash petition yet. Do a favor and do it now! Thanks.
Click to expand...
Click to collapse
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/
tobdaryl said:
1. It will only work on UNLOCKED devices
2. It requires access to Fastboot to prepare device first time
3. It won't work on fully bricked devices (See 2.)
from http://androidroot.mobi
http://androidroot.mobi/nvflash-for-tegra3-transformer-tf300t/
Click to expand...
Click to collapse
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.
graphdarnell said:
I'm not sure why that has to be the case. On the Iconia A500 and the TF101, getting into apx mode with the code allows NVflash to wipe the NAND clean, rewrite the partition table and then rewrite the bootloader. Which retros you back to the state antebellum, which would allow reinstallment of a rom of choice after. This, at least theoretically. I make no pretense at being an expert at it, but perhaps android mobi's is not the only possible way. If truth be told, instructions by mobi's are about as clear as mud for debutants. If enough devils get involved, we may even have an automated device not unlike the APX Flash Tool or BadSector for the A500. Again, I could be missing some critical elements big time. Please enlighten us if you could, tobdaryl. Many thanks.
Click to expand...
Click to collapse
Once nvflash is installed what you present is correct (at least that is my understanding - I have only done a simple restore for testing purposes). Look at my signature for a guide to restore with nvflash. The second method presented is what you suggest for the tf101.
The situation to install is different because Asus has locked the tablet to exclude installing nvflash.
I am in the dark as you are. I only know what I can and can't do on my tablet. Otherwise I can pass information provided by others.
My reference is the Nook Tablet. I can delete every partition and rebuild the drive from a blank state this is possible because the tablet can boot from an sdcard.
I had a pm request to provide an nvflash installation guide. I complied but did not present it on xda. The member making the request was pleased and successfully used it to install nvflash. I have since used it to install nvflash on one tablet. Honestly my guide is no better than the guide provided, just a different presentation and can be done by anyone who wishes go step by step through the guide already presented. Just copy and paste the info and do some minor rewording.
I wish I could truly help but I honestly can't. I have come to accept some related info as fact since I have not been able to prove otherwise and have grown tired while chasing dead ends. I don't have the expertise, experience, or hardware to move forward.
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.