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
I bought a used nexus its in great condition everything works but the buyer didnt tell me it was rooted already. Thats fine cause i was going to but i wanted to learn the ropes myself. So is there anyone to get back to 100% stock? He flashed a CWM too. I just want to do it myself. And is there anyway to wipe format the internal memory aswell? Thanks!
you can use this guide : http://forum.xda-developers.com/showthread.php?t=1626895
even if you don't want to convert and already have yakju or takju, this is the way you can go back to pure stock
bgdxv said:
you can use this guide : http://forum.xda-developers.com/showthread.php?t=1626895
even if you don't want to convert and already have yakju or takju, this is the way you can go back to pure stock
Click to expand...
Click to collapse
Yup this guide is the way to go. Flash the "takju" images. There's full 4.1.1 images now too.
Thanks guys i have a usa gsm model and I guess i looked around and found out a way to wipe the internal data with those tools so i think im good and im kinda getting the hang of using the tool kit. But the phone has 4.1 i wanted to install rooted 4.1.1 is that possible? or how would i go about doing that? Thanks alot for your quick and helpful responses!
Nocturnal86 said:
Thanks guys i have a usa gsm model and I guess i looked around and found out a way to wipe the internal data with those tools so i think im good and im kinda getting the hang of using the tool kit. But the phone has 4.1 i wanted to install rooted 4.1.1 is that possible? or how would i go about doing that? Thanks alot for your quick and helpful responses!
Click to expand...
Click to collapse
Don't use a toolkit. Follow that guide posted. That guide will wipe the device completely and put you on 100% stock 4.1.1. If you want root, you can follow the last part of the guide, which has a step-by-step routine to root also.
martonikaj said:
Don't use a toolkit. Follow that guide posted. That guide will wipe the device completely and put you on 100% stock 4.1.1. If you want root, you can follow the last part of the guide, which has a step-by-step routine to root also.
Click to expand...
Click to collapse
Why shouldnt i use the tools? they seem pretty straight foward is there something bad about them? But Im finally going to get a chance to follow that guide hopefully and go to 4.1.1 and then root it cause i just want root right now for back up purposes. But thans for the info!
Nocturnal86 said:
Why shouldnt i use the tools? they seem pretty straight foward is there something bad about them? But Im finally going to get a chance to follow that guide hopefully and go to 4.1.1 and then root it cause i just want root right now for back up purposes. But thans for the info!
Click to expand...
Click to collapse
The tools aren't inherently bad, but they're kind of a "black box" to new users, where they put their phone in and it comes out rooted/flashed. The issue occurs when something goes wrong, and the user doesn't know why because they don't understand the procedure, and they can't reverse engineer what happened to fix it. So what they end up doing is coming and posting threads, etc.
If they were doing it the "real" (manual) way, via Fastboot, they'd know what was going on and have a better understanding of what they're doing to their phone. Because we have a Nexus, there's really no reason not to just use Fastboot because it's the tool that Google gives us. You own a ~$650 (much cheaper now w/ the Play Store, but still) device, why not spend 15 minutes learning how to work with it properly?
martonikaj said:
The tools aren't inherently bad, but they're kind of a "black box" to new users, where they put their phone in and it comes out rooted/flashed. The issue occurs when something goes wrong, and the user doesn't know why because they don't understand the procedure, and they can't reverse engineer what happened to fix it. So what they end up doing is coming and posting threads, etc.
If they were doing it the "real" (manual) way, via Fastboot, they'd know what was going on and have a better understanding of what they're doing to their phone. Because we have a Nexus, there's really no reason not to just use Fastboot because it's the tool that Google gives us. You own a ~$650 (much cheaper now w/ the Play Store, but still) device, why not spend 15 minutes learning how to work with it properly?
Click to expand...
Click to collapse
I can understand that and i usually do want to learn the ropes but i was kind of thrust into the middle cause i bought a used nexus and it was rooted and had CWM 6 flashed to it so I am just trying to figure things out a bit or at least go back to Full stock and no recovory flashed so i can learn the ropes myself and flash recoverys myself if needed and i want to get 4.1.1 and root it myself. If possible can i use the tools to just go to stock and then learn the manual ways from there? I got adb and the fastboot.exe finally so i never had that or new i needed it and when i first used the toolkit to wipe my sd I think it installed some drivers that the tool kit told me to which im hoping are correct. I really hate to ask questions unless its needed and i apprecieate it.
Nocturnal86 said:
I can understand that and i usually do want to learn the ropes but i was kind of thrust into the middle cause i bought a used nexus and it was rooted and had CWM 6 flashed to it so I am just trying to figure things out a bit or at least go back to Full stock and no recovory flashed so i can learn the ropes myself and flash recoverys myself if needed and i want to get 4.1.1 and root it myself. If possible can i use the tools to just go to stock and then learn the manual ways from there? I got adb and the fastboot.exe finally so i never had that or new i needed it and when i first used the toolkit to wipe my sd I think it installed some drivers that the tool kit told me to which im hoping are correct. I really hate to ask questions unless its needed and i apprecieate it.
Click to expand...
Click to collapse
The guide that was linked earlier is extremely simple to follow. It breaks everything down step by step, and you will be fully stock.
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?
HI,
I've using my Galaxy Nexus (GSM) for a long time, but i want to get Root access, i've been reading a lot and it seems if i use Galaxy Nexus Toolkit it will delete all my data, there's any way to root it without losing any data?
Thanks a lot! :good: :fingers-crossed:
milerx said:
HI,
I've using my Galaxy Nexus (GSM) for a long time, but i want to get Root access, i've been reading a lot and it seems if i use Galaxy Nexus Toolkit it will delete all my data, there's any way to root it without losing any data?
Thanks a lot! :good: :fingers-crossed:
Click to expand...
Click to collapse
no.
you have to unlock your bootloader (no matter which method you use, also, dont use a toolkit, use the sticky at the top of the forum) which wipes your data. period.
Zepius said:
you have to unlock your bootloader (no matter which method you use, also, dont use a toolkit, use the sticky at the top of the forum) which wipes your data. period.
Click to expand...
Click to collapse
I did a root of my Galaxy Nexus, when I flashed the new 4.1. It did work fine. When the phone did the small update to 4.1.2, can it be true that it rolled back the root? My phone don't seem to be rooted anymore.
Isn't it possible to get root permissions again, without loosing data?
IsonNick said:
I did a root of my Galaxy Nexus, when I flashed the new 4.1. It did work fine. When the phone did the small update to 4.1.2, can it be true that it rolled back the root? My phone don't seem to be rooted anymore.
Isn't it possible to get root permissions again, without loosing data?
Click to expand...
Click to collapse
if your bootloader is unlocked, reflash the supersu.zip
otherwise, you have to unlock the bootloader and it will wipe your device.
Zepius said:
if your bootloader is unlocked, reflash the supersu.zip
Click to expand...
Click to collapse
It should be. Anyway to see that?
(sorry for noob questions)
IsonNick said:
It should be. Anyway to see that?
(sorry for noob questions)
Click to expand...
Click to collapse
if you enter fastboot, it will says "lock status: unlocked"
or you can see if when you first start up your phone if there's a little lock that is unlocked.
Zepius said:
or you can see if when you first start up your phone if there's a little lock that is unlocked.
Click to expand...
Click to collapse
Hep hep! The lock is unlocked. Perfect.
When I receive the 4.2 update (my phone is yakju), I will root again. Thank you for your help, I appreciate it a lot.
Similar thing happened to me. I was messing around with different ROM's for some time but in the end went back to the stock ROM. My phone now shows unlocked and using the stock recovery (as described here http://forums.androidcentral.com/google-samsung-galaxy-nexus/243004-recovery-mode.html).
The stock recovery offers 4 options: reboot, apply update from ADB or USB, wipe.
How do I "reflash the supersu.zip" from here? I want to avoid wiping as everything is set up as I like it now, and because it isn't rooted I can't back it up, catch 22 thing
madsere said:
Similar thing happened to me. I was messing around with different ROM's for some time but in the end went back to the stock ROM. My phone now shows unlocked and using the stock recovery (as described here http://forums.androidcentral.com/google-samsung-galaxy-nexus/243004-recovery-mode.html).
The stock recovery offers 4 options: reboot, apply update from ADB or USB, wipe.
How do I "reflash the supersu.zip" from here? I want to avoid wiping as everything is set up as I like it now, and because it isn't rooted I can't back it up, catch 22 thing
Click to expand...
Click to collapse
Why did you bump a 4 months old thread?
Obviously, you need a custom recovery to flash a non-Google zip...
Sent from my Nexus
bk201doesntexist said:
Why did you bump a 4 months old thread?
Obviously, you need a custom recovery to flash a non-Google zip...
Sent from my Nexus
Click to expand...
Click to collapse
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
madsere said:
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
Click to expand...
Click to collapse
Yeah?
Then it would be nice if you read the stickies.
Sent from my Nexus
madsere said:
I'm sorry, I didn't know there was a rule against that. I searched Google for the problem and this thread came up closest.
Well sorry if I am not a genius like you who know everything already. I thought that forums like this was for asking questions.
It would be nice if instead of just being mean and nasty you'd offer some constructive suggestions, such as would installing a custom recovery wipe the phone? The distinction between the boot loader and the custom recovery isn't clear to me.
Click to expand...
Click to collapse
Sarcastic, aren't we? Look, XDA is first and foremost a developer site for developers to develop. Answering and asking questions about that development is only incidental. Members are expected to have read the rules of XDA and to follow them. That includes not bumping old threads, but it also includes an expectation that you will read the information readily available to you. Seeing the same common questions get asked daily, when there are good guides made specifically for this purpose, gets very old very fast. The constructive suggestion is to search and read. Guides abound both in the stickies and elsewhere, and the fact that you haven't found answers to your fairly common questions tells me that you either haven't made an effort to look, or you just don't understand and therefore probably shouldn't be messing with your phone.
I was able to root my gnex without wiping the data!
I dont know how it happened, but it happened, I was surprised too because I was really frustrated couldn't root it even after 10-15 tries ( I am a big time noob) and suddenly I unlocked the boot loader and rooted the phone without any loss of data, actually I was rooting because I had the VM100U something memory issue and my phone was terribly slow! I was surprised becasue i was expecting to copy all my files and crap one by one but now I have no issues
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.