Related
Hi all,
Considering picking up an EVO to replace my touch pro2. If not evo, then an epic.
I was just wondering if there's a good intro link i should read up on, especially as far as installing custom rom's etc goes. I believe i need to get root access on the phone to do that, correct? is there a beginners guide on how to do that? Or a guide on available custom ROM's?
thanks
merkk said:
Hi all,
Considering picking up an EVO to replace my touch pro2. If not evo, then an epic.
I was just wondering if there's a good intro link i should read up on, especially as far as installing custom rom's etc goes. I believe i need to get root access on the phone to do that, correct? is there a beginners guide on how to do that? Or a guide on available custom ROM's?
thanks
Click to expand...
Click to collapse
just peruse the development forums for the Evo- each link is either a custom rom available, or a root method. Read through the root methods on how to go about rooting and nand unlocking the evo.
Check the wiki first - it will point you to all of the roms, radios, tutorials, etc.
The best place to get all of that info is the wiki, the stickies, and this thread, which benchmarks over 40 kernels and will help you choose the ones you want to try. If you don't quite understand all of the data in that thread (and the website it point you to), it will make more sense once you go through the wiki and stickies.
some quick answers - you do need to be rooted to flash a rom, which may or may not come with a custom kernel that breaks the fps cap, and may or may not be over/underclocked. If you don't like the kernel the rom comes with, try another, until you find a combo that works best with your phone (because not all evo's are created equal).
Most important thing to know is nand backup (with either amon ra, or clockwork/rom manager) before flashing ANYTHING.
nand backup? does that backup the original rom of the phone in case i muck something up and need to restore it? or should i just go RTFM before i ask more questions?
merkk said:
nand backup? does that backup the original rom of the phone in case i muck something up and need to restore it? or should i just go RTFM before i ask more questions?
Click to expand...
Click to collapse
Yes, and yes.
merkk said:
nand backup? does that backup the original rom of the phone in case i muck something up and need to restore it? or should i just go RTFM before i ask more questions?
Click to expand...
Click to collapse
lol, yeah, do your reading so you understand everything before you actually do anything. One of the subpages has a sticky on common misconceptions. It's pretty good, and someone posted a set of questions in that thread that you should be comfortable answering before you attempt root.
As far as nand goes, it backs up the current state (like a restore point in windows) of the phone at that time - so do one right before you flash anything, weather its a new Rom, kernel, radio, etc. That way if you run into bootloops or something, you can always go back to a working version of your Rom.
Sent from my blah blah blah blah
rugedraw said:
Yes, and yes.
Click to expand...
Click to collapse
Not true. It doesn't back up your original rom, just whichever one you have on it when you back it up.
IE you can't do a nand backup of a completely stock unrooted rom. You have to root in order to install the custom recovery which will allow you to back up
There are a few posts that explain how to unroot. The easiest way I have found is to run the first part of SimpleRoot then run the RUU program that you can find in various places in the forum.
Also a good habit to get into is wiping before you flash. It's a pain for having to backup settings, but I've had to unroot and reroot a few times because my 4g would get borked and stuff like that.
ok - one last question, i promise (maybe). Does the method of rooting change significantly from phone to phone? i.e. if i get an epic instead of an evo, will that make much of a difference? My guess would be no since they are running the same OS. I'm still not sure if i want an evo or epic. Gonna try and take a look at them both when i head out for lunch.
FattySparks said:
Not true. It doesn't back up your original rom, just whichever one you have on it when you back it up.
Click to expand...
Click to collapse
The OP is new; not new to planet Earth. Obviously it's going to back up whatever you have on it.
merkk said:
ok - one last question, i promise (maybe). Does the method of rooting change significantly from phone to phone? i.e. if i get an epic instead of an evo, will that make much of a difference? My guess would be no since they are running the same OS. I'm still not sure if i want an evo or epic. Gonna try and take a look at them both when i head out for lunch.
Click to expand...
Click to collapse
they can vary. like for the evo all you have to do is click a button now and your are rooted. go to the epic forums to see how they work. there are a lot of complaints w/ the epic for data uploads and gps. but then again the evo had problems when it first came out too. (now it's awesome )
rugedraw said:
The OP is new; not new to planet Earth. Obviously it's going to back up whatever you have on it.
Click to expand...
Click to collapse
the OP said will it back up your original rom. No it does not. It backs up the custom rom that you put on in order to root.
The OP may not have known that, and I really don't appreciate your snide remark when all I'm trying to do is help someone out.
rugedraw said:
The OP is new; not new to planet Earth. Obviously it's going to back up whatever you have on it.
Click to expand...
Click to collapse
LoL. Thanks. And yeah - i meant it would back up whatever is currently on the phone when you run it. Obviously if i need to root the phone before using that particular backup utility, it wont be backing up the original rom.
FattySparks said:
the OP said will it back up your original rom. No it does not. It backs up the custom rom that you put on in order to root.
The OP may not have known that, and I really don't appreciate your snide remark when all I'm trying to do is help someone out.
Click to expand...
Click to collapse
I appreciate both your comments. I wasn't aware that that backup utility required the phone to be rooted first before using it. So I assumed i could install it unrooted, and use it to backup the phone. I do realize though that it's not going to be able to backup something that''s already changed before i install the backup program.
FattySparks said:
the OP said will it back up your original rom. No it does not. It backs up the custom rom that you put on in order to root.
The OP may not have known that, and I really don't appreciate your snide remark when all I'm trying to do is help someone out.
Click to expand...
Click to collapse
Ok, then let me put it another way:
In order to create a nand back up, your phone is already rooted with nand unlocked one way or another. In which case, the "original" rom is not even on the phone. If the original rom was on the phone, you wouldn't be able to back it up anyway, so by definition, what I said is correct.
I assumed the OP meant whatever rom he was on before he started experimenting with roms. I wasn't trying to be snide; my apologies if I came across that way. Maybe next time I'll put a smiley face next to my comments so they aren't taken out of context.
merkk said:
I appreciate both your comments. I wasn't aware that that backup utility required the phone to be rooted first before using it. So I assumed i could install it unrooted, and use it to backup the phone. I do realize though that it's not going to be able to backup something that''s already changed before i install the backup program.
Click to expand...
Click to collapse
Apparently, both FattySparks and I were wrong. lol Yes, your phone needs to already be fully rooted to back up a rom, because it requires reading/writing from/to the system. However, once you root the phone and unlock nand, the back up you create will not be the original rom anymore. The original rom is available (called an RUU) if you search the Evo development section.
ok got it - thanks for the info/explanations
Best phone I have ever had, by far...love it.
Just got the phone yesterday and so far I like it. I really don't like the on screen keyboard though . but the speech to text kind of makes up for that
Sent from my PC36100 using XDA App
hey guys, so my kindle's micro USB port is defective, however i'm still under the warranty so I should be able to get a replacement right? But I have installed custom roms and recoveries and such, so the warranty is voided. Would flashing the stock rom get rid of all these things effectively, so that they wouldn't be able to tell? thanks
Not sure that actually voids the warranty. I was running CM9 and was able to do a full exchange 2 weeks ago.
They will actually send you your new kindle before you return the old one. But you can just revert to stock if you're really worried; it will get rid of everything. See the Sticky in the General forum for instructions.
And by all means wipe before flashing stock everything but your sdcard then flash it
mono feo0 said:
hey guys, so my kindle's micro USB port is defective, however i'm still under the warranty so I should be able to get a replacement right? But I have installed custom roms and recoveries and such, so the warranty is voided. Would flashing the stock rom get rid of all these things effectively, so that they wouldn't be able to tell? thanks
Click to expand...
Click to collapse
If you bought it from a brick and mortar store then I would suggest turning it off (or letting the battery die) then returning it. I have returned rooted Androids before and most of the time the customer service guys dont even check if its rooted. When it goes back to the factory Amazon is going to reflash the stock ROM anyhow so what difference does it make.
ghost_og said:
Not sure that actually voids the warranty. I was running CM9 and was able to do a full exchange 2 weeks ago.
They will actually send you your new kindle before you return the old one. But you can just revert to stock if you're really worried; it will get rid of everything. See the Sticky in the General forum for instructions.
Click to expand...
Click to collapse
is it necessary to return the old one?
Yes
mono feo0 said:
is it necessary to return the old one?
Click to expand...
Click to collapse
If you don't return the defective one, then they will charge you for the new one. If you don't already have a credit card on your Amazon account, then they will ask you for one to put on file prior to shipping the replacement.
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
atifsh said:
http://forum.xda-developers.com/showthread.php?t=1626895
alll you need to know
Click to expand...
Click to collapse
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
As I understand it, you should just be able to re-apply a stock GSM ROM to your Galaxy Nexus to get back to the original state of things. That's the whole point of a Nexus - it's stock with no customisations etc. It sounds like you'll have start from the very beginning and reinstall apps etc. but I guess you've already bitten that bullet, and presumably you're happy with your current ROM configuration?
It's not clear what recovery you have installed at the moment. You've made mention of CWM ... Clockwork Mod recovery possibly installed in that case? Again, as I understand it, Clockwork Mod recovery means you can't <s>receive</s> apply OTA updates. If you're on a stock ROM you should still receive notification about them though? If you are truly on stock, but have the Clockwork Mod recovery installed you can reinstall the stock boot recovery image. You should be able to find the stock images via a google search easily enough.
Once you've determined which recovery you currently have installed you'll have a better idea of how to get back to stock everything.
Above all, don't panic
PS I could add that busybox doesn't screw stuff up ... it just allows you to screw things up
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
real_becksaufex said:
Hi there,
the most simple way to go back to stock is using the GNex-Toolkit (to be found here http://forum.xda-developers.com/showthread.php?t=1392310) downloading the stock image here https://developers.google.com/android/nexus/images. Almost no chance to mess up your phone with this tool.
Click to expand...
Click to collapse
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Syn3rgi3 said:
Given a bit more research, I want to be able to get rid of Clockworkmod so I can receive OTA updates again.
Click to expand...
Click to collapse
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
I executed that successfully however CWM still exists =/
Syn3rgi3 said:
I've been over that thread twice now and cant find the Return to Stock instructions, am I blind? (happy to be proven wrong)
Click to expand...
Click to collapse
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
real_becksaufex said:
yeah and if tried the tool, you would have seen, that there is an option to flash stock recovery to your phone. you can also disable the bootloader again.
choose your model/build perform action 7 --> option 3 and your back on stock recovery
Click to expand...
Click to collapse
Disable bootloader?
Pressed from my Maguro
efrant said:
Seriously? The instructions in the first post...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Syn3rgi3 said:
This still doesn't solve the problem I have in regard to not having the original Telstra (yakjudv) ROM.
Click to expand...
Click to collapse
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
LOL, Telstra
Syn3rgi3 said:
Right, from the top, I'm a retard and shouldn't have messed with ROM's and custom recovery whilst blindly following a guide (I cant remember which guide, so mistake #1). I have a Telstra (Australian) Galaxy Nexus. I followed a guide to put CWM, Jelly Bean and root on, however I ran into a few problems and wanted to revert to my stock ROM, well I never performed a backup of my original ROM (mistake #2). I went looking and someone posted a Telstra stock ROM in CWM backup form here on xda, I successfully restored it and am *mostly* happy with the results, however no I cannot recieve OTA updates, which seems to be due to the prop file and others assert failing. Basically, I've learnt my lesson and want to be a good boy and go back to a non-root, completely out of the box state so if in the future, I need to return the phone for warranty, I can without fear of recourse for messing with the phone.
So again, I'm a tard, but can you help me?
EDIT: Mistake #3, I went back through my downloads and found the files I used from the guide I cant find to show you, but it DID involve Busybox which I have since read screws **** up.
Click to expand...
Click to collapse
DO NOT GET YAKJUDV!!! Try and just get Yakju, Then you will get your updates from Google NOT Telstra. You don't need the Telstra stock rom, you can use Google's Yakju. I have a Telstra one and I get updates from google because I put Yakju. You will need to flash the ROM though your pc. I have been through what you have with the exact phone (Telstra one), If you need any help you can PM me
I agree with the post from Atifsh.
The guide offered by Efrant gives you, step by step, everything you need to reach your goal.
Contrary to your case I did not need to change the factory ROM but I applied the rest of the guide (for instance post 855 in Efrant thread shows what I did).
Since I want to learn I refuse, so far, to rely on a toolkit.
I deeply share Efrant philosophy of learning. And I agree on the purpose of the XDA forum. It is not a walking clinic, it is a hospital implementing new medecines:laugh:.
Finally, taking into account my age I am closer to the hospital than to the clinic.
Thanks to Efrant and few others I am doing "stuff" I did not know I could do.
And, yes I am over the time I used to want and get everything at once.
efrant said:
I few things:
1) If you can find a backup of a yakjudv ROM from some Australian user, I'd be happy to help you restore it; but
2) You do realize that yakjudv is still on 4.0.4 (ICS) and not Jelly Bean, right? And you do realize that it only recently (past few weeks) got updated to 4.0.4 while yakju has been on 4.0.4 since March?
3) You do realize that yakju is stock, and the factory images provided by Google are the "stock" ones that get updated first. yakjudv is a Samsung build, not a stock Google build.
Click to expand...
Click to collapse
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
As you say, the problem is you need the stock recovery for the build that you are on. What build is the backup you restored? If it is ITL41F, then you are in luck. Go to this thread and download any one of the two yakjudv updates to /sdcard. Use CWM to flash it, and you will be all set -- it will wipe CWM and replace it with the correct stock recovery for that build.
---------- Post added at 08:49 PM ---------- Previous post was at 08:48 PM ----------
And please change the title of this thread to "Return to stock yakjudv" as it is very confusing. Most people refer to stock as yakju or takju for GSM devices.
Syn3rgi3 said:
I understand all the benefits of yakju, however I want to revert to yakjudv if for any reason in the future I require warranty (the phone is under contract).
I do in fact have a 4.0.1 Nandroid backup from another user on Telstra, I went ahead and restored it through CWM and everything was fine, except I still cannot receive OTA updates, doing some reading finds I need to get rid of CWM and revert to stock recovery, so how do I do this?
Click to expand...
Click to collapse
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
---------- Post added at 07:36 PM ---------- Previous post was at 07:31 PM ----------
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
picton said:
Can you please post the back up on here please via drop box or something, I need the same thing so I can return for a warranty issue however everywhere I look I just find silly people trying to inform me that I should use Google builds and no Samsung/Telstra build. I know all this however my phone is now on life support and everything seems to be going wrong so I just want to return to out of the box and return it.
I love it when people ignore the question in the OP and just decide to tell others to flash different firmware. This isnt helpful in any way when trying to return your device to Telstra in Australia as that's not what come with it so they will just give you your faulty POS back and laugh in your face because you are no longer covered by the warranty.
Click to expand...
Click to collapse
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
efrant said:
Have you tried returning a device with yakju and have Telstra give you back your "faulty POS" back? Have you heard of others who have experienced that? On the contrary, I have heard of many people returning their non-yakju-bought device with yakju, and have had full warranty.
And if you would have searched before lipping off, you would have found this: http://forum.xda-developers.com/showpost.php?p=29898676&postcount=175
Click to expand...
Click to collapse
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
picton said:
I have tried that link bro and it wont flash in CWM. I just get a red triangle with a robot on it. A mate of mine tried to take his back due to a similar problem im having and he was told he had played with the device and wouldn't fix it under warranty and wanted to charge him something stupid to fix it. I'm not giving ya lip but I have been looking for the last 6 hours and in every thread about this subject everyone is saying the same thing.
Click to expand...
Click to collapse
Ok, are you flashing it in CWM? The "red triangle with a robot" IS the stock recovery, it is not an error. What is the exact procedure you are using to flash it?
Just wanted to put info about the Kindle Fire 2 out so maybe we can start working on a 4.2 build
If you download the amazon software 10.2.4 from amazon...
you can then change the file name from .bin to .zip... doing so allows you to extract the file.
Doing this gives you all the files that are on the kindle on your computer... kernel, apps, scripts etc...
This is excellent information. I am tempted to tinker, but having never developed anything, I am not sure I would know what I was looking at, much less what to do with it. Is there any sort of guide for starting to develop on a new device?
skippyd said:
Just wanted to put info about the Kindle Fire 2 out so maybe we can start working on a 4.2 build
If you download the amazon software 10.2.4 from amazon...
you can then change the file name from .bin to .zip... doing so allows you to extract the file.
Doing this gives you all the files that are on the kindle on your computer... kernel, apps, scripts etc...
Click to expand...
Click to collapse
better yet, we can tinker with the cm10 build for the hd7... the problem with that being you need a recovery before the rom...
fmkilo said:
better yet, we can tinker with the cm10 build for the hd7... the problem with that being you need a recovery before the rom...
Click to expand...
Click to collapse
and how do we go about getting a recovery? i take it we would need to unlock the bootloader first before we can install a recovery? can anyone give me some more information regarding developing from start to finish i.e. what people are actually looking for when unlocking a bootloader, what changes need to be made to make your own kernel and what is involved in making a custom rom. I too am looking to start developing and any threads which i can read or tutorials are welcome. i am a complete noob but not afraid to try different things.
willieboya said:
and how do we go about getting a recovery? i take it we would need to unlock the bootloader first before we can install a recovery? can anyone give me some more information regarding developing from start to finish i.e. what people are actually looking for when unlocking a bootloader, what changes need to be made to make your own kernel and what is involved in making a custom rom. I too am looking to start developing and any threads which i can read or tutorials are welcome. i am a complete noob but not afraid to try different things.
Click to expand...
Click to collapse
to boot the twrp recovery for kf1, you need a fastboot cable. it isn't hard to boot, but it can't install anything yet. a twrp recovery is in the making for the kf2. so, yes. to install, bootloader unlock, but then the hd7 has been booting cm10 along with the hd8.9. so the bootloader unlock is not far away is it? as they are both running and booting an installed cwm.I believe that there may be a kf2 twrp within the week. if you have a kf2 and a fastboot cable, you can boot the twrp for kf1 by downloading the .img. then issue the fastboot boot *twrp*.img command while in fastboot.
Part of my phone's screen does not work. I have to get it fixed or even better just get a replacement. I have unlocked it and installed a custom recovery and custom ROM so I cannot just send it back because of warranty issues. I would like to revert it completely back to stock. It was some time ago I did all this flashing and whatnot and the massive amount of threads does not seem to help, they point at different sources and does not explain step by step exactly what to do. Could you please post a step-by-step how to do this without linking around and keep everything here, if possible?
Start Reading!
http://forum.xda-developers.com/showthread.php?t=1859714
vin4yak said:
Start Reading!
http://forum.xda-developers.com/showthread.php?t=1859714
Click to expand...
Click to collapse
I have no idea how I could have missed this guide. Many thanks!