Related
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
What does stock stand for?
udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.
El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App
Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.
I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.
Hey guys the official rom is out
http://blogs.att.net/consumerblog/story/a7783602
you have to update your device over kies.
Cheers
Got the message just now
" AT&T Free Msg: Samsung Captivate Glide upgrade to Android 4.0 Ice Cream Sandwich is now available! The OS update supports enhanced performance, user interface and other device improvements. Open the link from your PC (not your phone), and follow the instructions: www.samsung.com/us/attcaptivateglide/update "
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
page was working about an hour and now page not found. Maybe they pulled the update? I haven't tried it yet because of the keyboard backlight issue from other posts...and I have no desire to do any rooting/CWM stuff.
Page worked for me just now. It basically just says download kies and let it upgrade.
Does the official rom have the same version number as the leaked one?
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
There are no bugs, samsung has fixed it all
Does the official version have CarrierIQ?
Nevermind.
R3D X said:
There are no bugs, samsung has fixed it all
Click to expand...
Click to collapse
Oh? That's not what others have reported - the keyboard backlight is supposedly still broken, unsure about tethering or the other problems.
gnahc79 said:
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
Click to expand...
Click to collapse
No backlight on my wife's Glide... She's pissed...
Then root and install the zip
I actually passed on this phone because I was worried it might not get ICS. I'm glad it did all the same. I miss having a hard keyboard.
Sengfeng said:
No backlight on my wife's Glide... She's pissed...
Click to expand...
Click to collapse
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
gnahc79 said:
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
Click to expand...
Click to collapse
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
gnahc79 said:
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
Click to expand...
Click to collapse
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
Anh56 said:
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
Click to expand...
Click to collapse
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
bakageta said:
To fix the keyboard backlight bug, you'll need the following:
Odin 1.85
Clockworkmod Recovery
The Keyboard Backlight fix The one labeled LH2 is for the official, the one labeled CWM is for the leak. If you're not sure what you're on, go to About Phone, and check the Baseband Version, if it ends in LH2 you're on the official, if it ends in LG9 it's the leak.
Optionally, SuperUser 3.2 RC3 if you'd like root.
First, make sure you have Kies installed, so that you have the correct USB drivers. Download the 4.0.4 .exe file from here. Power off your phone, hold Volume Up and Power to turn it back on. Keep holding them until you get a screen warning you about custom software, and release, then press volume up again to enter download mode. Hook the phone up to your pc and run Odin 1.85. Uncheck "F. Reset Time" and make sure that the only box checked is Auto Reboot, you shouldn't need to change anything else. Click on the PDA button, and load the clockworkmod .md5 file you downloaded, then press the start button and wait for the device to reboot.
This time you'll reboot into recovery. Power the phone off, hold the volume down and power button to turn the phone one. Keep holding them until you see text about entering recovery in the top left, and release. Use the volume keys to navigate and power to select, and go to Install zip from sdcard. Select the keyboard backlight fix zip. Once that's finished, if you'd like to be rooted, repeat the process to flash a zip, and this time select Choose zip from sdcard, selecting the superuser zip you downloaded earlier. Select Yes, and wait for superuser to flash. If you plan on keeping Clockwork Mod Recovery, you should make a backup now. To do so, select Backup and restore, and backup. This will take a bit, just be patient. When you're finished, select reboot system now, and you should be set.
From here, if you rooted you can install something like Titanium Backup, which will use root access to let you remove the various AT&T bloatware.
Click to expand...
Click to collapse
Yeah backlight isn't working sorry, someone on a blog had said so. Very unprofessional of samsung. A rom cooked with cm9 willl have to include the backlight fix
bakageta said:
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
Click to expand...
Click to collapse
:good:
Cool, thanks for the info. Good to know root is not required. I'll still hold off on the update but I'm sure others will apply ICS+backlight fix.
I updated last night, and I can report that after ending any call the phone app reports a hard stop rather than just going away, and that resets your cell connection. And I imagine the keyboard backlight will be fixed very soon. But did these issues exist on the leaked rom in its first release and then programmers modified to get them back?
-Ara
Sent from my SGH-I927 using xda app-developers app
Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Boot in recovery now tgat you flashed stock rom. To boot in recovery press
Volume up+home button+on/off.
When samsung logo appears release the power button.
When it will boot in stock android recovery select wipe cache and wipe whole system (can't recall how it is written). Then select reboot now. That should do it.
Sent from my GT-N7100 using xda premium
mariosraptor said:
Volume up+home button+on/off.
Click to expand...
Click to collapse
That did not quite do it but I feel like a fool right now since this is the first time I realised that I mixed up Volume up and Volume down. But you gave me an option for that factory reset and after flashing CWM on top of that with ODIN it works again. One night wasted on nothing but my own lack of sleep and stupidity.
Thanks!
Good that it is working
Sent from my GT-N7100 using xda premium
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
SenK9 said:
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Anyway, glad it ended well for you OP!
Androssama said:
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Click to expand...
Click to collapse
Thanks! I haven't experimented much with custom kernels and my first try in combination with CM 10 didn't end that well. This gives me something to go from. Also I had a HTC Desire before and just got the Note 2 a few weeks ago, so there is another thing I have to get to know better.
Dude, please note that, for those kernels above which support both Touchwiz/Samsung and AOSP/Cyanogenmod based ROMS, there will be a separate version of the kernel for each.
hdr32 said:
Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Click to expand...
Click to collapse
As long as you can enter DOWNLOAD mode, your phone is NOT bricked. When you **** up your bootloader and stuff, then we can talk...
Hopefully this has taught you how important it is ti actually read up on something before you do it. Not only are the note2core and perseus kernels for samsung based roms only, other kernels such as redpill and neak only support the n7100 for their aosp/cm kernels.
As far as I know there is currently no other cm kernel for the n7105, although there is a neak cm kernel for the n7105 currently in beta testing.
Sent from my GT-N7100 using xda premium
No worries... learned my lesson... Sometimes I just need that smack in the face to get it.
And before I break my bootloader or some similar disaster occurs... I'll read first.
Sent from my GT-N7105 using xda app-developers app
Think we need a sticky with good instructions how to install and make a nandroid backup.
As well as sticky for EFS backup and why its so important to do it first and properly.
I know I had a lot of problems finding this info and implementing it proper,
Hi All,
Apologies if this is the wrong place to ask these questions. Please let me know if I should move the thread.
Backstory: I bought an unlocked S3 off of craigslist last weekend. I bought a SIM card adapter so my nano-sim from my iPhone 5 will work in the S3. I really love the phone, minus a few issues. I can't get LTE to work, and the battery seems to be pretty bad as it's constantly searching and dropping my 3g cell signal.
It's running Android 4.2.2 via Cyanogenmod. All I know is that this is not the standard Touchwiz OS that ships with the S3 from samsung, and is a variant of the standard 4.2.2 OS from Google.
Questions:
1. Is my lack of LTE due to the OS? Someone recommended to me that I should put the phone back to the stock Touchwiz OS (via Mobile Odin), which would enable the LTE. Think that's the case? Or is this an issue with my Nano SIM and AT&T account?
2. Using this Cyanogen 4.2.2, I don't get any onscreen notifications when I get a text, email or calendar alert. My friends with stock S3's and Notes all get these types of notifications. Am I missing something with Cyanogen 4.2.2 or should I try to go back to Touchwiz?
3. If I were to go back to touchwiz, I was told I could just download it onto my S3 sim card and install/load it via Mobile Odin. Is this the case? This is my first time working with Android phones, so it's all greek to me for now. If I switch to stock Touchwiz, will I lose all of my aps and configurations and have to re-set it up? What other cool things would I be losing?
I really do love this phone and would love to stick with it over my iPhone 5. The lack of LTE, good battery life (probably can be improved with tweaks) and onscreen notifications are making it tough for me to make this my daily driver.
Any and all help is greatly appreciated!!
what is the model number of your device? i747, i9300, etc.
without getting too technical at the moment, you're running a nightly release (not always stable) of an operating system. it was probably flashed on your device half-a** and you are experiencing bugs because of these 2 things. the thing about buying a used phone that is rooted running a custom rom is, you dont have a clue about its history. how things were run/setup/installed, etc. not a deal breaker, as i bought mine used, just have to consider starting over with it from square A in order to get and keep it running properly.
before you start changing/flashing anything, i would browse the forum and begin reading up. the more you know, the smoother and safer everything will go for you
xBeerdroiDx said:
what is the model number of your device? i747, i9300, etc.
without getting too technical at the moment, you're running a nightly release (not always stable) of an operating system. it was probably flashed on your device half-a** and you are experiencing bugs because of these 2 things.
before you start changing/flashing anything, i would browse the forum and begin reading up. the more you know, the smoother and safer everything will go for you
Click to expand...
Click to collapse
Model # is SGH-i747.
CyanogenMod version: 10.1-20130304-NIGHTLY-d2ATT
Build date: 3/4 2013
So the build is slightly out of date. Any recommendations on what I should do? Download the latest version? Buy MobilOdin and re-install touchwiz?
Thanks!
diggity said:
Model # is SGH-i747.
CyanogenMod version: 10.1-20130304-NIGHTLY-d2ATT
Build date: 3/4 2013
So the build is slightly out of date. Any recommendations on what I should do? Download the latest version? Buy MobilOdin and re-install touchwiz?
Thanks!
Click to expand...
Click to collapse
in my opinion, i would start over. thats just me, though. you might not want to download and setup everything again, though. if you do opt to reset, decide if you want to continue using a custom ROM or stock Samsung Touchwiz. in either case, you wont need to purchase anything. do you have a PC?
xBeerdroiDx said:
in my opinion, i would start over. thats just me, though. you might not want to download and setup everything again, though. if you do opt to reset, decide if you want to continue using a custom ROM or stock Samsung Touchwiz. in either case, you wont need to purchase anything. do you have a PC?
Click to expand...
Click to collapse
Nope I have a Mac, although I do have access to a PC at work if needbe though. When you mean start over, what do you mean? Sorry, gotta talk to me like I'm a 5yr old here for a bit. I'm not too versed or experienced with Android and development. I've been in the iOS world since 07.
diggity said:
Nope I have a Mac, although I do have access to a PC at work if needbe though. When you mean start over, what do you mean? Sorry, gotta talk to me like I'm a 5yr old here for a bit. I'm not too versed or experienced with Android and development. I've been in the iOS world since 07.
Click to expand...
Click to collapse
by start over i mean wipe the phone and install an OS. but only once you're sure of what you're doing.
xBeerdroiDx said:
by start over i mean wipe the phone and install an OS. but only once you're sure of what you're doing.
Click to expand...
Click to collapse
Would that remove the unlock?
How do I do that? What do install instead? Touchwiz or newest Cyanogenmod? If so, where do I get the latest/greatest of either?
Thanks!!
diggity said:
Would that remove the unlock?
How do I do that? What do install instead? Touchwiz or newest Cyanogenmod? If so, where do I get the latest/greatest of either?
Thanks!!
Click to expand...
Click to collapse
is this an at&t S3 on tmobile?
you shouldn't lose sim lock when you flash ROMs/firmware. did you get the unlock code from the seller, in the event you ever do have an issue where you need it?
xBeerdroiDx said:
is this an at&t S3 on tmobile?
you shouldn't lose sim lock when you flash ROMs/firmware. did you get the unlock code from the seller, in the event you ever do have an issue where you need it?
Click to expand...
Click to collapse
It's an AT&T S3 on AT&T (using my iphone 5 nanosim). I guess I didnt need to buy it unlocked, but that's what I got off of craigslist. I did not get the unlock code from the seller, but I could probably still get that from them easily.
diggity said:
It's an AT&T S3 on AT&T (using my iphone 5 nanosim). I guess I didnt need to buy it unlocked, but that's what I got off of craigslist. I did not get the unlock code from the seller, but I could probably still get that from them easily.
Click to expand...
Click to collapse
Read the thread in the development section about how to root without flashing trip counter. It tells you where to download Odin, what file to download and flash, and how to do it. Can get you back on a stock touchwiz ROM (+ root) in no time!
Sent from my SAMSUNG-SGH-I747
phositadc said:
Read the thread in the development section about how to root without flashing trip counter. It tells you where to download Odin, what file to download and flash, and how to do it. Can get you back on a stock touchwiz ROM (+ root) in no time!
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Great thanks! I'll give it a shot! You think getting back to stock touchwiz will fix my LTE, battery and notificaiton issues?
Thank you for all your help!
diggity said:
Great thanks! I'll give it a shot! You think getting back to stock touchwiz will fix my LTE, battery and notificaiton issues?
Thank you for all your help!
Click to expand...
Click to collapse
i think that returning to stock is the best way to get started on fixing these issues, whether you decide to stay on it or continue on to flashing something else.
here's the link to the stock firmware download: http://www.androidfilehost.com/?fid=9390212717148635192
here's the link to Odin: http://www.androidfilehost.com/?fid=9390275921635705049
here's a video i would recommend watching first: http://youtu.be/hqDW--uUX_8
Part 1: Backup and Wipe
Boot into recovery (vol up + home + power. release power button when device vibrates)
Go to backup and restore (use Volume Up / Down buttons in CWM).
Select Backup (power button in CWM).
After backup, go back to main screen and select Wipe data/factory reset
Select Wipe Cache
Select Advanced and Wipe Dalvik Cache
Part 2: Install stock firmware and Wipe
Extract the root66_xxx_.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_.tar.md5 you downloaded.
Leave F. Reset Time checked.
click start
When you get a PASS, unplug the phone and pull the battery. wait a second, replace and immediately go into recovery (vol up + home + power. release the power button at vibrate)
Select wipe data and wipe cache again.
Reboot and you're good to go
diggity said:
Great thanks! I'll give it a shot! You think getting back to stock touchwiz will fix my LTE, battery and notificaiton issues?
Thank you for all your help!
Click to expand...
Click to collapse
I agree with the above poster, returning to stock using the described method should fix your problems then you can decide if you want to stay stock or flash another ROM.
I think you should stay stock for at least a few days to get a general sense of how things should work, that way when you flash custom ROMs you will have a better idea what is broken and what is just typical android behavior.
Sent from my SAMSUNG-SGH-I747
phositadc said:
I think you should stay stock for at least a few days to get a general sense of how things should work, that way when you flash custom ROMs you will have a better idea what is broken and what is just typical android behavior.
Click to expand...
Click to collapse
agreed. as a matter of fact, stay stock for a week. the first 48 hours will really be just letting the software settle in. dont judge battery performance based off those first 2 or 3 days. let it get up and running.
Check your APN see if they are correct
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
hey let me ask you a stoopid question do you have some kinda case that has metal on the back on that phone,i ordered one of those battery covers that was like a metallic silver thats around the edges of the phone the white one anyway,and for the life of me i couldnt figure out why i wasnt gettin gps it was that cover,some of the cases that have metal on them or the battery back replacements that i had stay away form,but anyway pull your cover off and see if you lock u can also tighten up the screw under the cover
So I was working on putting on a new ROM and when I went to install the PA G Apps zip it said in my recovery that I didn't have enough space in the system storage. Which was a little confusing since I had just wiped it like usual through the recovery before I do a ROM. However I was navigating the recovery since it had been a while and just check out some of the things I didn't notice that changed. Went to the Mounts and Storage area, then I guess I touched "Format /system" and when I realized that it moved to asking me if I wanted to format /system I tried to push NO but apparently I have fat fingers and still pushed yes...So now after having rebooted the phone it is stuck at the screen "Google *small unlocked Lock at the bottom*". And now I'm not sure what to do.
Any advice?
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Well this is nothing serious. Just reflash your ROM or flash the new one you werd gonna flash..
P.s. formatting system is a good idea anyway before flashing a new ROM..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Well the issue is it is stuck...I let it sit for at least 5min or so and it just sat there at that same spot. Is that because I need to reflash it? I have the Galaxy Nexus Toolkit, but I haven't used it as of late since I haven't needed it. If you don't mind going into detail I would appreciate it .
Should also mention if I go into the bootloader, it hangs at "Downloading..." so effectively I can't do anything to reflash my ROM or anything. And I probably should be clear that this all happened AFTER I flashed the new ROM and then remembered I needed the PA G Apps. Should have refreshed my memory with doing this sort of thing since I'm not as experienced as I use to be long ways back.
Ysosrslawl said:
Should also mention if I go into the bootloader, it hangs at "Downloading..."
Click to expand...
Click to collapse
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
AndyYan said:
Did you actually use the right combination to go to bootloader? Because from what I understand, you simply wiped your /system clean, which is a simple matter to fix - just flash any ROM or restore any valid backup to make it work again.
Sent from Google Nexus 4 @ CM11
Click to expand...
Click to collapse
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Ysosrslawl said:
Volume button then Power button until it vibrates then keep holding down the volume button? Only way I know how to do it, seeing as I've never heard of another way to do it.
Click to expand...
Click to collapse
Yeah, make sure you hold BOTH volume keys for bootloader. Hold only VOLUME- for Download mode as you've seen before. If you indeed held both keys but still got to Download mode, chances are you have a broken volume key.
Sent from Google Nexus 4 @ CM11
Yep I'm dumb apparently and misjudged how the buttons were being pressed down...now on to step 2! Hmmm....
Seems like the zip for the ROM isnt in the storage anymore. How do I copy it back on from just being in fastboot mode or recovery? I'm not familiar with ADB at all. I may have figured out the problem so hold on...I think I derped and forgot that I removed the device drivers off my desktop because I wanted to fresh install them way back.
Edit2: Doing this the hard way.
OK SO I feel like a total noob, which I really am. I've never used ADB, never tried pushing files, or anything of the sort. I tried for a very long time to get the Galaxy Nexus toolkit to help me out but it REALLY didn't do ANYTHING for me. None of the options worked like I had hoped, the ONLY thing it did for me was to install the missing drivers I needed. Other than that it was utterly useless. You guys may find this funny, but I really had no idea on how to fix this even in the slightest. Even with the responses put here by some of the community.
However, with a little searching I was able to find the answers to my questions, not found here on XDA unfortunately. What I ended up doing was updating my SDK tools and learning how to open up ADB (had no idea why the adb.exe wasn't just opening for me like I assumed it would). From there I used the sideload option in my recovery to help me get my ROM flashed back on my phone. So now all is well and I can go back to being a noob who just likes to find good looking ROMS and play with them every couple months.
Thanks, my issue is now resolved.